{"id": "a7b82c5a0136-0", "text": "InterTest\u2122 and SymDump\u00ae 11.0", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "99573e741ec1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTable of Contents\nAnnouncements and News ...............................................................................................................63\nRelease Information ...........................................................................................................................64\nGA Continuous Delivery Release .................................................................................................................................72\nSMP/E Internet Service Retrieval Maintenance ............................................................................................................72\nEclipse Plugin Compatibility .........................................................................................................................................73\nPortfolio Simplification ..................................................................................................................................................73\nRelease Comparison ......................................................................................................................................................74\nThird Party Software Requirements .............................................................................................................................77\nProduct Accessibility Features .....................................................................................................................................78\nProduct Names and Abbreviations ..............................................................................................................................83\nInstalling ..............................................................................................................................................84\nPrepare for Installation ..................................................................................................................................................86\nInstallation Checklist ..................................................................................................................................................87\nInstallation Considerations ........................................................................................................................................89\nReview Installation and Configuration Best Practices ..............................................................................................93\nProduct Requirements ...............................................................................................................................................94\nConcurrent Releases ...............................................................................................................................................101\nInstall Products Using z/OSMF ...................................................................................................................................101\nAddress z/OSMF Requirements .............................................................................................................................102\nAcquire a z/OSMF Portable Software Instance ......................................................................................................103\nInstall Product Software Using z/OSMF Deployments ...........................................................................................105\nImport Product Information into z/OSMF ................................................................................................................107\nInstall Products Using CSM ........................................................................................................................................110\nAcquire Your Product Using CSM..........................................................................................................................111\nInstall Your Product Using CSM.............................................................................................................................114\nInstall Products Using SMP/E JCL .............................................................................................................................124\nAllocate and Mount a File System ..........................................................................................................................126\nAcquire the Product Pax Files ................................................................................................................................127\nCreate a Product Directory from the Pax File ........................................................................................................128\nCopy Installation Files to z/OS Data Sets ..............................................................................................................129\nPrepare the SMP/E Environment for a Pax Installation .........................................................................................130\nRun the Installation Jobs for a Pax Installation ......................................................................................................131\nClean Up the USS Directory ...................................................................................................................................132\nConfiguring ....................................................................................................................................................................132\nConfiguration Best Practices ...................................................................................................................................133", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "99573e741ec1-1", "text": "Configuring ....................................................................................................................................................................132\nConfiguration Best Practices ...................................................................................................................................133\nConfigure an InterTest and SymDump Software Instance Using z/OSMF Workflows............................................136\n 2", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2bfdc2a37d8c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nConfigure Your Product With CSM .........................................................................................................................139\nConfigure Your Product Without CSM ....................................................................................................................146\nConfiguring SymDump  for CICS ......................................................................................................................146\nConfiguring InterTest for CICS .........................................................................................................................146\nConfiguring SymDump  Batch ..........................................................................................................................147\nConfiguring InterTest Batch .............................................................................................................................147\nOptions .............................................................................................................................................................148\nUser Exits .........................................................................................................................................................195\nAllocate Files ....................................................................................................................................................225\nInterfaces and Compatibility ............................................................................................................................229\nActivate Your Product......................................................................................................................................271\nInstallation Verification.....................................................................................................................................278\nInstall Maintenance ......................................................................................................................................................282\nMaintain Products Using z/OSMF Software Update ..............................................................................................282\nMaintain Products Using CSM ................................................................................................................................283\nMaintain Products Using SMP/E JCL .....................................................................................................................297\nHOLDDATA..............................................................................................................................................................300\nDeployment ...................................................................................................................................................................301\nInstalling the Eclipse User Interface ..........................................................................................................................302\nInstall Testing Tools Server and REST API...............................................................................................................303\nIntegrate REST API with the Mediation Layer .......................................................................................................306\nConfigure PassTickets for the API Mediation Layer...............................................................................................308\nGetting Started .................................................................................................................................312\nInterTest for CICS Primers ..........................................................................................................................................312\nAssembler Primer ....................................................................................................................................................312\nAssembler Basic Demo Session .....................................................................................................................312\nAssembler Debugging Programs .....................................................................................................................328\nAssembler Advanced Monitoring Features ......................................................................................................345\nAssembler Advanced Demo Session ..............................................................................................................358\nCOBOL Primer ........................................................................................................................................................381\nCOBOL Basic Demo Session ..........................................................................................................................381\nCOBOL Debugging Programs .........................................................................................................................396\nCOBOL Advanced Monitoring Features ..........................................................................................................416\nCOBOL Advanced Demo Session ...................................................................................................................434\nPL/I Primer ..............................................................................................................................................................476\nPL/I Basic Demo Session ................................................................................................................................476", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2bfdc2a37d8c-1", "text": "PL/I Primer ..............................................................................................................................................................476\nPL/I Basic Demo Session ................................................................................................................................476\nPL/I Debugging Programs ...............................................................................................................................491\nPL/I Advanced Monitoring Features ................................................................................................................509\nPL/I Advanced Demo Session .........................................................................................................................527\nInterTest Batch Demo Sessions .................................................................................................................................560\n 3", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d02c7848b9b1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBasic Foreground Demo Session ...........................................................................................................................560\nBasic Batch Link Demo ..........................................................................................................................................570\nAdvanced Demo Session ........................................................................................................................................573\nAdvanced Demo Preliminaries ........................................................................................................................574\nAdvanced Demo Session for COBOL .............................................................................................................577\nAdvanced Demo Session for Assembler .........................................................................................................599\nAdvanced Demo Session for PL/I ...................................................................................................................610\nQuick References .........................................................................................................................................................635\nUsing ..................................................................................................................................................637\nUsing Batch Tools........................................................................................................................................................637\nBatch Debugging .....................................................................................................................................................638\nPanels and Functions ......................................................................................................................................639\nDebugging Panels ............................................................................................................................................642\nCore Option ......................................................................................................................................................655\nMap Option .......................................................................................................................................................657\nDebugging Commands ....................................................................................................................................658\nTesting Procedures..........................................................................................................................................731\nAllocations Facility for ISPF .............................................................................................................................745\nJCL Conversion for Roscoe ............................................................................................................................759\nBatch Link Facility ............................................................................................................................................762\nInterTest Batch Utilities ....................................................................................................................................781\nDDnames and Sample CLISTs........................................................................................................................784\nBatch Abend Analysis .............................................................................................................................................786\nUsing Symbolic Support ..................................................................................................................................787\nReporting ..........................................................................................................................................................789\nCAIPRINT Repository Viewer..........................................................................................................................862\nSymDump  Batch Utilities .................................................................................................................................900\nDynamic Symbolic Support ..............................................................................................................................912\nTroubleshooting................................................................................................................................................913\nUsing the Batch REST API .....................................................................................................................................915\nBatch REST API: Reports ...............................................................................................................................916\nBatch REST API: Full Dump with Index ..........................................................................................................918\nBatch REST API: Lock ....................................................................................................................................920\nBatch REST API: Unlock .................................................................................................................................921\nBatch REST API: Delete .................................................................................................................................922\nBatch REST API: Options ...............................................................................................................................923\nBatch REST API: Display Report Options ......................................................................................................924\nBatch REST API: Update Report Options .......................................................................................................926", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d02c7848b9b1-1", "text": "Batch REST API: Update Report Options .......................................................................................................926\nUsing CICS Tools.........................................................................................................................................................930\nCICS Debugging .....................................................................................................................................................931\n 4", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b2de9f47fd1b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMenus and Displays ........................................................................................................................................935\nSource Listing Facility for InterTest.................................................................................................................942\nUsing Breakpoints ............................................................................................................................................974\nBreakpoint Activities .........................................................................................................................................988\nComposite Support ........................................................................................................................................1038\nResume and Execution Options ....................................................................................................................1045\nMonitoring Menu Options ...............................................................................................................................1051\nSpecial Monitoring Situations ........................................................................................................................1068\nCNTL Commands and Menus .......................................................................................................................1085\nAccessing Main Storage CORE ....................................................................................................................1134\nAccessing Auxiliary Storage FILE .................................................................................................................1173\nUsing InterTest for CICS with DB2 and SQL/DS Programs ..........................................................................1221\nAnalyzing Dumps Symbolically SymDump  for CICS Option .........................................................................1230\nBreakpoint Displays for NonSymbolic Programs ...........................................................................................1231\nExamining Dumps ..........................................................................................................................................1240\nUsing the FOL= Option ..................................................................................................................................1245\nMonitoring Restrictions ...................................................................................................................................1246\nSYSVIEW  Integration .....................................................................................................................................1247\nCICS Abend Analysis ............................................................................................................................................1249\nCapturing Dumps ...........................................................................................................................................1252\nWorking with Dumps.....................................................................................................................................1255\nSource Listing Facility for SymDump ............................................................................................................1288\nBatch Utility ....................................................................................................................................................1303\nPrinting Dumps ...............................................................................................................................................1308\nProduction Strategies .....................................................................................................................................1312\nUsing InterTest for CICS to Find Errors ........................................................................................................1334\nUsing the CICS REST API ...................................................................................................................................1336\nCICS REST API: Reports ..............................................................................................................................1336\nCICS REST API: Full Dump with Index ........................................................................................................1338\nCICS REST API: Lock ...................................................................................................................................1339\nCICS REST API: Unlock ...............................................................................................................................1340\nCICS REST API: Delete ................................................................................................................................1342\nCICS REST API: Options ..............................................................................................................................1343", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b2de9f47fd1b-1", "text": "CICS REST API: Options ..............................................................................................................................1343\nDWARF..................................................................................................................................................................1344\nCOBOL Basic Demo Session for DWARF....................................................................................................1347\nDWARF FAQ..................................................................................................................................................1358\nUsing the Eclipse UI ..................................................................................................................................................1359\nUnderstanding Your Workspace...........................................................................................................................1361\nDebugging with the Eclipse UI .............................................................................................................................1364\nAbend Analysis with the Eclipse UI ......................................................................................................................1374\n 5", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3056bcde0d71-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBreakpoints .....................................................................................................................................................1377\nBookmarks ......................................................................................................................................................1383\nVisual Debugger....................................................................................................................................................1384\nGetting Started with Visual Debugger...........................................................................................................1384\nStatement Trace Visualization.......................................................................................................................1387\nDynamic Graph Update .................................................................................................................................1390\nNavigate Execution Flow History ...................................................................................................................1392\nLink with Editor ..............................................................................................................................................1393\nZoom and Pan ...............................................................................................................................................1396\nSave and Load Session Data ........................................................................................................................1398\nIntegrating .......................................................................................................................................1403\nSymbolic Support .......................................................................................................................................................1403\nCreating a PROTSYM File ....................................................................................................................................1406\nAdding Symbolic Information ................................................................................................................................1408\nIN25SYMC ......................................................................................................................................................1408\nIN25COB2 ......................................................................................................................................................1413\nIN25SYMP ......................................................................................................................................................1420\nIN25SYMA ......................................................................................................................................................1425\nIN25LINK ........................................................................................................................................................1430\nIN25SYMD ......................................................................................................................................................1434\nMaintaining a PROTSYM File ...............................................................................................................................1436\nDynamic Symbolic Support for Endevor  Software Change Manager ...................................................................1442\nRestrictions for PL/I ...............................................................................................................................................1446\nHow Postprocessors Store Symbolic Information ................................................................................................1447\nCOBOL OPTIMIZE Compiler Option ....................................................................................................................1448\nDebugger for Mainframe Extension for VS Code ...................................................................................................1450\nAbend Analyzer for Mainframe Extension for Visual Studio Code.......................................................................1450\nMessages and Codes ....................................................................................................................1452\nInterTest for CICS Messages ....................................................................................................................................1455\nCAIN3478 ..............................................................................................................................................................1455\nCAIN5340 ..............................................................................................................................................................1455\nCAIN5900 ..............................................................................................................................................................1455\nCAIN5901 ..............................................................................................................................................................1455\nCAIN5902 ..............................................................................................................................................................1456", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3056bcde0d71-1", "text": "CAIN5902 ..............................................................................................................................................................1456\nCAIN5903 ..............................................................................................................................................................1456\nCAIN5904 ..............................................................................................................................................................1456\nCAIN5905 ..............................................................................................................................................................1456\nCAIN5906 ..............................................................................................................................................................1456\nCAIN5907 ..............................................................................................................................................................1457\n 6", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "810eb468cba7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN5908 ..............................................................................................................................................................1457\nCAIN5909 ..............................................................................................................................................................1457\nCAIN5910 ..............................................................................................................................................................1457\nCAIN5911..............................................................................................................................................................1457\nCAIN5912 ..............................................................................................................................................................1458\nCAIN5913 ..............................................................................................................................................................1458\nCAIN5914 ..............................................................................................................................................................1458\nCAIN5915 ..............................................................................................................................................................1458\nCAIN5916 ..............................................................................................................................................................1458\nCAIN5917 ..............................................................................................................................................................1459\nCAIN5918 ..............................................................................................................................................................1459\nCAIN5919 ..............................................................................................................................................................1459\nCAIN5920 ..............................................................................................................................................................1459\nCAIN5930 ..............................................................................................................................................................1459\nCAIN5950 ..............................................................................................................................................................1459\nCAIN5951 ..............................................................................................................................................................1460\nCAIN5952 ..............................................................................................................................................................1460\nCAIN5953 ..............................................................................................................................................................1460\nCAIN5980 ..............................................................................................................................................................1460\nCAIN5981 ..............................................................................................................................................................1460\nCAIN5982 ..............................................................................................................................................................1461\nCAIN5984 ..............................................................................................................................................................1461\nCAIN5990 ..............................................................................................................................................................1461\nCAIN5992 ..............................................................................................................................................................1462\nCAIN5993 ..............................................................................................................................................................1462\nCAIN5994 ..............................................................................................................................................................1462\nCAIN5995 ..............................................................................................................................................................1462\nCAIN5996 ..............................................................................................................................................................1462\nCAIN5997 ..............................................................................................................................................................1463\nCAIN5999 ..............................................................................................................................................................1463\nSymDump  for CICS Online Messages .....................................................................................................................1463\nCASD3469 .............................................................................................................................................................1463\nCASD3470 .............................................................................................................................................................1463\nCASD6048 .............................................................................................................................................................1464\nCASD6049 .............................................................................................................................................................1464", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "810eb468cba7-1", "text": "CASD6049 .............................................................................................................................................................1464\nCASD6050 .............................................................................................................................................................1464\nCASD6069 .............................................................................................................................................................1464\nCASD6070 .............................................................................................................................................................1464\nCASD6071 .............................................................................................................................................................1464\nCASD6072 .............................................................................................................................................................1465\n 7", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7bd0bd44ec7f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6073 .............................................................................................................................................................1465\nCASD6074 .............................................................................................................................................................1465\nCASD6077 .............................................................................................................................................................1465\nCASD6078 .............................................................................................................................................................1465\nCASD6079 .............................................................................................................................................................1465\nCASD6080 .............................................................................................................................................................1466\nCASD6081 .............................................................................................................................................................1466\nCASD6082 .............................................................................................................................................................1466\nCASD6083 .............................................................................................................................................................1466\nCASD6084 .............................................................................................................................................................1466\nCASD6085 .............................................................................................................................................................1466\nCASD6086 .............................................................................................................................................................1467\nCASD6101 .............................................................................................................................................................1467\nCASD6102 .............................................................................................................................................................1467\nCASD6103 .............................................................................................................................................................1467\nCASD6104 .............................................................................................................................................................1468\nCASD6105 .............................................................................................................................................................1468\nCASD6106 .............................................................................................................................................................1468\nCASD6108 .............................................................................................................................................................1468\nCASD6109 .............................................................................................................................................................1468\nCASD6110.............................................................................................................................................................1468\nCASD6111.............................................................................................................................................................1469\nCASD6112.............................................................................................................................................................1469\nCASD6113.............................................................................................................................................................1469\nCASD6114.............................................................................................................................................................1469\nCASD6115.............................................................................................................................................................1469\nCASD6116.............................................................................................................................................................1470\nCASD6117.............................................................................................................................................................1470\nCASD6118.............................................................................................................................................................1470\nCASD6119.............................................................................................................................................................1470\nCASD6122 .............................................................................................................................................................1470\nCASD6123 .............................................................................................................................................................1471\nCASD6124 .............................................................................................................................................................1471\nCASD6125 .............................................................................................................................................................1471\nCASD6126 .............................................................................................................................................................1471", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7bd0bd44ec7f-1", "text": "CASD6126 .............................................................................................................................................................1471\nCASD6127 .............................................................................................................................................................1471\nCASD6128 .............................................................................................................................................................1471\nCASD6129 .............................................................................................................................................................1472\nCASD6176 .............................................................................................................................................................1472\nCASD6177 .............................................................................................................................................................1472\n 8", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a297279f4abb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6178 .............................................................................................................................................................1472\nCASD6179 .............................................................................................................................................................1472\nCASD6180 .............................................................................................................................................................1472\nCASD6181 .............................................................................................................................................................1473\nCASD6182 .............................................................................................................................................................1473\nCASD6183 .............................................................................................................................................................1473\nCASD6184 .............................................................................................................................................................1473\nCASD6185 .............................................................................................................................................................1473\nCASD6186 .............................................................................................................................................................1473\nCASD6187 .............................................................................................................................................................1474\nCASD6188 .............................................................................................................................................................1474\nCASD6189 .............................................................................................................................................................1474\nCASD6226 .............................................................................................................................................................1474\nCASD6227 .............................................................................................................................................................1474\nCASD6228 .............................................................................................................................................................1474\nCASD6229 .............................................................................................................................................................1475\nCASD6230 .............................................................................................................................................................1475\nCASD6231 .............................................................................................................................................................1475\nCASD6232 .............................................................................................................................................................1475\nCASD6233 .............................................................................................................................................................1475\nCASD6234 .............................................................................................................................................................1475\nCASD6235 .............................................................................................................................................................1476\nCASD6236 .............................................................................................................................................................1476\nCASD6237 .............................................................................................................................................................1476\nCASD6238 .............................................................................................................................................................1476\nCASD6239 .............................................................................................................................................................1476\nCASD6241 .............................................................................................................................................................1476\nCASD6242 .............................................................................................................................................................1476\nCASD6243 .............................................................................................................................................................1477\nCASD6244 .............................................................................................................................................................1477\nCASD6245 .............................................................................................................................................................1477\nCASD6246 .............................................................................................................................................................1477\nCASD6247 .............................................................................................................................................................1477\nCASD6250 .............................................................................................................................................................1477\nCASD6251 .............................................................................................................................................................1478", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a297279f4abb-1", "text": "CASD6251 .............................................................................................................................................................1478\nCASD6252 .............................................................................................................................................................1478\nCASD6253 .............................................................................................................................................................1478\nCASD6254 .............................................................................................................................................................1478\nCASD6255 .............................................................................................................................................................1478\nCASD6256 .............................................................................................................................................................1479\n 9", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b7bf66440a9d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6257 .............................................................................................................................................................1479\nCASD6258 .............................................................................................................................................................1479\nCASD6259 .............................................................................................................................................................1479\nCASD6260 .............................................................................................................................................................1480\nCASD6261 .............................................................................................................................................................1480\nCASD6262 .............................................................................................................................................................1480\nCASD6263 .............................................................................................................................................................1480\nCASD6264 .............................................................................................................................................................1480\nCASD6275 .............................................................................................................................................................1481\nCASD6276 .............................................................................................................................................................1481\nCASD6277 .............................................................................................................................................................1481\nCASD6278 .............................................................................................................................................................1481\nCASD6279 .............................................................................................................................................................1481\nCASD6280 .............................................................................................................................................................1482\nCASD6281 .............................................................................................................................................................1482\nCASD6282 .............................................................................................................................................................1482\nCASD6283 .............................................................................................................................................................1482\nCASD6284 .............................................................................................................................................................1482\nCASD6285 .............................................................................................................................................................1482\nCASD6286 .............................................................................................................................................................1482\nCASD6287 .............................................................................................................................................................1483\nCASD6288 .............................................................................................................................................................1483\nCASD6289 .............................................................................................................................................................1483\nCASD6290 .............................................................................................................................................................1483\nCASD6292 .............................................................................................................................................................1483\nCASD6293 .............................................................................................................................................................1483\nCASD6294 .............................................................................................................................................................1484\nCASD6295 .............................................................................................................................................................1484\nCASD6296 .............................................................................................................................................................1484\nCASD6297 .............................................................................................................................................................1484\nCASD6298 .............................................................................................................................................................1484\nCASD6299 .............................................................................................................................................................1484\nCASD6300 .............................................................................................................................................................1485\nCASD6301 .............................................................................................................................................................1485\nCASD63010 ...........................................................................................................................................................1485", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b7bf66440a9d-1", "text": "CASD63010 ...........................................................................................................................................................1485\nCASD6375 .............................................................................................................................................................1485\nCASD6376 .............................................................................................................................................................1485\nCASD6377 .............................................................................................................................................................1485\nCASD6378 .............................................................................................................................................................1486\nCASD6379 .............................................................................................................................................................1486\n 10", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8228344b5746-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6380 .............................................................................................................................................................1486\nCASD6509 .............................................................................................................................................................1486\nCASD6510 .............................................................................................................................................................1486\nCASD6511.............................................................................................................................................................1486\nCASD6512 .............................................................................................................................................................1487\nCASD6550 .............................................................................................................................................................1487\nCASD6551 .............................................................................................................................................................1487\nCASD6552 .............................................................................................................................................................1487\nCASD6607 .............................................................................................................................................................1487\nCASD6608 .............................................................................................................................................................1488\nCASD6609 .............................................................................................................................................................1488\nCASD6801 .............................................................................................................................................................1488\nCASD6802 .............................................................................................................................................................1488\nCASD6803 .............................................................................................................................................................1488\nCASD6804 .............................................................................................................................................................1488\nCASD6805 .............................................................................................................................................................1488\nCASD6806 .............................................................................................................................................................1489\nCASD6807 .............................................................................................................................................................1489\nCASD6808 .............................................................................................................................................................1489\nCASD6809 .............................................................................................................................................................1489\nCASD6810 .............................................................................................................................................................1489\nCASD6811.............................................................................................................................................................1489\nCASD6812 .............................................................................................................................................................1490\nCASD6813 .............................................................................................................................................................1490\nCASD6814 .............................................................................................................................................................1490\nCASD6815 .............................................................................................................................................................1490\nCASD6816 .............................................................................................................................................................1490\nCASD6817 .............................................................................................................................................................1491\nCASD6818 .............................................................................................................................................................1491\nCASD6819 .............................................................................................................................................................1491\nCASD6820 .............................................................................................................................................................1491\nCASD6951 .............................................................................................................................................................1491\nCASD6952 .............................................................................................................................................................1491\nCASD6953 .............................................................................................................................................................1492\nCASD6954 .............................................................................................................................................................1492", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8228344b5746-1", "text": "CASD6954 .............................................................................................................................................................1492\nCASD6955 .............................................................................................................................................................1492\nCASD6956 .............................................................................................................................................................1492\nCASD6957 .............................................................................................................................................................1492\nCASD6958 .............................................................................................................................................................1492\nCASD6959 .............................................................................................................................................................1493\n 11", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "640d46c24f38-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6960 .............................................................................................................................................................1493\nCASD6961 .............................................................................................................................................................1493\nCASD6962 .............................................................................................................................................................1493\nCASD6963 .............................................................................................................................................................1493\nCASD6964 .............................................................................................................................................................1493\nCASD6965 .............................................................................................................................................................1494\nCASD6966 .............................................................................................................................................................1494\nCASD6967 .............................................................................................................................................................1494\nCASD6968 .............................................................................................................................................................1494\nCASD6969 .............................................................................................................................................................1494\nCASD6970 .............................................................................................................................................................1494\nCASD6971 .............................................................................................................................................................1494\nCASD6972 .............................................................................................................................................................1495\nCASD7007 .............................................................................................................................................................1495\nCASD7008 .............................................................................................................................................................1495\nCASD7011.............................................................................................................................................................1495\nCASD7087 .............................................................................................................................................................1495\nCASD7207 .............................................................................................................................................................1496\nCASD7208 .............................................................................................................................................................1496\nCASD7211.............................................................................................................................................................1496\nCASD7301 .............................................................................................................................................................1496\nCASD7302 .............................................................................................................................................................1496\nCASD7303 .............................................................................................................................................................1496\nCASD7304 .............................................................................................................................................................1496\nCASD7305 .............................................................................................................................................................1497\nCASD7306 .............................................................................................................................................................1497\nCASD7308 .............................................................................................................................................................1497\nCASD7309 .............................................................................................................................................................1497\nCASD7400 .............................................................................................................................................................1497\nCASD7401 .............................................................................................................................................................1497\nCASD7402 .............................................................................................................................................................1498\nCASD7403 .............................................................................................................................................................1498\nCASD7404 .............................................................................................................................................................1498\nCASD7405 .............................................................................................................................................................1498\nCASD7406 .............................................................................................................................................................1498", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "640d46c24f38-1", "text": "CASD7406 .............................................................................................................................................................1498\nCASD7407 .............................................................................................................................................................1498\nCASD7409 .............................................................................................................................................................1499\nCASD7410 .............................................................................................................................................................1499\nCASD7411.............................................................................................................................................................1499\nCASD7412 .............................................................................................................................................................1499\n 12", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b4b3f95b9733-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD7413 .............................................................................................................................................................1499\nCASD7414 .............................................................................................................................................................1499\nCASD7415 .............................................................................................................................................................1500\nCASD7417 .............................................................................................................................................................1500\nCASD7418 .............................................................................................................................................................1500\nCASD7419 .............................................................................................................................................................1500\nCASD7420 .............................................................................................................................................................1500\nCASD7500 .............................................................................................................................................................1500\nCASD7501 .............................................................................................................................................................1501\nCASD7502 .............................................................................................................................................................1501\nCASD7503 .............................................................................................................................................................1501\nCASD7504 .............................................................................................................................................................1501\nCASD7505 .............................................................................................................................................................1501\nCASD7506 .............................................................................................................................................................1501\nSymDump  for CICS Messages ..................................................................................................................................1502\nCASD5351 .............................................................................................................................................................1502\nCASD5352 .............................................................................................................................................................1502\nCASD60490 ...........................................................................................................................................................1502\nCASD60500 ...........................................................................................................................................................1502\nCASD6051 .............................................................................................................................................................1503\nCASD6052 .............................................................................................................................................................1503\nCASD6053 .............................................................................................................................................................1503\nCASD6054 .............................................................................................................................................................1503\nCASD6055 .............................................................................................................................................................1503\nCASD6056 .............................................................................................................................................................1503\nCASD6057 .............................................................................................................................................................1503\nCASD6060 .............................................................................................................................................................1504\nCASD6061 .............................................................................................................................................................1504\nCASD6062 .............................................................................................................................................................1504\nCASD6063 .............................................................................................................................................................1504\nCASD6064 .............................................................................................................................................................1504\nCASD6065 .............................................................................................................................................................1504\nCASD6066 .............................................................................................................................................................1505\nCASD6067 .............................................................................................................................................................1505\nCASD6068 .............................................................................................................................................................1505", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b4b3f95b9733-1", "text": "CASD6068 .............................................................................................................................................................1505\nCASD60690 ...........................................................................................................................................................1505\nCASD60700 ...........................................................................................................................................................1505\nCASD60710 ...........................................................................................................................................................1505\nCASD60720 ...........................................................................................................................................................1506\nCASD60730 ...........................................................................................................................................................1506\n 13", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7b3f447be9dc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD60740 ...........................................................................................................................................................1506\nCASD60770 ...........................................................................................................................................................1506\nCASD60780 ...........................................................................................................................................................1506\nCASD60790 ...........................................................................................................................................................1507\nCASD6107 .............................................................................................................................................................1507\nCASD6120 .............................................................................................................................................................1507\nCASD6291 .............................................................................................................................................................1507\nCASD6303 .............................................................................................................................................................1507\nCASD6401 .............................................................................................................................................................1507\nCASD6403 .............................................................................................................................................................1508\nCASD6404 .............................................................................................................................................................1508\nCASD6405 .............................................................................................................................................................1508\nCASD65090 ...........................................................................................................................................................1508\nCASD6701 .............................................................................................................................................................1510\nCASD6702 .............................................................................................................................................................1510\nCASD6703 .............................................................................................................................................................1510\nCASD6704 .............................................................................................................................................................1510\nCASD6705 .............................................................................................................................................................1511\nCASD6706 .............................................................................................................................................................1511\nCASD6707 .............................................................................................................................................................1511\nCASD6708 .............................................................................................................................................................1511\nCASD6709 .............................................................................................................................................................1511\nCASD6710 .............................................................................................................................................................1511\nCASD6711.............................................................................................................................................................1512\nCASD6712 .............................................................................................................................................................1512\nCASD6713 .............................................................................................................................................................1512\nCASD6714 .............................................................................................................................................................1512\nCASD6715 .............................................................................................................................................................1512\nCASD6716 .............................................................................................................................................................1512\nCASD6717 .............................................................................................................................................................1513\nCASD6718 .............................................................................................................................................................1513\nCASD6719 .............................................................................................................................................................1513\nCASD6720 .............................................................................................................................................................1513\nCASD6721 .............................................................................................................................................................1513\nCASD6722 .............................................................................................................................................................1513", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7b3f447be9dc-1", "text": "CASD6722 .............................................................................................................................................................1513\nCASD6723 .............................................................................................................................................................1514\nCASD6724 .............................................................................................................................................................1514\nCASD6974 .............................................................................................................................................................1514\nCASD7126 .............................................................................................................................................................1514\nCASD7127 .............................................................................................................................................................1514\n 14", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2ea681e8be7d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD7128 .............................................................................................................................................................1514\nCASD7129 .............................................................................................................................................................1514\nCASD7130 .............................................................................................................................................................1515\nCASD7131 .............................................................................................................................................................1515\nCASD7132 .............................................................................................................................................................1515\nCASD7133 .............................................................................................................................................................1515\nCASD7134 .............................................................................................................................................................1515\nCASD7135 .............................................................................................................................................................1515\nCASD7136 .............................................................................................................................................................1516\nCASD7137 .............................................................................................................................................................1516\nCASD7138 .............................................................................................................................................................1516\nCASD7139 .............................................................................................................................................................1516\nCASD7140 .............................................................................................................................................................1516\nCASD7141 .............................................................................................................................................................1516\nCASD7142 .............................................................................................................................................................1516\nCASD7145 .............................................................................................................................................................1517\nCASD7146 .............................................................................................................................................................1517\nCASD7150 .............................................................................................................................................................1517\nCASD7300 .............................................................................................................................................................1517\nCASD73010 ...........................................................................................................................................................1517\nCASD73020 ...........................................................................................................................................................1517\nCASD73050 ...........................................................................................................................................................1518\nCASD73060 ...........................................................................................................................................................1518\nCASD7307 .............................................................................................................................................................1518\nCASD73080 ...........................................................................................................................................................1518\nCASD73090 ...........................................................................................................................................................1518\nCASD7310 .............................................................................................................................................................1518\nCASD7311.............................................................................................................................................................1519\nCASD7312 .............................................................................................................................................................1519\nCASD7315 .............................................................................................................................................................1519\nCASD7321 .............................................................................................................................................................1519\nCASD7322 .............................................................................................................................................................1519\nCASD7323 .............................................................................................................................................................1519\nCASD7324 .............................................................................................................................................................1520\nCASD7325 .............................................................................................................................................................1520", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2ea681e8be7d-1", "text": "CASD7325 .............................................................................................................................................................1520\nCASD7330 .............................................................................................................................................................1520\nCASD7335 .............................................................................................................................................................1520\nCASD7340 .............................................................................................................................................................1520\nCASD7341 .............................................................................................................................................................1520\nCASD7342 .............................................................................................................................................................1521\n 15", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c9f9059376f4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD7350 .............................................................................................................................................................1521\nCASD7351 .............................................................................................................................................................1521\nCASD7352 .............................................................................................................................................................1521\nCASD7353 .............................................................................................................................................................1521\nCASD7354 .............................................................................................................................................................1521\nCASD7507 .............................................................................................................................................................1521\nCASD8981 .............................................................................................................................................................1522\nCASD7431 .............................................................................................................................................................1522\nCASD7432 .............................................................................................................................................................1522\nCASD7433 .............................................................................................................................................................1522\nCASD7434 .............................................................................................................................................................1522\nCASD7435 .............................................................................................................................................................1522\nCASD7436 .............................................................................................................................................................1523\nCASD7437 .............................................................................................................................................................1523\nCASD7438 .............................................................................................................................................................1523\nCASD7439 .............................................................................................................................................................1523\nInterTest for CICS Online Help Messages ...............................................................................................................1523\nCAIN0001 ..............................................................................................................................................................1523\nCAIN0002 ..............................................................................................................................................................1523\nCAIN0003 ..............................................................................................................................................................1524\nCAIN0004 ..............................................................................................................................................................1524\nCAIN0005 ..............................................................................................................................................................1524\nCAIN0006 ..............................................................................................................................................................1524\nCAIN0007 ..............................................................................................................................................................1524\nCAIN0008 ..............................................................................................................................................................1524\nCAIN0009 ..............................................................................................................................................................1525\nCAIN0010 ..............................................................................................................................................................1525\nCAIN0011..............................................................................................................................................................1525\nCAIN0201 ..............................................................................................................................................................1525\nCAIN0202 ..............................................................................................................................................................1525\nCAIN0203 ..............................................................................................................................................................1525\nCAIN0204 ..............................................................................................................................................................1526\nCAIN0205 ..............................................................................................................................................................1526\nCAIN0206 ..............................................................................................................................................................1526\nCAIN0207 ..............................................................................................................................................................1526", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c9f9059376f4-1", "text": "CAIN0207 ..............................................................................................................................................................1526\nCAIN0208 ..............................................................................................................................................................1526\nCAIN0209 ..............................................................................................................................................................1526\nCAIN0210 ..............................................................................................................................................................1527\nCAIN0211..............................................................................................................................................................1527\nCAIN0212 ..............................................................................................................................................................1527\n 16", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "03498e7069b1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0213 ..............................................................................................................................................................1527\nCAIN0214 ..............................................................................................................................................................1527\nCAIN0215 ..............................................................................................................................................................1527\nCAIN0216 ..............................................................................................................................................................1528\nCAIN0217 ..............................................................................................................................................................1528\nCAIN0218 ..............................................................................................................................................................1528\nCAIN0219 ..............................................................................................................................................................1528\nCAIN0220 ..............................................................................................................................................................1528\nCAIN0221 ..............................................................................................................................................................1528\nCAIN0222 ..............................................................................................................................................................1529\nCAIN0401 ..............................................................................................................................................................1529\nCAIN0402 ..............................................................................................................................................................1529\nCAIN0403 ..............................................................................................................................................................1529\nCAIN0404 ..............................................................................................................................................................1529\nCAIN0405 ..............................................................................................................................................................1529\nCAIN0406 ..............................................................................................................................................................1530\nCAIN0407 ..............................................................................................................................................................1530\nCAIN0408 ..............................................................................................................................................................1530\nCAIN0409 ..............................................................................................................................................................1530\nCAIN0410 ..............................................................................................................................................................1530\nCAIN0411..............................................................................................................................................................1530\nCAIN0412 ..............................................................................................................................................................1530\nCAIN0413 ..............................................................................................................................................................1531\nCAIN0414 ..............................................................................................................................................................1531\nCAIN0415 ..............................................................................................................................................................1531\nCAIN0416 ..............................................................................................................................................................1531\nCAIN0417 ..............................................................................................................................................................1531\nCAIN0418 ..............................................................................................................................................................1531\nCAIN0419 ..............................................................................................................................................................1532\nCAIN0420 ..............................................................................................................................................................1532\nCAIN0421 ..............................................................................................................................................................1532\nCAIN0422 ..............................................................................................................................................................1532\nCAIN0423 ..............................................................................................................................................................1532\nCAIN0425 ..............................................................................................................................................................1532\nCAIN0426 ..............................................................................................................................................................1533", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "03498e7069b1-1", "text": "CAIN0426 ..............................................................................................................................................................1533\nCAIN0427 ..............................................................................................................................................................1533\nCAIN0428 ..............................................................................................................................................................1533\nCAIN0429 ..............................................................................................................................................................1533\nCAIN0430 ..............................................................................................................................................................1533\nCAIN0431 ..............................................................................................................................................................1533\n 17", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "93b1b1a2a76e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0432 ..............................................................................................................................................................1533\nCAIN0433 ..............................................................................................................................................................1534\nCAIN0434 ..............................................................................................................................................................1534\nCAIN0435 ..............................................................................................................................................................1534\nCAIN0436 ..............................................................................................................................................................1534\nCAIN0437 ..............................................................................................................................................................1534\nCAIN0438 ..............................................................................................................................................................1534\nCAIN0439 ..............................................................................................................................................................1535\nCAIN0440 ..............................................................................................................................................................1535\nCAIN0441 ..............................................................................................................................................................1535\nCAIN0442 ..............................................................................................................................................................1535\nCAIN0443 ..............................................................................................................................................................1535\nCAIN0444 ..............................................................................................................................................................1535\nCAIN0445 ..............................................................................................................................................................1536\nCAIN0446 ..............................................................................................................................................................1536\nCAIN0447 ..............................................................................................................................................................1536\nCAIN0448 ..............................................................................................................................................................1536\nCAIN0449 ..............................................................................................................................................................1536\nCAIN0450 ..............................................................................................................................................................1536\nCAIN0451 ..............................................................................................................................................................1537\nCAIN0452 ..............................................................................................................................................................1537\nCAIN0453 ..............................................................................................................................................................1537\nCAIN0454 ..............................................................................................................................................................1537\nCAIN0455 ..............................................................................................................................................................1537\nCAIN0456 ..............................................................................................................................................................1537\nCAIN0457 ..............................................................................................................................................................1537\nCAIN0458 ..............................................................................................................................................................1538\nCAIN0459 ..............................................................................................................................................................1538\nCAIN0460 ..............................................................................................................................................................1538\nCAIN0461 ..............................................................................................................................................................1538\nCAIN0462 ..............................................................................................................................................................1538\nCAIN0463 ..............................................................................................................................................................1538\nCAIN0464 ..............................................................................................................................................................1539\nCAIN0465 ..............................................................................................................................................................1539\nCAIN0466 ..............................................................................................................................................................1539", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "93b1b1a2a76e-1", "text": "CAIN0466 ..............................................................................................................................................................1539\nCAIN0467 ..............................................................................................................................................................1539\nCAIN0468 ..............................................................................................................................................................1539\nCAIN0469 ..............................................................................................................................................................1539\nCAIN0470 ..............................................................................................................................................................1540\nCAIN0471 ..............................................................................................................................................................1540\n 18", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4a412c1c6e9e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0472 ..............................................................................................................................................................1540\nCAIN0473 ..............................................................................................................................................................1540\nCAIN0474 ..............................................................................................................................................................1540\nCAIN0475 ..............................................................................................................................................................1540\nCAIN0476 ..............................................................................................................................................................1540\nCAIN0478 ..............................................................................................................................................................1541\nCAIN0479 ..............................................................................................................................................................1541\nCAIN0480 ..............................................................................................................................................................1541\nCAIN0481 ..............................................................................................................................................................1541\nCAIN0482 ..............................................................................................................................................................1541\nCAIN0483 ..............................................................................................................................................................1541\nCAIN0484 ..............................................................................................................................................................1542\nCAIN0485 ..............................................................................................................................................................1542\nCAIN0486 ..............................................................................................................................................................1542\nCAIN0487 ..............................................................................................................................................................1542\nCAIN0489 ..............................................................................................................................................................1542\nCAIN0490 ..............................................................................................................................................................1542\nCAIN0491 ..............................................................................................................................................................1543\nCAIN0492 ..............................................................................................................................................................1543\nCAIN0499 ..............................................................................................................................................................1543\nCAIN0601 ..............................................................................................................................................................1543\nCAIN0603 ..............................................................................................................................................................1543\nCAIN0604 ..............................................................................................................................................................1543\nCAIN0605 ..............................................................................................................................................................1544\nCAIN0606 ..............................................................................................................................................................1544\nCAIN0607 ..............................................................................................................................................................1544\nCAIN0608 ..............................................................................................................................................................1544\nCAIN0609 ..............................................................................................................................................................1544\nCAIN0610 ..............................................................................................................................................................1544\nCAIN0611..............................................................................................................................................................1545\nCAIN0612 ..............................................................................................................................................................1545\nCAIN0613 ..............................................................................................................................................................1545\nCAIN0614 ..............................................................................................................................................................1545\nCAIN0615 ..............................................................................................................................................................1545\nCAIN0616 ..............................................................................................................................................................1546", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4a412c1c6e9e-1", "text": "CAIN0616 ..............................................................................................................................................................1546\nCAIN0617 ..............................................................................................................................................................1546\nCAIN0618 ..............................................................................................................................................................1546\nCAIN0619 ..............................................................................................................................................................1546\nCAIN0620 ..............................................................................................................................................................1546\nCAIN0621 ..............................................................................................................................................................1546\n 19", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2e7344a966b7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0622 ..............................................................................................................................................................1547\nCAIN0623 ..............................................................................................................................................................1547\nCAIN0624 ..............................................................................................................................................................1547\nCAIN0625 ..............................................................................................................................................................1547\nCAIN0626 ..............................................................................................................................................................1547\nCAIN0627 ..............................................................................................................................................................1547\nCAIN0628 ..............................................................................................................................................................1548\nCAIN0629 ..............................................................................................................................................................1548\nCAIN0630 ..............................................................................................................................................................1548\nCAIN0631 ..............................................................................................................................................................1548\nCAIN0632 ..............................................................................................................................................................1548\nCAIN0633 ..............................................................................................................................................................1548\nCAIN0634 ..............................................................................................................................................................1549\nCAIN0635 ..............................................................................................................................................................1549\nCAIN0636 ..............................................................................................................................................................1549\nCAIN0637 ..............................................................................................................................................................1549\nCAIN0638 ..............................................................................................................................................................1549\nCAIN0639 ..............................................................................................................................................................1550\nCAIN0640 ..............................................................................................................................................................1550\nCAIN0641 ..............................................................................................................................................................1550\nCAIN0642 ..............................................................................................................................................................1550\nCAIN0651 ..............................................................................................................................................................1550\nCAIN0652 ..............................................................................................................................................................1550\nCAIN0653 ..............................................................................................................................................................1551\nCAIN0654 ..............................................................................................................................................................1551\nCAIN0655 ..............................................................................................................................................................1551\nCAIN0661 ..............................................................................................................................................................1551\nCAIN0662 ..............................................................................................................................................................1551\nCAIN0663 ..............................................................................................................................................................1551\nCAIN0665 ..............................................................................................................................................................1551\nCAIN0666 ..............................................................................................................................................................1552\nCAIN0667 ..............................................................................................................................................................1552\nCAIN0668 ..............................................................................................................................................................1552\nCAIN0671 ..............................................................................................................................................................1552\nCAIN0672 ..............................................................................................................................................................1552", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2e7344a966b7-1", "text": "CAIN0672 ..............................................................................................................................................................1552\nCAIN0673 ..............................................................................................................................................................1552\nCAIN0674 ..............................................................................................................................................................1553\nCAIN0675 ..............................................................................................................................................................1553\nCAIN0676 ..............................................................................................................................................................1553\nCAIN0677 ..............................................................................................................................................................1553\n 20", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "42415fa49feb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0678 ..............................................................................................................................................................1553\nCAIN0679 ..............................................................................................................................................................1553\nCAIN0680 ..............................................................................................................................................................1554\nCAIN0681 ..............................................................................................................................................................1554\nCAIN0682 ..............................................................................................................................................................1554\nCAIN0683 ..............................................................................................................................................................1554\nCAIN0684 ..............................................................................................................................................................1554\nCAIN0685 ..............................................................................................................................................................1554\nCAIN0686 ..............................................................................................................................................................1554\nCAIN0687 ..............................................................................................................................................................1555\nCAIN0688 ..............................................................................................................................................................1555\nCAIN0689 ..............................................................................................................................................................1555\nCAIN0690 ..............................................................................................................................................................1555\nCAIN0691 ..............................................................................................................................................................1555\nCAIN0692 ..............................................................................................................................................................1555\nCAIN0693 ..............................................................................................................................................................1556\nCAIN0694 ..............................................................................................................................................................1556\nCAIN0695 ..............................................................................................................................................................1556\nCAIN0696 ..............................................................................................................................................................1556\nCAIN0697 ..............................................................................................................................................................1556\nCAIN0698 ..............................................................................................................................................................1556\nCAIN0699 ..............................................................................................................................................................1557\nCAIN0700 ..............................................................................................................................................................1557\nCAIN0701 ..............................................................................................................................................................1557\nCAIN0702 ..............................................................................................................................................................1557\nCAIN0703 ..............................................................................................................................................................1557\nCAIN0709 ..............................................................................................................................................................1557\nCAIN0711..............................................................................................................................................................1558\nCAIN0712 ..............................................................................................................................................................1558\nCAIN0713 ..............................................................................................................................................................1558\nCAIN0714 ..............................................................................................................................................................1558\nCAIN0715 ..............................................................................................................................................................1558\nCAIN0716 ..............................................................................................................................................................1558\nCAIN0717 ..............................................................................................................................................................1558\nCAIN0719 ..............................................................................................................................................................1559", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "42415fa49feb-1", "text": "CAIN0719 ..............................................................................................................................................................1559\nCAIN0720 ..............................................................................................................................................................1559\nCAIN0726 ..............................................................................................................................................................1559\nCAIN0728 ..............................................................................................................................................................1559\nCAIN0731 ..............................................................................................................................................................1559\nCAIN0732 ..............................................................................................................................................................1559\n 21", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ef464e92ae34-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0733 ..............................................................................................................................................................1560\nCAIN0734 ..............................................................................................................................................................1560\nCAIN0735 ..............................................................................................................................................................1560\nCAIN0736 ..............................................................................................................................................................1560\nCAIN0737 ..............................................................................................................................................................1560\nCAIN0738 ..............................................................................................................................................................1560\nCAIN0739 ..............................................................................................................................................................1561\nCAIN0740 ..............................................................................................................................................................1561\nCAIN0741 ..............................................................................................................................................................1561\nCAIN0742 ..............................................................................................................................................................1561\nCAIN0750 ..............................................................................................................................................................1561\nCAIN0751 ..............................................................................................................................................................1561\nCAIN0752 ..............................................................................................................................................................1562\nCAIN0753 ..............................................................................................................................................................1562\nCAIN0754 ..............................................................................................................................................................1562\nCAIN0755 ..............................................................................................................................................................1562\nCAIN0756 ..............................................................................................................................................................1562\nCAIN0757 ..............................................................................................................................................................1562\nCAIN0758 ..............................................................................................................................................................1562\nCAIN0759 ..............................................................................................................................................................1563\nCAIN0760 ..............................................................................................................................................................1563\nCAIN0761 ..............................................................................................................................................................1563\nCAIN0762 ..............................................................................................................................................................1563\nCAIN0763 ..............................................................................................................................................................1563\nCAIN0764 ..............................................................................................................................................................1563\nCAIN0765 ..............................................................................................................................................................1564\nCAIN0766 ..............................................................................................................................................................1564\nCAIN0767 ..............................................................................................................................................................1564\nCAIN0768 ..............................................................................................................................................................1564\nCAIN0769 ..............................................................................................................................................................1564\nCAIN0770 ..............................................................................................................................................................1564\nCAIN0771 ..............................................................................................................................................................1564\nCAIN0780 ..............................................................................................................................................................1565\nCAIN0781 ..............................................................................................................................................................1565\nCAIN0782 ..............................................................................................................................................................1565", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ef464e92ae34-1", "text": "CAIN0782 ..............................................................................................................................................................1565\nCAIN0783 ..............................................................................................................................................................1565\nCAIN0784 ..............................................................................................................................................................1565\nCAIN0785 ..............................................................................................................................................................1565\nCAIN0786 ..............................................................................................................................................................1566\nCAIN0787 ..............................................................................................................................................................1566\n 22", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "03ad03121e38-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0788 ..............................................................................................................................................................1566\nCAIN0789 ..............................................................................................................................................................1566\nCAIN0790 ..............................................................................................................................................................1566\nCAIN0791 ..............................................................................................................................................................1566\nCAIN0792 ..............................................................................................................................................................1567\nCAIN0793 ..............................................................................................................................................................1567\nCAIN0794 ..............................................................................................................................................................1567\nCAIN0795 ..............................................................................................................................................................1567\nCAIN0796 ..............................................................................................................................................................1567\nCAIN0797 ..............................................................................................................................................................1567\nCAIN0798 ..............................................................................................................................................................1567\nCAIN0799 ..............................................................................................................................................................1568\nCAIN0800 ..............................................................................................................................................................1568\nCAIN0801 ..............................................................................................................................................................1568\nCAIN0802 ..............................................................................................................................................................1568\nCAIN0803 ..............................................................................................................................................................1568\nCAIN0804 ..............................................................................................................................................................1568\nCAIN0805 ..............................................................................................................................................................1569\nCAIN0806 ..............................................................................................................................................................1569\nCAIN1001 ..............................................................................................................................................................1569\nCAIN1002 ..............................................................................................................................................................1569\nCAIN1004 ..............................................................................................................................................................1569\nCAIN1010 ..............................................................................................................................................................1569\nCAIN1019 ..............................................................................................................................................................1569\nCAIN1020 ..............................................................................................................................................................1570\nCAIN1021 ..............................................................................................................................................................1570\nCAIN1022 ..............................................................................................................................................................1570\nCAIN1041 ..............................................................................................................................................................1570\nCAIN1042 ..............................................................................................................................................................1570\nCAIN1043 ..............................................................................................................................................................1570\nCAIN1044 ..............................................................................................................................................................1571\nCAIN1045 ..............................................................................................................................................................1571\nCAIN1055 ..............................................................................................................................................................1571\nCAIN1064 ..............................................................................................................................................................1571\nCAIN1066 ..............................................................................................................................................................1571", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "03ad03121e38-1", "text": "CAIN1066 ..............................................................................................................................................................1571\nCAIN1106..............................................................................................................................................................1571\nCAIN1150..............................................................................................................................................................1572\nCAIN1170..............................................................................................................................................................1572\nCAIN1174..............................................................................................................................................................1572\nCAIN1177..............................................................................................................................................................1572\n 23", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4ed66035f647-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN1179..............................................................................................................................................................1572\nCAIN1180..............................................................................................................................................................1572\nCAIN1181..............................................................................................................................................................1573\nCAIN1182..............................................................................................................................................................1573\nCAIN1185..............................................................................................................................................................1573\nCAIN1186..............................................................................................................................................................1573\nCAIN1187..............................................................................................................................................................1573\nCAIN1188..............................................................................................................................................................1573\nCAIN1189..............................................................................................................................................................1574\nCAIN1191..............................................................................................................................................................1574\nCAIN1192..............................................................................................................................................................1574\nCAIN1193..............................................................................................................................................................1574\nCAIN11930............................................................................................................................................................1574\nCAIN1194..............................................................................................................................................................1574\nCAIN1197..............................................................................................................................................................1575\nCAIN1250 ..............................................................................................................................................................1575\nCAIN1252 ..............................................................................................................................................................1575\nCAIN1255 ..............................................................................................................................................................1575\nCAIN1256 ..............................................................................................................................................................1575\nCAIN1257 ..............................................................................................................................................................1575\nCAIN1258 ..............................................................................................................................................................1576\nCAIN1259 ..............................................................................................................................................................1576\nCAIN1260 ..............................................................................................................................................................1576\nCAIN1261 ..............................................................................................................................................................1576\nCAIN1262 ..............................................................................................................................................................1576\nCAIN1263 ..............................................................................................................................................................1576\nCAIN1264 ..............................................................................................................................................................1577\nCAIN1265 ..............................................................................................................................................................1577\nCAIN1266 ..............................................................................................................................................................1577\nCAIN1267 ..............................................................................................................................................................1577\nCAIN1268 ..............................................................................................................................................................1577\nCAIN1269 ..............................................................................................................................................................1577\nCAIN1270 ..............................................................................................................................................................1578\nCAIN1271 ..............................................................................................................................................................1578\nCAIN1272 ..............................................................................................................................................................1578", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4ed66035f647-1", "text": "CAIN1272 ..............................................................................................................................................................1578\nCAIN1273 ..............................................................................................................................................................1578\nCAIN1274 ..............................................................................................................................................................1578\nCAIN1275 ..............................................................................................................................................................1578\nCAIN1276 ..............................................................................................................................................................1578\nCAIN1277 ..............................................................................................................................................................1579\n 24", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fb0ede1fcd63-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN1343 ..............................................................................................................................................................1579\nCAIN1344 ..............................................................................................................................................................1579\nCAIN1345 ..............................................................................................................................................................1579\nCAIN1346 ..............................................................................................................................................................1579\nCAIN1347 ..............................................................................................................................................................1579\nCAIN1348 ..............................................................................................................................................................1580\nCAIN1349 ..............................................................................................................................................................1580\nCAIN1350 ..............................................................................................................................................................1580\nCAIN1351 ..............................................................................................................................................................1580\nCAIN1358 ..............................................................................................................................................................1580\nCAIN1701 ..............................................................................................................................................................1580\nCAIN1702 ..............................................................................................................................................................1580\nCAIN1703 ..............................................................................................................................................................1581\nCAIN1704 ..............................................................................................................................................................1581\nCAIN1705 ..............................................................................................................................................................1581\nCAIN1706 ..............................................................................................................................................................1581\nCAIN1707 ..............................................................................................................................................................1581\nCAIN1708 ..............................................................................................................................................................1581\nCAIN1709 ..............................................................................................................................................................1582\nCAIN1710 ..............................................................................................................................................................1582\nCAIN1711..............................................................................................................................................................1582\nCAIN1712 ..............................................................................................................................................................1582\nCAIN1714 ..............................................................................................................................................................1582\nCAIN1713 ..............................................................................................................................................................1582\nCAIN1715 ..............................................................................................................................................................1582\nCAIN1716 ..............................................................................................................................................................1583\nCAIN1717 ..............................................................................................................................................................1583\nCAIN1718 ..............................................................................................................................................................1583\nCAIN1719 ..............................................................................................................................................................1583\nCAIN1720 ..............................................................................................................................................................1583\nCAIN1901 ..............................................................................................................................................................1583\nCAIN1902 ..............................................................................................................................................................1584\nCAIN1903 ..............................................................................................................................................................1584\nCAIN1904 ..............................................................................................................................................................1584\nCAIN1905 ..............................................................................................................................................................1584", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fb0ede1fcd63-1", "text": "CAIN1905 ..............................................................................................................................................................1584\nCAIN1906 ..............................................................................................................................................................1584\nCAIN1908 ..............................................................................................................................................................1584\nCAIN1909 ..............................................................................................................................................................1584\nCAIN1910 ..............................................................................................................................................................1585\nCAIN1911..............................................................................................................................................................1585\n 25", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "673a80026f7b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN1912 ..............................................................................................................................................................1585\nCAIN1913 ..............................................................................................................................................................1585\nCAIN2301 ..............................................................................................................................................................1585\nCAIN2302 ..............................................................................................................................................................1585\nCAIN2303 ..............................................................................................................................................................1586\nCAIN2304 ..............................................................................................................................................................1586\nCAIN2305 ..............................................................................................................................................................1586\nCAIN2306 ..............................................................................................................................................................1586\nCAIN2307 ..............................................................................................................................................................1586\nCAIN2308 ..............................................................................................................................................................1586\nCAIN2309 ..............................................................................................................................................................1587\nCAIN2310 ..............................................................................................................................................................1587\nCAIN2311..............................................................................................................................................................1587\nCAIN2312 ..............................................................................................................................................................1587\nCAIN2313 ..............................................................................................................................................................1587\nCAIN2314 ..............................................................................................................................................................1587\nCAIN2315 ..............................................................................................................................................................1587\nCAIN2316 ..............................................................................................................................................................1588\nCAIN2317 ..............................................................................................................................................................1588\nCAIN2318 ..............................................................................................................................................................1588\nCAIN2319 ..............................................................................................................................................................1588\nCAIN2320 ..............................................................................................................................................................1588\nCAIN2321 ..............................................................................................................................................................1588\nCAIN2322 ..............................................................................................................................................................1589\nCAIN2323 ..............................................................................................................................................................1589\nCAIN2324 ..............................................................................................................................................................1589\nCAIN2325 ..............................................................................................................................................................1589\nCAIN2326 ..............................................................................................................................................................1589\nCAIN2327 ..............................................................................................................................................................1589\nCAIN2328 ..............................................................................................................................................................1590\nCAIN2329 ..............................................................................................................................................................1590\nCAIN2330 ..............................................................................................................................................................1590\nCAIN2331 ..............................................................................................................................................................1590\nCAIN2332 ..............................................................................................................................................................1590\nCAIN2333 ..............................................................................................................................................................1590", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "673a80026f7b-1", "text": "CAIN2333 ..............................................................................................................................................................1590\nCAIN2334 ..............................................................................................................................................................1591\nCAIN2335 ..............................................................................................................................................................1591\nCAIN2336 ..............................................................................................................................................................1591\nCAIN2337 ..............................................................................................................................................................1591\nCAIN2338 ..............................................................................................................................................................1591\n 26", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "40513855bfbe-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2339 ..............................................................................................................................................................1591\nCAIN2340 ..............................................................................................................................................................1591\nCAIN2341 ..............................................................................................................................................................1592\nCAIN2342 ..............................................................................................................................................................1592\nCAIN2343 ..............................................................................................................................................................1592\nCAIN2344 ..............................................................................................................................................................1592\nCAIN2345 ..............................................................................................................................................................1592\nCAIN2346 ..............................................................................................................................................................1592\nCAIN2347 ..............................................................................................................................................................1593\nCAIN2348 ..............................................................................................................................................................1593\nCAIN2349 ..............................................................................................................................................................1593\nCAIN2350 ..............................................................................................................................................................1593\nCAIN2351 ..............................................................................................................................................................1593\nCAIN2352 ..............................................................................................................................................................1593\nCAIN2353 ..............................................................................................................................................................1593\nCAIN2354 ..............................................................................................................................................................1594\nCAIN2355 ..............................................................................................................................................................1594\nCAIN2356 ..............................................................................................................................................................1594\nCAIN2357 ..............................................................................................................................................................1594\nCAIN2358 ..............................................................................................................................................................1594\nCAIN2359 ..............................................................................................................................................................1594\nCAIN2360 ..............................................................................................................................................................1595\nCAIN2361 ..............................................................................................................................................................1595\nCAIN2362 ..............................................................................................................................................................1595\nCAIN2363 ..............................................................................................................................................................1595\nCAIN2364 ..............................................................................................................................................................1595\nCAIN2365 ..............................................................................................................................................................1595\nCAIN2366 ..............................................................................................................................................................1595\nCAIN2367 ..............................................................................................................................................................1596\nCAIN2368 ..............................................................................................................................................................1596\nCAIN2369 ..............................................................................................................................................................1596\nCAIN2370 ..............................................................................................................................................................1596\nCAIN2371 ..............................................................................................................................................................1596\nCAIN2372 ..............................................................................................................................................................1596\nCAIN2373 ..............................................................................................................................................................1597", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "40513855bfbe-1", "text": "CAIN2373 ..............................................................................................................................................................1597\nCAIN2374 ..............................................................................................................................................................1597\nCAIN2375 ..............................................................................................................................................................1597\nCAIN2376 ..............................................................................................................................................................1597\nCAIN2377 ..............................................................................................................................................................1597\nCAIN2378 ..............................................................................................................................................................1597\n 27", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "48a09b09daff-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2379 ..............................................................................................................................................................1597\nCAIN2380 ..............................................................................................................................................................1598\nCAIN2381 ..............................................................................................................................................................1598\nCAIN2390 ..............................................................................................................................................................1598\nCAIN2391 ..............................................................................................................................................................1598\nCAIN2392 ..............................................................................................................................................................1598\nCAIN2393 ..............................................................................................................................................................1598\nCAIN2394 ..............................................................................................................................................................1599\nCAIN2501 ..............................................................................................................................................................1599\nCAIN2502 ..............................................................................................................................................................1599\nCAIN2503 ..............................................................................................................................................................1599\nCAIN2504 ..............................................................................................................................................................1599\nCAIN2505 ..............................................................................................................................................................1599\nCAIN2506 ..............................................................................................................................................................1600\nCAIN2507 ..............................................................................................................................................................1600\nCAIN2508 ..............................................................................................................................................................1600\nCAIN2509 ..............................................................................................................................................................1600\nCAIN2510 ..............................................................................................................................................................1600\nCAIN2511..............................................................................................................................................................1600\nCAIN2512 ..............................................................................................................................................................1601\nCAIN2513 ..............................................................................................................................................................1601\nCAIN2514 ..............................................................................................................................................................1601\nCAIN2515 ..............................................................................................................................................................1601\nCAIN2516 ..............................................................................................................................................................1601\nCAIN2517 ..............................................................................................................................................................1601\nCAIN2518 ..............................................................................................................................................................1601\nCAIN2519 ..............................................................................................................................................................1602\nCAIN2520 ..............................................................................................................................................................1602\nCAIN2521 ..............................................................................................................................................................1602\nCAIN2522 ..............................................................................................................................................................1602\nCAIN2523 ..............................................................................................................................................................1602\nCAIN2524 ..............................................................................................................................................................1602\nCAIN2525 ..............................................................................................................................................................1603\nCAIN2526 ..............................................................................................................................................................1603\nCAIN2527 ..............................................................................................................................................................1603", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "48a09b09daff-1", "text": "CAIN2527 ..............................................................................................................................................................1603\nCAIN2528 ..............................................................................................................................................................1603\nCAIN2529 ..............................................................................................................................................................1603\nCAIN2530 ..............................................................................................................................................................1603\nCAIN2531 ..............................................................................................................................................................1604\nCAIN2601 ..............................................................................................................................................................1604\n 28", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "39d95e93ef60-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2602 ..............................................................................................................................................................1604\nCAIN2603 ..............................................................................................................................................................1604\nCAIN2604 ..............................................................................................................................................................1604\nCAIN2605 ..............................................................................................................................................................1604\nCAIN2606 ..............................................................................................................................................................1604\nCAIN2607 ..............................................................................................................................................................1605\nCAIN2608 ..............................................................................................................................................................1605\nCAIN2609 ..............................................................................................................................................................1605\nCAIN2610 ..............................................................................................................................................................1605\nCAIN2611..............................................................................................................................................................1605\nCAIN2612 ..............................................................................................................................................................1605\nCAIN2613 ..............................................................................................................................................................1606\nCAIN2614 ..............................................................................................................................................................1606\nCAIN2615 ..............................................................................................................................................................1606\nCAIN2616 ..............................................................................................................................................................1606\nCAIN2617 ..............................................................................................................................................................1606\nCAIN2618 ..............................................................................................................................................................1606\nCAIN2619 ..............................................................................................................................................................1607\nCAIN2620 ..............................................................................................................................................................1607\nCAIN2701 ..............................................................................................................................................................1607\nCAIN2702 ..............................................................................................................................................................1607\nCAIN2703 ..............................................................................................................................................................1607\nCAIN2704 ..............................................................................................................................................................1607\nCAIN2705 ..............................................................................................................................................................1608\nCAIN2706 ..............................................................................................................................................................1608\nCAIN2707 ..............................................................................................................................................................1608\nCAIN2708 ..............................................................................................................................................................1608\nCAIN2751 ..............................................................................................................................................................1608\nCAIN2752 ..............................................................................................................................................................1608\nCAIN2753 ..............................................................................................................................................................1608\nCAIN2754 ..............................................................................................................................................................1609\nCAIN2801 ..............................................................................................................................................................1609\nCAIN2802 ..............................................................................................................................................................1609\nCAIN2803 ..............................................................................................................................................................1609\nCAIN2804 ..............................................................................................................................................................1609", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "39d95e93ef60-1", "text": "CAIN2804 ..............................................................................................................................................................1609\nCAIN2901 ..............................................................................................................................................................1609\nCAIN2902 ..............................................................................................................................................................1610\nCAIN2903 ..............................................................................................................................................................1610\nCAIN2904 ..............................................................................................................................................................1610\nCAIN2905 ..............................................................................................................................................................1610\n 29", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c54d77c37b19-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2906 ..............................................................................................................................................................1610\nCAIN2907 ..............................................................................................................................................................1610\nCAIN2908 ..............................................................................................................................................................1611\nCAIN2909 ..............................................................................................................................................................1611\nCAIN2910 ..............................................................................................................................................................1611\nCAIN2911..............................................................................................................................................................1611\nCAIN2912 ..............................................................................................................................................................1611\nCAIN2913 ..............................................................................................................................................................1612\nCAIN2914 ..............................................................................................................................................................1612\nCAIN2915 ..............................................................................................................................................................1612\nCAIN2916 ..............................................................................................................................................................1612\nCAIN2917 ..............................................................................................................................................................1612\nCAIN2918 ..............................................................................................................................................................1612\nCAIN2919 ..............................................................................................................................................................1613\nCAIN2920 ..............................................................................................................................................................1613\nCAIN2921 ..............................................................................................................................................................1613\nCAIN2922 ..............................................................................................................................................................1613\nCAIN2923 ..............................................................................................................................................................1613\nCAIN2924 ..............................................................................................................................................................1613\nCAIN2925 ..............................................................................................................................................................1614\nCAIN2926 ..............................................................................................................................................................1614\nCAIN2927 ..............................................................................................................................................................1614\nCAIN2928 ..............................................................................................................................................................1614\nCAIN2929 ..............................................................................................................................................................1614\nCAIN2930 ..............................................................................................................................................................1614\nCAIN2931 ..............................................................................................................................................................1615\nCAIN2932 ..............................................................................................................................................................1615\nCAIN2933 ..............................................................................................................................................................1615\nCAIN2934 ..............................................................................................................................................................1615\nCAIN2935 ..............................................................................................................................................................1616\nCAIN2936 ..............................................................................................................................................................1616\nCAIN2937 ..............................................................................................................................................................1616\nCAIN2938 ..............................................................................................................................................................1616\nCAIN2939 ..............................................................................................................................................................1616\nCAIN2940 ..............................................................................................................................................................1616", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c54d77c37b19-1", "text": "CAIN2940 ..............................................................................................................................................................1616\nCAIN2941 ..............................................................................................................................................................1616\nCAIN2942 ..............................................................................................................................................................1617\nCAIN2943 ..............................................................................................................................................................1617\nCAIN2945 ..............................................................................................................................................................1617\nCAIN2946 ..............................................................................................................................................................1617\n 30", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "02ecdfa4b342-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2947 ..............................................................................................................................................................1617\nCAIN2948 ..............................................................................................................................................................1617\nCAIN2949 ..............................................................................................................................................................1618\nCAIN2950 ..............................................................................................................................................................1618\nCAIN2951 ..............................................................................................................................................................1618\nCAIN2952 ..............................................................................................................................................................1618\nCAIN2953 ..............................................................................................................................................................1618\nCAIN2954 ..............................................................................................................................................................1618\nCAIN2956 ..............................................................................................................................................................1619\nCAIN2957 ..............................................................................................................................................................1619\nCAIN2958 ..............................................................................................................................................................1619\nCAIN2959 ..............................................................................................................................................................1619\nCAIN2960 ..............................................................................................................................................................1619\nCAIN2961 ..............................................................................................................................................................1619\nCAIN2962 ..............................................................................................................................................................1620\nCAIN2963 ..............................................................................................................................................................1620\nCAIN2964 ..............................................................................................................................................................1620\nCAIN2965 ..............................................................................................................................................................1620\nCAIN2966 ..............................................................................................................................................................1621\nCAIN2967 ..............................................................................................................................................................1621\nCAIN2968 ..............................................................................................................................................................1621\nCAIN2969 ..............................................................................................................................................................1621\nCAIN2970 ..............................................................................................................................................................1621\nCAIN2971 ..............................................................................................................................................................1621\nCAIN2972 ..............................................................................................................................................................1622\nCAIN2973 ..............................................................................................................................................................1622\nCAIN2974 ..............................................................................................................................................................1622\nCAIN2975 ..............................................................................................................................................................1622\nCAIN2976 ..............................................................................................................................................................1622\nCAIN2977 ..............................................................................................................................................................1622\nCAIN2978 ..............................................................................................................................................................1623\nCAIN2979 ..............................................................................................................................................................1623\nCAIN2980 ..............................................................................................................................................................1623\nCAIN2981 ..............................................................................................................................................................1623\nCAIN2982 ..............................................................................................................................................................1623", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "02ecdfa4b342-1", "text": "CAIN2982 ..............................................................................................................................................................1623\nCAIN2983 ..............................................................................................................................................................1623\nCAIN2984 ..............................................................................................................................................................1624\nCAIN2985 ..............................................................................................................................................................1624\nCAIN2986 ..............................................................................................................................................................1624\nCAIN2987 ..............................................................................................................................................................1624\n 31", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "10646e4b0a2d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2988 ..............................................................................................................................................................1624\nCAIN2989 ..............................................................................................................................................................1624\nCAIN2990 ..............................................................................................................................................................1625\nCAIN2991 ..............................................................................................................................................................1625\nCAIN2992 ..............................................................................................................................................................1625\nCAIN2993 ..............................................................................................................................................................1625\nCAIN2994 ..............................................................................................................................................................1625\nCAIN2995 ..............................................................................................................................................................1625\nCAIN2996 ..............................................................................................................................................................1626\nCAIN2997 ..............................................................................................................................................................1626\nCAIN2998 ..............................................................................................................................................................1626\nCAIN2999 ..............................................................................................................................................................1626\nCAIN3000 ..............................................................................................................................................................1626\nCAIN3001 ..............................................................................................................................................................1627\nCAIN3006 ..............................................................................................................................................................1627\nCAIN3007 ..............................................................................................................................................................1627\nCAIN3008 ..............................................................................................................................................................1627\nCAIN3010 ..............................................................................................................................................................1627\nCAIN3020 ..............................................................................................................................................................1627\nCAIN3050 ..............................................................................................................................................................1627\nCAIN3051 ..............................................................................................................................................................1628\nCAIN3052 ..............................................................................................................................................................1628\nCAIN3099 ..............................................................................................................................................................1628\nCAIN3100 ..............................................................................................................................................................1628\nCAIN3101 ..............................................................................................................................................................1628\nCAIN3102 ..............................................................................................................................................................1629\nCAIN3103 ..............................................................................................................................................................1629\nCAIN3104 ..............................................................................................................................................................1629\nCAIN3105 ..............................................................................................................................................................1629\nCAIN3106 ..............................................................................................................................................................1629\nCAIN3107 ..............................................................................................................................................................1629\nCAIN3108 ..............................................................................................................................................................1630\nCAIN3109 ..............................................................................................................................................................1630\nCAIN3110..............................................................................................................................................................1630\nCAIN3111...............................................................................................................................................................1630", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "10646e4b0a2d-1", "text": "CAIN3111...............................................................................................................................................................1630\nCAIN3201 ..............................................................................................................................................................1630\nCAIN3202 ..............................................................................................................................................................1630\nCAIN3203 ..............................................................................................................................................................1630\nCAIN3205 ..............................................................................................................................................................1631\nCAIN3206 ..............................................................................................................................................................1631\n 32", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "670b239bd9af-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN3207 ..............................................................................................................................................................1631\nCAIN3208 ..............................................................................................................................................................1631\nCAIN3209 ..............................................................................................................................................................1631\nCAIN3211..............................................................................................................................................................1631\nCAIN3212 ..............................................................................................................................................................1632\nCAIN3213 ..............................................................................................................................................................1632\nCAIN3230 ..............................................................................................................................................................1632\nCAIN3231 ..............................................................................................................................................................1632\nCAIN3247 ..............................................................................................................................................................1632\nCAIN3264 ..............................................................................................................................................................1632\nCAIN3265 ..............................................................................................................................................................1632\nCAIN3266 ..............................................................................................................................................................1633\nCAIN3267 ..............................................................................................................................................................1633\nCAIN3268 ..............................................................................................................................................................1633\nCAIN3308 ..............................................................................................................................................................1633\nCAIN3323 ..............................................................................................................................................................1633\nCAIN3359 ..............................................................................................................................................................1633\nCAIN3360 ..............................................................................................................................................................1634\nCAIN3361 ..............................................................................................................................................................1634\nCAIN3395 ..............................................................................................................................................................1634\nCAIN3396 ..............................................................................................................................................................1634\nCAIN3397 ..............................................................................................................................................................1634\nCAIN3398 ..............................................................................................................................................................1634\nCAIN3399 ..............................................................................................................................................................1634\nCAIN3405 ..............................................................................................................................................................1635\nCAIN3406 ..............................................................................................................................................................1635\nCAIN3407 ..............................................................................................................................................................1635\nCAIN3408 ..............................................................................................................................................................1635\nCAIN3409 ..............................................................................................................................................................1635\nCAIN3416 ..............................................................................................................................................................1635\nCAIN3417 ..............................................................................................................................................................1636\nCAIN3418 ..............................................................................................................................................................1636\nCAIN3419 ..............................................................................................................................................................1636\nCAIN3475 ..............................................................................................................................................................1636\nCAIN3477 ..............................................................................................................................................................1636", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "670b239bd9af-1", "text": "CAIN3477 ..............................................................................................................................................................1636\nCAIN3501 ..............................................................................................................................................................1636\nCAIN3502 ..............................................................................................................................................................1637\nCAIN3627 ..............................................................................................................................................................1637\nCAIN3628 ..............................................................................................................................................................1637\nCAIN3629 ..............................................................................................................................................................1637\n 33", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "47aaa2757447-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN3630 ..............................................................................................................................................................1637\nCAIN3631 ..............................................................................................................................................................1637\nCAIN3632 ..............................................................................................................................................................1638\nCAIN3634 ..............................................................................................................................................................1638\nCAIN3637 ..............................................................................................................................................................1638\nCAIN3638 ..............................................................................................................................................................1638\nCAIN3639 ..............................................................................................................................................................1638\nCAIN3640 ..............................................................................................................................................................1638\nCAIN3641 ..............................................................................................................................................................1638\nCAIN3642 ..............................................................................................................................................................1639\nCAIN3643 ..............................................................................................................................................................1639\nCAIN3644 ..............................................................................................................................................................1639\nCAIN3645 ..............................................................................................................................................................1639\nCAIN3647 ..............................................................................................................................................................1639\nCAIN3648 ..............................................................................................................................................................1639\nCAIN3653 ..............................................................................................................................................................1640\nCAIN3654 ..............................................................................................................................................................1640\nCAIN3655 ..............................................................................................................................................................1640\nCAIN3656 ..............................................................................................................................................................1640\nCAIN3659 ..............................................................................................................................................................1640\nCAIN3661 ..............................................................................................................................................................1640\nCAIN3662 ..............................................................................................................................................................1640\nCAIN3701 ..............................................................................................................................................................1641\nCAIN3702 ..............................................................................................................................................................1641\nCAIN3703 ..............................................................................................................................................................1641\nCAIN3704 ..............................................................................................................................................................1641\nCAIN3705 ..............................................................................................................................................................1641\nCAIN3751 ..............................................................................................................................................................1641\nCAIN3752 ..............................................................................................................................................................1642\nCAIN3753 ..............................................................................................................................................................1642\nCAIN3754 ..............................................................................................................................................................1642\nCAIN3500 ..............................................................................................................................................................1642\nCAIN3503 ..............................................................................................................................................................1642\nCAIN3504 ..............................................................................................................................................................1642\nCAIN4301 ..............................................................................................................................................................1643", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "47aaa2757447-1", "text": "CAIN4301 ..............................................................................................................................................................1643\nCAIN4302 ..............................................................................................................................................................1643\nCAIN4303 ..............................................................................................................................................................1643\nCAIN4304 ..............................................................................................................................................................1643\nCAIN4305 ..............................................................................................................................................................1643\nCAIN4306 ..............................................................................................................................................................1643\n 34", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "febd9b68b311-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4307 ..............................................................................................................................................................1644\nCAIN4308 ..............................................................................................................................................................1644\nCAIN4309 ..............................................................................................................................................................1644\nCAIN4310 ..............................................................................................................................................................1644\nCAIN431 ................................................................................................................................................................1644\nCAIN4312 ..............................................................................................................................................................1644\nCAIN4313 ..............................................................................................................................................................1644\nCAIN4314 ..............................................................................................................................................................1645\nCAIN4315 ..............................................................................................................................................................1645\nCAIN4316 ..............................................................................................................................................................1645\nCAIN4317 ..............................................................................................................................................................1645\nCAIN4318 ..............................................................................................................................................................1645\nCAIN4319 ..............................................................................................................................................................1645\nCAIN4320 ..............................................................................................................................................................1646\nCAIN4321 ..............................................................................................................................................................1646\nCAIN4322 ..............................................................................................................................................................1646\nCAIN4323 ..............................................................................................................................................................1646\nCAIN4324 ..............................................................................................................................................................1646\nCAIN4325 ..............................................................................................................................................................1646\nCAIN4326 ..............................................................................................................................................................1647\nCAIN4327 ..............................................................................................................................................................1647\nCAIN4328 ..............................................................................................................................................................1647\nCAIN4329 ..............................................................................................................................................................1647\nCAIN4330 ..............................................................................................................................................................1647\nCAIN4331 ..............................................................................................................................................................1647\nCAIN4332 ..............................................................................................................................................................1647\nCAIN4333 ..............................................................................................................................................................1648\nCAIN4334 ..............................................................................................................................................................1648\nCAIN4335 ..............................................................................................................................................................1648\nCAIN4336 ..............................................................................................................................................................1648\nCAIN4337 ..............................................................................................................................................................1648\nCAIN4338 ..............................................................................................................................................................1648\nCAIN4339 ..............................................................................................................................................................1649\nCAIN4340 ..............................................................................................................................................................1649\nCAIN4341 ..............................................................................................................................................................1649", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "febd9b68b311-1", "text": "CAIN4341 ..............................................................................................................................................................1649\nCAIN4342 ..............................................................................................................................................................1649\nCAIN4343 ..............................................................................................................................................................1649\nCAIN4344 ..............................................................................................................................................................1649\nCAIN4345 ..............................................................................................................................................................1650\nCAIN4346 ..............................................................................................................................................................1650\n 35", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a25c859b39d2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4347 ..............................................................................................................................................................1650\nCAIN4348 ..............................................................................................................................................................1650\nCAIN4349 ..............................................................................................................................................................1650\nCAIN4350 ..............................................................................................................................................................1650\nCAIN4351 ..............................................................................................................................................................1650\nCAIN4352 ..............................................................................................................................................................1651\nCAIN4353 ..............................................................................................................................................................1651\nCAIN4354 ..............................................................................................................................................................1651\nCAIN4355 ..............................................................................................................................................................1651\nCAIN4356 ..............................................................................................................................................................1651\nCAIN4357 ..............................................................................................................................................................1651\nCAIN4358 ..............................................................................................................................................................1652\nCAIN4359 ..............................................................................................................................................................1652\nCAIN4360 ..............................................................................................................................................................1652\nCAIN4361 ..............................................................................................................................................................1652\nCAIN4362 ..............................................................................................................................................................1652\nCAIN4363 ..............................................................................................................................................................1652\nCAIN4364 ..............................................................................................................................................................1652\nCAIN4365 ..............................................................................................................................................................1653\nCAIN4366 ..............................................................................................................................................................1653\nCAIN4367 ..............................................................................................................................................................1653\nCAIN4369 ..............................................................................................................................................................1653\nCAIN4370 ..............................................................................................................................................................1653\nCAIN4371 ..............................................................................................................................................................1653\nCAIN4372 ..............................................................................................................................................................1654\nCAIN4373 ..............................................................................................................................................................1654\nCAIN4374 ..............................................................................................................................................................1654\nCAIN4375 ..............................................................................................................................................................1654\nCAIN4376 ..............................................................................................................................................................1654\nCAIN4377 ..............................................................................................................................................................1654\nCAIN4378 ..............................................................................................................................................................1655\nCAIN4379 ..............................................................................................................................................................1655\nCAIN4380 ..............................................................................................................................................................1655\nCAIN4381 ..............................................................................................................................................................1655\nCAIN4382 ..............................................................................................................................................................1655", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a25c859b39d2-1", "text": "CAIN4382 ..............................................................................................................................................................1655\nCAIN4383 ..............................................................................................................................................................1655\nCAIN4384 ..............................................................................................................................................................1656\nCAIN4385 ..............................................................................................................................................................1656\nCAIN4386 ..............................................................................................................................................................1656\nCAIN4387 ..............................................................................................................................................................1656\n 36", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9a22adbe30d9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4388 ..............................................................................................................................................................1657\nCAIN4501 ..............................................................................................................................................................1657\nCAIN4502 ..............................................................................................................................................................1657\nCAIN4503 ..............................................................................................................................................................1657\nCAIN4504 ..............................................................................................................................................................1657\nCAIN4505 ..............................................................................................................................................................1658\nCAIN4506 ..............................................................................................................................................................1658\nCAIN4507 ..............................................................................................................................................................1658\nCAIN4508 ..............................................................................................................................................................1658\nCAIN4510 ..............................................................................................................................................................1658\nCAIN4511..............................................................................................................................................................1658\nCAIN4513 ..............................................................................................................................................................1659\nCAIN4515 ..............................................................................................................................................................1659\nCAIN4516 ..............................................................................................................................................................1659\nCAIN4518 ..............................................................................................................................................................1659\nCAIN4519 ..............................................................................................................................................................1659\nCAIN4520 ..............................................................................................................................................................1659\nCAIN4521 ..............................................................................................................................................................1659\nCAIN4522 ..............................................................................................................................................................1660\nCAIN4523 ..............................................................................................................................................................1660\nCAIN4527 ..............................................................................................................................................................1660\nCAIN4528 ..............................................................................................................................................................1660\nCAIN4529 ..............................................................................................................................................................1660\nCAIN4530 ..............................................................................................................................................................1660\nCAIN4532 ..............................................................................................................................................................1661\nCAIN4533 ..............................................................................................................................................................1661\nCAIN4536 ..............................................................................................................................................................1661\nCAIN4537 ..............................................................................................................................................................1661\nCAIN4538 ..............................................................................................................................................................1661\nCAIN4539 ..............................................................................................................................................................1661\nCAIN4540 ..............................................................................................................................................................1661\nCAIN4541 ..............................................................................................................................................................1662\nCAIN4542 ..............................................................................................................................................................1662\nCAIN4543 ..............................................................................................................................................................1662\nCAIN4544 ..............................................................................................................................................................1662", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9a22adbe30d9-1", "text": "CAIN4544 ..............................................................................................................................................................1662\nCAIN4547 ..............................................................................................................................................................1662\nCAIN4548 ..............................................................................................................................................................1662\nCAIN4549 ..............................................................................................................................................................1663\nCAIN4550 ..............................................................................................................................................................1663\nCAIN4551 ..............................................................................................................................................................1663\n 37", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d9edbeacb0dc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4552 ..............................................................................................................................................................1663\nCAIN4553 ..............................................................................................................................................................1663\nCAIN4554 ..............................................................................................................................................................1663\nCAIN4555 ..............................................................................................................................................................1663\nCAIN4556 ..............................................................................................................................................................1664\nCAIN4557 ..............................................................................................................................................................1664\nCAIN4558 ..............................................................................................................................................................1664\nCAIN4559 ..............................................................................................................................................................1664\nCAIN4560 ..............................................................................................................................................................1664\nCAIN4561 ..............................................................................................................................................................1664\nCAIN4562 ..............................................................................................................................................................1665\nCAIN4563 ..............................................................................................................................................................1665\nCAIN4564 ..............................................................................................................................................................1665\nCAIN4565 ..............................................................................................................................................................1665\nCAIN4566 ..............................................................................................................................................................1665\nCAIN4567 ..............................................................................................................................................................1665\nCAIN4568 ..............................................................................................................................................................1666\nCAIN4569 ..............................................................................................................................................................1666\nCAIN4570 ..............................................................................................................................................................1666\nCAIN4571 ..............................................................................................................................................................1666\nCAIN4572 ..............................................................................................................................................................1666\nCAIN4573 ..............................................................................................................................................................1666\nCAIN4574 ..............................................................................................................................................................1667\nCAIN4575 ..............................................................................................................................................................1667\nCAIN4576 ..............................................................................................................................................................1667\nCAIN4577 ..............................................................................................................................................................1667\nCAIN4578 ..............................................................................................................................................................1667\nCAIN4579 ..............................................................................................................................................................1667\nCAIN4580 ..............................................................................................................................................................1668\nCAIN4581 ..............................................................................................................................................................1668\nCAIN4582 ..............................................................................................................................................................1668\nCAIN4583 ..............................................................................................................................................................1668\nCAIN4584 ..............................................................................................................................................................1668\nCAIN4585 ..............................................................................................................................................................1668\nCAIN4586 ..............................................................................................................................................................1668", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d9edbeacb0dc-1", "text": "CAIN4586 ..............................................................................................................................................................1668\nCAIN4587 ..............................................................................................................................................................1669\nCAIN4588 ..............................................................................................................................................................1669\nCAIN4589 ..............................................................................................................................................................1669\nCAIN4590 ..............................................................................................................................................................1669\nCAIN4591 ..............................................................................................................................................................1669\n 38", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fa96e5365f58-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4592 ..............................................................................................................................................................1669\nCAIN4593 ..............................................................................................................................................................1670\nCAIN4594 ..............................................................................................................................................................1670\nCAIN4595 ..............................................................................................................................................................1670\nCAIN4596 ..............................................................................................................................................................1670\nCAIN4597 ..............................................................................................................................................................1670\nCAIN4598 ..............................................................................................................................................................1670\nCAIN4599 ..............................................................................................................................................................1671\nCAIN4600 ..............................................................................................................................................................1671\nCAIN4601 ..............................................................................................................................................................1671\nCAIN4602 ..............................................................................................................................................................1671\nCAIN4603 ..............................................................................................................................................................1671\nCAIN4604 ..............................................................................................................................................................1671\nCAIN4605 ..............................................................................................................................................................1671\nCAIN4606 ..............................................................................................................................................................1672\nCAIN4607 ..............................................................................................................................................................1672\nCAIN4608 ..............................................................................................................................................................1672\nCAIN4609 ..............................................................................................................................................................1672\nCAIN4610 ..............................................................................................................................................................1672\nCAIN4611..............................................................................................................................................................1672\nCAIN4612 ..............................................................................................................................................................1673\nCAIN4613 ..............................................................................................................................................................1673\nCAIN4614 ..............................................................................................................................................................1673\nCAIN4615 ..............................................................................................................................................................1673\nCAIN4616 ..............................................................................................................................................................1673\nCAIN4617 ..............................................................................................................................................................1673\nCAIN4618 ..............................................................................................................................................................1674\nCAIN4619 ..............................................................................................................................................................1674\nCAIN4620 ..............................................................................................................................................................1674\nCAIN4621 ..............................................................................................................................................................1674\nCAIN4622 ..............................................................................................................................................................1674\nCAIN4623 ..............................................................................................................................................................1674\nCAIN4701 ..............................................................................................................................................................1675\nCAIN4702 ..............................................................................................................................................................1675\nCAIN4703 ..............................................................................................................................................................1675", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fa96e5365f58-1", "text": "CAIN4703 ..............................................................................................................................................................1675\nCAIN4704 ..............................................................................................................................................................1675\nCAIN4705 ..............................................................................................................................................................1676\nCAIN4707 ..............................................................................................................................................................1676\nCAIN4708 ..............................................................................................................................................................1676\nCAIN4709 ..............................................................................................................................................................1676\n 39", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c4d42e2c78d0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4710 ..............................................................................................................................................................1676\nCAIN4711..............................................................................................................................................................1676\nCAIN4712 ..............................................................................................................................................................1677\nCAIN4713 ..............................................................................................................................................................1677\nCAIN4714 ..............................................................................................................................................................1677\nCAIN4715 ..............................................................................................................................................................1677\nCAIN4716 ..............................................................................................................................................................1677\nCAIN4717 ..............................................................................................................................................................1678\nCAIN4718 ..............................................................................................................................................................1678\nCAIN4719 ..............................................................................................................................................................1678\nCAIN4720 ..............................................................................................................................................................1678\nCAIN4721 ..............................................................................................................................................................1678\nCAIN4722 ..............................................................................................................................................................1679\nCAIN4723 ..............................................................................................................................................................1679\nCAIN4724 ..............................................................................................................................................................1679\nCAIN4725 ..............................................................................................................................................................1679\nCAIN4726 ..............................................................................................................................................................1679\nCAIN4727 ..............................................................................................................................................................1679\nCAIN4728 ..............................................................................................................................................................1679\nCAIN4729 ..............................................................................................................................................................1680\nCAIN4730 ..............................................................................................................................................................1680\nCAIN4731 ..............................................................................................................................................................1680\nCAIN4732 ..............................................................................................................................................................1680\nCAIN4733 ..............................................................................................................................................................1680\nCAIN4734 ..............................................................................................................................................................1680\nCAIN4735 ..............................................................................................................................................................1681\nCAIN4736 ..............................................................................................................................................................1681\nCAIN4737 ..............................................................................................................................................................1681\nCAIN4738 ..............................................................................................................................................................1681\nCAIN4739 ..............................................................................................................................................................1681\nCAIN4740 ..............................................................................................................................................................1681\nCAIN4741 ..............................................................................................................................................................1681\nCAIN4742 ..............................................................................................................................................................1682\nCAIN4743 ..............................................................................................................................................................1682\nCAIN4744 ..............................................................................................................................................................1682", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c4d42e2c78d0-1", "text": "CAIN4744 ..............................................................................................................................................................1682\nCAIN4745 ..............................................................................................................................................................1682\nCAIN4746 ..............................................................................................................................................................1682\nCAIN4747 ..............................................................................................................................................................1682\nCAIN4748 ..............................................................................................................................................................1683\nCAIN4749 ..............................................................................................................................................................1683\n 40", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "120911a4f528-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4750 ..............................................................................................................................................................1683\nCAIN4751 ..............................................................................................................................................................1683\nCAIN4752 ..............................................................................................................................................................1683\nCAIN4753 ..............................................................................................................................................................1683\nCAIN4901 ..............................................................................................................................................................1683\nCAIN4902 ..............................................................................................................................................................1684\nCAIN4903 ..............................................................................................................................................................1684\nCAIN4904 ..............................................................................................................................................................1684\nCAIN4905 ..............................................................................................................................................................1684\nCAIN4906 ..............................................................................................................................................................1684\nCAIN4624 ..............................................................................................................................................................1684\nCAIN4625 ..............................................................................................................................................................1685\nCAIN4626 ..............................................................................................................................................................1685\nCAIN5101 ..............................................................................................................................................................1685\nCAIN5102 ..............................................................................................................................................................1685\nCAIN5103 ..............................................................................................................................................................1685\nCAIN5104 ..............................................................................................................................................................1685\nCAIN5105 ..............................................................................................................................................................1686\nCAIN5198 ..............................................................................................................................................................1686\nCAIN5199 ..............................................................................................................................................................1686\nCAIN5301 ..............................................................................................................................................................1686\nCAIN5302 ..............................................................................................................................................................1686\nCAIN5303 ..............................................................................................................................................................1686\nCAIN5304 ..............................................................................................................................................................1687\nCAIN8000 ..............................................................................................................................................................1687\nCAIN8001 ..............................................................................................................................................................1687\nCAIN8002 ..............................................................................................................................................................1687\nCAIN8003 ..............................................................................................................................................................1688\nCAIN8004 ..............................................................................................................................................................1688\nCAIN8005 ..............................................................................................................................................................1688\nCAIN8006 ..............................................................................................................................................................1688\nCAIN8981 ..............................................................................................................................................................1689\nCAIN8982 ..............................................................................................................................................................1689\nCAIN8983 ..............................................................................................................................................................1689\nCAIN8007 ..............................................................................................................................................................1689", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "120911a4f528-1", "text": "CAIN8007 ..............................................................................................................................................................1689\nInterTest Batch Messages and Abend Codes .........................................................................................................1689\nABA00 ....................................................................................................................................................................1689\nABA03 ....................................................................................................................................................................1689\nABA05 ....................................................................................................................................................................1689\nABA06 ....................................................................................................................................................................1690\n 41", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c5e71fefdd3c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nABA0A ...................................................................................................................................................................1690\nABA13 ....................................................................................................................................................................1690\nABA14 ....................................................................................................................................................................1690\nCAMRA011............................................................................................................................................................1690\nCAMRA012 ............................................................................................................................................................1690\nCAMRA013 ............................................................................................................................................................1690\nCAMRA014 ............................................................................................................................................................1690\nCAMRA028 ............................................................................................................................................................1690\nCAMRA029 ............................................................................................................................................................1690\nCAMRA033 ............................................................................................................................................................1690\nCAMRA034 ............................................................................................................................................................1691\nCAMRA035 ............................................................................................................................................................1691\nCAMRA036 ............................................................................................................................................................1691\nCAMRA037 ............................................................................................................................................................1691\nCAMRA038 ............................................................................................................................................................1691\nCAMRA090 ............................................................................................................................................................1691\nCAMRA092 ............................................................................................................................................................1691\nCAMRA093 ............................................................................................................................................................1691\nCAMRA094 ............................................................................................................................................................1691\nCAMRA095 ............................................................................................................................................................1691\nCAMRA097 ............................................................................................................................................................1692\nCAMRA098 ............................................................................................................................................................1692\nCAMRA099 ............................................................................................................................................................1692\nCAMRA101 ............................................................................................................................................................1692\nCAMRA102 ............................................................................................................................................................1692\nCAMRA103 ............................................................................................................................................................1692\nCAMRA104 ............................................................................................................................................................1692\nCAMRA105 ............................................................................................................................................................1692\nCAMRA107 ............................................................................................................................................................1692\nCAMRA301 ............................................................................................................................................................1692\nCAMRA302 ............................................................................................................................................................1693\nCAMRA303 ............................................................................................................................................................1693\nCAMRA304 ............................................................................................................................................................1693\nCAMRA305 ............................................................................................................................................................1693\nCAMRA306 ............................................................................................................................................................1693\nCAMR900E ............................................................................................................................................................1693\nCAMR901E ............................................................................................................................................................1693\nCAMR902W ...........................................................................................................................................................1693", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c5e71fefdd3c-1", "text": "CAMR902W ...........................................................................................................................................................1693\nCAMR910E ............................................................................................................................................................1694\nCAMR911E............................................................................................................................................................1694\n 42", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e072da1cea65-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAMR912E ............................................................................................................................................................1694\nCAMR914E ............................................................................................................................................................1694\nCAMR915E ............................................................................................................................................................1694\nCAMR916E ............................................................................................................................................................1694\nCAMR917E ............................................................................................................................................................1694\nCAMR950I .............................................................................................................................................................1694\nCAMR951E ............................................................................................................................................................1694\nCAMR952E ............................................................................................................................................................1695\nCAMR954E ............................................................................................................................................................1695\nCAMR955E ............................................................................................................................................................1695\nCAMR956E ............................................................................................................................................................1695\nCAMR957E ............................................................................................................................................................1695\nCAMR960E ............................................................................................................................................................1695\nCAMR961E ............................................................................................................................................................1695\nCAMR962E ............................................................................................................................................................1695\nCAMR963E ............................................................................................................................................................1695\nCAMRS01W ..........................................................................................................................................................1695\nCAMRS02E ...........................................................................................................................................................1695\nCAMRS03E ...........................................................................................................................................................1696\nCAMRS04E ...........................................................................................................................................................1696\nCAMRS05E ...........................................................................................................................................................1696\nCAMRS06I .............................................................................................................................................................1696\nCAMRS07I .............................................................................................................................................................1696\nCAMRS08I .............................................................................................................................................................1696\nCAMRS09E ...........................................................................................................................................................1696\nCAMRS10I .............................................................................................................................................................1696\nCAMRS011I...........................................................................................................................................................1696\nCAMRAS12I ..........................................................................................................................................................1697\nCAMAS13I .............................................................................................................................................................1697\nCAMRS14W ..........................................................................................................................................................1697\nCAMRS15I .............................................................................................................................................................1697\nCAMRS16I .............................................................................................................................................................1697\nCAMRS17I .............................................................................................................................................................1697\nCAMRS18I .............................................................................................................................................................1697\nCAMRS19E ...........................................................................................................................................................1697", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e072da1cea65-1", "text": "CAMRS19E ...........................................................................................................................................................1697\nCAMRS20E ...........................................................................................................................................................1697\nCAMRS20E0 .........................................................................................................................................................1698\nCAMRS21I .............................................................................................................................................................1698\nCAMRS22W ..........................................................................................................................................................1698\nCAMRS23I .............................................................................................................................................................1698\n 43", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0174b0bc31cd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAMRS24E ...........................................................................................................................................................1698\nCAMRS25W ..........................................................................................................................................................1698\nCAMRS26I .............................................................................................................................................................1698\nCAMRS27I .............................................................................................................................................................1698\nCAMRS28W ..........................................................................................................................................................1698\nCAMRS29I .............................................................................................................................................................1699\nCAMRS29W ..........................................................................................................................................................1699\nCAMRS30I .............................................................................................................................................................1699\nCAMRS31W ..........................................................................................................................................................1699\nCAMRS32W ..........................................................................................................................................................1699\nCAMRS33E ...........................................................................................................................................................1699\nCAMRS34E ...........................................................................................................................................................1699\nINTA006.................................................................................................................................................................1699\nINTA007.................................................................................................................................................................1700\nINTA008.................................................................................................................................................................1700\nINTA009.................................................................................................................................................................1700\nINTA010.................................................................................................................................................................1700\nINTA020.................................................................................................................................................................1700\nINTA021.................................................................................................................................................................1700\nINTA110.................................................................................................................................................................1700\nINTA120.................................................................................................................................................................1700\nINTA130.................................................................................................................................................................1700\nINTA210.................................................................................................................................................................1700\nINTA211.................................................................................................................................................................1700\nINTA212.................................................................................................................................................................1701\nINTA220.................................................................................................................................................................1701\nINTA221.................................................................................................................................................................1701\nINTA222.................................................................................................................................................................1701\nINTA223.................................................................................................................................................................1701\nINTA224.................................................................................................................................................................1701\nINTA225.................................................................................................................................................................1701\nINTA226.................................................................................................................................................................1701\nINTA300.................................................................................................................................................................1701\nINTA301.................................................................................................................................................................1701\nINTA302.................................................................................................................................................................1702\nINTA303.................................................................................................................................................................1702\nINTA304.................................................................................................................................................................1702", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0174b0bc31cd-1", "text": "INTA303.................................................................................................................................................................1702\nINTA304.................................................................................................................................................................1702\nINTA305.................................................................................................................................................................1702\nINTA306.................................................................................................................................................................1702\nINTA307.................................................................................................................................................................1702\n 44", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "112886e14eda-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nINTA308.................................................................................................................................................................1702\nINTA309.................................................................................................................................................................1702\nINTA310.................................................................................................................................................................1702\nINTA311.................................................................................................................................................................1702\nINTA312.................................................................................................................................................................1703\nINTA510.................................................................................................................................................................1703\nINTA520.................................................................................................................................................................1703\nINTA610.................................................................................................................................................................1703\nINTA620.................................................................................................................................................................1703\nINTA621.................................................................................................................................................................1703\nINTAK210...............................................................................................................................................................1703\nINTAK218...............................................................................................................................................................1703\nINTAK219...............................................................................................................................................................1703\nINTAK350...............................................................................................................................................................1703\nINTAK360...............................................................................................................................................................1704\nINTAK364...............................................................................................................................................................1704\nINTAK368...............................................................................................................................................................1704\nINTAK369...............................................................................................................................................................1704\nINTAK410...............................................................................................................................................................1704\nINTAK420...............................................................................................................................................................1704\nINTAK438...............................................................................................................................................................1704\nINTAK448...............................................................................................................................................................1704\nINTAL708...............................................................................................................................................................1704\nINTAM100..............................................................................................................................................................1704\nINTAM704..............................................................................................................................................................1705\nINTAM714..............................................................................................................................................................1705\nINTAN708..............................................................................................................................................................1705\nINTB000 .................................................................................................................................................................1705\nINTB001 .................................................................................................................................................................1705\nINTB002 .................................................................................................................................................................1705\nINTB003 .................................................................................................................................................................1705\nINTB004 .................................................................................................................................................................1705\nINTB005 .................................................................................................................................................................1705\nINTB006 .................................................................................................................................................................1705\nINTB007 .................................................................................................................................................................1705\nINTB008 .................................................................................................................................................................1705\nINTB009 .................................................................................................................................................................1706\nINTB100 .................................................................................................................................................................1706", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "112886e14eda-1", "text": "INTB009 .................................................................................................................................................................1706\nINTB100 .................................................................................................................................................................1706\nINTB101 .................................................................................................................................................................1706\nINTB102 .................................................................................................................................................................1706\n 45", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c3c89c8832cb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nINTG001 ................................................................................................................................................................1706\nINTG002 ................................................................................................................................................................1706\nINTG003 ................................................................................................................................................................1706\nINTG005 ................................................................................................................................................................1706\nINTG007 ................................................................................................................................................................1706\nINTG008 ................................................................................................................................................................1706\nINTG009 ................................................................................................................................................................1707\nINTG101 ................................................................................................................................................................1707\nINTG102 ................................................................................................................................................................1707\nXDAIR004 ..............................................................................................................................................................1707\nXDAIR008 ..............................................................................................................................................................1707\nXDAIR016 ..............................................................................................................................................................1707\nXDAIR020 ..............................................................................................................................................................1707\nXDAIR024 ..............................................................................................................................................................1707\nXDAIR028 ..............................................................................................................................................................1707\nXDAIR032 ..............................................................................................................................................................1707\nXDAIR036 ..............................................................................................................................................................1708\nXDAIR040 ..............................................................................................................................................................1708\nXDAIR044 ..............................................................................................................................................................1708\nXDAIR048 ..............................................................................................................................................................1708\nXDAIR052 ..............................................................................................................................................................1708\n001.........................................................................................................................................................................1708\n002.........................................................................................................................................................................1708\n003, 004, and 008 .................................................................................................................................................1708\n013.........................................................................................................................................................................1708\n02x.........................................................................................................................................................................1708\n030.........................................................................................................................................................................1708\n031.........................................................................................................................................................................1709\n032.........................................................................................................................................................................1709\n033.........................................................................................................................................................................1709\n034.........................................................................................................................................................................1709\n035.........................................................................................................................................................................1709\n036.........................................................................................................................................................................1709\n037.........................................................................................................................................................................1709\n038.........................................................................................................................................................................1709\n039.........................................................................................................................................................................1709\n03A........................................................................................................................................................................1709\n03B........................................................................................................................................................................1709\n03C........................................................................................................................................................................1709\n03D........................................................................................................................................................................1709\n 46", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "298412f296a0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n03E........................................................................................................................................................................1710\n0C1, 0C2, and 0C3 ...............................................................................................................................................1710\n0C4 and 0C6 .........................................................................................................................................................1710\n0C7........................................................................................................................................................................1710\n0C8 and 0CA ........................................................................................................................................................1710\n0C9 and 0CB ........................................................................................................................................................1710\n0CC, 0CD, 0CE, and OCF ...................................................................................................................................1710\n13E in BMP Region ..............................................................................................................................................1710\n213.........................................................................................................................................................................1711\n437.........................................................................................................................................................................1711\n706.........................................................................................................................................................................1711\n806.........................................................................................................................................................................1711\n80A........................................................................................................................................................................1711\n90A........................................................................................................................................................................1711\n913.........................................................................................................................................................................1711\nB37........................................................................................................................................................................1711\nC03........................................................................................................................................................................1711\nD37........................................................................................................................................................................1711\nE37........................................................................................................................................................................1712\n519.........................................................................................................................................................................1712\nSymDump  Batch Messages ......................................................................................................................................1712\nCAPC011W............................................................................................................................................................1713\nCAPC012I ..............................................................................................................................................................1713\nCAPC013I ..............................................................................................................................................................1713\nCAPC018E ............................................................................................................................................................1713\nCAPC020W ...........................................................................................................................................................1714\nCAPC021I ..............................................................................................................................................................1714\nCAPC022I ..............................................................................................................................................................1714\nCAPC023I ..............................................................................................................................................................1714\nCAPC024I ..............................................................................................................................................................1714\nCAPC025I ..............................................................................................................................................................1715\nCAPC030I ..............................................................................................................................................................1715\nCAPC031I ..............................................................................................................................................................1715\nCAPC032E ............................................................................................................................................................1715\nCAPC033I ..............................................................................................................................................................1715", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "298412f296a0-1", "text": "CAPC033I ..............................................................................................................................................................1715\nCAPC034I ..............................................................................................................................................................1715\nCAPC035E ............................................................................................................................................................1716\nCAPC040I ..............................................................................................................................................................1716\nCAPC041I ..............................................................................................................................................................1716\nCAPC042E ............................................................................................................................................................1716\n 47", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "531950c2cf50-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPC043W ...........................................................................................................................................................1716\nCAPC077E ............................................................................................................................................................1716\nCAPC078W ...........................................................................................................................................................1717\nCAPC081E ............................................................................................................................................................1718\nCAPC082E ............................................................................................................................................................1718\nCAPC084E ............................................................................................................................................................1718\nCAPC088E ............................................................................................................................................................1718\nCAPC089E ............................................................................................................................................................1718\nCAPC091E ............................................................................................................................................................1718\nCAPC094E ............................................................................................................................................................1719\nCAPC097E ............................................................................................................................................................1719\nCAPC098E ............................................................................................................................................................1719\nCAPC099E ............................................................................................................................................................1720\nCAPD107E ............................................................................................................................................................1720\nCAPD109W ...........................................................................................................................................................1720\nCAPD110W............................................................................................................................................................1720\nCAPD112W............................................................................................................................................................1720\nCAPD113W............................................................................................................................................................1721\nCAPD114W............................................................................................................................................................1721\nCAPD115W............................................................................................................................................................1721\nCAPD116W............................................................................................................................................................1721\nCAPD117W............................................................................................................................................................1721\nCAPD118W............................................................................................................................................................1722\nCAPD123I ..............................................................................................................................................................1722\nCAPD137I ..............................................................................................................................................................1722\nCAPD138I ..............................................................................................................................................................1722\nCAPD140E ............................................................................................................................................................1722\nCAPD141E ............................................................................................................................................................1722\nCAPD142W ...........................................................................................................................................................1723\nCAPD143W ...........................................................................................................................................................1723\nCAPD144W ...........................................................................................................................................................1723\nCAPD145W ...........................................................................................................................................................1723\nCAPD146W ...........................................................................................................................................................1723\nCAPD147I ..............................................................................................................................................................1724\nCAPD148I ..............................................................................................................................................................1724", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "531950c2cf50-1", "text": "CAPD148I ..............................................................................................................................................................1724\nCAPD149I ..............................................................................................................................................................1724\nCAPD150I ..............................................................................................................................................................1724\nCAPD151I ..............................................................................................................................................................1724\nCAPD152I ..............................................................................................................................................................1724\nCAPD153E ............................................................................................................................................................1725\n 48", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dc693757067c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPD154W ...........................................................................................................................................................1725\nCAPD157W ...........................................................................................................................................................1725\nCAPD158W ...........................................................................................................................................................1725\nCAPE001E .............................................................................................................................................................1725\nCAPE002E .............................................................................................................................................................1725\nCAPE003I ..............................................................................................................................................................1726\nCAPE003W ............................................................................................................................................................1726\nCAPE004I ..............................................................................................................................................................1726\nCAPE005I ..............................................................................................................................................................1726\nCAPE006E .............................................................................................................................................................1726\nCAPE007E .............................................................................................................................................................1726\nCAPE008E .............................................................................................................................................................1727\nCAPE009E .............................................................................................................................................................1727\nCAPE010E .............................................................................................................................................................1727\nCAPE011E.............................................................................................................................................................1727\nCAPE013I ..............................................................................................................................................................1727\nCAPE013W ............................................................................................................................................................1727\nCAPE014I ..............................................................................................................................................................1727\nCAPE015I ..............................................................................................................................................................1728\nCAPE016W ............................................................................................................................................................1728\nCAPE017I ..............................................................................................................................................................1728\nCAPE018I ..............................................................................................................................................................1728\nCAPE019I ..............................................................................................................................................................1728\nCAPE019W ............................................................................................................................................................1728\nCAPE021E .............................................................................................................................................................1729\nCAPE022I ..............................................................................................................................................................1729\nCAPE023I ..............................................................................................................................................................1729\nCAPE024E .............................................................................................................................................................1729\nCAPE025I ..............................................................................................................................................................1729\nCAPE026I ..............................................................................................................................................................1729\nCAPE027I ..............................................................................................................................................................1730\nCAPE028I ..............................................................................................................................................................1730\nCAPE029I ..............................................................................................................................................................1730\nCAPE030W ............................................................................................................................................................1730\nCAPE031I ..............................................................................................................................................................1730\nCAPE032W ............................................................................................................................................................1731\nCAPE033W ............................................................................................................................................................1731\nCAPE034W ............................................................................................................................................................1731", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dc693757067c-1", "text": "CAPE033W ............................................................................................................................................................1731\nCAPE034W ............................................................................................................................................................1731\nCAPH600W ...........................................................................................................................................................1731\nCAPH601E ............................................................................................................................................................1731\n 49", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f23fe634a3e8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPH602E ............................................................................................................................................................1731\nCAPH603E ............................................................................................................................................................1732\nCAPH604E ............................................................................................................................................................1732\nCAPH605I ..............................................................................................................................................................1732\nCAPH606E ............................................................................................................................................................1732\nCAPI000E ..............................................................................................................................................................1732\nCAPI002E ..............................................................................................................................................................1733\nCAPI004E ..............................................................................................................................................................1733\nCAPI005E ..............................................................................................................................................................1733\nCAPI006E ..............................................................................................................................................................1733\nCAPI007E ..............................................................................................................................................................1733\nCAPI010E ..............................................................................................................................................................1734\nCAPI011W.............................................................................................................................................................1734\nCAPI012W .............................................................................................................................................................1734\nCAPI015E ..............................................................................................................................................................1734\nCAPI016I ...............................................................................................................................................................1734\nCAPI017E ..............................................................................................................................................................1734\nCAPI018I ...............................................................................................................................................................1735\nCAPI021W .............................................................................................................................................................1735\nCAPI022E ..............................................................................................................................................................1735\nCAPI023W .............................................................................................................................................................1735\nCAPI026W .............................................................................................................................................................1735\nCAPI027I ...............................................................................................................................................................1736\nCAPI030I ...............................................................................................................................................................1736\nCAPI035W .............................................................................................................................................................1736\nCAPI036I ...............................................................................................................................................................1736\nCAPI037I ...............................................................................................................................................................1736\nCAPI040I ...............................................................................................................................................................1737\nCAPI041E ..............................................................................................................................................................1737\nCAPI042I ...............................................................................................................................................................1737\nCAPI045I ...............................................................................................................................................................1737\nCAPI049W .............................................................................................................................................................1737\nCAPI052I ...............................................................................................................................................................1738\nCAPI055I ...............................................................................................................................................................1738\nCAPI056I ...............................................................................................................................................................1738", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f23fe634a3e8-1", "text": "CAPI056I ...............................................................................................................................................................1738\nCAPI057I ...............................................................................................................................................................1738\nCAPI058I ...............................................................................................................................................................1739\nCAPI059E ..............................................................................................................................................................1739\nCAPI060I ...............................................................................................................................................................1739\nCAPI061E ..............................................................................................................................................................1739\n 50", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "68593c7a9ee3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPI062E ..............................................................................................................................................................1740\nCAPI063I ...............................................................................................................................................................1740\nCAPI064I ...............................................................................................................................................................1740\nCAPI066I ...............................................................................................................................................................1740\nCAPI067I ...............................................................................................................................................................1740\nCAPI070W .............................................................................................................................................................1741\nCAPI071W .............................................................................................................................................................1741\nCAPI074W .............................................................................................................................................................1741\nCAPI075W .............................................................................................................................................................1741\nCAPI075W0 ...........................................................................................................................................................1741\nCAPI098E ..............................................................................................................................................................1742\nCAPI099E ..............................................................................................................................................................1742\nCAPI100I ...............................................................................................................................................................1742\nCAPI101W .............................................................................................................................................................1743\nCAPI102E ..............................................................................................................................................................1743\nCAPI103W .............................................................................................................................................................1743\nCAPI108W .............................................................................................................................................................1743\nCAPI109W .............................................................................................................................................................1744\nCAPI111E...............................................................................................................................................................1744\nCAPI112W.............................................................................................................................................................1744\nCAPI118E..............................................................................................................................................................1745\nCAPI120W .............................................................................................................................................................1745\nCAPI121E ..............................................................................................................................................................1745\nCAPI122I ...............................................................................................................................................................1745\nCAPI123W .............................................................................................................................................................1746\nCAPI124E ..............................................................................................................................................................1746\nCAPI125I ...............................................................................................................................................................1746\nCAPI140E ..............................................................................................................................................................1746\nCAPI141E ..............................................................................................................................................................1746\nCAPI145E ..............................................................................................................................................................1746\nCAPI146E ..............................................................................................................................................................1747\nCAPI147E ..............................................................................................................................................................1747\nCAPI199E ..............................................................................................................................................................1747\nCAPI201E ..............................................................................................................................................................1747\nCAPI202E ..............................................................................................................................................................1748", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "68593c7a9ee3-1", "text": "CAPI202E ..............................................................................................................................................................1748\nCAPI203E ..............................................................................................................................................................1748\nCAPI204E ..............................................................................................................................................................1748\nCAPI205E ..............................................................................................................................................................1748\nCAPI206E ..............................................................................................................................................................1749\nCAPI207I ...............................................................................................................................................................1749\n 51", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ddda59da63da-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPI208E ..............................................................................................................................................................1749\nCAPI209W .............................................................................................................................................................1749\nCAPI210E ..............................................................................................................................................................1750\nCAPR312W ...........................................................................................................................................................1750\nCAPR313E ............................................................................................................................................................1750\nCAPR318E ............................................................................................................................................................1750\nCAPR321E ............................................................................................................................................................1750\nCAPR322E ............................................................................................................................................................1751\nCAPR323E ............................................................................................................................................................1751\nCAPR327W ...........................................................................................................................................................1751\nCAPR333W ...........................................................................................................................................................1751\nCAPR334E ............................................................................................................................................................1751\nCAPR338E ............................................................................................................................................................1752\nCAPR339E ............................................................................................................................................................1752\nCAPR340E ............................................................................................................................................................1752\nCAPR436E ............................................................................................................................................................1752\nCAPR441W ...........................................................................................................................................................1752\nCAPR442W ...........................................................................................................................................................1752\nCAPR443W ...........................................................................................................................................................1753\nCAPR444W ...........................................................................................................................................................1753\nCAPR445W ...........................................................................................................................................................1753\nCAPR446W ...........................................................................................................................................................1753\nCAPR447W ...........................................................................................................................................................1753\nCAPR448W ...........................................................................................................................................................1753\nCAPR449W ...........................................................................................................................................................1754\nCAPR450W ...........................................................................................................................................................1754\nCAPR451W ...........................................................................................................................................................1754\nCAPR452W ...........................................................................................................................................................1754\nCAPR453W ...........................................................................................................................................................1754\nCAPR499E ............................................................................................................................................................1754\nCAPU001E ............................................................................................................................................................1754\nCAPU002E ............................................................................................................................................................1755\nCAPU003E ............................................................................................................................................................1755\nCAPU004E ............................................................................................................................................................1755\nCAPU005E ............................................................................................................................................................1755", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ddda59da63da-1", "text": "CAPU005E ............................................................................................................................................................1755\nCAPU006E ............................................................................................................................................................1755\nCAPU007E ............................................................................................................................................................1755\nCAPU008E ............................................................................................................................................................1756\nCAPU009E ............................................................................................................................................................1756\nCAPU010E ............................................................................................................................................................1756\n 52", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b5b23933fc1c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPU011W............................................................................................................................................................1756\nCAPU012W ...........................................................................................................................................................1756\nCAPU013W ...........................................................................................................................................................1756\nCAPU014E ............................................................................................................................................................1756\nCAPU122E ............................................................................................................................................................1757\nCAPU301E ............................................................................................................................................................1757\nCAPU302E ............................................................................................................................................................1757\nCAPU303E ............................................................................................................................................................1757\nCAPU304E ............................................................................................................................................................1757\nCAPU305E ............................................................................................................................................................1758\nCAPU306E ............................................................................................................................................................1758\nCAPU308I ..............................................................................................................................................................1758\nCAPU309E ............................................................................................................................................................1758\nCAPU310W ...........................................................................................................................................................1760\nCAPU311W............................................................................................................................................................1760\nCAPU312I ..............................................................................................................................................................1760\nCAPU313E ............................................................................................................................................................1760\nCAPU399E ............................................................................................................................................................1761\nCAPU400I ..............................................................................................................................................................1761\nCAPU401I ..............................................................................................................................................................1761\nCAPU402I ..............................................................................................................................................................1761\nCAPU502E ............................................................................................................................................................1762\nCAPU307E ............................................................................................................................................................1762\nCAPHC001I ...........................................................................................................................................................1762\nCAPHC001W .........................................................................................................................................................1762\nSymDump REST API Messages ...............................................................................................................................1762\nCAVHR01E...........................................................................................................................................................1763\nCAVHR03E............................................................................................................................................................1763\nCAVHR04E............................................................................................................................................................1763\nCAVHR05E............................................................................................................................................................1763\nCAVHR06E............................................................................................................................................................1763\nCAVHR07E............................................................................................................................................................1763\nCAVHR08I..............................................................................................................................................................1764\nCAVHR09E............................................................................................................................................................1764", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b5b23933fc1c-1", "text": "CAVHR09E............................................................................................................................................................1764\nCAVHR10I..............................................................................................................................................................1764\nCAVHR11E............................................................................................................................................................1764\nCAVHR12I..............................................................................................................................................................1764\nCAVHR13E............................................................................................................................................................1765\nCAVHR14I..............................................................................................................................................................1765\nCAVHR15E............................................................................................................................................................1765\n 53", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cf53b55b327a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAVHR16E............................................................................................................................................................1765\nCAVHR17E............................................................................................................................................................1765\nCommon Runtime Messages ....................................................................................................................................1765\nDynamic Symbolic Support Messages ....................................................................................................................1767\nCAIN5900I .............................................................................................................................................................1767\nCAIN5903E ............................................................................................................................................................1767\nCAIN5903E0 ..........................................................................................................................................................1767\nCAIN5904I .............................................................................................................................................................1767\nCAIN5905E ............................................................................................................................................................1768\nCAIN5905E0 ..........................................................................................................................................................1768\nCAIN5905E1 ..........................................................................................................................................................1768\nCAIN5905E2 ..........................................................................................................................................................1768\nCAIN5907E ............................................................................................................................................................1768\nCAIN5908W ...........................................................................................................................................................1769\nCAIN5909I .............................................................................................................................................................1769\nCAIN5913I .............................................................................................................................................................1769\nCAIN5930I .............................................................................................................................................................1769\nCAIN5950I .............................................................................................................................................................1769\nCAIN5970W ...........................................................................................................................................................1770\nCAIN5980E ............................................................................................................................................................1770\nCAIN5980E0 ..........................................................................................................................................................1770\nCAIN5990I .............................................................................................................................................................1770\nCAIN5990I0 ...........................................................................................................................................................1770\nCAIN5991W ...........................................................................................................................................................1770\nCAIN5995E ............................................................................................................................................................1771\nCAIN6000E ............................................................................................................................................................1771\nCAIN6000W ...........................................................................................................................................................1771\nCAIN6010W ...........................................................................................................................................................1771\nCAIN6020W ...........................................................................................................................................................1771\nCAIN6070E ............................................................................................................................................................1772\nCAIN7000W ...........................................................................................................................................................1772\nCAIN7010I .............................................................................................................................................................1772", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cf53b55b327a-1", "text": "CAIN7010I .............................................................................................................................................................1772\nCAIN7020W ...........................................................................................................................................................1772\nCAIN7030W ...........................................................................................................................................................1772\nCAIN8000W ...........................................................................................................................................................1772\nCAIN8010I .............................................................................................................................................................1773\nCAIN8020I .............................................................................................................................................................1773\nCAIN8030W ...........................................................................................................................................................1773\nCAIN8040I .............................................................................................................................................................1773\nCAIN8050I .............................................................................................................................................................1773\n 54", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2547dda22385-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN8060I .............................................................................................................................................................1773\nCAIN8070I .............................................................................................................................................................1774\nCAIN8080I .............................................................................................................................................................1774\nCAIN8090I .............................................................................................................................................................1774\nCAIN8091I .............................................................................................................................................................1774\nCAIN8092I .............................................................................................................................................................1774\nCAIN8093I .............................................................................................................................................................1774\nCAIN8094I .............................................................................................................................................................1775\nCAIN8095I .............................................................................................................................................................1775\nCAIN8096I .............................................................................................................................................................1775\nCAIN8097I .............................................................................................................................................................1775\nCAIN8098W ...........................................................................................................................................................1775\nCAIN8100I .............................................................................................................................................................1776\nCAIN8100I0 ...........................................................................................................................................................1776\nCAIN8110I.............................................................................................................................................................1776\nCAIN8120I .............................................................................................................................................................1776\nCAIN8120I0 ...........................................................................................................................................................1776\nCAIN8130E ............................................................................................................................................................1776\nCAIN8140W ...........................................................................................................................................................1777\nCAIN8150I .............................................................................................................................................................1777\nCAIN8160I .............................................................................................................................................................1777\nCAIN8170I .............................................................................................................................................................1777\nCAIN8180I .............................................................................................................................................................1777\nCAIN8190I .............................................................................................................................................................1777\nCAIN8200I .............................................................................................................................................................1778\nCAIN8210I .............................................................................................................................................................1778\nCAIN8230I .............................................................................................................................................................1778\nCAIN8240E ............................................................................................................................................................1778\nCAIN8260W ...........................................................................................................................................................1778\nCAIN8270I .............................................................................................................................................................1778\nCAIN8300I .............................................................................................................................................................1779\nCAIN8310I .............................................................................................................................................................1779", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2547dda22385-1", "text": "CAIN8310I .............................................................................................................................................................1779\nCAIN8320I .............................................................................................................................................................1779\nCAIN8330E ............................................................................................................................................................1779\nCAIN8340E ............................................................................................................................................................1779\nCAIN8350W ...........................................................................................................................................................1779\nCAIN8360I .............................................................................................................................................................1780\nCAIN8380I .............................................................................................................................................................1780\nCAIN8390I .............................................................................................................................................................1780\nCAIN8400W ...........................................................................................................................................................1780\n 55", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "96c6f16005c9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN8410I .............................................................................................................................................................1780\nCAIN8410W ...........................................................................................................................................................1780\nSYMP001I ..............................................................................................................................................................1781\nSYMP002I ..............................................................................................................................................................1781\nSYMP003I ..............................................................................................................................................................1781\nSYMP004I ..............................................................................................................................................................1781\nSYMP005I ..............................................................................................................................................................1781\nSYMP006I ..............................................................................................................................................................1781\nSYMP101W ...........................................................................................................................................................1782\nSYMP102W ...........................................................................................................................................................1782\nSYMP103W ...........................................................................................................................................................1782\nSYMP104W ...........................................................................................................................................................1782\nSYMP105W ...........................................................................................................................................................1782\nSYMP106W ...........................................................................................................................................................1783\nSYMP107W ...........................................................................................................................................................1783\nSYMP108W ...........................................................................................................................................................1783\nSYMP110W...........................................................................................................................................................1784\nSYMP111W............................................................................................................................................................1784\nSYMP112W...........................................................................................................................................................1784\nSYMP113W...........................................................................................................................................................1784\nSYMP114W...........................................................................................................................................................1784\nSYMP115W...........................................................................................................................................................1784\nSYMP116W...........................................................................................................................................................1785\nSYMP117W...........................................................................................................................................................1785\nSYMP118W...........................................................................................................................................................1785\nSYMP119W...........................................................................................................................................................1786\nSYMP120W ...........................................................................................................................................................1786\nSYMP121W ...........................................................................................................................................................1786\nSYMP122W ...........................................................................................................................................................1786\nSYMP123W ...........................................................................................................................................................1787\nSYMP124W ...........................................................................................................................................................1787\nSYMP125W ...........................................................................................................................................................1787\nSYMP126W ...........................................................................................................................................................1787\nSYMP182W ...........................................................................................................................................................1787\nSYMP500E ............................................................................................................................................................1788", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "96c6f16005c9-1", "text": "SYMP500E ............................................................................................................................................................1788\nSYMP501E ............................................................................................................................................................1788\nSYMP502E ............................................................................................................................................................1788\nSYMP503E ............................................................................................................................................................1788\nSYMP503E0 ..........................................................................................................................................................1788\nSYMP503E1 ..........................................................................................................................................................1789\n 56", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0a704ce2f295-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSYMP503E2 ..........................................................................................................................................................1789\nSYMP503E3 ..........................................................................................................................................................1789\nSYMP504E ............................................................................................................................................................1789\nSYMP505E ............................................................................................................................................................1789\nSYMP507E ............................................................................................................................................................1789\nSYMP508E ............................................................................................................................................................1790\nSYMP509E ............................................................................................................................................................1790\nSYMP599E ............................................................................................................................................................1790\nSYMP599E0 ..........................................................................................................................................................1790\nSYMP599E1 ..........................................................................................................................................................1790\nSYMP599E2 ..........................................................................................................................................................1790\nSYMP599E3 ..........................................................................................................................................................1791\nSYMP599E4 ..........................................................................................................................................................1791\nSYMP599E5 ..........................................................................................................................................................1791\nSYMP599E6 ..........................................................................................................................................................1791\nSYMP801E ............................................................................................................................................................1791\nSYMP901S ............................................................................................................................................................1792\nSYMP902S ............................................................................................................................................................1792\nSYMP903S ............................................................................................................................................................1792\nSYMP904S ............................................................................................................................................................1792\nSYMP905S ............................................................................................................................................................1793\nSYMP906S ............................................................................................................................................................1793\nSYMP908S ............................................................................................................................................................1793\nSYMP909S ............................................................................................................................................................1793\nSYMP910S ............................................................................................................................................................1793\nSYMP911S............................................................................................................................................................1794\nSYMP912S ............................................................................................................................................................1794\nSYMP916S ............................................................................................................................................................1794\nSYMP917S ............................................................................................................................................................1794\nSYMP919S ............................................................................................................................................................1794\nSYMP920S ............................................................................................................................................................1795\nSYMP921S ............................................................................................................................................................1795\nSYMP922S ............................................................................................................................................................1795\nSYMP923S ............................................................................................................................................................1795", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0a704ce2f295-1", "text": "SYMP923S ............................................................................................................................................................1795\nSYMP924S ............................................................................................................................................................1795\nSYMP925S ............................................................................................................................................................1796\nSYMP926S ............................................................................................................................................................1796\nSYMP999S ............................................................................................................................................................1796\nError Codes .................................................................................................................................................................1796\nWD00 .....................................................................................................................................................................1796\n 57", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1be4cd30ffba-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWD01 .....................................................................................................................................................................1796\nWD02 .....................................................................................................................................................................1796\nWD03 .....................................................................................................................................................................1797\nWD09 .....................................................................................................................................................................1797\nWD12 .....................................................................................................................................................................1797\nWD13 .....................................................................................................................................................................1797\nWD14 .....................................................................................................................................................................1797\nWD15 .....................................................................................................................................................................1798\nWD16 .....................................................................................................................................................................1798\nWD17 .....................................................................................................................................................................1798\nWD18 .....................................................................................................................................................................1798\nWD22 .....................................................................................................................................................................1798\nWD34 .....................................................................................................................................................................1798\nWD45 .....................................................................................................................................................................1799\nWD46 .....................................................................................................................................................................1799\nWD47 .....................................................................................................................................................................1799\nWD48 .....................................................................................................................................................................1799\nWD49 .....................................................................................................................................................................1799\nWD50 .....................................................................................................................................................................1799\nWD51 .....................................................................................................................................................................1800\nWD56 .....................................................................................................................................................................1800\nWD57 .....................................................................................................................................................................1800\nWD62 .....................................................................................................................................................................1800\nWD63 .....................................................................................................................................................................1800\nWD66 .....................................................................................................................................................................1800\nCAWD073I.............................................................................................................................................................1801\nCAWD074I.............................................................................................................................................................1801\nCAWD100I.............................................................................................................................................................1801\nCAWD101I.............................................................................................................................................................1801\nCAWD120I.............................................................................................................................................................1801\nCAWD121I.............................................................................................................................................................1801\nCAWD090W...........................................................................................................................................................1802\nCAWD091W...........................................................................................................................................................1802\nCAWD095W...........................................................................................................................................................1802\nCAWD099W...........................................................................................................................................................1802\nCAWD126W...........................................................................................................................................................1802\nCAWD018E............................................................................................................................................................1802\nCAWD047E............................................................................................................................................................1803\nCAWD022E............................................................................................................................................................1803", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1be4cd30ffba-1", "text": "CAWD022E............................................................................................................................................................1803\nCAWD023E............................................................................................................................................................1803\n 58", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e4e6ee27433f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAWD024E............................................................................................................................................................1803\nCAWD035E............................................................................................................................................................1803\nCAWD039E............................................................................................................................................................1804\nIN25UTIL Program Messages ....................................................................................................................................1804\nUTIL001 .................................................................................................................................................................1804\nUTIL002 .................................................................................................................................................................1804\nUTIL003 .................................................................................................................................................................1804\nUTIL004 .................................................................................................................................................................1804\nUTIL005 .................................................................................................................................................................1805\nUTIL006 .................................................................................................................................................................1805\nUTIL007 .................................................................................................................................................................1805\nUTIL008 .................................................................................................................................................................1805\nUTIL009 .................................................................................................................................................................1805\nUTIL010 .................................................................................................................................................................1805\nUTIL011.................................................................................................................................................................1805\nUTIL012 .................................................................................................................................................................1806\nUTIL047 .................................................................................................................................................................1806\nUTIL048 .................................................................................................................................................................1806\nUTIL049 .................................................................................................................................................................1806\nUTIL050 .................................................................................................................................................................1806\nUTIL051 .................................................................................................................................................................1807\nUTIL052 .................................................................................................................................................................1807\nUTIL053 .................................................................................................................................................................1807\nUTIL054 .................................................................................................................................................................1808\nUTIL055 .................................................................................................................................................................1808\nUTIL056 .................................................................................................................................................................1808\nUTIL057 .................................................................................................................................................................1808\nUTIL058 .................................................................................................................................................................1808\nUTIL059 .................................................................................................................................................................1808\nUTIL060 .................................................................................................................................................................1809\nUTIL061 .................................................................................................................................................................1809\nUTIL062 .................................................................................................................................................................1809\nUTIL063 .................................................................................................................................................................1809\nUTIL064 .................................................................................................................................................................1809\nUTIL065 .................................................................................................................................................................1809\nUTIL066 .................................................................................................................................................................1810\nUTIL067 .................................................................................................................................................................1810\nUTIL068 .................................................................................................................................................................1810\nUTIL070 .................................................................................................................................................................1810\nUTIL071 .................................................................................................................................................................1810\n 59", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0964a5145694-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUTIL072 .................................................................................................................................................................1811\nUTIL073 .................................................................................................................................................................1811\nUTIL074 .................................................................................................................................................................1811\nUTIL075 .................................................................................................................................................................1811\nUTIL076 .................................................................................................................................................................1811\nUTIL077 .................................................................................................................................................................1811\nUTIL078 .................................................................................................................................................................1812\nUTIL079 .................................................................................................................................................................1812\nUTIL080 .................................................................................................................................................................1812\nUTIL094 .................................................................................................................................................................1812\nUTIL101 .................................................................................................................................................................1812\nUTIL102 .................................................................................................................................................................1813\nUTIL103 .................................................................................................................................................................1813\nUTIL100 .................................................................................................................................................................1813\nUTIL104 .................................................................................................................................................................1813\nUTIL105 .................................................................................................................................................................1813\nUTIL106 .................................................................................................................................................................1813\nUTIL107 .................................................................................................................................................................1814\nUTIL108 .................................................................................................................................................................1814\nUTIL109 .................................................................................................................................................................1814\nUTIL110.................................................................................................................................................................1814\nUTIL111..................................................................................................................................................................1814\nUTIL112.................................................................................................................................................................1815\nUTIL113.................................................................................................................................................................1815\nUTIL114.................................................................................................................................................................1815\nUTIL115.................................................................................................................................................................1815\nUTIL116.................................................................................................................................................................1815\nUTIL117.................................................................................................................................................................1815\nUTIL118.................................................................................................................................................................1815\nUTIL119.................................................................................................................................................................1816\nUTIL120 .................................................................................................................................................................1816\nUTIL121 .................................................................................................................................................................1816\nUTIL122 .................................................................................................................................................................1816\nUTIL123 .................................................................................................................................................................1816\nUTIL124 .................................................................................................................................................................1816\nUTIL200 .................................................................................................................................................................1817\nUTIL201 .................................................................................................................................................................1817\nUTIL202 .................................................................................................................................................................1817\nUTIL203 .................................................................................................................................................................1817\nSymbolic Post Processor Program Messages .......................................................................................................1817\n 60", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "964000579297-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSYM002 .................................................................................................................................................................1817\nSYM003 .................................................................................................................................................................1817\nSYM004 .................................................................................................................................................................1818\nSYM005 .................................................................................................................................................................1818\nSYM006 .................................................................................................................................................................1818\nSYM007 .................................................................................................................................................................1818\nSYM008 .................................................................................................................................................................1818\nSYM009 .................................................................................................................................................................1818\nSYM010 .................................................................................................................................................................1819\nSYM011.................................................................................................................................................................1819\nSYM012 .................................................................................................................................................................1819\nSYM013 .................................................................................................................................................................1819\nSYM014 .................................................................................................................................................................1819\nSYM015 .................................................................................................................................................................1819\nSYM016 .................................................................................................................................................................1820\nSYM017 .................................................................................................................................................................1820\nSYM018 .................................................................................................................................................................1820\nSYM019 .................................................................................................................................................................1820\nSYM020 .................................................................................................................................................................1820\nSYM021 .................................................................................................................................................................1820\nSYM022 .................................................................................................................................................................1821\nSYM023 .................................................................................................................................................................1821\nSYM024 .................................................................................................................................................................1821\nSYM025 .................................................................................................................................................................1821\nSYM026 .................................................................................................................................................................1821\nSYM027 .................................................................................................................................................................1821\nSYM028 .................................................................................................................................................................1821\nSYM029 .................................................................................................................................................................1822\nSYM030 .................................................................................................................................................................1822\nSYM031 .................................................................................................................................................................1822\nSYM032 .................................................................................................................................................................1822\nSYM033 .................................................................................................................................................................1822\nSYM034 .................................................................................................................................................................1823\nSYM035 .................................................................................................................................................................1823\nSYM036 .................................................................................................................................................................1823\nSYM038 .................................................................................................................................................................1823\nSYM039 .................................................................................................................................................................1823\nSYM040 .................................................................................................................................................................1824\nSYM042 .................................................................................................................................................................1824\nSYM043 .................................................................................................................................................................1824\n 61", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a3b6250aa3be-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSYM044 .................................................................................................................................................................1824\nSYM045 .................................................................................................................................................................1825\nSYM046 .................................................................................................................................................................1825\nSYM047 .................................................................................................................................................................1825\nSYM048 .................................................................................................................................................................1825\nSYM049 .................................................................................................................................................................1825\nSYM050 .................................................................................................................................................................1825\nSYM051 .................................................................................................................................................................1826\nSYM052 .................................................................................................................................................................1826\nSYM053 .................................................................................................................................................................1826\nSYM054 .................................................................................................................................................................1826\nSYM055 .................................................................................................................................................................1826\nSYM056 .................................................................................................................................................................1826\nSYM057 .................................................................................................................................................................1827\nSYM058 .................................................................................................................................................................1827\nSYM059 .................................................................................................................................................................1827\nSYM070 .................................................................................................................................................................1827\nSYM090 .................................................................................................................................................................1827\nSYM091 .................................................................................................................................................................1827\nSYM092 .................................................................................................................................................................1827\nSYM093 .................................................................................................................................................................1827\nSYM094 .................................................................................................................................................................1827\nSYM095 .................................................................................................................................................................1828\nSYM097 .................................................................................................................................................................1828\nSYM099 .................................................................................................................................................................1828\nSYM960 .................................................................................................................................................................1828\nSYM961 .................................................................................................................................................................1828\nDeployment Messages ...............................................................................................................................................1828\nCAVH100E.............................................................................................................................................................1828\nCAVH101E.............................................................................................................................................................1828\nCAVH102E.............................................................................................................................................................1829\nCAVH103E.............................................................................................................................................................1829\nAdditional Resources ....................................................................................................................1830\nDocumentation Legal Notice ........................................................................................................1831\n 62", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3fa536c5cebf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAnnouncements and News\nNews about your product, conferences, and community events.\nz/OSMF Training - Introduction, Process, and Impact to Existing Customers 200\nAre you responsible for installing, maintaining, configuring, and deploying Broadcom Mainframe products? Check\nout the latest z/OSMF training  from Broadcom Mainframe Education.\nIntroducing the New Broadcom Mainframe Digital Badge for InterTest for CICS\nBroadcom is pleased to announce the availability of the InterTest for CICS - Foundational  digital badge. Earn this\nbadge and showcase your InterTest for CICS skills including using InterTest for CICS in the debugging process.\nTo learn more about other Broadcom product badges, see Product Badges .\n\u2022Chorus Software Manager (CSM) End of Life\nAs part of our ongoing commitment to customer success and to help our customer base achieve their strategic\nbusiness initiatives, we are investing our resources in z/OSMF for software management. We will be discontinuing\ntechnical support for CSM . In accordance with the terms and conditions, guidelines, and parameters of Broadcom\u2019s\nsupport program, which is documented in the Broadcom Software Maintenance Policy Handbook , this announcement\nprovides written notification of End of Life for CSM . This notification means that CSM  will no longer be enhanced and\nmaintenance and technical support, including self-service support, will be discontinued effective June 30, 2023 . For full\ndetails, see the End of Life Announcement.\n\u2022Security Advisories: Security and Integrity Maintenance\nBroadcom  offers Security and Integrity maintenance that addresses a security or integrity exposure. We categorize this\nmaintenance as a \u201cSECINT\u201d or \u201cSecurity or Integrity\u201d fix type using our mainframe software packaging system. This\nmaintenance lets you quickly identify security or integrity maintenance among all published maintenance.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3fa536c5cebf-1", "text": "maintenance lets you quickly identify security or integrity maintenance among all published maintenance.\n\u2013With each Security or Integrity fix, Broadcom  also offers access to Security Advisory articles that include additional\ndetails and context about a security or integrity exposure. Each article details the CVSS score, the CVSS Vector\nString, the affected components, and the CVE numbers, if applicable. This central resource offers self-service\ninformation and an email subscription service to be alerted about new security advisories.\n\u2013To apply Security and Integrity fixes and sign up for our vulnerability subscription service, see Maintain Security and\nIntegrity Fixes  documentation. To review vulnerabilities, see Broadcom \u2019s Security Advisories portal.\n\u2022Mainframe Technical Exchange: October 4-6, 2022\nSave the date! We're bringing virtual technical education sessions, product demos, ideation discussions, and product\nroadmaps directly to you. Join us for this no-cost educational event and connect with peers and experts from across\nthe globe.  Bookmark this page  for current registration and event information.\n 63", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2311c14ea712-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nRelease Information\nIncludes new feature descriptions, product compatibility details, and third-party software agreements.\nThis release notes article explains the key features and details for InterTest and SymDump.\nGOTO Debugging Command for InterTest Batch\nInterTest Batch is enhanced with a new GOTO debugging control command, and a GT line command, to resume program\nexecution until the specified line is reached. This feature, released on 11 September 2022, is included in PTF LU06732\nSupport for New IBM z16 Machine Instructions\nInterTest Batch and InterTest CICS adds support for new IBM z16 machine instructions that are generated when the\ncompile option ARCH(14) is specified for IBM Enterprise COBOL or PL/I. Support is added for the following instructions:\nVCNF, VCFN, VSRP,  VSRPR,VCLFNH, VCLFNL, VUPKZH, VUPKZ, NNPA, VSCHP, VSCSHP, VCSPH,VCLZDP,\nVPKZR, VCRNF, SORTL.\nThis feature, released on 04 August 2022, comprises the following PTFs:\nPTF\nLU06741\nPTF\nLU06742\nPortable Software Instance\nInterTest and SymDump products support installation using the Portable Software Instance (PSWI) from 14 December\n2021. The PSWI is available for download from the Broadcom support pages.\nYou can also use z/OSMF Workflows to configure a software instance. This feature, released on April 22, 2022, is\nincluded in PTF LU05540 .\nSymDump CICS REST API Service\nSymDump  CICS was enhanced to provide a new REST API service. This service provides the following endpoints:\n\u2022LIST\n\u2022DISPLAY\n\u2022LOCK\n\u2022UNLOCK", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2311c14ea712-1", "text": "\u2022LIST\n\u2022DISPLAY\n\u2022LOCK\n\u2022UNLOCK\n\u2022DELETE\n\u2022OPTIONS\nNew SymDump  BATCH REST API Endpoints\nThe SymDump  Batch REST API Service is enhanced with the following new endpoints:\n\u2022Update Report Options\n\u2022Display Report Options\nThe preceding SymDump  CICS and Batch REST API features, released on 12 November 2021, are included in PTFs\nLU03402  and LU03403\n 64", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4054fb8dd8cc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCICS Transaction Server 6.1 (ETP16)\nThe InterTest and SymDump for CICS products now support CICS Transaction Server 6.1. (ETP16)\nNote:  The feature toggle to enable IEP (Instruction Execution Protection) is not currently supported for CICS Transaction\nServer 6.1.\nSupport for CICS Transaction Server 6.1 (ETP16), released on 18 November 2021, is enabled by the following PTFs:\n\u2022PTF LU03473\n\u2022PTF LU03474\n\u2022PTF LU03475\n\u2022PTF LU03476\n\u2022PTF LU03477\n\u2022PTF LU03478\nSymDump Batch REST API Service\nSymDump  Batch was enhanced to provide a new REST API service. This service provides the following endpoints:\n\u2022LIST\n\u2022DISPLAY\n\u2022LOCK\n\u2022UNLOCK\n\u2022DELETE\n\u2022OPTIONS\nThis feature, released on September 2, 2021, is included in PTF LU02175 .\nIntegration with CA SYSVIEW\nInterTest CICS integration with CA SYSVIEW Performance Management lets you see transaction debug session activity\nIn a Debug column on the SYSVIEW screen.\nThis feature, released on January 22, 2021 and included in PTF SO15873 , is available from SYSVIEW 16.\nCICS Transaction Server 5.6\nThe InterTest and SymDump for CICS products now support CICS Transaction Server 5.6.\nSupport for CICS Transaction Server 5.6, released on June 30, 2020, is enabled by the following PTFs:\n\u2022PTF SO13489\n\u2022PTF SO13490\n\u2022PTF SO13491\n\u2022PTF SO13492\n\u2022PTF SO13493\n\u2022PTF SO13578", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4054fb8dd8cc-1", "text": "\u2022PTF SO13492\n\u2022PTF SO13493\n\u2022PTF SO13578\nCross-Release Compatibility for CICS Dumps\nSymDump  for CICS now lets you view dumps that were captured in a different release of CICS.\nFor more information see Performance Considerations .\nThis feature, released on June 8, 2020, comprises the following PTFs:\n 65", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2bd9e43a0c43-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022PTF SO13167\n\u2022PTF SO13168\nRelease 11.0 (GA) Continuous Delivery\nInterTest and SymDump is now Generally Available (GA) and Continuous Delivery (CD). This version, released on\nJanuary 24, 2020, will be enhanced using the CD model, which provides new features and product fixes to you faster with\neasier deployment. For more information, see GA Continuous Delivery Release.\nRelease 11.0.09 (Incremental release 09)\nThis incremental, released on June 28, 2019, comprises the following PTFs:\nPTF SO08883\nfor Common CICS Component (FMID CABAB00)\nPTF SO08884\nfor Common CICS DB2 Component (FMID CABAB01)\nPTF SO08885\nfor SymDump for CICS Component (FMID CABQB00)\nPTF SO08886\nfor InterTest Batch Component (FMID CAMRB00)\nPTF SO08887\nfor SymDump  Batch Component (FMID CARXB00)\nPTF SO08888\nfor Common Symbolic Component (FMID CAVHB00)\nBQLSCRN\nAccess to the SymDump  for CICS Feature \"Last Screen\" can now be controlled using an external security manager.\nBQLSCRN lets the user select the Last Screen display from the Dump Tree.\nLearn More Link\nThe menu screen now includes a link to the Learn More  page of the documentation so that you can access the most up-\nto-date information, videos, and community posts about InterTest and SymDump.\nRelease 11.0.08 (Incremental release 08)\nThis incremental, released on February 15, 2019, comprises the following PTFs:\nPTF SO07315", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2bd9e43a0c43-1", "text": "PTF SO07315\nfor Common CICS Component (FMID CABAB00)\nPTF SO07316\nfor Common CICS DB2 Component (FMID CABAB01)\nPTF SO07317\nfor SymDump  for CICS Component (FMID CABQB00)\nPTF SO07318\nfor Common Symbolic Component (FMID CAVHB00)\nPTF SO07319\nfor InterTest for CICS Component (FMID CCSAB00)\n 66", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "be4040c371cd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCICS Transaction Server 5.5\nThe InterTest for CICS and SymDump  for CICS products now support CICS Transaction Server 5.5.\nRelease 11.0.07 (Incremental release 07)\nThis incremental, released on January 16, 2019, comprises the following PTFs:\nPTF SO06269\nfor Common CICS Component (FMID CABAB00)\nPTF SO06722\nfor Common CICS DB2 Component (FMID CABAB01)\nPTF SO06270\nfor InterTest Batch Component (FMID CAMRB00)\nPTF SO06723\nfor SymDump  Batch Component (FMID CARXB00)\nPTF SO06271\nfor Common Symbolic Component (FMID CAVHB00)\nPTF SO06272\nfor Common Eclipse UI Component (FMID CAVHB01)\nPTF SO06273\nfor InterTest for CICS Component (FMID CCSAB00)\nSecure Connection for GUI Server\nThe InterTest UI does not require a secondary connection to any address space other than the Tomcat server, which\nallows you to fully secure the communication with the server.\nMaintenance\nCurrent maintenance from the previous release 10.0:\nSO04768\n: DB2 STORED PROCEDURES HUNG UP HOLDING SYSZTIOT ENQ\nSO05323\n: INTERTEST CICS WD12 ABEND\nSO05634\n: SAMPLE BIND JCL GETS WARNINGS WITH DB2 V10 AND ABOVE\nSO05396\n: UNEXPECTED ABEND S0C1 WHEN USING UNSTRING COBOL STATEMENT\nRelease 11.0.06 (Incremental release 06)\nThis incremental, released on October 18, 2018,  comprises the following PTFs:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "be4040c371cd-1", "text": "PTF SO05170\nfor Common CICS Component (FMID CABAB00)\nPTF SO05171\nfor Common Symbolic Component (FMID CAVHB00)\nPTF SO05172\nfor InterTest for CICS Component (FMID CCSAB00)\n 67", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "12b181bd64d3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPTF SO05598\nfor Common CICS DB2 Component (FMID CABAB01)\nPTF SO05599\nfor SymDump  for CICS Component (FMID CABQB00)\nMaintenance\nCurrent maintenance from the previous release 10.0:\nSO04705\n: ABEND S0C9 ON DISPLAY OF INDEX OUT OF BOUNDS\nSO04807\n: VBP NOT STOPPING ON MAP FIELD IN COBOL 4.2\nSO03904\n: KEEP WINDOW NOT AUTOMATICALLY DISPLAYED FOR EVALUATE\nSO04023\n: OPTIMIZER POST-PROCESSOR FINISHED WITH SYM026 AND SYM023\nSO04640\n: ABEND 0C4 IN PROGRAM IN25COB2\nSO05074\n: POST-PROCESSOR TERMINATES WITH SYM042\nSO05103\n: ATCV ABEND WHEN CHOOSING OPTION 8 \"WHAT'S NEW?\"\nRelease 11.0.05 (Incremental release 05)\nThis incremental, released on August 21, 2018, comprises the following PTFs:\nPTF SO04582\nfor Common CICS Compoment (FMID CABAB00)\nPTF SO04583\nfor Common CICS DB2 Component (FMID CABAB01)\nPTF SO04584\nfor SymDump  for CICS Component (FMID CABQB00)\nPTF SO04585\nfor Common Symbolic Component (FMID CAVHB00)\nPTF SO04586\nfor InterTest for CICS Component (FMID CCSAB00)\nDWARF Symbolic Support\nThis release contains the first increments towards DWARF symbolic support.\nThis feature is under incremental development, so not all features that are available for PROTSYM are currently available", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "12b181bd64d3-1", "text": "for DWARF. Currently debugging using DWARF is only supported for COBOL programs in InterTest for CICS. For more\ninformation on the limitations, see DWARF Incremental Release State.\nA new parameter, SYMBOLIC, has been added to IN25OPTS which is used to turn on DWARF debugging.\n 68", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "142bc0cdbc36-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nXLDLOAD User Exit\nInterTest for CICS now uses global user exit XLDLOAD.\nRelease 11.0.04 (Incremental release 04)\nThis incremental, released on May 23, 2018, comprises the following PTFs:\nPTF SO01925\nfor Common CICS Component  (FMID CABAB00)\nPTF SO01926\nfor SymDump  for CICS Component (FMID CABQB00)\nPTF SO01927\nfor InterTest Batch Component (FMID CAMRB00)\nPTF SO01928\nfor SymDump  Batch Component (FMID CARXB00)\nPTF SO01929\nfor Common Symbolic Component (FMID CAVHB00)\nPTF SO01930\nfor Common Eclipse UI Component (FMID CAVHB01)\nPTF SO01931\nfor InterTest for CICS Component (FMID CCSAB00)\nARCH(12) Support\nInterTest and SymDump now support the ARCH(12) compile option of the IBM Enterprise COBOL and PL/I compilers.\nInterTest CICS: 6-digit statement numbers\nInterTest and SymDump 6-digit statement numbers even in the CNTL menu.\nMaintenance\nCurrent maintenance from previous release that was released before May 23, 2018:\nSO00391\n: DUPLICATE LET ENTRIES BEING GENERATED\nSO00924\n: ABP BREAKPOINT ON CALLS TO DB2 PROGRAM DSNTIAC\nSO01163\n: ABEND S0C4/AKEA AT X'A8' OF INXXRMIO\nSO01171\n: IMS REGION BECOMES UNRESPONSIVE DURING SYMDUMP PROCESSING\nSO01059\n: TOMCAT SERVER FAILS TO START COMPONENT\nSO01632", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "142bc0cdbc36-1", "text": "SO01059\n: TOMCAT SERVER FAILS TO START COMPONENT\nSO01632\n: ABEND S0C1 IN IN25COB2\nSO01034\n: SYMDUMP CICS CONFIGURATION MENU ABEND\n 69", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5d8158e47814-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSO01614\n, SO01615 : KEEP WINDOW IS NOT WORKING WITH COBOL 6.2\nSO01538, SO01539\n: CAINSRV SHUTDOWN ISSUE\nRelease 11.0.03 (Incremental release 03)\nThis incremental, released on March 12, 2018, comprises the following PTFs:\nPTF SO00796\nfor Common CICS Component  (FMID CABAB00)\nPTF SO00797\nfor InterTest Batch Component (FMID CAMRB00)\nPTF SO00798\nfor Common Symbolic Component (FMID CAVHB00)\nPL/I 5.2 Support\nInterTest and SymDump now support PL/I version 5.2.\nMaintenance\nCurrent maintenance from previous release (released before Mar 05, 2018).\nRelease 11.0.02 (Incremental release 02)\nThis incremental, released on December 21, 2017, comprises the following PTFs:\nPTF RO99718\nfor Common CICS Component  (FMID CABAB00)\nPTF RO99719\nfor SymDump  for CICS Component (FMID CABQB00)\nPTF RO99720\nfor InterTest Batch Component (FMID CAMRB00)\nPTF RO99721\nfor SymDump  Batch Component (FMID CARXB00)\nPTF RO99722\nfor SymDump  Batch DB2 Component (FMID CARXB01)\nPTF RO99723\nfor Common Symbolic Component (FMID CAVHB00)\nPTF RO99724\nfor Common Eclipse UI Component (FMID CAVHB01)\nPTF RO99725\nfor InterTest for CICS Component (FMID CCSAB00)\nVisual Debugger", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5d8158e47814-1", "text": "for InterTest for CICS Component (FMID CCSAB00)\nVisual Debugger\nInterTest Visual Debugger is a visual representation of a CICS COBOL transaction or COBOL batch program. For more\ninformation, see Visual Debugger.\nSee how InterTest Visual Debugger visually represents a COBOL application and simplifies the application analysis:\n 70", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "92b6c1a1b2af-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nz/OS v2.3 Support\nInterTest and SymDump now support z/OS version 2.3.\nCOBOL V6.2 Support\nInterTest and SymDump now support IBM Enterprise COBOL V6.2.\nRelease 11.0.01 (Incremental release 01)\nThis incremental, released on August 31, 2017, comprises the following PTFs:\nPTF RO97425\nfor Common CICS Component  (FMID CABAB00)\nPTF RO97426\nfor Common CICS DB2 Component  (FMID CABAB01)\nPTF RO97427\nfor SymDump  for CICS Component  (FMID CABQB00)\nPTF RO97428\nfor InterTest Batch Component  (FMID CAMRB00)\nPTF RO97429\nfor SymDump  Batch Component (FMID CARXB00)\nPTF RO97430\nfor SymDump  Batch DB2 Component (FMID CARXB01)\nPTF RO97431\nfor Common Symbolic Component (FMID CAVHB00)\nPTF RO97432\nfor Common Eclipse UI Component (FMID CAVHB01)\nPTF RO97433\nfor InterTest for CICS Component (FMID CCSAB00)\nGA release of CICS Transaction Server 5.4\nThe InterTest for CICS and SymDump  for CICS products now support the GA release of CICS Transaction Server 5.4.\nDB2 12.1 support\nInterTest and SymDump products now support version 12.1 of DB2 for z/OS.\nRelease 11.0.00 (Base)\nThis base version 11.0.00, released on May 26, 2017, contains the following improvements:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "92b6c1a1b2af-1", "text": "Batch Link Scheduling Table Configuration Change\nThe user replaceable configuration module CAMRSTBZ has been removed. The two options SIZE and SYSPLEX\nformerly specified in CAMRSTBZ are now configured in CAVHCONF as SCHTBSIZE and IBSYSPLEX.\nOptions PRTLIB and PRTLHCT were moved from the CAOUDFRX module to CAOETABL.\nIBM PL/I 5.1 support\nThe InterTest and SymDump products now support the debugging and fault analysis diagnostics for PL/I 5.1 programs.\n 71", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8498dc78849b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nExternal Security\nInterTest Batch now supports External Security for mismatched symbolic members.\nVector and Floating-Point Registers\nSymDump  for CICS and SymDump  Batch reports contain vector registers when Vector facility is installed (from z13\nmachines on) and floating-point registers are added for SymDump  for CICS when Vector facility is off.\nCICS Transaction Server 5.4\nThe InterTest for CICS and SymDump  for CICS products now support CICS Transaction Server 5.4.\nGA Continuous Delivery Release\nThe Continuous Delivery model provides product features and fixes to you faster.\nWe are pleased to present you with the Generally Available (GA) Continuous Delivery (CD) release of InterTest and\nSymDump . This version is enhanced using the CD model, which provides new features and product fixes to you faster\nwith easier deployment.\nIn the CD release model:\n\u2022Enhancements are delivered in the maintenance service stream as feature PTFs. New product features and fixes are\nno longer bundled together.\n\u2022Enhancements are delivered disabled where possible to give you more control over when and how the features\nare implemented. With new features disabled, you control when to make the new features available for use in your\nenvironment. Explicit action is required to enable the feature.\n\u2022Product validation programs are available so that you can influence feature design and test new features and\ncapabilities before they are made generally available (GA). For more information about these programs, go to https://\nvalidate.broadcom.com  or contact your product manager.\n\u2022Individual product fixes are provided when needed, separate from product features. You can apply product fixes\nwithout enabling new features, which limits exposure to more features being applied in a production environment.\nThese changes can limit SMP/E dependencies that were forced previously by bundling features and fixes together.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8498dc78849b-1", "text": "These changes can limit SMP/E dependencies that were forced previously by bundling features and fixes together.\nAfter full integration and regression testing with other Broadcom mainframe products, the enhancement and product\nfixes are added into the Broadcom Recommended Service for z/OS  (CARS ), ensuring product quality and the integrity\nof your environment. CARS  is an important part of a good preventive maintenance philosophy that lets you develop and\nimplement a proactive maintenance strategy in which you apply preventive maintenance on a regular schedule.\nIMPORTANT\nUse SMP/E Internet Service Retrieval  to acquire product maintenance. This service uses the IBM SMP/E\nRECEIVE ORDER command and can reduce hours of maintenance time to just minutes. You can acquire\nmaintenance on demand or can schedule an SMP/E job to run regularly, which eliminates time-consuming fix\nsearches and the need to select maintenance manually through the Broadcom Support Portal.\nSMP/E Internet Service Retrieval Maintenance\nAs part of our ongoing Mainframe strategy, Broadcom  now offers a new maintenance delivery service: SMP/E Internet\nService Retrieval .\nThis delivery method uses the IBM SMP/E RECEIVE ORDER command to acquire Broadcom  Mainframe product\nmaintenance over the internet by securely submitting an order for PTFs and HOLDDATA to a remote Broadcom  server.\nThis service can reduce maintenance time from hours to minutes, and allow your system programmers to be more\nproductive and to focus on higher value tasks.\nSMP/E Internet Service Retrieval :\n 72", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7bad04907f47-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Eliminates time-consuming fix searches and the need to select maintenance manually through Broadcom Support\nPortal\n\u2022Automates delivery of Broadcom  maintenance directly to your mainframe\n\u2022Fulfills orders based on the status of your SMP/E environments\n\u2022Enables scheduling of maintenance downloads\n\u2022Facilitates an easier installation of Broadcom  Recommended and Preventive service\nWith the SMP/E Internet Service Retrieval , you can acquire maintenance on demand or can schedule an SMP/E job to run\nregularly. The Broadcom  Order server supports the IBM-documented order types, which include: ALL, APARS, CRITICAL,\nHOLDDATA, PTFS, and RECOMMENDED.\nIf you are an existing CSM  customer, you can also use this new service to download maintenance and dramatically\nreduce the time needed to download PTFs.\nTo get started, review the SMP/E Internet Service Retrieval  Documentation .\nEclipse Plugin Compatibility\nUse the information in this article to identify which version of the Eclipse plug-in is compatible with your Testing Tools\nServer version.\nCurrent versions of the InterTest and SymDump plug-ins are available on the public site at the following URLs:\n\u2022https://plugins.packages.broadcom.com/artifactory/ca-plugins/intertest-plugin/\n\u2022https://plugins.packages.broadcom.com/artifactory/ca-plugins/symdump-plugin/\nThe following table provides an easy reference point to ensure that you download and install the compatible version of the\nInterTest and SymDump plug-ins for your set-up:\nNOTE\nInterTest plug-in v11.1.1 and higher ensure compatibility with Java 11.\nServer Version InterTest SymDump\n11.1.x 11.1.x 11.0.x\n11.2.0\nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7bad04907f47-1", "text": "11.2.0\nNOTE\n\u2022If necessary, older versions for the InterTest and SymDump plug-ins are delivered with PTFs and can be\ndownloaded from the update site at http://  host:port/software\n\u2022Contact your system programmer to get the host and port of the Testing Tools Server.\n\u2022The correct version for your system is determined automatically.\nFor more information, see Installing the Eclipse User Interface .\nPortfolio Simplification\nInterTest Batch now includes the following features and capabilities.\n 73", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "57cce71bbf6d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterTest Batch\nInterTest Batch for PL/I Provides the capability to symbolically debug programs written in\nthe IBM Enterprise PL/I language.\nInterTest Batch for IMS Provides the ability to debug COBOL, PL/I, or Assembler\nprograms that execute as IMS MPP or BMP programs.\nInterTest for CICS zOS\nInterTest for CICS zOS now includes the following features and capabilities.\nInterTest for CICS Option for PL/I This option provides the capability to symbolically debug programs\nwritten in the IBM Enterprise PL/I language.\nInterTest for CICS z/VSE\nInterTest for CICS z/VSE now includes the following features and capabilities.\nInterTest for CICS Option for PL/I Provides the capability to symbolically debug programs written in\nthe IBM Enterprise PL/I language.\nNext Steps\nTo use these options, go to your usual download facility (for example, Broadcom Support Online ) and download the\nadditional component  features from the drop-down list. If one of the downloads requires an LMP key, follow your usual\nprocess to acquire the key.\nRelease Comparison\nThis article compares the key features in all active releases of InterTest and SymDump  products.\nInterTest Batch\nKey Features Version 11.0 Version 10.0 Release 9.1\nBatch Link Scheduling Table\nConfiguration Changeyes no no\nExternal Security yes yes no\nVector and Floating-Point\nRegistersyes yes no\nSet Unconditional \"After\"\nBreakpointsyes yes no\nInvoke File Master Plus  from the\nBatch Link Facilityyes yes no\nSingle Pax File and Installation yes yes no\nIBM Enterprise COBOL and PL/I\nCompiler ARCH(11) Supportyes yes no\nRecord a Monitoring Session for\nLater Reuseyes yes no\n 74", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d6d13ba4b7ed-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nExternal Security Support for\nSymbolic Filesyes yes no\nIBM Enterprise COBOL 6.2\nsupportyes yes no\nDebugging on Foreign LPARs yes yes yes\nSharing Schedules Between\nLPARs in a SYSPLEXyes yes yes\nSupport for Multiple Program\nVersions in a Single PROTSYMyes yes yes\nPROTSYM Space Utilization\nMonitoringyes yes yes\nIBM Enterprise COBOL 6.1\nSupportyes yes yes\nIBM Enterprise COBOL 5.2\nSupportyes yes yes\nIBM PL/I 5.1 support yes yes yes\nUnicode Support yes yes yes\nInterTest for CICS\nKey Features Version 11.0 Version 10.0 Release 9.1\nyes yes no\nVector and Floating-Point\nRegistersyes yes no\nSET and DISPLAY Commands\nSupport COBOL Numeric Index\nValuesyes yes no\nSet Unconditional \"After\"\nBreakpointsyes yes no\nSingle Pax File and Installation yes yes no\nCICS Transaction Server 6.1 yes yes no\nCICS Transaction Server 5.6 yes yes no\nCICS Transaction Server 5.5 yes yes no\nCICS Transaction Server 5.4 yes yes no\nCICS Transaction Server 5.3 yes yes no\nIBM Enterprise COBOL and PL/I\nCompiler ARCH(11) Supportyes yes no\nRecord a Monitoring Session for\nLater Reuseyes yes no\nExternal Security Support for\nSymbolic Filesyes yes no\n 75", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "baa27af8ec93-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIBM Enterprise COBOL 6.2\nsupportyes yes no\nComposite Support\nImprovementsyes yes yes\nSupport for Multiple Program\nVersions in a Single PROTSYMyes yes yes\nPROTSYM Space Utilization\nMonitoringyes yes yes\nIBM Enterprise COBOL 6.1\nsupportyes yes yes\nIBM Enterprise COBOL 5.2\nSupportyes yes yes\nCICS Transaction Server 5.2 yes yes yes\nIBM PL/I 5.1 support yes yes yes\nSymDump  Batch\nKey Features Version 11.0 Version 10.0 Release 9.1\nVector and Floating-Point\nRegistersyes no no\nSet Unconditional \"After\"\nBreakpointsyes yes no\nSingle Pax File and Installation yes yes no\nFilter Abend Program Names\nfrom the Dump Indexyes yes no\nRemoval of MCHAR, PCHAR,\nand RCHAR Keywordsyes yes no\nExternal Security Support for\nSymbolic Filesyes yes no\nIBM Enterprise COBOL 6.2\nsupportyes yes no\nSupport for Multiple Program\nVersions in a Single PROTSYMyes yes yes\nPROTSYM Space Utilization\nMonitoringyes yes yes\nIBM Enterprise COBOL 6.1\nsupportyes yes yes\nIBM Enterprise COBOL 5.2\nSupportyes yes yes\nIBM PL/I 5.1 support yes yes yes\n 76", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dc0cb1806c60-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSymDump  for CICS\nKey Features Version 11.0 Version 10.0 Release 9.1\nVector and Floating-Point\nRegistersyes no no\nSingle Pax File and Installation yes yes no\nCICS Transaction Server 6.1 yes yes no\nCICS Transaction Server 5.6 yes yes no\nCICS Transaction Server 5.5 yes yes no\nCICS Transaction Server 5.4 yes yes no\nCICS Transaction Server 5.3 yes yes no\nExternal Security Support for\nSymbolic Filesyes yes no\nIBM Enterprise COBOL 6.2\nsupportyes yes no\nSupport for Multiple Program\nVersions in a Single PROTSYMyes yes yes\nPROTSYM Space Utilization\nMonitoringyes yes yes\nDump Capture Performance\nImprovementsyes yes yes\nSource Listing Display\nEnhancementyes yes yes\nBatch Dump Print Program\nIN25PDMP Changesyes yes yes\nIBM Enterprise COBOL 6.1\nsupportyes yes yes\nIBM Enterprise COBOL 5.2\nSupportyes yes yes\nCICS Transaction Server 5.2 yes yes yes\nIBM PL/I 5.1 support yes yes yes\nThird Party Software Requirements\nThis article defines the third-party software requirements that apply to this release.\nThe following copyright statements and licenses apply to open source software (\u201cOSS\u201d) distributed with the InterTest and\nSymDump  product (the \u201cLicensed Product\u201d). The Licensed Product does not necessarily use all the OSS referred to below\nand may also only use portions of a given OSS component.\nTo the extent required under an applicable open source license, Broadcom Inc. and/or its corporate affiliates (\u201cBroadcom\u201d)\nwill make source code available for applicable OSS upon request. Please send an inquiry to opensource@broadcom.com", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dc0cb1806c60-1", "text": "including your name, address, the product name and version, operating system, and the place of purchase.\nTo the extent the Licensed Product includes OSS, the OSS is typically not owned by Broadcom. THE OSS IS PROVIDED\nAS IS WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING,\nWITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR\n 77", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "290e18f36349-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPURPOSE. To the full extent permitted under applicable law, Broadcom disclaims all warranties and liability arising from\nor related to any use of the OSS.\nTo the extent the Licensed Product includes OSS licensed under the GNU General Public License (\u201cGPL\u201d) or the GNU\nLesser General Public License (\u201cLGPL\u201d), the use, copying, distribution and modification of the GPL OSS or LGPL OSS is\ngoverned, respectively, by the GPL or LGPL. A copy of the GPL or LGPL license may be found with the applicable OSS.\nAdditionally, a copy of the GPL License or LGPL License can be found at https://www.gnu.org/licenses or obtained by\nwriting to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.\nTo view each license and copyright notice, download the attached zip file .\nProduct Accessibility Features\nBroadcom  is committed to ensuring that all customers can successfully use our products and supporting documentation\nto accomplish business tasks. Enable Windows accessibility mode to optimize contrast in the user interface and activate a\nscreen reader for those users who need assistance.\nNOTE\n InterTest and SymDump accessibility features are best when used with Internet Explorer 10 and higher, and\nwith the Job Access With Speech (JAWS) screen reader.\nSystem Accessibility Inheritance\nInterTest and SymDump inherits accessibility enhancements from Windows-based and Macintosh-based environments in\nthe following areas:\nMouse\nYou can use the following options to make your mouse faster and easier to use:\nClick Speed\nChoose how fast to click the mouse button to make a selection.\nClick Lock\nHighlight or drag without holding down the mouse button.\nReverse Action\nReverse the functions controlled by the left and right mouse keys.\nBlink Rate\nChoose how fast the cursor blinks or if it blinks at all.\nPointer Options", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "290e18f36349-1", "text": "Choose how fast the cursor blinks or if it blinks at all.\nPointer Options\nDo the following:\n\u2022Hide the pointer while typing\n\u2022Show the location of the pointer\n\u2022Set the speed that the pointer moves on the screen\n\u2022Choose the pointer's size and color for increased visibility\n\u2022Move the pointer to a default location in a dialog box\nKeyboard\nYou can make the following keyboard adjustments:\nRepeat Rate\nSet how quickly a character repeats when a key is pressed.\n 78", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "20e64605ef10-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTones\nHear tones when pressing certain keys.\nSticky Keys\nUse keyboard shortcuts or type capital letters without needing to press more than one key at once.\nSound\nUse sound as an alternative to visual information or to make computer sounds easier to hear or distinguish by adjusting\nthe following options:\nVolume\nTurn the computer sound up or down.\nText-to-Speech\nHear command options and text read aloud.\nWarnings\nDisplay visual warnings.\nNotices\nProvides you aural or visual cues when accessibility features are enabled or disabled.\nSchemes\nAssociate computer sounds with specific system events.\nCaptions\nDisplay captions for speech and sounds.\nDisplay\nTo increase visibility on your computer display, you can adjust the following options:\nFont style, color, and size of items\nChoose font color, size, and other visual combinations.\nScreen resolution\nChange the pixel count to enlarge objects on the screen.\nCursor width and blink rate\nMake the cursor easier to find or minimize its blinking.\nIcon size\nMake icons larger for visibility or smaller for increased screen space.\nHigh contrast schemes\nSelect color combinations that are easier to see.\nNOTE\n This information applies to Windows-based and Macintosh-based applications. Java applications run on many\nhost operating systems, some of which already have assistive technologies available to them. For these existing\nassistive technologies to provide access to programs written in JPL, they need a bridge between themselves\nin their native environments and the Java Accessibility support that is available from within the Java Virtual\nMachine (Java VM). This bridge has one end in the Java VM and the other on the native operating systems, so it\nwill be slightly different for each platform it bridges to. Oracle is currently developing both the JPL and the Win32\nsides of this bridge.\n 79", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d71415db4f6b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nConfigure Accessibility in the GUI\nFollow these steps:\n1.Go to Window, Preferences , and expand General, Editors, Text Editors and click  Accessibility .\nThe Accessibility dialog opens. \n2.Select the appropriate Accessibility check boxes:\n\u2013Use custom caret\nDefault : Selected\n\u2013Enable thick caret\nDefault : Selected\n\u2013Use characters to show changes in vertical rulerDefault:  Cleared\n\u2013Use saturated colors in overview ruler Default:  Cleared \n3.To save your changes, click Apply  or OK.\nKeyboard Shortcuts\nIn the InterTest and SymDump GUI you can customize and create shortcut for many program commands. The following\ntable shows the default keyboard shortcuts for actions in the InterTest and SymDump GUI.\nFile Command Shortcuts\nCommand Binding Available When\nProperties Alt+Enter In Windows\nClose Ctrl+F4 In Windows\nRename F2 In Windows\nNew menu Alt+Shift+N In Windows\nClose All Ctrl+Shift+W In Windows\nPrint Ctrl+P In Windows\nNew Ctrl+N In Windows\nClose Ctrl+W In Windows\nSave Ctrl+S In Windows\nClose All Ctrl+Shift+F4 In Windows\nRefresh F5 In Windows\nSave All Ctrl+Shift+S In Windows\nEdit Command Shortcuts\nCommand Binding Available When\nFind Next Ctrl+K Editing Text\nPaste Ctrl+V In Dialogs and Windows\nPaste Shift+Insert In Dialogs and Windows\nCopy Ctrl+C In Dialogs and Windows\nDelete Delete In Windows\nCopy Ctrl+Insert In Dialogs and Windows\nCut Ctrl+X In Dialogs and Windows\nIncremental Find Reverse Ctrl+Shift+J Editing Text\n 80", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "af8ee068f2f0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFind Previous Ctrl+Shift+K Editing Text\nIncremental Find Ctrl+J Editing Text\nCut Shift+Delete In Dialogs and Windows\nQuick Diff Toggle Ctrl+Shift+Q Editing Text\nToggle Insert Mode Ctrl+Shift+Insert Editing Text\nContent Assist Ctrl+Space In Dialogs and Windows\nSelect All Ctrl+A In Dialogs and Windows\nToggle Block Selection Alt+Shift+A Editing Text\nContext Information Ctrl+Shift+Space In Dialogs and Windows\nFind and Replace Ctrl+F In Windows\nRedo Ctrl+Y In Dialogs and Windows\nUndo Ctrl+Z In Dialogs and Windows\nQuick Fix Ctrl+1 In Dialogs and Windows\nWord Completion Alt+/ Editing Text\nNavigation Command Shortcuts\nCommand Binding Available When\nPrevious Ctrl+, In Windows\nCollapse All Ctrl+Shift+Numpad_Divide In Windows\nShow In... Alt+Shift+W In Windows\nNext Page Alt+F7 In Windows\nLast Edit Location Ctrl+Q In Windows\nPrevious Sub-Tab Alt+PageUp In Dialogs and Windows\nGo to Line Ctrl+L Editing Text\nPrevious Page Alt+Shift+F7 In Windows\nNext Ctrl+. In Windows\nNext Sub-Tab Alt+PageDown In Dialogs and Windows\nExpand All Ctrl+Shift+Numpad_Multiply In Windows\nForward History Alt+Right In Windows\nText Editing Command Shortcuts\nCommand Binding Available When\nTo Upper Case Ctrl+Shift+X Editing Text\nSelect Next Word Ctrl+Shift+Right Editing Text\nJoin Lines Ctrl+Alt+J Editing Text\nSelect Line End Shift+End Editing Text\nLine Start Home Editing Text\nText End Ctrl+End Editing Text\nCollapse All Ctrl+Shift+Numpad_Divide Editing Text\nText Start Ctrl+Home Editing Text\n 81", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4500c03b4b29-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nToggle Overwrite Insert Editing Text\nSelect Line Start Shift+Home Editing Text\nInsert Line Above Current Line Ctrl+Shift+Enter Editing Text\nNext Word Ctrl+Right Editing Text\nReset Structure Ctrl+Shift+Numpad_Multiply Editing Text\nShow Tooltip Description F2 Editing Text\nExpand All Ctrl+Numpad_Multiply Editing Text\nDelete Line Ctrl+D Editing Text\nDuplicate Lines Ctrl+Alt+Up Editing Text\nDelete Previous Word Ctrl+Backspace Editing Text\nMove Lines Up Alt+Up Editing Text\nCopy Lines Ctrl+Alt+Down Editing Text\nDelete to End of Line Ctrl+Shift+Delete Editing Text\nTo Lower Case Ctrl+Shift+Y Editing Text\nInsert Line Below Current Line Shift+Enter Editing Text\nToggle Folding Ctrl+Numpad_Divide Editing Text\nMove Lines Down Alt+Down Editing Text\nSelect Previous Word Ctrl+Shift+Left Editing Text\nPrevious Word Ctrl+Left Editing Text\nLine End End Editing Text\nScroll Line Up Ctrl+Up Editing Text\nExpand Ctrl+Numpad_Add Editing Text\nDelete Next Word Ctrl+Delete Editing Text\nScroll Line Down Ctrl+Down Editing Text\nViews Command Shortcuts\nCommand Binding Available When\nShow View (Error Log) Alt+Shift+Q, L In Windows\nShow View Alt+Shift+Q, Q In Windows\nShow View (Outline) Alt+Shift+Q, O In Windows\nShow View (Console) Alt+Shift+Q, C In Windows\nShow View (Cheat Sheets) Alt+Shift+Q, H In Windows\nWindow Command Shortcuts\nCommand Binding Available When\nNext Editor Ctrl+F6 In Windows\nShow Ruler Context Menu Ctrl+F10 Editing Text\nQuick Switch Editor Ctrl+E In Windows\nQuick Access Ctrl+3 In Windows\nSwitch to Editor Ctrl+Shift+E In Windows\n 82", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "77fb34f547c1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nActivate Editor F12 In Windows\nMaximize Active View or Editor Ctrl+M In Windows\nShow Key Assist Ctrl+Shift+L In Dialogs and Windows\nPrevious View Ctrl+Shift+F7 In Windows\nShow Contributing Plug-in Alt+Shift+F3 In Dialogs and Windows\nNext View Ctrl+F7 In Windows\nPrevious Editor Ctrl+Shift+F6 In Windows\nShow View Menu Ctrl+F10 In Dialogs and Windows\nShow System Menu Alt+- In Windows\nProduct Names and Abbreviations\nInterTest and SymDump documentation includes references to the following products and abbreviations:\n\u2022InterTest and SymDump (InterTest, SymDump)\n\u2022ACF2\n\u2022Bind Analyzer\n\u2022Chorus Software Manager (CSM)\n\u2022Common Components and Services\n\u2022Datacom/DB\n\u2022Endevor\n\u2022File Master Plus\n\u2022IDMS\n\u2022JCLChec\n\u2022Librarian\n\u2022Mainframe Application Tuner (MAT)\n\u2022Netman\n\u2022NSM\n\u2022Optimizer/II\n\u2022Panexec\n\u2022Panvalet\n\u2022Realia II Workbench\n\u2022Roscoe\n\u2022Top Secret\n\u2022Verify\n 83", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "63b9d4a46df1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInstalling\nStandard SMP/E installation and maintenance best practices are used to install and maintain Broadcom  mainframe z/OS\nproducts. The installation process includes all the tasks that are typically performed by a systems programmer to acquire\nthe products and make them ready for use in a production environment.\nYou can install Broadcom  mainframe product software using IBM z/OSMF, CSM , or native SMP/E batch processing.\nNOTE\nz/OSMF installation is not available for every product.\nz/OSMF and CSM  are intuitive web-based tools that automate and simplify many installation activities on z/OS systems.\nThese applications also make obtaining and applying corrective, preventive, and recommended maintenance easier.\nThe following graphic provides a high-level overview of the installation process for Broadcom  mainframe products:\n 84", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c81bfbd6d110-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThese steps are described in the following procedure:\n1.Prepare for the installation by reviewing best practices and verifying that the software, hardware, security, and other\ninstallation requirements have been met.\n2.Acquire the product software using one of the following methods:\n\u2013From Broadcom Support , download a z/OSMF (filename.zOSMF.pax.Z) or classic SMP/E JCL (filename.pax.Z)\npackage. Only one can be selected.\nNOTE\nIf a z/OSMF package is not available, select the SMP/E JCL package. A z/OSMF package is not available\nfor all products.\n\u2013From CSM , select a classic SMP/E JCL package from the product list. You cannot acquire a z/OSMF portable\nsoftware instance from CSM .\n3.Perform an SMP/E installation to install the product software using one of the following methods:\n 85", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "80f22660498d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2013If you downloaded a z/OSMF package from Broadcom Support , install using z/OSMF Deployments.\n\u2013If you downloaded a classic SMP/E JCL package from Broadcom Support , use either  of the following options:\n\u2022Install using native SMP/E JCL\n\u2022Install using CSM\n\u2013If you downloaded a classic SMP/E JCL package from CSM , start the installation process from the SMP/E\nEnvironments  tab in CSM .\n4.Install maintenance using z/OSMF Software Update, SMP/E JCL, or CSM .\nNOTE\nUse SMP/E Internet Service Retrieval  to download and receive maintenance. This service lets you acquire\nmaintenance on demand and to schedule an SMP/E job to run as needed. The SMP/E Internet Service\nRetrieval  can reduce hours of maintenance time to just minutes, making your system programmers more\nproductive and allowing them to focus on higher value tasks. Migrate existing CSIs to z/OSMF and use z/\nOSMF Software Update to manage software updates.\n5.Finalize the installation:\n\u2013Configure your product.\n\u2013Deploy your product.\nFor these tasks, use the methods that your product supports and in the preferred sequence per your site.\nPrepare for Installation\nTo prepare for an installation or upgrade, we recommend that your team use our Installation Checklist or Upgrade\nChecklist. Upon completion of the installation, use the Day 1 Task Checklist under Getting Started. Doing so can help you\nstart using the product and can help you get acclimated to the customer documentation as well.\nTo install your product, we recommend that you understand:\n\u2022JCL\n\u2022TSO/ISPF\n\u2022Your organization IT environment, enterprise structure, and region structure\n\u2022z/OS environment and installing software in this environment\n\u2022z/OS UNIX System Services", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "80f22660498d-1", "text": "\u2022z/OS environment and installing software in this environment\n\u2022z/OS UNIX System Services\nConsult with the following personnel, as required:\n\u2022Security Administrator for access\n\u2022Storage Administrator for DASD allocations\n\u2022Systems Programmer for z/OS and VTAM definitions\nTIP\nIf you plan to use z/OSMF to install or configure your product, review the installation best practices, which\ninclude comprehensive z/OSMF video training from IBM.\nYou can install this release of your product and can continue to use an older release in another SMP/E environment. If you\nplan to continue to run a previous release, consider the following points:\n\u2022When you install the product into an existing SMP/E environment, the new installation deletes previous releases in that\nenvironment. We recommend that you install into a new CSI.\n\u2022If you acquired your product using SMP/E JCL, select different target and distribution zones for your new release from\nwhere your current release is installed. The new zones use different libraries than your current release.\n 86", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "db2e60170a45-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nCSM  installs a product into a new SMP/E environment by default. You can select an existing SMP/E\nenvironment from your working set.\n\u2022Define DDDEF entries in your new zones to point SMP/E to the proper libraries for installation. Ensure that they point\nto the new release libraries.\nInstallation Checklist\nTo plan your InterTest and SymDump installation, review the following checklist.\nThis checklist summarizes the required tasks, in the correct order, for a base/first-time installation. The checklist\nincludes a brief description of the tasks with links to comprehensive information required for the installation. To help\nthe pre-installation planning team members focus on appropriate tasks, the checklist also identifies the roles that are\ntypically required to complete the task.\nNOTE\nYou can often perform the security-related tasks in parallel with the other installation and configuration tasks.\nFor a printable version of this checklist, click here .\nPrepare for Installation\nTasks Description Role Status\nReview Installation Best\nPractices\u2022Manage Security and\nIntegrity Fixes.\n\u2022Configure SMP/E Internet\nService Retrieval for\nmaintenance\n\u2022Sign up for hiper\nnotifications\n\u2022Register on Broadcom\nSupport\n\u2022Apply IBM maintenanceSecurity Administrator\nSystems ProgrammerComplete, TBD, or N/A\nAddress Requirements \u2022Verify that your site\nmeets the pre-installation\nhardware, software, and\nsecurity requirements\nas noted in Product\nRequirementsSecurity Administrator\nSystems ProgrammerComplete, TBD, or N/A\nSelect an Installation Method \u2022Using z/OSMF Deployments\n\u2022Using native SMP/E\n\u2022Using CSMSystems Programmer Complete, TBD, or N/A\n 87", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dde3cbb256a5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInstall InterTest and SymDump\nTasks Description Role Status\nInstall Products Using z/OSMF\nOr\nInstall Products Using SMP/E\nJCL\nOr\nInstall Products Using CSM\u2022Create the product SMP/E\nand runtime environment\n(SMP/E data sets, target\nlibraries, and distribution\nlibraries).Systems Programmer Complete, TBD, or N/A\nMaintain Products Using z/\nOSMF Software Update\nOr\nMaintain Products Using SMP/E\nJCL\nOr\nMaintain Products Using CSMApply all PTFs required to bring\nInterTest and SymDump to\ncurrent maintenance.\n\u2022Download maintenance\n(corrective and preventive)\nautomatically using SMP/\nE Internet Service Retrieval\nor manually from Broadcom\nSupport.\n\u2022Obtain the current SMP/E\nHOLDDATA (download the\nexternal HOLDDATA file).\n\u2022Receive, apply, and accept\nmaintenance.Systems Programmer Complete, TBD, or N/A\nConfigure InterTest and SymDump\nTasks Description Role Status\nConfigure Products Using z/\nOSMF Workflow\nOr\nConfigure Your Product\nManually:\n\u2022Configure InterTest Batch\n\u2022Configure SymDump Batch\n\u2022Configure InterTest for CICS\n\u2022Configure SymDump for\nCICS\nOr\nConfigure Products using CSMComplete the minimum\nconfiguration tasks that are\nrequired before InterTest and\nSymDump can be started,\ncustomized, and used in your\nenvironment.\nUse the manual configuration\nsections to help you configure\nindividual InterTest and\nSymDump products. You\ncan install between one and\nfour InterTest and SymDump\nproducts at one time. By default,\nall four products are installed.\nTo configure all four products,\nbe sure to complete all of the\nconfiguration steps in this\nsection, beginning with Options .Security Administrator", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dde3cbb256a5-1", "text": "configuration steps in this\nsection, beginning with Options .Security Administrator\nSystems ProgrammerComplete, TBD, or N/A\n(Optional) Install Extensions \u2022Install Testing Tools Server\nand REST API\n\u2022Install the Debugger for\nMainframe Extension for\nVisual Studio Code\n\u2022Install the Abend Analyzer\nfor Mainframe Extension for\nVisual Studio CodeSecurity Administrator\nSystems ProgrammerComplete, TBD, or N/A\n 88", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5a35fdc6e68b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInstallation Considerations\nThis article identifies some items to consider and best practices to follow as you install your product.\nIf you are upgrading from an earlier release, we recommend that you completely replace the previous product. However,\nretain your ALIB files and any JCL that you converted for batch link.\nConcurrent Releases\nYou can install this release of your product and can continue to use an older release in another SMP/E environment. If you\nplan to continue to run a previous release, consider the following points:\n\u2022If you run Version 9.1 of the product and CAVHINIT initialized the product with a higher release, Batch link is not able\nto select the job from the queue for debugging.\n\u2022When you install the product into an existing SMP/E environment, this installation deletes previous releases in that\nenvironment.\n\u2022If you acquired your product with Pax ESD, select different target and distribution zones for your new release from\nwhere your current release is installed. The new zones use different libraries than your current release.\nNOTE\nCSM  installs a product into a new SMP/E environment by default. You can select an existing SMP/E\nenvironment from your working set. For more information, see the online help that is included in CSM .\n\u2022Define DDDEF entries in your new zones to point SMP/E to the proper libraries for installation. Ensure that they point\nto the new release libraries.\nIf you execute the application from LINKLIST, review your LINKLIST to ensure that the most recent version of your\nCommon Symbolic Component executables (defined to the Common Symbolic Component FMID) are highest in the\nconcatenation.\nInstalling an Individual Product\nThe following table lists each of the FMIDs that are shipped on the pax file and indicates which FMIDs for all 4 products", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5a35fdc6e68b-1", "text": "are installed. Please use the following table if you would like to install a subset of the 4 products.\nFMID Description InterTest Batch InterTest for CICS SymDump  Batch SymDump  for CICS\nCAVHB00 Common Symbolic\nComponentRequired Required Required Required\nCAVHB01 Common Eclipse UI\nComponentOptional Optional Optional Optional\nCABAB00 Common CICS\nComponentRequired Required\nCABAB01 Common CICS DB2\nComponentOptional Optional\nCAMRB00 InterTest Batch\nComponentRequired\nCCSAB00 InterTest for CICS\nComponentRequired\nCARXB00 SymDump  Batch\nComponentRequired\nCARXB01 SymDump  Batch\nDB2 ComponentOptional\n 89", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "104c316def70-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCABQB00 SymDump  for CICS\nComponent Required\nExample: Installation of InterTest Batch and SymDump  Batch\nIf you would like to only install InterTest Batch and SymDump  Batch, you would install the following FMIDs:\n\u2022CAVHB00\u2013 Common Symbolic Component\n\u2022CAVHB01\u2013 Common Eclipse UI Component (optional)\n\u2022CAMRB00\u2013 InterTest Batch Component\n\u2022CARXB00\u2013 SymDump  Batch Component\n\u2022CARXB01\u2013 SymDump  Batch DB2 Component (optional)\nSymbolic Files\nSymbolic files from previous releases are upward compatible with the current product release.\nCICS Products\n\u2022For detailed instructions on setting up your InterTest for CICS to support MRO, see Special Considerations for MRO\nSupport.\n\u2022If you require InterTest for CICS to support database system calls other than IBM's DB2 and DL/I, or IDMS  and\nDatacom, or calls to software that should not be monitored by InterTest for CICS, see Calls to Software and User\nMacro Support.\n\u2022If you plan to debug Hogan programs with InterTest for CICS, see CICS Interfaces and Compatibilities.\n\u2022To use InterTest for CICS with IBM's Omegamon product, start Omegamon before you start InterTest for CICS and\nexclude the InterTest transactions from the Omegamon Resource Limit (Time Out) Specification.\n\u2022To use InterTest for CICS with ASG's TMON product, exclude transactions from the TMON Resource Limit (Time Out)\nSpecification.\nBatch Products\n\u2022If you use File Master Plus  and you want to use the SymDump  Batch FM viewer command, perform the following\nadditional steps:\n\u2013Set up the File Master Plus  to use LIBDEFs (LIBALLOC='Y').", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "104c316def70-1", "text": "\u2013Set up the File Master Plus  to use LIBDEFs (LIBALLOC='Y').\n\u2013Ensure that the FM1 exec exists in a data set allocated to SYSPROC or SYSEXEC.\n\u2013Allocate CAI.CAVHCLS0 to SYSPROC or SYSEXEC.\n\u2022If you are using Compuware's AbendAid and SymDump  Batch on the same LPAR, execute CAIRIM after AbendAid's\ninitialization procedure. Also set the DUMP option to ON in the default options member CAOETABL.\n\u2022If you are using Macro4 DumpMaster and SymDump  Batch on the same LPAR, call the DumpMaster support group for\nthe required PTF that lets DumpMaster pass control to other dump formatting products. If you initialize DumpMaster\nbefore executing CAIRIM to initialize your product, set the DUMP option to ON in the default options member\nCAOETABL.\nInstallation Best Practices\nUse CSM  for Installation\nUse CSM  to acquire, install, deploy, and maintain your product. Although CSM  is the preferred method for installing\nBroadcom  mainframe products, some sites may decide to use the Electronic Software Delivery (ESD) installation method\ninstead.\nBusiness Value:\n 90", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "305f33d3b907-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCSM  provides a web interface, which works with ESD and standardized installation, to provide a common way to manage\nBroadcom  mainframe products. You can use it to download, install, and deploy your product.\nCSM  lets you download product and maintenance releases over the Internet directly to your system from the Broadcom\nSupport  website. After you use CSM  to download your product or maintenance, you use the same interface to install the\ndownloaded software packages using SMP/E. After installation, deployments allow system objects to be deployed across\nyour enterprise's different environments.\nUse Electronic Software Delivery\nAlthough CSM  is the preferred method for installing your Broadcom  mainframe products, some sites may decide to use\nthe Electronic Software Delivery (ESD) method instead. For sites who have decided to use ESD, download the installation\nfiles from Broadcom Support  and install directly from your disk.\nBusiness Value:\nUsing electronic software delivery (ESD) avoids ordering, shipping, and processing physical tape media to install the\napplication. It is more timely, more cost-effective, and environmentally friendly. It uses standard z/OS utilities to prepare\nthe product installation image on your system.\nFor information about how to download your Broadcom  products from the Broadcom Support  Online web site for\ninstallation using the enhanced ESD pax process, see Installing .\nIBM APARs\nNo IBM APARs are required at this time.\nBusiness Value:\nThere are no known IBM APARs that impact the operation or performance of the product. You may apply the most recent\nIBM APARs appropriate for your environment as needed.\nInstallation in a Test Environment\nPerform your installation and initial evaluations of a new release of the product and its components on a test system.\nBusiness Value:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "305f33d3b907-1", "text": "Business Value:\nNew releases of Broadcom  testing tools can always co-exist with previous releases, letting you test a new release on a\ntest system while still running the older version on a production system. Evaluating the product in a test environment lets\nyou detect any possible problems before you roll out the product to a production system.\nAdditional Considerations:\nAlways be sure to review any migration considerations in Installing before upgrading your Broadcom  product.\nCommon Symbolic Component\nWhen installing more than one of the Broadcom  mainframe testing tools, we recommend that you install and maintain only\none version of Broadcom  common symbolic component that is shared by all of the testing tool products.\nSeveral testing tool products ( InterTest Batch, InterTest for CICS, SymDump  for CICS, SymDump  Batch, Optimizer/II ,\nand MAT) each distribute the common symbolic component in the VH FMID. This FMID was named CVHrr00 in versions\nbefore Version 10 and is now named CAVHrr0. The rr portion of the FMID contains the version number.\nWhen installing any of these Broadcom  testing tool products, first query your Consolidated Software Inventory (CSI) to\ndetermine whether you already have a version of CVHrr00 or CAVHrr0 installed. If you use one CSI for all of your testing\ntool products then you need to perform only one query for these FMIDs. If you have one CSI for each testing tool product\nthen you will need to query each CSI.\n 91", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bebe14c0f7b4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIf you locate an installed version of CVHrr00 or CAVHrr0 during your query, compare the rr in your installed version of that\nFMID with the rr in the FMID provided with the product you are installing. Replace your existing FMID only if the rr in the\nproduct you are installing is higher than the rr in your existing function.\nBusiness Value:\nBy installing and maintaining a single version of the Broadcom  common symbolic component, you reduce your\nmaintenance effort, save disk space, and eliminate the possibility of executing symbolic utilities that are not up to date with\nthe latest maintenance.\nAdditional Considerations:\nThe APPLY job of the installation places an SMP/E copy of the CAVHrr0 function in a library; however, many companies\ndo not execute the testing tool products from this library. Therefore, always be sure to make the executables for the\ncommon symbolic component available for the testing tools products to use.\nThere are many ways to make the executables for the common symbolic component available, including:\n\u2022LNKLIST\nAlways update your LNKLIST library after applying maintenance to CAVHrr0 if you have copied the executables for the\ncommon symbolic component from CAVHrr0 into a separate load library that you have added to your LNKLIST for all\nproducts to share.\n\u2022STEPLIBs\n\u2022CLISTs (for ISPF interfaces)\nWe recommend using the LNKLIST method because it has the specific advantage of making the executables available\nto all Broadcom  products with no additional changes to any JCL or CLISTs. If you cannot use LNKLIST for some reason\n(for example, your company has issues with updating LNKLIST or has specific rules prohibiting or limiting the use of", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bebe14c0f7b4-1", "text": "LNKLIST), it is acceptable to add these executables to your STEPLIB or CLIST allocations. However, using STEPLIB or\nCLIST requires more initial setup and can be difficult to maintain if library names change.\nInterTest Batch JCLCheck Function CAZ2C00\nInterTest Batch uses the JCLCheck  Common Component Function CAZ2C00 to provide a certain functionality which\nis outlined below. If you are already licensed for the full JCLCheck  product on the CPU where you are installing your\nproduct, do not install function CAZ2C00 containing the JCLCheck  common component.  \nNOTE\nIf you are not licensed for the full JCLCheck  product, install function CAZ2C00. The CAZ2C00 function is a\nseparate Pax file installation. This Pax file is included and available for download along with the InterTest and\nSymDump  11.0 product package For more information, refer to the installation documentation for JCLCheck\nCommon Component.\nBusiness Value:\nThe JCLCheck  Common Component installation package includes the materials necessary to install the JCLCheck\ncommon component function CAZ2C00. However if you have already licensed and installed the JCLCheck  product, you\ncan save installation time, maintenance effort, and disk space by using your existing version instead.\nAdditional Considerations:\nThis common component is used to create ALIB members from your JCL for online allocations and to prepare JCL for\nuse with the Batch Link facility. For the Batch Link facility, this JCL conversion is a convenience rather than a requirement,\nsince JCL can be easily prepared manually for use with the Batch Link facility as described in Batch Debugging.\nNOTE\nWhen converting a PROC needed for use with DB2-stored procedures, a manual conversion is required and the\nJCL conversion feature is not used.\n 92", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5b66f94f004e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIf you do not already have function CAZ2C00 installed on the same CPU, you must install it so you can convert JCL\nwith your product. The materials needed to install that function have been provided as part of the JCLCheck  Common\nComponent installation package.\nIf you decide to install a second copy of function CAZ2C00 on the same CPU, be sure to maintain both copies when\napplying maintenance. Solutions required for this function will be provided to the application and JCLCheck  customers.\nAs a result of this condition you may have two different releases of function CAZ2C00 installed, one with the JCLCheck\nproduct and the other with the InterTest Batch product. This is acceptable and fully supported provided that the version\nused with your product meets the minimum release number requirements as described in  Installing.\nReview Installation and Configuration Best Practices\nReview the following installation best practices before you begin the installation process:\nConfigure SMP/E Internet Service Retrieval  for Product Maintenance\nConfigure SMP/E Internet Service Retrieval  to eliminate the need to download maintenance manually. This service uses\nthe IBM SMP/E RECEIVE ORDER command to acquire Broadcom  mainframe product maintenance. This service enables\nyou to acquire maintenance on demand or to schedule an SMP/E job to run as needed.\nIf you are an existing CSM  customer, you can also use this service to download maintenance and dramatically reduce the\ntime that is needed to download PTFs.\nBusiness Value:\nSMP/E Internet Service Retrieval  can reduce hours of maintenance time to just minutes, making your system\nprogrammers more productive and allowing them to focus on higher value tasks. SMP/E Internet Service Retrieval :\n\u2022Eliminates time-consuming fix searches and the need to select maintenance manually from the Broadcom Support\nportal\n\u2022Automates delivery of Broadcom  maintenance directly to your mainframe", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5b66f94f004e-1", "text": "portal\n\u2022Automates delivery of Broadcom  maintenance directly to your mainframe\n\u2022Fulfills orders based on the status of your SMP/E environments\n\u2022Enables scheduling of maintenance downloads\n\u2022Facilitates an easier installation of Recommended and Preventive service\nNOTE\nMore information:\nConfigure SMP/E Internet Service Retrieval\nImplement a Proactive Preventive Maintenance Strategy\nWe recommend that you use CARS  to implement a proactive preventive maintenance strategy. CARS  is patterned after\nthe IBM preventive maintenance model, Recommended Service Upgrade (RSU). With CARS , you can install preventive\nmaintenance for most Broadcom  z/OS based products consistently on a schedule that you select (monthly, quarterly,\nannually). You can follow the same schedule that you use to apply IBM maintenance, or you can implement a schedule for\nBroadcom  products only.\nBusiness Value:\nKeeping your products current with maintenance helps your team remain productive and minimizes errors while safely\nprotecting your systems. If you do not install preventive maintenance regularly, you risk encountering known problems for\nwhich we have published and tested fixes. Early notification about the potential need to apply a required fix helps avoid\nunscheduled downtime and assists you in proactively maintaining your software.\n 93", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a73915f09ad6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nMore information:\nCARS\nSign up for Hiper Notifications\nBroadcom Support  is always alert to any known problems that could affect customers. We recommend that you sign up\nfor hiper notifications for all Broadcom   products on the Broadcom Support  website so that you receive notification of\npotential problems as soon as possible. Select Hiper notifications and follow that dialog to receive notifications for your\nproducts.\nBusiness Value:\nEarly notification about the potential need to apply a required fix helps avoid unscheduled downtime and assists you in\nproactively maintaining your software.\nApply IBM Maintenance\nWe recommend that you review the current list of IBM APARs for z/OS, especially related to hipers. Then apply the\nAPARs that are appropriate to your environment.\nBusiness Value:\nMissing APARs can affect the operation or performance of your product.\nProduct Requirements\nThis article describes the requirements needed to install and use the InterTest and SymDump  products.\nHardware Requirements\nStorage Requirements\nEnsure that you have the following storage available:\n\u2022For ESD installations, 915 cylinders for the downloaded files\n\u2022For installation and setup:\n\u2013Installation: 1,750 cylinders\n\u2013SMP/E temporary libraries: 60 cylinders\nNOTE\nMany installation library names have been updated with new naming conventions. Review existing CLISTs, JCL,\nand procedures from prior product releases, and update the new data set names, if needed.\nData Monitoring\nThe data monitoring feature of InterTest for CICS requires a significant amount of storage over and above the\nstorage required by the programs being monitored. Compute the storage requirements as follows:\n500 bytes times the number of transaction entries as defined by the STMTTRCE option plus the size of mirror area for", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a73915f09ad6-1", "text": "each program in the transaction for which data monitoring is active, where the mirror area is equal to the size of storage\nfor the monitored program.\nIf you encounter storage problems while using the data monitoring feature, perform one or more of the following actions:\n 94", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "401c7f1b6cf2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Reduce the use of data monitoring in the region.\n\u2022Make the STMTTRCE value smaller in the default options table, IN25OPTS.\n\u2022Increase the EDSALIM for the CICS region.\nSecurity Requirements\nTo complete the tasks in this section, you need the following security privileges:\n\u2022Read authority for all the SMP/E target data sets.\n\u2022Update authority for the PROTSYM, ALIB (optional), and INCLUDE file (optional).\n\u2022Superuser authority for installing and configuring the GUI. To mount a ZFS, you must have either superuser authority\nor read access to the SUPERUSER.FILESYS.MOUNT resource (in the UNIXPRIV class).\nSoftware Requirements\nThe following software is required:\n\u2022Supported release of the following IBM products and features:\n\u2013z/OS\n\u2013SMP/E\n\u2013COBOL, PL/I, and Assembler compilers\n\u2013LE Runtime\nEclipse User Interface\nThe Eclipse UI needs access to the Broadcom  Testing Tools server. The Broadcom  Testing Tools server requires IBM 32-\nbit Java 5.0 (at or above SR5A) or IBM 32-bit Java 6.0 (at or above SR4).\nUTF-16 Support for COBOL\nThe InterTest Batch mainframe ISPF user interface can display UTF-16 (Unicode) data in the Keep window and Display\npanel when debugging a COBOL program. You must have z/OS Unicode Services installed to convert and display UTF-16\ndata. These services come standard with z/OS and are located in SYS1.CSSLIB.\nPL/I Programs\nWhen linking PL/I with Language Environment, CEESTART must be the first CSECT and the object module of the main", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "401c7f1b6cf2-1", "text": "procedure must be included before any object modules of subroutines. The products assume that these procedures are\nfollowed.\nCICS Temporary Storage Model Restriction\nThe products use a temporary storage queue prefixed with a lower case \"i\" when starting. Because of this, you cannot\nhave a CICS-defined TSMODEL prefixed with a lower case \"i\" defined as recoverable. This will cause the start of the\nproduct to wait endlessly for a syncpoint to be taken by the starting task.\nTerminal Input/Output Area Compression Routine Users\nExclude the products' transactions and programs from any Terminal Input/Output Area (TIOA) compression packages\nor routines, such as 3270 Super Optimizer/CICS and CTOP. Failure to do so produces unpredictable results because\nInterTest for CICS uses saved TIOAs. In addition, the InterTest for CICS FILE facility does not work properly with data files\nthat have been put through data compression routines.\n 95", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "203b63a82145-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTSO Logon Requirements for Foreground Debugging\nThe TSO logon requirements for foreground debugging in InterTest Batch are region size (when logging on) and the\nnumber of DD statements that can be dynamically allocated at any one time during the session (DYNAMBR).\n\u2022The application uses about 1 MB of virtual storage, so you should log on with a region large enough for this product\nand the program being debugged. A region of 4 MB is sufficient for most processing.\n\u2022The DYNAMBR number should be high, especially when running IMS/BTS applications in foreground. Allocation\nchecks to see if the number in DYNAMBR has been exceeded and has no other effect on the TSO session.\n\u2022Because the product has a dynamic STEPLIB facility, it is not necessary to allocate libraries containing dynamically\ncalled modules at logon time.\nACF2\nTo use InterTest for CICS with ACF2 , add the transactions IPLX, ISER, VTAT, LIST, and VIRC to your ACF2 SAFELIST.\nFor additional information on these InterTest for CICS transactions, see IN25OPTS Keywords.\nIf InterTest global logging is turned on and the XDCT System Initialization parameter specifies a resource class profile,\nensure that it allows access to the CSSL transient data queue. Similarly, if the XPCT System Initialization parameter\nspecifies a resource class profile, ensure that it allows access to the CNTL transaction.\nRACF Users\nTo use InterTest for CICS with RACF, define the InterTest for CICS transactions IPLX, ISER, VIRC, LIST, and VTAT to\nCICS with CMDSEC(NO) and RESSEC(NO). All InterTest for CICS transactions and programs require UACC(READ) for", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "203b63a82145-1", "text": "EXEC CICS INQUIRE commands to give all users RACF READ access. Using these settings makes the symbolics for a\nsource listing breakpoint display available to users.\nIf RACF file level security is in use, add the following statements to the xCICSFCT resource class:\nPROTSYM, PROTHLF ...UACC(READ)\nPROTCPF, PROTUHF, PROTMLOG ...UACC(UPDATE)\nIf InterTest global logging is turned on and the XDCT System Initialization parameter specifies a resource class profile,\nensure that it allows access to the CSSL transient data queue. Similarly, if the XPCT System Initialization parameter\nspecifies a resource class profile, ensure that it allows access to the CNTL transaction.\nCICS Startup Parameter Considerations\nIf you are running SymDump  for CICS on a CICS Transaction Server release earlier than 5.1, you might need to increase\nthe value of your MAXOPENTCB SIT parameter.  For CICS regions which run small workloads, we recommend a\nminimum value of 64. For CICS regions with large workloads, you might want to set MAXOPENTCB to the same value as\nMXT.\nCICS Global User Exits\nThis InterTest for CICS release requires the use of the following global user exits:\nXPCFTCH and XPCTA\nRequired for the CNTL=START and CNTL=END commands to operate InterTest for CICS and control monitoring.\nXDUREQ\nRequired for dump suppression and dump capture.\nXMEOUT\nRequired for suppression of abend messages.\n 96", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f61e24b21ccd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nXRMIOUT\nSupport for the CORE=LASTSQL command. Collects DB2-related call information for every DB2 call done in the\nsystem. This can have significant performance implications in some DB2 shops. The parameter XRMIO=YES/NO\nIN25OPTS controls the use of this exit. The default is XRMIO=YES.\nXLDLOAD\nRequired for DWARF new copy support\nWhen monitoring programs, observe the following rules:\n\u2022Do not disable the previous global user exits in any way. This action causes InterTest for CICS to stop functioning.\n\u2022The InterTest for CICS global user exits honor the return codes set by previous exits, which might have an impact on\nwhether InterTest for CICS successfully monitors a program. If you have problems caused by other CICS global user\nexits setting a return code before InterTest for CICS exits receive control, you can ensure that the InterTest for CICS\nexits are first to receive control by adding the program entry IN25PLTX to the CICS startup PLT. IN25PLTX is required\nas the first program entry in Phase 1 (prior to the DFHDELIM entry) of the PLT.\n\u2022If you are installing SymDump  for CICS  with InterTest for CICS, always place the SymDump  for CICS IN25INST\nprogram after the InterTest for CICS IN25PLT in the PLT.\nNOTE\nFor more information, see the section Invoking more than one exit program at a single exit  in the IBM\nKnowledge Centre at ibm.com  under Developing system programs  > Global user exit programs .\n\u2022If other exits receive control after InterTest for CICS, they must not change the return code or entry point fields in the\nuser exit parameter list.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f61e24b21ccd-1", "text": "user exit parameter list.\nTo disable SymDump  for CICS you must use the CNTL=END command.\nFailure to observe these rules will cause monitoring to be disabled. For example, InterTest for CICS monitoring is not\nperformed if another exit receives control before InterTest for CICS and passes on a modified return code or entry point.\nCICSplex Support\nInterTest for CICS provides optional support for CICS regions participating in a CICSplex environment. When you install\nInterTest for CICS with CICSplex support, participating CICS regions propagate InterTest for CICS commands and\nbreakpoints automatically to all regions in the CICSplex. This automatic propagation lets you easily debug dynamically\nrouted transactions and programs.\nCICSplex command propagation is accomplished mainly through CAICCI for z/OS, a Common Components and Services\nfor z/OS. Other than installing CAICCI for z/OS and setting the following customization options, you do not need anything\nelse to obtain CICSplex support.\nTo install InterTest for CICS with CICSplex support, follow these steps:\n1.Install CAICCI in all participating CICSplex regions as discussed in the section Common Components and Services  for\nz/OS Requirements.\n2.Follow the InterTest for CICS installation instructions. You can install using one of the following methods:\n\u2013CSM\n\u2013Pax-Enhanced Electronic Software Delivery\n3.Use the following IN25OPTS customization options in each participating CICSplex region:\n\u2013CICSPLEX=YES\n\u2013CPLXFMID=a CICSplex family name\n\u2013CPLXCKPI=hhmm (a checkpoint interval)\nFor details on setting these options, see IN25OPTS Keywords.\nNOTE\nObtain support for multiple CICSplex families within or across multiple z/OS regions by changing the CPLXFMID", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f61e24b21ccd-2", "text": "family name that is associated with each region.\n 97", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b7941dd9e152-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nStartup and Termination with CICSplex Support\nInterTest for CICS regions that you installed with CICSPLEX=YES are affected during startup and termination in the\nfollowing ways:\n\u2022The CNTL=START and CNTL=RESTART commands automatically have InterTest for CICS resynchronize monitoring\nwith any active regions in the CICSplex upon startup.\n\u2022The CNTL=END, SCOPE=GLOBAL command can be issued to terminate concurrently all InterTest for CICS\nprocessing in all connected regions in the CICSplex.\nDynamic Symbolic Support for Endevor\nAll InterTest and SymDump products provide optional support for Endevor  users to load dynamically the application\nprogram symbolic information from Endevor  when the footprint option is in use. This feature allows debugging  or fault\nanalysis to proceed when application program symbolics are not found in the PROTSYM files.\nTo support this feature, the following products are required:\n\u2022A supported release of Endevor .\n\u2022Endevor  AUTHLIB, CONLIB, and the data set containing C1DEFLTS must be in the LNKLIST.\n\u2022C1DEFLTS. Add the keyword COMPLISTWD=.LIST to the C1DEFLTS TYPE=MAIN section. This keyword identifies\nthe text string that Endevor  looks for in an element's component list to identify the listing data set for the print element\nlisting function. The period (.) before the variable LIST is used as a wildcard to denote anywhere within the DSN\n(LISTLIB, LISTING, COBLIST, for example). Change the variable LIST to conform to your DSN naming conventions for\ncompiler and assembler output files.\nNote the following rules:\n\u2022Create the listings using an Endevor  generate process.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b7941dd9e152-1", "text": "Note the following rules:\n\u2022Create the listings using an Endevor  generate process.\n\u2022Use Endevor  with the following DD statement coded to monitor the listing data set the Endevor  generate process that\nis created:\nMONITOR=COMPONENT,FOOTPRINT=CREATE\n\u2022The object and load module libraries must use the footprint feature with the following coded on their respective DD\nstatements:\nFOOTPRINT=CREATE\nIf your installation has defined multiple C1DEFLTS, additional customization steps are necessary. For more information\nabout defining multiple C1DEFLTS, see Interfaces and Compatibility.\nYou might also need to install and customize CAICCI.\nNOTE\nThe dynamic symbolic support for the Endevor  feature, hereafter referred to as the dynamic symbolic\nsupport feature, cannot differentiate between multiple listing outputs created by a single Endevor  processor\nfor the same element. Therefore, dynamic symbolic support using listing outputs from multiple compiles\nor assemblies from a single Endevor  GENERATE or MOVE action for the same element might produce\nunpredictable results.\nCommon Services Requirements\nInterTest and SymDump uses the following Common Components and Services  for z/OS components:\n\u2022CAI Resource Initialization Manager (CAIRIM)\n\u2022Broadcom  License Management Program ( LMP)\n\u2022CAI Common Communications Interface (CAICCI)\n\u2022Event Management\n\u2022Broadcom  Health Checker Common Service\n 98", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4aab1b11dd65-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\n\u2022If other Broadcom  products are installed at your site, some of these services may already be installed. For\nmore information, see Common Components and Services  for z/OS\n\u2022We recommend that you stay current on Common Components and Services  maintenance.\nTarget Libraries\nThe following list contains target libraries used by InterTest and SymDump . These libraries must be allocated if they do not\nalready exist for some other Broadcom  product at your site:\nCAI.CAVHAUTH\nTarget Authorized load library\nCAI.CAVHCLS0\nTarget CLIST library\nCAI.CAVHDBRM\nTarget DBRM library\nCAI.CAVHDATV\nTarget GUI/server executables library\nCAI.CAVHHELP\nTarget SymDump  Batch help library\nCAI.CAVHHLF\nTarget CICS help library\nCAI.CAVHJCL\nTarget sample JCL library\nCAI.CAVHLOAD\nTarget load library\nCAI.CAVHMAC\nTarget macro library\nCAI.CAVHMSG0\nTarget ISPF message library\nCAI.CAVHOPTN\nTarget common options library\nCAI.CAVHPNL0\nTarget ISPF panel0 library\nCAI.CAVHPNL1\nTarget InterTest Batch ISPF panel1 library\nCAI.CAVHPROC\nTarget procedure library\nCAI.CAVHRPF\nTarget InterTest Batch ROSCOE RPF library\nCAI.CAVHSAMP\nTarget sample source library\nCAI.CAVHSKL0\nTarget SymDump  Batch skeleton library\nCAI.CAVHSRC\nTarget InterTest Batch source library\n 99", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0a47fdc823b1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAI.CAVHSYM\nTarget sample CICS symbolic library\nCAI.CAVHTBL0\nTarget SymDump  Batch table library\nCAI.CAVHXML\nTarget installation XML\nDistribution Libraries\nThe following list contains the distribution libraries used by InterTest and SymDump. These libraries must be allocated if\nthey do not already exist for some other Broadcom  product at your site:\nCAI.AAVHCLS0\nSample REXX and CLIST\nCAI.AAVHDBRM\nDistribution DBRM library\nCAI.AAVHDATV\nDistribution GUI/Server executables library\nCAI.AAVHHELP\nDistribution SymDump  Batch help library\nCAI.AAVHHLF\nDistribution CICS help library\nCAI.AAVHJCL\nDistribution sample JCL library\nCAI.AAVHMAC\nDistribution macro library\nCAI.AAVHMOD0\nDistribution load library\nCAI.AAVHMSG0\nDistribution ISPF message library\nCAI.AAVHOPTN\nDistribution common options library\nCAI.AAVHPNL0\nDistribution panel0 library\nCAI.AAVHPNL1\nDistribution InterTest Batch panel1 library\nCAI.AAVHPROC\nDistribution procedure library\nCAI.AAVHRPF\nDistribution InterTest Batch ROSCOE RPF library\nCAI.AAVHSAMP\nDistribution sample library\nCAI.AAVHSKL0\nDistribution SymDump  Batch skeleton library\nCAI.AAVHSRC\nDistribution InterTest Batch source library\n 100", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eae667bf42bf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAI.AAVHSYM\nDistribution CICS symbolic library\nCAI.AAVHTBL0\nDistribution SymDump  Batch table library\nCAI.AAVHXML\nDistribution installation XML\nConcurrent Releases\nThis article describes concurrent release requirements.\nYou can install this release of your product and can continue to use an older release in another SMP/E environment. If you\nplan to continue to run a previous release, consider the following points:\n\u2022When you install the product into an existing SMP/E environment, the new installation deletes previous releases in that\nenvironment.\n\u2022If you acquired your product using SMP/E JCL, select different target and distribution zones for your new release from\nwhere your current release is installed. The new zones use different libraries than your current release.\nNOTE\nCSM  installs a product into a new SMP/E environment by default. You can select an existing SMP/E\nenvironment from your working set.\n\u2022Define DDDEF entries in your new zones to point SMP/E to the proper libraries for installation. Ensure that they point\nto the new release libraries.\nInstall Products Using z/OSMF\nLearn how to install product software using z/OSMF.\nAs a systems programmer, your responsibilities include acquiring, installing, maintaining, and configuring mainframe\nproducts on your systems. z/OSMF lets you perform these tasks for Broadcom  mainframe products and mainframe\nproducts from other vendors. z/OSMF lets you manage software on your z/OS systems through a browser at any time,\nfrom any location. By streamlining some traditional tasks and automating others, z/OSMF can simplify some areas of\nsystem management and also reduce the level of expertise that is required for managing system activities. Experienced\nusers can view, define, and update policies that affect system behavior, monitor system performance, and manage z/OS\nsoftware.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eae667bf42bf-1", "text": "software.\nAs products and vendors adopt z/OSMF services, you can install and maintain all your mainframe products in a common\nway according to industry best practices. After configuration is complete, you can execute the product and easily provision\nnew software instances for use on other systems throughout your environment.\nUse the following topics to guide you through the installation process using z/OSMF:\nAddress z/OSMF Requirements\nProvides information about z/OSMF general configuration and security requirements.\nAcquire a z/OSMF Portable Software Instance\nProvides the steps to acquire the product software from Broadcom Support  and register the portable software\ninstance in z/OSMF.\nInstall Product Software Using z/OSMF Deployments\nProvides the steps to install (deploy) the portable software instance to an LPAR using z/OSMF Deployments. This\nstep creates the SMP/E environment and runs the RECEIVE, APPLY, and ACCEPT steps to prepare the software\ninstance for SMP/E operations. This step also:\n 101", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b095c6ae651c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Customizes the data set names that are defined to SMP/E.\n\u2022Mounts required USS files if necessary.\n\u2022Performs workflow execution to customize the deployed runtime environment for use on a specific z/OS\nsystem.\nImport Product Information into z/OSMF\nProvides the steps to import the Broadcom  product information file so that z/OSMF has access to the latest\nproduct release information. For a list of products using z/OSMF, see Mainframe Products using z/OSMF in the\nMainframe Common Maintenance Procedures documentation.\nTIP\nSee our installation best practices article for a list of comprehensive z/OSMF video training from IBM.\nWhen these tasks are completed, you are ready to install preventive maintenance. You can also configure software\ninstances using z/OSMF workflows.\nAddress z/OSMF Requirements\nBefore you install your Broadcom  mainframe products using the IBM \u00ae z/OSMF Management Facility (z/OSMF), address\nthe installation and security requirements in the following table:\nTIP\nYour systems programmers and security administrators can complete these tasks in parallel.\nTask Role\nApply required maintenance for CA Common Services for z/OS (CCS) Version 15.0\n(SO12499)\nThe CCS PTF installs load module stubs for select IBM products into your installed\nCCS library hlq.CAW0CALL. If prompted during installation for the data set name of\na load library for an IBM product that you do not have installed, specify your installed\nhlq.CAW0CALL data set name.Systems programmer\nConfigure z/OSMF as described in the IBM Knowledge Center\nThe IBM z/OS Management Facility Configuration Guide   is your primary source of\ninformation about how to install and configure z/OSMF. We also strongly recommend that", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b095c6ae651c-1", "text": "information about how to install and configure z/OSMF. We also strongly recommend that\nyou review the z/OSMF overview and use the installation checklists that are provided in\nthe IBM Knowledge Center. You can open the IBM documentation in a separate browser\ntab for reference during installation of your products using z/OSMF Deployments.Systems programmer, security\nadministrator, domain administrator\nConfigure z/OSMF security for CA ACF2\u2122 for z/OS , CA Top Secret\u00ae for z/OS , or IBM\nRACF  as applicable to authorize users and resources.Security administrator\nConfirm that the installer has read, create, update, and execute privileges in z/OS. Write\naccess is also required to the UNIX System Services (USS) directories that are used for\nthe installation process.Security administrator\nAddress the following USS requirements:\n\u2022Create a USS directory to receive the z/OSMF pax file and to perform the unpack\nsteps.\n\u2022Confirm that you have write authority to the USS directories that are used for the z/\nOSMF pax installation process.\n\u2022Confirm that you have available USS file space.\nTo download and unpack the pax file, you need free space that is approximately 3.5\ntimes the pax file size in the file system that contains the pax directories. For example, to\ndownload and unpack a 14 MB pax file, you need approximately 49 MB of free space in\nthe file system hosting your pax directory. If you do not have sufficient free space, error\nmessages like EZA1490I Error writing to data set or EZA2606W File I/O error 133 can\noccur.Systems programmer, security\nadministrator\n 102", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "91d1b5ef4323-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAfter these requirements have been addressed, you are ready to acquire a z/OSMF Portable Software Instance or\nConfigure a Software Instance using z/OSMF Workflows.\nAcquire a z/OSMF Portable Software Instance\nAs a systems programmer, you can acquire an IBM z/OSMF portable package for your product from Broadcom Support\nand then add the portable software instance to z/OSMF. The product SMP/E environments are pre-built at Broadcom ,\nbacked up, and made available for download as a z/OSMF portable software instance. After you acquire the portable\nsoftware instance, you can use z/OSMF Deployments to perform the installation and z/OSMF workflows to perform post-\ninstall configuration.\nThe following diagram illustrates the acquisition process:\nWhen you complete the acquisition process, the product software is ready for installation using z/OSMF Deployments.\nUse the following topics to guide you through the z/OSMF product acquisition process:\n1.Address all z/OSMF requirements.\n2.Order the z/OSMF portable software instance .\nNOTE\nFor a list of Broadcom  mainframe products that provide a z/OSMF package, see Mainframe Products using\nz/OSMF for Software Maintenance .\n3.Register the portable software instance in z/OSMF .\nOrder the z/OSMF Portable Software Instance\nYou can order the z/OSMF portable software instance from the Broadcom Support  and then download the package\nto a local z/OSMF host as a single pax file. You can download directly to the mainframe or you can download to your\nworkstation and then transfer the pax file to the mainframe. A file transfer utility, such as FTP, is required to transfer data\nto the mainframe.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "91d1b5ef4323-1", "text": "to the mainframe.\nThe portable software instance is a portable form of a software instance, including the SMP/E CSI data sets, all\nassociated SMP/E-managed target and distribution libraries, non-SMP/E-managed data sets, and meta-data that is\nrequired to describe the product software instance.\n 103", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "34e7d5926e37-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nTo optimize downloads from Broadcom Support , configure the downloads.broadcom.com URL for HTTPS\nand Secure FTP in your network security software, firewalls, or both. Sites that regulate access through an IP\naddress are required to allow network access to 141.202.253.110.\n1.Go to Broadcom Support  at https://support.broadcom.com, and select Software , Mainframe Software , and My\nDownloads.\n2.Log in using your Broadcom Support  username and password.\nThe My Downloads  page appears.\n3.Select a product from the list or enter the product name in the Search  field.\nThe product page appears with two tabs under the product name: Products  and Solutions .\n4.Under Products , select the product that you want to download.\nA list by release, service pack, and language appears.\n5.Click the hypertext link to select a release.\nThe Primary Downloads  page appears. This page shows the available product-specific software packages that you\ncan select to download.\nIf an Additional Downloads  page is available, this page shows additional software packages that are related to your\nproduct selection that you can download. These products may already be installed.\n6.Review the packages that appear under Primary Downloads  and Additional Downloads  and complete the following\nsteps:\na.Select the zOSMF Package  (productid .VnnRn.ZOSMF.pax.Z) and other files that you want to include in the\nproduct download.\nIf more than one package is available, you can only select one.\nb.Select Download Selected , HTTPS Download , or Secure FTP Download . Secure FTP Download is the\npreferred method. For download tips, see Product Download Help . For sample JCL and security requirements, see\nDownload Methods and Locations .\nThe product package is downloaded.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "34e7d5926e37-1", "text": "Download Methods and Locations .\nThe product package is downloaded.\n7.Execute JCL to unpack the installation file and restore the individual pax files. Sample JCL follows:\n//USSBATCH EXEC PGM=BPXBATCH\n//STDOUT   DD SYSOUT=*\n//STDERR   DD SYSOUT=*\n//STDPARM  DD *\nsh cd /yourUSSpaxdirectory /; \npax -rvf yourpaxfilename.ZOSMF.pax.Z\n/*\nCustomize the sample JCL as follows and then submit for execution:\na.Add a JOB statement.\nb.Update the USS directory ( yourUSSpaxdirectory ) with the path name where you want to copy the pax file.\nc.Update yourpaxfilename  with the name of the pax file that you want to copy to the mainframe.\nUSSBATCH can take several minutes to execute. A return code of zero is expected. Any other return code indicates a\nproblem.\nAfter successful execution, the individual pax files have been restored and are ready for use. Go to Register Portable\nSoftware Instance in z/OSMF .\nRegister Portable Software Instance in z/OSMF\nAfter you have acquired and downloaded the portable software instance to a local z/OSMF host system, you must log\nin to z/OSMF to register the product software and define the portable software instance to z/OSMF as shown in the\n 104", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "33dfe019d8cf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nfollowing procedure. When you complete these steps, the portable software instance is registered in z/OSMF and ready\nfor installation (deployment).\n1.Log in to the z/OSMF web interface and select your user ID in the top or bottom right-hand corner to switch between\nthe Desktop Interface and Classic Interface.\n2.Complete either  of the following steps to display the Software Management page:\na.In the Desktop Interface, select Software Management .\nb.In the Classic Interface, select Software , Software Management .\n3.Select Portable Software Instances  to define your portable software instance to z/OSMF.\n4.Select Add from the Actions menu and select From z/OSMF System .\nThe Add Portable Software Instance page displays.\n5.Complete the following steps:\na.Select or type the system name (destination LPAR) and UNIX directory (destination USS directory) where the\nportable software instance files reside and select Retrieve .\nb.Enter a name for the new portable software instance. You can also enter an optional description and assign one or\nmore categories that display existing packages.\nc.Select OK.\nThe new portable software instance is now defined to z/OSMF.\nThe portable software instance is now registered in z/OSMF and ready to install (deploy). Go to Install Product Software\nusing z/OSMF Deployments.\nInstall Product Software Using z/OSMF Deployments\nAs a systems programmer, your responsibilities include installing product software in your z/OS environment. After\nthe portable software instance or software instance is registered in z/OSMF, you can use z/OSMF Deployments to\ninstall the product software and create the product data sets (global, CSI, target libraries, and distribution libraries) for\nthe new software instance. The deployment jobs create a copy of the source product data sets to create the product", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "33dfe019d8cf-1", "text": "target runtime environment. Creating a copy of the SMP/E target data sets keeps the SMP/E environment clean and it\nalso isolates the product runtime environment for maintenance activities. You can also perform z/OSMF workflows to\ncustomize the SMP/E data sets, mount UNIX System Services (USS) files if necessary, and configure the new software\ninstance on the target system.\nTo install Broadcom  mainframe products using z/OSMF and make the product software available for use on a system\nby users and other programs, define a new deployment. This step defines the SMP/E environment name and the prefix\nof the CSI data set in z/OSMF. You also specify data set allocation parameters for all SMP/E data sets, target libraries,\nand distribution libraries. To define a new deployment, complete the deployment checklist (specify the USS path, DSN,\nVOLSERs), and submit the deployment jobs through the z/OSMF user interface. When the deployment is complete, you\nhave a source and target copy of the software.\nNOTE\nFor more information about these tasks, see Deploying software  in the IBM documentation.\nSubsequent maintenance activities for the product update the SMP/E environment without affecting your active product\nruntime environments. You decide when to redeploy the maintenance-updated SMP/E target data sets to each of the\nproduct runtime environments.\nBefore you begin this process, review the installation best practices and verify the installation requirements in Prepare for\nInstallation.\nNOTE\nThe installer requires read, create, update, and execute privileges in z/OS. Write access is also required to the\nUSS directories that are used for the installation process. To deploy a product that has USS components, the\ninstaller's user ID must have access to the appropriate resource profiles in the UNIXPRIV class, access to the\n 105", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "592907dded04-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBPX.SUPERUSER resource profile in the FACILITY class, or UID(0). For UNIXPRIV, read access is required to\nSUPERUSER.FILESYS.CHOWN, SUPERUSER.FILESYS.CHGRP, and SUPERUSER.FILESYS.MOUNT.\n1.Display the Deployments table in z/OSMF ( Software Management, Deployments ).\n2.Define a new deployment by selecting New from the Actions menu.\nThe deployment checklist displays. You can also modify, view, copy, cancel, or remove existing deployments.\n3.Complete the deployment checklist items as described in Defining new deployments  in the IBM documentation.\nAs you complete the deployment checklist, be sure to make the following selections:\na.Specify the properties for this deployment (name, description, and optional category).\nb.Select the software to deploy.\nFor this step, select the Portable Software Instance  button and select your package.\nc.Select the objective for this deployment to indicate where and how you want to install the selected portable\nsoftware instance.\nFor this step, indicate that you want to create a software instance and specify the global zone CSI and the system\nwhere the target software instance will reside.\nd.Check for missing SYSMODs and view missing SYSMOD reports.\nFor this step, deselect the following report options:\n\u2022Requisite SYSMODs and Fix Categories reports\n\u2022Regressed SYSMODs and HOLDDATA Delta reports\ne.Configure this deployment to define the target software instance.\n\u2022For DLIBs , specify Yes to copy the distribution zones and libraries that are associated with the source software.\nYou can customize the names and the storage class or volumes of the new data sets.\n\u2022For Model , indicate The source software  to use as a model. z/OSMF uses the data sets, volumes, mount", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "592907dded04-1", "text": "points, catalogs, and SMP/E zones that are associated with the model to specify default values for the target\nsoftware instance.\n\u2022For SMP/E Zones , the DLIB and TLIB names do not typically need to be changed.\n\u2022For Data sets , change the target data set name prefix to the one that you want to use for your deployment.\nSpecify a volume or storage class to identify where to create the target data sets.\n\u2022For Catalogs , no action is required assuming that your target data set prefix is defined in a user catalog.\n\u2022For Volumes and Storage Classes, no action is required. A summary is presented of the target data sets to be\ncreated and how much space is required.\n\u2022For Mount Points , review the mount points for the UNIX file system data sets that are included in the target\nsoftware instance. When specifying a new target mount point, retain the static path extension in the path name\nto prevent failures in the configuration workflow. For example, targetpathname .\nNOTE\nIf your product does not include USS directories, ignore this instruction.\nf.Define the job settings to generate JCL to install the software and view the deployment summary. For this step,\nupdate the JOB statement as needed.\nNOTE\nIf the target system for the deployment is in a JES Multi-Access Spool (MAS) and the mount point is only\naccessible from the target system, add a System Affinity (SYSAFF) to the job card to ensure execution\non the system where the zFS resides.\ng.Submit the deployment jobs in sequential order, wait for each job to complete, and then select Refresh  to register\njob completion in z/OSMF.\nA return code of zero is expected.\nWhen all deployment jobs have executed successfully, you have unzipped and renamed the product data sets, and", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "592907dded04-2", "text": "updated the CSI data sets. The product data sets have also been successfully copied and the properties for the\ntarget software instance have been specified.\nh.Execute workflows if any exist for the software being deployed. Most products have at least one of the following\nworkflows:\n 106", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c522b6956a56-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPost SMP/E Workflow\nUpdates the CSI with site-specific external data sets, relinks load modules, and optionally mounts USS\ndirectories.\nNOTE\nIf prompted for the data set name of a load library for an IBM product that is not installed, specify your\ninstalled Common Components and Services  for z/OS CCS_hlq .CAW0CALL data set name.\nBase installation Workflow\nConfigures a new software instance for your product software.\nUpgrade Workflow\nUpdates an existing software instance for your product to a new product release.\nNOTE\nFor a list of products with workflows to complete post-install configuration, see Mainframe Products using\nz/OSMF for Software Management  in the Mainframe Common Maintenance Procedures documentation.\ni.Specify a name and description for the new target software instance.\nThe deployment process is complete. The new software instance is defined to z/OSMF. You are now ready to Import\nProduct Information into z/OSMF before you install product maintenance.\nImport Product Information into z/OSMF\nAs a systems programmer, your responsibilities include maintaining a current repository of acquired product packages\nthat are ready for installation in your mainframe environment. z/OSMF lets you view a consolidated list of the products and\nmaintenance packages that are included in each software instance or portable software instance. You can import product\ninformation for the Broadcom  mainframe products that you have installed on z/OS into z/OSMF. After retrieving the\ninformation, you can use the Products page in the z/OSMF Software Management task to obtain a list of products that are\ncontained in your software instances. This information helps you to determine which products are nearing or have reached\nend of service (EOS) or end of life (EOL) support. This information is useful when planning for future installations and", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c522b6956a56-1", "text": "upgrades. You can also use this information to identify software instances that will be affected by changes to a product.\nThe product information file for Broadcom  mainframe products is stored on the following FTP directory:\nhttps://ftpdocs.broadcom.com/WebInterface/phpdocs/0/MSPSaccount/COMPAT/BroadcomProdInfo.txt\nEnable Secure Downloads\nTo prevent SSL handshake failures when importing product information into z/OSMF, use the following procedure to\nenable secure downloads:\n1.Download the certificate from the following URL:\nhttps://ftpdocs.broadcom.com/WebInterface/redirectFTPDocs.html?path=/cadocs/0/certs/digicert-old/Digi-\nIntermediate.crt\nNote the location on your workstation where the certificate was downloaded.\n2.Upload the certificate as text data to your z/OS system in RECFM=VB and LRECL=84 format.\nIf you use FTP, use the following FTP commands to avoid truncation:\nASCII\nQUOTE SITE WRAP LRECL=84 RECFM=VB\nPUT your_PC_file_name  'your.mvs.dataset.name ' (REPLACE\nquit\n3.Add the certificate to the existing z/OSMF IZUSVR keyring.\nFor ACF2 , specify SET PROFILE(USER) DIV(CERTDATA)\nINSERT CERTAUTH. yourcertname  DSN('your.zos.dataset.name ') -\n  LABEL( yourlabeldescription )\n 107", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "378afedfa077-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCONNECT CERTDATA(CERTAUTH. yourDigicertCAcertname ) KEYRING(IZUSVR.keyr01)\n RINGNAME(IZUKeyring.IZUDFLT) USAGE(CERTAUTH)\nFor Top Secret, specify TSS ADD(CERTAUTH) DIGICERT( yourDigicertCAcertname ) LABLCERT( yourlabelname ) - \nDCDSN('your.zos.dataset.name ') TRUST\n            \nTSS ADD(IZUSVR) KEYRING( zosmfringname ) RINGDATA(CERTAUTH, yourDigicertCAcertname ) -\nUSAGE(CERTAUTH)\nFor IBM RACF, specifyRACDCERT CERTAUTH ADD(' your.zos.dataset.name ') WITHLABEL(' yourlabelname ') TRUST\nRACDCERT ID(IZUSVR) CONNECT(CERTAUTH LABEL('your_digicertCA_label') +\nRING(keyringname ) USAGE(CERTAUTH))\nTo load the contents of this file into z/OSMF, you can:\n\u2022Load the file from the Broadcom  URL\n\u2022Load the file from your local workstation\n\u2022Load the file from a z/OS data set or UNIX file\nAfter the file is loaded, you can then retrieve the product information in z/OSMF from the Products  view in the Software\nManagement task (see Displaying a list of your products in the IBM documentation).\nNOTE\nIf you create software instances or portable software instances in z/OSMF, import the product information file\nagain so that you have current information that is displayed about your installed products. We recommend that\nyou repeat the following procedures on a regular schedule or at least monthly to ensure that you have current\nBroadcom  product information available in z/OSMF. This process ensures that you have access to all product", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "378afedfa077-1", "text": "packages as they become available. For more information, see Retrieving product information from product\ninformation files  in the IBM documentation.\nLoad the File from the Broadcom  URL\nUse the following procedure to load the contents of the Broadcom  product information file into z/OSMF directly from the\nBroadcom  FTP directory.\n1.Log in to the z/OSMF web interface.\n2.Complete either  of the following steps:\n\u2013In the Desktop Interface, select Software Management.\n\u2013In the Classic Interface, select Software , Software Management .\nThe Software Management  dashboard displays.\n3.Select Products .\nThe Products table list  is displayed.\n4.Select Retrieve End of Service Information  from the Actions menu or select the Retrieve End of Service Information\nbutton if available.\nThe Select Product Information File  page displays.\n5.Complete the following steps:\na.Select the option to Select files that reside on or can be accessed by primary system  and select Add from the\nActions drop-down menu under Product Information Files.\nThe Add Product Information File  page is displayed.\nb.Select URL and then specify the following URL in the URL field.\nhttps://ftpdocs.broadcom.com/WebInterface/phpdocs/0/MSPSaccount/COMPAT/BroadcomProdInfo.txt\nc.Specify a description in the Description  field.\nd.Select OK.\nThe product information file table is updated with the new URL.\n 108", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "13030238e8d1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n6.Select the new URL and select Retrieve .\nThe contents of the file are loaded into z/OSMF.\nYou can now view the Broadcom  product information that has been retrieved from the Software Management dashboard.\nLoad the File from Your Local Workstation\nUse the following procedure to load the contents of the Broadcom  product information file into z/OSMF from your local\nworkstation.\n1.Download the product information file from the following Broadcom  FTP directory to your local workstation using your\nWeb Browser or an FTP client:\nhttps://ftpdocs.broadcom.com/WebInterface/phpdocs/0/MSPSaccount/COMPAT/BroadcomProdInfo.txt\n2.Log in to the z/OSMF web interface.\n3.Complete either  of the following steps:\n\u2013In the Desktop Interface, select Software Management.\n\u2013In the Classic Interface, select Software , Software Management .\nThe Software Management  dashboard displays.\n4.Select Products .\nThe Products table list  displays.\n5.Select Retrieve End of Service Information  from the Actions menu.\nThe Select Product Information File  page displays.\n6.Select the option to Select a file that resides on your local workstation , enter your file name and description, and\nselect Retrieve .\nThe contents of the file are loaded into z/OSMF.\nYou can now view the Broadcom  product information that has been retrieved from the Software Management dashboard.\nLoad the File from a z/OS Data Set or UNIX File\nUse the following procedure to load the contents of the Broadcom  product information file into z/OSMF from a z/OS data\nset or UNIX file that the primary z/OSMF host can access.\n1.Use FTP to download the product information file directly to the mainframe.\nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "13030238e8d1-1", "text": "1.Use FTP to download the product information file directly to the mainframe.\nNOTE\nUpload the file with binary in the FTP JCL so that the file is not converted to the EBCDIC character set.\nSample JCL follows that you can customize and execute:\n//FTPSTEP  EXEC PGM=FTP,PARM='(EXIT=08' \n//SYSTCPD  DD DSN= your_TCP/IP_data_set_name ,DISP=SHR \n//SYSPRINT DD SYSOUT=* \n//OUTPUT   DD SYSOUT=* \n//INPUT    DD * \nftp.broadcom.com 21 \nanonymous email_address  \ncd /pub/MSPSaccount/JSON/ \ndir \nasc \nlocsite LR=80 REC=FB BLOCKSI=0 \nlocsite PRI=20 SEC=10 CY \nget BroadcomProdInfo.txt ' z/OS_data_set ' (REPLACE\nyour_TCP/IP_data_set_name\nSpecify the TCP/IP stack for an external network.\n 109", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "13287769b9b3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nemail_address\nSpecify your valid email address.\nz/OS_data_set\nSpecify the z/OS data set name where you want to save the product information file. If the specified data set does\nnot exist, it is created during the download process.\n2.Log in to the z/OSMF web interface.\n3.Complete either  of the following steps:\n\u2013In the Desktop Interface, select Software Management.\n\u2013In the Classic Interface, select Software , Software Management .\nThe Software Management  dashboard displays.\n4.Select Products .\nThe Products table list  displays.\n5.Select Retrieve End of Service Information  from the Actions menu or select the Retrieve End of Service Information\nbutton if available.\nThe Select Product Information File  page displays.\n6.Complete the following fields:\na.Select the option to Select files that reside on or can be accessed by primary system  and select Add from the\nActions drop-down menu under Product Information Files.\nThe Add Product Information File  page displays.\nb.Select Primary z/OSMF system  and specify the z/OS_data_set_name  in the Data set or UNIX file  field.\nThe primary z/OSMF host system must be able to access the specified data set or UNIX file.\nc.Specify a description in the Description  field and select OK.\nThe product information file table is updated with the new URL.\n7.Select the new URL and select Retrieve .\nThe contents of the file are loaded into z/OSMF.\nYou can now view the Broadcom  product information that has been retrieved from the Software Management  dashboard.\nInstall Products Using CSM\nReview the following high-level process for installing product software using CSM .\nAs a systems programmer, you can acquire, install, and deploy your mainframe product software on z/OS systems using", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "13287769b9b3-1", "text": "CSM . CSM  simplifies and unifies the management of your Broadcom  mainframe products on z/OS systems. You can use\nCSM  to manage your product software in a common way according to industry best practices. You can also obtain and\napply corrective and recommended maintenance easier. A web-based interface lets you install and maintain your products\nfaster and with less chance of error.\nWARNING\nAs part of our ongoing commitment to customer success and to help our customer base achieve their\nstrategic business initiatives, we are investing our resources in z/OSMF for software management. We will\nbe discontinuing technical support for CSM . In accordance with the terms and conditions, guidelines, and\nparameters of Broadcom\u2019s support program, which is documented in the Broadcom Software Maintenance\nPolicy Handbook , this announcement provides written notification of End of Life for CSM . This notification means\nthat CSM  will no longer be enhanced and maintenance and technical support, including self-service support, will\nbe discontinued effective June 30, 2023 . For full details, see the End of Life Announcement.\nIf you do not have CSM  installed, download it from Broadcom Support .\nWARNING\nTo install a product using CSM , you must  modify the SYSPRINT size. The default allocation of 30 cylinders is\ninsufficient to complete the installation. Increase the allocation parameters of the SYSPRINT data set to at least\n120 cylinders.\n 110", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "37ebc3d7a955-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse the following topics to guide you through the product installation process using CSM :\n\u2022Acquire Your Products Using CSM\n\u2022Install Your Products Using CSM\nNOTE\nBefore you begin this process, review the installation best practices and verify that the installation requirements\nin Prepare for Installation have been met.\nWhen these steps are completed, you are ready to install preventive maintenance.\nAcquire Your Product Using CSM\nAs a systems programmer, your responsibilities include maintaining an up-to-date repository of acquired product\npackages that are ready for installation in your mainframe environment. CSM  provides a product list that lets you display\nthe list of licensed product installation and maintenance packages and to download these packages. Also, you can update\nthe product list to add external product packages that you acquired outside of CSM  so that they are ready for installation\nusing CSM .\nThe following diagram shows the product acquisition process:\n1.Configure CSM .\n2.Download the product package from Broadcom Support  or add an external product package:\n\u2013Download from Broadcom Support :\na.Update the product list .\nb.Download product packages .\n\u2013Add external product package:\na.Add external product installation packages .\n 111", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b738704f54f8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nb.Add external product maintenance packages .\nAfter you complete this process, the product packages are ready for installation with CSM .\nConfigure CSM\nBefore you start acquiring product packages, configure a Broadcom Support  Online account, a CSM  account, and the\nrequired download settings. If you have previously configured these settings, update the product list .\n1.Start your Web browser, and enter the CSM  access URL, which you can get from your system administrator.\nNOTE\nIf the Notice and Consent Banner appears, read and confirm the provided information.\n2.Enter your z/OS login user name and password, and log in.\nThe initial page appears. You are prompted to perform configuration.\n3.Configure the following settings:\n\u2013Proxies that CSM  uses to communicate with Broadcom Support  Online.\nIf proxies are not used, the following port numbers are used: HTTPS Port Number 443 and FTP Port Number 21.\nWARNING\nIf your site uses proxies, review your proxy credentials on the User Settings , Software Acquisition\npage.\n\u2013The USS path to the temporary directory for downloaded software packages\nIf you do not specify the directory, default settings are used that you can change later.\nNOTE\nThese settings are also available on the System Settings , Software Acquisition  page.\nSelect Next .\nYou are prompted to define your Broadcom Support  account.\n4.Select New.\nYou are prompted for the credentials to use on Broadcom Support .\n5.Specify the credentials, select OK, and then Next .\nYou are prompted to review your user settings. These settings are available on the User Settings  page.\n6.Change the settings or keep the defaults, and then select Finish .\nA dialog opens, which shows the progress of the configuration task.\n7.Select the Settings  tab, and review other settings, as needed.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b738704f54f8-1", "text": "7.Select the Settings  tab, and review other settings, as needed.\nYou have configured CSM  to acquire products.\nUpdate the Product List\nThe product list displays a list of downloadable licensed product packages. To see the current list of available product\npackages for download, update the Available Products tree.\n1.Log in to CSM  using your credentials.\n2.Select the Products  tab.\n3.(Optional) Update the product list only with packages that belong to specific site IDs.\na.Select the Edit button in the Filter  section and associate one or more site IDs to a filter in the Edit Filter  window.\nb.Select the filter in the Filter  section.\nc.Right-click the Products  link at the top of the product tree and select Update Product List .\n4.Select the Update Product List  link in the Actions  section on the left side.\nUpdating of the product list with all products for all site IDs starts.\n 112", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "68ff8af96afc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nIf you updated the product list only for a selected filter, skip this step.\n5.Confirm the update.\nA dialog that shows the progress of the task opens. When the task completes, select Show Results  on the Progress\ntab to close this dialog. The task output browser opens, and you can view the action details. Select Close  to close the\ntask output browser.\nNOTE\nWhile a task is in progress, you can perform other work. Select Hide  to exit the dialog and view the task\nstatus later on the Tasks tab.\nThe product list is updated.\nDownload Product Packages\nYou can download product installation and maintenance packages from the updated product catalog so they are ready for\ninstallation.\n1.Log in to CSM  using your credentials.\n2.Select the Products  tab.\n3.Select the product name on the Available Products tree.\nThe product releases are listed in the Releases  table on the right.\n4.Download product packages by selecting one of the following options:\n\u2013To download product packages for all product releases, right-click the product name in the list, and select Update\nProduct .\n\u2013To download packages only for specific releases, select one or more releases in the Releases  table on the right\nand select the Update Product Releases  link.\n5.View the downloaded packages using either of the following options:\n\u2013To display the downloaded maintenance packages, select the product release icon\nin the product list.\n\u2013To display the downloaded base installation package, select the product gen level icon\nbelow the product release in the product list.\nThe product packages are downloaded and ready for installation.\nAdd External Product Installation Packages\nSometimes you have product installation packages that you downloaded outside of CSM . For example, you do not\nhave an HTTP or an FTP access in your mainframe environment, or the required packages are not available from the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "68ff8af96afc-1", "text": "Broadcom Support  website. You can use CSM  to install these external packages according to your organization policy. If\nyou are using this installation option, first add the external packages to the CSM  software catalog.\n1.Log in to CSM  using your credentials.\n2.Select the Products  tab.\n3.Select the Add Product  link in the Actions  section.\n4.Specify the name, release, and gen level of the product, and select OK.\nThe product is added to the product list.\n5.Select the gen level of the product that you want to download on the product tree.\nThe Base Install Packages  section appears on the right.\n6.Select the Add External Package  button.\n 113", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5d0ad67795c2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n7.Specify one of the following package types and package details, and select OK.\nUNIX File\nAdds an installation package that is located in a USS directory in binary mode.\nFTP File\nAdds a product package that is not published on Broadcom Support . For example, a beta version of a product.\nSpecify the FTP host, FTP port, FTP path, package name, and the user name and password to access the FTP\nlocation.\n8.Refresh the page to see the added product package.\nThe product installation package is now listed in the product list and is available for installation with CSM .\nAdd External Product Maintenance Packages\nSometimes you have maintenance packages, for example, unpublished maintenance or a program temporary fix (PTF),\nthat you downloaded outside of CSM . You can use CSM  to install these external maintenance packages per your\norganization policy. For this installation option, first add the packages to the CSM  software catalog.\nUsually, the maintenance is placed as a single package. However, some Broadcom  products have older aggregated\nmaintenance packages that were released before December 31, 2013. An aggregated package  is a file that comprises\nseveral single maintenance packages (nested packages). When you add an aggregated package, CSM  inserts all the\nnested packages and the aggregated package itself. In the list of maintenance packages, the aggregated package is\nmarked with the CUMULATIVE type.\n1.Log in to CSM  using your credentials.\n2.Select the Products  tab.\n3.Select the product release for which the maintenance applies.\nThe maintenance packages for the release are listed.\n4.Select the Add External Maintenance  button.\nYou are prompted to specify the package.\n5.Specify one of the following package types and package details:\nData Set", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5d0ad67795c2-1", "text": "5.Specify one of the following package types and package details:\nData Set\nAdds a maintenance package that is located in a z/OS data set with a logical record length of 80 and with a record\nformat of fixed blocks.\nUNIX File\nAdds a maintenance package that is located in a USS directory in binary mode.\nFTP File\nAdds a maintenance package that is not published on Broadcom Support . This option is intended for downloading\na PTF to validate it. Specify the FTP host, FTP port, FTP path, maintenance package name, and the user name\nand password to access the FTP location.\nSolution\nAdds a published solution from Broadcom Support .\n6.Refresh the page to see the added maintenance package.\nThe product maintenance package is now listed in the product catalog and is available for installation with CSM .\nYou completed the acquisition process. The product packages are ready for installation with CSM .\nInstall Your Product Using CSM\nAs a systems programmer, your responsibilities include installing products in your z/OS environment using CSM . This step\nof the installation process creates or updates the SMP/E environment (global, target, and distribution zones).\nThe following diagram shows the major steps to install your product using CSM .\n 114", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "56ee29cb92c3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n1.(Optional) Configure base installation settings .\n2.(Optional) Configure a working set of SMP/E environments .\n3.Initiate product installation  and review product information .\n4.Select an installation type .\n5.Review installation prerequisites  if any are presented.\n6.Take one of the following steps to select an SMP/E environment :\n\u2013Create an SMP/E environment :\na.Set up the global zone .\nb.Create a target zone .\nc.Create a distribution zone .\n\u2013Use an existing SMP/E environment from your working set:\na.Update the global zone .\nb.Set up the target zone: Either create a target zone  or use an existing target zone .\nc.Set up the distribution zone: Either create a distribution zone  or use an existing distribution zone .\nNOTE\nIf you install a product or its components into an existing target or distribution zone, older versions are\ndeleted from the zone and associated data sets. Use new target and distribution zones for this installation.\nDoing so means that you can apply maintenance to your current version, if necessary.\n 115", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "76eab2c5fecc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n7.Review the installation summary and start the installation .\nConfigure Base Installation Settings\nYou can configure base installation settings on the System Settings, Software Installation page.\n1.Select the Settings  tab, and select the Software Installation link under System Settings in the Settings section on the\nleft side.\n2.In the SIS Base Install - File System  section, select the file system type that is used when installing a product that\nallocates file systems. If you select Product Specific File System , the file system that is used for installing a product\nis defined according to the product metadata. Otherwise, the product metadata is overwritten.\n3.In the Execute Checks During Base Installation  section, configure the following settings by selecting or clearing\ncorresponding checkboxes:\nExecute Apply Check During Base Installation\nVerifies that all requirements for the Apply step are satisfied before the Apply step executes. If the Apply Check\nstep fails, installation stops and all the previous steps are undone.\nSuspend Base Installation After Apply Check\nSuspends the base installation process after Apply Check is completed and generates pending installation actions\nfor the SMP/E environment where the product is being installed. This check box is enabled if you enable the\nExecute Apply Check During Base Installation  checkbox.\nExecute Accept Check During Base Installation\nVerifies that all requirements for the Accept step are satisfied before the Accept step executes. If the Accept\nCheck step fails, installation stops and all the previous steps are undone.\nSuspend Base Installation After Accept Check\nSuspends the base installation process after Accept Check is completed and generates pending installation\nactions for the SMP/E environment where the product is being installed. This check box is enabled if you enable\nthe Execute Accept Check During Base Installation  checkbox.\n4.Select Apply .\nA dialog that shows the progress of the task opens. When the task completes, select Show Results  on the Progress", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "76eab2c5fecc-1", "text": "tab to close this dialog. The task output browser opens, and you can view the action details.\nWhile a task is in progress, you can perform other work. Select Hide  to exit the dialog and view the task status later on\nthe Tasks tab.\nThe base installation settings are configured.\nNOTE\nIf you configure the base installation settings to execute checks during base installation, CSM  creates a pending\ninstallation for the SMP/E environment. For more information about the pending installation, see the CSM  online\nhelp.\nConfigure a Working Set of SMP/E Environments\nIf you plan to install a product in an existing SMP/E environment, add this SMP/E environment to your working set. A\nworking set  is a selected group of SMP/E environments with which you want to work. Although you can have only one\nworking set, you can have as many SMP/E environments in it as you need.\nCSM  does not have a default working set.\nIf you do not have the SMP/E environment in your working set, you can only create a new SMP/E environment during\nproduct installation. In this case, exit the installation wizard, configure your working set and then restart the wizard.\n1.Select the SMP/E Environments  tab, and select the SMP/E environments that you want to include in a working set.\nAn information text area under the list of SMP/E environments displays the number of environments you selected.\n 116", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "631c3b752604-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n2.Select Use as Working Set.\n3.Select OK.\nThe working set is configured.\nThe new working set replaces a previously defined working set.\nYou can display only those SMP/E environments that are in your working set by selecting Show Working Set Only.\nInitiate Product Installation\nYou can install a downloaded product from the Products  tab. The process starts a wizard that guides you through the\ninstallation. At the end of the wizard, a task dynamically invokes the SMP/E and other utilities that are required to install\nthe product.\n1.Select the Products  tab.\n2.Perform one of the following steps:\n\u2013If the package was acquired using CSM :\nFrom the product list on the left side, select the required product gen level (the innermost level in the product list\nunder the release level of a product; for example, SP0 or 0110). Locate the product package that you want to install,\nselect Actions  to the right of the package, and select Install.\n\u2013If the package was acquired outside of CSM :\nIn the Actions section in the left pane, select the Install External Package link. Enter the location of the package.\nSelect OK.\nThe Introduction step of the wizard appears where you can Review Product Information .\nReview Product Information\nReview the information about the product that you are installing.\n1.On the Introduction  step, review the information about the installation.\nIf the product license agreement appears, review it. If you agree, accept it. If you do not accept the license agreement,\nyou cannot proceed with the installation.\n2.Select Next .\nYou are prompted to select the type of installation .\nAn information text area can appear at the bottom of the wizard. The area provides information that helps you progress", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "631c3b752604-1", "text": "through the wizard. For example, if a field is highlighted (indicating an error), the information text area identifies the\nerror.\nSelect an Installation Type\nWhen you install a product, you select an installation type. There can be one or more installation types, according to the\nproduct.\nWhen you select the custom installation type, you are prompted to select the features that you want to install. If your\nselected features require installation of other features, the installation wizard includes the required features to the\ninstallation process. If your selected features are mutually exclusive, the installation wizard excludes any features\nconflicting with the features you selected last from the installation process. For example, you select feature 1 and select\nfeature 2 that is mutually exclusive with feature 1. The wizard automatically excludes feature 1.\n1.On the Features  step, select the type of installation, and select Next .\n2.(Optional) If you select the custom installation type, select the features to install, and select Next .\nA summary of the features to install appears, with prerequisites .\n 117", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2e61fa97c2e4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReview Installation Prerequisites\nSome products require an installation of other products first.\nReview the summary of installation prerequisites to verify that all prerequisites are satisfied on the Prerequisites  step.\n\u2022If no prerequisites exist, select Next .\nYou are prompted to select an SMP/E environment for the installation .\n\u2022If all prerequisites exist and are satisfied, you are prompted to locate the installed prerequisites.\nInstall the product to the same SMP/E environment and the target zone where the product prerequisites are installed.\na.From the SMP/E environment  drop-down list, select an SMP/E environment with the installed prerequisites. This\ndrop-down list represents all CSM -managed SMP/E environments where the prerequisites are installed.\nA list of target zones for the selected SMP/E environment where the prerequisites are installed is populated.\nb.From the target zone  drop-down list, select a target zone within the selected SMP/E environment where the\nprerequisites are installed.\nc.Select Next .\nYou are prompted to confirm the selected SMP/E environment for the installation .\n\u2022If prerequisites are not satisfied, perform one of the following actions:\n\u2013Select Cancel  to exit the wizard. Install the prerequisites or migrate an SMP/E environment to CSM  where the\nprerequisites are installed. Restart the installation.\n\u2013Open CSM  in another browser window and install the prerequisites, or migrate an SMP/E environment to CSM\nwhere the prerequisites are installed. When done, select Refresh  on the Prerequisites  step of the wizard. Then,\nselect the SMP/E environment and a target zone where the prerequisites are installed. Select Next  to continue the\nproduct installation.\nYou are prompted to confirm the selected SMP/E environment for the installation .\nSelect an SMP/E Environment\nYou select the SMP/E environment where you want to install your product in. You can create an SMP/E environment, or", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2e61fa97c2e4-1", "text": "you can select an existing SMP/E environment from your working set. You can configure your working set  from the SMP/E\nEnvironments tab.\nWhile you work with an SMP/E environment, the environment is locked and other CSM  users cannot perform any action\nagainst it. When the task finishes, logging out from CSM , or a CSM  session is inactive for more than 10 minutes, the lock\nreleases.\nIf you select an SMP/E environment being used in CSM  by another user, a notification message appears. You are\nprevented from performing any actions on the SMP/E environment. You can wait until the notification message disappears\nand the SMP/E environment becomes available or can select Cancel to select another SMP/E environment.\n1.On the SMP/E Environment  step, substep 1, take one of the following steps:\n\u2013Select Create a New SMP/E Environment  to create an SMP/E environment.\n\u2013Select an existing SMP/E environment from your working set.\n\u2022If no existing SMP/E environment appears, exit the wizard, configure your working set , and restart the wizard .\n\u2022If your product has the installed prerequisites , the SMP/E environment with the installed prerequisites that\nyou selected at the Prerequisites  step of the wizard is preselected for you. You cannot select another SMP/E\nenvironment. You cannot create a SMP/E environment.\nNOTE\nWhen you install a product in an existing SMP/E environment where HOLDDATA is received, the\nproduct installation may fail.\n2.Select Next .\nYou are prompted to complete one of the following tasks:\n 118", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b65fd9310612-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Create an SMP/E environment\n\u2022Review parameters of an existing SMP/E environment .\nCreate an SMP/E Environment\nYou can create an SMP/E environment while you are installing a product. During the process, you are asked to specify the\nfollowing information:\n\u2022The SMP/E environment name and the prefix of the CSI data set in CSM\n\u2022Data set allocation parameters\nYou can specify data set allocation parameters collectively for all SMP/E data sets, target libraries, and distribution\nlibraries that are allocated during product installation. You allocate data sets using one of the following methods:\n\u2022Allocate data sets using SMS parameters.\n\u2022Allocate cataloged data sets using UNIT and optionally VOLSER.\n\u2022Allocate uncataloged data sets using UNIT and VOLSER.\nIf you allocate uncataloged data sets, specify a VOLSER. Based on the value that you enter, CSM  performs the following\nvalidations to ensure integrity of the installation:\n\u2022The value of VOLSER must specify a mounted volume.\n\u2022You must have ALTER permissions for the data sets with the entered high-level qualifier (HLQ) on the volume that\nVOLSER defines.\n\u2022To test allocation, CSM  temporarily allocates one of the uncataloged data sets that are allocated during the installation.\na.The data set is allocated with one track for both primary and secondary space.\nb.CSM  verifies that the data set has been allocated on the specified volume.\nc.The data set is deleted.\nIf the data set allocation fails or the data set cannot be found on the specified volume, you cannot proceed with the\nproduct installation wizard.\n1.On the SMP/E Environment  step, substep 2, review and specify the following parameters as applicable:\nSMP/E Environment Name\nDefines the SMP/E environment name.\nData Set Name Prefix", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b65fd9310612-1", "text": "SMP/E Environment Name\nDefines the SMP/E environment name.\nData Set Name Prefix\nDefines the prefix for the name of the CSI VSAM data set.\nCatalog\nDefines the name of the SMP/E CSI catalog.\nCross-Region\nIdentifies the cross-region sharing option for SMP/E data sets. This parameter is set to its default value. You\ncannot edit it.\nCross-System\nIdentifies the cross-system sharing option for SMP/E data sets. This parameter is set to its default value. You\ncannot edit it.\nHigh-Level Qualifier\nSpecifies the high-level qualifier (HLQ) for all SMP/E data sets that are allocated during installation. Product\npackaging defines the low-level qualifiers (LLQ). The low-level qualifiers cannot be changed.\nDSN Type\nSpecifies the DSN type for allocating SMP/E data sets.\n 119", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c1cacbea3d3a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSMS Parameters / Data Set Parameters\nSpecifies if this SMP/E environment is using SMS parameters (Storage Class, Management Class, Data Class) or\ndata set parameters (VOLSER, Unit, Catalog).\nAn information text area can appear at the bottom of the wizard. The area provides information that helps you progress\nthrough the wizard. For example, if a field is highlighted (indicating an error), the information text area identifies the\nerror.\n2.Select Next.\nWork DDDEF allocation parameters and a list of the data sets to be created for the SMP/E environment appear.\nReview Parameters of an Existing SMP/E Environment\nWhen you use an existing SMP/E environment to install your product, you review the SMP/E environment parameters.\nIf applicable, you also specify parameters for any new data sets to be allocated while installing a product. During the\nprocess, you are asked to review allocation parameters for new data sets, which you can customize for each data set. The\nexisting data sets remain intact.\nThe Software Installation Service (SIS) determines which data sets exist and which must be allocated for the installation\nusing an existing SMP/E environment. If the SIS determines that new data sets must be allocated, you are prompted to\nspecify the data set allocation parameters. The data set allocation parameters are prepopulated with the values from the\nexisting data set that was found first.\n1.On the SMP/E Environment  step, substep 2, review the current SMP/E environment parameters and allocation\nparameters for data sets that must be added to the SMP/E environment. Update the information as applicable.\n2.Select Next .\nWork DDDEF allocation parameters and a list of the data sets to be created for the SMP/E environment, if any,\nappear .\nSet Up SMP/E Environment Parameters\nWhen creating an SMP/E environment for your product installation, you specify SMP/E environment parameters.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c1cacbea3d3a-1", "text": "When creating an SMP/E environment for your product installation, you specify SMP/E environment parameters.\nWhen using an existing SMP/E environment for installing your product, you review and, if necessary, update its SMP/E\nenvironment parameters.\nYou can assign different prefixes to each newly allocated data set during the installation process.\n1.On the SMP/E Environment step, substep 3, specify whether to use SMS parameters (Storage Class, Management\nClass, Data Class) or Unit parameters for allocating work DDDEFs for the SMP/E environment. Complete the\nappropriate fields.\nThe allocation parameters that you specify for work DDDEFs are applied only to new work DDDEFs that are created\nduring the installation. The existing work DDDEFs, if any, remain intact.\nNOTE\nThe settings for allocating work DDDEFs are globally defined on the System Settings, Software\nInstallation  tab. You must have the appropriate access rights to be able to modify these settings.\n2.Review the data set names if any appear. Select the Override link to change the high-level qualifier of the data set\nname and the allocation parameters. Select OK.\n3.(Optional) If any additional parameters appear, review the parameters that have the default values assigned. Edit the\nparameters if necessary and specify any missing parameters.\n4.Select Next .\nYou are prompted to select a target zone to use .\n 120", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7a77866288c9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSelect a Target Zone\nYou select a target zone in the SMP/E environment where you want to install your product. You create a target zone or\nselect an existing target zone in the SMP/E environment (if you use an existing SMP/E environment).\n1.On the Target Zone step, substep 1, perform one of the following actions:\n\u2013Select Create a New Target Zone to create a target zone.\n\u2013Select an existing target zone in the SMP/E environment.\nThis option is available only if you selected to use an existing SMP/E environment.\nWARNING\n\u2022If you install a product or its components into an existing target or distribution zone, older versions are\ndeleted  from the zone and associated data sets. Use new target and distribution zones for this installation\nso that you can apply maintenance to your current version, if necessary.\n\u2022If your product has the installed prerequisites , the target zone of the SMP/E environment with the installed\nprerequisites that you selected at the Prerequisites  step of the wizard is preselected for you. You cannot\nselect another target zone. You cannot create a target zone.\n2.Select Next .\nYou are prompted to create a target zone  or use an existing target zone .\nCreate a Target Zone\nYou can create a target zone in a new or an existing SMP/E environment where you install your product. The target zone\nparameters are prepopulated with the values that are entered for the SMP/E environment. You can change data set\nallocation parameters.\nYou can specify a different SMP/E environment data set to be used for a new target zone.\n1.On the Target Zone step, substep 2, review and specify the target zone SMP/E parameters as applicable.\nTarget Zone Name\nDefines the name for the target zone.\nCreate New CSI Data Set\nSpecifies that a new CSI data set will be created for the target zone.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7a77866288c9-1", "text": "Specifies that a new CSI data set will be created for the target zone.\nData Set Name Prefix\nDefines the prefix for the name of the target zone data set. This field is only enabled when you have selected the\nCreate New CSI Data Set  check box.\nCatalog\nDefines the name of the SMP/E target zone catalog. This field is only enabled when you have selected the Create\nNew CSI Data Set  check box.\nCross-Region\nIdentifies the cross-region sharing option for SMP/E data sets. This parameter is set to its default value. You\ncannot edit it.\nCross-System\nIdentifies the cross-system sharing option for SMP/E data sets. This parameter is set to its default value. You\ncannot edit it.\nHigh-Level Qualifier\nSpecifies the high-level qualifier (HLQ) for all target zone data sets that are allocated during installation. Product\npackaging defines the low-level qualifiers (LLQ) and they cannot be changed.\nDSN Type\nSpecifies the DSN type for allocating target zone data sets.\n 121", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ea8b1c91e0be-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSMS Parameters / Data Set Parameters\nSpecifies if this target zone uses SMS parameters (Storage Class, Management Class, Data Class) or data set\nparameters (VOLSER, Unit, Catalog).\nAn information text area can appear at the bottom of the wizard. The area provides information that helps you progress\nthrough the wizard. For example, if a field is highlighted (indicating an error), the information text area identifies the\nerror.\n2.Select Next .\nA list of the data sets to be created for the target zone appears .\nUse an Existing Target Zone\nWhen using an existing target zone for installing your product, you review and, if necessary, update its parameters.\n1.On the Target Zone step, substep 2, review the current target zone parameters and allocation parameters for data\nsets that must be added. Update as applicable.\nNOTE\nYou cannot change the current SMP/E environment parameters.\n2.Select Next .\nIf there are any data sets to be created for the target zone, a list of data sets appears . If the list is empty, no new data\nsets are going to be allocated.\nSet Up Target Zone Parameters\nWhen creating a target zone in the SMP/E environment for your product installation, specify target zone parameters.\n1.On the Target Zone step, substep 3, review the data set names if any appear. Select the Override  link to change the\nhigh-level qualifier of the data set name and the allocation parameters. Select OK.\n2.(Optional) If more parameters appear, review the parameters that have the default values assigned. Edit the\nparameters if necessary and specify any missing parameters.\n3.Select Next .\nYou are prompted to confirm the distribution zone .\nConfirm a Distribution Zone\nYou must confirm a distribution zone of the SMP/E environment where you want to install your product. Depending on", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ea8b1c91e0be-1", "text": "whether you created a target zone or you selected an existing target zone, create a distribution zone or select an existing\ndistribution zone in the SMP/E environment.\n1.On the Distribution Zone  step, substep 1, review the selected option for the distribution zone.\n\u2013If you are using an existing target zone, the related distribution zone is automatically selected. You cannot select\nother distribution zones or cannot create one.\nNOTE\nIf you install a product or its components into an existing target or distribution zone, older versions are\ndeleted from the zone and associated data sets. Use new target and distribution zones for this installation\nso that you can apply maintenance to your current version, if necessary.\n\u2013If you are creating a target zone, you can create a distribution zone or you can select an existing distribution zone.\nNOTE\nUsing an existing distribution zone with a new target zone relates the existing distribution zone to the\nnew target zone. This action breaks the relationship from the previous target zone that was related to\n 122", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e1f8d039ed5b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nthis distribution zone. You cannot accept maintenance packages from the previous target zone to this\ndistribution zone using CSM .\n2.Select Next .\nYou are prompted to set up the distribution zone.\nCreate a Distribution Zone\nYou can create a distribution zone that is related to the newly created target zone. The distribution zone parameters are\nprepopulated with the values that are entered for the SMP/E environment. You can change data set allocation parameters.\nYou can specify a different SMP/E environment data set to be used for the new distribution zone.\nYou can also specify the same SMP/E environment data set as the one that you specified for the target zone. In that case,\nthe target and distribution zones share the SMP/E environment data set. The SMP/E environment data set is allocated\nusing the parameters that you have defined when specifying the target zone.\n1.On the Distribution Zone  step, substep 2, review and specify the following parameters as applicable:\nDistribution Zone Name\nDefines the name for the distribution zone.\nCreate New CSI Data Set\nSpecifies that a new CSI data set is created for the distribution zone.\nData Set Name Prefix\nDefines the prefix for the name of the distribution zone data set. This field is only enabled when you have selected\nthe Create New CSI Data Set  check box.\nCatalog\nDefines the name of the SMP/E distribution zone catalog. This field is only enabled when you have selected the\nCreate New CSI Data Set  check box.\nCross-Region\nIdentifies the cross-region sharing option for SMP/E data sets. This parameter is set to its default value. You\ncannot edit it.\nCross-System\nIdentifies the cross-system sharing option for SMP/E data sets. This parameter is set to its default value. You\ncannot edit it.\nHigh-Level Qualifier", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e1f8d039ed5b-1", "text": "cannot edit it.\nHigh-Level Qualifier\nSpecifies the high-level qualifier (HLQ) for all distribution zone data sets that are allocated during installation.\nProduct packaging defines the low-level qualifiers (LLQ) that cannot be changed.\nDSN Type\nSpecifies the DSN type for allocating distribution zone data sets.\nSMS Parameters / Data Set Parameters\nSpecify if this distribution zone is to use SMS parameters (Storage Class, Management Class, Data Class) or\ndata set parameters (VOLSER, Unit, Catalog). Complete the applicable fields.\nAn information text area can appear at the bottom of the wizard. The area provides information that helps you progress\nthrough the wizard. For example, if a field is highlighted (indicating an error), the information text area identifies the\nerror.\n2.Select Next .\nA list of the data sets to be created for the distribution zone appears .\n 123", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9dc1a4451011-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse an Existing Distribution Zone\nYou can use an existing distribution zone that is related to the existing target zone you selected, or with a new target zone.\nThe distribution zone parameters are prepopulated with the values that are entered for the SMP/E environment. You can\nchange data set allocation parameters.\nNOTE\nUsing an existing distribution zone with a new target zone relates the existing distribution zone to the new target\nzone. This action breaks the relationship from the previous target zone that was related to this distribution zone.\nYou cannot accept maintenance packages from the previous target zone to this distribution zone using CSM .\n1.On the Distribution Zone  step, substep 2, review the current distribution zone parameters and allocation parameters\nfor data sets that you want to add. Update as applicable.\nNOTE\nYou cannot change the current SMP/E environment parameters.\n2.Select Next .\nIf there are any data sets to be created for the distribution zone, a list of data sets appears . If the list is empty, no new\ndata sets are going to be allocated.\nSet Up Distribution Zone Parameters\nWhen creating a distribution zone in the SMP/E environment where you want to install your product, specify distribution\nzone parameters.\n1.On the Distribution Zone  step, substep 3, review the data set names if any appear. Select the Override  link to\nchange the high-level qualifier of the data set name and the allocation parameters. Select OK.\n2.(Optional) If any additional parameters appear, review the parameters that have the default values assigned. Edit the\nparameters if necessary and specify any missing parameters.\n3.Select Next .\nYou see a summary of the installation task .\nStart the Installation\nAfter you complete setting up the SMP/E environment and its zones, you are ready to start the installation.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9dc1a4451011-1", "text": "To start the installation, review the summary on the Summary  step, and select Install .\nA dialog that shows the progress of the task opens. When the task completes, Select Show Results  on the Progress  tab\nto close this dialog. The task output browser opens, and you can view the action details.\nWhile a task is in progress, you can perform other work. Select Hide  to exit the dialog and view the task status later on the\nTasks tab.\nYou completed the product installation. You can now start maintaining the installed products.\nInstall Products Using SMP/E JCL\nAs a systems programmer, your responsibilities include installing products on your mainframe system. With this option,\nyou acquire a product pax file and the latest product updates from Broadcom Support  and then install, maintain,\ndeploy, and configure the products on your systems. Batch jobs are provided to create the SMP/E environment. A basic\nunderstanding of UNIX System Services (USS) is required.\nNOTE\nBefore you begin this process, review the installation best practices and verify that the installation requirements\nin Prepare for Installation have been met.\n 124", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9e97e35256f7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nYou perform the following tasks to install a product with a pax file:\nWhen these steps are completed, you are ready to install preventive maintenance.\nUNIX System Services Environment\nYou need a UNIX System Services (USS) directory and a file system with adequate space to perform the following tasks:\n\u2022Receive product pax files from Broadcom Support .\n\u2022Perform utility functions to unpack the pax file into z/OS data sets that you can use to complete the product installation.\nWe recommend that you allocate and mount a dedicated file system for this process. The amount of space that you need\nfor the file system depends on the following variables:\n\u2022The size of the pax files that you intend to download.\n\u2022Whether you plan to keep the pax files after unpacking them. We do not recommend this practice.\nWe recommend that you use one directory for downloading and unpacking pax files. Reusing the same directory\nminimizes USS setup. Complete the USS setup only one time. You reuse the same directory for subsequent downloads.\nAlternatively, you can create a directory for each pax download.\nWARNING\nDownloading pax files for the SMP/E installation requires write authority to the USS directories that are used\nfor the native SMP/E JCL installation process. In the file system that contains the pax directories, you also\nneed free space approximately 3.5 times the pax file size to download the pax file and unpack its contents. For\nexample, to download and unpack a 14-MB pax file, you need approximately 49 MB of free space in the file\nsystem hosting your pax directory.\n 125", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d4068eb8f7c6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAllocate and Mount a File System\nThe product installation process requires a UNIX System Services (USS) directory to receive the pax file and to perform\nthe unpack steps. We recommend that you allocate and mount a file system that is dedicated to the product acquisition.\nWe also recommend that you create a directory in this file system where the pax file will be located. This directory\n(yourUSSpaxdirectory) is used later in the installation process when acquiring and unpacking the product pax file.\nNOTE\nTo issue the USS mount command for the file system, read access is required to the SAF resource name\nSUPERUSER.FILESYS.USERMOUNT in the UNIXPRIV class.\n1.Allocate the zFS by customizing the following sample JCL to your site requirements:\n//DEFINE   EXEC PGM=IDCAMS\n//SYSPRINT DD   SYSOUT=*\n//SYSUDUMP DD   SYSOUT=*\n//AMSDUMP  DD   SYSOUT=*\n//SYSIN    DD *\n  DEFINE CLUSTER ( +\n  NAME(YOUR_ZFS_DATA_SET_NAME ) +\n  STORAGECLASS( class) +\n  LINEAR +\n  CYL(primary secondary ) +\n  SHAREOPTIONS(3 3) +\n  )\n/*\n//FORMAT   EXEC PGM=IOEAGFMT,REGION=0M,\n// PARM=('-aggregate YOUR_ZFS_DATA_SET_NAME  -compat')\n//SYSPRINT DD   SYSOUT=*\n//SYSUDUMP DD   SYSOUT=*\n//STDOUT   DD   SYSOUT=*\n//STDERR   DD   SYSOUT=*\n//CEEDUMP  DD   SYSOUT=*\n//*\n\u2013Add a JOB card.\n\u2013Issue the NUM ON  command followed by UNNUM to edit the JCL with number off (no sequence numbers in columns", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d4068eb8f7c6-1", "text": "73 through 80).\n\u2013Issue the CAPS OFF  command. However, where needed, use uppercase and lowercase values. For example,\nYOUR_ZFS_DATA_SET_NAME  must be uppercase and aggregate  and compat  must be lowercase.\n\u2013Ensure the the zFS data set name that you use conforms to your data set naming conventions for USS file\nsystems.\nIf the allocation of the file system data set fails, it is because of environmental settings now allowing for the\nallocation.\n\u2013Ensure that the SYSIN DD is indented at least one space.\nWhen these edits are complete, the zFS is allocated.\n2.Create a mount point for the file system. This example shows how to create your USS pax directory named\nyourdirectory /PAX in the existing /u/maint directory. From the TSO OMVS shell, enter the following commands:\ncd /u/maint/\nmkdir yourdirectory\ncd yourdirectory\nmkdir PAX\nFurther references to this mount point appear as yourUSSpaxdirectory . You can reuse the same directory for all\nproduct acquisitions to minimize USS setup. Alternatively, you can create a directory for each pax download.\n 126", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "faa07f8050af-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe mount point is created.\n3.Mount the file system by customizing the following sample:\n//MOUNT    EXEC PGM=IKJEFT01,REGION=0M          \n//SYSTSPRT DD SYSOUT=*                        \n//SYSTSOUT DD SYSOUT=*                        \n//SYSTSIN  DD *\nMOUNT FILESYSTEM(' your_zFS_data_set_name ') +\nMOUNTPOINT(' yourUSSpaxdirectory ') +\nTYPE(ZFS) MODE(RDWR) +\nPARM('AGGRGROW')\n/*\nThe file system is mounted.\n4.(Optional) Set security permissions for the directory. You can permit write access to anyone in the same group as the\nperson who created the directory. For example, to allow write access to the USS pax directory for other users in your\nUSS group, enter the following command from the TSO OMVS shell or the Telnet or SSH client of choice at your site:\nNOTE\nUSS commands are case-sensitive.\nchmod -R 770 / yourUSSpaxdirectory /\nWrite access is granted. Other users can access the USS pax directory and its files.\n5.Verify that the file system is mounted. To do so, enter the following commands from the Telnet or SSH client:\ncd {yourUSSpaxdirectory}\ndf - k .\nThe file system is mounted. The output shows the mount point and the mount data set. Resolve errors before\ncontinuing.\nAcquire the Product Pax Files\nTo begin the product installation procedure, copy the product pax file into the USS directory that you set up.\nNOTE\nTo optimize downloads from Broadcom Support , configure the downloads.broadcom.com URL for HTTPS\nand Secure FTP in your network security software, firewalls, or both. Sites that regulate access through an IP", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "faa07f8050af-1", "text": "address are required to allow network access to 141.202.253.110.\nThis procedure explains how to transfer a product pax file from Broadcom Support  online to the mainframe.\n1.Confirm that you have addressed the following UNIX System Services (USS) requirements:\n\u2013Write authority to the USS directories that are used for the pax installation process.\n\u2013Available USS file space.\nNOTE\nIn the file system that contains the pax directories, you also need free space approximately 3.5 times the\npax file size to download the pax file and unpack its contents. For example, to download and unpack a 14-\nMB pax file, you need approximately 49 MB of free space in the file system hosting your pax directory.\nIf you do not have sufficient free space, error messages similar to the following appear:\nEZA1490I Error writing to data set\nEZA2606W File I/O error 133\n2.Go to Broadcom Support  at https://support.broadcom.com, and select Software , Mainframe Software , and My\nDownloads.\n3.Log in using your Broadcom Support  username and password.\nThe My Downloads  page appears.\n4.Select a product from the list or enter the product name in the Search  field.\n 127", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d203e0edbbf8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe product page appears with two tabs under the product name: Products  and Solutions .\n5.Under Products , select the product that you want to download.\nA list by release, service pack, and language appears.\n6.Click the hypertext link to select a release.\nThe Primary Downloads  page appears. This page shows the available product-specific software packages that you\ncan select to download.\nIf an Additional Downloads  page is available, this page shows additional software packages that are related to your\nproduct selection that you can download. These products may already be installed.\n7.Review the packages that appear under Primary Downloads  and Additional Downloads  and complete the following\nsteps:\na.Select the SMP/E JCL Package  (classic pax) and other files that you want to include in the product download.\nIf more than one package is available, you can only select one.\nb.Select Download Selected , HTTPS Download , or Secure FTP Download . Secure FTP Download is the\npreferred method. For download tips, see Product Download Help . For sample JCL and security requirements, see\nDownload Methods and Locations .\nThe product package is downloaded.\nYou are now ready to extract the contents of the product package into a product directory that you create.\nCreate a Product Directory from the Pax File\nAfter you acquire and download the product package (pax file), you are ready to create a product directory in which to\nextract the contents of the package. You can do so using the pax command or the ESDUNPAX sample JCL.\nUse the pax Command\nTo use the pax command to create a product directory, enter:\ncd /yourUSSpaxdirectory/\npax -rvf pax-filename\nThese commands set the current working directory in your USS directory to the directory containing the pax file and", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d203e0edbbf8-1", "text": "These commands set the current working directory in your USS directory to the directory containing the pax file and\nthen performs the following actions:\n\u2022Extracts the files and directories that are packaged within the pax file.\n\u2022Creates a USS directory in the same directory structure where the pax file resides.\n\u2022Automatically generates a product and level-specific directory name.\nThe product directory is created. You are now ready to copy the sample installation JCL to a z/OS data set.\nUse the ESDUNPAX Sample JCL\nTo use the ESDUNPAX sample JCL to create a product directory, review the following JCL sample and edit it as shown in\nthe procedure that follows:\n//ESDUNPAX JOB ( ACCOUNTNO ),'UNPAX PAX FILE',\n// MSGCLASS=X,CLASS=A,NOTIFY=&SYSUID\n//*********************************************************************\n//* This sample job can be used to invoke the pax command to create   *\n//* the product-specific installation directory.                      *\n//*                                                                   *\n//* This job must be customized as follows:                           *\n//* 1. Supply a valid JOB statement.                                  *\n//* 2. Replace \"yourUSSpaxdirectory\" with the name of the USS         *\n//*    directory used on your system for Pax ESD downloads.           *\n 128", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c5ddbb3fc5fb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n//* 3. Replace \"paxfile.pax.Z\" with the name of the pax file.         *\n//* NOTE: If you continue the PARM= statement on a second line,       *\n//*       start entering characters in column 16 and make sure        *\n//*       the 'X' continuation character is in column 72.     *\n//*********************************************************************\n//UNPAXDIR EXEC PGM=BPXBATCH,\n// PARM='sh cd / yourUSSpaxdirectory /; pax -rvf paxfile.pax.Z '\n//*UNPAXDIR EXEC PGM=BPXBATCH,\n//* PARM='sh cd / yourUSSpaxdirectory /; pax                              X\n//*             -rvf paxfile.pax.Z '\n//STDOUT DD SYSOUT=*\n//STDERR DD SYSOUT=*\nEdit the sample JCL as described in the following steps:\n1.Replace ACCOUNTNO with a valid JOB statement.\n2.Replace yourUSSpaxdirectory  with the name of the USS directory that you use for product downloads.\nThe job points to your specific directory.\n3.Replace paxfile.pax.Z  with the name of the pax file.\nThe job points to your specific pax file.\n4.Submit the job.\nThe job creates the product directory.\nNOTE\nIf the PARM= statement exceeds 71 characters, comment out the first UNPAXDIR. Then uncomment and\nuse the second form of UNPAXDIR instead. This sample job uses an X in column 72 to continue the PARM=\nparameters to a second line.\nThe product directory is created. You are now ready to copy the sample installation JCL to a z/OS data set.\nCopy Installation Files to z/OS Data Sets", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c5ddbb3fc5fb-1", "text": "Copy Installation Files to z/OS Data Sets\nUse this procedure to invoke the SMP/E GIMUNZIP utility to create the SAMPJCL z/OS data set.\nThe file UNZIPJCL in the product directory contains a sample job to extract the installation package. You edit and submit\nthe UNZIPJCL job to copy the sample installation JCL to a z/OS data set.\n1.Locate and read the product readme file or installation notes, if applicable, which resides in the product-specific\ndirectory that the pax command created. This file contains the product-specific details that you require to complete the\ninstallation procedure.\nYou have identified the product-specific installation details.\n2.Use ISPF EDIT or TSO ISHELL to edit the UNZIPJCL sample job. You can perform this step in one of the following\nways:\nUse ISPF EDIT Specify the full path name of the UNZIPJCL file.\nUse TSO ISHELL Navigate to the UNZIPJCL file and use the E line command to edit the file.\nThe job is edited.\n3.Change the SMPDIR DD PATH to the product-specific directory created by the pax command.\nYour view is of the product-specific directory.\n4.If ICSF is not active, perform the following steps:\na.Change the SMPJHOME DD PATH to your Java runtime directory. This directory varies from system to system.\nb.Perform one of the following steps:\n 129", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b64325635c5f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Change the SMPCPATH DD PATH to your SMP/E Java application classes directory, typically /usr/lpp/smp/\nclasses/.\n\u2022Change HASH=YES to HASH=NO on the GIMUNZIP parameter.\nOne of the following outcomes occurs: ICSF is active or you are using Java.\n5.Change yourHLQ  to the high-level qualifier (HLQ) for z/OS SAMPJCL data set.  We suggest that you use a unique\nHLQ for each expanded pax file to identify uniquely the package.\n6.Submit the UNZIPJCL job.\nThe UNZIPJCL job completes with a zero return code. Messages GIM69158I and GIM48101I in the output and\nIKJ56228I in the JES log are acceptable. The SAMPJCL data set is created with the HLQ that you specified in the\nUNZIP job. You use this data set to perform the product installation.\nPrepare the SMP/E Environment for a Pax Installation\nThe members in the following procedure are used to prepare the product data sets, initialize the SMP/E zones, and create\nthe DDDEFs for your product. These steps include:\n\u2022Allocating product and SMP/E data sets, and product USS data sets and directories\n\u2022Creating and customizing the SMP/E CSI\n\u2022(Optional) Customizing the SMP/E CSI for USS\nFor information about the members, see the JCL comments.\n1.Customize the macro AVHSEDIT as follows with your site-specific information:\na.Replace the rightmost parameters for each ISREDIT CHANGE command.\nb.Set the PRODHLQ to the same value specified for yourHLQ  within the JCL that is used to unzip the pax file.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b64325635c5f-1", "text": "c.(Optional) Set the NULLFILE HLQ if applicable and use it for the IMS, HSSR, and CICS DDDEF specifications\nwhen valid system libraries do not exist in your environment. This setting does not apply to every product.\nd.Save your changes and then copy the macro to your SYSPROC location.\nThe macro is ready to customize the yourHLQ .SAMPJCL members.\nWhen you edit an installation member, type AVHSEDIT on the command line, and press Enter to replace the defaults\nwith your specifications.\nNOTE\nThe following steps include instructions to execute the AVHSEDIT macro each time you open a new\nSAMPJCL member. To edit all SAMPJCL members simultaneously, read and follow the instructions in the\nAVHAREAD member, and submit the AVHEDALL member.\n2.Open the SAMPJCL member AVH00ALL in an edit session and execute the AVHSEDIT macro from the command\nline.\nAVH00ALL is customized.\n3.Submit AVH00ALL.\nThis job produces the following results:\n\u2013Creates the target and distribution data sets for your product.\n\u2013Creates unique SMPLTS, SMPMTS, SMPSCDS, and SMPSTS data sets for this target zone.\n4.Complete the following steps if your product requires a zFS file system or if you want to install a feature of the product\nthat requires a zFS file system:\nWARNING\nIf the following members do not exist in SAMPJCL, ignore this step. This step does not apply to your product.\nGo to Step 5.\na.Open the SAMPJCL member AVH03ALU in an edit session and execute the AVHSEDIT macro from the command\nline.\nAVH03ALU is customized.\nb.Submit AVH03ALU.\n 130", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8fe56ec40c6c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThis job allocates your zFS data sets.\nc.Open the SAMPJCL member AVH06MKD in an edit session and execute the AVHSEDIT macro from the command\nline.\nAVH06MKD is customized.\nd.Submit AVH06MKD.\nThis job creates all directories and mounts the file system.\n5.Open the SAMPJCL member AVH10CSI in an edit session and execute the AVHSEDIT macro from the command line.\nAVH10CSI is customized.\n6.Submit AVH10CSI.\nThis job produces the following results:\n\u2013Defines the CSI data set.\n\u2013Allocates the SMPPTS and SMPLOG data sets.\n\u2013Initializes the global, target, and distribution zones.\n\u2013The DDDEF entries for your product are created.\n\u2013The DDDEFs for the required SMP/E data sets are created.\n7.Complete the following steps to add the DDDEFs that are required for the zFS file system to your SMP/E environment:\nWARNING\nIf the following member does not exist in SAMPJCL, ignore this step. This step does not apply to your\nproduct. Go to Run the Installation Jobs for a Pax Installation.\na.Open the SAMPJCL member AVH15CSU in an edit session and execute the AVHSEDIT macro from the command\nline.\nAVH15CSU is customized.\nb.Submit AVH15CSU.\nThis job customizes the CSI by adding the DDDEFs associated with the directory.\nYou are now ready run the installation jobs that are used to receive, apply, and accept SMP/E base functions. Go to Run\nthe Installation Jobs for a Pax Installation.\nRun the Installation Jobs for a Pax Installation", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8fe56ec40c6c-1", "text": "the Installation Jobs for a Pax Installation.\nRun the Installation Jobs for a Pax Installation\nThe members in the following procedure are used to receive, apply, and accept SMP/E base functions. Submit and run\nthese SAMPJCL members in sequence. Do not proceed with any job until the previous job has completed successfully.\nNOTE\nThe following steps include instructions to execute the AVHSEDIT macro each time that you open a new\nSAMPJCL member. To edit all SAMPJCL members simultaneously, read and follow the instructions in the\nAVHAREAD member, and submit the AVHEDALL member.\n1.Open the SAMPJCL member AVH20RCB in an edit session, and execute the AVHSEDIT macro from the command\nline.\nAVH20RCB is customized.\nNOTE\nTo include optional components, uncomment the applicable FMID in the customized job.\n2.Submit AVH20RCB to receive SMP/E base functions.\nYour product is received and now resides in the global zone.\n3.Open the SAMPJCL member AVH30APB in an edit session, and execute the AVHSEDIT macro from the command\nline.\nAVH30APB is customized.\n4.Submit AVH30APB to apply SMP/E base functions with the CHECK option.\na.Note any unresolved errors.\nb.Verify that resolving PTFs are applied before implementing products in production.\nc.After successful completion, rerun APPLY with the CHECK option removed.\n 131", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cdfcb74ad7e9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nYour product is applied and now resides in the target libraries.\n5.Open the SAMPJCL member AVH40ACB in an edit session, and execute the AVHSEDIT macro from the command\nline.\nAVH40ACB is customized.\n6.Submit AVH40ACB to accept SMP/E base functions with the CHECK option. After successful completion, rerun\nACCEPT with the CHECK option removed.\nYour product is accepted and now resides in the distribution libraries.\nYou can now clean up the USS directory (optional) or apply preventive maintenance as described in Maintain Products\nusing SMP/E JCL.\nClean Up the USS Directory\nThis procedure is optional. If you decide to perform this procedure, do so after you complete the installation process and\nwhen you do not need the installation files. When this procedure is done, you are ready to install preventive maintenance.\nTo free file system disk space for subsequent downloads after downloading and processing the pax files for your\nBroadcom  mainframe product, remove files from your USS directory and delete unnecessary z/OS data sets. You can\ndelete the following items:\n\u2022Pax file\n\u2022Product-specific directory that the pax command created and all the files in it\n\u2022SMP/E RELFILEs, SMPMCS, and HOLDDATA MVS data sets. These data sets have the HLQ that you assigned in the\nUNZIPJCL job.\nNOTE\nRetain non-SMP/E installation data sets such as yourHLQ .INSTALL.NOTES for future reference.\n1.Navigate to your Pax ESD USS directory.\nYour view is of the applicable USS directory.\n2.Delete the pax file by entering the following command:\nrm paxfile\npaxfile Specifies the name of the product pax file that you downloaded.\nThe pax file is deleted.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cdfcb74ad7e9-1", "text": "The pax file is deleted.\n3.Delete the product-specific directory by entering the following command:\nrm -r product-specific-directory\nproduct-specific-\ndirectorySpecifies the product-specific directory that you created previously using the pax command or sample\nJCL.\nThe product-specific directory is deleted.\nNOTE\nYou can also use TSO ISHELL to navigate to the pax file and product-specific directory, and delete them using\nthe D line command.\nWhen you are done with this step, you are ready to install maintenance.\nConfiguring\nConfigure InterTest and SymDump  products.\nThis article contains information about the steps you need to take to configure InterTest and SymDump  products. To\nconfigure your product, follow the instructions in either Configure Your Product With CSM  or Configure Your Product\nWithout CSM .\n 132", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "46d2dd0fa111-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIMPORTANT\nFor consistent product behavior when you upgrade to a newer InterTest release, ensure that you:\n\u2022Carry your configurations forward to the new version.\n\u2022Review the configuration checklists for each product to determine which features apply to your site.\nConfiguration Best Practices\nThis article contains configuration best practices for your product.\nSymbolic Files\nBefore you configure your Broadcom  testing tool product, carefully consider how to best organize your symbolic\ninformation that is stored in your PROTSYM files. Well-organized symbolic information allows for the most effective and\nefficient access to your symbolics during testing.\nThere is no best way to organize symbolic information that works for everyone. How your symbolic information is\norganized depends on your environments, your application systems, and the number of programs and programmers\ninvolved in your testing. Consider the following guidelines when you plan for symbolic support:\n\u2022In a production environment , consider maintaining a separate PROTSYM file for each application system that can be\nshared by all of your programmers. Because only one copy of each program is typical in a production environment, the\nsame symbolic information could be shared by any programmer debugging in that environment.\nIn production environments, symbolic information is often limited to a single version of each program, and testing or\ndebugging is typically less frequent and often limited to critical, real-time failures. Separate, shared PROTSYM files\nallow you to maintain a single set of symbolic information for each production application system that is accessible if\nthere is a failure.\n\u2022In a test environment , multiple versions of the same program are more likely to exist, and shared executable libraries\nare complimented by sandbox libraries that house test fixes or works in progress. For this environment, a single shared\nsymbolic repository is adequate for the shared executables. However, each programmer might want to own their", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "46d2dd0fa111-1", "text": "symbolic repository is adequate for the shared executables. However, each programmer might want to own their\nown PROTSYM file. This arrangement provides programmers with the freedom to test using the correct symbolic\ninformation without impacting other team members.\nBusiness Value:\nWell-organized symbolic information lets your application programmers easily locate, access, and share symbolic\ninformation for their programs. The result is improved performance for your Broadcom  testing tools, optimal use of your\nDASD space, and optimum productivity for your application programmers.\nAdditional Considerations:\nGenerally, think of your PROTSYM files as nothing more than a match for your load libraries, remembering that for each\nunique version of a load module you may require symbolic information for testing or debugging. Like the load libraries\nthat exist at each level or stage of your development environment, the corresponding symbolic files should vary in size\ndepending on the maximum number of programs that are expected at each level, with the individual PROTSYM files being\nthe smallest by far.\nIf you are also licensed for Endevor  Software Change Manager ( Endevor ), Broadcom  testing tools provide an extra level\nof automation through dynamic symbolic support. This feature lets you populate your PROTSYM file dynamically on\ndemand with symbolic information for programs built using Endevor .\nWe recommend that you set the threshold for used space in the symbolic file to monitor the space utilization percentage.\nWhen the threshold is reached, a message indicates that the symbolic file is almost full. Set the threshold by specifying\nthe USEDSPACEMSG parameter with the INITIALIZE or UPDATE functions of IN25UTIL.\nMore Information:\nFor more information about creating, populating, maintaining, and using your PROTSYM symbolic repositories to enhance\nyour testing, see Symbolic Support which is provided with each Broadcom  testing tool product.\n 133", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4130d221361f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFor more information about dynamic symbolic support, see Installing .\nDynamic Symbolic Support for Endevor\nIf you are licensed for Endevor  Software Change Manager ( Endevor ), Broadcom  recommends using the dynamic\nsymbolic support feature that is provided by the Broadcom  testing tools. This feature allows you to populate your\nPROTSYM file dynamically on demand with symbolic information for programs built using Endevor .\nBecause there multiple ways to maintain the content of your PROTSYM files, you may encounter the situation where you\nhave multiple versions of the same program for which you need to locate and select the correct symbolic information.\nDynamic symbolic support gives you the option to create your symbolic information only when it is needed, rather than\nalways reloading your PROTSYM file after each compilation or assembly. This can save you time, CPU utilization, and\neven DASD space.\nBusiness Value:\nThe dynamic symbolic support feature is available with many of Broadcom  testing tool products including InterTest Batch,\nInterTest for CICS, SymDump  Batch, and SymDump  for CICS. This feature simplifies the setup requirements for using\nsymbolic support, while simultaneously eliminating most potential associated setup errors. By improving the accuracy\nof your symbolic file content, and eliminating common setup errors, dynamic symbolic support greatly increases the\nproductivity of your programmers.\nAdditional Considerations:\nDynamic symbolic support requires that you compile or assemble your applications using an Endevor  process with the\nfootprint feature active. When symbolic information is required by one of the Broadcom  testing tools, your PROTSYM\nfiles are inspected first for the matching symbolic information. When no matching information is found, the executable\nis inspected for an Endevor  footprint. If this footprint is found, that footprint is used to locate the matching listing that", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4130d221361f-1", "text": "is dynamically loaded into your specified PROTSYM file. The matching symbolic information is then used by your test\nsession.\nFor specific instructions related to setting up and using dynamic symbolic support, see Installing and Batch Debugging.\nStarting and Stopping InterTest for CICS in a CICS Region\nTo ensure that the CICS global user exits required by InterTest are the first to receive control, Broadcom  recommends that\ncustomers start InterTest for CICS during CICS PLT processing.\nBusiness Value:\nThis practice ensures that other global user exits do not interfere with InterTest for CICS when the product makes a\ndecision to monitor or debug a CICS program.\nMore Information:\nFor more information on starting InterTest for CICS, during CICS PLT processing, see Activate Your Product.\nPerformance Considerations for CICS Regions Using DB2\nSymDump  recommends that customers starting InterTest or SymDump for CICS in a region with DB2 activity reviews the\nXRMIO option and sets the option according to their needs.\nWhen the XRMIO option is set to YES (the default), InterTest and SymDump for CICS provides additional diagnostic\ninformation about the application by using the CORE=LASTSQL command. This command causes InterTest and\nSymDump for CICS to display the last SQL statement executed by the application. However, if you set XRMIO to YES and\nthe applications that run in your CICS region heavily use EXEC SQL calls, performance in that region might degrade.\nBusiness Value:\n 134", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7b4e6b009559-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAlthough using the XRMIOUT global user exit from IBM can affect performance in regions that use EXEC SQL calls\nextensively, this exit can provide valuable diagnostic information for DB2 applications that contain EXEC SQL statements. \nThis information can be useful in identifying or resolving problems and improve time to resolution.\nAdditional Considerations:\nYou must carefully weigh the value of the information you receive against the performance considerations of using\nXRMIOUT in regions where heavy DB2 activity exists. Especially in production regions where performance is most critical,\nconsider carefully whether the additional diagnostic information provided by XRMIOUT is valuable enough to risk the\npossible performance impact of using this option where extensive DB2 activity exists.\nSymDump  Batch Installation with Other SVC 51 Intercepts\nIf you have multiple products that use an intercept for SVC 51, run CAIRIM to initialize SymDump  Batch after all other\nproducts.\nBusiness Value:\nInitializing SymDump  Batch after all other products have been initialized helps ensure that SymDump  Batch gets control\nfirst. This enables the most accurate analysis and reporting possible before interference occurs.\nAdditional Considerations:\nWhen SymDump  Batch is initialized, it replaces the address of SVC 51, the DUMP SVC. When the product is finished with\nits reporting, it takes one of the following actions, depending on the SymDump option.\n\u2022If the SymDump option is OFF, control is returned to the operating system.\n\u2022If the SymDump option is ON, control is given to the address that was replaced when SymDump  Batch was initialized.\nTherefore, if another product, such as SymDump  System, that intercepts SVC 51 was initialized before SymDump  Batch,\nthat product does not get control unless the SymDump option is set to ON.\nSymDump  Batch PRTLIB Repositories Management", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7b4e6b009559-1", "text": "SymDump  Batch PRTLIB Repositories Management\nWhen you configure SymDump  Batch, you must set your default PRTLIB. The PRTLIB repository is the VSAM data set\nthat maintains your abend reports. You can have one repository for multiple z/OS systems, or one per system. However,\ncare must be taken to determine if your installation requires the use of more than one PRTLIB.\nBusiness Value:\nWell-managed repositories let your application programmers easily locate, access, and share abend reports for their\napplications. You can use multiple repositories per system with the use of multiple default tables, or by using a user exit.\nAs a result, you get better performance from your Broadcom  testing tools, optimal use of your DASD space, and the best\npossible productivity for your application programmers.\nAdditional Considerations:\nWhen SymDump  Batch is configured, the default PRTLIB data set is defined with the PRTLIB option of CAOETABL.\nHowever, not all installations may prefer writing all abend reports to one repository. Specific installations may want a few\ngroups to write to a specific repository. To provide this flexibility, you can override the PRTLIB value in several ways.\n\u2022Use the existing user exit, CAOCUPRT to return the PRTLIB to use based on JOBNAME, STEPNAME, abending\nprogram name, and USERID.\n\u2022Define the PRTLIB by specifying a PRTLIB value in your CAIOPTS DD within the job step JCL.\n\u2022Allocate the CAIOPTS DD dynamically for each user by following the naming convention userid.CAIOPTS.\nRepository Maintenance\nUse the following SymDump  Batch options to automatically manage aspects of PRTLIB repository maintenance:\n 135", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "362fcc3e8107-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Set the PRTLHCT of CAOETABL to receive notification when the PRTLIB reaches the designated percentage full\n\u2022Set the DUPLIM of CAOUDFRX to eliminate duplicate reports\n\u2022Set the EXPDAYS of CAOUDFRX to delete expired reports.\nMore information:\nFor specific instructions on setting up the user exit CAOCUPRT, the PRTLIB option, or dynamic allocation of your\nCAIOPTS data set, see Installing and Batch Abend Analysis.\nSymDump  for CICS PROTDMP Files\nYou can view transaction dumps from multiple CICS regions using a single dump viewing CICS region. Because the\nSymDump  for CICS dump viewer runs as a CICS transaction, it is possible to view dumps from multiple CICS regions\nfrom a single dump viewing region. To do this, add remote CICS file definitions for the dump data sets from all CICS\nregions.\nNOTE\nThe CICS releases for all related dump data sets must match the dump viewing region. You cannot mix dump\ndata sets from different CICS releases in the same dump viewing region.\nBusiness Value:\nBy providing access to dumps from multiple CICS regions through a single viewing region, SymDump  for CICS simplifies\nthe process of locating dumps and ensures that dumps remain available even when the CICS region in which those\ndumps were produced becomes unavailable. This improves programmer productivity, reduces time to resolution, and\nhelps to control or eliminate costly down time .\nMore Information:\nFor more information on creating PROTDMP files and estimating their size, see Allocate Files. For more information on\nmaintaining and reporting on the contents of your PROTDMP files, see Batch Utility.\nConfigure an InterTest and SymDump Software Instance Using z/OSMF\nWorkflows", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "362fcc3e8107-1", "text": "Configure an InterTest and SymDump Software Instance Using z/OSMF\nWorkflows\nInstructions to configure InterTest and SymDump product instances using z/OSMF Workflows.\nAs a systems programmer, security administrator, or someone responsible for managing the configuration of your z/OS\nsystems, you can use z/OSMF workflows to configure a product software instance with less effort, time, and mainframe\nexpertise. The workflows guide you through the configuration process and help automate configuration of a product\ninstance. This approach significantly reduces the time that is required to perform configuration tasks.\nDuring installation of your product using z/OSMF Deployments, you can execute z/OSMF configuration workflows\nto configure the product software instance. Alternatively, you can execute the product configuration workflows after\ninstallation from the Workflows page or software instance in z/OSMF Software Management as shown in the following\nprocedures. You can also use these procedures to configure a software instance that is installed using native SMP/E or\nCSM  or to re-execute a workflow that was initially executed during installation using z/OSMF Deployments.\nTo configure a software instance using z/OSMF workflows:\n\u2022Address prerequisites\n\u2022Register z/OSMF workflows\n\u2022Execute z/OSMF workflows\nWhen these tasks are completed, the product or component is ready for use on the system where the software instance\nwas configured.\nAddress Prerequisites\n 136", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ee4f73a40abc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBefore you begin this process:\n\u2022Ensure that your site has configured z/OSMF as described in the IBM Knowledge Center and addressed the z/OSMF\nsecurity requirements for ACF2 , Top Secret, or IBM RACF  as applicable. Appropriate permissions are required to\nregister and execute workflows and add software instances in z/OSMF.\n\u2022If you installed using CSM  or native SMP/E JCL, register your SMP/E environment (CSI) as a software instance in z/\nOSMF. To do so, see Adding software instances  in the IBM Knowledge Center documentation.\n\u2022Apply all z/OSMF related product maintenance to ensure that all defined workflows are available for use. Workflows\nare provided as part of a portable software instance or through PTF maintenance.\nRegister z/OSMF Workflows\nBefore you can execute a workflow that you acquired through PTF maintenance, register it in z/OSMF. Experienced\nsystem programmers typically perform this task.\nNOTE\nIf you have already downloaded and installed a portable software instance using z/OSMF Deployments, the\nworkflows are included and already registered. Skip this task.\nTo register the workflows, gather the fully qualified name of the workflow definition file (.xml) and optional workflow\nvariable input file (.properties). These files typically reside in the SMP/E target zFS file system that was mounted during\ninstallation. You can use these files to customize product software instances and to automate workflow execution, saving\ntime and effort when deploying multiple standardized product software instances.\nUse either  of the following procedures to add a new workflow instance in z/OSMF:\n\u2022Register Workflows from a Software Instance\n\u2022Register Workflows from the Workflows Task\nNOTE\nFor more information about registering the workflows, see Create a workflow  in the IBM Knowledge Center\ndocumentation.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ee4f73a40abc-1", "text": "documentation.\nRegister Workflows from a Software Instance\nUse the following procedure to register workflows from an existing software instance in z/OSMF.\nFollow these steps:\n1.Log in to z/OSMF and go to Software , Software Management , and select Software Instances .\n2.Right-click your software instance from the list and select Modify  from the Actions menu.\n3.Select the Workflows tab, and select Add from the Actions menu.\n4.Specify the following values:\n\u2013Specify the sequence in which the workflow should be performed.\n\u2013Specify the workflow name and description.\n\u2013Indicate whether the workflow steps must be performed on the host system or whether they can be performed on\nanother system in the same sysplex.\n\u2013Specify the location of the workflow definition file. The workflow is located in the SMP/E target library and includes\nyour three-character product identifier in the workflow name. Include the SMP/E element type and name for your\nproduct or the location of the partitioned data set member, sequential data set, or UNIX file.\n5.Select OK.\nThe workflow is available for execution. Go to Execute z/OSMF Workflows.\nRegister Workflows from the Workflows Task\nUse the following procedure to register workflows from the Workflows task in z/OSMF.\n 137", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e44aa530cc4a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFollow these steps:\n1.Select Workflows in z/OSMF.\n2.Select Create Workflow from the Actions  menu.\nThe Create Workflow panel appears.\n3.Specify the following values:\n\u2013Specify the path to the following files:\n\u2022Workflow Definition File\nThe workflow is located in the SMP/E target library, hlq.CAVHXML(CAVHWCNF).\n\u2022(Optional) Workflow Variable Input File\nNOTE\nSpecify a value for this field only when you have predefined the values by editing the .properties file\nmanually. Editing the .properties file lets you customize the product configurations and establish the\noperational settings that are processed when the product starts. For example, the data set name prefix\nto be used for the final configured run-time libraries and the serial number (VOLSER) of the volume on\nwhich the data sets are to be allocated.\n\u2013Select the system where the workflow resides. This system is where the workflow steps are performed.\n4.Select Next .\n5.Complete the following fields:\n\u2013Specify a unique name for the workflow.\n\u2013Select or enter an Owner user ID  for the workflow, and select Assign all steps to owner user ID .\n6.Select Finish .\nThe workflow is available for execution. Go to Execute z/OSMF Workflows.\nExecute z/OSMF Workflows\nThe following procedure describes how to execute the workflow steps to complete the configuration of your product\nsoftware instance. z/OSMF presents the workflow customization steps in sequence and guides you through the required\nsteps and changes. When you complete all workflows, the product is ready for use.\nYou can execute z/OSMF workflows from an existing software instance or from the Workflows task.\nNOTE\nBefore you execute the workflow steps, provide a valid JOB statement that includes your ACCOUNTINFO and", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e44aa530cc4a-1", "text": "NOTE\nBefore you execute the workflow steps, provide a valid JOB statement that includes your ACCOUNTINFO and\nMSGCLASS information. To prevent errors, do not use the default MSGCLASS value. For more information\nabout customizing the JOB statement for z/OSMF workflows, see the IBM documentation.\nFollow these steps:\n1.Complete either  of the following steps:\n\u2013Select the software instance that you want to configure from the Software Instances page in z/OSMF ( Software\nManagement, Software Instances ). Right-click the software instance, and select Perform Workflows from the\nActions menu.\nThe registered workflows for the software instance display.\n\u2013Select Workflows to display the existing workflows for your installation. Sort the workflows by product using the\nConfigure Columns  action to display product information (name, ID, and version).\nThe available workflow instances display.\n2.Select the workflow that you want to execute.\nThe required execution steps display.\n3.Execute the steps in order. Select Refresh  until the job completes. A return code of zero (0) is expected.\nFor general information about how to execute z/OSMF workflow steps, refer to the IBM documentation.\n4.Repeat steps 2 and 3 for each required workflow.\nWhen all workflows are executed, the software instance is configured and you are ready to start using the product or\ncomponent.\n 138", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0cd0d5e3edb7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nConfigure Your Product With CSM\nThis article describes the manual tasks you perform when configuring your product using CSM .\nData sets are created by CSM  after successfully completing each step, that is the SMP/E installation, deployment, and\nconfiguration procedures.\nNOTE\nBroadcom  strongly advises that you perform the initial installation and configuration of your product and its\ncomponents in a test environment as a precaution. This testing will let you detect any possible conflicts with\nother vendor products.\nConfigure the Deployed Product\nConfiguration is a process of copying the deployed libraries to run-time libraries and customizes the product for your\nsite to bring it to an executable state. You can configure Broadcom  products that you have already acquired, installed,\nand deployed using CSM . You cannot use CSM  to configure a product unless you have already used CSM  to deploy the\nproduct.\nYou perform the following high-level tasks to configure your products using CSM :\n1.Select a configurable deployment on the Deployments tab to view details and products for that deployment.\n2.Select a product in the deployment and start the Configuration wizard to create a configuration. Complete each of\nthe steps in the wizard. The wizard has multiple levels of detailed instructions and guides you through choosing\nconfiguration settings for your site. At any point, you can save your work and can come back to it later. Configurations\nwhere you have partially completed the steps in the wizard are listed on the Configurations tab. The steps in the\nwizard include the following:\na.Define a configuration name and select a system for the configuration.\nb.Select configuration functions and options.\nc.Define system preferences.\nd.Create target settings.\ne.Select and edit resources.\n3.Build the configuration. The last step of the Configuration wizard lets you build the configuration. If needed, you can", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0cd0d5e3edb7-1", "text": "edit the configuration and can build the configuration again. Building the configuration closes the wizard and creates a\nconfiguration with all your settings.\n4.(Optional) Validate the configuration. Validation verifies access to resources that are going to be used when you\nimplement the configuration.\n5.Implement the configuration. You implement a configuration to make your deployed software fully functional.\nImplementation executes on the destination system, applying the variables, resources, and operations that are defined\nin the configuration.\nCSM  configures the product.\nAfter the configuration process completes, the product is ready for you to use.\nInterTest Batch Tasks\nConfigure the external tasks for InterTest Batch.\nFollow these steps:\n1.APF authorize the application runtime load library. For more information, see the Activate Batch Link article.\n2.Allocate a profile data set for each user. Required, if the USERPROFLIBS configuration options is selected. If the\nUSERPROFLIBS option is not selected, a single PROFLIB will be created automatically. For more information, see\nAllocate Files.\n3.Allow users to concurrently update PROTSYM files. Required, if the NEWPROTSYM option is selected.\n 139", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "291fbbed23bf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n4.Allocate an ALIB for each user.  Required, if both the ALIB and USERALIBS configuration options are selected or you\nwill be using the Foreground debugging feature.\n5.Allocate an INCLUDE library for each user. Required, if both the INCLIB and USERINLIBS options are selected.\n6.(Optional) Add the product to the ISPF main menu. For more information, see Batch Interfaces and Compatibility.\n7.Add InterTest Batch to your TSO logon procedure.\n8.(Optional) Customize Roscoe  for use with the application.\n9.Customize the application started task for Endevor  Dynamic Symbolic Support. For more information, see Interfaces\nand Compatibility.\nNOTE\nRequired, if the MULTNDVRSITES option is selected, indicating that the customer is using multiple Endevor\nsite IDs.\n10.(Optional) Update the OS/VS COBOL procedure, COBINT and compile, bind, and post-process the OS/VS COBOL\nforeground demonstration program, CAMRCOB.\nNOTE\nRequired, if the COBOL configuration option is selected and the customer still compiles with the OS/VS\nCOBOL compiler.\nActivate Batch Link\nThis operation updates your CAS9 procedure and PARMLIB then executes the CAS9 procedure to activate Batch Link.\nUse the following procedure to activate the Batch Link feature of InterTest Batch.\nFollow these steps:\n1.Add and APF-authorize the InterTest Batch runtime load libraries (CAI.CAVHAUTH and CAI.CAVHLOAD) to the\nSTEPLIB concatenation in your CAS9 procedure.\nNOTE\nAll customized configuration elements must be available through STEPLIB.\n2.Add the following control card to the member or data set pointed to by the PARMLIB DD in your CAS9 procedure:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "291fbbed23bf-1", "text": "PRODUCT(CA INTERTEST/SYMDUMP) VERSION(VHA0) INIT(CAVHINIT) PARM(220)\n3.Execute CAIRIM using your CAS9 procedure.\nYou have activated Batch link.\nMSM can execute this step automatically during the implementation process when you change the default value of\nManual operation to Automatic operation before releasing it. Otherwise, specify Confirm manual operation when you\nimplement the configuration.\nSymDump  Batch Tasks\nFollow these steps to configure the external tasks for SymDump  Batch:\n1.Allow Concurrent Updates to Symbolic Files.\n2.Customize for Dynamic Symbolic Support.\n3.Add Support for File Master Plus .\n4.Review Language Environment (LE) Considerations.\n5.Add Runtime Load Library to LNKLST.\n6.APF-Authorize Runtime Load Library.\n7.Activate SymDump  Batch.\n8.Establish Access to the TSO Facility.\n 140", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cf17e5d37a18-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAllow Concurrent Updates to Symbolic Files\nThe MVS RESERVE and DEQ macros are used to allow sharing of a PROTSYM file between regions or systems. The\nresource major name used in the RESERVE and DEQ macros is INTERTST. Place the major name INTERTST into an\nMVS service that converts the RESERVE into a cross-system ENQ if this service is available at your site.\nCustomize for Dynamic Symbolic Support\nIf you are an existing Endevor  user and the FOOTPRINT feature is used when applications programs are generated in\nEndevor , you can customize Endevor  for dynamic symbolic support by editing the started task procedure.\nNOTE\nThis step is not required if you have only one C1DEFLTS.\nFollow these steps:\n1.Use the CAI.CAVHJCL member INTNDVR, the started task procedure, to access DSS to dynamically load program\nsymbolic information.\nThis started task must be an APF-authorized task.\n2.Modify this procedure to conform to your installation standards.\n3.Copy the procedure to a system procedure library.\nThe member name of the procedure must have the Endevor  C1DEFLTS table site ID appended to it. For example, if\nthe site ID is 3, the procedure member name should be INTNDVR3.\nThe first seven-character prefix of the procedure member name you copied to the system procedure library must\nmatch the value defined in the NDVRPROC option in CAOUDFRX.\nNOTE\nCreate a procedure for each unique site ID.\nAdd Support for File Master Plus\nIf you are an existing File Master Plus  user and want to use the FM viewer command, you must perform the following\nadditional set up. Before you can use FM viewer command you must perform the following procedure.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cf17e5d37a18-1", "text": "additional set up. Before you can use FM viewer command you must perform the following procedure.\nFollow these steps:\n1.Set up the File Master Plus  to use LIBDEFs (LIBALLOC='Y').\n2.Verify that the FM1 executable exists in a data set allocated to SYSPROC or SYSEXEC.\n3.Allocate CAI.CAVHCLS0 to SYSPROC or SYSEXEC.\nReview Language Environment (LE) Considerations\nUse the following procedure to add abnormal termination exit entry for CAOECEEX.\nFollow these steps:\n1.Edit CEE.SCEESAMP(CEEEXTAN).\n2.Follow the instructions in this member to add an abnormal termination exit entry for CAOECEEX.\n3.Apply the applicable SYSMOD to make these changes take effect.\nNOTE\nFor more information about the CEEEXTAN exit, see the IBM z/OS Language Environment Customization\nguide.\n 141", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6db870f7f582-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAdd Runtime Load Library to LNKLST\nAdd the SymDump  Batch runtime load library, CAI.CAVHLOAD, to the LNKLST concatenation. This can be done\ndynamically by creating and activating a new LNKLST set. For example, a new LNKLST set called LNKLST01 can be\ncreated by copying the existing set, LNKLST00, and adding CAI.CAVHLOAD to the end of the concatenation.\nFollow these steps:\n1. SETPROG LNKLST,DEFINE,NAME=LNKLST01,COPYFROM=LNKLST00\n2. SETPROG LNKLST,ADD,NAME=LNKLST01,DSNAME=CAI.CAVHLOAD,ATBOTTOM\n3. SETPROG LNKLST,ACTIVATE,NAME=LNKLST01\nThe PROGxx or LNKLSTxx member of SYS1.PARMLIB should be updated to permanently add CAI.CAVHLOAD to the\nIPL LNKLST set at the desired location in the concatenation.\nAPF-Authorize Runtime Load Library\nTo APF-authorize the SymDump  Batch runtime load library, add an entry for CAI.CAVHAUTH to member IEAAPFxx of\nSYS1.PARMLIB.\nNOTE\nAuthorization does not take effect until the next IPL.\nActivate SymDump  Batch\nFollow these steps:\n1.Add the SymDump  Batch load library CAI.CAVHAUTH to the STEPLIB concatenation in your CAS9 procedure\n(SYS1.PROCLIB(CAS9)).\n2.Add the following control card to the member or data set pointed by the PARMLIB DD (in SYS1.PROCLIB(CAS9)):", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6db870f7f582-1", "text": "PRODUCT(CA INTERTEST/SYMDUMP) VERSION(VHA0) INIT(CAVHINIT) PARM(220)\n3.Execute CAIRIM using the CAS9 procedure.\nEstablish Access to the TSO Facility\nYou must include the SymDump  Batch ISPF libraries in your session ISPF files concatenation to access the SymDump\nBatch panels. Use the following procedure to concatenate the ISPF file and tailor the Master panel.\nFollow these steps:\n1.Concatenate the following data sets into the indicated ddnames (if they were not previously concatenated):\nData Set Name DDName Description\nCAI.CAVHPNL0 ISPPLIB ISPF panels for SymDump  Batch\nCAI.CAVHSKL0 ISPSLIB ISPF skeletons for SymDump  Batch\nCAI.CAVHMSG0 ISPMLIB ISPF messages for SymDump  Batch\nCAI.CAVHTBL0 ISPTLIB ISPF tables for SymDump  Batch\nCAI.CAVHCLS0 SYSPROC ISPF CLISTs for SymDump  Batch\nCAI.CAVHLOAD ISPLLIB or STEPLIB SymDump  Batch Load Library\n2.Perform the following steps if your site uses variable-length CLISTs:\na.Execute CAI.CAVHJCL(CARXCNVT) to change the CLISTs from fixed to variable length format.\nb.Point the SYSPROC DD to the CAI.VCAICLIB data set (instead of CAI.CAVHCLS0).\n 142", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "15a2f72d04ea-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n3.Allocate the following data sets into the indicated ddname (if they were not previously allocated):\nData Set Name DDName Description\nCAI.CAVHTBL0 CAOEXTBL ISPF tables for SymDump  Batch\nCAI.CAVHHELP CAOIHELP ISPF Help library\nYou have now placed the SymDump  Batch ISPF libraries into your session ISPF files concatenation.\nTo tailor the ISPF Master panel, do one of the following\n\u2022Copy the ISP@MSTR panel supplied with SymDump  Batch (named CARXSBA0)\n\u2022Add new lines to your existing ISP@MSTR panel.\nUse the following procedure to add new lines to your existing panel.\nFollow these steps:\n1.Add the first line after the last option selection displayed on the panel.\n2.Define this line as an option number for the user to select with a brief description of the function. For example:\n% 6 +CA SYMDUMP BATCH - Options Panels\n% 7 +CA SYMDUMP BATCH - Invoke the CAIPRINT Repository Viewer\n3.Add the lines containing the commands required to execute the options to the list of &SEL variables defined at the end\nof the panel. For example:\n6. 'PANEL(CAOEP001) NEWAPPL(CA$Z)'\n7, 'PGM(CAOIF000) NEWAPPL(CAOI)'\nInterTest for CICS Tasks\nWe recommend that you configure your product using CSM .\nWhen you configure your product using CSM , perform the manual tasks described in following procedure to configure\nthe external tasks. Data sets are created by CSM  after successfully completing each step that is the SMP/E installation,\ndeployment, and configuration procedures.\nFollow these steps:\n1.Allow concurrent updates to symbolic files.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "15a2f72d04ea-1", "text": "deployment, and configuration procedures.\nFollow these steps:\n1.Allow concurrent updates to symbolic files.\nThe MVS RESERVE and DEQ macros are used to allow sharing of a PROTSYM file between regions or systems. The\nresource major name used in the RESERVE and DEQ macros is INTERTST. Place the major name INTERTST into an\nMVS service that converts the RESERVE into a cross-system ENQ if this service is available at your site.\n2.Customize for Dynamic Symbolic Support.\na.Edit member INTNDVR of the Broadcom  Testing and Fault Management common runtime procedure library\n(CAI.CAVHPROC), modify it to conform to your installation standards, then save it.\nb.To create a started task for an Endevor  site ID, copy INTNDVR to a system procedure library as member\nINTNDVRn, where n is the Endevor  C1DEFLTS table site ID. Create a procedure for each unique Endevor  site ID.\nNOTE\nThe INTNDVRn procedures require read security access to any load library data sets in which application\nprograms that were created by Endevor  reside and which may require symbolic support for debugging with\nInterTest for CICS. They also require write security access to any PROTSYM files they will populate.\n3.Add CCI spawn parameters.\nThis step adds the CCI spawn parameters for the InterTest for CICS dynamic symbolic support feature to the JCL\nprocedure used to start CAIENF. If you want this step to be executed automatically by CSM , use the 'Action' button to\nchange it from a 'Manual' to an 'Automatic' operation before releasing it at implementation time.\nTo perform this step manually, add the following DD statement to the SPNPARMS DD in the JCL procedure used to\nstart CAIENF:\n 143", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a7c37e647311-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    // DD DISP=SHR,DSN=avhproclib(INDVSPWN) \n4.Refresh CAIENF.\nSchedule a refresh of CAIENF to activate the CCI spawn parameters for InterTest for CICS dynamic symbolic support\nof Endevor . The dynamic symbolic support feature will not be available until CAIENF has been refreshed.\n5.Update CICS startup JCL and restart CICS.\nNOTE\nIf your site has previously installed SymDump  for CICS as a separate product, some DD statements may\nalready exist.\nIf you use DD statements in your CICS startup JCL, your InterTest for CICS files, as defined in the CSD, require\nDD statements in the JCL for CICS. DISP=SHR must be specified for PROTSYM to allow batch compiles to run\nconcurrently with CICS. Alternatively, you may directly add the data set names to the CEDA FILE definition, defined in\nthe CSDINT member in CAI.CAVHJCL and remove the DD statements for those files.Add the following DD statements\nto your CICS startup JCL:\n//PROTCPF DD DSN=CAI.PROTCPF,DISP=OLD \n//PROTSYM DD DSN=CAI.PROTSYM,DISP=SHR \n//PROTHLF DD DSN=CAI.CAVHHLF,DISP=SHR \n//PROTUHF DD DSN=CAI.PROTUHF,DISP=SHR \n//PROTMLOG DD DSN=CAI.PROTMLOG,DISP=SHR\nIf you are using the InterTest for CICS dynamic symbolic support feature for Endevor , add an NDVRSYM DD", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a7c37e647311-1", "text": "statement to specify the PROTSYM file to be used for dynamic symbolic loading. The NDVRSYM DD must be\nspecified in the CICS startup JCL for InterTest for CICS to invoke the dynamic symbolic load option. A sample\nNDVRSYM DD statement follows:\n//NDVRSYM DD DSN=CAI.PROTSYM,DISP=SHR \nIf you specified more than one symbolic file in the SYMFIL variable of the IN25OPTS variable group, include a DD for\neach SYMFIL specified.\nAdd both InterTest for CICS load library and the symbolic common component load library to the DFHRPL in the CICS\nstartup JCL:\n// DD DSN=CAI.CAVHLOAD,DISP=SHR  \nIf you execute the demo programs, add the following DD to the DFHRPL in your CICS startup JCL to specify the same\nload library data set name that you used when you ran the demo program's compile and link JCL:\n// DD DSN=CAI.demoload,DISP=SHR\nNOTE\nInterTest for CICS makes calls to IEWBIND when using the online COMPOSITE module command and\nIEWBIND requires about 750 KB of below the line storage. To ensure there is sufficient storage available\n(below the line for IEWBIND calls), you must ensure that your DSALIM is at least 750 KB less than your\nbelow the line private area size. Failure to do this could result in S0F4 and U900 abends in your CICS region\nduring dump capture.\nSymDump  for CICS Tasks\nThis section describes the manual tasks that you perform when configuring SymDump  for CICS (SYMC) using CSM .\nFollow these steps:\n1.(Optional) Add CCI Spawn Parameters.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a7c37e647311-2", "text": "Follow these steps:\n1.(Optional) Add CCI Spawn Parameters.\nThis step is only required if the ENDEVOR option is selected. This step adds the CCI spawn parameters for the\nInterTest for CICS dynamic symbolic support feature to the JCL procedure used to start CAIENF. If you want this step\nto be executed automatically by CSM , use the Action button to change it from a \u2018Manual\u2019 to an \u2018Automatic\u2019 operation\nbefore releasing it at implementation time.\nTo perform the step manually, add the following DD statement to the SPNPARMS DD in the JCL procedure used to\nstart CAIENF:\n 144", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bdf56317da5b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n// DD DISP=SHR,DSN=CAI.CAVHPROC(INDVSPWN)\n2.(Optional) Refresh CAIENF.\nThis step is only required if the ENDEVOR option is selected. Schedule a refresh of CAIENF to activate the CCI spawn\nparameter for InterTest for CICS dynamic symbolic support of Endevor . The dynamic symbolic support feature will not\nbe available until CAIENF has been refreshed.\n3.Install or Customize DFHPEP.\nIf your site does not have a custom DFHPEP module implemented, the DFHPEP included in the product load library\nmust be installed in a library concatenated before the IBM CICS library suffixed with SDFHLOAD, so that it replaces\nthe IBM supplied dummy version of DFHPEP. If your site already uses a customized DFHPEP it should be customized\nand relinked to include the following source statement:\nEXEC CICS LINK PROGRAM('IN25PEP')\nUsing the supplied copy of DFHPEP or customizing your own DFHPEP to link to IN25PEP is not a hard requirement\nfor installation of SymDump  for CICS. The dump capture still functions without DFHPEP/IN25PEP processing.\nHowever the failure to configure DFHPEP as suggested previously prevents capture of the last screen display in an\nMRO environment.\n4.Update CICS Startup JCL and Restart CICS.\nNOTE\nIf your site has previously installed InterTest for CICS as a separate product, some DD statements may\nalready exist.\nIf you use DD statements in your CICS startup JCL, your SymDump  for CICS files, as defined in the CSD, require", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bdf56317da5b-1", "text": "DD statements in the JCL for CICS. DISP=SHR must be specified for PROTSYM to allow batch compiles to run\nconcurrently with CICS. Alternatively, you may add the dataset names directly to the CEDA FILE definition defined in\nthe CSDSYM member in CAI.CAVHJCL and remove the DD statements for those files.\nAdd the following DD statements to your CICS startup JCL:\n//PROTDMP  DD DSN=CAI.PROTDMP,DISP=SHR\n//PROTSYM  DD DSN=CAI.PROTSYM,DISP=SHR\n//PROTHLF  DD DSN=CAI.CAVHHLF,DISP=SHR\n//PROTUHF  DD DSN=CAI.PROTUHF,DISP=SHR\n//PROTMLOG DD DSN=CAI.PROTMLOG,DISP=SHR      \nIf you are using the InterTest for CICS dynamic symbolic support feature for Endevor , add an NDVRSYM DD\nstatement to specify the PROTSYM file to be used for dynamic symbolic loading. The NDVRSYM DD must be\nspecified in the CICS startup JCL for InterTest for CICS to invoke the dynamic symbolic load option. A sample\nNDVRSYM DD statement follows:\n//NDVRSYM  DD DSN=CAI.PROTSYM,DISP=SHR\nNOTE\nTo view dumps from another concurrently active CICS region, each region must have its own SymDump  for\nCICS file. In addition, the region used to view the dumps must have a separate FCT entry for each dump file.\nIf you specified more than one symbolic file in the SYMFIL variable of IN25OPTS, include a DD for each SYMFIL\nspecified.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bdf56317da5b-2", "text": "specified.\nAdd the SymDump  for CICS load library to the DFHRPL in the CICS startup JCL.\n//   DD DSN=CAI.CAVHLOAD,DISP=SHR         <productname>\nNOTE\nSymDump  for CICS makes calls to IEWBIND when using the online COMPOSITE module command and\nIEWBIND requires about 750 KB of below the line storage. To make sure that there is sufficient storage\navailable (below the line for IEWBIND calls), you must verify that your DSALIM is at least 750 KB less than\nyour below the line private area size. Failure to do this may result in S0F4 and U900 abends in your CICS\nregion during dump capture.\nWhen you have completed the changes to your CICS startup JCL, restart the CICS region.\n 145", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "50c52bbe7feb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nConfigure Your Product Without CSM\nConfigure your product manually without CSM .\nWhile we recommend that you use CSM  to configure your product, you can also configure your product manually. This\nsection describes the tasks you need to configure your product without CSM . Click on the link for the product that you are\nconfiguring to see the tasks for that product.\nConfiguring SymDump  for CICS\nAfter you complete the installation process, configure SymDump  for CICS using CSM  or using the manual process\noutlined in this article.\nFollow these steps to manually configure your installation of SymDump  for CICS:\n1.Customize Global Options  in CAVHCONF.\n2.Configure the default SymDump  for CICS options .\n3.Configure the dump capture  options.\n4.Configure external security options  in CAVHCONF.\n5.Define the SymDump  for CICS user exits .\n6.Allocate files.\n7.Configure dynamic symbolic support.\n8.Customize the following options:\n\u2013DB2 support\n\u2013Language Environment (LE)\n\u2013DSA limit parameters\n\u2013CICS JCL and startup parameters\n\u2013CICS resource definitions\n\u2013Assembler DSECTs\n\u2013DFHPEP\n9.Review Performance Considerations under CICS Interfaces and Compatibility .\n10.Activate your product.\n11.Verify your installation\nConfiguring InterTest for CICS\nAfter you complete the installation process, configure InterTest for CICS using CSM  or using the manual process outlined\nin this article.\nFollow these steps to manually configure your installation of InterTest for CICS:\n1.Customize  Global Options  in CAVHCONF.\n2.Configure the default CICS options\n3.Configure the InterTest for CICS options\n4.Configure external security options  in CAVHCONF.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "50c52bbe7feb-1", "text": "4.Configure external security options  in CAVHCONF.\n5.Define the InterTest for CICS user exits.\n6.Allocate files.\n7.Configure dynamic symbolic support.\n8.Customize the following options:\n 146", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6e8e0ac1a504-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2013DB2 support\n\u2013DSA limit parameters\n\u2013CICS JCL and startup parameters\n\u2013CICS resource definitions\n\u2013Assembler DSECTs\n9.Customize the following interface and compatibility options for InterTest for CICS :\n\u2013PROMMAC macro\n\u2013CNTL commands\n\u2013Calls to software and macro support\n\u2013DB2 support for InterTest for CICS\n\u2013Wild branch handling\n\u2013Add COBOL file structures to the symbolic file\n\u2013User-defined CORE commands\n\u2013HOGAN software support\n\u2013EDF support\n\u2013MRO support\n10.Review performance considerations.\n11.Activate your product.\n12.Verify your installation.\nConfiguring SymDump  Batch\nAfter you complete the installation process, configure SymDump  Batch using CSM  or using the manual process outlined\nin this article.\nFollow these steps to manually configure your installation of SymDump  Batch:\n1.Customize Global Options  in CAVHCONF.\n2.Configure the default SymDump  Batch Options .\n3.Configure external security options  in CAVHCONF.\n4.Define the SymDump  Batch user exits .\n5.Allocate files.\n6.Configure dynamic symbolic support.\n7.Customize the following Interfaces and Compatibility  options:\n\u2013DB2 support\n\u2013Language Environment (LE)\n\u2013CLISTs\n\u2013ISPF main panel\n\u2013Log and notify procedures\n\u2013Netman\n8.Activate your product.\n9.Verify your installation.\nConfiguring InterTest Batch\nAfter you complete the installation process, configure InterTest Batch using CSM  or using the manual process outlined in\nthis article.\n 147", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4be8cbb89e0c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFollow these steps to manually configure your installation of InterTest Batch:\n1.Customize Global Options  in CAVHCONF.\n2.Configure ISPF options .\n3.Configure batch Link and SYSPLEX .\n4.Configure external security options  in CAVHCONF.\n5.Define the InterTest Batch user exits  .\n6.Allocate files.\n7.Configure dynamic symbolic support.\n8.Customize the following  batch interfaces and compatibility  options:\n\u2013CLISTs\n\u2013Compile procedures\n\u2013ISPF main panel\n\u2013TSO logon procedure\n\u2013Roscoe\n\u2013BTS extended support\n\u2013DB2 SP and IMS/DC Debugging\n9.Activate your product.\n10.Verify your installation\nOptions\nThis article describes options that apply to all InterTest and SymDump  products.\nFor all products, you must update CAVHCONF or the application uses the default values. After you review and optionally\nupdate CAVHCONF, set the options that apply to the specific products that you are installing. These options are described\nin the following pages in this section of the documentation.\nGlobal Options\nThe options that control all products are stored in CAVHCONF. Modify the CAI.CAVHJCL(CAVHCONF) sample JCL to\nupdate the default values before you submit the modified job.\nYou can update any of the following keywords.\nNOTE\nSYMPSWD and EXTSEC=ALL|SYMBOLIC are mutually exclusive and SYMPSWD is ignored if EXTSEC=ALL\nor EXTSEC=SYMBOLIC is specified.\nABEND_PGM_FILTER\nActivates the abend program filtering option in SymDump  Batch. The default is OFF. To activate this option,\nspecify ON and create a list of abend program names in the CAVHFMOD module. The specified abend program", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4be8cbb89e0c-1", "text": "names are then from the dump index and replaced with a meaningful program name. This name is obtained by\ngoing up one level on the active program call chain. Use ABEND_PGM_FILTER to avoid filling the dump index\nwith multiple instances of a common error handling program name.\nNOTE\nThis filtering applies only to the dump index. The abending program name and offset are not changed in\nthe abend report.\nSyntax:\nABEND_PGM_FILTER=( OFF|ON)\n 148", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "756534adb1df-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nFor more information, see Define the Abend Filter Table CAVHFMOD.\nEXTSEC\nSpecifies the external security settings in IN25UTIL and InterTest Batch. Specify SYMBOLIC to activate external\nsecurity for the symbolic file INITIALIZE, UPDATE, DELETE, PURGE, and RELOAD functions. Specify INTBAT to\nactivate external security for mismatched symbolic members.\nSyntax :\nEXTSEC=( NONE|ALL|SYMBOLIC,INTBAT)\nIBSYSPLEX\nSpecifies whether the sysplex support of InterTest Batch is enabled.\nValues: Y, N\nDefault:  N\nPINT\nSpecifies whether a product can be used on a specific LPAR. If permitted, then the normal LMP checks for that\nproduct are performed. If not permitted, a message appears stating that the product is unavailable on this LPAR.\n(This message appears in place of an LMP warning.) The default value is DYNAMIC. This value causes the\nproduct to determine which products have valid LMP keys on an LPAR. The product then sets the product intent\nvalues accordingly.\nSyntax :\nPINT=(INTBAT,INTCICS,SYMBAT,SYMCICS|ALL| DYNAMIC)\nSCHTBSIZE\nSpecifies the maximum number of entries in the Batch Link Scheduling Table for monitoring DB2 stored\nprocedures and IMS/DC transactions.\nLimits:  0 (disables the schedule function) - 60\nNote:  With the schedule function disabled (SCHTBSIZE=0), all DB2 SP and IMS/DC transactions run\nunmonitored.\nDefault:  20\nSYMPSWD\nSpecifies the PROTSYM password.\nDefault: 12345678\nLimits: Up to eight characters\nWORKUNIT\nSpecifies the unit name for temporary data sets.\nDefault : SYSDA", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "756534adb1df-1", "text": "WORKUNIT\nSpecifies the unit name for temporary data sets.\nDefault : SYSDA\nLimits:  Up to eight characters\nExamples:\n CAVHCONF TYPE=CSECT,PINT=DYNAMIC,ABEND_PGM_FILTER=ON\n \n CAVHCONF TYPE=CSECT,PINT=(SYMBAT,INTBAT)\n \n CAVHCONF TYPE=CSECT,PINT=ALL\n \n CAVHCONF TYPE=CSECT,PINT=DYNAMIC\n \n CAVHCONF TYPE=CSECT,SYMPSWD=87654321\n \n CAVHCONF TYPE=CSECT,PINT=(SYMBAT,INTBAT),EXTSEC=SYMBOLIC\n 149", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "177ab8648b5d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n \n CAVHCONF TYPE=CSECT,IBSYSPLEX=Y,SCHTBSIZE=30\n \nSymDump  Batch Options\nThis article describes the following SymDump  Batch options:\nData set CAI.CAVHJCL contains members CAOUDFRX, CAOETABL, and CAOCAB80. These members contain the JCL\nto assemble and link the product defaults.\nData set CAI.CAVHPROC contains the CAOUASML PROC to assemble and link the default table.\nAll SymDump  Batch options default to unfixed, indicating that they can be overridden in the JCL. To fix an option, insert an\nasterisk (*) between the equal sign (=) and the option value.\nOptionally copy and update each member to conform to your installation standards. Submit each job to create a new set\nof defaults.\nWARNING\nEnsure that you change the following data set names to conform to your installation standards:\n\u2022The default symbolic libraries (member CAOUDFRX, macro CAOUSYM)\n\u2022The CAIPRINT repository library (member CAOETABL, option PRTLIB)\nExecution-Time Options CAOUDFRX\nThis section describes the options that SymDump  Batch uses at execution time.\nNOTE\nDefault options member CAOUDFRX contains references to options that are not documented here. These\noptions are used by other Broadcom  products that share this member. These options have no effect on\nSymDump  Batch.\nCAOUSYM dsname\nAdds a symbolic file (a PROTSYM or CSL) to the search list for abend and Snap reports. Insert one CAOUSYM\nstatement for each symbolic file used at your installation.\nCAOUXDUP modname\nSpecifies whether to add a control section name to the exclusion list for duplicate dump suppression. Control", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "177ab8648b5d-1", "text": "Specifies whether to add a control section name to the exclusion list for duplicate dump suppression. Control\nsections in the exclusion list are not subject to the duplication limit (DUPLIM) value. Exclude as many control\nsections as needed by including one CAOUXDUP statement for each name.\nCAOUXMOD modname\nSpecifies whether to add a control section name to the exclusion list for abend reports. Control sections in the\nexclusion list are not displayed in dump format as part of an abend report. Exclude as many control sections as\nneeded by including one CAOUXMOD statement for each name.\nDUPLIM=5| nnn\nSpecifies the maximum number of duplicate reports to store in a single repository. Specify a number from 1 to\n999, or specify 0 to suppress duplication checking. Duplicate reports have the same abending program name,\nprogram offset, and completion code. Lowering the value of DUPLIM does not delete any existing reports in the\nrepository.\nEXPDAYS=0|nnn\nSpecifies the maximum number of days to retain a report in the repository, starting from the day it is added.\nSpecify the number of days from 1 to 999, or specify 0 to suppress report expiration. Expired reports are\n 150", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5a8f39914a36-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nautomatically deleted during the auto-maintenance cycle. This cycle occurs immediately before any new report\nis added. During auto-maintenance, the age of each report is compared to the current  EXPDAYS value. (Auto-\nmaintenance does not use the EXPDAYS value when the reports were added.)\nLANGMSG=ENGLISH| xxxxxxxx\nSpecifies the language in which to write all execution-time messages. Only ENGLISH is supported currently.\nLANGWTO=ENGLISH|xxxxxxxx\nSpecifies the language in which to write all execution-time WTOs. Only ENGLISH is supported currently.\nLIBDD=SYSLIB| ddname\nSpecifies the ddname that MRS uses to identify the load library being reported on.\nLINECNT=60| nnn\nSpecifies the maximum number of lines to display on a page for all execution-time reports.\nNDVRDD=CAINDVR| ddname\nSpecifies the ddname that is used in the execution JCL to define the symbolic file. The symbolic file is populated\ndynamically when Dynamic Symbolic Support (NDVRDSS) is active for Endevor .\nNDVRDSN= dsname\nSpecifies the symbolic file that is populated dynamically when Dynamic Symbolic Support (NDVRVSS) is active\nfor Endevor . Specify a PROTSYM file. When a data set is specified, it is included in the symbolic file search list\nautomatically. If you do not want to specify a default dsname, leave this option blank.\nNDVRPROC= procname\nSpecifies the seven-character prefix of the procedure name. This procedure is started when Dynamic Symbolic\nSupport (NDVRDSS) is active for Endevor  and when multiple site IDs are used by the installation.\nOPTSDD=CAIOPTS| ddname", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5a8f39914a36-1", "text": "OPTSDD=CAIOPTS| ddname\nSpecifies the ddname that references the execution-time options data set.\nPANACCS=PANEACCS|pgmname\nSpecifies the Panexec  library access routine. This option is ignored at execution time if PANEXEC=OFF is\nspecified.\nPANEXEC=OFF|ON\nSpecifies whether Panexec  is present on the system.\nPRINTDD=CAIPRINT| ddname\nSpecifies the ddname that references the report file.\nPRTLBDD=CAIPRTLB|ddname\nSpecifies the ddname that references the central VSAM repository.\nREGMAX=( nnnn |128,nnnn |256)\nSpecifies the number of storage bytes to format before and after each register address for Assembler programs.\nSAVEHEAP=ON|OFF\nSpecifies whether to save LE or PL/I heap storage for abending applications.\nSHOWHEAP=ON|OFF\nSpecifies whether to format LE or PL/I heap storage. For LE enabled Assembler or PL/I programs,\nSHOWHEAP=ON requires SAVEHEAP=ON at execution time.\nSHOWUNMRG=ALL|NONE|TBLS\nSpecifies whether to display storage for which symbolic names are not merged. This option applies only when\nmerging options are used. This storage can result from slack  bytes between fields. This storage can also result\nfrom table entries which are not merged because of limits imposed by the OCCURS option. The following options\nare valid:\nALL\nFormats all unmerged storage.\n 151", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d087342481bb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNONE\nSuppresses unmerged storage.\nTBLS\nFormats only table storage which is unmerged because of the limits imposed by the OCCURS option.\nSNAPS=0| nnnnn |ON|OFF\nSpecifies the maximum number of Snap reports to produce during a job step. When this value is exceeded, all\ncalls to CAODSNAP are ignored.\nThe default value for nnnnn is 32767.\nNOTE\nEach call to CAODSNAP generates a separate SNAP report in your central VSAM repository. If your\nprogram contains multiple SNAP calls or a SNAP call within a loop, you can flood the repository. To\navoid this problem, you can write the output to the CAIPRINT DD alone. See the PRTREPT option.\nSPBLKLN=0| nnnnn\nSpecifies the default block length to use for dynamic allocation.\nSPPRIM=1| nnnnnnnn\nSpecifies the primary space allocation to use for dynamic allocation.\nSPSECND=1| nnnnnnnn\nSpecifies the secondary space allocation to use for dynamic allocation.\nSPUNITS=CYL|TRK|BLK\nSpecifies the default space units to use for dynamic allocation.\nSTORCLS=storclas\nSpecifies the default storage class to use for dynamic allocation. Currently, this option is used only for temporary\nfiles that the viewer creates.\nSUPPRS=OFF|ON\nSpecifies whether to suppress the following items:\n\u2022The CAIOPTS File Processing report and Report Summary for programs containing snap calls when the\nSNAP option is OFF.\n\u2022The CAIOPTS File Processing report and Execution Monitor Summary for applications containing one or more\nprograms that were optimized using the Optimizer/II  DTECT option and which terminate normally.\nSYMDD=CAISYM| ddname", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d087342481bb-1", "text": "SYMDD=CAISYM| ddname\nSpecifies the ddname that is used in your execution JCL to define a symbolic file override.\nSYSOUT=*| x\nSpecifies the default SYSOUT class to use when report files or dump files are allocated dynamically.\nSYSOUTD=destination\nSpecifies the default destination for SYSOUT data sets that are allocated dynamically for report or dump files. The\ndefault is blank. When blank, no destination is used.\nUNIT=SYSDA| xxxxx\nSpecifies the default UNIT name to use for dynamic allocation.\nUSERID='CA'| string\nSpecifies a text string that appears in the top left corner of each page of the execution reports.\nAbend Handler and Reporter CAOETABL\nNOTE\nIf SymDump  System is also installed, set the DUMP option to ON in the default member CAOETABL.\n 152", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b3ade0ce41fd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nExclusion Options\nCAOETABL includes the CAOETXCL macro, which lets you specify exclusion criteria for your abend reports.\nYou can use the following wildcard characters when specifying your criteria:\n*\nDenotes a prefix. For example,\nABC*\nexcludes all items that start with ABC.\n?\nIndicates a single character. For example,\nAB??EFGH\nexcludes any items that start with \"AB\" and have \"EFGH\" in positions 5-8.\n:\nDelimits a range. For example,\n100:200\nexcludes any account number from 100 to 200.\nNOTE\nThis wildcard applies only to the ACCOUNT= keyword.\nYou can specify the following keywords in the CAOETXCL macro:\nABNDCDE=\nSpecifies a list of the system abend codes to exclude. Each entry is exactly 3 bytes.\nACCOUNT=\nSpecifies a list or range of account numbers to exclude. If an account number includes subfields, they are\nconcatenated and treated as a single field. The maximum length is 25 bytes.\nJOBNAME=\nSpecifies a list of job names to exclude. The maximum length is 8 bytes.\nPGMNAME=\nSpecifies a list of program names to exclude. These names correspond to the name of the job step program.\nThese names do not necessarily match the name of the abending program. The maximum length is 8 bytes.\nSMFIDS=\nSpecifies the SMF ID of the running system to exclude. The maximum length is 4 bytes.\nSUBSYS=\nSpecifies the subsystem type to exclude. Subsystem means a batch job (INIT), a started task (STC), a TSO\nsession (TSO), IMS, DB2, or Datacom/DB .\nUSRABND=", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b3ade0ce41fd-1", "text": "USRABND=\nSpecifies a list of the user abend codes to exclude. Each entry is exactly 4 bytes.\nReporting, Logging, and Security Options\nUse the following keywords in macro CAOETGEN to set the reporting, logging, and security options:\nACB=OFF|ON\nSpecifies whether to print the access method control blocks for open VSAM files.\nAMB=OFF|ON\nSpecifies whether to print the access method blocks for open VSAM files.\n 153", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "65ea03879c1b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAMBL=OFF|ON\nSpecifies whether to print the access method block list for open VSAM files.\nASMINST=ON|OFF\nDisplays the abending Assembler instruction and associated operands on the abend page.\nBLLMAX=512|nnnnn\nSpecifies the maximum number of bytes to format for an unknown BLL cell range. (The length of an 01-item in the\nLINKAGE SECTION cannot always be determined.) The maximum value is 4096.\nBINDER=ON|OFF\nSpecifies whether to access user load modules through the binder API function calls or the standard I/O macros.\nBINFRMT=DEC|HEX\nSpecifies whether to display the binary data values in decimal display or hexadecimal format.\nBLOCKS=OFF|ON\nSpecifies whether to print all data management control blocks. This keyword overrides all other options that\ncontrol the formatting of control blocks.\nCOBONLY=OFF|ON\nSpecifies whether to suppress an abend report when the ABEND does not occur in a COBOL program.\nDB2ACTIV=OFF|ON\nSpecifies whether to display summary information for packages and DBRMs that are active when an ABEND\noccurs.\nDCB=OFF|ON\nSpecifies whether to format the data control blocks for all open files.\nDEB=OFF|ON\nSpecifies whether to format the data extent blocks for all open files.\nDUMP=OFF|ON\nSpecifies whether to produce a system dump after the abend report is written.\nFILES=ON|OFF\nSpecifies whether to report on all open files that did not appear in the File Section displays for any COBOL\nprogram in the abend report.\nFST128=OFF|ON\nSpecifies whether to limit the display of file buffers to the first 128 bytes. This option affects the File Section", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "65ea03879c1b-1", "text": "displays and the Open Files report.\nGRPADDR=ON|OFF\nSpecifies whether to display the base locator, displacement, and address of a group item on the merged Data\nDivision displays.\nIOB=OFF|ON\nSpecifies whether to format the input/output blocks for all open files.\nLINECNT=60| nnn\nSpecifies the maximum number of lines to display on each page of an abend or Snap report.\nLINKAGE=ON|OFF\nSpecifies whether to format the LINKAGE SECTION of any COBOL program being reported on.\nLCLSTOR=ON|OFF\nSpecifies whether to format the LOCAL-STORAGE SECTION of any COBOL program being reported on.\nLISTLINE=0| nn\nSpecifies the number of extra listing lines to merge into a report before and after the source statement at ABEND,\nsnap, or transfer.\n 154", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "51bc31af01d9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nLOGNET=OFF|ON\nSpecifies whether to write a record to Netman  to use for automated problem tracking. If ON is specified, also set\nthe Netman  files that are required for Machine-Generated Problem Tracking (MGPT).\nLOGROS=ON|OFF\nSpecifies whether to send a message describing the ABEND to the Roscoe  IE user who submitted the job. If ON\nis specified, also specify the Roscoe  IE job name in the ROSCOE option.\nLOGTSO=ON|OFF\nSpecifies whether to send a message describing the ABEND to the TSO user who submitted the job.\nLOGUNI=ON|OFF\nSpecifies whether to send a message describing the ABEND to the NSM  console.\nMEMMAP=ON|OFF\nSpecifies whether to format the DSA, TGT, and PGT Memory Maps for any COBOL program being reported on.\nMERGEDB=ON|OFF\nSpecifies whether to map areas in the DB2, IDMS/DB , and IMS database reports symbolically.\nMRGAUTO=ON|OFF\nSpecifies whether to merge symbolic names onto automatic storage for PL/I procedures.\nMRGBASED=ON|OFF\nSpecifies whether to merge symbolic names onto based variable storage for PL/I procedures.\nMRGCNTLD=ON|OFF\nSpecifies whether to merge symbolic names onto controlled storage for PL/I procedures.\nMRGDATA=ON|OFF\nSpecifies whether to turn all merging options ON or OFF.\nMRGDSECT=ON|OFF\nSpecifies whether to merge symbolic names onto Assembler program storage when DSECTs are used and\nUSINGs are defined.\nMRGFILES=ON|OFF\nSpecifies whether to map the FILE SECTION display symbolically.\nMRGLINK=ON|OFF", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "51bc31af01d9-1", "text": "Specifies whether to map the FILE SECTION display symbolically.\nMRGLINK=ON|OFF\nSpecifies whether to map the LINKAGE SECTION display symbolically.\nMRGLOCAL=ON|OFF\nSpecifies whether to map the LOCAL-STORAGE SECTION display symbolically.\nMRGPARMS=ON|OFF\nSpecifies whether to merge symbolic names onto parameter storage for PL/I procedures.\nMRGSTAT=ON|OFF\nSpecifies whether to merge symbolic names onto static storage for PL/I programs.\nMRGWORK=ON|OFF\nSpecifies whether to map the WORKING-STORAGE SECTION display symbolically.\nNDVRASM=OFF|ON\nSpecifies whether the symbolic file is always populated dynamically for assembler programs which are not LE\nenabled. This option takes effect only when Dynamic Symbolic Support (NDVRDSS) is active for Endevor .\nNDVRDSS=OFF|ON\nSpecifies whether Dynamic Symbolic Support is active for Endevor .\nNTMGCTL=CAI.NTMMGCTL|OFF\nSpecifies the Netman  NTMMGCTL file that is allocated dynamically when LOGNET=ON is specified.\n 155", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "40b1db27ae3b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNTMPI=CAI.NTMPI| dsname\nSpecifies the Netman  NTMPI file that is allocated dynamically when LOGNET=ON is specified.\nNTMSC=CAI.NTMSC| dsname\nSpecifies the Netman  NTMSC file that is allocated dynamically when LOGNET=ON is specified.\nOCCURS=1| nnnnnnnn |MAX\nSpecifies the maximum number of table occurrences to map symbolically when using the merging options. MAX\nsets the option to its maximum value of 16777215.\nOPMEM=xxxxxxx\nSpecifies the member name that contains the execution options when the options file is a dynamically allocated\nPDS.\nOPSUFIX=CAIOPTS| xxxxxxxx\nSpecifies the suffix to append to the user ID that submitted the job. This suffix is used when no options data set is\nincluded in the JCL. The suffix and ID create the options data set name for dynamic allocation.\nOPTSDD=CAIOPTS| ddname\nSpecifies the ddname for the options file that is dynamically allocated when it is not specified in the JCL. The\nabend Handler/Reporter performs the dynamic allocation, but the Execution Monitor reads the file. This name\nmust match the name that is specified for the same variable in the CAOETGEN defaults member.\nPLH=OFF|ON\nSpecifies whether to format the place holders for open VSAM files.\nPRTLHCT=80|nn\nSpecifies the percent full the PRTLIB dataset must reach to trigger a health check exception condition. If this\npercentage is reached the health check program will go into exception state and issue consol messages every 15\nminutes until the problem is corrected.\nPRTLIB=CAI.PRTLIB|dsname", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "40b1db27ae3b-1", "text": "minutes until the problem is corrected.\nPRTLIB=CAI.PRTLIB|dsname\nSpecifies the central VSAM repository to write abend and Snap reports. If you do not want to use a repository,\nleave this option blank. For more information, see Allocate CAIPRINT Repository Library.\nPRTREPT=BOTH|REPOS|PRTDD\nSpecifies whether to write abend or Snap reports to the central VSAM repository (REPOS), the CAIPRINT DD\n(PRTDD), or both.\nREADLL=ON|OFF\nSpecifies whether SymDump  Batch reads the LINKLIST libraries to obtain module information for abend and\nSnap reports. If READLL is OFF, SymDump  Batch may not be able to report on programs that were loaded from\nLINKLIST.\nREGMAX=( nnnn |128,nnnn |256)\nSpecifies the number of storage bytes to format before and after each register address for Assembler programs.\nROSCOE= list of names\nSpecifies the Roscoe  IE job names to use when LOGROS=ON is specified. You can include up to four names.\nRPL=OFF|ON\nSpecifies whether to format the request parameter list for open VSAM files.\nRPTSZ80=OFF|ON\nSpecifies whether to force all data that is in dump format to appear in an 80-column format.\nSAVEHEAP=ON|OFF\nSpecifies whether to save LE or PL/I heap storage for abending applications.\nSHOWHEAP=ON|OFF\nSpecifies whether to format LE or PL/I heap storage. For LE enabled Assembler or PL/I programs,\nSHOWHEAP=ON requires SAVEHEAP=ON at execution time.\n 156", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cde77f45d11c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSHOWUNMRG=ALL|NONE|TBLS\nWhen merging options are used, this option specifies whether to display storage for which symbolic names are\nnot merged. This storage can result from \"slack\" bytes between fields. This storage can also result from table\nentries that are not merged because of limits imposed by the OCCURS option. The following options are valid:\nALL\nFormats all unmerged storage.\nNONE\nSuppresses unmerged storage.\nTBLS\nFormats only table storage which is unmerged because of the limits imposed by the OCCURS option.\nSMF=OFF|ON\nSpecifies whether to write a record to the System Management Facility. If ON is specified, include the SMF record\nnumber in the SMFREC option.\nSMFREC= nnn\nSpecifies the SMF record number for SMF recording when SMF=ON is specified. This value must be from 128\nthrough 255, and it cannot conflict with an existing record number.\nSNAPS=ON|OFF\nSpecifies whether to support SNAP requests in a program.\nNOTE\nEach call to CAODSNAP generates a separate SNAP report in your central VSAM repository. If your\nprogram contains multiple SNAP calls or a SNAP call within a loop, you can flood the repository. To\navoid this problem, write the output to the CAIPRINT DD alone. See the PRTREPT option.\nSTOPDD=CAOESTOP|ddname\nSpecifies the ddname that is used in the execution JCL to suppress abend reports.\nSVAREA=ON|OFF\nSpecifies whether to produce a Save Area Trace report. This report shows the changed save areas, starting with\nthe program that abended.\nSYSOUT=*| x\nSpecifies the default SYSOUT class to use at execution time when report files or dump files are allocated", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cde77f45d11c-1", "text": "Specifies the default SYSOUT class to use at execution time when report files or dump files are allocated\ndynamically.\nUCB=OFF|ON\nSpecifies whether to format the unit control blocks list for open files.\nVSAMCAT=OFF|ON\nSpecifies whether to format the VSAM catalog information for each open VSAM file.\nVSMIDX=OFF|ON\nSpecifies whether to format the VSAM indexed control blocks for the index portion of each open VSAM file\nwith the control blocks for the data portion.\nWRKSTOR=ON|OFF\nSpecifies whether to format the WORKING-STORAGE of each COBOL program in an abend report.\nWTL=OFF|ON\nSpecifies whether to send a message describing the ABEND to the system log.\nWTO=ON|OFF\nSpecifies whether to send a message describing the ABEND to the job log (using WTO with ROUTCDE=11).\n 157", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6b3bc94a7f63-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWTOXCL=OFF|ON\nSpecifies whether to send a message which describes the reason that a report was not generated because of\nexclusion criteria.\nDefine the User Abend Control Table CAOCAB80\nThe following tables control the abend processing:\nProduct Table\nContains predefined controls. The product table contains only the common system abend codes.\nUser Table\nContains user-defined abend control entries. These entries can define new controls, and can also override\nexisting controls in the product table.\nNOTE\nThe user abend control table must be link-edited with the load module name CAOCAB80.\nEach entry in a control table defines the processing options for a specific abend code.\nYou can design diagnostic programs for the user abends and system abends.\nFollow these steps:\n1.Add an entry to the user abend control table, CAOCAB80, for the specific abend using the DMOD parameter.\n2.Use the CPXACODE macro (included with the product) to define user abend control table entries for CAOCAB80. The\nfollowing example shows the syntax to use. The first positional parameter is required.\n[label] CPXACODE START\n        CPXACODE abendcode [,keyword=ON|OFF[,...]] [,DMOD= modulename ]\n        CPXACODE END\n\u2013label\nIdentifies a specific code section.\n\u2013START\nGenerates a CSECT statement. If a label is specified, the label is used as the CSECT name. Otherwise, the\ngenerated CSECT name is the default, CAOCAB80.\nNOTE\nThe CSECT must be link-edited as a single CSECT load module. The module must be named\nCAOCAB80.\n\u2013abendcode", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6b3bc94a7f63-1", "text": "CAOCAB80.\n\u2013abendcode\nSpecifies the abend code. The following values are valid:\n\u2022S001-SFFF (for the system abend codes)\n\u2022U0001-U4095 (for the user abend codes)\n\u2013keyword\nSpecifies a keyword and whether to enable the abend reporting function:\nON\nEnables the abend reporting function for this keyword.\nOFF\nDisables the abend reporting function for this keyword.\nThe keywords in this macro have the same function as the keywords in the CAIOPTS (SYSIN) data set. For  more\ninformation about these keywords, see SymDump  Keyword Descriptions and Data Management Control Block\nKeywords.\n\u2013DMOD\n(Optional) Specifies the program name of an existing user diagnostic module.\n 158", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1dc30cd1cf46-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe SymDump  Batch diagnostic modules are still called when the user CPXACODE macro definitions do not\nspecify the DMOD operand.\n\u2013END\nGenerates a trailer table entry that must be specified last.\nExample:\nThe following syntax adds a new entry to the user control table:\nCAOCAB80 CPXACODE START\n         CPXACODE U1005,BLOCKS=ON,DUMP=OFF\n         CPXACODE S322,DUMP=OFF,DMOD=TIMEOUT\n         CPXACODE END\n         END\nSymDump  Batch Keyword Descriptions\nThis section describes the SymDump  Batch keywords:\nDTECT\nTurns abend reporting on and off.\nDefault:  ON\nDUMP\nForces a SYSUDUMP.\nDefault:  OFF\nF128\nPrints only the first 128 bytes of a record.\nDefault:  OFF\nMEMMAP\nPrints the DSA, TGT, and PGT memory map.\nDefault:  ON\nFILES\nPrints open files report.\nDefault:  ON\nSAVEAREA\nPrints the save area trace report.\nDefault:  ON\nData Management Control Block Keywords\nThis section describes the Data Management Control Block keywords:\nBLOCKS\nSets all Data Management keywords to OFF.\nDefault:  OFF\nACB\nIncludes the VSAM Access Method Control Block.\nDefault:  OFF\nAMB\nIncludes the VSAM Access Method Block.\nDefault:  OFF\n 159", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2839471a1ed7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAMBL\nIncludes the VSAM Access Method Block List.\nDefault:  OFF\nDCB\nIncludes the Data Control Block.\nDefault:  OFF\nDEB\nIncludes the Data Extent Block.\nDefault:  OFF\nIOB\nIncludes the I/O Block.\nDefault:  OFF\nPLH\nIncludes the VSAM Place Holder.\nDefault:  OFF\nRPL\nIncludes the VSAM Request Parameter List.\nDefault:  OFF\nUCB\nIncludes the Unit Control Block.\nDefault:  OFF\nVSAMIDX\nIncludes the VSAM Indexed Control Blocks.\nDefault:  OFF\nNOTE\nUse ON to print the indicated control blocks; use OFF if you do not want the control block to print.\nUser-Supplied Abend Diagnostic Modules\nYou can develop abend diagnostics modules to supplement SymDump  Batch processing. These programs provide\ndiagnostic material for the abend and diagnostic logic to determine the abend cause.\nSymDump  Batch provides a CPXDIAG macro to help you build diagnostic modules. This macro provides entry logic and\nexit logic, user workspace, and addressability to parameter information. This macro also provides the Abend Reporter\ninterface for printing lines and altering abend control information.\nThe use of the CPXDIAG macro assumes the following register conventions:\nRegister Description\nR0, R1, R14, R15 Standard macro linkage and usage\nR13 Provides addressability to register save area, parameter\ninformation, print line build area, and user workspace\nR12 Program base register\nSee the following CPXDIAG function definitions:\n\u2022The following syntax establishes the CSECT name and the program and DSECT addressability, and saves the caller\nregisters. Specify this function type first and code a label.\nlabel CPXDIAG TYPE=START", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2839471a1ed7-1", "text": "label CPXDIAG TYPE=START\n\u2022The following syntax restores the caller registers and returns. Specify this function at the end of your processing.\n 160", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "47267f01a05c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nlabel CPXDIAG TYPE=END\n\u2022The following syntax writes a block of text to the abend report. The text is automatically centered on the report.\nEnclose each line of text in apostrophes. Verify that each line is less than or equal to 76 bytes. Generate blank lines by\ncoding two or more contiguous commas.\nlabel CPXDIAG TYPE=BLKTEXT,'L1', 'L2', 'L3',\u2026'Ln'\n\u2022The following syntax writes a 133-byte line of data to the abend report. Provide the address of this line by using the\nAREA keyword. The first byte of the line is reserved for an ASA control character; you must place one there.\nlabel CPXDIAG TYPE=PRINT,Rx,AREA= < label>\n\u2022The following syntax alters the abend control table options, but only for the current execution. You can specify one\nor more of the listed keywords. Assign a value of ON or OFF to each keyword. See the third point in the following\nexample.\nlabel CPXDIAG TYPE=ALTER, ACB=, AMB=, AMBL=,BLOCKS=, DCB=, DEB=,DTECT=, DUMP=, FILES=,F128=, IOB=,\n MEMMAP=,PLH=, RPL=, SAVAREA=,UCB=,\nExample:\nThe following example shows a user diagnostic module:\nSR1234  CPXDIAG  TYPE=START  establish CSECT name and addressability\n1.           CPXDIAG  TYPE=BLKTEXT,                                   x\n                      'U1234 - PAYROLL SYSTEM ABEND.',                X\n                      'FICA TABLE IS NOT CURRENT'                     X \n                .\n                . \n                .", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "47267f01a05c-1", "text": ".\n                . \n                .\n         user diagnostic logic\n                .\n                .\n                .\n2.          MVI CPXLINE,C'0'                DOUBLE SPACE\n            MVC CPXLINE+1(132),FICATABLE    LOAD 132 CHARACTER AREA\n            CPXDIAG     TYPE=PRINT,AREA=CPXLINE\n            \n3.          CPXDIAG     TYPE=ALTER,                                   X\n                        DUMP=OFF,DTECT=OFF\n            CPXDIAG     TYPE=END Notes:\nConsider the following important points:\n\u2022When printing a text block, create a double space by specifying a NULL operand. (This operand consists of two\napostrophes with no intervening spaces; for example,  '' .) Enclose all text in single quotes. Each text block can\ncontain up to 76 characters between the quotes.\n\u2022When using carriage control characters, consider the following information:\n\u2013'blank' represents a single space.\n\u2013'0' represents a double space.\n\u2013'-' represents a triple space.\n\u2022Instruct SymDump  Batch not to perform any additional abend processing and to suppress the system dump.\nThe following information is available to the user diagnostic module automatically. The CPXDIAG TYPE=START macro\nautomatically provides addressability using Register 13. You can build your own print lines in the CPXLINE space\nprovided, or by using the TYPEPRINT macro. In addition, 120 bytes of workspace are provided at CPXUSPCE for your\nown routines.\nCPXDSECT  DSECT\n 161", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3fffe47bad01-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCPXSAVE   DS   18F    REGISTER SAVE AREA\nCPXIFACE  DS   A      ADDRESS OF MACRO INTERFACE TO DETECTOR\nCPXMDGBL  DS   A      INTERFACE PARM\nCPXIPRM   DS   5A     PARM LIST TO INTERFACE RTN\nCPXTCB    DS   A      ADDRESS OF ABENDING TASK TCB\nCPXTIOT   DS   A      ADDRESS OF ABENDING TASK TIOT\nCPXCSECT  DS   CL8    ABENDING CSECT NAME\nCPXENTRY  DS   A      ABENDING CSECT ENTRY POINT ADDRESS\nCPXDATE   DS   CL8    CURRENT DATE \"MM/DD/YY\" GREGORIAN FORMAT\nCPXTIM    DS   CL8    TIME OF ABEND \"HH.MM.SS\" FORMAT\nCPXSFLAG  DS   X      STAE/ESTAE FLAGS\nCPXREQ    EQU  X'80'  DUMP REPORT HAS BEEN TERMINATED, STEP OPTION\n                      SPECIFIED ON ABEND MACRO    \nCPXSTCC   EQU  X'10'  DON'T STORE COMPLETION CODE, NOT USED IN OS/VS2\nCPXRETCD  DS   XL1    SYSTEM RETURN CODE FOR GIVEN ABEND\n          DS   XL1    FUTURE USE \nCPXATYPE  DS   CL1    ABEND TYPE\nCPXUSER   EQU  C'U'   USER ABEND\nCPXSYSTEM EQU  C'S'   SYSTEM ABEND\nCPXACODE  DS   CL4    ABEND CODE 0001-FFFF\nCPXAPSW   DS   XL8    PSW AT ENTRY TO ABEND\nCPXPPSW   DS   XL8    LAST PROBLEM PROGRAM PSW", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3fffe47bad01-1", "text": "CPXPPSW   DS   XL8    LAST PROBLEM PROGRAM PSW\nCPXRO     DS   F      REGISTERS AT ABEND\n  .       .    .      .\n  .       .    .      .\n  .       .    .      .\nCPXR15    DS   F          \n          DS   8A     FUTURE USE\nCPXLINE   DS   CL133  USER PRINT LINE WORK AREA\n          DS   XL3    FUTURE USE\n          DS   OF\nCPXUSPCE  DS   XL120  USER WORK SPACE\nCPXLENGTH EQU  *-CPXDSECT  LENGTH OF DIAGNOSTIC INFORMATION AREA\nThe following table contains the default product settings. You can update CAOCAB00 to change these settings.\nAbend Code FIRST128 MEMMAP FILES SAVEAREA DUMP\n001 ON ON ON\n002 ON ON\n013 ON ON\n031 ON\n038 ON\n03D\n0C1 ON ON ON ON\n0C2 ON ON ON ON\n0C4 ON ON ON ON\n0C5 ON ON ON ON\n0C6 ON ON ON ON\n0C7 ON ON\n 162", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "937edd66e19f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n0C8 ON ON\n0C9 ON ON\n0CA ON ON\n0CB ON\n137 ON ON\n213 ON ON\n214 ON ON\n237 ON ON\n314 ON ON\n322 ON ON ON\n413 ON\n513 ON ON ON\n522 ON\n613 ON ON\n637 ON ON\n706 ON\n713 ON\n714 ON ON ON\n722 ON ON ON\n804 ON\n806 ON ON\n80A ON ON\n813\n913 ON ON\nA13 ON ON\nB37 ON ON\nC13 ON ON\nD37 ON ON\nE37 ON ON\nDefault Entry (for\nany abend types not\nshown)ON ON ON ON\nDefine the Abend Filter Table CAVHFMOD\nThe CAI.CAVHJCL(CAVHFMOD) member controls which abend program names are filtered from your dump index. This\nmember is used by SymDump  Batch.\nMany of your applications may use a common abend handling program. When an abend occurs, the common program\nname and its offset appear in the dump index for all application failures. Multiple occurrences of a common name make\nit difficult to identify the abending application correctly. This problem also makes it difficult to implement automatic\nnotification of the appropriate personnel when production failures occur.\n 163", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cb6d30a0f84c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nHowever, you can use CAVHFMOD to specify one or more program names to filter. When an application abends, the\nspecified names do not appear in the dump index. Instead, they are replaced with a meaningful program name and offset.\nThese values are obtained by going up one level on the active program call chain.\nNOTE\n\u2022The program names that you specify here are not filtered from the dump index unless you activate the\nfiltering option. Specify ABEND_PGM_FILTER ON in CAI.CAVHJCL(CAVHCONF).\n\u2022This filtering applies only to the dump index. The abending program name and offset are not changed in the\nabend report.\nTo configure the CAVHFMOD options, access the member and edit its JCL. This member contains sample JCL to\nassemble and link the CAVHFMOD filter table.\nUse the following syntax to specify which program names to filter:\nCAVHFMOD START\nCAVHFMOD FILTER,PROGRAM= name\nCAVHFMOD END\nSTART\nIndicates the start of the abend program list. Specify START once, before any FILTER syntax.\n\u2022FILTER,PROGRAM=name\nSpecifies a program name to filter. You can specify a fully qualified program name. You can also use the following\nwildcards:\n*\nDenotes a prefix. For example,\nABC*\nselects all program names that start with ABC.\n?\nIndicates a single character. For example,\nAB??EFGH\nselects all program names that start with \"AB\" and have \"EFGH\" in positions 5-8.\nEND\nIndicates the end of the abend program list. Specify END once, after all FILTER syntax.\nExample: Filter Four Program Names From the Dump Index", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cb6d30a0f84c-1", "text": "Example: Filter Four Program Names From the Dump Index\nThe following syntax sample specifies four abend program names to filter:\nCAVHFMOD START\nCAVHFMOD FILTER,PROGRAM=IEFBR14\nCAVHFMOD FILTER,PROGRAM=CEE*\nCAVHFMOD FILTER,PROGRAM=I?BABEND\nCAVHFMOD FILTER,PROGRAM=USERDUMP\nCAVHFMOD END END ,\nWhen this syntax is submitted, the specified program names are filtered out. These names are replaced with the program\nname from the preceding level of the active program call chain.\nFacilitate Multiple Default Execution Options\nThe SymDump  Batch defaults are established during installation. Each application programming area that uses SymDump\nBatch can require different run-time defaults. In that case, the desired options are passed to the Execution Monitor by\nusing the CAIOPTS data set.\n 164", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6216e9307066-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFollow these steps:\n1.Establish a library for the default options.\n2.Create a library member for each programming area. Populate each member with the appropriate execution options\nfor that area.\n3.Verify that the CAIOPTS DD points to the correct library member.\nExamples:\nUse the following syntax when the program is executed directly:\n//CAIOPTS DD DSN=EXEC.PARAMLIB(MEMBERA),DISP=SHR\nUse the following syntax to override a default option in the library member. After this syntax, add the syntax for those\noptions that are different from, or not specified in, the MEMBERA member.\n//CAIOPTS DD DSN=EXEC.PARAMLIB(MEMBERA),DISP=SHR\n//        DD *\nUse the following syntax when a GO step in a cataloged procedure executes the program. Specify your member name\nusing the symbolic parameter PARAMEM when invoking the procedure.\n//CAIOPTS DD DSN=EXEC.PARAMLIB(&PARAMEM).,DISP=SHR\nUse the following syntax to override a default option in the library member. After this syntax, add the syntax for those\noptions that are different from, or not specified in, the MEMBERA member.\n//GO.CAIOPTS DD DSN=EXEC.PARAMLIB(MEMBERA),DISP=SHR\n//           DD *\nNOTE\nIf SymDump  System is also installed, specify DUMP=ON in the default member CAOETABL.\nInterTest Batch Options\nThis section contains instructions how to customize InterTest Batch ISPF options, batch link options and enable the Cross-\nLPAR debugging feature.\nConfigure ISPF Options\nWhen you configure InterTest Batch without CSM , use member INTISPF in the CAVHSAMP library to customize the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6216e9307066-1", "text": "options that are passed to the application when it is invoked under ISPF.\nThe INTISPF member parameters are as follows:\nISPF\nThis is required to run the application under the ISPF dialog manager.\nSYMLDYN\nThis parameter is no longer used.\nTRACE(n)\nSpecifies the number of entries to be saved in the trace table and displayed by the TRACE and TRACE SOURCE\ncommands. The default is 1000 and n is an integer between 1 and 32760.\nEXTSTOR(nM|nK)\nThe extended storage parameter allows you to set the amount of extended storage that is accessed by InterTest\nBatch under the z/OS operating system. This storage is used when formatting data preceding the 16 MB line. The\n 165", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "22dbb21ba902-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\ndefault amount is 64M. Specify the amount in megabytes (M) or kilobytes (K), and n is any integer between 1 and\n100.\nLINKPARM(n)\nSpecifies the maximum number of linkage parameters that can be set by the installation. The default is 32 and n\nis any integer between 1 and 1000. Each linkage parameter requires a page of memory (4096 bytes) unless the\ndefault has been changed.\nLINKSIZE(n)\nSpecifies the amount of memory to be getmained for each linkage parameter. The default is 4096. It is not\nrecommended to specify less than 1024 or more than 32768. The parameters are always on page boundaries.\nNOSLOW\nTurns off the SLOW command at the installation. The users are notified with a message stating this when\nattempting to use the SLOW command. Comment this parameter out if you do not want the SLOW command\ndisabled.\nSLOWFAST(n)\nSpecifies the duration of the wait time in hundredths of a second between executable statements when using the\nSLOWFAST command. The default is one quarter of a second (n=25). The value is any integer between 1 and\n4096. This might be helpful to TCAM users with buffering problems.\nNOSTAX\nThis is a required startup parameter.\nNOESTAE\nThis is a required startup parameter.\nNOSTAE\nThis is a required startup parameter.\nNOESTAI\nThis is a required startup parameter.\nNOJSCB\nThis is a required startup parameter.\nConfigure Batch Link and Sysplex\nConfigure the batch link schedule feature to leverage your DB2 stored procedure and IMS/DC testing environment.\nDefine the Batch Link Scheduling Table", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "22dbb21ba902-1", "text": "Define the Batch Link Scheduling Table\nThe batch link schedule feature helps you to leverage your DB2 stored procedure and IMS/DC testing environment by\nallowing you to specify exactly which of these programs you want InterTest Batch to monitor. To enable the batch link\nschedule feature, customize the SCHTBSIZE option in CAVHCONF. For more information, see Options.\nThe SCHTBSIZE parameter of macro CAVHCONF defines the number of entries of an in-core table you want the product\nto maintain in CSA.\nSet SCHTBSIZE to a reasonable value (for example SCHTBSIZE=30) to stay in your testing threshold. Each entry uses\n27 bytes of CSA storage.\nThe maximum value for SCHTBSIZE is 60. Setting SCHTBSIZE to zero (SCHTBSIZE=0) disables the schedule function.\nWhen the schedule function is disabled, all DB2 SP and IMS/DC transactions run unmonitored.\nThe contents of the table are maintained through the product interface. For more information about maintaining this table,\nsee Batch Link Facility.\nIf you want the product to load a fixed schedule at every IPL, insert the following DD card to the CAS9 initialization job\nstream:\n 166", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0bccc15b5f7c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n //INT1SKUT DD DISP=SHR,DSN=xxxx\n \nxxxx is a fully qualified data set containing schedule entries to be imported. This data set can be a sequential data set or\na partitioned data set. If it is a partitioned data set, provide a member name in parenthesis. Create this data set using the\nEXPORT function. For more information about the EXPORT function, see DB2 and IMS Schedule Menu.\nEnable the SYSPLEX (Cross-LPAR) Debugging Feature\nYou can view and debug jobs that are executing on different (foreign) LPARs than the one you are currently logged on to.\nFor more information about debugging jobs executing on foreign LPARs, see Batch Link Selection Panel.\nFollow these steps:\n1.Ensure that TCP/IP is active and accessible across the SYSPLEX, and that the Broadcom  Testing Tools Server is\nrunning on all LPARs within the SYSPLEX.\n2.Specify the port number that you want to use for InterTest Batch SYSPLEX support. Update BLSPORT=\"XXXXX\" in\nCAVHUOPT member which is located in CAVHOPTN target library data set.\n3.Specify IBSYSPLEX=Y in your CAVHCONF configuration module.\n4.Restart the Broadcom  Testing Tools server if the server is already running.\nCICS Options\nThis article describes how to change the default installation options for InterTest for CICS and SymDump for CICS.\nTo create an IN25OPTS load module, all users must use the following sample JCL. To make changes to IN25OPTS after\nyou install your product, you will also perform the procedure to Refresh IN25OPTS.\nConfigure IN25OPTS Options", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0bccc15b5f7c-1", "text": "Configure IN25OPTS Options\nInterTest for CICS and SymDump  for CICS installation options are contained in the IN25OPTS load module. Create an\nIN25OPTS load module that contains the modified options with a batch assemble-and-linkedit job.\nSample JCL to Assemble the Options Program\nThe following example shows the JCL needed to assemble the InterTest for CICS and SymDump for CICS Options\nProgram (IN25OPTS). Member CABAOPTJ in CAI.CAVHJCL contains sample JCL that can be used to assemble and link\nIN25OPTS. In the following example, the options LETSVC, EXTSEC and CWALET have been generated:\n//IN25OPTS JOB \n//************************************************************\n//*       IN25OPTS SAMPLE JCL                                *\n//************************************************************\n//ASM      EXEC PGM=ASMA90,REGION=1M,\n//             PARM='LIST,XREF(SHORT),DECK,NOOBJ'\n//SYSPRINT DD  SYSOUT=*\n//SYSPUNCH DD  DSN=&&OBJECT,UNIT=SYSDA,DISP=(NEW,PASS),\n//       DCB=BLKSIZE=3200,SPACE=(TRK,(1,1))\n//SYSLIB   DD  DSN=CAI.CAVHMAC,DISP=SHR\n//         DD  DSN=CICS.MACLIB,DISP=SHR\n//SYSUT1   DD  UNIT=SYSDA,SPACE=(CYL,(1,1))\n//SYSUT2   DD  UNIT=SYSDA,SPACE=(CYL,(1,1))\n//SYSUT3   DD  UNIT=SYSDA,SPACE=(CYL,(1,1))\n//SYSIN    DD  *                                       \n 167", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "66dd44458bde-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n*** CWA USER DSECT REQUIRED HERE IF USING THE CWALET OPTION ***\n         USING CWADS,0                 CA INTERTEST REQUIREMENT\nCWADS    DSECT                         USER CWA        \nCWAFLD1  DS    CL20\nCWAFLD2  DS    CL15\nCWAFLD3  DS    CL100\n******** CA INTERTEST AND SYMDUMP OPTION SPECIFICATIONS********\n        IN25OPTS TYPE=CSECT,                                   X\n              LETSVC=NO,                                       X\n              EXTSEC=Y\n        IN25OPTS TYPE=CSECT,                                   X\n              CWALET=(CWAFLD1,CWAFLD2+15)\n        IN25OPTS TYPE=FINAL\n        END\n/*\n//LKED EXEC PGM=IEWL,PARM=(XREF,LIST,MAP),\n// REGION=1M,COND=(4,LT,ASM)\n//SYSPRINT DD SYSOUT=*\n//SYSLMOD DD DSN=USER.LOADLIB(IN25OPTS),DISP=SHR\n//SYSLIN DD DSN=&&OBJECT,DISP=(OLD,DELETE)\n//       DD *\n      ENTRY IN25OPTS\n      NAME IN25OPTS(R)   \n//   \nNOTE\nThe CWALET option requires you to place your user CWA DSECT before the first IN25OPTS specification in the\nassembly. The USING statement for this DSECT is required. The register value for the USING statement can be\nany value from 0 to 15.\nRefresh IN25OPTS Options\nIf you have already installed and configured the product, you can follow this procedure to change the existing IN25OPTS", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "66dd44458bde-1", "text": "options. Create a new copy of the IN25OPTS load module, and then take the following steps to refresh the options.\nFollow these steps:\n1.Terminate InterTest for CICS and SymDump for CICS.\n2.Update the IN25OPTS load module that contains the modified options with a batch assemble-and-linkedit job.\n3.Run the following commands.\nCEMT SET  PROG(IN25*)  NEWCOPY\nCEMT SET  PROG(IN##*)  NEWCOPY\nNOTE\nReplace ## with your two-digit CICS release number (68 for CICS 5.1, 69 for CICS 5.2, 70 for CICS 5.3, 71\nfor CICS 5.4, 72 for CICS 5.5, 73 for CICS 5.6, and 74 for CICS 6.1).\nIgnore any failures of IN##HOOK and IN25INIT to newcopy.\n4.Restart InterTest for CICS and SymDump for CICS.\nIN25OPTS Keywords\nThe following list describes the IN25OPTS keywords.\n 168", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c58c9e0f37ae-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nKeywords apply to either InterTest for CICS, SymDump  for CICS, or to both products.\nIf you change a transaction ID, also change the  CICS transaction definition.\nDefaults are underlined. Slashes (/) between parameters indicate you must make a choice.\nCommon Keywords\nBKPTERM\nBKPTERM=  <no value>   /MOD2\nno value\nThe breakpoint display will not force a MOD2 terminal.\nMOD2\nThe breakpoint display will always be treated as a MOD2 terminal.\nCORET\nCORET= CORE /transaction-id\nSpecify a four-character transaction ID for the InterTest for CICS CORE transaction. Be sure to adjust the CICS\ntransaction definition if you do not use the default.\nNOTE\nThe CICS restriction that no user transaction ID starts with the character C is not strict. You can use IDs such as\nCNTL and CORE if the CICS system does not use them.\nEXTSEC\nEXTSEC=YES/ NO\nIndicates whether External Security Manager is to be used.\nYES\nInterTest for CICS and SymDump  for CICS call the External Security Manager to verify access to secured\nfunctions.\nNO\nInterTest for CICS and SymDump  for CICS bypass the calls to the External Security Manager. When first installing\nInterTest for CICS and SymDump  for CICS, this setting is useful until the product is tested and the security rules\nare written.\nHELPFIL\nHELPFIL= PROTHLF /filename\nSpecify the file name for the InterTest for CICS Help file. The name cannot exceed seven characters. Be sure to adjust the\nCICS file definition if you do not use the default.\nHELPT\nHELPT= HELP /transaction-id", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c58c9e0f37ae-1", "text": "HELPT\nHELPT= HELP /transaction-id\nSpecify a four-character transaction ID for the InterTest for CICS HELP transaction. Be sure to adjust the CICS transaction\ndefinition if you do not use the default.\n 169", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0b3efa4def3d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIGLUT\nIGLUT= IGLU /transaction-id\nSpecify a four-character transaction ID for the InterTest for CICS IGLU transaction. This transaction displays the\nInterTest/SymDump  for CICS global user exit list.\nNOTE\nAdjust the CICS transaction definition if you do not use the default.\nLISTT\nLISTT= LIST /transaction-id\nSpecify a four-character transaction ID for the InterTest for CICS LIST transaction (viewing of the compile or assembly\nlisting). Be sure to adjust the CICS transaction definition if you do not use the default.\nNDVRASML\nNDVRASML= NO/YES\nNon LE assembler programs do not have a standard date/time stamp within the load module to compare against the date/\ntime stamp of the program symbols in the PROTSYM file. Without a date/time stamp the symbols, verification fails and\ncauses symbols for assembler programs to always be loaded by the Endevor  dynamic symbolic load feature if the feature\nis active.\nNO\nIndicates you do not want symbols for non-LE assembler programs to be dynamically loaded on every request.\nYES\nIndicates you want symbols for non-LE assembler programs to be dynamically loaded on every request.\nNDVRPROC\nNDVRPROC= INTNDVR  procedure name\nSpecify the name of the dynamic symbolic support for Endevor  procedure defined in the install procedure. This is the\nseven-character name prefix of the procedure, which starts when dynamic symbolic support is active and a dynamic\nsymbols load is necessary.\nSLBMARG\nSLBMARG=  1 /nn\nSpecifies a decimal number, from 1 to 41, of the default margin value on the LIST facility screens for Assembler programs.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0b3efa4def3d-1", "text": "Regardless of this setting, the Location field of each source listing line is shown. The margin value can be adjusted online\nat any time.\n1\nPresents the left-most portion of each source listing line.\n41\nPresents the right-most portion.\n28\nSuppresses the machine code.\n34\nSuppresses the machine code and statement numbers.\n 170", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c7eb6b92faf0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSLBSCRL\nSLBSCRL= PAGE /HALF/STOP/nnnn\nSpecifies the default scroll value for the LIST facility (online viewing of compile and assembly listings) when the user\npresses the PF7 or PF8 keys. Regardless of this setting, the value can be adjusted online at any time.\nPAGE\nScrolls the display one page.\nHALF\nScrolls the display half a page.\nSTOP\nScrolls the display to the next declared breakpoint.\nnnnn\nScrolls the display the specified number of lines (1 to 9999).\nSLBTIT\nSLBTIT= TITLES  /NO/REGISTERS/KEEP/PROGRAM\nSpecifies the default view at the top of the display (info area) of the LIST facility (online viewing of compile and assembly\nlistings). Regardless of this setting, the value can be adjusted online at any time.\nTITLES\nDisplays the title and header lines, leaving less space for the source listing.\nNO\nDisplays only the entry fields and a command line, leaving more space for the source listing.\nREGISTERS\nDisplays the general registers and the condition code at a breakpoint.\nKEEP\nDisplays your program data items at a breakpoint.\nPROGRAM\nDisplays the load module name and the symbolic file information.\nSYMDINT\nSYMDINT= YES /NO\nFor SymDump  for CICS users viewing a source listing, this option specifies whether the user can invoke InterTest for\nCICS functions for the abended program.\nYES\nSymDump  for CICS users can invoke InterTest for CICS functions when viewing a source listing for an abended\nprogram. For example, users can set monitoring, invoke the FILE facility, and perform other InterTest for CICS\nfunctions directly from SymDump  for CICS.\nNO", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c7eb6b92faf0-1", "text": "functions directly from SymDump  for CICS.\nNO\nSymDump  for CICS users cannot invoke InterTest for CICS functions when viewing a source listing for an\nabended program. To invoke InterTest for CICS functions, users must access InterTest for CICS directly.\nSYMFIL\nSYMFIL= PROTSYM  /file/(file1,file2,....)\n 171", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9876cb6fd1f9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSpecify the CICS file definition names for the InterTest for CICS symbolic files. The names cannot exceed seven\ncharacters. If more than one name is specified, the names must be separated by commas and the entire list enclosed in\nparentheses. Be sure to adjust the CICS file definition if you do not use the default.\nThis option tells InterTest for CICS the CICS file definitions of the InterTest for CICS symbolic files and their search order\nfor program data. When monitoring is turned on for a program, InterTest for CICS searches the symbolic files in the\nsequence specified and for COBOL and PL/I programs finds the symbolic file member that matches the corresponding\nload module compile date/time. If a matching date/time cannot be found or a symbolic file member has a more recent\ndate than the date in the load module, a symbolic file mismatch screen will appear and the customer must choose which\nsymbolic file member to use for debugging. For Assembler programs, the symbolic file mismatch screen will always\nappear if a program is found on more than one symbolic file.\nOnce a matching date/time member is found or a member is selected from a mismatch screen, InterTest for CICS\nwill continue to use the selected symbolic file member until all breakpoints and monitoring has been turned off for the\nprogram.\nThere is no upper limit to the number of symbolic files that you can specify. However, limit the number of files to reduce\nthe overhead and the storage required for the VSAM buffers because each CICS file definition must be defined with\nLSRPOOL=NONE.\nUCONLY\nUCONLY=NO/YES\nDetermines whether certain terminal output will be dynamically translated from lowercase to uppercase.\nNO\nTerminal output is not dynamically translated.\nYES\nTerminal output is dynamically translated to uppercase characters. If you previously installed the uppercase", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9876cb6fd1f9-1", "text": "YES\nTerminal output is dynamically translated to uppercase characters. If you previously installed the uppercase\nversion of the InterTest for CICS load libraries because your terminals did not support the mixed case English\ncharacter set, you should specify YES.\nUSERHELP\nUSERHELP= PROTUHF  / filename\nSpecify the file name for the optional help file of user-defined abend descriptions. The name cannot exceed seven\ncharacters. Be sure to adjust the CICS file definition if you do not use the default.\nVRPTT\nVRPTT= VRPT  /transaction-id\nSpecify a four-character transaction ID for the InterTest for CICS VRPT transaction used to verify the installation and\ndisplay the installation options. Be sure to adjust the CICS transaction definition if you do not use the default.\nXRMIO\nXRMIO=NO/ YES\nFor InterTest for CICS users, determines whether or not to use the CICS XRMIOUT Global User Exit to keep track of the\nlast SQL call issued by an application program.\nNO\nAllows capture of SQL information provided that an EXEC CICS command has not occurred between the SQL call\nand the abend.\n 172", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5ccdbb59e33c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nYES\nProvides the last SQL call to the applications programmer for the CORE=SQLCA and CORE=LASTSQL\ncommands, but there is an overhead associated with the use of the XRIMIOUT exit that not all shops will want to\nincur.\nInterTest for CICS Keywords\nAUDIT\nAUDIT= NO/YES\nFor auditing purposes, certain installations require that all CORE, FILE, and CNTL commands be recorded.\nNO\nSpecify NO if you did not specify the GLOG= option or if you want to dynamically activate and deactivate global\nlogging with CNTL=GLOG,ON and CNTL=GLOG,OFF commands.\nIf you specify NO, the user can request logging of FILE commands by specifying FUNC=LOG on the FILE menu.\nYES\nSpecify YES if you specified the GLOG= option and you need the global logging facility always active.\nWith AUDIT=YES, neither the CNTL=GLOG,ON command nor the CNTL=GLOG,OFF command are accepted.\nThe CNTL commands and InterTest for CICS responses are always recorded in the transient data queue or data\nset that was specified with the GLOG= keyword. CORE changes to storage areas not owned by the task (usually\npassword protected) are always recorded. The FILE transaction operates in the LOG=ON mode; that is, all user\nrequests and resulting FILE screen images are recorded.\nNOTE\nIf you do not specify the GLOG= keyword, the AUDIT=YES specification is ignored.\nAUTMON\nAUTMON= YES/NO\nIndicates whether a new Monitor Table entry is created.\nYES\nCreates a new Monitor Table entry for a program when an automatic breakpoint is about to occur if the program is\nbeing monitored under a Monitor Table entry that does not name this program by its full name (for example, if the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5ccdbb59e33c-1", "text": "entry names a transaction). The new entry assumes all monitoring options currently in effect. This option makes it\neasier to debug the program.\nNO\nDoes not create a separate Monitor Table entry.\nBREAK\nBREAK= YES/NO\nIndicates whether InterTest for CICS is allowed to execute breakpoints.\nYES\nAllows InterTest for CICS to execute breakpoints; that is, to stop execution of the application program at certain\npoints. Select this option if you intend to use InterTest for CICS as an interactive debugging tool.\nNO\nDoes not allow InterTest for CICS to execute breakpoints. This option might be desirable in a separate version\nof InterTest for CICS used solely for monitoring production applications. InterTest for CICS generated with\nBREAK=NO monitors with less overhead, which is important in production.\n 173", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e7521e594477-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInstead of causing automatic breakpoints, InterTest for CICS abnormally terminates transactions with a\ntransaction dump when it detects a standards violation. The abend/dump code is INTE. The dump contains all of\nthe usual diagnostic information.\nCICSPLEX\nCICSPLEX=YES/ NO\nInterTest for CICS provides special support for CICS regions participating in a CICSplex environment. Participating\nCICSplex regions have InterTest for CICS commands propagated across all regions in the CICSplex.\nYES\nIndicates that this CICS region is participating in at least one CICSplex family of regions, as named in the\nCPLXFMID keyword. Invokes InterTest for CICS CICSplex processing by using CAICCI.\nIf CICSPLEX=YES, CAICCI processing must be installed on the z/OS operating system and available to CICS.\nNO\nIndicates that this CICS region is not participating in a CICSplex family.\nCKPTFIL\nCKPTFIL= PROTCPF / filename\nSpecify the file name for the InterTest for CICS checkpoint file. The name must not exceed seven characters. If you do not\nuse the default, be sure to adjust the CICS file definition.\nCNTLSEC\nCNTLSEC= YES/NO\nIndicates whether certain CNTL commands can be protected with a password.\nYES\nProtects certain CNTL commands with a password and allows for password protection of certain CNTL options.\nSpecify CNTLSEC=YES if the CNTL command functions should be available only to authorized personnel. With\nCNTLSEC=YES, the keyword CNTOSEC further specifies whether the subset of CNTL options should also be\npassword protected.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e7521e594477-1", "text": "password protected.\nThe passwords are defined in the IN25SEC2 macros. See InterTest for CICS User Exits for the list of CNTL\ncommands and options subject to password protection and details on specifying passwords using IN25SEC2.\nWith CNTLSEC=YES, you must use the IN25SEC2 macro to generate the InterTest for CICS program IN25SEC2\nor use the IN25SEC2 delivered with InterTest for CICS.\nNO\nDoes not protect certain CNTL commands with passwords and does not allow for password protection of certain\nCNTL options.\nCNTLT\nCNTLT= CNTL /transaction-id\nSpecify a four-character transaction ID for the InterTest for CICS CNTL transaction. Be sure to adjust the CICS transaction\ndefinition if you do not use the default.\nNOTE\nThe CICS restriction that no user transaction ID begins with the character C is not strict. IDs such as CNTL and\nCORE can be used if the CICS system does not use them.\n 174", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "761450d9f0d9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCNTOSEC\nCNTOSEC=YES/NO\nWhen the value for the keyword CNTLSEC is YES, specify this keyword to include or exclude certain CNTL options from\npassword protection. When CNTLSEC=NO, this keyword is ignored.\nYES\nProtects certain CNTL options with a password. The password is defined in an IN25SEC2 macro, as discussed in\nPassword Protection.\nNO\nDoes not protect any CNTL options with passwords.\nCNTSQLG\nCNTSQLG= YES/NO\nIndicates whether CNTL commands are logged.\nYES\nLogs CNTL commands executed from a sequential terminal and responses to them into the transient data\ndestination defined in the GLOG option.\nNO\nDoes not log CNTL commands.\nCORSEC\nCORSEC= YES/NO\nIndicates whether a password is required to modify a main storage area protected by InterTest for CICS.\nYES\nRequires a password when a user of the CORE facility is about to modify a main storage area that is protected by\nInterTest for CICS, but does not require the password during normal debugging. Specify CORSEC=YES if you will\nuse the InterTest IN25SEC2 macro to generate a password that would prevent the CORE facility from being used\nby unauthorized personnel.\nThe IN25SEC2 macro must be used to generate the InterTest for CICS program IN25SEC2 or use the IN25SEC2\ndelivered with InterTest for CICS. The use of the IN25SEC2 macro is described in Password Protection.\nWithout the password, the CORE transaction lets you modify only those storage areas that belong to a task that is\nwaiting in a breakpoint and are not protected by InterTest for CICS from being modified by the monitored program.\nNO", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "761450d9f0d9-1", "text": "NO\nDoes not require a password before allowing modification of any field within the CICS region in main storage.\nSee the description of the CORE transaction in CICS Debugging. The CORSEC specification also applies to data\nmodification in the LIST Keep window.\nNOTE\nRegardless of the CORSEC= specification, the following main storage areas are not available for\nmodification by the CORE transaction:\n\u2022CICS/VS Sign-on Table (DFHSNT)\n\u2022Main storage outside of the CICS region\nCPF11\nCPF11=7B/BF\nActivates the PF11 key on the Detailed Breakpoint screen.\n 175", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "52b4521e961e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n7B\nAllows application programmers to use the PF11 key on the Detailed Breakpoint screen to tell InterTest for CICS\nto force the execution of any error condition that InterTest for CICS has detected even though the error condition\nthat caused the automatic breakpoint still exists. In effect, the user tells InterTest for CICS that this is really not a\nviolation and to execute regardless of the consequences.\nBefore enabling this facility, be aware of the following considerations:\n\u2022As a result of this execution, not only the tested transaction's data could be damaged but other concurrent\ntransactions could also be affected and the entire CICS system may crash.\n\u2022Using PF11 ignores not only the immediate error condition, but also all subsequent error conditions until the\nnext breakpoint or CICS Service Request (whichever comes first).\nBF\nSpecify CPF11=BF if you do not want to provide this facility.\nCPLXCKPI\nCPLXCKPI= 0020 /hhmm\nIf CICSPLEX=YES and the checkpoint facility is started by a CICSPLEX resynchronization request, defines the time\ninterval in hours (HH) and minutes (MM) between checkpoints.\nCPLXFMID\nCPLXFMID= INTERTST /CICSplex-familyname\nDefines an eight-character CICSplex family name associated with the CICS region. The same family name must be\ngiven to all CICS regions participating in that family to obtain CICSplex support throughout the family. InterTest for CICS\nsupports multiple CICSplex families within or across multiple z/OS regions.\nFor example, all regions associated with CPLXFMID=REGIONA participate in one CICSplex family, while all regions\nassociated with CPLXFMID=REGIONB participate in another.\nCWALET", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "52b4521e961e-1", "text": "associated with CPLXFMID=REGIONB participate in another.\nCWALET\nCWALET= <no value>  /(label,label)\nSpecify the CWALET keyword only if you want to remove InterTest for CICS storage protection from certain CWA fields.\nWARNING\nIf you choose to specify one or more CWALET areas, you must code a separate  IN25OPTS TYPE=CSECT\nmacro for each CWALET area (one area per macro).\nIN25OPTS macros with CWALET must follow other IN25OPTS macros except for the TYPE=FINAL macro, which must be\nthe last one.\nno value\nInterTest for CICS protection will not be removed. Use the CSA= and LET= online options to let specific monitored\nprograms modify additional areas of main storage. See CICS Debugging for details about online options.\n(label,label)\nSpecify two Assembler labels, separated by a comma and enclosed in parentheses; for example,\nCWALET=(CSAUTA1,CSAUTA4). The first label defines the first byte of the area to be unprotected; the second\nlabel defines the first byte past the area.\nWhen using labels, they must be defined in the DSECT for the CWA and inserted in the IN25OPTS compile; see\nthe section Sample JCL to Assemble the Options Program for details.\nIf your CWA has an existing DSECT, use existing labels and offsets from the labels to define the unprotected\narea.\n 176", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "60b676586b91-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIf you do not have an existing DSECT in your CWA, add the following two statements to the IN25OPTS module to\ncreate one:\n*********** CWA USER DSECT REQUIRED HERE ************\nUSING CWADS,0   CA INTERTEST REQUIREMENT\nCWADS           DSECT                   USER CWA\n******** CA INTERTEST SPECIFICATIONS ******\nYou can then specify offsets from the beginning of the CWA. For example, the following macro unprotects a 20-\nbyte area starting at the beginning of the CWA:\nIN25OPTS TYPE=CSECT,CWALET=(CWADS,CWADS+20)\nDFLTUSER\nDFLTUSER=.ANY /SPECIFIC/BACKGROUND\nDFLTUSER stands for default user and controls how InterTest for CICS monitoring functions by default. A user can\noverride the default settings established by this parameter at any time.\n.ANY\nWhen this setting is used, InterTest for CICS monitoring pays no attention to the CICS user ID of the session,\neven if the user is signed on to CICS. Monitoring is set for all users, and breakpoints, by default, are directed to\nthe same terminal used to set them.\nSPECIFIC\nThis setting is only valid in a secure InterTest for CICS region where the users log on to CICS. When\nDFLTUSER=SPECIFIC is used, InterTest for CICS qualifies each monitoring entry with the user's CICS user ID.\nIn addition, InterTest for CICS directs all options to monitoring to .ANY terminal. This setting allows many users to\ntest the same program or transaction independently. This also allows users to move from terminal to terminal and\nhave their monitoring entries and monitoring options follow them.\nBACKGROUND", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "60b676586b91-1", "text": "have their monitoring entries and monitoring options follow them.\nBACKGROUND\nThis setting is only valid in a secure InterTest for CICS region where the users log on to CICS. Code this if your\nCICS system is used predominantly as an Application Server, where most transactions are not attached to\nterminals (that is, web interface transactions). This setting sets the FROM terminal to .ANY, and the breakpoint\n(TO) terminal to the current terminal that is setting the breakpoints.\nWARNING\nWhen DFLTUSER=SPECIFIC is used and a user does not sign on to the CICS region, InterTest for\nCICS uses the value of the CICS DFLTUSER for the monitoring entry. The CICS default user ID is\noptionally specified in the SIT parameters. If not specified in the SIT, its value is CICSUSER.\nDL1SIZE\nDL1SIZE= 8192 /nnnnn\nSpecifies the number of bytes in the largest DL/I segment to be retrieved using the InterTest for CICS FILE facility.\nStorage corruption may occur if the size specified here is smaller than a DL/I segment that is retrieved using FILE.\nFDISP\nFDISP= FC/DL/TD/TS/DB\nDetermines the default menu for the FILE transaction. The various menu types are described in CICS Debugging. The\nuser can change the menu of the FILE facility online at any time.\nFC\nThe FILE transaction shows its first display in the DATATYPE=FC format; that is, ready to process CICS files\ndefined in the CICS file definition (File Control Table).\n 177", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "12e1f498abdb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDL\nThe FILE transaction shows its first display in the DATATYPE=DL format; that is, ready to process DL/I segments.\nTD\nThe FILE transaction shows its first display in the DATATYPE=TD format; that is, ready to process CICS transient\ndata queues.\nTS\nThe FILE transaction shows its first display in the DATATYPE=TS format; that is, ready to process CICS\ntemporary storage.\nDB\nThe FILE transaction shows its first display in the DATATYPE=DB format; that is, ready to process DB2 data.\nFFORM\nFFORM= D/C/V/S\nDetermines the default format in which the FILE transaction displays the data. The user can change the format of the FILE\ndisplay online at any time. For illustrations of FILE displays, see CICS Debugging.\nD\nThe FILE transaction shows its first display in dump format, similar to the nonstructured display of the CORE\ntransaction. Shows both character and hexadecimal images.\nC\nThe FILE transaction shows its first display in character format. This format displays the largest amount of data,\nbut is useless for noncharacter data records.\nV\nThe FILE transaction shows its first display in vertical format, similar to the DITTO utility. This format displays the\nleast amount of data.\nS\nThe FILE transaction shows its first display in structured format if symbolic information for the program containing\nthe structures is stored in the InterTest for CICS symbolic file. COBOL and PL/I structures use 01 level names;\nAssembler structures use DSECT names. Shows both character and hexadecimal images. See the FSYMP\noption.\nFILET\nFILET= FILE  /transaction-id\nSpecify a four-character transaction ID for the InterTest for CICS FILE transaction. Be sure to adjust the CICS transaction\ndefinition  if you do not use the default.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "12e1f498abdb-1", "text": "definition  if you do not use the default.\nFILSEC\nFILSEC= YES/NO\nIndicates whether the InterTest IN25SEC2 macro generates passwords for security purposes.\nYES\nThe InterTest IN25SEC2 macro generates passwords to prevent the FILE transaction from being used by\nunauthorized personnel. More comprehensive security enforcement has to be implemented on the CICS level or\non the operating system level.\nWith FILSEC=YES the IN25SEC2 macro must be used to generate the InterTest for CICS IN25SEC2 program,\nor use the IN25SEC2 delivered with InterTest for CICS. Failure to do so will make the FILE transaction useless.\nUsing the IN25SEC2 macro is described in Password Protection.\n 178", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5ecfa7b2b26c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNO\nPermits users of the FILE transaction to access any CICS file or DL/I data without an InterTest for CICS-enforced\npassword.\nFSYMP\nFSYMP= PROTFILE /symbolic-programname\nSpecify the name of the default dummy COBOL or PL/I program that contains all of the 01 level structures used at the\nsite or the Assembler program that contains all the DSECTs. Symbolic information for this program must be stored in the\nInterTest for CICS symbolic file.\nUsers of the FILE transaction requesting records or DL/I segments in structured format must specify the symbolic name of\nthe program that contains the structure. However, if a default program containing all of the structures has been compiled\nor assembled, users can omit the symbolic program name.\nFor a sample default COBOL program, see Add COBOL File Structures to the Symbolic File. For more information on\nadding Assembler file structures, see Add Assembler DSECTs to the Symbolic File.\nGLOG\nGLOG= CSSL /DCT-destination-id\nSpecify a four-character name of a transient data destination in the CICS Destination Control Table (DCT). The default,\nGLOG=CSSL, provides the statistics destination that is always present in the CICS system and is usually printed when\nthe CICS system is terminated\nThe destination must specify a direct or indirect extra partition transient data set that has a record size of at least 110\nbytes (variable-length format, including the length field).\nInterTest for CICS writes records to the specified transient data queue (destination) after the command CNTL=GLOG,ON\nis entered. See the description of the AUDIT keyword; also see the description of the InterTest for CICS global logging\nfacility in CICS Debugging.\nICMDBUF", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5ecfa7b2b26c-1", "text": "facility in CICS Debugging.\nICMDBUF\nICMDBUF= 1024 /nnnnn\nSpecifies the indirect command buffer size, which is the number of bytes used by InterTest for CICS when acquiring and\nallocating Indirect Command Input Work Buffers. These buffers are used by the Indirect Command Processing Program,\nwhich displays and executes indirect commands specified by the user for specific programs. The minimum buffer size is\n80. The maximum buffer size is 32767.\nICMDEXE\nICMDEXE= 50/nnnnn\nSpecifies the maximum indirect command execution count. When the maximum number of indirect commands executed\nexceeds the ICMDEXE count, message CAIN1266 is generated. The minimum count allowed is 1. The maximum count\nallowed is 1024.\nICMDMAX\nICMDMAX= 50/nnnnn\nSpecifies the maximum indirect command statements count. When the number of indirect command statements exceeds\nthe ICMDMAX count, message CAIN1259 is generated. The minimum count allowed is 1. The maximum count allowed is\n1024.\n 179", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ce2fd799b35d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIPINIT\nIPINIT= YES/NO\nIndicates whether support should be initialized for the common user interface.\nYES\nIndicates that the common user interface mainframe initialization should occur.\nNO\nIndicates that the common user interface will not be used and the CUI initialization should not be performed.\nIPLXT\nIPLXT= IPLX /transaction-id\nSpecifies a four-character transaction ID for the CICSplex CCI (Common Communications Interface) to be used for\nCICSplex support by InterTest for CICS.\nNOTE\nAdjust the CICS transaction definition if you do not use the default.\nIRCTT\nIRCTT= VIRC /transaction-id\nSpecify a four-character transaction ID for the InterTest for CICS VIRC transaction. This is an internal InterTest for CICS\ntransaction used only for handling breakpoints. Its use must not be protected by a specific signon. If started by mistake\nfrom a terminal, the transaction program does nothing.\nIn an MRO or ISC environment, the VIRC transaction must be installed as local in all Terminal Owning Regions and\nApplication Owning Regions that use InterTest for CICS.\nIn a CICS environment that does not use MRO or ISC, the VIRC transaction must be installed to support automatic single-\nstepping.\nNOTE\nIf you change the transaction ID, also change the CICS transaction definition.\nISERT\nISERT= ISER /transaction-id\nSpecify a four-character transaction ID for the internal InterTest for CICS ISER transaction. Do not assign protection to a\nspecific user.\nNOTE\nIf you change the transaction ID, also change the CICS transaction definition.\nITSTT\nITSTT= ITST /transaction-id", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ce2fd799b35d-1", "text": "ITSTT\nITSTT= ITST /transaction-id\nSpecify a four-character transaction ID for the InterTest for CICS ITST transaction. This transaction displays the InterTest\nfor CICS Primary Option menu from a CICS prompt. Do not assign protection to a specific user.\nNOTE\nIf you change the transaction ID, also change the CICS transaction definition.\n 180", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6ccc0c65fe6f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nLETSVC\nLETSVC= YES/NO\nIndicates whether SVCs are permitted.\nYES\nPermits any SVCs in application programs except:\nSVC 13  (hex 0D) -- ABEND macro\nNO\nIndicates that application programs do not use any SVCs except:\nSVC 11  (hex 0B) -- TIME macro\nThese are the SVCs often used implicitly in applications, but any other SVCs should not be used in CICS\nprogramming.\nRegardless of this keyword, you can use BYP= options during an InterTest for CICS test session to permit the\nmonitored program to use SVCs.\nMONOM\nMONOM= NO/MENU/NOMENU\nControls the activation of the segmented monitoring feature.\nNO\nDeactivates the segmented monitoring feature and removes any previous MON and NOM entries from the CNTL\nmain menu.\nMENU\nActivates the feature and displays the MON and NOM options on the CNTL main menu.\nNOMENU\nActivates the segmented monitoring feature, but limits users to implementing segmented monitoring through\nCNTL commands or the LIST facility. NOMENU disables the use of the MON and NOM options on the Monitoring\nmenus, and removes the MON and NOM entries from the CNTL main menu.\nMONOMSEC\nMONOMSEC= YES/NO\nControls password protection for the segmented monitoring options in the CNTL facility. If MONOM=NO, MONOMSEC is\nignored.\nYES\nImplements password protection of the segmented monitoring feature. The password is controlled by a keyword in\nthe IN25SEC2 macro. Instructions for specifying passwords for CNTL options are in Password Protection.\nNO\nPermits the use of the segmented monitoring feature without password protection.\nOSGETM\nOSGETM=  YES /NO", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6ccc0c65fe6f-1", "text": "OSGETM\nOSGETM=  YES /NO\nIndicates whether a GETMAIN SVC is allowed to be issued.\nYES\nPermits COBOL programs monitored by InterTest to issue the GETMAIN SVC. As suggested by the CICS\nApplication Programmer's Reference Manual , any CICS COBOL program should be coded so that no COBOL\nfacilities require a GETMAIN SVC. Such a GETMAIN SVC obtains storage from the OSCORE storage pool\n 181", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f37433357dbc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\noutside the storage controlled by the CICS Storage Management. There is no FREEMAIN if the COBOL program\nterminates. When, eventually, a GETMAIN cannot be satisfied, the CICS system will be abended by the operating\nsystem.\nOSGETM=YES is implied by the LETSVC=YES specification.\nNO\nDoes not permit the GETMAIN SVC to be issued by COBOL programs. Unless you run software that issues the\nGETMAIN SVC, we recommend that you specify OSGETM=NO as GETMAINs should not be permitted. With this\nspecification, an automatic breakpoint will occur when the GETMAIN SVC is detected. However, OSGETM=NO is\noverridden by LETSVC=YES.\nPROMD\nPROMD= 00000020  /name/number\nThe name or the number in this keyword is used for the default value of the PROM= parameter of the CNTL=START\ncommand.\nname\nSpecify the InterTest IN25SEC2 macro generates passwords the name (up to eight characters) of the InterTest\nfor CICS Startup Table that has to be generated with the PROMMAC macro. The use of the macro is described in\nActivate Your Product.\nnumber\nSpecify the number to be used as the default value of the PROM= parameter of the CNTL=START command,\nwhich specifies the initial number of entries in the Monitoring Table. This number must be eight characters long.\nFor the initial period of use, the default value should suffice.\nThe number of entries in the table should be no less than the number of names to be declared for monitoring.\nHowever, for efficiency, allow enough entries at the beginning by specifying the PROM= parameter here or in\nthe CNTL=START command. A large number of unoccupied entries use more storage but do not increase the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f37433357dbc-1", "text": "overhead because only occupied table entries are examined when the table is scanned.\nREADBUF\nREADBUF= YES/  NO\nIndicates whether the read buffer function is supported.\nYES\nBefore sending a breakpoint to a terminal, InterTest for CICS issues a read buffer to save the last user screen\nfrom that terminal. If your InterTest for CICS demonstration session runs successfully, specify YES.\nNO\nYou must specify NO if all terminals that would be used by InterTest for CICS users run under TCAM or do not\nsupport the read buffer function. If you do not specify NO, you must declare the NRB=ON online option whenever\nmonitoring is declared.\nRECNTMU\nRECNTMU=YES/ NO\nIndicates whether CNTL menu generated commands are displayed before execution.\nYES\nDisplays the CNTL commands generated by the InterTest for CICS menus just before the commands are\nexecuted. The user can learn these commands from the screen and, for efficiency, use them instead of menus.\nNO\nSuppresses display of CNTL commands.\n 182", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ea43b5b5ec8b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nRECNTNW\nRECNTNW=  YES /NO\nIndicates whether CNTL RESTART or NEWCOPY commands are displayed before execution.\nYES\nDisplays the CNTL commands that are automatically generated by CNTL=RESTART or CNTL=NEW,PROG=\ncommands. These appear just before they are executed so that the user can see what is being done.\nNO\nSuppresses display of CNTL commands. Specify NO if users are not interested in these details.\nSDISPLAY\nSDISPLAY=HEX/ DATA\nFacility of the Structure display and AutoKeep display feature. Specifies the global default value for Structure Display\nFormat. Regardless of this setting, the value can be adjusted online by program name.\nHEX\nDisplay data in hexadecimal character format\nDATA\nDisplay data in Structure Display Format\nSLB\nSLB= YES /NO\nIndicates whether Source Listing Breakpoint displays are available.\nYES\nUses Source Listing Breakpoint displays for the terminal from which the program was declared for monitoring if\nthe compile (assembly) listing is available in the InterTest for CICS symbolic file.\nNO\nUses Detailed Breakpoint displays when a program is declared for monitoring.\nIn either case, Source Listing Breakpoint displays can be turned on or off during the online test session.\nNOTE\nThe InterTest for CICS LIST facility (the online viewing of compile and assembly listings before program\nexecution) is not affected by this setting.\nSLBAKEEP\nSLBAKEEP= YES /NO\nSpecifies the default value for the LIST facility of the AutoKeep display feature. Regardless of this setting, the value can\nbe adjusted online at any time.\nYES\nDisplays items in the Keep window concerning the currently highlighted line and any data items you have\nrequested to be displayed in the Keep Window.\nNO", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ea43b5b5ec8b-1", "text": "requested to be displayed in the Keep Window.\nNO\nDisplays only the data items you have requested to be displayed in the Keep Window.\nSTMTTRCE\nSTMTTRCE= 500 /nnnnn\n 183", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "77952b9aa019-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSpecify the number of entries in the statement trace table. This table will be allocated to any transaction which executes\none or more COBOL programs for which the TRACE option is active. The maximum value is 32767.\nSTUAR\nSTUAR=  NO /YES\nAffects breakpoint processing in regard to the TCTTE user area (an area embedded in the TCTTE, whose address is in\nthe field labeled TCTTECIA).\nNO\nThe contents of the area are not saved for the duration of the breakpoint or restored when the task continues\nexecution from the breakpoint. There is no need to preserve the data in the area if the breakpoint display is to be\nsent to another terminal, or if the area is to be modified (during the breakpoint) only by the person performing the\ntest. Because command level (EXEC CICS) applications rarely use this area, STUAR=NO should be appropriate.\nAlso specify STUAR=NO if the area may be affected during the breakpoint by a facility other than the tested\napplication.\nYES\nThe contents of the area are preserved for the duration of the breakpoint. Specify STUAR=YES if the logic of the\ntested application depends on saving this area while your task waits at a breakpoint, and then restoring it to its\nprevious value, possibly with your modifications.\nSTUAR=YES is desirable if the area can be used during the breakpoint and use of the area must not affect the\ntested program.\nSYMBOLIC\nSYMBOLIC= PROTSYM /PSYMDFLT/COMPAT/ASK/DWARFASK/DWRFDFLT/DWARF\nDetermines which symbolic format, PROTSYM, DWARF or both, should be used with InterTest for CICS.\nPROTSYM\nIndicates that only PROTSYM symbolic files are used.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "77952b9aa019-1", "text": "PROTSYM\nIndicates that only PROTSYM symbolic files are used.\nPSYMDFLT\nIndicates that priority is given to a PROTSYM file. If there is no PROTSYM file, the DWARF data is used. In other\ncases, the Source Listing Display panel with available symbolic data displays.\nCOMPAT\nIndicates that a matching PROTSYM file is used if one is available. If no PROTSYM file is available, the Source\nListing Display panel with available symbolic data displays.\nASK\nIndicates that the Source Listing Display panel with available symbolic data always displays.\nDWARFASK\nIndicates that if DWARF data is available, the Source Listing Display panel with available symbolic data\ndisplays. If there is no DWARF data, a matching PROTSYM file is used. In other cases, the Source Listing Display\npanel with available symbolic data displays.\nDWRFDFLT\nIndicates that priority is given to DWARF symbolic data. If there is no DWARF data, a matching PROTSYM file is\nused. In other cases, the Source Listing Display panel with available symbolic data displays.\nDWARF\nIndicates that only DWARF symbolic data is used.\nResulting action if DWARF data is available\n 184", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "39590124673c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBehavior of SYMBOLIC options when DWARF symbolic is available and PROTSYM symbolic either match, does not\nmatch, or is not present:\nPROTSYM file available? Matching Not matching None\nPROTSYM p a n\nPSYMDFLT p a d\nCOMPAT p a a\nASK a a a\nDWARFASK a a a\nDWARFDFLT d d d\nDWARF d d d\nResulting action if DWARF data is not available\nBehavior of SYMBOLIC options when DWARF symbolic is not available and PROTSYM symbolic either match, does not\nmatch, or is not present:\nPROTSYM file available? Matching Not matching None\nPROTSYM p a n\nPSYMDFLT p a n\nCOMPAT p a n\nASK a a n\nDWARFASK p a n\nDWARFDFLT p a n\nDWARF n n n\nKey:\n\u2022p = PROTSYM file is used\n\u2022d = DWARF data is used\n\u2022a = the Source Listing Display with a list of available symbolic data displays\n\u2022n = nothing\nVERCOR\nVERCOR=  NO /YES\nDetermines whether changes to main storage must be verified.\nNO\nChanges to main storage requested in a CORE transaction command can, but need not be, verified in the same\ncommand.\nIf CORSEC=YES is specified, the user cannot modify any foreign piece of storage by mistake because the CORE\ntransaction will ask for the password. As a result, you can specify VERCOR=NO because a careless user can\nharm only the tested program's data.\nYES\nAny change to main storage requested in a CORE transaction command must be verified in the same command\nregardless of password protection (see the CORSEC= keyword). This compulsory verification could make a", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "39590124673c-1", "text": "regardless of password protection (see the CORSEC= keyword). This compulsory verification could make a\ndebugging session unnecessarily tedious, thus decreasing productivity. The system programmer will find this\n 185", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b269cf0719b7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nspecification a hindrance, especially in situations when a certain value must be forced upon an area whose\ncontent continually changes.\nFor more information, see Accessing Main Storage CORE.\nVTATT\nVTATT= VTAT /transaction-id\nSpecify a four-character transaction ID for the InterTest for CICS VTAT transaction. This is an internal InterTest for CICS\ntransaction used only for handling breakpoints. Since it is not used by any operator, its use must not be protected by a\nspecific user. If started by mistake from a terminal, the program does nothing. Be sure to adjust the CICS transaction\ndefinition if you do not use the default.\nUSSPATH\nUSSPATH=path-name\nSpecify a USS directory where all the information from a non-interactive debugging session is stored. The data that is\nstored comprises trace data, code coverage and a report.\nFor more information about non-interactive debugging monitoring, see the TFL Set Non-Interactive Monitoring  section of\nCNTL Commands and Menus .\nSymDump  for CICS Keywords\nSYMDFIL\nSYMDFIL= PROTDMP  /filename\nFor SymDump  for CICS users, specify the file name for the SymDump  for CICS (the Symbolic Dump option) file. This is\nthe name of the file from which dumps can be  viewed; SymDump  for CICS always writes to the file PROTDMP. The name\ncannot exceed seven characters. Be sure to adjust the CICS file definition if you do not use the default.\nSYMDL\nSYMDL= SYMD  /transaction-id\nFor SymDump  for CICS users, specify a four-character transaction ID for the SymDump  for CICS transaction for the\ncapture for the last SQL statement in background during dump capture. Be sure to adjust the CICS transaction definition if", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b269cf0719b7-1", "text": "you do not use the default. If no value is specified for this option, then no transaction will be scheduled.\nSYMDSVCD\nSYMDSVCD= YES/NO\nWhen unexpected events occur, such as task purging or catastrophic application failures, SymDump  for CICS may have\nto abbreviate its dump capture. When this occurs, SymDump  for CICS may produce an SVC diagnostic dump that could\nassist in researching whatever issues have transpired.\n\u2022Yes\n(Default)\nSymDump  for CICS may produce an SVC diagnostic dump if dump capture processing encounters unexpected\nconditions.\nNo\nSymDump  for CICS will not produce an SVC diagnostic dump.\n 186", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0f3f7d833fcd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSYMDT\nSYMDT= SYMD  /transaction-id\nFor SymDump  for CICS users, specify a four-character transaction ID for the SymDump  for CICS transaction that allows\ndumps to be viewed online. Be sure to adjust the CICS transaction definition  if you do not use the default.\nSYMDWILD\nSYMDWILD=\nSpecify a wild card prefix for the Dump File ID that is specified on the DUMP/TRACE ANALYSIS screen. This limits what\ncan be specified as a wildcard. For example, coding SYMDWILD=PROT lets you specify file names with a wildcard prefix\nof PROT in the Dump File ID input field of the SymDump  Analysis screen. In this case, PROT* would be valid input but\nPRO* would be in error.\nTRCFDCLS\nTRCFDCLS=\nFor SymDump  for CICS users, specify an allocation DATA CLASS that the TRACE FORMAT REGION will use to allocate\nstorage for trace formatting. This parameter is used only by the TRACE FORMAT REGION and is ignored by a CICS\nregion.\nTRCFFMID\nTRCFFMID= SYMDTRCF  /8 character unique id\nFor SymDump  for CICS users, specify the unique TRACE FAMILY ID that a CICS region will use to locate and form an\naffinity with a TRACE FORMAT REGION that has an IN25OPTS with the same TRCFFMID. This parameter is used by\nboth the CICS region and the TRACE FORMAT REGION.\nTRCFMCLS\nTRCFMCLS=\nFor SymDump  for CICS users, specify an allocation MANAGEMENT CLASS that the TRACE FORMAT REGION will use\nto allocate storage for trace formatting. This parameter is used only by the TRACE FORMAT REGION and is ignored by a\nCICS region.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0f3f7d833fcd-1", "text": "CICS region.\nTRCFMEGM\nTRCFMEGM= 120 / total number of megs\nFor SymDump  for CICS users, specify the maximum size of extended private area storage in megabytes that the\nTRACE FORMAT REGION will allocate for use by all threads. This amount of extended private must be available to the\nTRACE FORMAT REGION when it starts, or the job will terminate. If this number is exceeded when a trace is selected\nfor formatting, the user is invited to try again later, this allows performance tuning of the formatted trace facility. This\nparameter is used only by the TRACE FORMAT REGION and is ignored by a CICS region.\nTRCFMEGT\nTRCFMEGT= 15 /megs per thread\nFor SymDump  for CICS users, specify the maximum size of extended private area storage in megabytes that the TRACE\nFORMAT REGION will allocate for use by one thread. If this is not available when a trace is selected for formatting, the\nuser is invited to try again later. This will allow performance tuning of the formatted trace facility. This parameter is used\nonly by the TRACE FORMAT REGION and is ignored by a CICS region.\n 187", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "73993408a26d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFor more information, see Performance Considerations.\nTRCFSCLS\nTRCFSCLS=\nFor SymDump  for CICS users, specify an allocation STORAGE CLASS that the TRACE FORMAT REGION will use to\nallocate storage for trace formatting. This parameter is used only by the TRACE FORMAT REGION and is ignored by a\nCICS region.\nTRCFTHRD\nTRCFTHRD= 8  / number of threads\nFor SymDump  for CICS users, specify the number of simultaneous threads that will be supported for trace format\nrequests. This parameter should be used as a rudimentary throttle to allow performance tuning of the formatted trace\nfacility. This parameter is used only by the TRACE FORMAT REGION and is ignored by a CICS region.\nTRCFTOUT\nTRCFTOUT= 240 / trace timeout in seconds\nFor SymDump  for CICS users, specify trace timeout value in seconds that both the TRACE FORMAT REGION and the\nCICS task will wait on CCI calls used to communicate between the CICS task and the TRACE FORMAT REGION. When\nthis value is exceeded, the CCI session is terminated, and the formatted trace resources are freed. The operator remains\nwithin the reloaded dump, and is given the option of reformatting the trace. This will allow performance tuning of the\nformatted trace facility. This parameter is used by both the CICS region and the TRACE FORMAT REGION.\nTRCFUNIT\nTRCFUNIT=\nFor SymDump  for CICS users, specify an allocation UNIT that the TRACE FORMAT REGION will use to allocate storage\nfor trace formatting. This parameter is used only by the TRACE FORMAT REGION and is ignored by a CICS region.\nTRCFVOL\nTRCFVOL=\nFor SymDump  for CICS users, specify an allocation VOLUME that the TRACE FORMAT REGION will use to allocate", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "73993408a26d-1", "text": "storage for trace formatting. This parameter is used only by the TRACE FORMAT REGION and is ignored by a CICS\nregion.\nInterTest for CICS Options\nTo complete the configuration for your product, follow the steps described in this article.\nConfigure Abend Codes\nThis section describes how to limit the interception of abends and customize abend code help text.\nSpecify Non-Intercepted Abend Codes\nIf certain abend codes should not be intercepted regardless of the InterTest for CICS Automatic Breakpoint (ABI) setting,\nuse the IN25ABEN macro to specify the codes. InterTest for CICS provides a default IN25ABEN that includes the abend\ncodes AKC3, ATNI, ATCV, and AEXY.\n 188", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3747cef2339d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nAKC3 is needed to run InterTest for CICS with Verify for CICS.\nTo specify your own codes in the IN25ABEN macro, customize the sample member CCSAABEN in CAI.CAVHJCL.\nThe following example demonstrates the IN25ABEN macro usage:\n//ASM.SYSIN DD *\n     IN25ABEN TYPE=INITIAL\n     IN25ABEN ABCODE=(ATNI,ATCV,AEXY)\n     IN25ABEN ABCODE=AKC3\n     IN25ABEN ABCODE=(AKCT,APLE)\n     IN25ABEN ABCODE=(1234,'# Q$',1UMF)\n     IN25ABEN TYPE=FINAL\n     END\n/* \nIN25ABEN Coding Rules  -- Follow these rules when coding IN25ABEN:\n\u2022IN25ABEN TYPE=INITIAL must be coded first.\n\u2022The ABCODE= parameters must specify four-character abend codes. The abend codes ATNI, ATCV, and AEXY must\nbe included. Include the code AKC3 if you are running InterTest with Verify for CICS.\n\u2022If ABCODE specifies a list of abend codes, then separate the codes with commas and enclose the list in parentheses.\n\u2022Codes that include spaces or special characters must be enclosed in single quotes.\n\u2022IN25ABEN TYPE=FINAL terminates the table.\n\u2022END terminates the assembly source.\nAfter coding the macro, submit the JCL to assemble your options.\nCustomize Help Abend Codes\nYou can customize the help text displayed at an automatic breakpoint for abend codes. A separate help file, PROTUHF, is\navailable to hold your user-defined abend code descriptions.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3747cef2339d-1", "text": "available to hold your user-defined abend code descriptions.\nAfter installation, the online Abend Code Maintenance menu (ITST Option 7.2) lets you add, inquire, update, and delete\nentries in the user-defined help file. Press PF1 from this menu to obtain help on using the facility.\n        CA InterTest for CICS ABEND CODE MAINTENANCE MENU\nOPTION ===>\n    Enter Option, Abend code, and Program name; then press enter.\n  1 Add                  - Add an Abend code/Program name\n  2 Inquire              - Inquire on an Abend code/Program name\n  3 Update               - Update an Abend code/Program name\n  4 Delete               - Delete an Abend code/Program name\n  Abend code . . ____ Program name . . ________\n \n  PF1 Help    2         3 End     4 Return   5        6\n  PF7         8         9        10         11       12 \nYou can tie an abend code to a specific program by entering both the abend code and program name fields. You can\ncreate a generic abend code for all program names by entering the abend code only, with no program name.\nDuring a user session when InterTest for CICS intercepts an abend, it first searches for a matching abend code entry on\nthe user-defined help file. If a description for the abend code is found on the user-help file, InterTest for CICS displays its\ncontents at the breakpoint and on related SymDump  for CICS analysis displays.\n 189", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0ea702e76815-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIf there is no user-defined description or if the user file does not exist, then the abend code description from the\nInterTest for CICS help file is used. If there is no abend code description in the InterTest for CICS help file, then a default\nNOTFABCODE is displayed.\nSymDump  for CICS Options\nThis article describes SymDump  for CICS options.\nYou can choose to selectively override the SymDump  for CICS dump suppression criteria, by identifying dumps that must\nalways be captured.\nThe IN25CAPT load module contains the criteria for forcing dump capture.\nYou can use the following steps to create a customized copy of IN25CAPT.\nFollow these steps:\n1.Modify member CABQCAPJ of CAVHJCL and specify the abend codes, programs and transactions that identify the\ndumps you intend to capture.\n2.Assemble and link your customized code to create load module IN25CAPT.\n3.Stop SymDump , if active.\nNOTE\nIf SymDump  is active when you issued the NEWCOPY, the module does not get replaced.\n4.Issue the following CICS command to load the new copy of IN25CAPT\nCEMT SET PROG(IN25CAPT) NEWCOPY\nNOTE\nYou can skip this step the first time you use IN25CAPT.\n5.Restart SymDump  for CICS.\nProcedure for Modifying Dump Capture Criteria\nTo create module IN25CAPT and specify the dump capture options, use macro IN25CAPT to specify the abend codes,\nprograms and transactions, using any combination of exact and generic values.\nInvoke the macro once to initialize the Dump Capture Table, once for each entry you require and once to terminate the\ntable.\nFollowing tasks are performed:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0ea702e76815-1", "text": "table.\nFollowing tasks are performed:\n1.Each table entry identifies, either specifically or generically, the combination of abend code, program name and\ntransaction name that describe abends that must always be captured. \nThis task occurs regardless of the SymDump  for CICS options that suppress duplicate dumps, or suppress dumps by\nabend code. \nGeneric values are specified with a trailing asterisk (*).\n2.A dump gets captured when an abend matches at least 1 of the entries in IN25CAPT. To match a table entry, an abend\nmust match all three specified criteria (Abend code, Program and Transaction). Even if one of the criteria is omitted, or\na value of asterisk (e.g., PROG=*) is specified then the status indicates that all abends match that criteria.\nIN25CAPT Keywords\nThis section lists the IN25CAPT keywords. Slashes (/) between parameters indicate you must make a choice.\nSymDump  for CICS does not validate the values specified for abend codes, transaction names or program names.\nSpecifying undefined or invalid values results in no match, and hence, there is no change in dump handling.\n 190", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "92ec9804d1db-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTYPE=CSECT/ENTRY/FINAL\nDescribes the type of table entry.\nCSECT\nInitializes the table. Must be the first entry in the table and can only occur once.\nENTRY\nCreates a single table entry, specifying one combination of abend codes, transactions and programs that\nidentify abends that should be captured\nFINAL\nTerminates the table. Must be the last entry in the table and can only occur once.\nABEND=code identifier\nIdentifies the abend code(s) described by this entry.\ncode identifier\n1-4 characters, specifying the abend code(s) to be captured. If the final character is asterisk (*), abend\ncodes that begin with the characters preceding the asterisk are considered a match. ABEND=* indicates\nthat all abend codes are considered a match.\nPROG=program name\nIdentifies the program(s) described by this entry.\nprogram name\n1-8 characters, specifying the abending programs to be captured. If the final character is asterisk (*),\nprograms that begin with the characters preceding the asterisk are considered a match. PROG=*\nindicates that all program names are considered a match.\nTRAN=transaction name\nIdentifies the transaction(s) described by this entry.\ntransaction name\n1-4 characters, specifying the transactions(s) to be captured. If the final character is asterisk (*),\ntransactions that begin with the characters preceding the asterisk are considered a match. TRAN=*\nindicates that all transaction names are considered a match.\nHow Macro IN25CAPT Controls  Dump Capture \nThe section illustrates the effect of specifying certain values in the Capture option.\nAssuming your customized IN25CAPT was assembled with the following options:\nIN25CAPT TYPE=CSECT", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "92ec9804d1db-1", "text": "IN25CAPT TYPE=CSECT   \nIN25CAPT TYPE=ENTRY,TRAN=ABCD,PROG=PGM1\nIN25CAPT TYPE=ENTRY,ABEND=ASRA,TRAN=CA*,PROG=*\nIN25CAPT TYPE=ENTRY,TRAN=DDX,PROG=MYPROG*\nIN25CAPT TYPE=ENTRY,TRAN=X12*,PROG=USERPG1\nIN25CAPT TYPE=ENTRY,ABEND=AN*,PROG=USERP*\nIN25CAPT TYPE=FINAL\nThe following table lists the abends and resulting actions for the above source code:\nAbend Codes, abending transactions and programs Result\nAbend ASRA, program IEFBR14, transaction CAD Capture, due to entry TRAN=CA*,PROG=*\nAbend ASRA, program GENE, transaction DDX No effect, no matching entries\nAbend AICA, program MYPROG, transaction X123 No effect, no matching entries\n 191", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "25483ac4a54e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAbend ANQA, program PGM123, transaction ABCD No effect, no matching entries\nAbend ANQA, program USERPG3, any transaction Capture due to entry ABEND=AN*,PROG=USERP\nAbend AD22, program USERPG2, transaction ABCD No effect, no matching entries\nAny abend, program MYPROG2, transaction DDX Capture due to entry TRAN=DDX,PROG=MYPROG*\nAbend ASRA, program USER1, transaction X12 No effect, no matching entries\nExternal Security Option\nUse the EXTSEC installation option in CAVHCONF to control the external security feature for individual product\ncomponents.\nThe default is NONE. For more information about setting and modifying CAVHCONF options, see Global Options.\nResource Protection Levels\nThe following resources are protected in Symbolic Component under the External Security feature:\nNOTE\n\u2022Systems that initialize, update options, delete, purge, or reload a PROTSYM must also have the required\naccess.\n\u2022The CAMRUSR1 and CAMRUSR2 user exits are called only if the user has the necessary authorities for the\nrequested action.\nVHALTER\nClass\nCA@NTSYM\nEntity\nVHALTER\nAccess Level\nRead\nFunction Type\nInitialize, Update\nProduct Options/Menu Options\nIN25UTIL INIITIALIZE, UPDATE OPTIONS (MAXPGMVER, USEDSPACEMSG)\nVHALTER lets you use the symbolic component IN25UTIL utility INITIALIZE and UPDATE functions.\nVHCONTR\nClass\nCA@NTSYM\nEntity\nVHCONTR\nAccess Level\nRead\nFunction Type\nDelete, Purge, Reload Listing\nProduct Options/Menu Options\nIN25UTIL DELETE, PURGE, or RELOAD\n 192", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6e73a721ce6d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nVHCONTR lets you use the symbolic component IN25UTIL utility DELETE, PURGE, and RELOAD functions.\nThe following resources are protected in InterTest Batch under the External Security feature::\nMRMISM\nClass\nCA@NTSYM\nEntity\nMRMISM\nAccess Level\nRead\nFunction Type\nMismatched Symbolic members\nProduct Options/Menu Options\nForeground or Batch Link debugging\nMRMISM lets you select a mismatched symbolic member during a debugging session.\nExternal Security Using Top Secret\nThe external security interface that is used in Symbolic Component is compatible with Top Secret 12.0 or above.\nDefine the Resource Class CA@NTSYM\nThe Symbolic Component uses a unique resource class, CA@NTSYM, for its security controls.\nList a Resource Class\nTo determine if CA@NTSYM is defined to your Top Secret system, issue the following command:\nTSS LIST(RDT) RESCLASS(CA@NTSYM)\nThis command lists the definition of the CA@NTSYM resource in the Top Secret Resource Definition Table (RDT).\n\u2022If CA@NTSYM is present and its definition matches the attributes below, no further action is required:\nACCESS = ALL,UPDATE,READ DEFACC = READ\n\u2022If any of the attributes do not match, change the definition using the TSS REPLACE(RDT) command, specifying the\ncorrect parameters.\n\u2022If you get an error message that indicates the resource is missing, invalid, or reserved, you must define CA@NTSYM\nIf CA@NTSYM is not defined, you must add it to the RDT. Add new classes using the TSS command ADDTO function\nthrough any facility supporting the TSS command. Once added, these resources become a permanent part of the security\nfile and can be immediately administered and reported on by name.\nAdd a Resource Class", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6e73a721ce6d-1", "text": "file and can be immediately administered and reported on by name.\nAdd a Resource Class\nThe syntax to add the CA@NTSYM resource is as follows.\nTSS ADDTO(RDT) RESCODE(38) RESCLASS(CA@NTSYM) -\nACLST(ALL,UPDATE,READ) DEFACC(READ)\nThe syntax uses a RESCODE of 38. This code value is up to each site and must be unique. Codes 01 to 3F are available.\nOnce you define the resource CA@NTSYM to your system, you can establish access controls to IN25UTIL functions. No\nIPL, re-initialization, or parameter changes are needed for these changes to become active and permanent.\n 193", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d7b798adbc24-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse CA@NTSYM to Control IN25UTIL Functions\nThe CA@NTSYM resource controls IN25UTIL utility INITIALIZE, UPDATE, DELETE, PURGE, and RELOAD functions.\nCA@NTSYM is a standard short resource and is managed in the same manner as other access level resources.\nIssue the following command:\nTSS ADDTO(deptname) CA@NTSYM(VHALTER,VHCONTR)\n\u2022To allow user USER01 to have Read access to entity VHALTER, use the following command:\nTSS PERMIT(USER01) CA@NTSYM(VHALTER) ACCESS(READ)\nIf you omit the ACCESS keyword, Top Secret defaults the PERMIT to Read access.\n\u2022To allow user USER01 to have Read access to entity VHCONTR, use the following command:\nTSS PERMIT(USER01) CA@NTSYM(VHCONTR) ACCESS(READ)\nIf you omit the ACCESS keyword, Top Secret defaults the PERMIT to Read access.\nExternal Security Using ACF2\nThe external security interface in Common Component is compatible with ACF2  6.2 or higher.\nDefine the Resource Class CA@NTSYM\nCommon Component uses a unique resource class, CA@NTSYM, for its internal security controls.\nCA@NTSYM must be defined to ACF2  with its own three-character resource type. In the following example, CA@NTSYM\nis defined using the resource type SYM.\nSET CONTROL(GSO) INSERT clasmap.CA@NTSYM - \nRESOURCE(CA@NTSYM) RSRCTYPE(SYM) ENTITYLN(7)\nAfter you add this clasmap definition, refresh the GSO clasmap.\nBy default, logging of SMF records is turned off. To have SMF records written for this resource class, add the LOG", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d7b798adbc24-1", "text": "parameter to the definition.\nSET CONTROL(GSO) INSERT clasmap.CA@NTSYM - \nRESOURCE(CA@NTSYM) RSRCTYPE(SYM) ENTITYLN(7) LOG\nTo protect and allow access to the Common Component PROTSYM file, use the standard ACF2  rule writing.\nSET RESOURCE(SYM) COMPILE * $KEY(VHALTER) TYPE(SYM) UID(uidstring/mask) SERVICE(READ) ALLOW $KEY(VHCONTR)\n TYPE(SYM) UID(uidstring/mask) SERVICE(READ) ALLOW END STORE *\nIf the SERVICE keyword is not supplied, ACF2  defaults to permit access to all service levels.\nExternal Security Using IBM RACF\nThe external security interface in Common Component can be used with IBM RACF, and is compatible with IBM RACF\nv1.9 or higher.\nDefine the Resource Class CA@NTSYM\nDefine a new class, CA@NTSYM, for Common Component security in the IBM RACF Class Descriptor Table (module\nICHRRCDE). The following information should be included in the ICHERCDE macro entry:\nREDEFINE CDT CA@NTSYM UACC(NONE) CDTINFO(POSIT(201) CASE(UPPER) FIRST(ALPHA,NATIONAL) + \nOTHER(ALPHA,NATIONAL) MAXLENGTH(7) MAXLENX(44) PROFILESALLOWED(YES))\n 194", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1c3ccd6e6dd4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nRecommendations are not given for any DFTUACC and are determined by each site.\nRouter Table Entry for CA@NTSYM\nMake an entry for the CA@NTSYM class in the IBM RACF Router Table (module ICHRFR01). Specify ACTION=RACF.\nThis entry is generated by the ICHRFRTB macro.\nEnabling the Class CA@NTSYM\nTo activate the new class CA@NTSYM defined in the CDT and Router Table, issue the following command:\nSETROPTS RACLIST(CDT) REFRESH\nIssue IBM RACF RDEFINES for Common Component Entities First, you must issue the IBM RACF RDEFINE command\nfor every Common Component entity that you want to protect. For example, issue the following commands to protect the\nCA@NTSYM resources:\nRDEFINE CA@NTSYM VHALTER UACC(NONE) RDEFINE CA@NTSYM VHCONTR UACC(NONE)\nTo protect and allow access to the Common Component PROTSYM file, use the standard RACF rule writing.\nExample:\nDefine a general user with access to VHALTER:\nPERMIT VHALTER CLASS(CA@NTSYM) ID(userid) ACC(READ)\nUser Exits\nThis article describes the user exits for each of the InterTest and SymDump  products.\nThe user exits are unique for each product. Click the page for your product to view the documentation on the user exits.\nInterTest Batch User Exits\nThis article describes InterTest Batch user exits.\nDefine Excluded Programs\nCAVHSRC member CAMRXMOD defines the list of programs that will not be automatically monitored when wildcarding\nis used on the monitor control panel. Edit the list to include any programs that you do not want to be automatically", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1c3ccd6e6dd4-1", "text": "monitored. We suggest that the supplied default list is left intact. If you must monitor a program whose name is present in\nthis list, you can still monitor the program by explicitly adding the name of the program to the monitor control panel.\nThe JCL is included in the configuration PTF that assembles and links this program. The JCL member is CAMRXMOJ and\nit is found in the CAI.CAVHJCL data set. The JCL must be modified JCL to conform to their installation standards before\nsubmitting it.\nDefine the Batch Link Selection User Exit\nWhen you make a selection from the Batch Link Selection panel, a user exit, CAMRUSR1, is called. This allows for\nsecurity checks to verify that the user who selected the job has the authority to monitor its execution. You can use the\nSYSID passed to CAMRUSR1 to enable further security checks, for instance when you have the SYSPLEX option\nenabled to allow debugging jobs on foreign LPARs.\n 195", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3c1612366cf5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nFor more information about coding this user exit, see the CAVHJCL member CAMRUSR1. The shipped default\nmember allows all users to select any available batch link job for debugging.\nThe JCL is included in the configuration PTF that assembles and links this program. The JCL member is CAMRUS1J and\nit is found in the CAI.CAVHJCL data set. The JCL must be modified JCL to conform to their installation standards before\nsubmitting it.\nDefine the Batch Link Scheduling User Exit\nWhen you make a selection from the Batch Link DB2 and IMS Schedule panel, a user exit, CAMRUSR2, is called. This\nallows for security checks to verify that the user has the authority to perform the scheduling functions.\nNOTE\nFor more information about coding this user exit, see the CAVHJCL member CAMRUSR2. The shipped default\nmember permits all users this authority.\nThe JCL is included in the configuration PTF that assembles and links this program. The JCL member is CAMRUS2J and\nit is found in the CAI.CAVHJCL data set. The JCL must be modified JCL to conform to their installation standards before\nsubmitting it.\nSymDump  Batch User Exits\nThis article describes SymDump  Batch user exits.\nControl Exclusion Criteria\nSymDump  Batch provides a user exit (CAOEUSR1) that permits more detailed exclusion or inclusion criteria. This user\nexit receives control following the examination of normal exclusion criteria (from CAOETABL).\nCAOEUSR1 is entered with the following registers:\nR1\nAddress of USRDATA parameter list\nR13\nAddress of 72-byte save area\nR14\nReturn address\nR15\nAddress of CAOEUSR1", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3c1612366cf5-1", "text": "R14\nReturn address\nR15\nAddress of CAOEUSR1\nThe USRDATA parameter list contains the following information:\nUSRDATA  DSECT\nUSRFLGS  DS    XL1              FLAG BYTE\nUSRACTM  EQU   B'10000000'      ACCOUNT CODE MATCH\nUSRSMFM  EQU   B'01000000'      SMF CODE MATCH\nUSRSABM  EQU   B'00100000'      SYSTEM ABEND CODE MATCH\nUSRUABM  EQU   B'00010000'      USER ABEND CODE MATCH\nUSRSUBM  EQU   B'00001000'      SUB SYSTEM MATCH\nUSRPROGM EQU   B'00000100'      PROGRAM NAME MATCH\nUSRJOBM  EQU   B'00000010'      JOB NAME MATCH\nUSRACCNT DS    CL25             CURRENT JOB CARD ACCOUNT\nUSRSMF   DS    CL4              ACTIVE SMF ID\n 196", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eec922dc7612-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUSRSABND DS    CL3              USER ABEND CODE\nUSRUABND DS    CL4              SYSTEM ABEND CODE\nUSRSUBS  DS    CL4              ACTIVE SUBSYSTEM\nUSRPROG  DS    CL8              PROGRAM NAME\nUSRJOB   DS    CL8              JOB NAME\n         DS    0F\nUSRWORK  DS    CL64             64-BYTE WORK AREA\nUSRLEN   EQU   *-USRDATA \nUse copybook CAOEPRM1 to map the USRDATA parm area.\nSymDump  Batch acts on the return code (in R15) from CAOEUSR1 as follows:\n0\nThe application uses its normal exclusion criteria from CAOETABL\n4\nThe application produces a report\n6\nThe application does not produce a report\nAfter you customize the source for CAOEUSR1 in CAI.CAVHJCL, submit the JCL to assemble and link the program. After\nlinking the program, an IPL is required to load a new copy of the user exit into CSA.\nNOTE\nWhen using the CAOEUSR1 user exit, note the following:\n\u2022CAOEUSR1 is provided as a stub that always returns with RC=0, so your exclusion criteria in CAOETABL is\nhonored.\n\u2022CAOEUSR1 executes AMODE=31 and RMODE=ANY and must be REENTRANT.\nControl the Destination of Reports\nCAIPRINT Repository Library\nSymDump  Batch provides a user exit, CAOCUPRT, which allows the CAIPRINT repository library to be determined based\nupon user-specified criteria (such as the userid or job name). The user exit receives control if the CAIPRTLB DD is not\nspecified in the JCL.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eec922dc7612-1", "text": "specified in the JCL.\nTo control the CAIPRINT repository library, code this user exit in Assembler language, and ensure that it conforms to the\nregister conventions described next.\nRegister Conventions\nCAOCUPRT is entered with the following registers:\nR1\nAddress of PRTPARM parameter list (as defined next)\nR13\nAddress of 72-byte save area\nR14\nReturn address\nR15\nAddress of CAOCUPRT\n 197", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2fd15277aa90-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUser Exit Parameter List\nThe PRTPARM parameter list contains the following information:\nPRTPARM  DSECT                    PARMLIST PASSED TO CAOCUPRT\nPRTJOB   DS    CL8                JOB NAME                    \nPRTSTEP  DS    CL8                STEP NAME                       \nPRTUSRID DS    CL8                USERID                          \nPRTTIME  DS    CL8                TIME OF REPORT IN EBCIDIC\n*                                 (00HHMMSS)\nPRTDATE  DS    CL8                DATE OF REPORT IN EBCIDIC\n*                                 (YYYYMMDD)\nPRTPGMID DS    CL8                PROGRAM ID                      \nPRTCODE  DS    CL7                COMPLETION CODE (LEFT JUSTIFIED)\nPRTDSN   DS    CL44               DATA SET NAME                    \nPRTPARML EQU   *-PRTPARM                                          \n* NOTE:  THE COMPLETION CODE WILL BE IN ONE OF THE FOLLOWING\n*        FORMATS:\n*          SYSTEM ABEND CODE = SXXX                               \n*          USER ABEND CODE   = UXXXX                              \n*          MESSAGE ID        = MSGXXXX  (I.E., CEE3501 OR IGZ0035)\n*          RETURN CODE       = RCXXXX                                 \nAll of the fields in the PRTPARM DSECT, including PRTDSN, are set before the call to CAOCUPRT. However, if the\napplication did not abend, the program name will be blank.\nUpon return from CAOCUPRT, if R15 contains a nonzero return code, the repository library defined in the default CSECT,\nCAOUDFRX, or specified by the option override in the CAIOPTS DD is used. If R15 contains a zero return code, the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2fd15277aa90-1", "text": "repository library returned by CAOCUPRT in the PRTDSN field of the PRTPARM DSECT is used.\nSample User Exit Program\nThe following sample program returns a repository data set name based upon the assigned group of the user:\nCAOCUPRT TITLE 'CAOCUPRT  -  CAIPRINT Repository User Exit'\nCAOCUPRT CSECT\nCAOCUPRT AMODE 31\nCAOCUPRT RMODE ANY\n         USING CAOCUPRT,12\n         STM   R14,R12,12(R13)         SAVE REGS                 \n         LR    R12,R15                 SET BASE REGISTER\n         SPACE ,                                 \n         LR    R3,R1                   -> INPUT PARM LIST\n         USING PRTPARM,R3                                    \n         LA    R2,USRTBL               -> USERID TABLE          \n         USING USERDEF,R2                                      \nTBLLOOP  DS    0H                                         \n         C     R2,=A(USRTEND)          END OF TABLE?        \n         BNL   NODSN                   YES, SET RC AND EXIT     \n         CLC   USERID,PRTUSRID         FIND USERID IN TABLE?       \n         BE    GETDSN                  YES, GET PRTLIB DSN       \n         LA    R2,USERDEFL(,R2)        GET NEXT ENTRY         \n         B     TBLLOOP                 LOOP\n         SPACE ,                                               \nGETDSN   DS    0H                                         \n 198", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "357604944c0f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n         LH    R1,USERGRP              GET GROUP INDEX       \n         MH    R1,=H'44'               CALC INDEX INTO DSN LIST \n         A     R1,=A(DSNLIST)                                 \n         MVC   PRTDSN,0(R1)            SET PRTLIB DSN           \n         SR    R15,R15                 SET RC=0              \n         B     EXIT                    RETURN                   \n         DROP  R2,R3                                          \n         SPACE ,                                               \nNODSN    DS    0H                                             \n         LA    R15,4                   SET RC=4                  \n         SPACE ,                                               \nEXIT     DS    0H                                                \n         L     R14,12(R13)             RESTORE R14              \n         LM    R0,R12,20(R13)          RESTORE R0-R12           \n         BR    R14                     RETURN                \n         SPACE ,                                               \n         TITLE 'GROUP EQUATES'                                 \nDEVL     EQU   0    \nQA       EQU   1                                              \nPROD     EQU   2                                             \n         SPACE ,                                               \n         TITLE 'USERID TABLE'                                 \nUSRTBL   EQU   *                                              \n         DC    CL8'USER1',Y(DEVL)                           \n         DC    CL8'USER2',Y(DEVL)                              \n         DC    CL8'USER3',Y(DEVL)                            \n         DC    CL8'USER4',Y(QA)                             \n         DC    CL8'USER5',Y(QA)                             \n         DC    CL8'USER6',Y(QA)                             \n         DC    CL8'USER7',Y(QA)                             \n         DC    CL8'USER8',Y(PROD)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "357604944c0f-1", "text": "DC    CL8'USER8',Y(PROD)                           \n         DC    CL8'USER9',Y(PROD)                          \n         DC    CL8'USER10',Y(PROD)                            \nUSRTEND  EQU   *                                            \n         SPACE ,                                              \n         TITLE 'PRTLIB DSN LIST'                              \nDSNLIST  EQU   *                                           \n         DC    CL44'DEVL.PRTLIB'                        \n         DC    CL44'QA.PRTLIB'            \n         DC    CL44'PROD.PRTLIB'                  \n         LTORG ,                                       \n         EJECT                                                \nR0       EQU   0                                              \nR1       EQU   1                                              \nR2       EQU   2                                              \nR3       EQU   3                                              \nR4       EQU   4                                              \nR5       EQU   5                                              \nR6       EQU   6                                              \nR7       EQU   7                                              \nR8       EQU   8                                              \nR9       EQU   9                                              \nR10      EQU   10                                             \n 199", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "314dcc2be313-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nR11      EQU   11                                             \nR12      EQU   12                                             \nR13      EQU   13                                             \nR14      EQU   14                                             \nR15      EQU   15                                            \n         SPACE 1                                              \nPRTPARM  DSECT                    PARMLIST PASSED TO CAOCUPRT \nPRTJOB   DS    CL8                JOB NAME                    \nPRTSTEP  DS    CL8                STEP NAME                       \nPRTUSRID DS    CL8                USERID                          \nPRTTIME  DS    CL8                TIME OF REPORT IN EBCIDIC\n*                                 (00HHMMSS)\nPRTDATE  DS    CL8                DATE OF REPORT IN EBCIDIC\n*                                 (YYYYMMDD)\nPRTPGMID DS    CL8                PROGRAM ID                      \nPRTCODE  DS    CL7                COMPLETION CODE (LEFT JUSTIFIED)\nPRTDSN   DS    CL44               DSN RETURNED                    \nPRTPARML EQU   *-PRTPARM                                          \n* NOTE:  THE COMPLETION CODE WILL BE IN ONE OF THE FOLLOWING\n*        FORMATS:*          SYSTEM ABEND CODE = SXXX                               \n*          USER ABEND CODE   = UXXXX                              \n*          MESSAGE ID        = MSGXXXX  (I.E., CEE3501 OR IGZ0035)\n*          RETURN CODE       = RCXXXX                        \n          SPACE 1                                                  \nUSERDEF  DSECT                                                    \nUSERID   DS    CL8                                                \nUSERGRP  DS    H                                                  \nUSERDEFL EQU   *-USERDEF                                   \n               SPACE 1                                             \n               END   CAOCUPRT        \nUser Exit JCL", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "314dcc2be313-1", "text": "SPACE 1                                             \n               END   CAOCUPRT        \nUser Exit JCL\nJCL to assemble and link this user exit can be found in CAI.CAVHJCL(CAOCUPRT). The previous example is provided in\nthat member.\nNOTE\nWhen using the CAOCUPRT user exit to control the destination of abend reports, note the following information:\n\u2022CAOCUPRT is provided as a stub that always returns with RC=4. Therefore, the repository data set name\ndoes not change if a user exit is not provided.\n\u2022CAOCUPRT can execute AMODE=24 or AMODE=31, and must be REENTRANT.\nDynamic Allocation for the CAIPRINT DD\nSymDump  Batch provides a user exit, CAOCUDSN that enables CAIPRINT to be written to a user-specified data set. The\nuser exit receives control if the CAIPRINT DD is not specified in the JCL.\nTo control dynamic allocation for the CAIPRINT DD, code this user exit in Assembler language, and ensure that it\nconforms to the register conventions described next.\nRegister Conventions\nCAOCUDSN is entered with the following registers:\n 200", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3678c1ca1a50-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nR1\nAddress of the USERDSN parameter list (as defined in User Exit Parameter List)\nR13\nAddress of 72-byte save area\nR14\nReturn address\nR15\nAddress of CAOCUDSN\nUser Exit Parameter List\nThe USRDSN parameter list contains the following information:\nUSERDSN  DSECT        * PARM LIST PASSED TO CAOCUDSN\nUSRJOBID DS   CL8     JOB NUMBER (ASSIGNED BY THE SYSTEM)\nUSRJBNAM DS   CL8     JOB NAME   (FROM THE JOB CARD)\nUSRJBSTP DS   CL8     STEP NAME\nUSRLENID DS   CL1     LENGTH OF USERID\nUSRUSRID DS   CL8     USERID     (PERSON WHO SUBMITTED THE JOB)\nUSRTIME  DS   CL8     TIME OF REPORT IN EBCIDIC (FORMAT THHMMSS)\nUSRDATE  DS   CL8     DATE OF REPORT IN EBCIDIC (FORMAT MMDDYYYY)\nUSRPRGNM DS   CL8     MAIN PROGRAM (LOAD MODULE ABEND OCCURRED IN)\nUSRABCDE DS   CL5     COMPLETION CODE (LEFT JUSTIFIED, Sxxx OR\n*                     Unnnn\n* LAST 3 FIELDS ARE FILLED IN BY THE USER EXIT CAOCUDSN\nUSRDSN   DS   CL44    DSN RETURNED\nUSRUNIT  DS   CL8     UNIT NAME RETURNED (OPTIONAL)\nUSRVOL   DS   CL6     VOLSER FOR DSN RETURNED (OPTIONAL)\nUSRLEN   EQU  *-USRDSN \nUpon return from CAOCUDSN, if R15 contains a nonzero return code or the USRDSN field is blank, CAIPRINT is", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3678c1ca1a50-1", "text": "dynamically allocated to SYSOUT. If R15 contains a zero return code, CAIPRINT is dynamically allocated to the data set\ndefined in USRDSN. If the UNIT or volume fields were also specified, they are used by dynamic allocation.\nExample:\nA sample user exit program appears next:\nCAOCUDSN TITLE 'CAOCUDSN'\nCAOCUDSN CSECT\nCAOCUDSN AMODE 24\nCAOCUDSN RMODE 24\n*THIS SAMPLE PROGRAM WILL RETURN A DATA SET NAME OF\n*USERID.TIME.JOBNAME\n         USING CAOCUDSN,R12\n         STM   R14,R12,12(R13)\n         LR    R12,R15\n         LR    R3,R1\n         USING USERDSN,R3\n         XR    R4,R4\n         IC    R4,USRLENID             GET LENGTH OF USERID\n         BCTR  R4,0                    EXECUTE LENGTH\n         LA    R5,USRDSN               POINT TO OUTPUT FIELD\n         EX    R4,MOVEID               MOVE IN USERID\n 201", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7401c8efccce-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n         LA    R5,1(R4,R5)             BUMP POINTER\n         MVI   0(R5),C'.'              MOVE IN PERIOD\n         LA    R5,1(,R5)               BUMP POINTER\n         MVC   0(8,R5),USRTIME         MOVE IN TIME\n         LA    R5,8(,R5)               BUMP POINTER\n         MVI   0(R5),C'.'              MOVE IN PERIOD\n         LA    R5,1(,R5)               BUMP POINTER\n         MVC   0(8,R5),USRJBNAM        MOVE IN JOB NAME\n         LA    R5,8(,R5)               BUMP POINTER\n         L     R14,12(R13)\n         XR    R15,R15\n         LM    R0,R12,20(R13)\n         BR    R14\nMOVEID   MVC   0(R4,R5),USRUSRID\n         LTORG ,\n         EJECT\nR0       EQU   0\nR1       EQU   1\nR2       EQU   2\nR3       EQU   3\nR4       EQU   4\nR5       EQU   5\nR6       EQU   6\nR7       EQU   7\nR8       EQU   8\nR9       EQU   9\nR10      EQU   10\nR11      EQU   11\nR12      EQU   12\nR13      EQU   13\nR14      EQU   14\nR15      EQU   15\nUSERDSN  DSECT \n*   PARM LIST PASSED TO CAOCUDSN", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7401c8efccce-1", "text": "*   PARM LIST PASSED TO CAOCUDSN\nUSRJOBID DS   CL8     JOB NUMBER (ASSIGNED BY THE SYSTEM)\nUSRJBNAM DS   CL8     JOB NAME   (FROM THE JOB CARD)\nUSRJBSTP DS   CL8     STEP NAME\nUSRLENID DS   CL1     LENGTH OF USERID\nUSRUSRID DS   CL8     USERID     (PERSON WHO SUBMITTED THE JOB)\nUSRTIME  DS   CL8     TIME OF REPORT IN EBCIDIC (FORMAT THHMMSS)\nUSRDATE  DS   CL8     DATE OF REPORT IN EBCIDIC (FORMAT MMDDYYYY)\nUSRPRGNM DS   CL8     MAIN PROGRAM (LOAD MODULE ABEND OCCURRED IN)\nUSRABCDE DS   CL5     COMPLETION CODE (LEFT JUSTIFIED, SXXX OR\n*                     UNNNN)\n*   LAST 3 FIELDS ARE FILLED IN BY THE USER EXIT CAOCUDSN\nUSRDSN   DS   CL44    DSN RETURNED\nUSRUNIT  DS   CL8     UNIT NAME RETURNED (OPTIONAL)\nUSRVOL   DS   CL6     VOLSER FOR DSN RETURNED (OPTIONAL)\nUSRLEN   EQU  *-USRDSN\n         END   CAOCUDSN \n 202", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4b516c2db3a5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUser Exit JCL\nJCL to assemble and link this user exit can be found in CAI.CAVHJCL(CAOIUSR1). The previous example is provided in\nthat member.\nNOTE\nWhen using the CAOCUDSN user exit to control the destination of abend reports, note the following information:\n\u2022CAOCUDSN is provided as a stub that always returns with RC=4. Therefore, the dynamic allocation of\nCAIPRINT does not change if a user exit is not provided.\n\u2022CAOCUDSN executes AMODE=24 and RMODE=24 and must be REENTRANT. It is linked with module\nCAOCIN00.\n\u2022When CAOIUSR1 is updated, the product must be reinitialized for the user exit to take effect.\nControl Access to Reports in the Repository\nYou can customize and build the user exit program CAOIUSR1 to secure the following types of access to the abend\nrepository:\n\u2022Viewing reports\n\u2022Deleting reports\n\u2022Locking and unlocking reports\n\u2022Modifying formatting options\n\u2022Printing reports\nThis user exit receives control whenever any user attempts to access the repository for any of these operations.\nTo control access to reports in the repository, you must code this user exit in Assembler language, and it must conform to\nthe conventions described next.\nInput Registers\nCAOIPRM1 is entered with the following registers:\nR1\nAddress of the input parm, mapped by DSECT CAOIPRM1. This area contains the ID of the user attempting the\naccess, the request type, and information about the report being accessed.\nR13\nAddress of a 72-byte register save area provided by the caller.\nR14\nAddress where CAOIUSR1 must return to its caller.\nR15\nAddress of CAOIUSR1.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4b516c2db3a5-1", "text": "R15\nAddress of CAOIUSR1.\nOutput Registers\nCAOIPRM1 is required to restore all registers to their original values, except R15, which must return one of the following\nvalues:\nR15=0\nAllow the access requested.\nR15=4\nDeny the access requested\nAny other value in R15 may produce unpredictable results.\n 203", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "00d3676aa444-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUser Exit Parameter List\nThe CAOIPRM1 parameter list contains the following information:\nCAOIPRM1 DSECT                                                   \nPRM1REQ  DS    XL4                    Request type               \nP1_OPEN  EQU   5                        5 = Open a report for view\nP1_DEL   EQU   9                        9 = Delete a report      \nP1_LOCK  EQU   16                      16 = Lock a report        \nP1_UNLK  EQU   17                      17 = Unlock a report      \nP1_OPTS  EQU   21                      21 = Update report options\nP1_PRINT EQU   22                      22 = Print a report       \nPRM1USR  DS    CL8                    Requestor's user id        \nPRM1RJOB DS    CL8                    Report Job Name            \nPRM1RUSR DS    CL8                    Report User Id             \nPRM1WORK DS    XL256                  256-BYTE WORK AREA         \nLPRM1    EQU   *-CAOIPRM1              \nSample User Exit Program\nThe following sample version of CAOIUSR1 that unconditionally enables every requested access is provided\nin CAI.CAVHJCL:\nCAOIUSR1 TITLE 'Sample Repository Viewer Security Exit'               \n**------------------------------------------------------------------**\n**                                                                  **\n**  CAOIUSR1 - Sample Repository Viewer Security Exit               **\n**                                                                  **\n**  This user exit performs security validation prior to            **\n**  various repository viewer functions.                            **\n**                                                                  **\n**  Input Registers:                                                **\n**                                                                  **\n**  R1 contains the address of the parm area (CAOIPRM1)             **\n**  R13 contains the address of a register save area                **", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "00d3676aa444-1", "text": "**  R13 contains the address of a register save area                **\n**  R14 contains the return address                                 **\n**  R15 contains the address of CAOIUSR1                            **\n**                                                                  **\n**  All other registers are unpredictable.                          **\n**                                                                  **\n**  Output Registers:                                               **\n**                                                                  **\n**  R15 contains the return code (described next)                   **\n**                                                                  **\n**  All other registers must be returned unchanged.                 **\n**                                                                  **\n**  Return Codes                                                    **\n**                                                                  **\n**  R15 = 0   Allow access.                                         **\n**  R15 > 0   Disallow access.                                      **\n**                                                                  **\n**------------------------------------------------------------------**\n         SPACE ,                                                      \nCAOIUSR1 CSECT                                                     \n 204", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ca7f362c6132-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n         USING CAOIUSR1,R12            Map the User Exit            \n         USING CAOIPRM1,R8             Map the Parameter Area         \n         USING LDATA,R13               Map Local Data                  \n         SPACE ,                                                      \n         STM   R14,R12,12(R13)         Save caller's registers      \n         LR    R12,R15                 Set procedure base             \n         LR    R8,R1                   Set parm base                 \n         SPACE ,                                                   \n         LA    R1,PRM1WORK             @ Work area provided         \n         XC    0(256,R1),0(R1)         Clear it out                 \n         ST    R13,4(,R1)              Save backward chain          \n         ST    R1,8(,R13)              Save forward chain           \n         LR    R13,R1                  Set our RSA address           \n         SPACE ,                                                       \n* Perform security validation here.                                 \n         SPACE ,                                                      \nRETURN   DS    0H                                                    \n         L     R15,LDRC                Load the return code          \n         L     R13,4(,R13)             Restore @ caller's rsa         \n         L     R14,12(,R13)            Load return address            \n         LM    R0,R12,20(R13)          Restore registers              \n         BR    R14                     Return to caller              \n         TITLE 'LITERALS'                                           \n         LTORG ,                                                    \n         TITLE 'DSECTS: Local Data'                                   \nLDATA    DSECT                                                        \nLDSAVE   DS    18F                                                    \nLDRC     DS    F                                                    \n         TITLE 'DSECTS: Parameter Area'                         \n         COPY  CAOIPRM1                                             \n         TITLE 'REGISTER EQUATES'                                     \nR0       EQU   0", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ca7f362c6132-1", "text": "TITLE 'REGISTER EQUATES'                                     \nR0       EQU   0                                                      \nR1       EQU   1                                                      \nR2       EQU   2                                                      \nR3       EQU   3                                                      \nR4       EQU   4                                                      \nR5       EQU   5                                                      \nR6       EQU   6                                                      \nR7       EQU   7                                                      \nR8       EQU   8                                                      \nR9       EQU   9                                                      \nR10      EQU   10                                                     \nR11      EQU   11                                                     \nR12      EQU   12                                                     \nR13      EQU   13                                                     \nR14      EQU   14                                                     \nR15      EQU   15                                                   \n         END   CAOIUSR1  \nUser Exit JCL\nAfter you customize the source for CAOIUSR1 in CAI.CAVHJCL, submit the JCL to assemble and link the program.\n 205", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "11fad526c501-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nWhen using the CAOIUSR1 user exit to secure the various types of access to the abend repository, note the\nfollowing information:\n\u2022CAOIUSR1 resides as a stand-alone single-CSECT load module.\n\u2022CAOIUSR1 receives control in 31-bit addressing mode.\nManagement Reporting System (MRS) User Exits\nThe Management Reporting System (MRS) provides you with a facility to develop your own output report. Two user exits\nenable access to the data that the MRS processes. You can specify these exits separately or concurrently by using the\nCOBOLEX or NOCOBEX execution options. (COBOLEX accesses Detail Report information; NOCOBEX accesses non-\nCOBOL CSECTs.)\nAccess Detail Report Information (COBOLEX)\nCOBOLEX provides access to the information that MRS uses to print the Detail Report. If you specify this exit, MRS\nloads a copy of the specified user program (see Invoke a User Exit JCL). Each time MRS processes a COBOL CSECT, a\nbranch is made and data is passed to the user program using a parameter list pointed to by Register 1. The list contains\nthe two parameters shown next:\n XDATADDR DS A            address of MRS dataXNEWADDR DS AL1(128),AL3 address for a substitute print line \nXDATADDR contains the address of the CSECT data being passed. The following DSECT shows the order in which the\nfields appear:\nEXITBUF  DS   0CL102           USER EXIT BUFFER        \nXITMNAME DS    CL8             MODULE NAME             \nXITMSIZE DS    PL5             MODULE SIZE             \nXITCNAME DS    CL8             CSECT NAME", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "11fad526c501-1", "text": "XITCNAME DS    CL8             CSECT NAME              \nXITCSIZE DS    PL5             CSECT SIZE             \nXITDDLEN DS    PL5             DATA SIZE              \nXITPDLEN DS    PL5             PROCEDURE SIZE          \nXITCMPLR DS    CL4             COMPILER                \n***********************************************************\n* POSSIBLE VALUES ARE                                  \n*        DC    C'COBF'         COBOL-F                 \n*        DC    C'ANS2'         ANS VERSION 2           \n*        DC    C'ANS3'         ANS VERSION 3           \n*        DC    C'ANS4'         ANS VERSION 4           \n*        DC    C'VSR1'         OS/VS COBOL             \n*        DC    C' C2 '         COBOL/II                \n*        DC    C' C3 '         COBOL/370               \n*        DC    C'CMVS'         COBOL FOR MVS AND VM    \n*        DC    C'C390'         COBOL FOR OS/390        \n***********************************************************\nXITCMPID DS    CL8             COMPILER ID            \n         DS    CL1             FILLER                  \nXITCREL  DS    CL3             COMPILER RELEASE         \n         DS    CL3             FILLER                  \nXITCDATE DS    CL8             COMPILE DATE           \n         DS    CL3             FILLER                  \nXITCTIME DS    CL8             COMPILE TIME            \nXITOPTIM DS    CL6             OPTIMIZER              \n 206", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d2a43090449b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n         DS    CL1             FILLER                  \nXITOPREL DS    CL3             OPTIMIZER RELEASE       \nXITD     DS    CL1             DTECT                   \nXITP     DS    CL1             PFLOW                  \nXITC     DS    CL1             XCOUNT                  \nXITX     DS    CL1             XTIME                   \nXITF     DS    CL1             FDCHECK                 \nXITS     DS    CL1             SUBRNGCK                \nXITR     DS    CL1             PARMCHK                 \nXITB     DS    CL1             DBGSLEEP                \nXITW     DS    CL1             WSINIT                  \nXITI     DS    CL1             CICS                    \nXITE     DS    CL1             EOS                     \nXITL     DS    CL1             WSCLEAR                 \nXITH     DS    CL1             PUSHPOP                 \nXITO     DS    CL1             CASORT                 \n         DS    CL4             FILLER                   \nYou can use XNEWADDR to pass back a substitute print line.\nMRS expects the user program to pass a return code back in Register 15. When a return code 0 is passed back to MRS,\nprocessing continues as normal (the print line is output to SYSPRINT). When the return code is set to 8, MRS substitutes\nthe print line whose address is passed back to MRS in the return parameter list (XNEWADDR). When substituting a new\nprint line, specify a carriage control character in column 1. The total line length, including the carriage control, must be 133\nbytes. An error message replaces the normal print line for any other return code.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d2a43090449b-1", "text": "bytes. An error message replaces the normal print line for any other return code.\nThe MRS branches to the user program one final time after processing the entire library. The XDATADDR parameter\naddresses binary zeros in all of the data fields as a signal to the user program to close any open files. A system abend\ncan occur if open files are not closed.\nAccess Non-COBOL CSECTs (NOCOBEX)\nNOCOBEX provides access to every non-COBOL CSECT in the library, except for the COBOL ILBOxxxx and IGZ xxxxx\nroutines in COBOL load modules.\nMRS loads a copy of the specified user program if you specify this exit in the JCL (see Invoke a User Exit JCL). Each time\nMRS processes a non-COBOL CSECT, a branch is made and the CSECT data is passed to the user program using a\nparameter list pointed to by Register 1. The list contains one address:\nXDATADDR DS AL1(128),AL3 \nXDATADDR contains the address of the CSECT data being passed. This DSECT shows the order in which the data\nappears:\nXDATA       DSECTXMNAME      DS      CL8      LOAD MODULE NAME\nXMSIZE      DS      PL5      LOAD MODULE SIZE\nXPNAME      DS      CL8      PROGRAM (CSECT) NAME\nXPSIZE      DS      PL5      PROGRAM (CSECT) SIZE\nXCOBONLY    DS      CL76     FOR FUTURE USE \nMRS does not expect a return code from the NOCOBEX user program. MRS branches to the user program one final time\nafter processing the entire library. The XDATADDR parameter addresses binary zeros in all of the data fields as a signal to", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d2a43090449b-2", "text": "the user program to close any open files. A system abend can occur if open files are not closed.\n 207", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "91bb2b0f554b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSample User Exit Program\nThe following Assembler program shows how you can use NOCOBEX to print your own detail report for non-COBOL\nCSECTs.\nASMEXIT  TITLE 'MRS EXIT ROUTINE FOR NON COBOL CSECTS (NOCOBEX)'\nASMEXIT  CSECT\n         STM   14,12,12(13)\n         LR    12,15\n         USING ASMEXIT,12\n         LA    2,SAVE                  PERFORM SAVE AREA CHAINING\n         ST    13,4(,2)                 BETWEEN MRS AND ASMEXIT.\n         ST    2,8(,13)\n         LR    13,2 \n         L     10,0(,1)                GET DATA POINTER AND SET UP\n         USING INLINE,10                ADDRESSABILITY FOR DATA AND\n         LA    11,BUFFER                 OUTPUT BUFFERS.\n         USING OUTLINE,11\n         MVI   OUTLINE,X'40'           CLEAR OUTPUT LINE\n         MVC   OUTLINE+1(132),OUTLINE\n         CLI   INMOD,C'A'              CHECK FOR VALID DATA BUFFER.\n         BL    ALLDONE                  - IF NOT VALID THEN DONE.\n         TM    FLAGS,PASS1             CHECK FOR 1ST ENTRY TO ASMEXIT.\n         BZ    GETCSECT                 - IF 1ST ENTRY OPEN SYSRPT.\n         OPEN  (OUTDCB,(OUTPUT))\n         PUT   OUTDCB,HEADLINE         OUTPUT HEADER LINE.\n         NI    FLAGS,X'FF'-PASS1       RESET 1ST PASS FLAG.\nGETCSECT DS    0H\n         AP    TOTCSIZE,INCSIZE        ADD CSECT SIZE TO TOTALS.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "91bb2b0f554b-1", "text": "MVC   OUTCSECT,INCSECT        MOVE CSECT NAME TO OUT BUFFER.\n         MVC   EDITBUF,PATTERN         EDIT CSECT SIZE INTO BUFFER.\n         ED    EDITBUF,INCSIZE\n         MVC   OUTCSIZE,EDITBUF+4\n         CLC   INMOD,CURRMOD           CHECK FOR NEW MODULE NAME.\n         BE    WRITEREC                 - IF NEW THEN GET NEW DATA.\nGETMOD   DS    0H\n         AP    TOTMSIZE,INMSIZE        ADD NEW MODULE SIZE TO TOTALS.\n         MVC   OUTMOD,INMOD            MOVE MODULE NAME TO OUT BUFFER.\n         MVC   EDITBUF,PATTERN         EDIT MODULE SIZE INTO BUFFER.\n         ED    EDITBUF,INMSIZE\n         MVC   OUTMSIZE,EDITBUF+4 \n         MVC   CURRMOD,INMOD\nWRITEREC DS    0H\n         PUT   OUTDCB,OUTLINE          OUTPUT THIS RECORD TO SYSPRT.\n         B     RETURN                  RETURN TO MRS.\nALLDONE  DS    0H\n         MVC   BUFFER,TOTLINE          MOVE SKELETON LINE TO BUFFER\n         MVC   EDITBUF,PATTERN         EDIT TOTAL MODULE SIZE INTO\n         ED    EDITBUF,TOTMSIZE         OUTPUT BUFFER.\n         MVC   OUTMSIZE,EDITBUF+4\n         MVC   EDITBUF,PATTERN         EDIT TOTAL CSECT SI<E INTO\n         ED    EDITBUF,TOTCSIZE         OUTPUT BUFFER.\n         MVC   OUTCSIZE,EDITBUF+4\n         PUT   OUTDCB,OUTLINE            SPACE AND OUTPUT TOTALS.\n 208", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4ddc58f01f25-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n         CLOSE (OUTDCB)                CLOSE SYSRPT FILE.\nRETURN   DS    0H\n         L     13,4(,13)               RESTORE SAVE AREA ADDRESS.\n         LM    14,12,12(13)            RESTORE REGISTERS FOR MRS.\n         XR    15,15                   SET ZERO RETURN CODE.\n         BR    14                      RETURN TO MRS.\n*\n \n*   LITERALS, CONSTANTS AND VARIABLES FOR ASMEXIT\n*\n         LTORG\nSAVE     DC    18F'0'                  REGISTER SAVE AREA\nCURRMOD  DC    CL8' '                  CURRENT LOAD MODULE NAME\nTOTMSIZE DC    PL5'0'                  TOTAL MODULE SIZE (BYTES)\nTOTCSIZE DC    PL5'0'                  TOTAL CSECT SIZE (BYTES)\nEDITBUF  DC    XL12'00'\nPATTERN  DC    XL12'402020206B2020206B202020'\nFLAGS    DC    AL1(PASS1)\nPASS1    EQU   X'80'\nOUTDCB   DCB   DDNAME=SYSRPT,MACRF=PM,DSORG=PS,RECFM=F,LRECL=133,      X\n               BLKSIZE=133\nBUFFER   DC    CL133' '\nHEADLINE DC    CL133' MODULE    LENGTH          CSECT     LENGTH'\nTOTLINE  DC    CL133' TOTALS'\n*\n*   DSECT FOR OUTPUT BUFFER (SYSRPT)\n*\nOUTLINE  DSECT\nOUTCTL   DS    CL1                     CTL CHARACTER FOR OUTPUT\nOUTMOD   DS    CL8                     LOAD MODULE NAME\n         DS    CL2\nOUTMSIZE DS    CL8                     LOAD MODULE SIZE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4ddc58f01f25-1", "text": "DS    CL2\nOUTMSIZE DS    CL8                     LOAD MODULE SIZE\n         DS    CL8\nOUTCSECT DS    CL8                     CSECT NAME\n         DS    CL2\nOUTCSIZE DS    CL8                     CSECT SIZE\n         DS    CL2\nOUTXTRA  DS    CL76                    NOT USED\n*\n*   INPUT DATA FROM MRS (CSECT/MODULE INFORMATION)\n*\nINLINE   DSECT\nINMOD    DS    CL8                     MODULE NAME\nINMSIZE  DS    PL5                     MODULE SIZE\nINCSECT  DS    CL8                     CSECT NAME\nINCSIZE  DS    PL5                     CSECT SIZE\nINXTRA   DS    CL76                    NOT USED\n         END   ASMEXIT \nInvoke a User Exit JCL\nTo invoke a user exit, code the PARM parameter on the EXEC statement.\n 209", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "79a96b9296ba-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCOBOLEX and NOCOBEX are keyword parameters that require the name of the designated user program as a value.\nSpecify the user exits separately or concurrently.\nIf you are using a cataloged procedure, code the PARM parameter as follows:\n //STEP10 EXEC CAIMRSII,LIBRARY='COBOL load library',\n//            PARM=('NOCOBEX= XXXXXXXX ,COBOLEX= YYYYYYYY ') \nInterTest for CICS User Exits\nThis article describes InterTest for CICS user exits.\nUnprotect Main Storage with User Exit IN25LETX\nIN25LETX is an optional exit program coded by the user that specifies areas in main storage that should not  be protected\nby InterTest for CICS. The areas to be unprotected are indicated by beginning and ending storage addresses.\nThis exit program provides a programmable function equivalent to the InterTest for CICS interactive LET option. This is a\nparticularly useful option, because frequently an application program is designed to modify a storage area that is protected\nby InterTest for CICS. Ordinarily when that happens, InterTest for CICS initiates an automatic breakpoint and halts the\nprogram's execution.\nIN25LETX must follow the rules for command-level programs. It executes within the task of the monitored application\nprogram, and must not do anything that would affect normal execution of the application. IN25LETX is invoked each time\nInterTest for CICS begins monitoring and also when it resumes monitoring, such as after a CICS command or after any\nkind of breakpoint.\nThe interface to IN25LETX is a CICS command level LINK with a COMMAREA. This allows a user's IN25LETX module to\nissue CICS SPI or API commands to locate key module addresses.\nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "79a96b9296ba-1", "text": "issue CICS SPI or API commands to locate key module addresses.\nNOTE\nThe interface permits IN25LETX to return a variable-length table of pairs to InterTest for CICS in a single pass.\nPrevious non-ESA versions of IN25LETX branched to InterTest for CICS for each address pair until all address\npairs were passed.\nIN25LETX COMMAREA\nThe following table contains the IN25LETX COMMAREA fields. See the section Sample IN25LETX Program for the\nCOMMAREA layout.\nCOMMAREA Field Length Primed By\nTable Address Fullword User\nMonitored Program 8 bytes InterTest for CICS\nApplication Registers Fullword InterTest for CICS\nTable Address\nThis field is set to zeros upon entry to the exit. InterTest for CICS assumes it was passed a valid table address\nif this field is modified. Leaving this field set to zeros causes InterTest for CICS to remove any address pairs\npreviously set by this exit for this task.\nMonitored Program\nContains the name of the program being monitored by InterTest for CICS at the time this exit was invoked.\n 210", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c38c07bb526a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nApplication Registers\nThe full word address of the 16-full word area containing the application's registers (0 to 15) that were saved just\nbefore the entry to this exit.\nLETX Table\nFor each area of main storage that is to be unprotected, IN25LETX stores a pair of addresses in a table (the LETX table).\nEach pair of addresses represents a from and a  to area of storage that will not be protected by InterTest for CICS if those\nareas are modified by the application. For example, if the area to be unprotected resides at address X'11AA2E0' and is\nX'2000' bytes long, the address pair is 11AA2E0 and 11AC2E0.\nThe last entry in the table must contain two full words of X'FFFFFFFF'.\nIn many cases, the declared addresses may only need to be unprotected for a particular CICS task or program execution.\nThus the logic of IN25LETX may need to consider the varying circumstances of execution, including the following tasks:\n\u2022Transaction identification\n\u2022Terminal identification\n\u2022Logical level of execution\n\u2022Program identification\nIN25LETX must deliver a full table of address pairs each time it is invoked. IN25LETX does not have to be reentrant,\nmeaning it can contain save areas and tables in which permanent addresses can be stored. There is no need to rebuild\nthe LETX table if the addresses do not change. In this case, a one-time routine can find the areas, build the LETX table,\nand save the table in the IN25LETX module for the next time. IN25LETX can make itself resident by loading itself again\n(see the section Sample IN25LETX Program).", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c38c07bb526a-1", "text": "(see the section Sample IN25LETX Program).\nIN25LETX can reside above or below the 16 MB line and execute in either addressing mode. All table addresses,\nhowever, must have the X'80000000' bit turned off; that is, the address X'01234567' must not be passed as X'81234567'.\nSample IN25LETX Program\nThe sample IN25LETX program that follows locates two areas, both permanently resident in storage, which are to be\nunprotected for all monitored programs running under transaction code ABCD. The first area is a table pointed to by\nan address in the user's TWA. The second area is a table loaded as a member of the CICS program definition named\nATABLE. Both areas are established before InterTest for CICS becomes active and remain resident in main storage.\n*\n         TITLE 'IN25LETX -- CA INTERTEST LET EXIT -- USER CODED'\n         DFHREGS                     REGISTER EQUATES\n*                                             \nDFHEISTG DSECT                       WORKING STORAGE DSECT         \nXPROGLEN DS    F                     PROGRAM LENGTH              \n****************************************************************  *       I N 2 5 L E T X    C O M M A R E A \n                    *\n**************************************************************** \nCOMMAREA DSECT                       COMMAREA                     \nCTBLADDR DS    F                     ADDRESS OF USER LET TABLE    \nINTPROG  DS    CL8                   NAME OF MONITORED PROGRAM    \nINTREGS  DS    F                     ADDR OF APPL REGISTERS (0-15) *                                         \n                       \nUSERTWA  DSECT                       DSECT FOR USER TWA           \nUTBLADDR DS    F                     ADDRESS OF USER TABLE        \nUTBLLEN  DS    H                     LENGTH OF USER TABLE          *                                         \n                         \n*****************************************************************\n 211", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e464a3d9d5ae-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIN25LETX DFHEIENT EIBREG=R11,CODEREG=R12,DATAREG=R13              \n*         L     R10,DFHEICAP         POINT TO COMMAREA\n         USING COMMAREA,R10                                      *                                           \n           \n         CLC   EIBTRNID,=C'ABCD'    IS THIS THE TRANSACTION?\n         BNE   RETURN               NO, RETURN, DO NOT SET ANY   \n*                                   ADDRESSES FOR THIS TASK      *                                           \n                      \nPROCESS  CLC   LTWATBL,=D'0'        HAVE THEY BEEN ALREADY SAVED?\n         BE    GETAREAS             NO, GO GET THEM     \n         LA    R1,LTABLE            THEN, THE LET TABLE IS BUILT...\n         ST    R1,CTBLADDR          PUT LET TABLE ADDR IN THE COMMAREA*                                       \n                            \nRETURN   EXEC CICS RETURN                                            *                                        \n                            \nGETAREAS DS    0H                                                    \n*\n         EXEC CICS ADDRESS TWA(R5)                                 \n         USING USERTWA,R5                                            *                                       \n                \n         L     R1,UTBLADDR           GET THE START OF THE TWA AREA\n         N     R1,=X'7FFFFFFF'       ENSURE HIGH-ORDER BIT IS TURNED\n*                                    OFF IN USER'S ADDRESS\n         ST    R1,LTWATBL           STORE THE AREA'S START ADDRESS\n         AH    R1,UTBLLEN           ADD THE TABLE LENGTH \n         ST    R1,LTWATBL+4         STORE THE AREA'S END ADDRESS   \n*\n         EXEC CICS INQUIRE PROGRAM('ATABLE') LOADPOINT(R0)           X\n                    LENGTH(XPROGLEN)                                  *", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e464a3d9d5ae-1", "text": "LENGTH(XPROGLEN)                                  *                                      \n                          \n         ST    R0,LPROGTBL           STORE THE AREA'S START ADDRESS\n         A     R0,XPROGLEN           ADD THE PROGRAM'S LENGTH \n         ST    R0,LPROGTBL+4         STORE THE AREA'S END ADDRESS      \n*                     \n**********************************************************************\n* LOAD THIS EXIT AGAIN SO IT WILL NOT HAVE TO REOBTAIN THE ADDRESSES * \n* ON THE NEXT CALL TO THIS EXIT.                                     * \n**********************************************************************\n         EXEC CICS LOAD PROGRAM('IN25LETX') HOLD                        *                                     \n                               \n         LA    R1,LTABLE\n         ST    R1,CTBLADDR           PUT ADDR OF LET TABLE IN COMMAREA\n         B     RETURN                                                  *                                      \n                                \nLTABLE   DS    0H                    LET TABLE                         \nLTWATBL  DC    2F'0'                 ADDRESSES OF TWA TABLE\nLPROGTBL DC    2F'0'                 ADDRESSES OF PROGRAM TABLE        \nLEND     DC    X'FFFFFFFF'           END OF TABLE INDICATOR           \n         LTORG                                                      \n         END \n 212", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a9d3ee4a55b9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDisable IN25LETX\nInterTest for CICS uses IN25LETX during all monitoring; that is, for all entries of the InterTest for CICS monitoring table. To\nprevent InterTest for CICS from executing IN25LETX, you must disable it or remove it from the program library.\nOnce a link to IN25LETX fails (because the program is disabled), InterTest for CICS will not try the link again, thus\navoiding much overhead. In such a case, the execution of IN25LETX will not resume until the next InterTest for CICS start.\nPassword Protection\nOnline password protection is an optional InterTest for CICS feature. You can disable it selectively by redefining the\npassword installation options CNTLSEC, CNTOSEC, MONOMSEC, CORSEC, and FILSEC. For instructions, see\nIN25OPTS Keywords.\nThe IN25SEC2 macro is used to assemble an InterTest for CICS load module that contains the passwords for the CORE\nfacility, FILE facility, and CNTL facility. The IN25SEC2 passwords are not stored anywhere in their unscrambled form. For\nsecrecy, you can code PRINT OFF in your IN25SEC2 assembly. The default passwords are as follows:\nMAIN\nCORE\n$FUN\nCNTL functions (commands)\n$OPT\nCNTL options\n$MNO\nCNTL options for segmented monitoring on and off (MON and NOM)\nFILE\nNo default\nPasswords can be changed at any time, even if someone is using the CORE or FILE facilities. Just run an IN25SEC2\nassembly with the new passwords. If the CICS system is active, enter the following command to put the new passwords\ninto effect:\nCEMT SET PROG(IN25SEC2) NEW\nRequired Parameters", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a9d3ee4a55b9-1", "text": "into effect:\nCEMT SET PROG(IN25SEC2) NEW\nRequired Parameters\nThe IN25SEC2 macro is delivered in the InterTest for CICS source code file and must be unloaded from the distribution\nfiles before the assembly job.\nIN25SEC2 TYPE=INITIAL,SCRNUM=(x,x,x,x)\nThe TYPE=INITIAL macro initiates the assembly and specifies the four numbers in the SCRNUM keyword that are to be\nused in your version of the scrambling algorithm. These numbers must be a value from 1 to 16, separated by commas,\nand enclosed in parentheses.\nThe TYPE=FINAL macro must be the last macro before the END statement. This macro must not contain any other\nparameters.\nBetween the TYPE=INITIAL and TYPE=FINAL macros, specify the IN25SEC2 macros to assign passwords to protected\nresources using the following keywords:\nNAME\nSpecifies the name of the resource.\nPASS\nSpecifies the four-character password for the resource. Only the characters A-Z, 0-9, $, @, and # are allowed.\n 213", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "35e45c773779-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSpecify Passwords for the CORE Facility\nThe macro for the CORE password is as follows:\nIN25SEC2 NAME=PROTCORE,PASS=xxxx\nNAME\nYou must specify PROTCORE.\nxxxx\nSpecifies the password.\nWhen a user of the CORE facility receives the message ENTER SECURITY PASSWORD, the user must enter the four-\ncharacter password. This password is then scrambled and compared with the scrambled password specified in the\nPASS= parameter. If the codes are equal, the CORE change is made and the password does not have to be entered\nagain during the same session. If the password is entered incorrectly, the CORE facility asks for it again.\nNOTE\nEven if the password is entered correctly, areas outside CICS storage cannot be modified.\nThe following IN25SEC2 macro, delivered with the pregenerated version of InterTest for CICS, protects all storage not\nowned by a user's task:\nIN25SEC2 NAME=PROTCORE,PASS=MAIN\nPROTCORE\nSpecifies that this entry is for the CORE transaction.\nMAIN\nThe default password. To change or remove this password, update or remove the above macro and reassemble\nthe IN25SEC2 program.\nSpecify Passwords for Files and DL/I Databases\nThe macros for the FILE facility are:\nIN25SEC2    NAME=yyyyyyyy,PASS=xxxx            WRITE only\nIN25SEC2    NAME=yyyyyyyy,PASS=xxxx,FPROT=YES  READ and WRITE\nyyyyyyyy\nSpecifies the name of the file ID (from the CICS file definition) or the DBD identification.\nxxxx\nSpecifies the password.\nFPROT=YES\nIndicates that the file or DBD name should also be fetch protected; that is, data cannot be viewed or changed\nunless the password is correctly entered.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "35e45c773779-1", "text": "unless the password is correctly entered.\nYou must code one IN25SEC2 macro for every file or DBD name you want to protect; files or DBDs not named in a macro\nare not password protected against unauthorized use. These passwords apply only to access through the InterTest for\nCICS FILE facility.\nWhen a user of the FILE facility receives the message ENTER SECURITY PASSWORD, the user must enter the four\ncharacter password. This password is then scrambled and compared with the scrambled password specified in the\nPASS= parameter. If the codes are equal, the specified FILE or DBD is accessed. If the password is entered incorrectly,\nthe FILE facility terminates.\nYou can code an IN25SEC2 macro to protect all files and DBD names that are not specifically protected in individual\nIN25SEC2 macros.\n 214", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1ae001637826-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe following example password protects FILEA against both reads and writes with the password ASEC, password\nprotects FILEB against writes only with the password BSEC, and password protects all other files against both reads and\nwrites with the password FSEC.\nIN25SEC2    NAME=PROTFILE,PASS=FSEC,FPROT=YES   \nIN25SEC2    NAME=FILEA,PASS=ASEC,FPROT=YES  \nIN25SEC2    NAME=FILEB,PASS=BSEC    \nNOTE\nAny security measures of your CICS installation are applied by CICS or the operating system after InterTest for\nCICS password protection is satisfied. The FILE facility functions as an application within CICS.XE \"DL/I\".\nSpecify Passwords for CNTL Commands and Options\nPassword protection is available for certain CNTL commands and monitoring options.\nTo use InterTest for CICS to protect other commands and options or not protect the ones listed here, contact Broadcom\nSupport .\nCNTL password protection does not apply to the following situations:\n\u2022Automatic startup of InterTest for CICS from the table assembled from InterTest for CICS PROMMAC macros.\n\u2022CNTL=RESTART command.\n\u2022CNTL=NEW command.\n\u2022CNTL=EXEC command.\n\u2022Startup of InterTest for CICS by the IN25PLT program in the PLT table.\n\u2022Execution of a CNTL command from a CRLP terminal; that is, a simulated terminal consisting of input and output\nsequential files.\n\u2022Execution of a CNTL command from the system console.\nYou do not need passwords in these situations because they either automatically start InterTest for CICS, which is\ncontrolled by the system programming staff, or reestablish functions that were password protected when they were\noriginally requested.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1ae001637826-1", "text": "originally requested.\nPassword Protected CNTL Commands\nThe following commands are password protected by default if you use the pregenerated version of InterTest for CICS.\nCNTL=CKPT\nStart and end checkpoint\nCNTL=END\nRemove InterTest for CICS from CICS\nCNTL=EXCL\nEnter a program, transaction, or terminal in the Exclusion Table to prevent monitoring\nCNTL=INCL\nRemove a program, transaction, or terminal from the Exclusion Table\nCNTL=ABP\nActivate and deactivate the global automatic breakpoint facility\nCNTL=PURGE\nStart and end the purging of tasks that remained at a breakpoint longer than the specified time\nCNTL=GLOG\nStart and end logging of CNTL commands and CORE changes\n 215", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e5db7dd37639-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCNTL=ON,PROG=.ALL\nDeclare monitoring for all application programs not specifically declared for monitoring\nCNTL=OFF,PROG=.ALL\nRemove monitoring of all application programs not specifically declared for monitoring\nCNTL=ON,PROG=.ALL\nAdd monitoring options for all applications not specifically declared for monitoring\nCNTL=ALL\nDeclare and remove monitoring for all applications not specifically declared for monitoring\nCNTL=OFF\nRemoves monitoring options\nThis command is password protected only to the extent that the option to be removed is password protected.\nThe following IN25SEC2 macro, delivered with the pregenerated version of InterTest for CICS, protects all of the\npreviously listed CNTL commands:\nIN25SEC2 NAME=PROT$FUN,PASS=$FUN\nPROT$FUN\nIdentifies the CNTL commands listed previously. To change or remove this password, update or remove the\nabove macro and reassemble the IN25SEC2 program.\nDefault:  $FUN\nPassword Protected CNTL Options\nThe following monitoring options are password protected by default; that is, if you use the pregenerated version of\nInterTest for CICS. You can disable password protection for these CNTL options by redefining the InterTest for CICS\ninstallation option CNTOSEC.\n,BYP\nBypass storage protection or monitoring of BALR 14,15 and BALR 14,14 routines (for XA, BASSM, and BASR)\n,CSA=(offset,length)\nDo not protect specified areas of the CSA or CWA\n,LET=name\nDo not protect storage occupied by a specified program module\n,LET=(address,length)\nDo not protect a specified storage area\n,MON=location\nSet segmented monitoring on\n,NOM=location\nSet segmented monitoring off\n,OVR=errcode", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e5db7dd37639-1", "text": "Set segmented monitoring on\n,NOM=location\nSet segmented monitoring off\n,OVR=errcode\nDisregard an error condition that would typically cause a breakpoint\n,STR=ON\nPreserve a copy of the CICS Trace Table for the duration of a breakpoint\n,TON=*\nor ,TON=terminal\nLimit monitoring to a specific terminal\n,USH=ON\nRemove storage protection from storage areas in the shared subpool\n 216", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "626d645a8ccd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPROT$OPT Name Option\nThe following IN25SEC2 macro, delivered with the pregenerated version of InterTest for CICS, protects all of the\npreviously listed CNTL options except MON and NOM:\nIN25SEC2 NAME=PROT$OPT,PASS=$OPT\nPROT$OPT\nIdentifies the password protected CNTL options.\n$OPT\nThe default password. To change or remove this password, update or remove the above macro and reassemble\nthe IN25SEC2 program.\nPROT$MNO Name Option\nThe following IN25SEC2 macro, delivered with the pregenerated version of InterTest for CICS, protects the segmented\nmonitoring functions (MON and NOM) when MONOM=MENU or NOMENU, and MONOMSEC=YES:\nIN25SEC2 NAME=PROT$MNO,PASS=$MNO\nPROT$MNO\nIdentifies the CNTL options MON and NOM.\n$MNO\nThe default password. To change or remove this password, update or remove the above macro and reassemble\nthe IN25SEC2 program.\nSample IN25SEC2 Assembly JCL\nSample JCL member CCSASEC2 is provided in CAI.CAVHJCL. Customize the member and submit it to assemble your\npassword table.\nThe following example demonstrates the macro usage:\n\u2022The CORE password is changed to CORE.\n\u2022All files except FILE1 and FILE2 are WRITE protected with the password FSEC.\n\u2022FILE1 will be READ and WRITE protected with password WXYZ.\n\u2022FILE2 will be WRITE protected with password ABCD.\n\u2022CNTL commands and monitoring options are protected with the password CNTL.\n//ASM.SYSIN DD *\n  IN25SEC2 TYPE=INITIAL,SCRNUM=(1,1,1,1)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "626d645a8ccd-1", "text": "IN25SEC2 NAME=PROTCORE,PASS=CORE\n  IN25SEC2 NAME=PROTFILE,PASS=FSEC\n  IN25SEC2 NAME=FILE1,PASS=WXYZ,FPROT=YES \n  IN25SEC2 NAME=FILE2,PASS=ABCD\n  IN25SEC2 NAME=PROT$FUN,PASS=CNTL\n  IN25SEC2 NAME=PROT$OPT,PASS=CNTL\n  IN25SEC2 TYPE=FINAL  END /*\nSymDump  for CICS User Exits\nThis article describes SymDump  for CICS user exits.\n 217", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "63370923c895-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nGlobal User Exit XDUREQ\nSymDump  for CICS uses the CICS global user exit XDUREQ. If other products at your site that use this same exit, you\nwill not have to modify SymDump  for CICS. However, be aware of the following points:\n\u2022The exit modules get control in the order in which they are enabled. If another product uses the XDUREQ exit and is\nenabled before SymDump  for CICS at PLT time, that product may change the storage associated with the abending\ntransaction. SymDump  for CICS does not modify task storage and is transparent to exit modules that are invoked after\nit has processed.\n\u2022The SymDump  for CICS IN25INST program should always be placed after the InterTest for CICS IN25PLT program in\nthe PLT.\n\u2022A return code from the XDUREQ global exit tells CICS whether to take the dump after the exit has processed it. If there\nare multiple exits and they pass different return codes, CICS ignores the return codes and processes the dump as if a\nnormal return code were returned. This means that if SymDump  for CICS and another product using the XDUREQ exit\ndisagree about CICS taking its own dump, CICS takes the dump anyway.\nConfigure SymDump for CICS Security\nSecure SymDump  for CICS\nYou can secure access to SymDump  for CICS facilities by:\n\u2022Transaction-level security\n\u2022Menu-level security\n\u2022Dump-level security\nTransaction Level Security\nYou can apply transaction-level security to the SymDump  for CICS transaction IDs using your site's external security\npackage, such as Top Secret, ACF2 , or IBM RACF. Transaction-level security applies when the user enters the\ntransaction ID directly from CICS.\nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "63370923c895-1", "text": "transaction ID directly from CICS.\nNOTE\nApplying transaction-level security does not secure menu access to the equivalent functions. You may need to\nsecure both.\nThe following table contains SymDump  for CICS transaction IDs:\nTransaction ID Function IN25OPTS Keyword\nSYMD SymDump  Primary Option menu SYMDT\nSYME Terminate (End) SymDump  capture\nSYMI Configure SymDump\nSYMS Start SymDump  capture facility\nSYMT Capture a CICS internal trace\nNOTE\nTo increase transaction-level security, we recommend that you restrict the transaction SYMD  to the following\nroles:\n\u2022CICS sysprogs\n\u2022Application failure analysts\nYour site may have changed the transaction IDs using IN25OPTS. Use the VRPT transaction to display the current values\nonline.\n 218", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "de5969d6b90b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMenuLevel Security\nYou can secure menu access to SymDump  for CICS functions by using your site's external security package and the\nExternal Security Facility. Menu access applies whenever the user accesses the SymDump  for CICS Primary Option\nmenu from CICS (SYMD transaction) or from InterTest for CICS (ITST Option 5).\nDumpLevel Security\nYou can use a user-written security exit to control access to specific dumps and traces from either the online display or the\nbatch print function. Dumps and traces meeting the criteria specified in the security exit are not displayed or printed.\nExternal Security Installation Option\nThe EXTSEC installation option in IN25OPTS turns the SymDump  for CICS external security feature on or off. When\nSymDump  for CICS is first installed, it is useful to leave EXTSEC set to No (the default) until the product is installed,\ntested, and the security rules written.\nFor more information about setting and modifying SymDump  for CICS options, see IN25OPTS Keywords.\nResource Protection Levels\nThe resources protected in SymDump  for CICS under the External Security feature are listed in the table below:\nClass Entity Access Level Function Type SymDump  Menu\nOptions\nCA@NTSYM BQUSER Read User 1 Analysis (View dumps\nand traces)\nCA@NTSYM BQUSER Update Privileged user 1 Analysis (View plus\nHold, Release, Delete)\nCA@NTSYM BQTRACE Update Trace authority 2 Trace capture\nCA@NTSYM BQADMIN Update Administrator 3 Configuration\nCA@NTSYM BQOPER Update Operator 4 Start\n5 Stop\nCA@NTSYM BQLSCRN Update Last screen display", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "de5969d6b90b-1", "text": "5 Stop\nCA@NTSYM BQLSCRN Update Last screen display\nBQUSER  with Read access lets the user access SymDump  for CICS menu option 1, Dump Analysis. The user can view\nthe list of dumps and traces, and then select individual dumps or traces to view. This user cannot hold, release, or delete\ndumps or traces.\nBQUSER  with Update access lets the user fully use SymDump  for CICS menu option 1, Dump Analysis. This user can\nview the list of dumps and traces, select individual dumps or traces to view, and hold, release, and delete individual\ndumps or traces.\nBQTRACE  lets the user access SymDump  for CICS menu option 2, Trace. This allows the user to request a CICS internal\ntrace for later analysis. To view the trace, the user must also have BQUSER access with at least Read authority.\nBQADMIN  lets the user access SymDump  for CICS menu option 3, Configuration. The administrator has access to the\nSymDump  for CICS Configuration panel and the ability to set options for running SymDump  for CICS.\nBQOPER  lets the user access SymDump  for CICS menu options 4 and 5, which Start and Stop the SymDump  for CICS\ncapture facility, respectively.\nBQLSCRN lets the user select the Last Screen display from the Dump Tree.\nTo set up external security for your environment, continue by following the directions in the appropriate section:\n 219", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "009731d104da-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nExternal Security Using Top Secret\nThe external security interface in SymDump  for CICS is compatible with Top Secret 4.2 or above.\nSymDump  for CICS always performs its functions under the control of CICS. Therefore, no special definition of SymDump\nfor CICS as a unique facility is required.\nDefine the Resource Class CA@NTSYM\nSymDump  for CICS uses a unique resource class, CA@NTSYM, for its internal security controls.\nList a Resource Class\nTo determine if CA@NTSYM is currently defined to your Top Secret system, issue the following command:\nTSS LIST(RDT) RESCLASS(CA@NTSYM)\nThis command lists the definition of the CA@NTSYM resource in the Top Secret Resource Definition Table (RDT).\n\u2022If CA@NTSYM is present and its definition matches the attributes below, no further action is required:\nACLST(UPDATE=6000,READ) DEFACC(READ)\n\u2022If any of the attributes do not match, you must change the definition using the TSS REPLACE(RDT) command,\nspecifying the correct parameters.\n\u2022If you get an error message indicating that the resource is missing, invalid, or reserved, you must define it.\nIf CA@NTSYM is not defined, you must add it to the RDT. New classes are added using the TSS command ADDTO\nfunction through any facility supporting the TSS command. Once added, these resources become a permanent part of the\nsecurity file and can be immediately administered and reported on by name.\nAdd a Resource Class\nThe syntax to add the CA@NTSYM resource is shown next. The syntax uses a RESCODE of 38. This code value is up to\neach site and must be unique. Codes 01 to 3F are available.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "009731d104da-1", "text": "each site and must be unique. Codes 01 to 3F are available.\nTSS ADDTO(RDT) RESCODE(38) RESCLASS(CA@NTSYM) -\n    ACLST(UPDATE=6000,READ) DEFACC(READ)    \nOnce you define the resource CA@NTSYM to your system, you can establish access controls to SymDump  for CICS\nfunctions and information. No IPL, re-initialization, or parameter changes are needed for these changes to become active\nand permanent.\nUse CA@NTSYM to Control SymDump  for CICS Functions\nThe CA@NTSYM resource controls all SymDump  for CICS functions. CA@NTSYM is a standard short resource and is\nmanaged in the same manner as other access level resources. For a definition of the access levels by entity name, see\nResource Protection Levels.\nTo define the SymDump  for CICS functions to Top Secret, use the following command:\nTSS ADDTO(deptname)- \nCA@NTSYM(BQUSER,BQTRACE,BQADMIN,BQOPER, BQLSCRN)\nNOTE\nNotice that all entity names start with BQ to uniquely identify them as SymDump  for CICS commands. The rest\nof the entity name identifies its function, USER, TRACE, ADMIN, OPER(ator) or Last Screen Display.\n 220", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bb94aab65aeb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDefine User Access to BQ Functions\nTo allow user USER01 to have Read access to Option 1 of the SymDump  for CICS menu to analyze a dump or trace, use\nthe following command:\nTSS PERMIT(USER01) CA@NTSYM(BQUSER)   ACCESS(READ)\nTo allow user USER02 to have full (update) access to Options 1 and 2 of the SymDump  for CICS menu to view, hold,\nrelease, and delete dumps and traces, and to capture a trace, use the following commands:\nTSS PERMIT(USER02) CA@NTSYM(BQUSER)   ACCESS(UPDATE)\nTSS PERMIT(USER02) CA@NTSYM(BQTRACE)  ACCESS(UPDATE)\nTo allow user USER99 to access all functions of SymDump  for CICS:\nTSS PERMIT(USER99) CA@NTSYM(BQUSER)   ACCESS(UPDATE)\nTSS PERMIT(USER99) CA@NTSYM(BQTRACE)  ACCESS(UPDATE)\nTSS PERMIT(USER99) CA@NTSYM(BQADMIN)  ACCESS(UPDATE)\nTSS PERMIT(USER99) CA@NTSYM(BQOPER)   ACCESS(UPDATE)\nIf you omit the ACCESS keyword, Top Secret defaults the PERMIT to Read access.\nExternal Security Facility\nSymDump  for CICS external security provides menu-accessed resource protection and control through the use of your\nsite's external security package, such as Top Secret, ACF2 , or IBM RACF. The external security option provides security\nfor the following:\n\u2022Protection for the configuring, starting, and stopping of SymDump  for CICS through SymDump  for CICS menu options\n3, 4, and 5, respectively", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bb94aab65aeb-1", "text": "3, 4, and 5, respectively\n\u2022Protection for viewing, holding, releasing, and deleting dumps through SymDump  for CICS menu option 1\n\u2022Control over whom is able to capture a CICS internal trace through SymDump  for CICS menu option 2\nSymDump  for CICS checks authorization at the time of access, rather than checking authorization at signon. This enables\nyour site to track security violations.\nProtecting menu access to SymDump  for CICS functions does not secure direct access to the same functions using a\nCICS transaction ID. To do this, you must secure the equivalent transaction IDs as discussed in Securing SymDump  for\nCICS.\nExternal Security Using ACF2\nThe external security interface in SymDump  for CICS is compatible with ACF2  6.2 or higher.\nDefine the Resource Class CA@NTSYM\nSymDump  for CICS uses a unique resource class, CA@NTSYM, for its internal security controls. CA@NTSYM needs to\nbe defined to ACF2  with its own three-character resource type. In the following example, CA@NTSYM is defined using\nthe resource type CAM.\nSET CONTROL(GSO) INSERT CLASMAP.CA@NTSYM -\nRESOURCE(CA@NTSYM) RSRCTYPE(CAM) ENTITYLN(8)\nAfter adding this clasmap definition, you must refresh the GSO clasmap.\nTo protect and allow access to SymDump  for CICS, use the standard ACF2  rule writing, as shown below:\n 221", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dd46e06302f8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSET RESOURCE(CAM)\nCOMPILE *\n$KEY(entity) TYPE(CAM)\nUID(uidstring/mask) SERVICE(READ/READ,UPDATE/UPDATE) -\n    ALLOW/LOG/PREVENT\nEND\nSTORE *\nIf the SERVICE keyword is not supplied, ACF2  defaults to permit access to all service levels.\nOnce the resource CA@NTSYM is defined to your system, you can establish access controls to SymDump  for CICS\nfunctions and information.\nUse CA@NTSYM to Control SymDump  for CICS Functions\nThe CA@NTSYM resource controls all SymDump  for CICS functions. For a definition of the access levels by entity name,\nsee Resource Protection Levels.\nNOTE\nNotice that all entity names start with BQ to uniquely identify them as SymDump  for CICS commands. The rest\nof the entity name identifies its function, USER, TRACE, ADMIN, or OPER(ator).\nTo enable CICS functions, use the following comments in the order listed:\n1.Define access for CA@NTSYM:\nSet RESOURCE(CAM)\nCOMPILE *\n2.Define access for SymDump  for CICS analysis:\n$KEY(BQUSER) TYPE(CAM)\n3.Set general user read-only access:\nUID(general user UID) SERVICE(READ) ALLOW\n4.Set privileged user read and update access:\nUID(privileged user UID) SERVICE(READ,UPDATE) ALLOW\n5.Define access for SymDump  for CICS tracing:\n$KEY(BQTRACE) TYPE(CAM)\nUID(tracing user UID) SERVICE(UPDATE) ALLOW\n6.Define access for SymDump  for CICS Administration:\n$KEY(BQADMIN) TYPE(CAM)\nUID(admin user UID) SERVICE(UPDATE) ALLOW", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dd46e06302f8-1", "text": "UID(admin user UID) SERVICE(UPDATE) ALLOW\n7.Define access for SymDump  for CICS operator:\n$KEY(BQOPER) TYPE(CAM)\nUID(operator user UID) SERVICE(UPDATE) ALLOW\nEND\nSTORE *\nExternal Security Using IBM RACF\nThe external security interface in SymDump  for CICS can be used with RACF. It is compatible with all supported versions\nof Common Components and Services  for z/OS.\n 222", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f9168fdfbe86-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nRequired RACF Table Entries\nBefore implementing RACF security, you must define a new class for SymDump  for CICS (CA@NTSYM) in the Class\nDescriptor Table, update the Router Table for the new class, and then enable the class. These steps are detailed next.\n1.Class Descriptor Table (CDT) Entry for CA@NTSYM\nDefine a new class, CA@NTSYM, for SymDump  for CICS security in the RACF Class Descriptor Table (module\nICHRRCDE). The following information should be included in the ICHERCDE macro entry:\nMAXLNTH=8, FIRST=ALPHANUM, OTHER=ALPHANUM.\nNOTE\nNo recommendations are given for any DFTUACC; this is completely determined by each site.\n2.Router Table Entry for CA@NTSYM\nMake an entry for the CA@NTSYM class in the RACF Router Table (module ICHRFR01). Specify ACTION=RACF.\nThis entry is generated by the ICHRFRTB macro.\n3.Enabling the Class CA@NTSYM\nActivate the new class CA@NTSYM just defined in the CDT and Router Table. To do this, issue the following\ncommand:\nSETROPTS CLASSACT(CA@NTSYM)\nProtect SymDump  for CICS Entities\nThe CA@NTSYM resource controls all SymDump  for CICS functions. For a definition of access levels by entity name, see\nResource Protection Levels earlier in this section.\nNOTE\nNotice that all entity names begin with BQ to uniquely identify them as SymDump  for CICS commands. The rest\nof the entity name identifies its function, USER, TRACE, ADMIN, or OPER(ator).\nIssue RACF RDEFINES for SymDump  for CICS Entities", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f9168fdfbe86-1", "text": "Issue RACF RDEFINES for SymDump  for CICS Entities\nFirst, you must issue the RACF RDEFINE command for every SymDump  for CICS entity that you want to protect. For\nexample, issue the following commands to protect the CA@NTSYM resources:\nRDEFINE CA@NTSYM BQUSER UACC(NONE)\nRDEFINE CA@NTSYM BQTRACE UACC(NONE)\nRDEFINE CA@NTSYM BQADMIN UACC(NONE)\nRDEFINE CA@NTSYM BQOPER UACC(NONE)\nGive all entities a universal access of NONE. Defining this security type denies access to anyone that does not have\nauthorization.\nPermit the Use of CA@NTSYM Entities\nOnce you protect the entities, use the PERMIT command to give different levels of access to individual users for separate\nSymDump  for CICS functions. For example:\n\u2022Define a general user with read-only access to the analysis panels by issuing:\nPERMIT BQUSER CLASS(CA@NTSYM) ID(userid) ACCESS(READ)\n\u2022Define a privileged user with read and update access to the analysis panels by issuing:\n 223", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "479ebf41e348-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPERMIT BQUSER CLASS(CA@NTSYM) ID(userid) ACCESS(READ,UPDATE)\n\u2022Define access for SymDump  for CICS trace capture function by issuing:\nPERMIT BQTRACE CLASS(CA@NTSYM) ID(userid) ACCESS(UPDATE)\n\u2022Define access for SymDump  for CICS administration (configuration panel) by issuing:\nPERMIT BQADMIN CLASS(CA@NTSYM) ID(userid) ACCESS(UPDATE)\n\u2022Define access for SymDump  for CICS operator (start and stop functions) by issuing:\nPERMIT BQOPER CLASS(CA@NTSYM) ID(userid) ACCESS(UPDATE)\nSecurity Exit Facility\nSymDump  for CICS provides an optional security exit facility. This is an alternative to using the External Security Facility.\nThe security exit facility allows a user-written security exit to control access to dumps from the online dump display\nfunction and the batch print function.\nThe security exit receives control during online and batch processing when dumps that meet specified selection criteria\nare found. In effect, the security check is another selection criterion. No security violation message appears; instead,\ndumps for which the user is not authorized are not shown.\nBoth online and batch exits are optional and can be written in Assembler, COBOL, or PL/I. The SymDump  for CICS SMP\ntarget libraries contain sample COBOL and Assembler exit programs in both source and load form. PL/I samples are not\nprovided.\nActivate the Exit Facility\nTo activate the exit facility, you need only provide an active CICS exit module named IN25XC1 and an active batch exit\nmodule named IN25XB1.\nUse the following example to activate the CICS Assembler sample exit.\nFollow these steps:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "479ebf41e348-1", "text": "Use the following example to activate the CICS Assembler sample exit.\nFollow these steps:\n1.Rename supplied load module IN25XC1A to IN25XC1.\n2.Restart your CICS region or bring in new copies of IN##XCMR and IN25XC1, where ## specifies your two-digit CICS\nrelease number (for example, 66 for CICS 4.1, 67 for CICS 4.2, 68 for CICS 5.1, 69 for CICS 5.2, 70 for CICS 5.3, and\n71 for CICS 5.4).\nUse the following example to activate the batch Assembler sample exit.\nFollow these steps:\n1.Rename supplied load module IN25XB1 to IN25XB1D.\n2.Rename supplied load module IN25XB1A to IN25XB1.\n3.Submit your execution JCL for the batch dump print program IN##PDMP where ## specifies your two-digit CICS\nrelease number (for example, 66 for CICS 4.1, 67 for CICS 4.2, 68 for CICS 5.1, 69 for CICS 5.2, 70 for CICS 5.3, and\n71 for CICS 5.4). Sample JCL for execution of this program is member SYMPDMP in the CAVHJCL library.\nIf you do not want to install the exits immediately, you can leave the exit load modules. The user exit manager for CICS\nhandles not finding the exit. The user exit manager for batch uses the dummy module provided.\nThe SymDump  load library contains the following modules related to the security exit:\nModule Description\nIN##XCMR SymDump  CICS user exit manager\n 224", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bb51800b4f7a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIN25XBMR SymDump  batch user exit manager\nIN25XC1A Sample SymDump  CICS security user exit (Assembler)\nIN25XC1C Sample SymDump  CICS security user exit (COBOL)\nIN25XB1A Sample SymDump  batch security user exit (Assembler)\nIN25XB1C Sample SymDump  batch security user exit (COBOL)\nIN25XB1 SymDump  batch security user exit (dummy stub)\nThe CAVHSAMP target library also provides source code for the sample user exits.\nTest the Exit Facility\nThe samples are set up to allow access to dumps with the seconds in the time field less than 30, and to disallow the\nothers. Try accessing dumps first without the exits, and then rename the sample exits to the proper names and try\naccessing dumps again (be sure to bring in new copies of IN##XCMR and IN25XC1 first). Fewer dumps are allowed to\nyou. Trying this verifies the basic functioning of the exits.\nOnline Dump Display\nThe CICS user exit is invoked separately for each dump. The exit gets control through a standard Command Level link\nand is passed a COMMAREA. This COMMAREA contains:\n\u2022A field containing the total length of the area\n\u2022A return code field\n\u2022Product and function identification fields\n\u2022All the identification data for the dump as shown on the Dump/Trace Analysis and Selection screens (such as CICS\napplid, CICS user ID, program, transaction ID, abend code, terminal ID, language, and date and time)\nThe copy member for the COMMAREA used by the exit is:\n\u2022SDMPXCMA for the Assembler exit\n\u2022SDMPXCMC for the COBOL exit\nBatch Print", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bb51800b4f7a-1", "text": "\u2022SDMPXCMC for the COBOL exit\nBatch Print\nThe batch version of the user exit is linked to when dumps that meet the specified selection criteria are found. The user\nexit is invoked for both print and index functions so that the list of dumps available to a user is always identical.\nThe batch user exit is invoked separately for each dump. The exit gets control through a standard OS link and is passed a\nstandard parameter list with one entry that is identical in format to the COMMAREA described in Online Dump Display in\nthis section.\nExit Processing\nFor both online and batch exits:\n\u2022A zero return code indicates that the user's request is authorized\n\u2022A nonzero return code indicates that access is denied\nAllocate Files\nUse file allocation steps to configure your product.\nThis article describes the required and optional file allocation steps that are used for product configuration. All products\nmust allocate the PROTSYM file. File allocations specific to each product are described after the PROTSYM information.\n 225", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8883dd98c3f0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAllocate PROTSYM\nMember CAVHPROT creates the PROTSYM VSAM file, which contains the symbolic information and source listings\nfor your application programs. Edit the JCL in the CAVHJCL library to conform to your installation standards and the\npreviously completed worksheet.\nNote the following items when you create the symbolic file:\n\u2022Do not specify a secondary space allocation.\n\u2022Depending on the file size, the CAVHPROT utility job (running the IN25UTIL program) can run for a long time.\nNote:  This behavior only occurs the first time after the file is created by the IDCAMS job.\n\u2022Each symbolic file has an upper limit of about four million 2 KB records, and holds approximately 147,000 programs.\n\u2022The symbolic file must not reside in the LSR pool.\nConcurrently Updating the PROTSYM File\nThe application uses the MVS RESERVE and DEQ macros to allow sharing of the PROTSYM file between regions or\nsystems.\nThe resource major name that is used in the RESERVE and DEQ macros is INTERTST. Place the major name INTERTST\ninto an MVS service that converts the RESERVE into a cross-system ENQ if this service is available at your site.\nPopulate the Symbolic File\nThis section applies only to InterTest for CICS and SymDump  for CICS users.\nYou can skip this step if your site previously loaded a PROTSYM file with the symbolic information for CICS DSECTs and\nInterTest for CICS and SymDump  for CICS DSECTs,.\nMember CABALSYM, located in the CAVHJCL library, populates the PROTSYM VSAM file with symbolic information for", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8883dd98c3f0-1", "text": "CICS DSECTs and InterTest and SymDump for CICS DSECTs. Edit the JCL to conform to your installation standards.\nNOTE\nSymbolic information and source listings for the demonstration programs are loaded into the PROTSYM file\nwhen you prepare the programs for execution.\nUpdate Your In-house Compile and Assemble Procedures\nTo update the compile and assemble procedures and create symbolic information for your Assembler, PL/I, or COBOL\nprograms, see Symbolic Support.\nInterTest Batch Files\nAllocate PROFLIB\nBefore you execute the application, you must allocate a profile data set. CAVHPROC library member CAMRPROF\ncontains the sample allocation for the profile data set. You can allocate PROFLIBs by user or by site. To maintain session\nvariables, each user requires one block and one directory entry in the PROFILE library. Allocate the same number of\nblocks as the number of programmers who access the application. Each directory block contains three users. If the\nnumber of users is greater than 90, change the number of directory blocks.\nThe following parameters are needed for this JCL:\nTGTVOL=,\nVOLSER of the PROFLIB\nPREFIX='USER.',\nThe USERID high-level qualifier (default = USER)\n 226", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "36293112628b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPERMDA=SYSDA\nThe generic UNIT for permanent DASD (default = SYSDA)\nNOTE\nDuring execution, each user requires WRITE access to the PROFILE library only. Secure all other required\napplication files with READ access only. Be sure to give similar attention to the optional files that the application\nuses (for example, the session log).\nAllocate ALIBs (Optional)\nThe product uses an ALIB data set to save allocation information. The number of ALIBs is not limited, but all ALIBs must\nbe created manually.\nCAVHPROC library member CAMRALIB creates and catalogs an ALIB. The following parameters are needed for this JCL:\nTGTVOL=,\nThe VOLSER of the target data sets\nPREFIX='USER.',\nThe USERID high-level qualifier (default = USER)\nPERMDA=SYSDA\nThe generic UNIT for permanent DASD\nAllocate INCLIBs (Optional)\nIf you intend to use the INCLUDE command, you must allocate the INCLUDE library. CAVHPROC library\nmember CAMRINCL allocates this library.\nThe following parameters are needed for this JCL:\nTGTVOL=,\nVOLSER of the target data set\nPREFIX='USER.',\nThe SITE/USERID high-level qualifier (default = USER)\nPERMDA=SYSDA\nThe generic UNIT for permanent DASD (default = SYSDA)\nSymDump  Batch\nAllocate CAIPRINT Repository Library\nMake a copy of CAI.CAVHJCL(CARXREPO) and update it to conform to your installation standards.\nUse CARXREPO to create and initialize a new CAIPRINT repository library. The data set name for your CAIPRINT", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "36293112628b-1", "text": "repository is defined in the PRTLIB option of CAOETABL. This data set name is defined in the next step. Specify the same\ndsname when you customize CARXREPO.\nCARXREPO consists of the following steps:\nStep Program Description\n1 IDCAMS Allocate the CAIPRINT repository.\n2 CAOUPRTU Initialize the CAIPRINT repository.\nNOTE\nTo enable file sharing between regions and systems, RESERVE and DEQ macros are used when the CAIPRINT\nrepositories are updaterd. The resource major name that is used in the RESERVE and DEQ macros is\n 227", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5d09f17e50b1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAOUPRTA. If your installation uses a service that converts RESERVEs into cross-system ENQs, define the\nmajor name CAOUPRTA to the service.\nEstimated Size of the PRTLIB Repository Library\nThe size of an individual PRTLIB report varies greatly depending on factors that include the number of active programs,\nthe size of the data in each active program, and the number of allocated files. These factors make it difficult to determine\nhow much space to allocate for the repository.\nAs a guideline, using CAOEDEMO and a repository of one cylinder, you can store 17 reports in the repository. This report\ncontains only one active COBOL program, but contains a large data division of approximately 500 KB.\nDue to the number of factors to consider to determine the size of your repository, base this decision on the amount of\nspace that you want to dedicate to saving abend reports. You can migrate the reports to a larger repository later with the\nCAOUPRTU utility COPY function.\nNOTE\nDo not specify a secondary space allocation when you create the repository. The capacity of the repository is\nfixed by the allocation job and cannot be increased using secondary extents.\nNOTE\nThe LE option TERMTHDACT(UADUMP) generates a U4039 abend when a severity 2 or greater unhandled\ncondition occurs. SymDump  Batch reports on this abend.\nNOTE\nThe SymDump PRTLIB report index has a limit of 4000 entries.\nInterTest for CICS and SymDump  for CICS\nInstall the Help Facility\nThe member DEFHELP, found in the CAVHJCL library, creates and loads the VSAM file that contains the InterTest and\nSymDump for CICS online help information. Edit the JCL to conform to your installation standards and the previously", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5d09f17e50b1-1", "text": "completed worksheet. This member and other referenced members are located in the CAI.CAVHJCL library after the\nAPPLY step.\nCreate the User-Defined Abend Description File\nThe member DEFUHLP, located in the CAVHJCL library, creates the VSAM file that contains the user-defined abend\ndescription information. Edit the JCL to conform to your installation standards and the previously completed worksheet.\nThis member and other referenced members are found in the CAI.CAVHJCL library after the APPLY step.\nInterTest for CICS\nCreate the Debug Session File\nThe member DEFMLOG, located in the CAI.CAVHJCL library, creates the file that is used to record breakpoints and\nkeeps set when monitor logging is turned on. These records can be loaded for another debug session later without setting\nbreakpoints and keeps again. Edit the JCL to conform to your installation standards. If you use the optional PROTMLOG\nfeature, a unique MLOG dataset is required for each CICS region.\nNOTE\nFor more information about the Monitor Logging facility, see Monitoring Menu Options .\n 228", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "930d63716100-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCreate the Checkpoint File\nThe member DEFCKPT, located in the CAVHJCL library, creates the checkpoint file that is used to periodically record\nthe status of InterTest for CICS for a possible restart. This member and other referenced members are located in the\nCAI.CAVHJCL library. Edit the JCL to conform to your installation standards.\nNOTE\nFor more information on the checkpoint recording facility, see Monitoring Menu Options .\nSymDump  for CICS\nCreate the PROTDMP File\nThe SymDump  for CICS VSAM file, PROTDMP, is the SymDump  for CICS dump data set. This file contains all dumps\nto view and maintain with SymDump  for CICS. PROTDMP files that were initialized using a release of SymDump  for CICS\nafter r8.0 are compatible with this release.\nUse member SYMFILE in CAI.CAVHJCL to create and initialize the file with program IN25INIT. Be aware of the following\nconsiderations:\n\u2022The maximum number of dumps the SymDump  for CICS dump data set can hold depends on the CI (Control Interval)\nsize. For more information, see the SYMFILE member in the CAVHJCL.\n\u2022Do not specify a secondary space allocation.\n\u2022Depending on the file size, the SYMFILE job may run for a long time.\n\u2022Two or more concurrently active CICS regions cannot share the same SymDump  for CICS PROTDMP file for update.\nNOTE\nYou cannot run IN25INIT on a previously initialized PROTDMP file. IN25INIT can only run against a newly\ndefined VSAM file.\nEstimate the Size of the PROTDMP File", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "930d63716100-1", "text": "defined VSAM file.\nEstimate the Size of the PROTDMP File\nThe size of an individual dump varies greatly depending on the number of active programs, the size of the data in\neach active program, and so on. Because of these issues, it is difficult to determine how much space to allocate for the\nPROTDMP file.\nTherefore, Broadcom  suggests that you determine the amount of space you are willing to dedicate to saving dumps. You\ncan use the COPY function of the IN25DMPU utility to migrate dumps to a larger PROTDMP file later.\nNOTE\nBecause the capacity of the PROTDMP file is fixed by the allocation job and cannot be increased using\nsecondary extents, do not specify a secondary space allocation when you create the PROTDMP file.\nInterfaces and Compatibility\nUse your InterTest and SymDump  products with other products and interfaces.\nThis article describes considerations for using your InterTest and SymDump  products with other products and interfaces.\nThis article contains the considerations for all products.\nConfigure Dynamic Symbolic Support\nThe dynamic symbolic support feature improves your productivity by reducing the pre-testing setup time that is commonly\ninvolved in locating and loading a program compiler or assembler listing. This feature automatically locates the listing and\nloads the symbolic file. This feature is fully integrated with Endevor .\n 229", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ced6b27a378a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIf the Endevor  footprint (FOOTPRNT) feature is used when application programs are generated in Endevor , you can\nimplement the dynamic symbolic support feature.\nConfigure the Started Task Procedure for Endevor  support\nThis configuration procedure is required in the following situations:\n\u2022If you want to use Dynamic Symbolic Support for InterTest CICS or SymDump CICS.\n\u2022If you are not using CICS products and you use multiple Endevor  C1DEFLTS which are not in your STEPLIBs. For\nmore information, see Batch Link Facility or Symbolic Utilities.\nFollow these steps:\n1.Install CAICCI as discussed in the section Common Components and Services  for z/OS and Requirements.\n2.Copy the CAVHSAMP member INDVSPWN to the CAIENF parameter library and add the spawn parameter to the\nCAIENF spawn parameter list.\n3.To access Endevor  to dynamically load program symbolic information, use the started task procedure of the\nCAVHPROC member INTNDVR,  \n4.To conform your installation standards, modify this procedure.\n5.Copy the procedure to a system procedure library as member INTNDVRn. The member name of the procedure should\nhave the appended Endevor  C1DEFLTS table site ID. For example, if the site ID is 3, the procedure member name\nshould be INTNDVR3.\n6.Repeat step 5 for each unique site ID.\nNOTE\n\u2022This started task must be an APF-authorized task.\n\u2022To load library data sets in which application programs that were created by Endevor  reside, the INTNDVRn\nprocedures require read security access . The procedures also require write security access to PROTSYM\nfiles that they populate.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ced6b27a378a-1", "text": "files that they populate.\n\u2022To activate the new spawn parameters that are added for this feature, CAIENF must be refreshed\nShut Down Endevor  Dynamic Symbolic Support Started Task\nWhen shutdown is required, the SymDump  for CICS Dynamic Symbolic Support started task is canceled with the\nCANCEL operator command.\nConfigure Dynamic Symbolic Support for InterTest Batch\nIf you changed the procedure name from the default INTNDVR, you must also change and reapply USERMOD for the\nIN25SITE table. Edit CAVHJCL member IN25SITE.\nThe following table is a sample IN25SITE program:\n******************************************************************\n* THIS TABLE IS USED TO SUPPORT CUSTOMER'S ENVIRONMENT *\n* WHERE MULTIPLE C1DEFLTS ARE USED. *\n* *\n* THE TABLE CONTAINS AN ENDEVOR SITE ID AND THE ASSOCIATED *\n* PROCNAME TO START LISTING SERVER AS A STARTED TASK TO *\n* RETRIEVE LISTINGS STORED UNDER ENDEVOR CONTROL. *\n* *\n* THIS TABLE MUST BE MODIFIED VIA SMP/E USRMOD IF THE *\n* CUSTOMER HAS MORE THAN ONE C1DEFLTS. A SINGLE C1DEFLTS *\n* SITE, DOES NOT NEED TO MODIFY THIS TABLE. *\n* *\n 230", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9169ebf7dc3b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n* THIS MODULE MUST BE ASSEMBLED AND LINKAGE EDITED INTO *\n* CA INTERTEST BATCH LOAD MODULE LIBRARY. *\n* *\n* MACRO @NDVRSTE IS USED TO GENERATE THIS TABLE. *\n* *\n* MACRO FORMAT: *\n* @NDVRSTE PROC= *\n* PROC = A MAXIMUM OF 7 CHARACTER PROC NAME. *\n* PROC = BLANKS FOR SINGLE C1DEFLTS SITE. *\n* *\n* NOTE: CA INTERTEST WILL APPEND THE SITE ID OBTAINED FROM *\n* ENDEVOR FOOTPRINT AS THE 8TH CHARACTER. THUS THE *\n* PROCNAME IN YOUR PROCLIB IS EIGHT CHARACTERS. *\n*******************************************************************\nIN25SITE CSECT , \nIN25SITE AMODE 31 \nIN25SITE RMODE ANY \n* \n @NDVRSTE PROC= \n* @NDVRSTE PROC=INTNDVR \n* END ,\nThe table is generated using macro @NDVRSTE. The macro has one parameter PROC, which is explained as follows:\nA maximum seven-character name of a cataloged procedure is used to start the listing server started task (STC). The\neighth character is reserved as a suffix to be appended by the product based on your site ID. The name that is defined in\nthe PROC keyword parameter must match the procedure name in the previous description.\nThe JCL is included in the configuration PTF that assembles and links this program. The JCL member is IN25SITE and\nit is found in the CAVHJCL data set. The JCL must be modified JCL to conform to their installation standards before\nsubmitting it.\nConfigure Dynamic Symbolic Support for SymDump  Batch", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9169ebf7dc3b-1", "text": "submitting it.\nConfigure Dynamic Symbolic Support for SymDump  Batch\nThe first seven-character prefix of the procedure member name that you copied to the system procedure library must\nmatch the value that is defined in the NDVRPROC option in CAOUDFRX.\nConfigure Dynamic Symbolic Support for InterTest and SymDump for CICS\n\u2022The seven-character prefix for this procedure name is specified and can be changed by editing the NDVRPROC\nparameter in the IN25OPTS macro.\n\u2022Include an NDVRSYM ddname in the IN25OPTS SYMFIL= parameter to indicate the PROTSYM file to be used for\ndynamic symbolic loading. The presence of an NDVRSYM PROTSYM ddname in the CICS startup JCL indicates to\nInterTest and SymDump for CICS to invoke the dynamic symbolic load option.\nSYMFIL=(PROTSYM,xxxxxxx,xxxxxxx,NDVRSYM)\n\u2022If you use multiple Endevor  C1DEFLTS in your environment.\nBatch Interfaces and Compatibility\nThis article contains interface and compatibility considerations for InterTest Batch and SymDump  Batch.\n 231", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5ffb284288f8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterTest Batch\nCustomize CLISTs\nYou may need to customize a number of CLISTs provided in the CAVHCLS0 library to run your product. These CLISTs are\nas follows:\n\u2022CAMRDRVR\n\u2022CAMRCLST\n\u2022CAMRCIMS\n\u2022CAMRCBTS\n\u2022CAMRCDB2\n\u2022CAMRSTRT\n\u2022CAMRKEYS\n\u2022CAMRCMD\nCAMRDRVR\nMember CAMRDRVR is a sample CLIST that acts as a driver for the four startup CLISTs. The following modifications\nshould be made if you want to use this driver:\n\u2022Modify the PREFIX to match the prefix of the installed data sets.\n\u2022Under /*Note2*/, uncomment the library allocations that are not allocated in your TSO logon procedure or other CLIST.\nCAMRCLST\nMember CAMRCLST is a sample CLIST showing necessary file allocations for the application. The following modifications\nshould be made:\n\u2022Modify the PREFIX to match the prefix of the installed data sets.\n\u2022Under /*Note2*/, uncomment the option that pertains to your installation. Use ISPLLIB for the LE run-time library if it is\ndifferent from the default (linklist).\nSelect per-site or per-user PROFLIB. In the sample CLIST, the first allocation statement after /*Note3*/ is for those that\nwant to allocate one PROFILE data set per site. The second allocation statement after /*Note3*/ is for those that want\nto allocate a PROFILE data set per-user. The third statement after /* Note3 */ is a CLIST that can create a per-user\nPROFILE data set if one does not exist and then allocate it. Note that you may have to tailor these statements or the\nCLIST to meet your specific installation requirements.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5ffb284288f8-1", "text": "CLIST to meet your specific installation requirements.\n\u2022Under /*Note4*/, uncomment the optional files you are using with the InterTest Batch. The optional files are as follows:\nINT1CLIB\nDefines the partitioned data set that contains InterTest Batch commands used by the INCLUDE command. If it\nis not allocated, the INCLUDE command is disabled. For more information about the INCLUDE command, see\nBatch Debugging. CAI.CAVHSAMP is the data set that includes the members needed for executing the demos\n(these members must be copied if you define another name for INT1CLIB and you want to run one of the demos).\nUncomment the ALLOC statement for INT1CLIB to allocate the default CAI.CAVHSAMP data set. Alternatively,\nyou can execute the CLIST INT1CLIB, the next comment in the CLIST, to create a personal include library and\nallocate it to INT1CLIB.\nINT1CLOG\nDefines a sequential file used for the InterTest Batch session log. If it is not allocated, logging is disabled. For\nmore information about the session log, see Batch Debugging. Uncomment the first ALLOC DD(INT1CLOG)\nstatement if you want to write your LOG data to a pre-allocated data set. You must create the data set yourself.\nUncomment the second ALLOC statement if you want your LOG data written to SYSOUT. Uncomment the CLIST\nINT1CLOG to create a personal LOG data set and allocate INT1CLOG to it.\n 232", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "510624f63111-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nINT1REPT\nDefines a sequential file used to store the HISTogram and XSUM reports. If it is not allocated, the HIST and\nXSUM commands are disabled. For more information about the reports, see the HIST and XSUM Report\nCommand descriptions in Batch Debugging. Uncomment the first ALLOC DD(INT1REPT) statement if you want\nto write your histogram data to a pre-allocated data set. You must create the data set yourself. Uncomment the\nsecond ALLOC statement if you want your histogram data written to SYSOUT. Uncomment the CLIST INT1REPT\nto create a personal histogram data set and allocate INT1REPT to it.\nINT1ALIB\nDefines the partitioned data set that contains allocations saved under option 3, ALLOCATION. If it is not allocated,\nthe save and retrieve features are disabled. For more information on allocating data sets and saving the\nallocations, see Allocations Facility for ISPF. Uncomment the CLIST INT1ALIB if you want to dynamically create\nand allocate a personal allocation library.\nCAMRCIMS\nCAMRCIMS is a sample CLIST showing the necessary file allocations for the foreground testing of IMS/DB or DL/I\nprograms. If you are licensed for the IMS option and want to debug these types of applications in foreground, the following\nmodifications should be made:\n\u2022Modify the PREFIX and IMS to match the prefix of the installed application and IMS data sets.\n\u2022Under /*Note2*/, uncomment the option that pertains to your installation. Use ISPLLIB for the LE run-time library if it is\ndifferent from the default (linklist).\nNOTE\nThere are two sections marked /*Note2*/ in this CLIST.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "510624f63111-1", "text": "NOTE\nThere are two sections marked /*Note2*/ in this CLIST.\nSelect per-site or per-user PROFLIB. In the sample CLIST, the first allocation statement after /*Note3*/ is for those that\nwant to allocate one PROFILE data set per site. The second allocation statement after /*Note3*/ is for those that want\nto allocate a PROFILE data set per-user. The third statement after /* Note3 */ is a CLIST that can create a per-user\nPROFILE data set if one does not exist and then allocate it. Note that you may have to tailor these statements or the\nCLIST to meet your specific installation requirements.\n\u2022Under /*Note4*/, uncomment the optional files you are using with your product. See the optional files listed under\nCAMRCLST for a description of the optional files.\n\u2022Under /*Note5*/, add any other IMS files needed for your application.\nThis CLIST is only required if you will be debugging your IMS applications in foreground.\nCAMRCBTS\nCAMRCBTS is a sample CLIST showing the necessary file allocations for the foreground testing of IMS/DC programs\nunder BTS. If you are licensed for the IMS option and want to debug these types of applications in foreground, the\nfollowing modifications should be made:\n\u2022Modify the PREFIX, IMS and BTS to match the prefix of the installed application, IMS, and BTS data sets.\nUnder /*Note2*/, uncomment the option that pertains to your installation. Use ISPLLIB for the LE run-time library if it is\ndifferent from the default (linklist).\nNOTE\nThere are two sections marked /*Note2*/ in this CLIST.\nSelect per-site or per-user PROFLIB. In the sample CLIST, the first allocation statement after /*Note3*/ is for those that", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "510624f63111-2", "text": "want to allocate one PROFILE data set per site. The second allocation statement after /*Note3*/ is for those that want\nto allocate a PROFILE data set per-user. The third statement after /* Note3 */ is a CLIST that can create a per-user\nPROFILE data set if one does not exist and then allocate it. Note that you may have to tailor these statements or the\nCLIST to meet your specific installation requirements.\n 233", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "42fb3dc71d13-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022For the statements under /*Note4*/, uncomment the optional files you are using with your product. See the optional\nfiles listed under CAMRCLST for a description of the optional files.\n\u2022Under /*Note5*/, add any other IMS files needed for your application.\n\u2022Under /*Note6*/, modify your BTSIN and other BTS-related files according to your installation standards.\n\u2022Modify the BTSAL parameter (in the first line of the CLIST) to NEW if the BTS files are to be recreated for every\ndebugging session.\nThis CLIST is only required if you will be debugging your BTS applications in foreground.\nCAMRCDB2\nCAMRCDB2 is a sample CLIST showing necessary file allocations for the foreground testing of DB2 programs. If you\nwant to debug these types of applications in foreground, the following modifications should be made:\n\u2022Modify the PREFIX to match the prefix of the installed data sets.\n\u2022Under /*Note2*/, uncomment those libraries that are not allocated in your TSO logon procedure or in another CLIST.\nUse ISPLLIB for the COBOL run-time library if it is different from the default (linklist). If the DB2 libraries to run the\napplication are not available through linklist or your TSO logon PROC, you must allocate them before issuing the\nRUN command in CLIST CAMRCDBX. The allocations can be made in CAMRCDB2 or CAMRCDBX, where the DB2\nsubsystem name is provided to the product.\nNOTE\nThere are two sections marked /*Note2*/ in this CLIST.\nSelect per-site or per-user PROFLIB. In the sample CLIST, the first allocation statement after /*Note3*/ is for those that\nwant to allocate one PROFILE data set per site. The second allocation statement after /*Note3*/ is for those that want", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "42fb3dc71d13-1", "text": "to allocate a PROFILE data set per-user. The third statement after /* Note3 */ is a CLIST that can create a per-user\nPROFILE data set if one does not exist and then allocate it. Note that you may have to tailor these statements or the\nCLIST to meet your specific installation requirements.\n\u2022Under /*Note4*/, uncomment the optional files you are using with the application. See the optional files listed under\nCAMRCLST for a description of the optional files.\nThis CLIST is only required if you will be debugging your DB2 applications in foreground.\nCAMRCDBX\nYou might need to udpate CAMRCDBX to allocate the DB2 libraries to run the application, if they are not available through\nlinklist or your TSO logon PROC. See the description for CAMRCDB2.\n\u2022Modify the PROC to include a query of the user supplied DB2 subsystem, &MRSSN, and then allocate the DB2\nsubsystem\u2019s appropriate loadlibs, both DSN and loadlib. Add a LIBDEF statement for ISPLLIB to allocate these\nloadlibs.\n\u2022If your InterTest Batch loadlib is not in your linklist then you also need to include that loadlib in the LIBDEF statement of\nISPLLIB concatenation.\n\u2022If your application load library that contains the program you are debugging also has a program with the name\n\u201cCALL\u201d, then that \u201cCALL\u201d program will be executed in place of the INTBATCH program in the TSO CLIST \u201cCALL\n'CAI.CAVHLOAD(INTBATCH)' 'MEMBER(INTISPF)'\u201d statement, which will cause unpredictable results or failures. If\nthis situation exists, then you should add the TSO \u201cTEST\u201d command to the CAMRCDBX CLIST in between the \u2018RUN\u2019\nand \u2018CALL\u2019 commands.\nCAMRSTRT", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "42fb3dc71d13-2", "text": "and \u2018CALL\u2019 commands.\nCAMRSTRT\nCAMRSTRT is called under an ISPF NEWAPPL. If you would like to modify the initial PF key settings for this APPL,\nuncomment the call to the CLIST CAMRKEYS.\n 234", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "329a73ec3d64-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAMRKEYS\nCAMRKEYS is called optionally from the CLIST CAMRSTRT to set up initial PF key settings for this APPL. By default, all\nof the PF keys are set to an initial value. By default, the PF keys will only be set once. To have the PF keys reset, modify\nthe variable CHANGED.\nCAMRCMD\nMember CAMRCMD is the CLIST that is called from the /clist command during a debugging session. For more information\non the /clist command, see Batch Debugging.\nCustomize Compile Procedures\nSeveral sample JCL members are provided in library CAVHPROC, which can be modified and used as the application\ncompile/assemble procedures. Which member you use depends whether you are using COBOL/VS, COBOL II and\nhigher, PL/I, or Assembler.\nCOBINT\nCOBINT is a sample JCL stream showing a COBOL/VS compile. The difference between this compile procedure and the\nstandard procedure supplied by IBM is that this procedure updates the symbolic information in the PROTSYM file.\nYou must supply the following parameters:\nPROT\nSpecifies the data set name of the PROTSYM file.\nCOPT\nOverrides the compiler options.\nYou must specify several additional items in the JCL. Information that must be modified or supplied includes the following:\n\u2022COBOL compiler library\n\u2022COBOL copy library\n\u2022COBOL source library\n\u2022LKED SYSLIB\nCOB2INT\nCOB2INT is a sample JCL stream showing a COBOL II or IBM COBOL compile. The difference between this compile\nprocedure and the standard procedure supplied by IBM is that this procedure updates the symbolic information in the\nPROTSYM file.\nYou must supply the following parameters:\nPROTSYM", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "329a73ec3d64-1", "text": "PROTSYM file.\nYou must supply the following parameters:\nPROTSYM\nSpecifies the data set name of the PROTSYM file.\nCOPT\nOverrides the compiler options.\nYou must specify several additional items in the JCL. Information that must be modified or supplied includes the following:\n\u2022COBOL compiler library\n\u2022COBOL copy library\n\u2022COBOL source library\n\u2022LKED SYSLIB\n 235", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e8167d644d50-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nASMINT\nASMINT is a sample JCL stream showing an assemble procedure. This procedure updates the symbolic information in the\nPROTSYM file.\nYou must supply the following parameters:\nPROTSYM\nSpecifies the data set name of the PROTSYM file.\nAOPT\nOverrides the assembler options.\nYou must specify several additional items in the JCL. Information that must be modified or supplied includes the following:\n\u2022Assembler library\n\u2022Assembler macro library\n\u2022LKED SYSLIB\nPLIINT\nPLIINT is a sample JCL stream showing a PL/I compile. This procedure updates the symbolic information in the\nPROTSYM file.\nYou must supply the following parameters:\nPROTSYM\nSpecifies the data set name of the PROTSYM file.\nPOPT\nOverrides the PL/I compile options.\nYou must specify several additional items in the JCL. Information that must be modified or supplied includes the following:\n\u2022PL/I source library\n\u2022PL/I copy library\n\u2022LKED SYSLIB\nAdd to ISPF Main Panel (Optional)\nTo add InterTest Batch to your ISPF main menu, use member CAMRISPF in the InterTest Batch runtime source library\n(CAVHSAMP) as a model to add option INTB to your ISPF main menu.\nAdd ISPF Libraries to TSO Logon Procedure (Optional)\nTo add the InterTest Batch ISPF libraries to your TSO logon procedure (instead of using LIBDEFs in the startup CLISTs),\nmake the following changes to your TSO logon procedure:\n1.Add the InterTest Batch ISPF panel library (CAVHPNL0) to the ISPPLIB concatenation.\n2.Add the InterTest Batch ISPF message library (CAVHMSG0) to the ISPMLIB concatenation.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e8167d644d50-1", "text": "3.Add the InterTest Batch CLIST library (CAVHCLS0) to the SYSPROC concatenation.\n4.If the COBOL runtime library is different than the site default, add it to the ISPLLIB concatenation.\nRefer to member CAMRTSOL in the InterTest Batch runtime source library (CAVHSAMP) for an example.\nCustomize Roscoe  (Optional)\nThis step applies only to Roscoe  users.\n 236", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "073e651edd44-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe CAVHSAMP library provides three sample members for customizing Roscoe  for the application: CAMRETSO,\nCAMREPL, and INTROS.\nCAMRETSO\nCAMRETSO is a sample JCL to add to your Roscoe  JCL. It should be concatenated to your Roscoe  ETSOLIB. Add the\nCOBOL runtime library if it is different from the site default.\nCAMREPL\nCAMREPL contains sample definitions to add to your Roscoe  Eligible Program List for the application. Incorporate it into\nyour Roscoe  EPL.\nINTROS\nUse member INTROS in the CAVHSAMP library to customize the options that are passed to the application when it is\ninvoked under Roscoe .\nThe INTROS member parameters include the following:\nSYMLDYN\nThis parameter is no longer used.\nTRACE(n)\nSpecifies the number of entries saved in the trace table and displayed by the TRACE and TRACE SOURCE\ncommands. The default is 1000 and n is an integer between 1 and 32760.\nEXTSTOR(nM|nK)\nThe extended storage parameter allows you to set the amount of extended storage that is accessed by the\napplication under the z/OS operating system. This storage is used when formatting storage above the 16 MB\nline.The default is 64M. Specify the amount in megabytes (nM) or kilobytes (nK), and n is any integer between 1\nand 100.\nLINKPARM(n)\nSpecifies the maximum number of linkage parameters that are set by the installation. The default is 32 and  n is\nany integer between 1 and 1000. Each linkage parameter requires a page of memory (4096 bytes) unless the\ndefault has been changed.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "073e651edd44-1", "text": "default has been changed.\nLINKSIZE( n)\nSpecifies the amount of memory to be getmained for each linkage parameter. The default is 4096. It is not\nrecommended to specify less than 1024 or more than 32768. The parameters are always on page boundaries.\nNOSLOW\nTurns off the SLOW command at the installation. You are notified with a message stating this when attempting to\nuse the SLOW command. Comment this parameter out if you do not want the SLOW command disabled.\nSLOWFAST(n)\nSpecifies the duration of the wait time in hundredths of a second between the executable statements when using\nthe SLOWFAST command. The default is one quarter of a second (n=25). The value is any integer between 1 and\n4096. This might be helpful to TCAM users with buffering problems.\nNOSTAX\nThis is a required startup parameter.\nNOESTAE\nThis is a required startup parameter.\nNOSTAE\nThis is a required startup parameter.\n 237", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eb5f8645cdb6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOESTAI\nThis is a required startup parameter.\nNOJSCB\nThis is a required startup parameter.\nOther considerations for Roscoe  users include:\n\u2022Concatenate the COBOL or PL/I runtime library if it is not in linklist and it is required to execute your application under\nRoscoe .\n\u2022Increase the Roscoe  ETSALLOC parameter, if necessary.\n\u2022The CAI.CAVHRPF library must be imported to a Roscoe  RPF library.\nReview and Customize for BTS\nMember INTBTSX is provided for ISPF users with Business Transaction Services (BTS) extended support. (This member\nis provided for clients who are licensed for the IMS option and want to debug BTS applications in foreground.) Parameters\nrelating to INTBTSX are listed following:\nISPF\nThis is required to run the application under the ISPF dialog manager.\nSYMLDYN\nThis option is no longer used.\nTRACE(n)\nSpecifies the number of entries saved in the trace table and displayed by the TRACE and TRACE SOURCE\ncommands. The default is 1000 and n is an integer between 1 and 32760.\nEXTSTOR(nM|nK)\nThe extended storage parameter allows you to set the amount of extended storage that is accessed by the\napplication under the z/OS operating system. This storage is used when formatting storage above the 16 MB\nline. The default is 64M. Specify the amount in megabytes (nM) or kilobytes (nK), and n is any integer between 1\nand 100.\nLINKPARM(n)\nSpecifies the maximum number of linkage parameters that are set by the installation. The default is 32. n is any", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eb5f8645cdb6-1", "text": "integer between 1 and 1000. Each linkage parameter requires a page of memory (4096 bytes) unless the default\nhas been changed.\nLINKSIZE(n)\nSpecifies the amount of memory to be getmained for each linkage parameter. The default is 4096. It is not\nrecommended to specify less than 1024 or more than 32768. The parameters are always on page boundaries.\nNOSLOW\nTurns off the SLOW command at the installation. You are notified with a message stating this when attempting to\nuse the SLOW command. Comment this parameter out if you do not want the SLOW command disabled.\nSLOWFAST(n)\nSpecifies the duration of the wait time in hundredths of a second between the executable statements when using\nthe SLOWFAST command. The default is one quarter of a second (n=25). The value is any integer between 1 and\n4096. This might be helpful to TCAM users with buffering problems.\nBTSNAME(*******)\nThis is a BTSTSOST user-defined name.\nBTSEXT\nThis is intercepted PA2 support.\nBTSSYSO\nThis is BTS SYSOUT support.\n 238", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a84630b8989a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOSTAX\nThis is a required startup parameter.\nNOESTAE\nThis is a required startup parameter.\nNOESTAI\nThis is a required startup parameter.\nNOJSCB\nThis is a required startup parameter.\nScreen Handling Solution for the Message BTS0067I\nThis product has a great deal of code that deals with screen handling in the BTS environment. While this code handles the\nmajority of environments, there is a screen-handling problem that occurs when a transaction reinserts itself without issuing\na COBOL GOBACK verb.\nSymptom: BTS does not display the next IMS screen because BTS fails to realize that the PA2 key from VTAM is\nactually a RESHOW indicator, and has not been entered by the terminal operator. If this occurs, the following message is\ndisplayed:\nBTS0067I NO MORE MESSAGES. SCREEN CLEARED.\nIf your site has programs that perform the previous function, or your site has experienced any problems with PA2,\nparameter BTSEXT in member INTBTSX (see the previous parameter list) signals the application to use extended BTS\nsupport. The extended support causes BTS to ignore the PA2 key.\nThis modification has the following side effects on BTS:\n\u2022With the PA2 key disabled, it is not functional for paging.\nThis only affects applications that use multiple page or segment output messages and use the transaction insertion\ntechnique described previously.\n\u2022The change also replaces the PF key simulation capability of BTS.\nThis only affects users and BTS using terminals with NO program function (PF) keys.\nIf either of these effects causes a problem at your site, contact Broadcom Support .\nThe problem arises because BTS does not enter and exit full-screen mode properly. While it functions in a stand-alone", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a84630b8989a-1", "text": "environment, a failure occurs when BTS is run with another full-screen product such as this product.\nApplications Using Message Switching and DISPLAY or Figure Verbs\nApplications that perform message switching and use DISPLAY, Figure, or both verbs should use the BTSSYSO option.\nParameter BTSSYSO in member INTBTSX (see the previous parameter list) signals the application to use extended BTS\nSYSOUT support.\nThe BTSSYSO parameter is recommended if your site has programs that use DISPLAY, Figure, or both in the BTS\nenvironment.\nCustomize for DB2 SP and IMS/DC Debugging\nSpecial support is provided for debugging DB2 stored procedures and for IMS/DC transactions without the use of\nBTS. For more information about using batch link, see Batch Link Facility.\nNOTE\nThe batch link scheduling feature must be active and the DB2 SP or IMS/DC transaction name to be debugged\nmust have already been defined to the schedule table before job submission. Otherwise the submitted DB2 SP\nor IMS/DC job will run unmonitored.\n 239", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ef3e94cd07fe-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUsing Batch Link to Debug Your DB2 Stored Procedures\nYou can use batch link to debug your DB2 stored procedures. Manually convert the JCL used to start the WLM address\nspace in which the DB2 stored procedure executes. For more information about making the necessary changes to the\nprocedure, see InterTest Batch JCL Requirements.\nUpdate the new INT1OPTS data set by adding the DB2SP option at the end of the control statement.\nThe following panel is an example of the converted JCL:\n//D810WLM PROC RGN=7M,APPLENV=D810WLM,DB2SSN=D810,NUMTCB=1\n//IEFPROC EXEC PGM=CAMRBL01,REGION=&RGN,TIME=NOLIMIT,\n// PARM='&DB2SSN,&NUMTCB,&APPLENV'\n//STEPLIB DD DISP=SHR,DSN=CAI.CAVHLOAD\n//        DD DISP=SHR,DSN=DB2V8104.RUNLIB.LOAD\n//        DD DISP=SHR,DSN=CEE.SCEERUN\n//        DD DISP=SHR,DSN=DB2.DB2810.SDSNLOAD\n//INT1LOAD DD DISP=SHR,DSN=CAI.CAVHLOAD\n//INT1PNLL DD DISP=SHR,DSN=CAI.CAVHPNL1\n//INT1MSGL DD DISP=SHR,DSN=CAI.CAVHMSG0\n//INT1PARM DD DISP=SHR,DSN=CAI.CAVHSAMP\n//INT1PROF DD DISP=SHR,DSN=CAI.PROFLIB\n//INT1CLOG DD SYSOUT=*/\n/INT1OPTS DD *", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ef3e94cd07fe-1", "text": "//INT1CLOG DD SYSOUT=*/\n/INT1OPTS DD *\n  EXEC DSNX9WLM,DB2SP\n/*\nAfter modifying the JCL that WLM uses to run the stored procedure, invoke the stored procedure. Start the application,\nselect option 5 for batch link, and then option 2. Your stored procedure will be waiting to be debugged.\nUsing Batch Link to Debug Your Online IMS Programs\nUse batch link to debug your online IMS applications without the use of BTS.\n1.Convert the JCL to start the MPP region for use with batch link.\n2.Add the IMSDC option to the INT1OPTS DD. The following is an example of the converted JCL with the option added:\n//IMSZMPP4 JOB (07300000),'MPP REGION',REGION=4096K,\n// CLASS=3,MSGCLASS=X,MSGLEVEL=(1,1)        \n//REGION EXEC PGM=CAMRBL01,REGION=512K,\n// TIME=1440,DPRTY=(12,0),\n// PARM=(MSG,001000000000,\n// N00000000,\n// ,,,,10,\n// 5,IMSZ,,,,\n// ,,,N,\n// '',,)\n//INT1OPTS DD *EXEC=DFSRRC00,PROFILE=TESTMPP,IMSDC\n/*\n//INT1PARM DD DISP=SHR,DSN=CAI.CAVHSAMP\n//INT1LOAD DD DISP=SHR,DSN=CAI.CAVHLOAD\n//INT1PNLL DD DISP=SHR,DSN=CAI.CAVHPNL1\n//INT1MSGL DD DISP=SHR,DSN=CAI.CAVHMSG0", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ef3e94cd07fe-2", "text": "//INT1PROF DD DISP=SHR,DSN=CAI.PROFLIB/\n/INT1CLOG DD SYSOUT=*\n//INT1REPT DD SYSOUT=*\n//STEPLIB DD DSN=CAI.CAVHLOAD,DISP=SHR\n 240", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4d05184591fb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n// DD DSN=IMS.USER.LOAD,DISP=SHR\n// DD DSN=IMS.IMSZ.PGMLIB,DISP=SHR\n// DD DSN=IMS.IMSZ.RESLIB,DISP=SHR\n//PROCLIB DD DSN=IMS.IMSZ.PROCLIB,DISP=SHR\n//SYSUDUMP DD SYSOUT=A,\n// DCB=(LRECL=121,BLKSIZE=3129,RECFM=VBA),\n// SPACE=(125,(2500,100),RLSE,,ROUND)\n3.Start the region by submitting the modified JCL.\n4.Define the transaction that you want to debug that is scheduled to run in the 'test mpp' region. Run the transaction.\n5.Start the application, select option 5, Batch Link, and then option 2. Your transaction will be waiting to be debugged.\nNOTE\nFor information about using the scheduling feature, see Batch Link Facility. Using this feature, you can select\nwhich applications you would like to debug and which should be executed unmonitored.\nSymDump  Batch\nBind DB2 Support Member\nNOTE\nIf your site executes programs in a DB2 environment, you must perform this step.\nMember CARXBIND in CAI.CAVHJCL binds DBRM CAODDBB0 into package CAODPACK, the package into plan\nCAODPLAN, and grants EXECUTE authority of the plan to PUBLIC.\nUsing the instructions provided in the JCL, copy and edit the JCL as needed for your DB2 subsystem.\nSubmit the job and review the output to verify that BIND processing ran successfully. If BIND processing completed with a\nreturn code greater than 4, review the output, correct the problem, and resubmit.\nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4d05184591fb-1", "text": "NOTE\nIf your site uses multiple DB2 subsystems, you must execute this job for each subsystem.\nAbend Reporting with Language Environment (LE)\nIf your application is executing under IBM's Language Environment (LE), it is possible to receive abend reports even when\nan ABEND and system dump do not occur.\nReview Language Environment (LE) Considerations\nApplications that terminate abnormally under IBM's Language Environment (LE) may not result in an abend or a system\ndump. The two types of abnormal terminations that your applications might experience under LE are listed following:\n\u2022User abends, system abends, or program check interrupts\n\u2013For abends or program check interrupts in a user program with the LE TRAP option set to TRAP(ON), the LE\nCondition Manager intercepts the abend. The application is usually terminated without an abend or system dump.\n\u2013For abends or program check interrupts in a user program with the LE TRAP option set to TRAP(OFF), the\napplication is terminated by the abend and a system dump is produced.\n\u2013For abends issued by LE, the application is terminated by the abend and a system dump is produced.\n\u2022Unhandled LE conditions\nIf a condition is raised (by LE or a user program) with severity 2, 3, or 4, and is not handled by a condition handler, the\napplication is terminated without an abend or system dump.\nThere are abnormal terminations under LE, which do not ordinarily result in an Abend report, because SymDump  Batch\nremains dormant until a system dump is requested. To guarantee that SymDump  Batch reports are produced for every\nabnormal termination under LE, SymDump  Batch provides CAOECEEX to be used as the LE abnormal termination exit.\n 241", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0c97d2f95968-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nThere are several ways in which an LE-enabled application can handle its own abend, such as using USRHDLR\nor CEEHDLR. When an application defines a condition handler and a SymDump Batch abend report is also\nneeded, it is up to that program to percolate the abend.\nCAOECEEX - Add Abnormal Termination Exit Entry\nUse the following procedure to add abnormal termination exit entry for CAOECEEX.\nFollow these steps:\n1.Edit CEE.SCEESAMP(CEEEXTAN).\n2.Follow the instructions in this member to add an abnormal termination exit entry for CAOECEEX.\n3.Apply the applicable SYSMOD to make these changes take effect.\nNOTE\nFor more information about the CEEEXTAN exit, see the IBM z/OS Language Environment Customization\nguide.\nEstablish Access to the TSO Facility\nIf your site does not have CLIST libraries with variable length records, proceed to Concatenate ISPF File and Tailor\nMaster Panel.\nConvert CLIST Library from Fixed to Variable\nThe SymDump  Batch ISPF panels are shipped with several CLISTs. These CLISTs are in CAI.CAVHCLS0 after APPLY\nprocessing completes. For Broadcom  to ship corrective maintenance to these CLISTs, they must be in a fixed-length,\ncard-image library because SMP/E invokes IEBUPDTE to make source changes.\nMany sites use CLISTs that are in variable-length libraries. If you are one of these sites, Broadcom  provides a small,\nstand-alone batch utility that converts our CLISTs from the fixed-length form we ship into a variable form you can\nconcatenate with the rest of your CLIST libraries.\nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0c97d2f95968-1", "text": "concatenate with the rest of your CLIST libraries.\nNOTE\nThis utility program can be used to convert any fixed CLIST library to a variable library. It does not check\nwhether the library you are converting is from Broadcom . This utility does not support selective conversion; it\nconverts the entire library.\nThe JCL to invoke the utility is in CAI.CAVHJCL(CARXCNVT). The REPLACE parameter is optional; you can specify\nif you want the CLISTs in the output data set replaced by similarly named CLISTs from the input data set. Use this\nparameter with caution .\nCheck the following information when you review this JCL:\n\u2022If the SymDump  Batch load libraries are added to the linklist, the STEPLIB is not necessary.\n\u2022All messages from CAOHCNVT are written to DDNAME SYSPRINT. The program does not execute if you do not\nallocate SYSPRINT. It is a fixed-length, 121-byte record with ASA carriage control.\n\u2022The input (fixed-length) CLIST library must be allocated to SYSUT1, and the output (variable-length) CLIST library\nmust be allocated to SYSUT2.\nNOTE\nYou must  specify a BLKSIZE if the output data set is being created. The BLKSIZE must be an even multiple\nof 255 plus 4 (for the Block Descriptor Word).\n 242", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "355f8047c1ac-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nConcatenate ISPF File and Tailor the Master Panel\nYou must include the SymDump  Batch ISPF libraries in your session ISPF files concatenation to access the SymDump\nBatch panels. Use the following procedure to concatenate the ISPF file and tailor the Master panel.\nFollow these steps:\n1.Concatenate the following data sets into the indicated ddnames (if they were not previously concatenated):\nData Set Name DDName Description\nCAI.CAVHPNL0 ISPPLIB ISPF panels for SymDump  Batch\nCAI.CAVHSKL0 ISPSLIB ISPF skeletons for SymDump  Batch\nCAI.CAVHMSG0 ISPMLIB ISPF messages for SymDump  Batch\nCAI.CAVHTBL0 ISPTLIB ISPF tables for SymDump  Batch\nCAI.CAVHCLS0 SYSPROC ISPF CLISTs for SymDump  Batch\nCAI.CAVHLOAD ISPLLIB or STEPLIB SymDump  Batch Load Library\n2.Perform the following steps if your site uses variable-length CLISTs:\na. Execute CAI.CAVHJCL(CARXCNVT) to change the CLISTs from fixed to variable length format.\nb. Point the SYSPROC DD to the CAI.VCAICLIB data set (instead of CAI.CAVHCLS0).\n3.Allocate the following data sets into the indicated ddname (if they were not previously allocated):\nData Set Name DDName Description\nCAI.CAVHTBL0 CAOEXTBL ISPF tables for SymDump  Batch\nCAI.CAVHHELP CAOIHELP ISPF Help library\nYou have now placed the SymDump  Batch ISPF libraries into your session ISPF files concatenation.\nTo tailor the ISPF Master panel, do one of the following", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "355f8047c1ac-1", "text": "To tailor the ISPF Master panel, do one of the following\n\u2022Copy the ISP@MSTR panel supplied with SymDump  Batch (named CARXSBA0)\n\u2022Add new lines to your existing ISP@MSTR panel.\nUse the following procedure to add new lines to your existing panel.\nFollow these steps:\n1.Add the first line after the last option selection displayed on the panel.\n2.Define this line as an option number for the user to select with a brief description of the function. For example:\n% 6 +CA SYMDUMP BATCH - Options Panel\n% 7 +CA SYMDUMP BATCH - Invoke the CAIPRINT Repository Viewer\n3.Add the lines containing the commands required to execute the options to the list of &SEL variables defined at the end\nof the panel. For example:\n6. 'PANEL(CAOEP001) NEWAPPL(CA$Z)'\n7. 'PGM(CAOIF000) NEWAPPL(CAOI)'\nLog and Notify Facilities\nThe following LOG and NOTIFY facilities are available with SymDump  Batch. For more information, see SymDump  Batch\nOptions.\nWTO\nWrites a description of every abend to the job log using WTO with ROUTCDE=11\n 243", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0f3ae436bdbc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWTL\nWrites a description of every abend to the system log\nLOGROS\nSends a description of every abend to the Roscoe  IE user who submitted the job\nLOGTSO\nSends a description of every abend to the TSO user who submitted the job\nLOGNET\nWrites a description of every abend to Netman\nLOGUNI\nWrites a description of every abend to the NSM  console\nSMF\nWrites a description of every abend to the SMF log\nFor WTO, WTL, LOGROS, LOGTSO, and LOGUNI, one of the following messages is provided depending on the amount\nof information available:\nCAPE022I jjjjjjjj ssssssss ABENDED tnnnn IN PROGRAM pppppppp AT +xxxxxx\nCAPE023I jjjjjjjj ssssssss ABENDED tnnnn AT ccccccccccccccccccccccccccc\njjjjjjjj\nIdentifies the jobname.\nssssssss\nIdentifies the stepname.\nt\nIdentifies the abend type (S=System or U=User).\nnnnn\nIdentifies the abend code.\npppppppp\nIdentifies the program name.\nxxxxxx\nIdentifies the program offset.\ncccccccc\nIdentifies the source statement from the symbolic file.\nNOTE\nThe source statement is only available in the log message if symbolic processing is done at execution\ntime (that is, the Abend report is written to the CAIPRINT DD).\nThe SMF records are formatted as follows:\nCSMFREC  EQU   *                   MAP FOR SMF RECORD\nCSMFRDW  DS    XL4                 RDW FOR SMF RECORD\n*....... STANDARD SMF RECORD HEADER\nCSMFIND  DS    XL1", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0f3ae436bdbc-1", "text": "*....... STANDARD SMF RECORD HEADER\nCSMFIND  DS    XL1\nCSMFRECC DS    XL1                 SMF RECORD TYPE\nCSMFTIME DS    XL4\nCSMFDATE DS    XL4\nCSMFSYSD DS    XL4*....... END OF SMF RECORD HEADER\nCSMFJOB  DS    CL8                 JOBNAME\nCSMFSTEP DS    CL8                 STEPNAME\nCSMFJBID DS    CL8                 JOB NUMBER\n 244", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0f21ff6e9b9c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCSMFACCT DS    CL25                JOB ACCOUNT NUMBER\nCSMFPGID DS    CL21                PROGRAMMER NAME\nCSMFTSOD DS    CL8                 TSOID\nCSMFPROG DS    CL8                 NAME OF ABENDING PROGRAM\nCSMFCSEC DS    CL8                 NAME OF ABENDING CSECT\nCSMFOFFS DS    XL3                 OFFSET INTO PROGRAM\nCSMFABTP DS    CL1                 TYPE ABEND (SYSTEM OR USER)\nCSMFABCD DS    CL4                 ABEND CODE\nCSMFREAS DS    XL1                 REASON CODE\nCSMFPSW1 DS    XL4                 FIRST WORD OF ABENDING PSW\nCSMFPSW2 DS    XL4                 SECOND WORD OF ABENDING PSW\nCSMFFLG1 DS    XL1                 FLAG BYTE\nCSMFOPT  EQU   B'10000000'         PROGRAM IS CA-OPTIMIZED\nCSMFCSL  EQU   B'00001000'         CSL IMAGE IS PRESENT\nCSMFLANG DS    XL1                 LANGUAGE CODE\nCSMFCOBV EQU   C'S'                VS COBOL\nCSMFCOB2 EQU   C'X'                COBOL II\nCSMFNCOB EQU   X'00'               NOT COBOL\nCSMFCBV4 EQU   C'4'                COBOL VERSION 4\nCSMFCBV3 EQU   C'3'                COBOL VERSION 3\nCSMFCBV2 EQU   C'2'                COBOL VERSION 2\nCSMFOREL DS    CL6                 OPTIMIZER RELEASE\nCSMFCTIM DS    CL8                 TIME PROGRAM COMPILED", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0f21ff6e9b9c-1", "text": "CSMFCTIM DS    CL8                 TIME PROGRAM COMPILED\nCSMFCDAT DS    CL11                DATE PROGRAM COMPILED\nCSMFSEQ  DS    CL4                 EDS SEQUENCE NUMBER\n         DS    CL4                 **  RESERVED **\nCSMFCSLI DS    CL133               CSL IMAGE- INCLUDED ONLY\n*                                  IF CSL INDICATOR ON.\nCSMFEND  EQU   *\nA utility program (CAOESMF) is provided to select and report on SymDump  Batch SMF records. You can use this utility to\ndesign your own customized report using the DSECT provided.\n*******************************************************************************\n                             SEQUENCE NUMBER = 0000005\n    JOBNAME        =  MIKEDA          STEPNAME       = TSOPROC    \n    DATE           =  mm/dd/yy        TIME           = hh.mm.ss\n    ABEND          =  S0C7            SMFID          = XE86\n    JOB NUMBER     =  TSU06037        ACCOUNT #      = 40500000\n    LMOD           =  CAO2DEMO        PROGRAM        = CAO2DEMO\n    REL INTERRUPT  =  000006BC        ABS INTERRUPT  = 000066BC\n    LANGUAGE       =  COBOL II CA-OPTIMIZED    \n    CSL NOT AVAILABLE\n*******************************************************************************\n                             SEQUENCE NUMBER = 0000006\n    JOBNAME        =  MIKEDB          STEPNAME       = TSOPROC\n    DATE           =  mm/dd/yy        TIME           = hh.mm.ss\n    ABEND          =  S0C4            SMFID          = XE86\n    JOB NUMBER     =  TSU08811        ACCOUNT #      = 40500000\n    LMOD           =  MAINPROG        PROGRAM        = MAINPROG", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0f21ff6e9b9c-2", "text": "LMOD           =  MAINPROG        PROGRAM        = MAINPROG\n    REL INTERRUPT  =  00000202        ABS INTERRUPT  = 0000EA02\n    LANGUAGE       =  NOT COBOL\n    CSL NOT AVAILABLE\n*******************************************************************************\n 245", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "05116dbb392e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                             SEQUENCE NUMBER = 0000007\n    JOBNAME        =  MIKEDC          STEPNAME       = TSOPROC\n    DATE           =  mm/dd/yy        TIME           = hh.mm.ss\n    ABEND          =  S0C7            SMFID          = XE86\n    JOB NUMBER     =  TSU08983        ACCOUNT #      = 40500000\n    LMOD           =  TESTPGM         PROGRAM        = TESTPGM\n    REL INTERRUPT  =  000001FC        ABS INTERRUPT  = 000061FC\n    LANGUAGE       =  NOT COBOL\n    CSL NOT AVAILABLE\n*******************************************************************************\n    Total number of records processed = 3\nUse Netman  Interface\nThe LOGNET option activates the Netman  interface. SymDump  Batch uses the Machine-Generated Problem Tracking\n(MGPT) facility to open a problem record with Netman . Before this facility can be used, you must complete the following\nsteps.\nFollow these steps:\n1.Install and activate Netman  on the same system on which SymDump  Batch will be active.\n2.Select the MGPT feature during Netman  system generation.\n3.Identify the NTMMGCTL, NTMSC, and NTMPI files in CAOETABL when the SymDump  Batch options are customized.\n4.Add two MGPT table entry records to the Netman  database. One record must specify SymDump  Batch as the source\nproduct and SYS-ABEND as the input category. The other record must specify SymDump  Batch as the source product\nand USER-ABEND as the input category.\n5.Copy the Netman  MGPT interface modules NTMENV, NTMGGUP, and NTMECLS into a linklist library so that they are", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "05116dbb392e-1", "text": "available for SymDump  Batch at abend time.\n6.Ensure that the Netman  started task NTMBRD is up and running if the problem records are to be transferred to the\nproblem tracking database (NTMPI file).\nThe Netman  problem record layout is as follows:\nNETMREC  DSECT\nNRECTO   DC    CL8'NETMAN'             PRODUCT TO\nNRECFROM DC    CL8'CA-EDS'             PRODUCT FROM\nNRECLNAM DS    CL44                    LOGICAL NAME\n         ORG   NRECLNAM+16\nNRECSER# DS    CL10      BLANK         SERIAL NUMBER\nNRECRES1 DS    CL18                    RESERVED\nNRECDATE DS    CL6      (CURRENT)      INCIDENT DATE - CYYDDD\nNRECTIME DS    CL8      (CURRENT)      INCIDENT TIME - HHMMSSTH\nNRECLOC  DS    CL8      BLANK          LOCATION\nNRECRES2 DS    CL2                     RESERVED\nNRECSYS  DS    CL4      SMFID          SYSTEM CODE\nNRECEQMT DS    CL10     BLANK          EQUIPMENT TYPE\nNRECUNIT DS    CL5      BLANK          UNIT ID\n         SPACE 1\nNRECACT  DS    CL1      (1)            ACTION NEEDED\nNRECACTO EQU   C'1'                      OPEN A PROBLEM\nNRECACTU EQU   C'2'                      UPDATE A PROBLEM\nNRECACTC EQU   C'4'                      CLOSE A PROBLEM\n         SPACE 1\nNRECUPD  DS    CL1      (N)            SOURCE TO UPDATE\n 246", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "40aac8352c2d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNRECUPDY EQU   C'Y'                      MGPT WILL UPDATE OR CLOSE\nNRECUPDN EQU   C'N'                      MGPT WILL ONLY OPEN\n         SPACE 1\nNRECDEV  DS    CL1      (N)            SPECIFIC DEVICE\nNRECDEVY EQU   C'Y'                      SPECIFIC DEVICE ASSOCIATED\nNRECDEVN EQU   C'N'                      NO SPECIFIC DEVICE ASSOCIATED\n         SPACE 1\nNRECCAT  DS    CL10     SYS-ABEND      PROBLEM CATEGORY\n*                    OR USER-ABEND\nNRECDESC DS    CL40  SHORT MSG TEXT       PROBLEM SHORT DESCRIPTION\n*----------------------------------------------------------*\n*        SHORT MESSAGE TEXT IS 'PROGRAM GOT SABC  AT +00000000 RC=NN\n*----------------------------------------------------------*\n         SPACE 1\nNRECTEXT EQU   *                       ADDITIONAL DESCRIPTION\nNRECJLIT DC    C'JOB='\nNRECJNAM DS    CL8                     AREA FOR JOBNAME\n         DS    CL1\nNRECSLIT DC    C'STEP='\nNRECSNAM DS    CL8                     AREA FOR STEPNAME\n         DS    CL1\nNRECILIT DC    C'JOBID='\nNRECJBID DS    CL8                     AREA FOR JOB ID\n         DS    CL1\nNRECALIT DC    C'ACCOUNT='\nNRECACCT DS    CL25                    ACCOUNTING CODE\n         DS    CL1\nNRECNLIT DC    C'NAME='\nNRECPGID DS    CL21                    PROGRAMMER NAME\n         DS    CL1\nNRECTLIT DC    C'LANGUAGE='\nNRECLANG DS    CL9                     COMPILED LANGUAGE\n*----------------------------------------------------------*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "40aac8352c2d-1", "text": "NRECLANG DS    CL9                     COMPILED LANGUAGE\n*----------------------------------------------------------*\n*        EITHER 'NOT COBOL'                                *\n*               'VS COBOL'                                 *\n*               'COBOL II'                                 *\n*               'COBOL V N'                                *\n*----------------------------------------------------------*\n         DS    CL1\nNRECCSL  DS    CL80                    AREA FOR CSL IMAGE IF AVAILABLE\nNRECTUSE EQU   *-NRECTEXT\nNRECFILL DS    CL(205-NRECTUSE)        REMAINDER OF RECORD\n         SPACE 1\nNRECEND  EQU   *                       END OF EVENT RECORD\nNRECSIZE EQU   NRECEND-NRECTO          SIZE OF ONE RECORD\n*=====================================================================*\nSufficient fields and identifying data are included in the record to permit filtering on a variety of criteria.\nFor more information about the uses for MGPT record details, see the Netman  documentation.\n 247", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7167ad8b9005-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCICS Interfaces and Compatibility\nThis article contains interface and compatibility considerations for InterTest for CICS and SymDump  for CICS.\nInterTest for CICS and SymDump  for CICS\nThe following interface and compatibility information pertains to both InterTest for CICS and SymDump  for CICS.\nInstall DB2 Support\nUse the following procedure to install DB2 support:\n1.The following members on CAI.CAVHJCL provide RDO entries:\n\u2013CSDDB266 for CICS 4.1\n\u2013CSDDB267 for CICS 4.2\n\u2013CSDDB268 for CICS 5.1\n\u2013CSDDB269 for CICS 5.2\n\u2013CSDDB270 for CICS 5.3\n\u2013CSDDB271 for CICS 5.4\n\u2013CSDDB272 for CICS 5.5\n\u2013CSDDB273 for CICS 5.6\n\u2013CSDDB274 for CICS 6.1\n2.Bind the DBRM members (INB0FIDB and INB0AIDB) provided in the CAI.CAVHDBRM into an InterTest DB2 plan\n(the recommended name is INB0PLAN). The SAMPBIND member on the CAI.CAVHJCL library provides a sample of\nDB2 BIND statements for the InterTest DB2 plan. For SymDump  for CICS, you only need to bind the DBRM member\nINB0AIDB provided on the CAI.CAVHDBRM into the DB2 plan (the recommended name is INB0PLAN).\n3.The DBA must grant bind and execute authority to the plan created in the previous step.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7167ad8b9005-1", "text": "3.The DBA must grant bind and execute authority to the plan created in the previous step.\n4.For DB2 subsystems running in new function mode (release 10.1 and above), ensure that the library that contains\nthe customized DSNHDECP (either SDSNEXIT or SDSNLOAD) is in the DFHRPL DD concatenation after the CICS\nprogram libraries.\n5.To support the CORE=LASTSQL command for InterTest and SymDump for CICS, the global exit XRMIOUT is started\nby default when you start the product. This exit then collects DB2-related call information for every system DB2 call.\nThis can have significant performance implications in some DB2 shops. The parameter XRMIO=YES/NO IN25OPTS\ncontrols use of this exit. The default is XRMIO=YES. Review this before you use the default settings.\nCICS Startup DSA Limit Parameter\nInterTest for CICS and SymDump for CICS make calls to IEWBIND when using the new online COMPOSITE module\ncommand and IEWBIND requires about 750 KB of below the line storage. To ensure that sufficient storage is available\n(below the line for IEWBIND calls), your DSALIM must be at least 750 KB less than your below the line private area size.\nFailure to follow this storage guideline can result in S0F4 and U900 abends in your CICS region during dump capture.\nUpdate the CICS JCL and Startup Parameters\nIf your site has previously installed InterTest or SymDump for CICS as a separate product, some DD statements may\nexist already.\nIf you use DD statements in your CICS startup JCL, your InterTest and SymDump for CICS files, as defined in the CSD,\nrequire DD statements in the JCL for CICS. DISP=SHR must be specified for PROTSYM to allow batch compiles to", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7167ad8b9005-2", "text": "run concurrently with CICS. You can also directly add the data set names to the CEDA FILE definition, defined in the\nCSDSYM member in CAI.CAVHJCL, and remove the DD statements for those files.\n 248", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "00be9f3a3c04-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterTest and SymDump Common DD Statements\nAdd the product load library to the DFHRPL in the CICS startup JCL.\n//  DD   DSN=CAI.CAVHLOAD,DISP=SHR\nNOTE\n\u2022If you modified the IN25OPTS options during installation, make sure the load library that contains the\nmodified IN25OPTS is in your DFHRPL concatenation before the CAI.CAVHLOAD library.\n\u2022InterTest for CICS and SymDump  for CICS do not currently support the IBM Dynamic program LIBRARY\nconcatenation feature.\nIf you execute the demo programs, add the following DD to the DFHRPL in your CICS startup JCL. Specify the name of\nthe load library which contains the demo programs:\n// DD DSN=CAI.demoload,DISP=SHR\nCICS DD statements\n//PROTCPF  DD DSN=CAI.PROTCPF,DISP=OLD (InterTest  for CICS only)\n//PROTDMP  DD DSN=CAI.PROTDMP,DISP=SHR (SymDump for CICS only)\n//SYSMDUMP DD DSN= your.dataset.name , (SymDump for CICS only)\n//PROTSYM  DD DSN=CAI.PROTSYM,DISP=SHR\n//PROTHLF  DD DSN=CAI.CAVHHLF,DISP=SHR\n//PROTUHF  DD DSN=CAI.PROTUHF,DISP=SHR\nNOTE\nPre-allocate your SYSMDUMP data set with RECFM=FB,LRECL=4160,BLKSIZE=4160 and with enough space\nto capture an SVC dump for your CICS region.\nAdd the Required CICS Resource Definitions", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "00be9f3a3c04-1", "text": "to capture an SVC dump for your CICS region.\nAdd the Required CICS Resource Definitions\nMember, CSDINT in CAI.CAVHJCL library adds the CICS resource definitions for the InterTest for CICS programs, files,\nand transactions. The CSDSYM member in CAI.CAVHJCL adds the CICS resource definitions for the SymDump  for CICS\nprograms, files, and transactions. Modify the JCL according to the instructions in these members.\nAdd the corresponding RDO group to your CICS startup list (the SIT parameter GRPLIST=) as listed in the following table:\nCICS Level InterTest for CICS RDO Group SymDump  for CICS RDO Group\nCTS 5.1 INT11068 SYM11068\nCTS 5.2 INT11069 SYM11069\nCTS 5.3 INT11070 SYM11070\nCTS 5.4 INT11071 SYM11071\nCTS 5.5 INT11072 SYM11072\nCTS 5.6 INT11073 SYM11073\nCTS 6.1 INT11074 SYM11074\nThe use of the InterTest for CICS transactions ISER, VIRC, and VTAT must not be protected to a specific sign on, and for\nACF2  and RACF users must meet the special considerations described in Installation Considerations .\nDo not change any of the options specified for the InterTest or SymDump for CICS entries. If you believe there is an error\nin any of the entries, contact Broadcom Support .\n 249", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eb09600292aa-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFor CICS regions that use DB2, you must install the DB2CONN group before the InterTest or SymDump for CICS RDO\nentries.\nAdd Assembler DSECTs to the Symbolic File\nInterTest and SymDump for CICS let you display the major CICS areas in Assembler DSECT format. You can also display\nyour own user areas in DSECT format. One way to do this is to add your DSECTs to the ones supplied by InterTest and\nSymDump for CICS. However, if you do this, your entries will disappear when you install a new release of InterTest and\nSymDump for CICS. A better way is to create one or more symbolic file members to contain your DSECTs.\nSaving all of the DSECTs used at your site in one symbolic file member allows users of the FILE transaction to omit the\nsymbolic program name when requesting records or DL/I segments in structured format. The name of this member must\nbe referenced in the FSYMP installation option. The default name is PROTFILE.\nTo create your own symbolic file members, complete the following steps :\n1.Run a job to add the members containing the DSECTs to the symbolic file.\n2.Run a job to define the CORE keywords required to display the DSECTs.\nSample JCL for Adding Members to the Symbolic File\nThis sample JCL adds member USERDSEC to the symbolic file. This member contains the DSECT USERTWAF.\n//USERDSEC         JOB   **your JOB card goes here**\n//ASM          EXEC  PGM=ASMA90,REGION=1024K\n//SYSLIB       DD    DSN=USER.SOURCE,DISP=SHR", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eb09600292aa-1", "text": "//SYSLIB       DD    DSN=USER.SOURCE,DISP=SHR\n//SYSUT1       DD    DSN=&SYSUT1,SPACE=(1024,(120,120),,,ROUND),\n                     UNIT=VIO,\n//                   DCB=BUFNO=1\n//SYSPUNCH     DD    SYSOUT=B\n//SYSTERM      DD    SYSOUT=*\n//SYSPRINT     DD    DSN=&&TEMP,DISP=(,PASS),UNIT=SYSDA,\n                     SPACE=(CYL,(3,2)),\n//                   DCB=(RECFM=FBM,LRECL=121,BLKSIZE=2420)\n//SYSIN        DD    *\nUSERTWAF       DSECT\n               COPY USERTWAF\nUSERDSEC       CSECT\n               END\n//*\n//PARM         EXEC  PGM=IN25PARM,REGION=512K,\n//                   PARM='USERDSEC,LISTER=REF,NOPURGE'\n//STEPLIB      DD    DSN=CAI.CAVHLOAD,DISP=SHR\n//CARDS        DD    DSN=&&CARDS,DISP=(,PASS),UNIT=SYSDA,\n                     SPACE=(80,1)\n//*\n//SA           EXEC  PGM=IN25SYMA,REGION=512K\n//STEPLIB      DD    DSN=CAI.CAVHLOAD,DISP=SHR\n//INPUT        DD    DSN=&&TEMP,DISP=(OLD,DELETE)\n//OUTPUT       DD    SYSOUT=*,\n                     DCB=(RECFM=FBM,LRECL=121,BLKSIZE=2420)\n//MESSAGE      DD    SYSOUT=*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eb09600292aa-2", "text": "//MESSAGE      DD    SYSOUT=*\n//PROTSYM      DD    DSN=INTRTST.PROTSYM,DISP=SHR\n//CARDS        DD    DSN=&&CARDS,DISP=(OLD,DELETE) \n/*\n 250", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "258db76a9b37-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFor instructions on the STEPLIB DD, see the section Add COBOL File Structures to the Symbolic File.\nFor an explanation of the IN25PARM and IN25SYMA programs, see Adding Symbolic Information.\nNOTE\nThis job does not require a link-edit step because it only updates the symbolic file. No load module is produced.\nLanguage Environment (LE) Considerations\nIf your application is executing under IBM Language Environment (LE), region level run-time options could prevent\nthe application from intercepting problems. One option is TERMTHDACT, which controls what happens when an error\ncondition occurs, and which can prevent control from returning to InterTest.\nFor example, you could see the message \"IGZ0063S An invalid sign was detected in a numeric edited sending field\" in\nyour CEE message log, but the application does not stop at that instruction. The cause of the message might be that\nthe value of TERMTHACT is set to TRACE, which would not produce an abend and return control to InterTest. To allow\nstorage to be dumped, change the value to UADUMP and InterTest gets control and stops at the invalid instruction.\nUse the CLER transaction in CICS to dynamically change options while the region is running. Changes made with CLER\nare reset when the region is recycled. To permanently change a run-time option and not globally change the LE options\nat your site, assemble the CEEROPT CSECT and link it into a library. Place it into the RPL to override the options for a\nsingle CICS region. The input into the assembly step would look as follows:\nExample:\nCEEROPT CSECT \nCEEROPT AMODE ANY \nCEEROPT RMODE ANY", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "258db76a9b37-1", "text": "CEEROPT AMODE ANY \nCEEROPT RMODE ANY \n CEEXOPT TERMTHDACT=((UADUMP,CESE,96),OVR)\n END\nInterTest for CICS\nUse the PROMMAC Macro\nYou can use PROMMAC macros in an assembly to create a load module defined in the CICS program definition that\ncontains a number of CNTL commands. These commands are executed consecutively in the order of their appearance in\nthe macros when either of the following commands is submitted:\nCNTL=START,PROM=tablname\nCNTL=EXEC,MODULE=tablname\nWhere  tablname   is the name of the load module generated by the assembly of the PROMMAC macros.\nYou can generate several alternate modules with different names, each with a CICS program definition, if you want\nalternate ways to start InterTest for CICS or execute CNTL commands.\nIf the PROMD=tablname option is specified in the IN25OPTS macro, you can achieve the same result by specifying the\nfollowing command:\nCNTL=START\nIf the CNTL=START command is issued from a CRT terminal or CRLP-type terminal (a terminal whose input and output\nare two sequential files; see the IBM CICS System Programmer's Guide ), the commands from the load module are\ndisplayed back. For a CRT terminal, there is a small time delay before each command is executed so the user can see\nwhat is being done.\nThe first positional parameter of the PROMMAC macro contains the CNTL command to be executed. The command must\nbe enclosed in apostrophes.\n 251", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d597799c35c4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIf the table is to be used by the CNTL=START command, the first PROMMAC macro must contain this command:\nCNTL=START,PROM=nn,PROX=nn'\nWhere  nn sets the sizes of the internal InterTest for CICS tables.\nThe second positional parameter of the PROMMAC macro must contain END. THis parameter must be coded in\nthe last PROMMAC macro before the END statement.\nAny CNTL command can be specified except CNTL=LIST and CNTL=INQ.\nSample PROMMAC Macros\nThe following JCL is suitable for z/OS installations. These examples are shown for illustration purposes only. For more\ninformation, see CICS Debugging  .\n//PROMAC JOB (NTSM,473),'JOHN BROWN',CLASS=D,MSGCLASS=A\n//ASSEM  EXEC  PGM=ASMA90,REGION=512K,\n//       PARM='XREF(SHORT),DECK,NUM,LIST,ALIGN,NOOBJ'\n//*\n//SYSLIB   DD DSN=CAI.CAVHMAC,DISP=SHR\n//SYSUT1   DD SPACE=(CYL,(1,1)),UNIT=SYSDA\n//SYSUT2   DD SPACE=(CYL,(1,1)),UNIT=SYSDA\n//SYSUT3   DD SPACE=(CYL,(1,1)),UNIT=SYSDA\n//SYSPUNCH DD DSN=&OBJ,SPACE=(TRK,(1,1)),UNIT=SYSDA,\n//       DCB=(BLKSIZE=800,LRECL=80,RECFM=FB),DISP=(,PASS)   \n//SYSPRINT DD SYSOUT=A\n//SYSIN    DD *", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d597799c35c4-1", "text": "//SYSPRINT DD SYSOUT=A\n//SYSIN    DD *  \n  PROMMAC  'CNTL=START,PROM=20,PROX=5'\n  PROMMAC  'CNTL=ABP,ON,T321'\n  PROMMAC  'CNTL=ON,PROG=(CFIL,TERMIO,FILEIO,ERRORS,SCAN,LLASRCH),\n            USR=.ANY'  \n  PROMMAC  'CNTL=EXCL,PROG=(TERMIO,FILEIO)'\n  PROMMAC  'CNTL=ON,PROG=PBMASTER,FOL=ON,USR=.ANY'\n  PROMMAC  'CNTL=PURGE,INTRVAL=0100',END\n  END\n/*      \n//LINK  EXEC  PGM=IEWL,PARM='LIST,XREF,MAP',REGION=512K\n//SYSLMOD  DD DSN=CAI.CAVHLOAD(PROMAC),DISP=SHR\n//SYSUT1   DD UNIT=SYSDA,SPACE=(TRK,(10,10))\n//SYSPRINT DD SYSOUT=A\n//SYSLIN   DD DSN=&&OBJ,DISP=(OLD,DELETE)\n//\nNOTE\nA CICS program definition named PROMAC is required for the generated table.\nEnter CNTL Commands from a CRLP-Type Terminal\nIf you have at least one CRLP-type terminal defined in your TCT, the input sequential file can contain CNTL commands.\nThese commands are executed in sequence as if they were entered manually from a terminal. Responses to these\ncommands are written in the terminal output sequential file.\nTo reduce the amount of time required to process large numbers of CNTL commands, perform the following steps:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d597799c35c4-2", "text": "1.Create a load module that contains the CNTL commands to be processed using the PROMMAC macro.\n2.Add a PPT entry for the load module.\n 252", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6ba65dd59d69-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n3.Set the following InterTest for CICS options:\nRECNTMU=NO\nRECNTNW=NO\n4.Replace the CNTL commands in the sequential input with the following command:\nCNTL=START,PROM=name\nWhere name is the name of the module that was created in Step 1.\nNOTE\nTo assign the entries to a specific user ID, you can add the USR= option to any embedded CNTL=ON\ncommands . See CNTL Commands and Menus  .\nCalls to Software and User Macro Support\nThis section explains how to support software (which must not be monitored by InterTest for CICS) that is invoked by\nCALLs from your application programs or your own macros. For example:\n\u2022To support global routines with addresses found in the CWA, and that are given control from monitored programs by a\nBALR 14,14 or BALR 14,15 instruction. When such routines are given control, they are not monitored by InterTest for\nCICS until they return to the next byte after the BALR in the calling program.\n\u2022To make InterTest for CICS recognize a call (a COBOL or PL/I CALL verb or the Assembler CALL macro) to specific\ninterfaces (such as database systems), and execute the call without monitoring the interface code.\nIn both cases, optional routines can be coded to do the following:\n\u2022Check the parameters before the global routine is given control\n\u2022Display InterTest for CICS automatic breakpoints with error codes defined by you\nWARNING\nInterTest for CICS assumes that the global routine of the CALL interface always returns control to the point of\nthe CALL. If it does not, the user-written routine is mandatory.\nHow Support Is Provided", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6ba65dd59d69-1", "text": "the CALL. If it does not, the user-written routine is mandatory.\nHow Support Is Provided\nTo provide support, code a few lines of Assembler source code using the IN25UEX macros delivered in the\nCAI.CAVHMAC library. (The next section explains how to code these macros.) Then run assembly and link-edit steps to\ncreate the IN25UEXI module.\nThe macros create a table that, in addition to identification names and other information, contains references to the\nsame routines that get link-edited with application programs because of CALLs issued by application programs. These\nreferences are resolved at link-edit time.\nThe IN25UEXI module consists of the table and the same modules that are usually link-edited with application programs.\nIn the IN25UEXI, however, these modules are never executed. They only exist to compare a piece of their code with the\ncode in the application load module.\nInterTest for CICS uses the IN25UEXI module to compare the two pieces of code: the one link-edited with the IN25UEXI\nand the one that is about to receive control from the application program. The compared pieces of code are at the offset\n(from the entry point) and the length specified in the IN25UEX macros. If a large piece of code is involved, there is no\nneed to include all of it with the IN25UEXI; include just enough to make the comparison. The comparison is made when a\nBALR 14,15 or BALR 14,14 instruction (for XA, BASSM or BASR instruction) is about to be executed.\nIf the code matches and there is no associated routine (defined in the IN25UEXI), InterTest for CICS drops monitoring and\nproduces a standard InterTest for CICS entry in the CICS Trace Table (USER 144 code) with the identifier found in the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6ba65dd59d69-2", "text": "corresponding entry in the IN25UEXI module. Monitoring resumes only upon return from the called module to the CALL\nstatement.\n 253", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bceeec6619d8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIf there is a user-defined routine, the routine is performed first. The routine can check the CALL parameters and decide\nwhether a particular interface should be given control or an automatic breakpoint should occur (if the CALL is incorrect),\nand whether monitoring should continue when the interface returns to the calling program.\nIN25UEXI routines receive control in:\n\u2022AMODE31\n\u2022EXECKEY (CICS)\n\u2022BASESPACE MODE\nCode IN25UEX Macros for Called Software\nThe entry points are specified by using one of the following formats:\nIN25UEX CALL=entry1,ROUT=routine,LENGTH=xx,DISP=xx,ID=xx\n   \"      \"    \"\n   \"      \"    \"\nor\nIN25UEX CALL=(entry1,......,entryn)\n   \"      \"    \"\n   \"      \"    \"\nIN25UEX TYPE=FINAL                   (REQUIRED)\n place optional routines here\nCALL=entry1\nThis required parameter specifies the name of an entry point. Specify the same name used in your COBOL or PL/I CALL\nstatement or Assembler CALL macro, or specify an arbitrary name.\nA name specified in this CALL parameter is displayed on the InterTest for CICS Request Breakpoint menus and on the\nCNTL=INQ reports.\nAs shown in the second format, multiple entry point names can be specified, however the optional parameters that are\nlisted next cannot be used.\nWARNING\nDo not specify entry points used in a CALL that is the result of an EXEC CICS.\nROUT=routine\nThis optional parameter specifies the name of your special routine. If there is no routine, omit this parameter.\nLENGTH=xx\nThis optional parameter specifies the length (in decimal) of the comparison. The maximum length is 64 and the default", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bceeec6619d8-1", "text": "length is 16. The default is usually sufficient.\nDISP=xx\nThis optional parameter specifies the offset (in decimal) from the entry point of the code to be compared. The maximum\noffset (displacement) is 512; the default offset is 0.\nID=xx\nThis optional parameter specifies the identification value for the InterTest for CICS entry in the CICS Trace Table. Like\nall such entries produced by InterTest for CICS, the first byte contains the character C (USER 144), field A contains the\n 254", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b572cce1c3e8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\ndisplacement, and field B contains the characters US followed by the two characters specified in this parameter. If the ID=\nparameter is not specified, InterTest for CICS generates a value.\nAfter IN25UEXI is link-edited, verify the total size of the result as shown in the link-edit listing. There is no need to include\nentire interface modules in the IN25UEXI, as the comparison occurs only for the specified (or default) length at the\nspecified (or default) offset. If the IN25UEXI module is too large, you can code little Assembler CSECTs that identically\nreplace the ones used by applications in IN25UEXI. This technique has been used in the pregenerated version of\nIN25UEXI. Its source code is provided in the CAI.CAVHJCL source library in member UEXIDB2. This technique has\nreduced the size of IN25UEXI from approximately 30 KB to just 192 bytes.\nSupport Your Site Global Routines\nThis section does not apply to most InterTest for CICS sites. This section applies to global routines that are given control\nby the following two machine instructions:\nL     14,CWALABEL\nBALR  14,14\nWhere  CWALABEL is the label of a field in the CWA that contains the address of the global routine.\nTo specify entry points, use one of the following formats:\n  ********** CWA USER DSECT REQUIRED HERE **********\n      USING CWADS,0 CA INTERTEST REQUIREMENT\n      CWADS  DSECT          USER CWA\n      CWAFLD1    DS CL20\n      CWAENT1    DS F       USER ROUTINE\n      CWAFLD3    DS CL100\n ************ CA INTERTEST SPECIFICATIONS *************", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b572cce1c3e8-1", "text": "CWAFLD3    DS CL100\n ************ CA INTERTEST SPECIFICATIONS *************\n      IN25UEX CWAD=label1,ROUT=routine,ID=xx\n         \"      \"    \"\n         \"      \"    \"\n      IN25UEX CWAD=labeln\n      IN25UEX TYPE=FINAL                        (REQUIRED)\n        place optional routines here\n       or\n      IN25UEX CWAD=(label1,.....,labeln)\n      IN25UEX TYPE=FINAL                            (REQUIRED)\n      place optional routines here\nCWAD=cwadadr\nThis required parameter specifies a label that is defined in the CWA and contains the address of the entry point of a piece\nof commonly used code, such as a date conversion routine. For example, if the routine address is 20 bytes from the\nbeginning of the CWA, you can code:\nIN25UEX CWAD=(CWADS+20)\nMultiple entry point names can be specified as in the second format; however, if specified in this manner, the optional\nparameters listed next cannot be used.\nROUT=routine\nThis optional parameter is used as in the CALL= form.\n 255", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b7a9d8c7521c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nID=xx\nThis optional parameter is used as in the CALL= form.\nCode the ROUT= Routine\nThe ROUT= parameter coded in the IN25UEX macro specifies the name of a routine that is performed by InterTest for\nCICS prior to the execution of the IN25UEXI-supported CWA routine or CALL. The routines are coded in Assembler after\nthe IN25UEX TYPE=FINAL control card. CICS commands are not allowed.\nEach routine must be a CSECT whose name is specified by the ROUT= keyword. When InterTest for CICS passes control\nto the routine, the registers are set as follows:\nR0 = 0\nR1 = address of the BALR instruction\nR2 = address of the called routine that is about to receive control by the BALR (or, for XA, by BASSM or BASR)\nR3 = address of the InterTest for CICS work area\nR4 = undetermined\nR5 = undetermined\nR6 = undetermined\nR7 = undetermined\nR8 = undetermined\nR9 = address of an eight-byte field that contains the name specified in the CALL= or CWAD= parameter\nR10 = undetermined\nR11 = undetermined\nR12 = user's TWA address\nR13 = EIB address\nR14 = return address for this routine\nR15 = entry point address for this routine\nNOTE\n\u2022In XA or ESA systems, this routine receives control in the same AMODE (Addressing mode 24 or 31) that the\nbranch instruction had before execution.\n\u2022Registers 3 and 14 must not be changed by the routine. If these registers are used, they must be saved and\nrestored by the routine.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b7a9d8c7521c-1", "text": "restored by the routine.\n\u2022The application program registers 0 to 15 (Before the branch instruction execution) are at 96 (X'60') bytes\npast the address in register 3.\nIn addition to checking application-related parameters, the routine must determine if InterTest for CICS should continue\nmonitoring. Monitoring must not continue if the code that is called by the monitored program does not return control to the\nnext byte after the BALR instruction.\nBefore the routine returns to the address in register 14, it must set register 0 to one of the following values:\n0\nExecute the CALL without monitoring.\n 256", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c31b1d8829fd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nX'D0' X'FF'\nInterTest for CICS should issue an automatic breakpoint with this error code.\n-1\nThe routine does not return control to the next byte after the BALR; therefore monitoring must be dropped.\nAny other negative value\nInterTest for CICS should monitor the called piece of code.\nSample JCL for Generating IN25UEXI Programs\nThis example shows a call to the global routine CWAENT1, which has an associated routine called MYCHECK.\n//IN25UEXI JOB (123,45),USERID,MSGCLASS=A,TIME=(,09)\n//ASM      EXEC PGM=ASMA90,REGION=1024K,\n//         PARM='DECK,LIST,XREF(SHORT),ALIGN'\n//SYSPRINT DD  SYSOUT=A\n//SYSPUNCH DD  DSN=&&LOADSET,DISP=(NEW,PASS),UNIT=SYSDA,\n//            DCB=(RECFM=FB,LRECL=80,BLKSIZE=400),SPACE=(400,(100,100,1))\n//SYSLIB   DD  DSN=CAI.CAVHMAC,DISP=SHR\n//SYSUT1   DD  UNIT=SYSDA,SPACE=(CYL,(5,1))\n//SYSUT2   DD  UNIT=SYSDA,SPACE=(CYL,(5,1))\n//SYSUT3   DD  UNIT=SYSDA,SPACE=(CYL,(5,1))\n//SYSIN    DD  *\n********** CWA USER DSECT REQUIRED HERE **********\n        USING CWADS,0   CA INTERTEST REQUIREMENT    \nCWADS    DSECT      USER CWA    \nCWAFLD1  DS CL20", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c31b1d8829fd-1", "text": "CWAFLD1  DS CL20    \nCWAENT1  DS F       USER ROUTINE    \nCWAFLD3  DS CL100   \n************ CA INTERTEST SPECIFICATIONS *************\n*\n*    INSERT YOUR IN25UEX STATEMENTS HERE\n*\n      IN25UEX CWAD=CWAENT1,ROUT=MYCHECK\n      IN25UEX TYPE=FINAL\n*\n*    INSERT USER WRITTEN ROUTINES HERE\n*        TITLE 'ROUTINE TO CHECK CWAENT1'\nMYCHECK CSECT\n        USING MYCHECK,15          ESTABLISH ADDRESSABILITY\n        L     4,X'60'+4(,3)       OBTAIN APPLICATION'S REGISTER 1\n        LTR   4,4                 IS REGISTER 1 ZERO ?\n        BZ    RETOKAY             YES, NOTHING MORE TO CHECK.\n        L     4,0(,4)             PICK UP 1ST ADDR FROM PARM LIST\n        LTR   4,4                 IS THE HIGH ORDER BIT ON ?\n        BM    ONLYONE             YES, ONLY ONE PARAMETER.\n        CLC   =C'FINAL',0(4)      1ST PARAMETER SAYS 'FINAL' ?\n        BNE   NOFINAL             NO, TREAT SEPARATELY.\n        LH    0,=H'-1'            YES, INDICATE 'DROP MONITORING'\n        BR    14                  AND RETURN TO CA INTERTEST.\n 257", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d4f01a182369-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n NOFINAL CLI   0(4),C'0'           1ST CHARACTER NUMERIC ?\n        BNL   RETOKAY             YES, GO CONTINUE NORMALLY.\n        LH    0,=H'-2'            NO, KEEP MONITORING THE CALLED-\n        BR    14                    - ROUTINE. \n ONLYONE CLI   0(4),C'X'           1ST CHARACTER EQUAL TO \"X\"\n        BE    RETOKAY             YES, GO CONTINUE NORMALLY.\n        LA    0,X'E5'             NO,DO A BREAKPOINT WITH CODE E5\n        BR    14                  AND RETURN TO CA INTERTEST.\n RETOKAY SR    0,0                 INDICATE 'CONTINUE NORMALLY'\n*                                 (DO NOT MONITOR THE CALL)\n        BR    14                  AND RETURN TO CA INTERTEST.\n        LTORG                     TERMINATES THE ROUTINE. \n*\n*      CODE ANY ADDITIONAL ROUTINES HERE\n*\n        END                       TERMINATES THE ASSEMBLY OF IN25UEXI\n/*\n//LKED     EXEC PGM=IEWL,REGION=512K,PARM=(XREF,LIST,MAP)\n//SYSLMOD  DD  DSN= yourlib,DISP=SHR\n//SYSUT1   DD  UNIT=SYSDA,DCB=BLKSIZE=1024,SPACE=(1024,(200,200))\n//SYSPRINT DD  SYSOUT=A\n//SYSLIN   DD  DSN=&&LOADSET,DISP=(OLD,DELETE)\n//         DD *\n    ENTRY IN25UEXI\n    NAME IN25UEXI(R)    \n//", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d4f01a182369-1", "text": "ENTRY IN25UEXI\n    NAME IN25UEXI(R)    \n//\nThe IN25UEXI module created by the previous jobstream is used by the monitor program of InterTest for CICS. To install\nthis module, perform the following steps:\n1.Terminate InterTest for CICS (You can issue the InterTest for CICS checkpoint command before you teminiate\nInterTest for CICS).\n2.Issue a CEMT SET PROG(IN25UEXI) NEWCOPY command for the new copy.\n3.Issue a CEMT SET PROG(IN##PGM2) NEWCOPY command for the new copy.\n4.Start or restart InterTest for CICS.\nNOTE\nReplace ## with your two-digit CICS release number:\n\u202268 for CICS 5.1\n\u202269 for CICS 5.2\n\u202270 for CICS 5.3\n\u202271 for CICS 5.4\n\u202272 for CICS 5.5\n\u202273 for CICS 5.6\n\u202274 for CICS 6.1\nIN25UEXI Instructions for other Vendor Products\nThis section lists IN25UEXI instructions for the following vendor products:\n 258", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "30f3c67bb33d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Calls for COMPUTATIONS users\n\u2022Calls for SHRINK users\n\u2022Calls for Patient Care System (PCS) users\n\u2022Calls for HOGAN users\n\u2022Calls for InterTest users\nCalls for COMPUTATIONS Users\nTo handle a call to the COMPUTATIONS package, code the IN25UEX control statement as follows:\nIN25UEX CALL=MGCALL,DISP=12,LENGTH=8\nAlso add an INCLUDE MSSECALL in your link-edit step.\nYou should exclude the COMPUTATIONS program from monitoring. To do this, issue the CNTL=EXCL,PROG=PS* and\nCNTL=EXCL,PROG=PE* commands.\nCalls for SHRINK Users\nTo handle calls to SHRINK, code the IN25UEX control statements as follows:\nIN25UEX CALL=SHRINK\nIN25UEX CALL=EXPAND\nIN25UEX CALL=PUFFUP\nIN25UEX CALL=PUFFDOWN\nIN25UEX CALL=CLOSE\nWhere SHRINK, EXPAND, PUFFUP, PUFFDOWN, and CLOSE are the entry points.\nCalls for Patient Care System (PCS) Users\nTo handle calls to PCS, uncomment the COPY statement provided in the IN25UEXI member in CAI.CAVHSAMP:\n***         COPY PCSUEXI\nCalls for HOGAN Users\nTo handle calls to HOGAN, add this COPY statement to the IN25UEXI member in CAI.CAVHSAMP:\nCOPY UEXIHOGN\nAdd the HOGAN.MACLIB to the ASSEMBLY step's SYSLIB.\nAdd the HOGAN.LOADLIB to the SYSLIB of the LKED step.\nCalls for InterTest Users", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "30f3c67bb33d-1", "text": "Calls for InterTest Users\nTo handle calls to InterTest, add this copy statement to the IN25UEXI member in CAI.CAVHSAMP:\nCOPY UEXIVG\nDB2 Support\nDB2 Application Program Support\nThe installation procedure is explained next. For information on how to test and debug DB2 application programs with\nInterTest for CICS, see CICS Debugging  .\n 259", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fa7bf38ffc2c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUsing the Pregenerated Version -- A pregenerated IN25UEXI with DB2 support is provided. If you have no other special\nsoftware situations that the IN25UEXI program handles, there are no further installation steps to perform for DB2 support.\nCreating the IN25UEXI Module for DB2  -- To monitor application programs that issue SQL calls, a special program\nnamed IN25UEXI must exist in your InterTest for CICS load library. A pregenerated version of IN25UEXI, assembled for\nDB2 Release 10.1 and above, is provided.\nYou can also use the IN25UEXI program to support calls to programs that are not to be monitored by InterTest for CICS.\nIf you have programs that issue calls, or require special handling, review the section Calls to Software and User Macro\nSupport. In this case, you must combine the two uses in one IN25UEXI.\nThe source code for the preassembled version of IN25UEXI with DB2 support is provided in the member UEXIDB2 in the\nCAI.CAVHMAC library.\nThe following JCL example creates the IN25UEXI module for combined DB2 and special uses. Modify this example to\nmeet your system requirements.\n//IN25UEXI JOB ...\n//ASM      EXEC PGM=ASMA90,REGION=1024K,\n//         PARM='DECK,LIST,XREF(SHORT),ALIGN'\n//SYSPRINT DD  SYSOUT=A\n//SYSPUNCH DD  DSN=&&LOADSET,DISP=(NEW,PASS),UNIT=SYSDA,\n//           DCB=(RECFM=FB,LRECL=80,BLKSIZE=400),SPACE=(400,(100,100,1))", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fa7bf38ffc2c-1", "text": "//SYSLIB   DD  DSN=CAI.CAVHMAC,DISP=SHR\n//SYSUT1   DD  UNIT=SYSDA,SPACE=(CYL,(5,1))\n//SYSUT2   DD  UNIT=SYSDA,SPACE=(CYL,(5,1))\n//SYSUT3   DD  UNIT=SYSDA,SPACE=(CYL,(5,1))\n//SYSIN    DD  *\n      COPY UEXIIDMS      CA IDMS\n      COPY UEXIDATA      CA DATACOM\n      COPY UEXITELN      CA TELON\n      COPY UEXISORT      CA SORT\n      COPY UEXIMAST      CA MASTERPIECE\n      COPY UEXIDB2       DB2\n      COPY UEXICPSM      CICSPLEX SM\n      COPY UEXISOKT      TCP/IP SOCKETS\n*\n*    INSERT YOUR IN25UEX STATEMENTS FOR SPECIAL CALLS HERE\n*\n      IN25UEX TYPE=FINAL\n*\n*    INSERT ANY USER WRITTEN ROUTINE HERE\n*\n      END               TERMINATES THE ASSEMBLY OF IN25UEXI\n/*\n//LKED EXEC PGM=IEWL,REGION=512K,PARM=(XREF,LIST,MAP)\n*\n* INSERT ANY //SYSLIB STATEMENTS FOR SPECIAL LOADLIBS HERE\n*\n//SYSLMOD DD DSN=yourlib,DISP=SHR\n//SYSUT1 DD UNIT=SYSDA,DCB=BLKSIZE=1024,SPACE=(1024,(200,200))\n//SYSPRINT DD SYSOUT=A\n//SYSLIN DD DSN=&&LOADSET,DISP=(OLD,DELETE)\n//       DD *\n       ENTRY IN25UEXI\n 260", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "606273469fb5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    NAME IN25UEXI(R)    \n//\nThe IN25UEXI module created by the previous jobstream is used by the monitor program of InterTest for CICS. To install\nthis module, you must perform the following steps:\n1.Terminate InterTest for CICS (you can issue the InterTest for CICS checkpoint command before terminating InterTest\nfor CICS).\n2.Issue a CEMT SET PROG(IN25UEXI) NEW command for the new copy.\n3.Issue a CEMT SET PROG(IN##PGM2) NEW command for the new copy.\n4.Start or restart InterTest for CICS.\nNOTE\nReplace ## with your two-digit CICS release number:\n\u202268 for CICS 5.1\n\u202269 for CICS 5.2\n\u202270 for CICS 5.3\n\u202271 for CICS 5.4\n\u202272 for CICS 5.5\n\u202273 for CICS 5.6\n\u202274 for CICS 6.1\nMonitor DB2 Applications\nA pregenerated version of IN25UEXI, assembled for DB2 Releases 10.1 and above, is provided in your InterTest for CICS\nload library.\nIf you do not have other special software situations to be handled by the IN25UEXI program, you do not need to perform\nadditional installation steps for DB2 support. However, if you have programs that issue calls or require special handling,\nsee Calls to Software and User Macro Support.\nSupport DB2 Calls in the FILE and CORE Facilities\nThe FILE facility supports dynamic SQL calls to DB2. This feature lets users view, alter, add, or delete data in DB2 tables\nwithout  leaving CICS. The CORE facility lets you view the last SQL statement executed (CORE=LASTSQL).", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "606273469fb5-1", "text": "The pregenerated versions of IN25AIDB and IN25FIDB are preassembled with DB2 Release 10.1.\nHandle Wild Branches\nWhen a monitored program passes control to another program directly by a branch instruction, bypassing the CICS\nservices of an XCTL or a LINK macro or command, InterTest for CICS treats this as a wild branch (branching outside\na module) and causes an automatic breakpoint. Such direct passing of control, although not advised by CICS coding\nstandards, is used frequently in some applications.\nYou cannot monitor just the program receiving control by a direct branch from another program. To monitor a receiving\nprogram, you must also monitor the program passing control to it. Monitoring can begin only with the program that\noriginally received control from CICS.\nMost often, the program receives control by a direct branch caused either by a CALL statement or by a special macro.\nUsually, such code should not be monitored by InterTest for CICS. See the section Calls to Software and User Macro\nSupport  for an explanation of how to make InterTest for CICS drop monitoring in such cases.\n 261", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a3efe2a6425a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMonitor a Wild Branch\nIf the program that receives control should be monitored and you want to debug it with InterTest for CICS, there are three\npossible situations:\n\u2022The receiving program resides in the same load module as the program that passes control. In this situation, use\nthe composite support facility of InterTest for CICS. This facility lets you debug a subprogram as if it were a separate\nprogram, and supports all language combinations.\n\u2022The receiving program resides in another load module that has a CICS program definition. In this situation, use\nthe FOL=CICS-program-definition-name online option and, if needed, composite support. This approach makes all\nInterTest for CICS debugging features available for the branched-to program.\nNOTE\nFor COBOL II dynamically called programs, the FOL= option is not needed. Set breakpoints in the dynamically\ncalled program as you would for any other CICS program.\n\u2022The receiving program resides elsewhere and has no CICS program definition. In this situation, use the FOL=ON\nonline option. In this case, breakpoints can be set for addresses, not offsets, and symbolic InterTest for CICS support\nis not available.\nUse the FOL=ON Option\nWe strongly advise that the FOL=ON online option be applied only at the program level; that is, monitoring declared with\na CNTL=ON,PROG= command as opposed to CNTL=ON,TRAN= or CNTL=ON,TERM= commands. This allows online\noptions to be used in the most convenient way, with different options such as breakpoints declared for different programs.\nIf necessary, the FOL=ON online option can also be specified at the terminal or transaction level.\nAdd COBOL File Structures to the Symbolic File", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a3efe2a6425a-1", "text": "Add COBOL File Structures to the Symbolic File\nThe COBOL  program shown next is an example of a dummy default program that contains 01 level structures. Saving\nall of the 01 level structures used at a site in one file allows users of the FILE transaction to omit the symbolic program\nname when requesting records or DL/I segments in structured format. Symbolic information for the default program must\nbe saved in the symbolic file, and its name must be referenced in the FSYMP installation option. The default name is\nPROTFILE.\n//PROTFILE JOB (NTSM,473),'JOHN BROWN',CLASS=D,MSGCLASS=A \n//*\n//COB      EXEC PGM=IGYCRCTL,REGION=1024K, \n//   PARM='OBJECT,APOST,FLAG(I,W),LIST,XREF,MAP,NOOPT,VBREF' \n//STEPLIB  DD DSN=SYS1.COB2COMP,DISP=SHR \n//SYSLIB   DD DSN=CICS.COBLIB,DISP=SHR \n//SYSLIN   DD DSN=&&LOADSET,DISP=(MOD,PASS), \n//           UNIT=SYSDA,SPACE=(80,(250,100)) \n//SYSUT1   DD UNIT=SYSDA,SPACE=(460,(350,100)) \n//SYSUT2   DD UNIT=SYSDA,SPACE=(460,(350,100)) \n//SYSUT3   DD UNIT=SYSDA,SPACE=(460,(350,100)) \n//SYSUT4   DD UNIT=SYSDA,SPACE=(460,(350,100)) \n//SYSUT5   DD UNIT=SYSDA,SPACE=(460,(350,100))", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a3efe2a6425a-2", "text": "//SYSUT6   DD UNIT=SYSDA,SPACE=(460,(350,100)) \n//SYSUT7   DD UNIT=SYSDA,SPACE=(460,(350,100)) \n//SYSPRINT DD DSN=&&TEMPIN,DISP=(,PASS),UNIT=SYSDA,SPACE=(TRK,(15,5)), \n//        DCB=(DSORG=PS,LRECL=133,BLKSIZE=1330,RECFM=FBA) \n//SYSIN    DD *\n       ID DIVISION.\n       PROGRAM-ID. PROTFILE.\n       ENVIRONMENT DIVISION.\n 262", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "68d9689c923b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n       DATA DIVISION.\n       WORKING-STORAGE SECTION.\n       77  PROGRAM-NAME       PIC X(8) VALUE 'PROTFILE'.\n       LINKAGE SECTION.\n       **  CAR SEGMENT  **\n        01  CAR.\n           05  CAR-SEGMENT-KEY-FIELD.\n               15  CAR-SEGMENT-MAKE    PIC X(12).\n           05  CAR-SEGMENT-MODEL       PIC X(12).\n           05  CAR-SEGMENT-TYPE        PIC X(10).\n           05  CAR-SEGMENT-WEIGHT      PIC S9(5)      COMP-3.\n           05  CAR-SEGMENT-CYLINDRS    PIC S9(3)      COMP-3.\n      **  DEALER SEGMENT  **\n        01  DEALER.\n           05  CAR-DEALER-SEGMENT-KEY.\n               15  CAR-DEALER-SHORT-NAME PIC X(9).\n               15  CAR-DEALER-TIEB     PIC S999       COMP-3.\n               15  CAR-DEALER-NBRWD    PIC S9         COMP-3.\n           05  CAR-DEALER-FIRST-NAME   PIC X(24).\n        PROCEDURE DIVISION.\n           MOVE 'PROTFILE' TO PROGRAM-NAME.\n           GOBACK. \n//* \n//SYMSTEP  EXEC PGM=IN25COB2,REGION=1024K \n//STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR \n//INPUT    DD DSN=&&TEMPIN,DISP=(OLD,DELETE)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "68d9689c923b-1", "text": "//INPUT    DD DSN=&&TEMPIN,DISP=(OLD,DELETE) \n//OUTPUT   DD SYSOUT=A,DCB=(RECFM=FBA,LRECL=133,BLKSIZE=1330) \n//MESSAGE  DD SYSOUT=A \n//PROTSYM  DD DSN=** your protsym file **,DISP=SHR \n//CARDS    DD * \nPROTFILE,LISTER=ALL,NOPURGE \n//*\nIn the STEPLIB DD statement on the symstep specify the name of the library that contains the Testing and Fault\nManagement Symbolic component.\nNOTE\nA similar job can be used for COBOL/VS.\nDeclare User-Defined CORE Commands\nThis section explains how to define your own CORE keywords. User-defined CORE keywords provide a shorthand\nmethod for entering a complex CORE command by specifying a simple command that contains one or more of your own\nkeywords. The new keyword is automatically replaced with a string of command elements that could otherwise be difficult\nto remember.\nAmong the new commands can be some to display your own areas in main storage, such as crucial control tables for\nrunning an application system. If your replacement command includes the USE= element, the storage areas can be\ndisplayed as COBOL or Assembler structures, with names and offsets attached to each data field.\nFor details, see the InterTest for CICS Help facility. Select the CORE Facility, then Structured Data Displays, and then\nAdditional Features.\n 263", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "96cf2a171746-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCORUCOM Macro\nThe CORUCOM macro lets you define any number of new CORE command keywords, each an abbreviation for a series\nof CORE command elements. For instance, there is a user table that is pointed to by an address located eight bytes into\nthe CWA. There is a counter 12 bytes into this table that contains the number of times a service request transaction was\nissued. Add the following CORUCOM entry and assemble the CORUCOM table:\nCORUCOM CODE=SERVCNT,COMND=CWA@8+C\nTo display the service request count online, issue:\nCORE=SERVCNT\nCode one CORUCOM macro for each new CORE keyword. Submit the resulting source code to assemble a new InterTest\nfor CICS load module named IN25UCOM. The module is used by the CORE facility as a table to convert your own\nkeywords into strings of CORE keywords.\nSince the CORUCOM macro generates a separate CICS load module, you can add new or modified commands at any\ntime. To do this, code the commands, assemble the module, and then do a NEWCOPY for the load module IN25UCOM\nby issuing:\nCEMT SET PROG(IN25UCOM) NEWCOPY\nCode the CORUCOM Macros\nThe CORUCOM macro is delivered in the CAI.CAVHMAC library. The first CORUCOM statement must be coded as\nfollows:\nCORUCOM TYPE=INITIAL\nThe last CORUCOM statement must be coded as follows:\nCORUCOM TYPE=FINAL\nEach user-defined CORUCOM statement specifies one user-defined element of the CORE command and one string of\nCORE commands that will replace that user-defined element.\nThe user-defined element is specified by the CODE= keyword. Each element keyword must be less than eight characters", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "96cf2a171746-1", "text": "long, must consist only of alphanumeric characters and, to prevent confusion with a hexadecimal number, must contain\nat least one of these characters: GHIJKLMNOPQRSTUVWXYZ. When two or more keywords have the same prefix (for\nexample, ICE2, ICE), the longer keyword must be specified first, as illustrated in the following example.\nThe string of CORE command elements is specified by the COMND= keyword. The string must be enclosed in\napostrophes and, within the string, any apostrophe must be coded as two apostrophes. All elements of the CORE\ncommand are permitted, including other user-defined elements. In the following example:\n\u2022The new keyword ICE2 (second macro) uses another new keyword ICE (in the third macro). Notice that the longer\nkeyword is specified first.\n\u2022The fourth macro defines the keyword MYTABLE, which displays a storage area pointed to by the address in the\nCWA, and produces a display formatted as a structure named MYTABLE in the InterTest for CICS symbolic file records\nidentified by the name MYSYMDEF. For more details, see the section Adding Assembler DSECTs to the symbolic file.\n\u2022The * in column 72 means continuation.\n               1     1                                            7\n COL= 1...5....0.....6............................................2\n               CORUCOM TYPE=INITIAL   (required)\n               CORUCOM CODE=ICE2,COMND='ICE@4'\n               CORUCOM CODE=ICE,COMND='=CSA@54'\n               CORUCOM CODE=MYTABLE,COMND='=CWA@8,USE=MYSYMDEF.MYT*\n 264", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "930230866849-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                     ABLE'\n               CORUCOM TYPE=FINAL     (required)\nSample JCL for Assembling IN25UCOM\nThe following IN25UCOM JCL example uses the standard IBM procedure to assemble and link-edit macro level programs.\n//UCOM JOB ...\n//*  (COMMENT: A STANDARD IBM PROC FOR ASSEMBLER MACRO LEVEL)\n//STEP  EXEC ASMFCL//ASM.SYSLIB DD DSN=CAI.CAVHMAC,DISP=SHR\n//ASM.SYSIN  DD *\n      CORUCOM TYPE=INITIAL\n*     YOUR FIRST CORUCOM STATEMENT GOES HERE\n         ..   .....\n      CORUCOM TYPE=FINAL\n      END\n/*\n//LKED.SYSLMOD DD DSN=CAI.CAVHLOAD,DISP=SHR\n//LKED.SYSIN DD *\n       NAME IN25UCOM(R)\n /*\n//\nNOTE\nThe IN25UCOM member of the InterTest for CICS source library contains sample source for assembling the\nIN25UCOM load module.\nSample JCL for Defining CORE Keywords\nAfter you have added the necessary members to the symbolic file, run a job to define the commands needed to access\nyour DSECTs. The sample job below uses CORUCOM macros to define the user CORE keyword TWAF. For more\ninformation, see Declare User-Defined CORE Commands.\n//UCOM JOB ...\n//*  (COMMENT: A STANDARD IBM PROC FOR ASSEMBLER MACRO LEVEL)\n//STEP  EXEC ASMFCL\n//ASM.SYSLIB   DD  DSN=CAI.CAVHMAC,DISP=SHR\n//ASM.SYSIN  DD  *\n        COPY CORUCOM\n        CORUCOM TYPE=INITIAL", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "930230866849-1", "text": "COPY CORUCOM\n        CORUCOM TYPE=INITIAL\n        CORUCOM CODE=TWAF,COMND='TWA,USE=USERDSEC.USERTWAF'\n        CORUCOM TYPE=FINAL\n        END\n/*\n//LKED.SYSLMOD     DD DSN=CAI.CAVHLOAD,DISP=SHR\n//LKED.SYSIN       DD  *\n        NAME IN25UCOM(R) \n/*\n//\nSpecial Considerations for HOGAN Systems\nInterTest for CICS features are available for debugging HOGAN applications, including symbolic support if the InterTest for\nCICS post-compile step was executed.\n 265", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aa493ea923b3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse Considerations\nMonitoring the PEM Module  -- The PEM module does not need to be debugged and should not be monitored by\nInterTest for CICS. Monitor only your HOGAN application programs using the segmented monitoring option, as discussed\nnext.\nMonitoring Application Programs that use HOGAN  -- Application programs that use HOGAN should be monitored only\nby using the InterTest for CICS segmented monitoring options. Do not monitor such programs by transaction or terminal\nname, or by global monitoring. CICS Debugging  explains how to use segmented monitoring.\nThe USH=ON monitoring option must also be used to prevent unnecessary automatic breakpoints from occurring.\nAll of the InterTest for CICS online options are available. However, the FOL= option should not be used. It is advisable to\nlearn how to use the BYP= option and the PF11 override option.\nInstallation Procedure\nTo install InterTest for CICS for HOGAN support, first complete all of the required steps given in Configure Your Product\nwith CSM  and Installing Your Product Using Pax ESD or DVD. Then complete your installation by performing the following\nsteps.\n1.Create the IN25UEXI module for HOGAN. Instructions are given in the section IN25UEXI Instructions for Additional\nVendor Products.\nNOTE\nThis routine is customized for each release of HOGAN. To ensure compatibility, please contact Broadcom\nSupport .\n2.Enable the InterTest for CICS segmented monitoring options. To do this, you must set the MONOM installation option\nin the IN25OPTS module to either MENU or NOMENU. Optionally, you can enable password security for segmented\nmonitoring by setting the MONOMSEC installation option to YES.\nThis completes the installation for HOGAN support in a CTS environment.\nIBM's EXEC Debugging Facility (EDF) Support", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aa493ea923b3-1", "text": "IBM's EXEC Debugging Facility (EDF) Support\nThe EDF facility, which is activated by the CEDF transaction and described in the IBM CICS/VS Application Programmer's\nGuide Command Level , does not interfere with the InterTest for CICS monitoring and interactive testing. InterTest for CICS\nalso does not interfere with EDF, except when EDF presents the EDF breakpoint display of the program that is being\nmonitored by InterTest for CICS, EDF incorrectly indicates the location of the command since commands are issued by\nInterTest for CICS, not by the program.\nAdvantages of InterTest for CICS over EDF\nInterTest for CICS offers many advantages over the EDF facility, including the following advantages:\n 266", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2d64d4d62f11-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022The ability to set breakpoints anywhere in the program (not just at EXEC CICS commands).\n\u2022Data display and modification by symbolic names. This means the programmer does not need the most recent listing\nof the tested program, if the data names or paragraph names (labels in Assembler) remain the same.\n\u2022Monitoring, such as the ability to detect any illegal action of the program between CICS commands. CICS abends are\nintercepted by EDF, but damage may have occurred on the way to the abend and EDF may not give any specifics on\nthe problem.\n\u2022The ability to declare an unconditional or conditional breakpoint at a specific location -- the EXEC CICS call at the point\nwhen the EXEC CICS call parameters have already been formatted. At that time you can change the parameters (for\nexample, by issuing the CORE=ARGnn command) before you let the command execute.\n\u2022The ability to set request breakpoints for a particular type of CICS command regardless of where in the program\nit occurs, for all EXEC CICS commands, or for all except some EXEC CICS commands. For example, with one\nspecification you can set breakpoints at all File Control commands or at all READ or WRITE commands.\nUse InterTest for CICS with EDF\nIf you want to use InterTest for CICS with EDF, you can turn on EDF before you begin monitoring a program with InterTest\nfor CICS. Moreover, when a monitored program is stopped at a request breakpoint for an EXEC CICS command, you\ncan activate EDF by entering any character in the field marked EDF in the lower-right corner of the Detailed Breakpoint\ndisplay.\nWhen InterTest for CICS and EDF are being used on the same task, be aware of the following:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2d64d4d62f11-1", "text": "\u2022If an InterTest for CICS breakpoint is set at an EXEC CICS command, the InterTest for CICS breakpoint occurs before\nthe command is passed to CICS.\n\u2022At the breakpoint, the programmer can review and change any parameters of the command before telling InterTest for\nCICS to continue with the task.\n\u2022InterTest for CICS checks the parameters and, if necessary, halts the task at an automatic breakpoint.\n\u2022If that does not happen, the command is passed by InterTest for CICS to CICS for execution; that is, to the EXEC\ninterface.\n\u2022Subsequently, EDF presents the EDF breakpoint display of the program that is being monitored by InterTest for CICS,\nbefore a command breakpoint. The EDF facility, however, is in control at that time and any changes by the user during\nthe EDF breakpoint cannot be checked by InterTest for CICS.\n\u2022Only after the command is executed and a command EDF breakpoint display appears and EDF is told to continue with\nthe task can InterTest for CICS resume control and continue monitoring.\nSpecial Considerations for MRO Support\nTo use InterTest for CICS in an MRO environment, you must have the following items:\n\u2022All InterTest for CICS required CICS definitions in any CICS application-owning region (AOR) that will use InterTest for\nCICS for testing.\n\u2022A local program definition for IN25VIRC in the terminal-owning region (TOR).\n\u2022A local transaction definition for VIRC in the TOR; this transaction ID must be identical in the TOR and all AORs.\n\u2022One remote transaction definition for VTAT in the TOR for each AOR that will use InterTest for CICS. Of course, the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2d64d4d62f11-2", "text": "TOR's local VTAT transaction IDs must be unique (for example, VTA1, VTA2, VTA3, and so on). However, the remote\ntransaction IDs can be the same for all AORs (for example, VTAT), so you do not need to maintain a unique IN25OPTS\nfor each AOR. If you choose to specify an alternate VTAT transaction ID in one or more AORs, you must be sure to\nspecify the same alternate transaction ID in the TOR's remote VTAT transaction definition.\nIn addition, for all CICS regions that will use InterTest for CICS -- both AOR and TOR -- the transaction definition for VIRC\nmust specify the same transaction code.\n 267", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "39b9df372d20-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nA sample set of definitions is supplied in member CSDINTTO in CAI.CAVHJCL library. This sample set contains all of\nthe RDO definitions required for the CICS TOR region. All InterTest for CICS transaction names are the same as those\nspecified in the AOR and can be modified by your site.\nNOTE\nWe recommend that the InterTest for CICS CORE transaction be installed in the TOR as local to help system\nsupport staff resolve problems in that region.\nRemote transaction definitions can be defined for all transactions except VIRC, which can be started from the TOR to run\nin the AOR. Using these transaction definitions is usually preferable to starting routing sessions with the CRTE SYSID=\ntransaction.\nYou can add a transaction definition in each TOR.\nDEFINE  TRANSACTION(LNTL)\nWhere LNTL -- is a four-character transaction name for the InterTest for CICS CNTL transaction in the TOR:\nREMOTENAME(RNTL)\nWhere RNTL -- is a four-character transaction name for the InterTest for CICS CNTL transaction in the AOR:\nREMOTESYSTEM(TROW)\nWhere TROW -- the name under which the AOR is known to the TOR.\nNOTE\nRNTL and LNTL can be the same name.\nMonitor Considerations for DFLTUSER\nInterTest for CICS qualifies all monitoring entries with a CICS user ID. All monitoring entries use the form:\npromid.userid\nThe ATTACHSEC option of the CONNECTION entry in the CSD is used with the DFLTUSER= option setting in IN25OPTS\nto provide the granularity of monitoring required. Only the combinations of DFLTUSER and ATTACHSEC given in the\nfollowing table are supported:\nIN25OPTS DFLTUSER= CSD CONNECTION,", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "39b9df372d20-1", "text": "following table are supported:\nIN25OPTS DFLTUSER= CSD CONNECTION,\nATTACHSEC=Typical Use Additional Consideration\nANY LOCAL Nonsecure MRO environment AOR and TOR need the same\ndefault CICS user ID (set in the\nSIT)\nSPECIFIC IDENTIFY Secure MRO environment TOR's SIT uses SEC=YES or\nMIGRATE option\nThe following sections discuss each combination in detail.\nMonitor in a Nonsecure MRO Environment\nThe following combination says that monitoring and monitoring options should be set by terminal ID and not by CICS user\nID.\nDFLTUSER=.ANY\nATTACHSEC=LOCAL\nhis setting is typically used in a nonsecure MRO environment where the TOR's SIT uses the SEC=NO option. The user ID\npassed from the TOR is the TOR's default user ID as set in the SIT (typically CICSUSER).\n 268", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "561f6e315e93-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterTest for CICS compares this user ID to the AOR's default user ID and, if they match, sets the user ID to be monitored\nby .ANY user. This entry causes all users of the program to be monitored (as in earlier InterTest for CICS releases).\nWARNING\nEnsure that the default user IDs in the AOR and TOR are the same.\nMonitor in a Secure MRO Environment\nDFLTUSER=SPECIFIC\nATTACHSEC=IDENTIFY\nIn this case, the application's unique user ID is passed from the TOR to the AOR only if the ATTACHSEC option of the\nCONNECTION entry is IDENTIFY. This requirement and specifying DFLTUSER=SPECIFIC in IN25OPTS allows InterTest\nfor CICS to assign the user ID to each monitoring command as a default. This saves the user from having to type it in or\nspecify it, and allows InterTest for CICS to properly monitor user activity in the TOR.\nAdditional Monitoring Considerations\nThe CRT terminal that is to receive the InterTest for CICS breakpoint display is called the receiving terminal. After\nreceiving the display, the terminal remains ready to execute any InterTest for CICS command. However, until the user\ndisconnects from InterTest for CICS, it will accept only InterTest for CICS commands.\nThe receiving terminal must meet these specifications:\n\u2022IBM 3270-type CRT or compatible:\n\u2013The terminal must have ATI (automatic task initiation) capability.\n\u2013If its screen is larger than model 2, its default screen size (as defined in the TCT) must be 24 lines x 80 characters\n(the model 2 size)\n\u2022For two-terminal testing:\n\u2013The receiving terminal must be logged on to the TOR at the time the breakpoint is about to be displayed.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "561f6e315e93-1", "text": "\u2013At the time the first breakpoint display is about to appear, the receiving terminal must not be occupied by any task\n(transaction). This restriction also applies to CRTE.\n\u2013The next transaction ID must not be primed in the TCTTE of the receiving terminal. If this occurs, InterTest for CICS\ncannot write the breakpoint screen because CICS prevents automatic task initiation.\n\u2013The receiving terminal must not be occupied by an explicit routing session. (Explicit routing sessions are started by\nentering CRTE SYSID= and are normally ended by entering Cancel.) When necessary, InterTest for CICS starts a\nrouting session for the receiving terminal to allow the terminal to receive a breakpoint display.\n\u2013The terminal from which the tested transaction is entered, or the terminal that the tested transaction owns, is called\nthe sending terminal. Since a user typically sets breakpoints without naming the receiving or sending terminal,\nthe receiving and sending terminal is the terminal from which the CNTL command was entered when the user ID\nmonitoring option=.ANY.\n\u2013If the sending terminal is not the same as the receiving terminal, the sending terminal is unavailable and tied to the\ntested transaction during the breakpoint. This restriction does not apply if the receiving terminal is the same as the\nsending  terminal because the user can disconnect from InterTest for CICS.\nRemote FILE Support\nAll CICS regions that participate in a remote FILE transaction session must be at InterTest for CICS Version 4.2 or above.\nAlso, the FILE transaction and the associated program entry IN25FLE must be defined to the file-owning region. The\ntransaction name assigned to the FILE transaction must be the same in all regions.\n 269", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7ead6ca66894-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSymDump  for CICS\nInstall or Customize DFHPEP\nIf your site does not have a custom DFHPEP module implemented, the DFHPEP included in the CAI.CAVHLOAD library\nmust be installed in a library that is concatenated before the IBM CICS library suffixed with SDFHLOAD, so that it replaces\nthe IBM supplied dummy version of DFHPEP.\nIf your site already uses a customized DFHPEP, it should be customized and relinked to include the following source\nstatement:\nEXEC CICS LINK PROGRAM('IN25PEP')\nUsing the supplied copy of DFHPEP, or customizing your own DFHPEP, to link to IN25PEP is not a hard  SymDump  for\nCICS installation requirement. The dump capture functions without DFHPEP/IN25PEP processing. However, the failure to\nconfigure DFHPEP as previously suggested prevents capture of the last screen display in an MRO environment.\nPerformance Considerations\nCICS Virtual Storage\nThe CICS virtual storage requirement of the dump-writing part of SymDump  for CICS is 20 KB for the permanent\nresident program IN25COLD.  The CPU and I/O resources that are used by SymDump  for CICS to produce\na dump will often be less than the resources required by a standard dump, and are unlikely to exceed those\nrequired by a standard dump. The CICS virtual storage that is required to view a dump online is equal to the\nstorage the dumping task originally required (Including program storage for the program active at dump time).\nAlso add the size of the CSA, CWA, TCTTE, TUA, and the formatted trace table of the dumping task.\nWARNING\nThe formatted trace table is only built upon user request.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7ead6ca66894-1", "text": "WARNING\nThe formatted trace table is only built upon user request.\nBecause the SymDump  for CICS task is conversational, these CICS areas are held while a particular dump is\nanalyzed. When the next dump is selected, these areas are freed. Most virtual storage requests, including the\ntrace table, are moved above the 16-megabyte line, easing the virtual storage constraint.\nCICS Internal Trace Table\nSymDump  for CICS dump capture and analysis relies on the availability of the CICS internal trace table for many\ndiagnostic functions. A trace table of 512 KB is usually large enough to hold a typical task processing flow. You\ncan increase or decrease the trace table size as required by your applications. Failure to activate the internal\ntrace results in product functionality loss.\nEDSA utilization increases approximately 600 KB for each concurrent SymDump  for CICS user. If you capture\nthe CICS Internal Trace Table using the SYMT transaction, increase the EDSA size approximately twice the\nsize of the CICS Internal Trace Table for each concurrent user of the SYMT transaction. Adjust your SIT EDSA\nspecification accordingly.\nPROTDMP File\nPROTDMP files initialized using SymDump  for CICS release v9.0 and higher are compatible with this release. We\nrecommend a single PROTDMP file for each CICS region because sharing files across regions is not supported.\nClients who use the GUI to view dumps do not have this limitation, and are free to share a single PROTDMP file\nto contain any version of CICS dumps.\nTrace Formatting Region\nThe TRACE FORMAT REGION requires a maximum DASD workspace of approximately 40 KB for every 4 KB\nblock of raw unformatted CICS trace as specified in the TRCFMEGT IN25OPTS parameter. This storage is", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7ead6ca66894-2", "text": "dynamically obtained and released during the format process in a serial fashion for each SymDump  for CICS,\nCICS trace that is selected, for example, only one format subtask has this DASD workspace at a time. Once\na trace is formatted, the DASD workspace is released before the trace is displayed to the user. The next trace\n 270", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "db308a3bd637-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nformat request re-obtains the needed DASD workspace. For parameters controlling where to get this dynamic\nDASD allocation, refer to your IN25OPTS definition.\nThe TRACE FORMAT REGION also requires 50 KB of extended private area main storage for every 4 KB block\nof raw unformatted CICS trace that is being formatted. This region stores the formatted trace once formatted by\nDFHTUXX0 for review and filtering by the user. This is a cumulative amount for every trace that is simultaneously\nformatted and reviewed. It is obtained during the format request, and is released once the user completely leaves\nthe SymDump  for CICS selection screen on the CICS region from which the dump was selected.\nFor a transaction dump, SymDump  for CICS captures up to 180 4 KB blocks of raw trace data. If the maximum\n180 blocks is captured and the trace is selected for formatting by three users simultaneously, the TRACE\nFORMAT REGION, in a serial fashion, obtains and releases approximately 7 MB of DASD workspace, and gets\n27 MB of total extended private area, or 9 MB per trace.\nIf one of the users exits the trace, the TRACE FORMAT REGION uses 18 MB of extended private area for the two\nremaining traces. Since the traces are already formatted by DFHTUXX0, and reside in the extended private area\nof the TRACE FORMAT REGION, no DASD workspace is used until a new format request is received.\nThe new SymDump  for CICS TRACE FORMAT REGION allows trace formatting to be offloaded from the CICS\nregion that the trace format request originates from. This results in improved performance within the CICS region\nsince the actual formatting of the CICS trace is performed by DFHTUXX0 in the TRACE FORMAT REGION.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "db308a3bd637-1", "text": "The response times for trace formatting depend on the size of the traces, the number of simultaneous requests\nperformed by a TRACE FORMAT REGION, and the amount of machine resource available to the TRACE\nFORMAT REGION. For optimal performance, carefully review the IN25OPTS parameters that control trace\nformatting.\nYou are not limited to having one TRACE FORMAT REGION in your shop. By having a different TRCFFMID\nparameter specification in your IN25OPTS definition, you can have different TRACE FORMAT REGIONS each\nwith different performance characteristics. For example, you may want to have a separate TRACE FORMAT\nREGION with much larger thread allocation sizes (TRCFMEGT) with only a few threads (TRCFTHRD) that you\nmake available to your users that want to view large traces that are captured with the SYMT trace capture facility.\nSymDump  for CICS uses the CICS INTERNAL TRACE TABLE as its source for capturing trace information. A\nrule of thumb for the number of trace entries for a 4 KB trace block in the CICS internal trace table is 40. This may\nvary significantly with the application or system activity being traced at the client site.\nFor the TRCFMEGM (TRACE TOTAL MEGS, MAX IS 2000) and TRCFMEGT (TRACE THREAD MEGS MIN IS\n9) settings, each MB of storage set aside by these parameters support or 'back' approximately 20 raw 4 KB trace\nblocks.\nSymDump  for CICS currently captures up to 180 4 KB trace blocks for a transaction dump, and captures the\nentire CICS internal trace table for an SYMT dump. The minimum recommended thread storage limit is therefore\nestimated to be 9 MB, and the theoretical max thread limit for a 2 GB max storage specification is 222.\nBased on these guidelines, a general approximation for the SYMT internal trace capture is", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "db308a3bd637-2", "text": "Based on these guidelines, a general approximation for the SYMT internal trace capture is\nTRCFMEGT=((TRTABSZ/4)/20). The rule for the TRCFMEGM is also an approximation, since you cannot\nassume that all threads always use maximum storage allocations. For a FORMAT REGION that would only\nhandle SYMT traces, multiply threads * TRCFMEGT to get TRCFMEGM.\nLarge traces, such as those captured by SYMT, can significantly affect the performance of an individual TRACE\nFORMAT REGION. The new SymDump  for CICS TRACE FORMAT REGION uses the IBM DFHTUXX0 (where\nXX corresponds to your release of CICS) module that is provided with the base CICS product. If IBM changes\nthis module due to routine maintenance, you need to recycle your TRACE FORMAT REGION to pick up these\nchanges. To recycle the TRACE FORMAT REGION, issue a cancel or purge on the address space and then\nrestart it .\nActivate Your Product\nUse these steps to activate your product.\nThis article describes the steps you need to activate your product. Product-specific instructions follow the instructions for\nAll Products . There are no product-specific instructions for InterTest Batch.\n 271", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1ecf0dfef5f4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAll Products\nAuthorization\nBefore you activate your product, you must make the executables in CAI.CAVHAUTH available through STEPLIB or\nLINKLIST. CAI.CAVHAUTH must be APF authorized.\nCAIRIM\nCAIRIM must be active on each system that runs InterTest or SymDump  products. You can specify the following\nparameters to customize CAIRIM before activating your products.\nSTEPLIB\nThe following loadlibs are required if they are not in the linklist:\n\u2022The loadlib containing CAIRIM\n\u2022All customized configuration elements, which must be APF authorized.\n\u2022CAI.CAVHAUTH\n\u2022CAI.CAVHLOAD\nRIMPARM\nAdd the following control card to the member or data set pointed to by the RIMPARM DD to initialize the InterTest\nand SymDump  products.\nPRODUCT(CA INTERTEST/SYMDUMP) VERSION(VHB0) INIT(CAVHINIT) PARM(220)\nYou can specify the INIT and PARM parameters as follows:\nINIT\nSpecifies the name of the initialization routine. Specify one of the following values:\n\u2022CAVHINIT\n(Required)\nInitializes or refreshes the InterTest and SymDump  products based on the settings in CAVHCONF.\nCAVHTERM\nTerminates SymDump  Batch.\nPARM\nYou can specify the following values:\n\u2022\u2013SVC number (Required for InterTest Batch)\nSpecify an SVC value between 200 and 255. The value must be an unused SVC number that has no\nlocks assigned to it.\n\u2013RTLONLY\nActivate or deactivate the Optimizer/II  RTL but not SymDump Batch.\n\u2013SBONLY", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1ecf0dfef5f4-1", "text": "Activate or deactivate the Optimizer/II  RTL but not SymDump Batch.\n\u2013SBONLY\nActivate or deactivate SymDump Batch but not the Optimizer/II  RTL. You must have Optimizer/II  RTL activated to\nexecute Optimizer/II  programs.\nNOTE\nCAIRIM inserts a hook into the SVC table (specifically SVC51). If you have concerns about compatibility with\nother dump formatting products, see Installation Considerations. The existing address for SVC51 will be saved.\nControl will be passed to this address depending on the value of the DUMP option of CAOETGEN.\nNOTE\nIf you upgrade from a previous product release, an IPL is required to refresh all modules from the previous\nrelease. However, there is no functional requirement for an IPL when upgrading from version 10 to version 11. \n 272", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8939fbd5c7d6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nQuery Activation Status\nJCL\nA procedure called CAVHLPAQ is provided to invoke the Initialization Summary program. To obtain an initialization\nsummary for your data center, specify the following:\n // EXEC   CAVHLPAQ\n \nThe initialization summary program, CAVHLPAQ, uses the following DD statements:\nSTEPLIB\nDefines the library containing InterTest and SymDump  Initialization Summary program.\nSYSPRINT\nDefines the report file.\nReport\nThe Initialization Summary report displays the following information:\n\u2022Module name\n\u2022Address where module resides\n\u2022Release of each module\n\u2022Date module when the module was assembled\n\u2022Time when the module was assembled\n\u2022Size of module\n\u2022Number of InterTest SymDump  modules found\n\u2022Contents of module CAOESQAT (for support purposes)\n\u2022Contents of CAOETABL\nInterTest for CICS\nActivate InterTest for CICS from a Program\nIn one of your programs you can code a routine to activate InterTest for CICS by the CICS command:\n EXEC CICS START TRANSID('CNTL') FROM(data-area)...\n \nThe data-area  must contain the command:\n CNTL=START,PROM=tablname\n \nWhere tablname  is the name of the load module assembled through PROMMAC macros. The table name must be\nfollowed by a space.\nIf the CNTL task to be automatically initiated is to own a terminal, be sure that the terminal is in service and has the ATI\n(automatic task initiation) capability when the CNTL task is started.\nIssuing CNTL Commands from a Program\nYou can issue any CNTL command using the EXEC CICS START command. However, for the CNTL=START command,\nthe only permitted format is:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8939fbd5c7d6-1", "text": "the only permitted format is:\n CNTL=START,PROM=tablname\n 273", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "399e8be0fb10-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n \nIf the CNTL task is activated at a terminal, response messages are displayed there and the command is executed as\nif someone had entered it from that terminal. For example, if the CNTL command sets a breakpoint, the from and to\nterminals are the terminal at which the task was activated.\nAfter InterTest for CICS starts, a program can issue an EXEC CICS START command with the data record containing:\n CNTL=EXEC,MODULE=tablname\n \nThis command executes the table of commands contained in tablname .\nStart InterTest for CICS from a PLT\nIf the program IN25PLT is included in the PLT, it starts InterTest for CICS as specified in the IN25OPTS member. IN25PLT\nis delivered in the distribution load library.\nThe following InterTest for CICS PLTPI entry must be added after DFHDELIM so that it is part of stage 2 processing:\n DFHPLT TYPE=ENTRY,PROGRAM=IN25PLT\n \nThe IN25PLT program can be called by another user-written PLT program that passes a valid InterTest for CICS start\ncommand in a COMMAREA to IN25PLT. An example is given next:\nINTSTART DC  C'CNTL=START,PROM=PROMTABL ...'\n.\n.\n.\n EXEC CICS      LINK\n        PROGRAM('IN25PLT')\n        COMMAREA(INTSTART)\n        LENGTH(=Y(L'INSTART))    \nNote the following points:\n\u2022The transient data destination specified in the GLOG= InterTest for CICS option must be defined to CICS and must be\nopened.\n\u2022The group DFHINQUI must be defined in the CICS startup list  for IN25PLT to execute.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "399e8be0fb10-1", "text": "\u2022The InterTest for CICS Help file, PROTHLF, must be defined and available.\n\u2022If installing SymDump  with InterTest, the SymDump  for CICS IN25INST program should always be placed after the\nInterTest for CICS IN25PLT program in the PLT.\n\u2022You can guarantee that the InterTest for CICS exits are first to receive control by adding the program entry IN25PLTX\nto the CICS startup PLT. IN25PLTX is required as the first program entry in Phase 1 (prior to the DFHDELIM entry) of\nthe PLT.\nAutomatic Startup in CICSplex Regions\nIf InterTest for CICS is automatically started in a CICSplex-participating region (that is, CICSPLEX=YES in IN25OPTS), it\nresynchronizes its monitoring options with any active CICSplex members upon startup.\nNOTE\nResynchronization occurs whenever the CNTL=START or CNTL=RESTART command is issued in a CICSplex-\nparticipating region.\n 274", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "48c93714f061-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nActivate InterTest for CICS\nAfter you have completed the installation steps, you can activate InterTest for CICS in your CICS system at any time. To\nactivate InterTest for CICS, issue the following command:\n CNTL=START\n \nFor InterTest for CICS regions installed with CICSplex support (CICSPLEX=YES in IN25OPTS), the CNTL=START and\nCNTL=RESTART commands automatically have InterTest for CICS resynchronize monitoring with any active regions in\nthe CICSplex.\nAt this time, you can compile and assemble your programs with the InterTest for CICS symbolic post-processor programs\nas described in Symbolic Support. These programs let you use symbolic references during testing.\nRemember, however, that you do not have to compile your programs with one of the InterTest for CICS symbolic\npost-processor programs. All of the InterTest for CICS monitoring facilities are available for current programs without\nrecompiling or reassembling them. We do recommend that you recompile or reassemble current programs if InterTest for\nCICS detects errors because symbolic support greatly facilitates debugging.\nTo activate InterTest for CICS at CICS startup, perform the following procedures:\n1.Manually activate InterTest for CICS by issuing the CNTL=START command.\n2.Automatically activate InterTest for CICS using the PROMMAC macro or the IN25PLT PLTPI program.\nDeactivate InterTest for CICS\nInterTest for CICS can be deactivated at any time by issuing the following command:\n CNTL=END\n \nFor regions using the CICSplex support option, you can issue the following command to concurrently deactivate InterTest\nfor CICS in all connected CICSplex regions:\n CNTL=END,SCOPE=GLOBAL", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "48c93714f061-1", "text": "CNTL=END,SCOPE=GLOBAL\n \nInterTest for CICS maintains a permanent  service task that runs under the transaction ID ISER. The program is\nIN25SERV. CICS cannot complete a normal shutdown until this task ends. It is important that you deactivate InterTest for\nCICS before CICS shutdown to terminate this task.\nTo deactivate InterTest for CICS at CICS shutdown, perform one of the following procedures:\n\u2022Manually deactivate InterTest for CICS by issuing the CNTL=END command.\n\u2022Automatically deactivate InterTest for CICS using the IN25PLTE program. If you add this InterTest for CICS-supplied\nshutdown PLT program to your shutdown program list, InterTest for CICS will be deactivated automatically at normal\nCICS termination.\nAdd the following InterTest for CICS PLTSD entry before DFHDELIM so that it is part of Stage 1 processing:\n DFHPLT TYPE=ENTRY,PROGRAM=IN25PLTE\n \nRestart CICS and Run VRPT Transaction\nAfter InterTest for CICS has been installed, restart CICS and run the InterTest for CICS check-out program IN25VRPT.\nThis program checks for common mistakes that may have been made during the installation of InterTest for CICS.\n 275", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b4dcb02dbfd2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWARNING\nYou are strongly advised to perform this step so errors can be detected quickly.\nUse the following procedure to check out the installation of InterTest for CICS.\nFollow these steps:\n1.Enter the transaction code VRPT. InterTest for CICS displays the selection menu.\n2.Enter 1 in the Option field and press Enter. InterTest for CICS displays the first screen of programs.\n3.Continue to press Enter to display the next screen.\n4.The InterTest for CICS check-out procedure is completed when the selection menu is displayed with the option field\nset to 4  or beyond.\nNOTE\nIf you are upgrading from a previous release, urge your users to use ITST Option 8 to review \"What's New\" in\nthis release.\nSymDump  for CICS\nDefine and Schedule the Trace Format Region Job\nThe TRACE FORMAT REGION must be running within your CCI network in order for you to format CICS traces within\nSymDump  for CICS.\nMember TRCMSAMP contains the sample JCL for the SymDump  for CICS TRACE FORMAT REGION. This job\nmay be run as a normally scheduled job, or as a started task at your discretion. The TRACE FORMAT REGION can\naccommodate trace format requests from multiple CICS regions that have SymDump  for CICS installed within an existing\nCCI NETWORK. These CICS regions may be at different releases of CICS.\nNOTE\nThe association between a given CICS region and the TRACE FORMAT REGION is made through CCI services\nbased on parameter TRCFFMID in your IN25OPTS definition.\nAlthough the TRACE FORMAT REGION will probably work with the standard defaults for the relevant IN25OPTS\nparameters, you are encouraged to familiarize yourself with the new IN25OPTS parameters that control trace formatting.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b4dcb02dbfd2-1", "text": "This helps to ensure that you are successful in implementing this powerful feature of SymDump  for CICS.\nEdit the JCL to conform to your installation standards and the previously completed worksheet. However, never change\nany of the ddnames.\nYou must now include a STEPLIB DD statement pointing to your CAVHLOAD load library in addition to the STEPLIB DD\nstatement pointing to your CICS load library. This is already in the TRCMSAMP sample JCL member.\nSubmit this job before attempting to format CICS traces from SymDump  for CICS.\nRestart CICS and Run VRPT Transaction\nAfter SymDump  for CICS is installed, restart CICS and run the SymDump  for CICS check-out program IN25VRPT. This\nprogram checks for common mistakes that may have been made during the installation of SymDump  for CICS.\nWARNING\nYou are strongly advised to perform this step so errors can be detected quickly.\nFollow these steps:\n1.Type the transaction code VRPT. SymDump  for CICS displays the selection menu.\n2.Type 4 in the Option field and press Enter. SymDump  for CICS displays the first program screen.\n3.Continue to press Enter to display the next screen.\n 276", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6ba770058acb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n4.When the selection menu appears with the option field set to 1, the SymDump  for CICS check-out procedure is\ncomplete.\nStart and Stop Dump Capture Facility\nAfter installing SymDump  for CICS, you can use one of the following methods to start the dump capture facility\nautomatically with your CICS system.\n\u2022Enter the SYMS command from a CRLP-type terminal . If you have at least one CRLP-type terminal defined in your\nTCT, its input sequential file can contain the SYMS command. The command executes just as if it was entered\nmanually from a CRT, and responses to it are written in the terminal's output sequential file.\n\u2022Start SymDump  for CICS from a PLT table. If the program IN25INST is included in the PLT table, it starts SymDump  for\nCICS. IN25INST is delivered in the target load library.\nPurge a Dump Data Set Automatically at Startup\nIf you are starting SymDump  for CICS from the PLT table using IN25INST, you can automatically purge old dumps at\nthat time. If the automatic purge of dumps configuration parameter is set to Y, IN25INST purges any dumps equal to or\nolder than the number of days specified in the automatic purge hold days parameter. The default for this parameter is one\nday. For more information, see CICS Abend Analysis.\nWARNING\nIf you do not want your dumps to be automatically deleted, set the automatic purge of dumps parameter to N\nand refer to the dynamic purge of oldest dump parameter. This allows SymDump  for CICS to dynamically purge\nnon-held dumps during dump capture on a first-in, first-out basis to obtain space for the new dump.\nShut Down Automatically", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6ba770058acb-1", "text": "Shut Down Automatically\nYou must deactivate SymDump  for CICS prior to shutting down your CICS region, or an abend may occur.\nYou can manually deactivate SymDump  for CICS using the SYME transaction from a 3270 terminal.\nYou can automatically deactivate SymDump  for CICS using the IN25ENPL program. If you add this SymDump  for CICS-\nsupplied shutdown PLT program to your shutdown program list, SymDump  for CICS is deactivated automatically at normal\nCICS termination.\nTo take advantage of this feature, add the following SymDump  for CICS PLTSD entry before DFHDELIM so it becomes\npart of Stage 1 processing:\n DFHPLT TYPE=ENTRY,PROGRAM=IN25ENPL\n \nShut Down Trace Format Region\nThe SymDump  for CICS Trace Format Region can be shut down in an orderly fashion by replying shutdown to the\noutstanding write to operator message (CAIN5951) that is on the operator's console.\nSymDump  Batch\nDeactivate SymDump  Batch\nTo deactivate SymDump  Batch, use the same procedure that is used to activate the product, but instead of the RIMPARM\ncard specified in that procedure, use the following:\n PRODUCT(CA SYMDUMP/INTERTEST) VERSION(VHB0) INIT(CAVHTERM)\n \n 277", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d2a817f9237b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInstallation Verification\nRun the demo programs for each application to validate the installation.\nThis article describes how to run the demo programs for each application. Running the demo programs validates the\ninstallation and provides an introduction to using your product.\nInterTest Batch\nUse one of the procedures customized in the Customize Compile Procedures to compile, assemble, and link one of the\ndemo programs provided in CAI.CAVHSAMP. The following list shows the demo program names for each compiler. For\ndetailed information about running the demo program, see InterTest Batch Demo Sessions.\nCAMRASM\nFor Assembler programmers\nCAMRPLI\nFor PL/I programmers\nCAMRCOB\nFor OS/VS COBOL programmers\nCAMRCOB2\nFor COBOL II programmers\nNOTE\nThese programs use ISPF. Programmers on Roscoe  systems can use CAMRDMR and CAMRDMR2 for\ndemonstration purposes.\nSymDump  Batch\nValidate the SymDump  Batch installation by completing the following steps:\n1.Review and edit JCL member CARXDEMO.\n2.Run the demo and examine the results.\n3.Run the database demo programs.\n4.Review abend reports using the Viewer.\nReview and Edit JCL Member CARXDEMO\nJCL member CAI.CAVHJCL(CARXDEMO) is a compile, postprocess, link, and run of the demo program, CAOEDEMO.\nEdit the JCL to conform to your installation standards.\nRun the Demo and Examine the Results\nSubmit CARXDEMO and examine the results. Successful execution results in a S0C7 from the RUN step.\nBy default, the RUN step always produces the following SymDump  Batch reports:\n\u2022CAIOPTS File Processing report\n\u2022Abend report", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d2a817f9237b-1", "text": "\u2022CAIOPTS File Processing report\n\u2022Abend report\nRun the IDMS/DB , DB2, and IMS Demo Programs\nIf you use the IDMS/DB , DB2, and IMS abend reporting features, run the demo programs that apply to your site. If your\nsite is not using these features, skip this step.\nThe sample JCL members for the demo programs are stored in CAI.CAVHJCL. Review and edit the following members\nthat apply to your shop.\n 278", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a27a339c8dfd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCARXDEM1\n\u2014for IDMS/DB\nCARXDEM2\n\u2014for DB2\nCARXDEM3\n\u2014for IMS\nRun the job and examine the results. A SymDump  Batch report is produced when each job abends.\nReview Abend Reports Using the Viewer\nYou have an option of reviewing abend reports for validating the installation.\nFollow these steps:\n1.Select the appropriate option from your ISPF main menu (updated in Concatenate ISPF File and Tailor Master Panel)\nto start the CAIPRINT repository viewer.\nAn index of all the abend reports that were created during this installation step is displayed.\nCA SymDump Batch  ---------- Report Index -------------------- Line 1 of 1\nCommand ===>                                                   Scroll ===> \nCSRCAPI100I Repository contains 1 report(s) --------------------------------------\nRepository Dsname: CAI.PRTLIB                                     \n     3509 Data Records       36 Used     1.1% Full                              \nFilter: Jobname *       Step/Tsk *        Program   *             Offset *                  \n        Comp    *       UserID   *        Lock      *             System *\n------------------------------------------------------------------------- Lvl 1>\nCmd  JobName   Step/Tsk  Program   Offset   Comp    Date        Time   UserId  .\n     USER01X   RUN       CAOEDEMO  0003B64  S=0C7   2007/03/17  16.47  USER01 \n-------------------------------------------------------------------------------\n2.Select a report for viewing by entering an s in the Cmd column next to the report entry, and press Enter.\nThe Report Tree panel appears.\nCA SymDump Batch  ---------- Report Tree -------------------- Line 1 of 13\nCommand ===>                                                   Scroll ===>", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a27a339c8dfd-1", "text": "Command ===>                                                   Scroll ===> \nCSRCAPI052I Profile restored as of 17:58:49 on 2011/07/20 ------------------------\nJobName  USER01A    Step/Tsk  RUN       UserId  USER01      Date  2011/07/20\n  \nProgram  CAOEDEMO   Offset    00041B6   Comp    S=0C7       Time  17.57        \n------------------------------------------------------------------------- Lvl 2\nCmd  LineNo.   Description                                                     \n.         1 - Job=USER01A                                                     \n.         1   |-Input Options Display \nIf the report tree is displayed, you have successfully validated your installation.\nNOTE\nFor a detailed description of the CAIPRINT repository viewer and its functionality, see Batch Abend Analysis.\n 279", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4943364c0141-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterTest for CICS\nDemonstration programs are distributed for Assembler, COBOL, and PL/I in the source format. You can assemble or\ncompile them using the jobs found in CAVHJCL. The PROCs executed by these sample jobs are defined in CAVHPROC.\nThe sample jobs provide symbolic parameter overrides to the respective PROC members. You can modify the appropriate\nPROC members to define these symbolic parameters as defaults. You need to modify the PROC members to define\ncertain default symbolic parameters to comply with your installation standards. For detailed information about running the\ndemo program, see InterTest for CICS Primers.\nThe following list details the five members in CAI.CAVHJCL.\nCABADMAJ\nThe CABADMAJ job prepares the Assembler language demonstration program for execution. For more\ninformation about using the ASMDEMO program, see Assembler Primer. This job contains the following steps:\nStep ALOCLIBS\nAllocates an object library and a load library. This step can be deleted if you are using existing libraries.\nStep ASMDEMO\nExecutes PROC CABAASMP to translate, assemble, and postprocess the Assembler language demonstration\nprogram ASMDEMO.\nStep LKEDDEMO\nExecutes program IEWL to bind the object module created by Step ASMDEMO.\nCABADMCJ\nThe CABADMCJ job prepares the COBOL language demonstration program (COBDEMO) for execution. For\nmore information about using the COBDEMO program, see COBOL Primer. This job contains the following steps:\nStep ALOCLIBS\nAllocates an object library and a load library. This step can be deleted if you are using existing libraries.\nStep COBDEMO", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4943364c0141-1", "text": "Step COBDEMO\nExecutes PROC CABACOBP to compile and postprocess the COBOL language demonstration program\nCOBDEMO.\nStep LKEDDEMO\nExecutes program IEWL to bind the object module from the previous step.\nStep CSBIN25\nExecutes PROC CABACOBP to compile and postprocess the COBOL language demonstration subprogram\nCSBIN25.\nStep ASBIN25\nExecutes PROC CABAASMP to translate, assemble, and postprocess the Assembler language demonstration\nsubprogram ASBIN25.\nStep COBDEML\nExecutes PROC CABACOBP to compile and postprocess the COBOL language demonstration program\nCOBDEML.\nStep LKEDDEML\nExecutes program IEWL to bind the object modules from the previous steps into a composite load module.\nStep GLNKDEML\nExecutes program IN25LINK to prepare COBDEML for composite mapping demonstration.\nCABADWCJ\nThe CABADWCJ job prepares the COBOL language demonstration program (COBDEMO) with DWARF symbolic\ninformation for execution. For more information about using the COBDEMO program, see COBOL Primer. This\njob contains the following steps:\nStep ALOCLIBS\nAllocates an object library and a load library. This step can be deleted if you are using existing libraries.\nStep COBDEMO\nExecutes the PROC CABACOBD to compile the COBOL language demonstration program COBDEMO with\nDWARF symbolic information.\n 280", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4f1610fb2862-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nStep LKEDDEMO\nExecutes the program IEWL to bind the object module from the previous step.\nCABADMDJ\nThe CABADMDJ job prepares the COBOL DB2 demonstration program (DB2DEMO) for execution. For more\ninformation about using the DB2DEMO program, see COBOL Primer. This job contains the following steps:\nStep ALOCLIBS\nAllocates an object library and a load library. This step can be deleted if you are using existing libraries.\nStep DB2TRAN\nExecutes the DB2 Translator for the demonstration program DB2DEMO.\nStep COBDEMO\nExecutes PROC CABACOBP to compile and postprocess the COBOL language demonstration program\nDB2DEMO.\nStep LKEDDEMO\nExecutes program IEWL to bind the object module from the previous step.\nStep BINDPLAN\nExecutes program IKJEFT01 to bind the plan for DB2DEMO program.\nCABADMPJ\nThe CABADMPJ job prepares the PL/I language demonstration programs. For more information about using the\nPL1DEMO program, see PL/I Primer. This job contains the following steps:\nStep ALOCLIBS\nAllocates an object library and a load library. This step can be deleted if you are using existing libraries.\nStep PLIDEMO\nExecutes PROC CABAPLIP to compile and postprocess the PL/I language demonstration program PL1DEMO.\nStep LKEDDEMO\nExecutes program IEWL to bind the object modules from the previous step.\nStep PSBIN25\nExecutes PROC CABAPLIP to compile and postprocess the PL/I language demonstration subprogram PSBIN25.\nStep ASBIN25", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4f1610fb2862-1", "text": "Step ASBIN25\nExecutes PROC CABAASMP to translate, assemble, and postprocess the Assembler language demonstration\nsubprogram ASBIN25.\nStep PLIDEML\nExecutes PROC CABAPLIP compile and postprocess the PL/I language demonstration program PL1DEML.\nStep LINKDEML\nExecutes program IEWL to bind the object modules from the previous steps into a composite load module.\nStep GLNKDEML\nExecutes program IN25LINK to prepare PL1DEML for composite mapping demonstration.\nSymDump  for CICS\nAfter you install SymDump  for CICS and start CICS, you can run the demonstration programs to force and then view a\ntransaction dump.\nFollow these steps:\n1.Entering the transaction code SYMD to verify that SymDump  for CICS was started.\n2.Type 4 in the Option field and press Enter.\nSymDump  for CICS will start or will tell you that it was already started.\n3.Type X to terminate SYMD.\n4.Type one or more of the following transaction codes. After the menu appears, press Enter to force an ASRA abend\nand the creation of a CICS transaction dump that should be captured and displayable by SymDump  for CICS.\nDEMA    Assembler program ASRA (0C7)    \nDEMC    COBOL program ASRA (0C7)    \nDEMD    COBOL DB2 program ASRA (0C7)    \n 281", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "82d7ad650423-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDEMP    PL1 program ASRA (0C7)  \n5.Type the transaction code SYMD.\n6.Type 1 on the Option field and follow the menu instructions to view the dumps created in the previous Step 4.\nInstall Maintenance\nAfter you have successfully installed any Broadcom  mainframe product software, check for important product\nmaintenance that may have been released after the product installation package was prepared. The product releases are\nbuilt and maintained using standardized SMP/E packaging and installation procedures. These procedures include error\nand FIXCAT HOLDDATA, new product features, and product interoperability validation. PTFs that pass interoperability test\ncriteria are released monthly and designated as CARS .\nYou can install the following types of maintenance:\n\u2022Corrective maintenance that fixes an issue.\n\u2022Preventive maintenance to avoid problems that others have reported or to provide a compatibility fix for hardware and\nsoftware.\n\u2022FIXCAT maintenance to support a particular hardware device, software release, or new product function.\nWARNING\nYou can initiate a maintenance installation activity at any time using z/OSMF Software Update, SMP/E JCL, or\nCSM . However, before you do so, we recommend that you obtain the current SMP/E HOLDDATA.\nSee Broadcom Mainframe Product Maintenance  for a list of solutions that have been published within the last year. From\nthis page, you can search solutions for all Broadcom  mainframe products by product name, date, or keyword. You can\nalso search for new product features or by a CARS  level (CARSID). You can also find HIPER or PE PTFs and security\nor integrity PTFs. Once you have your list, you can download in Excel or CSV format. To download PTFs automatically\nwithout having to search regularly on the portal, use SMP/E Receive Order .", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "82d7ad650423-1", "text": "without having to search regularly on the portal, use SMP/E Receive Order .\nFor a comprehensive collection of articles that are dedicated to all mainframe maintenance concepts and procedures, see\nMainframe Common Maintenance Procedures .\nMaintain Products Using z/OSMF Software Update\nAs a systems programmer, you are responsible for keeping your systems current with product maintenance to ensure\noptimal system usage. To do so, use IBM z/OSMF Software Update. Software Update provides an easy to follow wizard\nthat guides systems programmers of all levels through the maintenance process. z/OSMF Software Update offers a\nmodern approach to software maintenance and provides the following features:\nCorrective Service Installs a software update to fix an issue.\nPreventive Service Installs vendor-recommended software updates.\nFIXCAT Installs software updates (Fix Categories) that provide a new function to a system.\nNOTE\nWe are not adding new features to CSM . We recommend that you use z/OSMF Software Update to apply\nmaintenance to z/OS software.\nPrerequisites\nEnsure that you meet the following software requirements before you use Software Update:\n\u2022Configure z/OSMF as described in the IBM documentation and address the z/OSMF security requirements for ACF2 ,\nTop Secret, or IBM RACF as applicable.\n\u2022Apply all z/OSMF Software Update-related maintenance from IBM.\n\u2022Register your SMP/E environments (CSIs) in z/OSMF Software Management. For more information, see Software\nManagement task  in the IBM documentation.\n 282", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a8965e634717-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTIP\nA migration tool is provided to help you register existing CSM  and non-CSM CSIs as new software instances\nin z/OSMF. For more information about the migration tool, see Migrate SMP/E Environments into z/OSMF .\n\u2022Download and receive maintenance, HOLDDATA, and CARS  maintenance for your products. As a best practice, we\nrecommend that you do so on a daily or weekly basis and that you automate this process using SMP/E Receive Order\n(see Configure SMP/E Internet Service Retrieval ). You can also perform these tasks manually from Broadcom Support .\nNOTE\nYou can only apply maintenance for SYSMODs that are already received in the GLOBAL zone of the CSI.\nIMPORTANT\nThe ASSIGN statements for CARS  maintenance are not cumulative. To install the latest CARS  maintenance,\ndownload all YEARLY ASSIGN files, and then download the monthly ASSIGN files as needed.\nUse Software Update\nLog in to your instance of z/OSMF and click the Software Update  icon on the desktop. If the Software Update  icon does\nnot appear on the desktop, open the App Center in the bottom-left corner.\nYou can now maintain software instances, using the z/OSMF Software Update functionality. For more information about\nhow to use Software Update, see  Software Update in the IBM documentation.\nMaintain Products Using CSM\nUse the procedures in this topic to receive, apply, and accept maintenance for your products using CSM .\nCSM  provides a product list that lets you display the list of licensed product maintenance packages and to download these\npackages. You can also manage external maintenance packages that were acquired outside of CSM  so that they can be\napplied using  CSM .\nWARNING\nAs part of our ongoing commitment to customer success and to help our customer base achieve their", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a8965e634717-1", "text": "WARNING\nAs part of our ongoing commitment to customer success and to help our customer base achieve their\nstrategic business initiatives, we are investing our resources in z/OSMF for software management. We will\nbe discontinuing technical support for CSM . In accordance with the terms and conditions, guidelines, and\nparameters of Broadcom\u2019s support program, which is documented in the Broadcom Software Maintenance\nPolicy Handbook , this announcement provides written notification of End of Life for CSM . This notification means\nthat CSM  will no longer be enhanced and maintenance and technical support, including self-service support, will\nbe discontinued effective June 30, 2023 . For full details, see the End of Life Announcement.\nNOTE\nDuring your initial product installation, apply all product maintenance. Otherwise, you may have to repeat the\ndeployment and configuration processes.\nThe following diagram shows the maintenance process using CSM :\n 283", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4d8f7e08ff92-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse the following procedure to maintain products using CSM :\n1.(Optional) Configure automatic HOLDDATA download.\n2.(Optional) Configure CSM  to reject unneeded maintenance .\n3.Download product maintenance packages .\n\u2013(Optional) Configure CSM  to perform automatic maintenance updates .\n4.(Optional) Manage maintenance downloaded outside of CSM . As part of this management, you can also view the\naggregated package details .\n5.Receive maintenance .\n6.(Optional) Reject maintenance .\n7.Apply maintenance .\na.Consider whether you require a product USERMOD .\nb.Review and process any unresolved HOLDDATA.\nc.Apply CARS  maintenance .\nd.(Optional) Apply FIXCAT maintenance.\n8.(Optional) Restore maintenance .\n9.Accept maintenance .\n\u2013(Optional) Accept maintenance in GROUPEXTEND mode .\n 284", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7a62409690de-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAfter you complete this process, the maintenance packages for your products are accepted.\nYou have deployed and configured a product across your enterprise. Now you are applying maintenance to this product.\nCreate a deployment and a configuration for this product to get this maintenance to your target systems.\nConfigure Automatic HOLDDATA Download\nYou can configure CSM  to download automatically the available HOLDDATA that it uses for each maintenance installation.\nYou then have current information about what maintenance packages are marked as PE (PTF in Error).\n1.Select the Settings  tab, and select the Software Catalog  link under System Settings  in the Settings  section on the\nleft side.\n2.In the HOLDDATA Settings section, select the Enable Automatic Updates  checkbox.\n3.Set up values for the following fields, and select Apply :\nOwner of Update Task\nSpecifies the TSO user ID under which the update task is run.\nRecurrence\nSpecifies how often the task recurs.\nUpdate Software Catalog Every number of Days\nor Update Software Catalog On day of week  Every  number of  Weeks\nSpecifies the frequency of downloading HOLDDATA to your software catalog, in days or weeks, depending on the\nvalue the Recurrence  field.\nExample : Imagine you set the recurrence for a specific number of days and you set the time that precedes the\ncurrent time. Then the first update occurs in the specified number of days at the specified time. For example, on\nMonday at 10.30 am, you set the number of days to 3 and time to 07.00. The first update then occurs on the third\nday, Thursday, at 7.00 am. When you set the time past the current time, the first update occurs on the same day", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7a62409690de-1", "text": "at the time set. For example, on Monday at 10.30 am, you set the number of days to 3 and time to 11.00. The first\nupdate then occurs on that Monday at 11.00 am.\nSystem Time\nSpecifies the system time when an automatic update occurs. The system time reflects your CSM  application\nserver time zone. The TZ parameter within Tomcat startup libraries defines the time zone. If the TZ parameter is\nnot defined, the CSM  application server time zone defaults to GMT - Greenwich Mean Time.\nLocal time is calculated based on the system time that you set.\nNOTE\nTo download available HOLDDATA to the software catalog immediately, select Update Immediately .\nThe automatic HOLDDATA download is configured.\nConfigure CSM  to Reject Unneeded Maintenance from the SMP/E Environment\nDuring the regular, FIXCAT, or CARS  maintenance wizard execution, CSM  may receive maintenance. Some maintenance\npackages may not be directly associated with the maintenance that you want to apply.\nYou can configure CSM  to reject the maintenance that was received but not applied during the wizard execution.\n\u2022If you exit the wizard before the maintenance installation started, CSM  rejects the maintenance that has been received\nduring the wizard execution. The SMP/E environment is restored to the state that it had before you started the wizard.\n\u2022If you navigated through the wizard steps, started the maintenance installation task, and the task completed\nsuccessfully, CSM  rejects the received but not applied maintenance that is not directly associated with the\nmaintenance that you have applied.\n 285", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9e0e31b46715-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThis process ensures that your SMP/E environments do not contain unneeded received maintenance.\n1.Select the Settings  tab, and select the Software Installation  link under System Settings  on the left side.\n2.In the Maintenance Installation  section, select the Reject Received Maintenance  checkbox.\n3.Select Apply .\nA dialog that shows the progress of the task opens. When the task completes, select Show Results  on the Progress\ntab to close this dialog. The task output browser opens, and you can view the action details.\nNOTE\nWhile a task is in progress, you can perform other work. Select Hide  to exit the dialog and view the task\nstatus later on the Tasks tab.\nCSM  is configured to reject unneeded maintenance.\nDownload Product Maintenance Packages\nYou can download maintenance packages for installed products through the Products  tab. You can download:\n\u2022All maintenance packages for a product\n\u2022Only maintenance packages that have been released from the time the product release was updated last\nNOTE\nThe information for HIPERs and new maintenance on the Software Status tab  is based on the current\ninformation in your software catalog. Update the product list on a daily or weekly basis to keep it current.\nWARNING\nYou can also download maintenance using the SMP/E Internet Service Retrieval . This option uses the IBM\nSMP/E RECEIVE ORDER command to download Broadcom  mainframe product maintenance over the Internet,\nby securely submitting an order for PTFs and HOLDDATA to a remote Broadcom  server. This service eliminates\nthe manual steps that are required to download maintenance from Broadcom Support . The orders are fulfilled\nbased on the status of your SMP/E environments. Based on your order criteria, all PTFs and their requisites are\ndownloaded automatically and received to your system.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9e0e31b46715-1", "text": "downloaded automatically and received to your system.\nTo use this download option, complete the procedures to configure the SMP/E Internet Service Retrieval  as\ndescribed in the Mainframe Common Maintenance Procedures  documentation. After you set up this service, you\ncan use CSM  to apply and accept your maintenance.\n1.Verify that your CSM  login user name is associated with a registered user of Broadcom Support  on the Software\nAcquisition Settings  page.\nCSM  uses the credentials to access Broadcom Support .\n2.Select the name of the product for which you want to download maintenance in the product list on the left side.\nMaintenance information about the product appears in the Releases section on the right side.\n3.For the product release for which you want to download maintenance, select the Actions  drop-down list to the right of\nthe release. Complete one of the following steps:\na.Select Update Product Release  to download all maintenance packages for the product release.\nb.Select Get Latest Maintenance  to download only maintenance packages that have been released from the time\nthe product release was updated last.\nA dialog that shows the progress of the task opens. When the task completes, select Show Results  on the Progress\ntab to close this dialog. The task output browser opens, and you can view the action details.\nThe maintenance packages are downloaded.\n 286", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8ae0e159711a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nConfigure CSM  to Perform Automatic Maintenance Updates\nYou can configure CSM  to perform automatic maintenance updates (downloading and receiving maintenance) for\nproducts that are installed in an SMP/E environment.\nManage Maintenance Downloaded Outside of CSM\nSometimes you acquire maintenance packages, such as unpublished maintenance, PTF, APARs, and USERMODs,\noutside of CSM . For example, you are validating a test PTF released for a product. You can add information about these\nmaintenance packages to CSM  from the Products tab.\nAdding these maintenance packages to CSM  provides you with a complete view of all the maintenance for a product\nrelease. After a package is migrated, you can use CSM  to apply the maintenance.\nUsually, the maintenance is placed as a single package. However, some Broadcom  mainframe products still have older\naggregated maintenance packages that were released before December 31, 2013. An aggregated package  is a file that\ncomprises several single maintenance packages (nested packages). When you add an aggregated package, CSM  inserts\nall the nested packages and the aggregated package itself. In the list of maintenance packages, the aggregated package\nis marked with the CUMULATIVE type.\nWhen you insert an aggregated package, CSM  assigns a fix number to it. The fix number is unique and contains eight\ncharacters. The first two characters are AM (for Aggregated Maintenance) and a unique six-digit number follows. The\nnumber value increases by 1 with each added aggregated package.\nIf the aggregated maintenance package has the same fix number as one of its nested packages, only the nested package\nis added. The aggregated package itself is not available in the list of maintenance packages.\n1.Select the Products  tab, and select the product release for which the maintenance applies.\n2.Select the Add External Maintenance  button.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8ae0e159711a-1", "text": "2.Select the Add External Maintenance  button.\n3.Specify one of the following package types and package details:\nData Set\nAdds a maintenance package that is located in a z/OS data set with an LRECL of 80 and RECFM of FB.\nUNIX File\nAdds a maintenance package that is located in a USS directory in binary mode.\nFTP File\nAdds a maintenance package that is not published on Broadcom Support . This option is intended for downloading\na PTF to validate it.\nFTP Host Specifies the FTP server where the maintenance package is located. Select a server from the list, or\nprovide your FTP server host.\nFTP Port Specifies the FTP port number for the FTP server.\nFTP Path Defines the FTP path where the maintenance package is located. Start the path with a forward slash\n(/). Enter only a forward slash to specify the root directory.\nExample:  /outgoing/\nMaintenance Name Defines the maintenance package name.\nExample:  RO01111.bin\nUser Name Defines a valid user name to access the FTP location.\nPassword Defines a valid password to access the FTP location.\nSolution\nAdds a published solution on Broadcom Support .\nNOTE\nTo add several data sets or UNIX file packages from the same location, use masking.\n4.Select OK.\n 287", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0ee5135fd241-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nA dialog that shows the progress of the task opens. When the task completes, select Show Results  on the Progress\ntab to close this dialog. The task output browser opens, and you can view the action details.\nThe maintenance package with the related information is saved in the CSM  database. To see the added package, refresh\nthe page.\nView Aggregated Package Details\nYou can view which nested packages are included in the aggregated package. The information includes the fix number,\npackage type, and package description.\nNOTE\nAggregated maintenance packages were discontinued December 31, 2013. However, some Broadcom\nmainframe products have aggregated maintenance packages that were released before this date.\n1.Select the Products  tab, and select the product release that has the aggregated package whose details you want to\nview.\n2.Select the Fix #  link for the aggregated package.\nThe Maintenance Package Details dialog opens.\n3.Select the Nested Packages  tab.\nA list of nested packages that the aggregated package contains appears.\nReceive Maintenance\nAfter maintenance has been downloaded for a product, you can receive the maintenance to the global zone of an SMP/E\nenvironment where the related products are installed. Once received, maintenance packages can be applied.\nWhile you work with an SMP/E environment, the environment is locked and other CSM  users cannot perform any action\nagainst it. When the task finishes, logging out from CSM , or a CSM  session is inactive for more than 10 minutes, the lock\nreleases.\n1.Select the SMP/E Environments  tab, and select the SMP/E environment where you want to receive maintenance\npackages.\n2.Select Maintenance . If you do not see any maintenance packages, verify that you have maintenance view criteria\ndefined.\n3.Select the maintenance packages that you want to receive, and select the Receive link.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0ee5135fd241-1", "text": "defined.\n3.Select the maintenance packages that you want to receive, and select the Receive link.\nThe maintenance wizard opens to the Introduction step.\nNOTE\nIf you select an SMP/E environment being used in CSM  by another user, a notification message appears.\nYou are prevented from performing any actions on the SMP/E environment. Wait until the notification\nmessage disappears and the SMP/E environment becomes available, or select Cancel to select another\nSMP/E environment.\n4.Review the information about the receiving, and select Next .\n5.Review and adjust the receive list selections as required, and select Next .\n6.Review the summary, and select Receive .\nA dialog that shows the progress of the task opens. When the task completes, select Show Results  on the Progress\ntab to close this dialog. The task output browser opens, and you can view the action details.\nThe maintenance packages are received to the SMP/E environment global zone.\nReject Maintenance\nYou can reject a received maintenance package. Information about the maintenance package is removed from the SMP/E\nenvironment global zone.\n 288", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3dd7c74f731f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWhile you work with an SMP/E environment, the environment is locked and other CSM  users cannot perform any action\nagainst it. When the task finishes, logging out from CSM , or a CSM  session is inactive for more than 10 minutes, the lock\nreleases.\n1.Select the SMP/E Environments  tab, and select the SMP/E environment from which you want to reject maintenance.\n2.Select Maintenance . If you do not see any maintenance packages, verify that you have maintenance view criteria\ndefined.\n3.Select the maintenance packages that you want to reject, and select the Reject  link. You can filter out only received\npackages.\nThe maintenance wizard opens to the Introduction step.\nNOTE\nIf you select an SMP/E environment being used in CSM  by another user, a notification message appears.\nYou are prevented from performing any actions on the SMP/E environment. Wait until the notification\nmessage disappears and the SMP/E environment becomes available, or select Cancel to select another\nSMP/E environment.\n4.Review the information about the rejection, and select Next .\n5.Review and adjust the rejected list selections as required, and select Next .\n6.Review the summary, and select Reject .\nA dialog that shows the progress of the task opens. When the task completes, select Show Results  on the Progress\ntab to close this dialog. The task output browser opens, and you can view the action details.\nThe maintenance packages are rejected. Information about the maintenance packages is removed from the SMP/E\nenvironment global zone.\nApply Maintenance\nAfter maintenance has been downloaded for a product, you can apply the maintenance to products that are installed in an\nSMP/E environment.\nWARNING\nBefore you apply maintenance, ensure that required file systems are mounted and that you have specified the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3dd7c74f731f-1", "text": "WARNING\nBefore you apply maintenance, ensure that required file systems are mounted and that you have specified the\ncorrect path to the DDDEFs that are contained in the file systems. The path must be the mount point of the zFS\nfile system, plus the directory /CA. For example, if the zFS file system is mounted at /broadcom/abc, the DDDEF\npath must be /broadcom/abc/CA.\nAs an option, CSM  lets you verify that the maintenance packages can be applied to the selected target zones without\napplying the packages.\nWhile you work with an SMP/E environment, the SMP/E environment is locked and other CSM  users cannot perform any\naction against it. When the task finishes, logging out from CSM , or a CSM  session is inactive for more than 10 minutes,\nthe lock releases.\n1.Select the SMP/E Environments  tab, and select the SMP/E environment whose products you want to apply\nmaintenance to.\n2.Select Maintenance . If you do not see any maintenance packages, verify that you have maintenance view criteria\ndefined.\n3.Select the maintenance packages that you want to apply, and select the Apply  link.\nNOTE\nIf you select an SMP/E environment being used in CSM  by another user, a notification message appears.\nYou are prevented from performing any actions on the SMP/E environment. Wait until the notification\nmessage disappears and the SMP/E environment becomes available, or select Cancel to select another\nSMP/E environment.\n4.Follow the instructions on the wizard to navigate through the wizard steps.\n 289", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1d6cf451cdf1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n5.From the Summary  step, review the summary, and select Check and Apply .\nA dialog that shows the progress of the task opens. When the task completes, select Show Results  on the Progress\ntab to close this dialog. The task output browser opens, and you can view the action details.\nCSM  verifies and applies the maintenance packages to the selected target zones.\nIf the task fails, navigate to the Tasks tab and review SMPOUT in the task output to identify and correct problems. Rerun\nthe wizard.\nYou have completed acquiring and applying maintenance. You can accept the applied maintenance (except USERMODs)\nfrom the SMP/E Environments, Maintenance tab.\nUSERMODs\nA product USERMOD can be provided as a published maintenance package downloaded during the Update Product\nprocess. When CSM  downloads a package including a ++USERMOD statement, it is loaded under the product with a\nUSERMOD type. You can install these packages using CSM  but cannot accept them because they are not intended to be\npermanent.\nYou can create a USERMOD manually, or we can provide an unpublished maintenance package as a USERMOD. In this\ncase, the USERMOD file, which contains the ++USERMOD statement and the body of the USERMOD, must be managed\nas an externally downloaded package .\nUnresolved HOLDDATA Processing\nWhen you apply maintenance, review and process any unresolved HOLDDATA for the applied maintenance and its\nprerequisites. The maintenance wizard displays all unresolved HOLDDATA and lets you review the HOLDDATA and\ndetails about the HELD maintenance. You can then bypass the HOLDDATA or exclude the HELD maintenance. CSM\ndetermines unresolved HOLDDATA by running SMP/E APPLY GROUP/GROUPEXTEND CHECK.\nIn the maintenance wizard, you can perform the following actions:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1d6cf451cdf1-1", "text": "In the maintenance wizard, you can perform the following actions:\n\u2022Select HOLDDATA (HOLDDATA TYPE, REASON, or maintenance) to bypass it.\n\u2022Leave HOLDDATA unselected to exclude it. If you do not select a HOLDDATA entry checkbox, CSM  excludes the\nHELD maintenance from the processing.\nIf you exclude at least one HELD maintenance package, CSM  runs an appropriate SMP/E APPLY GROUP/\nGROUPEXTEND CHECK command to verify the processing. CSM  verifies whether other maintenance requires the\nexcluded maintenance. If so, CSM  also excludes it from processing.\nIf the SMP/E APPLY GROUP/GROUPEXTEND CHECK command discovers further unresolved HOLDDATA, you are\nnotified about all unresolved HOLDDATA again. Select what HOLDDATA to bypass and what HELD maintenance to\nexclude.\nThis iterative process repeats until all HOLDDATA is resolved or bypassed. You can then proceed to the next step.\nA list of maintenance packages that are excluded during the processing of unresolved HOLDDATA is displayed in the\nSummary step.\nApply CARS  Maintenance\nCSM  lets you track and apply CARS  maintenance for your products.\nCARS  is a set of maintenance packages that have been tested in a mainframe-integrated system test environment. Install\nCARS  maintenance to keep your products current. Broadcom  releases CARS  maintenance regularly. The release date\ndetermines the CARS  maintenance level.\n 290", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ea98d9faa605-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo learn about new CARS  maintenance that is available, download the files that are listed for published CARS\nmaintenance. You can configure CSM  to download these files automatically , or add CARS files manually . You can filter\nthis maintenance in the SMP/E Environments, Maintenance  section based on information that is in the files. You can\nalso select the packages that are applicable within a CARS  level.\nYou can apply particular CARS  maintenance packages. You can update all products in an SMP/E environment.\nA CARS  file can list a maintenance package that the HOLDDATA marked as PE (PTF in Error). The CARS  file can also\nreflect a corrective maintenance package for this PE that is not listed in this CARS  file. This situation can occur if a\nmaintenance package is found in error after the CARS  file is published. The CARS  processing continues as expected, and\nthe maintenance package that is marked as PE is not applied. However, the CARS  level for the product is not updated to\nthe current level until you apply the corrective maintenance package to the SMP/E environment.\nConfigure Automatic CARS  File Download\nYou can configure CSM  to download available CARS  files automatically. After download, the files are stored in a USS\ndirectory under the software catalog.\n1.Select the Settings  tab, and select the Software Catalog  link under System Settings  in the Settings  section on the\nleft side.\n2.In the CARS Setting  section, select the Enable Automatic Updates  checkbox.\n3.Set up field values and select Apply .\nNOTE\nTo download available CARS  files to the software catalog immediately, select Update Immediately .\nThe automatic CARS  file download is configured.\nAdd a CARS  File", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ea98d9faa605-1", "text": "The automatic CARS  file download is configured.\nAdd a CARS  File\nIf you cannot automatically download available CARS  files, add them to the software catalog manually. Use the Add\nCARS File  link. The files that were added manually are stored in the same USS directory as other files.\n1.Download the CARS  file using FTP from the Broadcom  file server directly to your USS directory.\na.Connect to the FTP site at the following location:\nftp://ftp.broadcom.com\nb.Log in to ftp.broadcom.com as follows:\nuser name: anonymous\npassword: your-email-address\n \nc.Change to the following directory:\n/pub/ASSIGNS\nd.Change your download mode to ASCII.\ne.Download the CARS  file. These files appear in the format:\nCARyymm.TXT\n2.In the CSM  web-based interface, select the Products  tab, and select the Add CARS File  link in the Actions section on\nthe left side.\n3.Specify the USS path to the CARS  file you want to add, and select OK.\nInformation about the CARS  file is saved in the CSM  Software Catalog USS database.\nApply CARS  Maintenance to an SMP/E Environment\nYou can upgrade products that are installed in an SMP/E environment to a specific CARS  level. During processing, CSM\nverifies that maintenance packages that are associated with the selected CARS level can be applied to the products, and\nthen applies the packages.\n 291", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "859147088e6d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAs an option, CSM  lets you verify that the maintenance packages can be applied to the selected target zones without\napplying the packages.\nWhile you work with an SMP/E environment, the environment is locked and other CSM  users cannot perform any action\nagainst it. When the task finishes, logging out from CSM , or a CSM  session is inactive for more than 10 minutes, the lock\nreleases.\n1.Select the SMP/E Environments  tab.\n2.From the list on the right, locate the SMP/E environment whose products you want to upgrade the CARS  level for.\nSelect the Actions  drop-down list to the right of the SMP/E environment, and select Upgrade CARS Level .\nNOTE\nIf you select an SMP/E environment being used in CSM  by another user, a notification message appears.\nYou are prevented from performing any actions on the SMP/E environment. Wait until the notification\nmessage disappears and the SMP/E environment becomes available, or select Cancel  to select another\nSMP/E environment.\n3.Follow the instructions on the wizard to navigate through the wizard steps.\n4.From the Summary  step, review the summary and select Check and Apply .\nA dialog that shows the progress of the task opens. When the task completes, select Show Results  on the Progress\ntab to close this dialog. The task output browser opens, and you can view the action details.\nCSM  verifies and applies the CARS  maintenance packages to the selected target zones.\nIf the task fails, navigate to the Tasks tab and review SMPOUT in the task output to identify and correct problems. Rerun\nthe wizard.\nYou can accept the applied maintenance (except USERMODs) from the SMP/E Environments, Maintenance  tab.\nApply FIXCAT Maintenance", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "859147088e6d-1", "text": "Apply FIXCAT Maintenance\nCSM  lets you select and apply maintenance for your products according to FIXCAT.\nFIXCAT (fix category) associates a maintenance package to one or more categories of PTFs (for example, installation,\nfunction, z/OS version, or communication).\nFIXCAT data is provided in the same file as error HOLDDATA. Error HOLDDATA contains FIXCAT HOLDDATA statements\nthat assign a maintenance package to a category. Select a category, and CSM  determines and applies associated\nmaintenance packages to the selected products installed in an SMP/E environment.\nMasking Maintenance Categories\nWhen you select maintenance categories in the wizard, you can use masking.\nUse an asterisk (*), or a percent sign (%), or both to specify naming masks. An asterisk substitutes for any number of\nsymbols. A percent sign substitutes for one symbol.\nFor example:\nSystem.z/OS.*\nSelects all the categories whose names start with System.z/OS.\nSystem.z/OS.%%\nSelects all the categories under System.z/OS whose last segment consists of two symbols.\nApply Maintenance by FIXCAT Category\nYou can select and apply maintenance for your products based on FIXCAT using CSM .\nAs an option, CSM  lets you verify that the maintenance packages can be applied to the selected target zones without\napplying the packages.\n 292", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "52d8d212d4c3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWhile you work with an SMP/E environment, the environment is locked and other CSM  users cannot perform any action\nagainst it. When the task finishes, logging out from CSM , or a CSM  session is inactive for more than 10 minutes, the lock\nreleases.\n1.Select the SMP/E Environments  tab.\n2.From the list on the right, locate the SMP/E environment whose products you want to apply FIXCAT\nmaintenance. Select the Actions  drop-down list to the right of the SMP/E environment, and select Update Using Fix\nCategories .\nNOTE\nIf you select an SMP/E environment being used in CSM  by another user, a notification message appears.\nYou are prevented from performing any actions on the SMP/E environment. Wait until the notification\nmessage disappears and the SMP/E environment becomes available, or select Cancel  to select another\nSMP/E environment.\n3.Follow the instructions on the wizard to navigate through the wizard steps.\n4.From the Summary  step, review the summary, and select Check and Apply .\nA dialog that shows the progress of the task opens. When the task completes, select Show Results  on the Progress\ntab to close this dialog. The task output browser opens, and you can view the action details.\nCSM  verifies and applies the FIXCAT maintenance packages to the selected target zones.\nIf the task fails, navigate to the Tasks tab and review SMPOUT in the task output to identify and correct problems. Rerun\nthe wizard.\nYou can accept the applied maintenance (except USERMODs) from the SMP/E Environments, Maintenance tab.\nRestore Maintenance\nYou can restore (back out) an applied maintenance package (but not an accepted maintenance package).\nWhile you work with an SMP/E environment, the environment is locked and other CSM  users cannot perform any action", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "52d8d212d4c3-1", "text": "against it. When the task finishes, logging out from CSM , or a CSM  session is inactive for more than 10 minutes, the lock\nreleases.\n1.Select the SMP/E Environments  tab, and select the SMP/E environment from which you want to restore\nmaintenance.\n2.Select Maintenance . If you do not see any maintenance packages, verify that you have maintenance view criteria\ndefined.\n3.Select the maintenance packages that you want to restore, and select the Restore  link. You can filter out only applied\npackages.\nNOTE\nIf you select an SMP/E environment being used in CSM  by another user, a notification message appears.\nYou are prevented from performing any actions on the SMP/E environment. Wait until the notification\nmessage disappears and the SMP/E environment becomes available, or select Cancel  to select another\nSMP/E environment.\n4.Review the information about the restoring, and select Next .\n5.Review and adjust the list selections as required. Select Zones to review and adjust the zones where the maintenance\nis restored from. You can only perform maintenance actions on zones you select here. Select OK to confirm the\nselection and return to the wizard, and select Next .\n6.Review the prerequisites if they exist, and select Next . CSM  restores these prerequisites as part of the maintenance\nrestoring process.\n7.Review the summary, and select Restore .\nA dialog that shows the progress of the task opens. When the task completes, select Show Results  on the Progress\ntab to close this dialog. The task output browser opens, and you can view the action details.\n 293", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3e8975176dd0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe maintenance packages are restored.\nAccept Maintenance\nAfter maintenance has been applied, you can accept the maintenance for products that are installed in an SMP/E\nenvironment. You cannot accept USERMODs.\nUse this procedure to accept the maintenance in GROUP mode.\nWARNING\nBefore you start, update the HOLDDATA in your software catalog. To do so, select Update HOLDDATA in the\nActions  section on the Software Catalog  page. You can also set up the automatic HOLDDATA download as\ndescribed previously in this article.\nWhile you work with an SMP/E environment, the environment is locked and other CSM  users cannot perform any action\nagainst it. When the task finishes, logging out from CSM , or a CSM  session is inactive for more than 10 minutes, the lock\nreleases.\n1.Select the SMP/E Environments  tab, and select the SMP/E environment whose products you want to accept\nmaintenance.\n2.Select Maintenance . If you do not see any maintenance packages, verify that you have maintenance view criteria\ndefined.\n3.Select the maintenance packages that you want to accept, and select the Accept  link.\nNOTE\nIf you select an SMP/E environment being used in CSM  by another user, a notification message appears.\nYou are prevented from performing any actions on the SMP/E environment. Wait until the notification\nmessage disappears and the SMP/E environment becomes available, or select Cancel to select another\nSMP/E environment.\n4.Review the information about the maintenance, and select Next .\n5.Review and adjust the accept list selections as required. Select Zones  to review and adjust the zones where the\nmaintenance is accepted. You can only perform maintenance actions on zones you select here. Select OK to confirm\nthe selection and return to the wizard, and select Next .", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3e8975176dd0-1", "text": "the selection and return to the wizard, and select Next .\n6.Select the installation mode for the selected maintenance, and select Next .\n7.Perform one of the following actions to address prerequisites:\n\u2013If no prerequisites exist, select Next . A list of HOLDDATA appears.\n\u2013If prerequisites exist and are available, review them, and Select Next . A list of HOLDDATA appears. The\nprerequisites are accepted as part of the process.\n\u2013If a prerequisite is not available, the wizard cannot continue. Select Cancel  to exit the wizard. Acquire the\nprerequisite and restart the process.\n8.Review HOLDDATA entries, if they exist. Select Export Table to open all HOLDDATA information for all selected\nmaintenance in a separate browser window. Selecting Export Table is similar to running the LIST SYSMODS\nHOLDDATA command within your SMP/E environment.\n9.Select Next .\nSMP/E work DDDEFs of SMPWRK x and SYSUT x, with their allocation parameters, are listed.\n10.Review the work DDDEF allocation parameters, and edit them, if necessary, to verify that sufficient space is allocated\nfor them during the maintenance acceptance:\nNOTE\nChanges in the allocation parameters apply to the current maintenance processing only.\n1.Select Override  for a DDDEF to edit its allocation parameters.\nA pop-up window opens.\n2.Make the necessary changes, and select OK to confirm.\n 294", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "efa70e728e37-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe pop-up window closes, and the DDDEF entry is selected in the list indicating that the allocation parameters\nhave been overridden.\nYou can also:\n\u2022Update allocation parameters for the DDDEFs automatically by select Resolve Overrides.\nCSM  provides values for all DDDEFs based on the total size of the selected maintenance packages being\naccepted. All DDDEF entries are selected in the list indicating that the allocation parameters have been overridden.\nNOTE\nTo edit the allocation parameters for a DDDEF after automatically updating them with the Resolve\nOverrides button, select Override . Make the necessary changes. Select OK to confirm and return to the\nwizard.\n\u2022Cancel a parameter update for any DDDEF by clearing its checkbox.\n11.(Optional) Select View SMP/E Work DDDEFs to review SMP/E work DDDEF and their allocation parameters for the\nselected SMP/E environment zones. Select Close  to return to the wizard.\nNOTE\nSometimes, the allocation parameters differ from the allocation parameters that you obtained using the\nResolve Overrides  button.\nSelect Next .\n12.Review the summary, and select Accept .\nA dialog that shows the progress of the task opens. When the task completes, select Show Results  on the Progress\ntab to close this dialog. The task output browser opens and you can view the action details.\nThe maintenance packages are accepted.\nAccept Maintenance in GROUPEXTEND Mode\nCSM  lets you invoke the SMP/E utility with the GROUPEXTEND option enabled for accepting maintenance.\nWhen you accept maintenance in GROUPEXTEND mode, the following installation modes are available:\nAccept Check\nChecks if the maintenance can be accepted to the selected SMP/E environment in GROUPEXTEND mode.\nAccept\nAccepts the maintenance to the selected SMP/E environment in GROUPEXTEND mode.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "efa70e728e37-1", "text": "Accepts the maintenance to the selected SMP/E environment in GROUPEXTEND mode.\nAccept Check and Accept\nChecks if the maintenance can be accepted to the selected SMP/E environment in GROUPEXTEND mode. Then\naccepts it if possible.\nFor the GROUPEXTEND option, CSM  does not automatically receive and display maintenance or HOLDDATA\nprerequisites that must be bypassed when accepting the maintenance. Accept check mode lets you check if any\nprerequisites or HOLDDATA exist and report them in the task output.\nHow Maintenance in GROUPEXTEND Mode Works\nAccept maintenance in GROUPEXTEND mode in the following sequence:\n1.Apply all maintenance packages that you want to include by the GROUPEXTEND option.\n2.Run the maintenance in Accept check mode.\n\u2013If the task fails, review SMPOUT in the task output. Review if there are missing (not applied) maintenance\npackages or HOLDDATA that must be resolved or bypassed.\n\u2013If the task succeeds, review SMPRPT in the task output. Review what maintenance packages were found and\naccepted.\n 295", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "894cc6d986c6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n3.Run the maintenance in Accept mode. Specify the maintenance packages that you want to exclude and HOLDDATA\nthat you want to bypass, if any exist.\nThe followings options are available for bypassing HOLDDATA:\n\u2013HOLDSYSTEM\n\u2013HOLDCLASS\n\u2013HOLDERROR\n\u2013HOLDUSER\nYou can run the maintenance in Accept mode in the same CSM  session after Accept check mode is completed. The\nvalues that you entered for Accept check mode are then prepopulated on the wizard dialogs.\nAccept Maintenance with the GROUPEXTEND Option Enabled\nYou can accept maintenance (except USERMODs) with the GROUPEXTEND option enabled.\nWhile you work with an SMP/E environment, the environment is locked and other CSM  users cannot perform any action\nagainst it. When the task finishes, logging out from CSM , or a CSM  session is inactive for more than 10 minutes, the lock\nreleases.\n1.Select the SMP/E Environments  tab, and select the SMP/E environment holding the maintenance packages that you\nwant to accept in GROUPEXTEND mode.\n2.Select Maintenance .\nMaintenance packages available for the products are listed. If you do not see any maintenance packages, verify that\nyou have maintenance view criteria defined.\n3.Select the maintenance packages that you want to accept in GROUPEXTEND mode, and select the Accept\nGROUPEXTEND link.\nNOTE\nIf you select an SMP/E environment that is being used by another user, a notification message appears. You\nare prevented from performing any actions on the SMP/E environment. Wait until the notification message\ndisappears and the SMP/E environment becomes available, or select Cancel  to select another SMP/E\nenvironment.\n4.Review the information about the maintenance, and select Next .", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "894cc6d986c6-1", "text": "environment.\n4.Review the information about the maintenance, and select Next .\nThe packages that you want to accept are listed.\nNOTE\nSelect a link in the Status column for a maintenance package, if available, to review a list of zones. The\nzones indicate where the maintenance package is received, applied, or accepted. Select Close  to return to\nthe wizard.\n5.Review the packages, and select Next .\nWARNING\nFor the GROUPEXTEND option, CSM  does not automatically receive and display maintenance or\nHOLDDATA prerequisites that must be bypassed when accepting the maintenance. Accept check mode lets\nyou review if any prerequisites or HOLDDATA exist and report them in the task output. Run the maintenance\nin Accept check mode first.\n6.Read the information that is displayed on this tab, and select Next .\nThe installation options appear.\n7.Specify installation options as follows, and select Next :\na.Select the installation mode for the selected maintenance.\nb.Review the GROUPEXTEND options and select the ones that you want to apply to the maintenance:\nNOAPARS\nExcludes APARs that resolve error reason ID.\n 296", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "15c0f08d6504-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOUSERMODS\nExclude USERMODs that resolve error reason ID.\nc.(Optional) Enter maintenance packages that you want to exclude in the Excluded SYSMODs field. You can enter\nseveral packages, separate them by a comma.\nThe Bypass HOLDDATA step of the wizard appears.\n8.(Optional) Enter the BYPASS options for the HOLDDATA that you want to bypass during the maintenance installation.\nYou can enter several BYPASS options, separate them by a comma.\n9.Select Next .\n10.Review the summary, and select Accept GROUPEXTEND .\nA dialog that shows the progress of the task opens. When the task completes, select Show Results  on the Progress\ntab to close this dialog. The task output browser opens, and you can view the action details.\nNOTE\n\u2022If you run the maintenance installation in Accept check mode and the task succeeds, review SMPRPT in\nthe task output. Review what maintenance packages were found and accepted.\n\u2022If you run the maintenance installation in Accept check mode and the task fails, review SMPOUT in the\ntask output. Review if there are missing (not accepted) maintenance packages or HOLDDATA that must\nbe resolved or bypassed.\nYou completed maintaining products with CSM .\nMaintain Products Using SMP/E JCL\nAs a systems programmer, your responsibilities include maintaining products and maintenance packages in your\nmainframe environment. You can download, receive, apply, and accept maintenance manually. After you complete the\nmaintenance process, the product is ready to deploy.\nDownload and Receive Maintenance\nPTF Maintenance and HOLDDATA are available at Broadcom Support . To download and receive maintenance, use SMP/\nE Receive Order or the following procedure during product installation and for ongoing preventive maintenance in non-\ninstallation use cases according to your maintenance strategy.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "15c0f08d6504-1", "text": "installation use cases according to your maintenance strategy.\nWe recommend that you use SMP/E Internet Service Retrieval  to submit requests securely for PTFs and HOLDDATA\nto a remote Broadcom  server. This service eliminates the manual steps that are required to download the PTFs and\nHOLDDATA from Broadcom Support . The orders are fulfilled based on the status of your SMP/E environments. Based on\nyour order criteria, all PTFs and their requisites are downloaded automatically and received to your system. See Configure\nSMP/E Internet Service Retrieval .\nYou can also download maintenance manually from Broadcom Support . With this option, you manually select PTFs\nand build a package for all applicable PTFs and requisites. You then use the CAUNZIP utility to unpackage and receive\nthe files. This utility processes ZIP packages directly on z/OS without the need for an intermediate platform, such as a\nMicrosoft Windows workstation. The utility resides in yourCCSHLQ .CAW0JCL(CAUNZIP). To use this download option,\nyou must be running Common Components and Services  Version 15.0. Review the CAUNZIP requirements .\n1.Select one of the following options to create a PTF maintenance package:\n\u2013Use SMP/E Internet Service Retrieval  to download and receive maintenance. To do so, see Configure SMP/E\nInternet Service Retrieval .\nAfter your PTFs are downloaded and received, you are ready to apply and accept maintenance. To do so, go to\nApply and Accept Maintenance .\n\u2013Select the PTFs manually, and then use the CAUNZIP utility to unpackage and receive the files. To do so, go to\nstep 2 and complete the remaining steps in this procedure.\n 297", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "abf603c1d3b3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n2.Go to Broadcom Support  at https://support.broadcom.com , and select Software , Mainframe Software , and My\nDownloads.\n3.Log in using your Broadcom Support  username and password.\nThe My Downloads - Mainframe Software  page appears.\n4.Select a product from the list or search by product name and then select a product from the list.\nThe product page appears with two tabs under the product name: Products  and Solutions .\n5.Select the Solutions  tab and select the product that you want.\nA list of releases appears.\n6.Use the hypertext link to select the release that you want.\nA list of published solutions appears with the most recently published solutions shown first.\n7.Select the checkbox next to the solutions that you want to download.\nNOTE\nTo filter the list, search by solution number, CARS level, or description. You can also select an operating\nsystem or component. For download solution search tips, see Solution Download Help .\n8.Select a download method:\n\u2013Select Download Selected  to go to the Download Manager . Use this option to create a complete solution\npackage that includes all requisite solutions back to an optional date. From the Download Manager, you can select\nyour download method (HTTPS or Secure FTP).\n\u2013Select HTTPS Download  to start downloading immediately. Check your browser for the download progress.\n\u2013Select Secure FTP  Download  to download securely from downloads.broadcom.com. This option is the fastest and\nmost efficient download method.\nFor assistance, see Solution Download Help . For HTTPS and Secure FTP information, and sample JCL, see\nDownload Methods and Locations .\nThe solution package is downloaded.\n9.Run the CAUNZIP utility by completing the following steps.\nCAUNZIP unzips the package of published solutions and creates an SMPNTS file structure that the SMP/E RECEIVE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "abf603c1d3b3-1", "text": "FROMNTS command can process. After execution completes, the ZIPRPT data set contains the summary report. The\nsummary report:\n\u2013Summarizes the content of the product order ZIP file.\n\u2013Details the content of each data set and the z/OS UNIX files produced.\n\u2013Provides a sample job to receive the PTFs in your order.\n10.Review the sample job that is provided in the CAUNZIP output ZIPRPT file and then complete the following steps:\na.Cut and paste the JCL into a data set.\nb.Specify your SMP/E CSI on the SMPCSI DD statement.\nc.Submit the job to receive the PTFs in your order.\n11.Verify that you have the values from the base installation in the AVHSEDIT macro, which you customized in the\ninstallation steps.\n12.Open the SAMPJCL member AVH60RCH in an edit session and execute the AVHSEDIT macro from the command\nline.\nNOTE\nUpdate AVH60RCH SAMPJCL to download the HOLDDATA file.\nAVH60RCH is customized.\n13.Submit AVH60RCH.\nThe job downloads the external HOLDDATA file.\nThe maintenance packages are received to the SMP/E environment global zone. After maintenance has been\ndownloaded for a product, you can apply and optionally accept the maintenance for products that are installed in the SMP/\nE environment. Go to Apply and Accept Maintenance .\n 298", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0306c109149b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nApply and Accept Maintenance\nAfter downloading and receiving your maintenance package, use this procedure to apply and optionally accept corrective\nmaintenance.\nWARNING\nBefore you apply maintenance, ensure that any required file systems are mounted and that you have specified\nthe correct path to the DDDEFs that are contained in the file systems. The path must be the mount point of the\nzFS file system, plus the directory /CA. For example, if the zFS file system is mounted at /cai/abc, the DDDEF\npath must be /cai/abc/CA.\n1.Open the SAMPJCL member AVH80APM in an edit session and execute the AVHSEDIT macro from the command\nline.\nAVH80APM is customized.\n2.Submit AVH80APM.\nThe PTFs are applied.\n3.(Optional) Open the SAMPJCL member AVH90ACM in an edit session and execute the AVHSEDIT macro from the\ncommand line.\nAVH90ACM is customized.\n4.(Optional) Submit AVH90ACM.\nThe PTFs are accepted.\nNOTE\nYou do not have to submit the job now. You can accept the PTFs according to your site policy.\nCorrective maintenance is complete. You can now optionally apply CARS  maintenance .\nApply CARS  Maintenance\nUse this procedure to apply CARS  maintenance as a part of managing preventive maintenance.\nNOTE\nFor information about CARS  maintenance, see CARS  in the Mainframe Common Maintenance Procedures\ndocumentation.\n1.Download the ASSIGN statements.\nIMPORTANT\nThe ASSIGN files are not cumulative. To install the latest RS level, download all YEARLY ASSIGN\nstatements, and then download the monthly ASSIGN files as needed.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0306c109149b-1", "text": "statements, and then download the monthly ASSIGN files as needed.\na.Determine whether to download the yearly or monthly ASSIGN statements in the following files:\nftp.broadcom.com/pub/ASSIGN/YEARLY/YEAR yyyy.TXT\nftp.broadcom.com/pub/ASSIGN/CAR yymm.TXT\nb.Open the SAMPJCL member AVH50CAR in an edit session, update AVH50CAR SAMPJCL to download your\nASSIGN statements from Broadcom Support , and execute the AVHSEDIT macro from the command line.\nAVH50CAR is customized.\n2.Submit AVH50CAR.\nThe job downloads the ASSIGN statements.\n3.Open the SAMPJCL member AVH70RCM in an edit session, manually add the data set that contains the ASSIGN\nstatements to the SMPPTFIN DD, and execute the AVHSEDIT macro from the command line.\nAVH70RCM is customized.\n4.Submit AVH70RCM.\nThe job receives the external HOLDDATA file and ASSIGN statements.\n5.Open the SAMPJCL member AVH80APM in an edit session and execute the AVHSEDIT macro from the command\nline.\nAVH80APM is customized.\n 299", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "11ba1f0898c2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n6.Submit AVH80APM.\nThe CARS  PTFs are applied.\n7.(Optional) Open the SAMPJCL member AVH90ACM in an edit session and execute the AVHSEDIT macro from the\ncommand line.\nAVH90ACM is customized.\n8.(Optional) Submit AVH90ACM.\nThe CARS  PTFs are accepted.\nNOTE\nYou do not have to submit the job now. You can accept the PTFs according to your site policy.\nHOLDDATA\nWhen you apply maintenance, you typically encounter SMP/E HOLDDATA. We use HOLDDATA to notify your SMP/E\nsystem of SYSMODs that have errors or special conditions. We support system and external HOLDDATA.\nSystem HOLDDATA\nSystem HOLDDATA indicates data that is an in-stream part of the SYSMOD, informing you of special conditions. The\nfollowing reasons are used with SYSTEM HOLDDATA for your product.\nACTION Indicates that you must perform special processing before or after you apply this SYSMOD.\nAO Affects automated operations. It changes the message identifier or the displacement of a field inside the\nmessage.\nDB2BIND Indicates that DBRMs have changed and packages must be rebound.\nDDDEF Indicates that data sets and DDDEFs are being added or modified.\nDELETE Deletes the SYSMOD load module. You cannot reverse this type of SYSMOD with the SMP/E RESTORE\ncommand.\nDEP Indicates a dependency for this SYSMOD that you must externally verify.\nDOC Indicates a documentation change with this SYSMOD.\nDOWNLD Indicates that some or all the elements that this SYSMOD delivers are to be downloaded to a workstation.\nDYNACT Describes the steps to dynamically activate this fix without performing an IPL.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "11ba1f0898c2-1", "text": "DYNACT Describes the steps to dynamically activate this fix without performing an IPL.\nEC Indicates that this SYSMOD requires a hardware engineering change. An EC hold SYSMOD usually does\nnot affect the product unless the EC is present on the hardware device.\nENH Introduces a small programming enhancement. The hold contains the instructions to implement the\nenhancement. If no action is required to implement the enhancement, give a summary of the enhancement.\nEXIT Indicates that changes delivered by this SYSMOD require reassembly of user exits.\nEXRF Indicates that the SYSMOD must be installed in both the Active and Alternate Extended Recovery Facility\nSystems.\nIPL Indicates that an IPL is required for this SYSMOD to take effect. This option is used only when there is no\nalternative for dynamic activation.\nMSGSKEL Indicates that the SYSMOD contains internationalized message versions that must be run through the\nmessage compiler for each language.\nMULTSYS Apply this SYSMOD to multiple systems for pre-conditioning, coexistence, or exploitation.\nRESTART Indicates that after applying this SYSMOD, the site must perform a special restart as opposed to a routine\nrestart.\nSQLBIND Indicates that a bind is required for a database system other than DB2.\nExternal HOLDDATA\nExternal HOLDDATA is not part of the PTF. The HOLDDATA resides in a separate file and contains both error and FIXCAT\nHOLDDATA. The error HOLDDATA is used for SYSMODs that have been distributed and later are discovered to cause\n 300", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2607ff70123e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nproblems. The FIXCAT HOLDDATA helps identify maintenance that is required to support a particular hardware device,\nsoftware, or function.\nDownload the external HOLDDATA from Broadcom Support  to a DASD file, and allocate the file to the SMPHOLD\nDD statement. To take care of the external HOLDDATA, receive it into your SMP/E environment. SMP/E receives the\nHOLDDATA from Broadcom -supplied jobs.\nYou can find JCL to download the external HOLDDATA in your SAMPJCL member. Open xxx60RCH or xxx1HOLD in\nan edit session and execute the xxxSEDIT macro on the command line ( xxx is the high-level identifier for your product).\nThen, submit the JCL.\nError HOLDDATA\nIf a SYSMOD has unresolved error HOLDDATA, SMP/E does not install it unless you add a bypass to your APPLY\ncommand. You can bypass error HOLDDATA in situations that are not applicable to you. Error HOLDDATA that is not\napplicable to you can include a problem that happens only with a hardware device that you do not have or in a product\nfeature that you do not use.\nWhen Broadcom  publishes a SYSMOD that resolves the error HOLDDATA, the resolving SYSMOD supersedes the error\nHOLDDATA. This action lets you apply the original SYSMOD with the fixing SYSMOD.\nThe only manual task is running a REPORT ERRSYSMODS. This report identifies the following:\n\u2022Any held SYSMODs already applied to your system\n\u2022Any resolving SYSMODs that are in RECEIVE status\nSMP/E identifies the SYSMOD to apply to correct the situation.\nFIXCAT HOLDDATA\nBroadcom  provides FIXCAT HOLDDATA to help identify maintenance that is required to support a particular hardware", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2607ff70123e-1", "text": "device, software, or function. Fix categories are supplied as SMP/E FIXCAT HOLDDATA statements. Each FIXCAT\nHOLDDATA statement associates an APAR and its related fixing PTF to one or more fix categories.\nDeployment\nThis article contains information about deploying your product.\nPrepare for Deployment\nApply IBM APARs\nThe informational APAR or Product Information Bulletin (PIB) is official information relative to a product. Download PIBs\nfrom Broadcom Support.\nThe naming convention for PIBs is RIxxxxx. RI identifies an informational APAR. xxxxx is an identification number.\nProgram Temporary Fixes\nA Program Temporary Fix (PTF) is an official replacement module or modules that fixes one or more problems. The\nnaming convention for PTFs is ROxxxxx, where xxxxx is a unique identifier. Download PTFs from Broadcom Support.\nDeploy Using CSM\nA deployment  is a CSM  object that you create to deploy libraries and data sets using a process that copies target\nlibraries defined to SMP/E and user data sets across both shared DASD and networked environments. A deployment\n 301", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4c5e3409aef4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nhelps automate the creation of libraries in a target environment. Use a deployment to deploy your product in multiple\nenvironments, for example in a staging and non-staging (production) environment.\nEach deployment must have a methodology . You use a methodology as a template to specify how data sets are named\non the target system. A methodology provides the what  of a deployment, that is, what you want to call your data sets. A\nmethodology is a named object with a description that is assigned to an individual deployment.\nWhen setting up data set names, use your company naming standards and conventions. A methodology lets you copy\nproducts and data sets to the target system and rename them as you copy. The methodology also lets you specify a\ndisposition, which means you can overwrite the data set if it exists. Conversely, you can create data sets on the target\nsystem.\nFollow these steps:\n1.Set up the system registry:\na.Determine the systems you have at your enterprise.\nb.Set up remote credentials for those systems.\nc.Set up the target systems (non-sysplex, sysplex or monoplex, shared DASD cluster, and staging), and validate\nthem.\nd.Add network information, including data destination information, to each system registry entry.\n2.Set up methodologies.\n3.Create the deployment, which includes completing each step in the New Deployment wizard.\nAfter creating the deployment, you can save it and change it later by adding and editing systems, products, custom\ndata sets, and methodologies, or you can deploy directly from the wizard.\nNOTE\nIf you must deploy other products to the previously defined systems using the same methodologies, you\nmust create a separate deployment.\n4.Deploy the product, which includes taking a snapshot, transmitting to target, and deploying (unpacking) to your\nmainframe environment.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4c5e3409aef4-1", "text": "mainframe environment.\nAfter the deployment process completes, the product is ready for you to configure.\nYou may have to perform other steps manually outside of CSM  before beginning the configuration process.\nDeploy Without CSM\nFollow the procedures in Configure Your Product Without CSM  before starting any of the products.\nTo complete deployment for InterTest and SymDump, deploy a runtime copy of all target libraries specified in Product\nRequirements.\nInstalling the Eclipse User Interface\nInstall the Eclipse User Interface to access InterTest and SymDump applications through an Eclipse-based graphical user\ninterface (Eclipse UI).\nThis article describes how to install the InterTest and SymDump Plus Eclipse plug-ins.\nYou can use a standard Eclipse IDE or any Eclipse-based IDE of your choice to install the InterTest and SymDump plug-\nins into. Examples of IDEs you can use include:\n\u2022 The standard Eclipse IDE, which is available on the Eclipse official website.\n\u2022 IBM Explorer for z/OS (z/OS Explorer), which is an Eclipse-based integration platform for z/OS users.\nPrerequisites:\n 302", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "843f0ece4d96-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Eclipse-based IDE\n\u2022To provide functionality for the Eclipse UI, the Testing Tools Server must be installed and running on\nthe mainframe. Contact your system programmer to get the host and port of the Testing Tools Server.\n\u2022Confirm the server and the plug-in version compatibility:\na.Navigate to the following URL:  http://host:port/software  .\nThe website displays the current version of the server, for example: 11.1.0.\nNOTE\nUse https:// host:port /software  for a secure connection.\nb.Note the server version number. This number is required to ensure that you select the correct plug-in.\nc.Determine the correct plug-in version to install using the instructions on the Eclipse Plug-in Compatibility  page.\nFollow these steps:\nInterTest\n1.In Eclipse, go to Help , Install New Software .\n2.Select  Add , and enter the url:  https://plugins.packages.broadcom.com/artifactory/ca-plugins/\nintertest-plugin\n3.Select the plug-in version that you require.\n4.Click Next .\n5.Accept the license agreement that appears, and click Finish .\nSymDump\n1.In Eclipse, go to Help , Install New Software .\n2.Select Add, and enter the url:  https://plugins.packages.broadcom.com/artifactory/ca-plugins/\nsymdump-plugin\n3.Select the plug-in version that you require.\n4.Click Next .\n5.Accept the license agreement that appears, and click Finish .\nYou added the application plug-in and can now access the application as a new perspective.\nNOTE\n\u2022When you install the Eclipse plug-in for InterTest and SymDump products, you might receive a provisioning\nerror in the Eclipse error log. This error does not impact the product functionality and can be ignored.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "843f0ece4d96-1", "text": "error in the Eclipse error log. This error does not impact the product functionality and can be ignored.\n\u2022You can install the plug-ins for multiple InterTest and SymDump products. We recommend that you install\nonly one instance of the Broadcom  Testing Tools Eclipse Runtime Components.\n\u2022If you do not have access to the public repository, use the following latest zipped plug-in versions and share\nthe files locally within your environment:\n\u2013https://plugins.packages.broadcom.com/artifactory/ca-plugins/intertest-plugin/\nzipped/\n\u2013https://plugins.packages.broadcom.com/artifactory/ca-plugins/symdump-plugin/\nzipped/\nInstall Testing Tools Server and REST API\nInstall the Testing Tools Server and REST API.\nThis article describes how to install the Testing Tools Server, also known as the GUI Server or Mainframe Support.\nSymDump  Batch functionality is also available through a REST API that you can use for your application programming\nneeds. The Testing Tools Server provides functionality for the following components:\n 303", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9604201d6833-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Eclipse UI\n\u2022Debugger for Mainframe extension for VS Code and Che\n\u2022SymDump Batch REST API\nThe REST API and the Eclipse UI run on an instance of Apache Tomcat Server.\nImplementation Options\nSingle Tomcat Install\nApache Tomcat lets you use the same binaries to share the binary executables and run separate instances of\nApache Tomcat for different applications in your environment. With this option, you can have unlimited Apache Tomcat\ninstances and maintain only one Apache Tomcat installation. To apply a program fix, patch the Apache tomcat installation\nand restart all of your Apache Tomcat instances individually. Without a Single Install, a copy of the binaries is stored within\neach instance.\nNOTE\nA CCS Tomcat installation is created when the TOMDPLOY job is executed.\nShared Tomcat Instance\nThe InterTest and SymDump Testing Tools Server and REST API can be deployed to an existing Apache Tomcat instance\nthat is shared with other applications. For example, all testing tools products can share one Tomcat instance. With this\noption, you maintain only one server and configuration file, and you use the same address and port for all services running\non the server.\nNOTE\n\u2022Running multiple applications on one Tomcat instance might have a negative impact on performance. This\nimpact depends on the workload and number of clients who access the Tomcat server.\n\u2022Due to heavy memory consumption, we recommend that you run Tomcat on 64-bit Java for a shared\ninstance.\nPrerequisites\nApache Tomcat 8.5 web server or higher\nApache Tomcat web server is a prerequisite for the Testing Tools Server and the REST API. Ensure that you\nhave Apache Tomcat 8.5 or higher installed. For instructions about how to deploy and configure the CCS Apache", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9604201d6833-1", "text": "Tomcat server, see the Deploy and Configure CCS Apache Tomcat section of the Common Components and\nServices  for z/OS  documentation.\n(Optional) HTTPS secure communication\nTo enable HTTPS communication on the Tomcat server and secure the Apache Tomcat web server, follow the\nsteps in the Set Up Security for CCS Apache Tomcat section of the Common Components and Services  for z/OS\ndocumentation.\nAllocation, Deployment, and Configuration of the Testing Tools Server\nFollow these steps:\n1.Modify CAVHJCL data set member CAVHALOC as described within the JCL and execute the job. This job allocates,\ninitializes, and mounts a Broadcom  Testing Tools server instance file system, and creates the starting directory inside.\nIf this step is not needed and you do not have restricted privileges, ignore the error that is generated.\n 304", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b9ec5e11f08d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nInfo: This attribute is not needed unless your STEPLIB is PROGRAM CONTROLLED.\n2.Modify CAVHOPTN data set member CAVHUOPT as described within the member. This file is used as the input to the\nserver that provides product and runtime directory information.\n3.Modify CAVHPROC data set member CAVHSRVR to your site standards, and copy to a system procedure library.\nThis JCL is used to start the Broadcom  Testing Tools server. The owner of the CAVHSRVR job requires access to IBM\nSURROGAT class BPX.SRV. Ensure that the owner has read access to the following IBM BPX facilities:\n\u2013BPX.DAEMON.HFSCTL\n\u2013BPX.FILEATTR.APF\n\u2013BPX.FILEATTR.PROGCTL\n\u2013BPX.SERVER\n\u2013BPX.SUPERUSER\nNOTE\n\u2022If you use CSM  to configure your product, this manual operation replaces the InterTest Common User\nInterface server procedure, CAHVSRVR, in the system PROCLIB. If you previously customized and do\nnot want to replace CAHVSRVR, confirm this operation when you implement the configuration.\n\u2022To have CSM  execute this step automatically during the implementation, change the operation value from\nManual  (Default) to Automatic  before you release the task.\n4.Modify CAVHJCL data set member CAVHDPLY as described within the JCL and execute to a successful completion.\nThis job deploys the Broadcom  Testing Tools server components to the file system allocated by the previous step.\nActivation of the IP CICS Sockets\nTo install the Eclipse UI for InterTest for CICS or SymDump  for CICS, or to use the Debugger for Mainframe extension for", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b9ec5e11f08d-1", "text": "VS Code and Che to debug CICS programs, activate the IP CICS sockets in the CICS region. For more information, see\nthe IBM z/OS Communications Server IP CICS Sockets Guide.\nFollow these steps:\n1.Update the CICS startup JCL to include TCP/IP data sets.\na.Add your site TCPIP.SEZATCP data set to the DFHRPL concatenation.\nb.Add a TCPDATA DD statement:\n//TCPDATA  DD SYSOUT=*,DCB=(DSORG=PS,RECFM=V,BLKSIZE=136)\nc.Add an EZACONFG DD that points to your configuration data set. For more information, see step 4.\nd.Add a SYSTCPT DD statement:\n//SYSTCPT DD SYSOUT=*\n2.Define the TCP/IP resources to CICS.\na.Use TCPIP.SEZAINST(EZACICCT) to add RDO definitions to your CICS region.\nb.Set SIT option TCPIP= to YES:\nTCPIP=YES\n3.Define the CICS region to TCP/IP. Define the CICS region and ports your CICS region uses in hlq.PROFILE.TCPIP.\n4.Build the TCP/IP configuration data set.\na.Use IBM sample configuration member TCPIP.SEZAINST(EZACICFG) to define TCP/IP in your CICS region by\nrunning a CSD upgrade (DFHCSDUP).\nb.Update the APPLID= and TCPADDR= parameters to your site-specific names.\nNOTE\nThese steps are the minimum requirements to activate IP CICS sockets for the common user interface. To\nset up IP CICS sockets for the first time, see the IBM z/OS Communications Server IP CICS Sockets Guide .\n 305", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "db93685f9c01-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe IBM guide details all available EZACICD parameters and extra functionality of IP CICS sockets that are\navailable for your implementation.\nSet Up an IRC Connection\nTo install the Eclipse UI for InterTest for CICS, or to use the Debugger for Mainframe extension for VS Code and Che to\ndebug CICS programs, define the connection and session resources for your CICS region. For more information, refer to\nthe IBM CICS Transaction Server documentation.\nModify and submit the CAI.CAVHJCL data set member CSDJ2C## as described within the JCL, and execute to a\nsuccessful completion. This job defines the resources necessary for connections through the CICS EXCI interface. This\njob also updates the DFHCSD data set that is used for InterTest for CICS and SymDump  for CICS.\nNOTE\nInfo: Replace ## with your two-digit CICS release number:\n\u202268 for CICS 5.1\n\u202269 for CICS 5.2\n\u202270 for CICS 5.3\n\u202271 for CICS 5.4\n\u202272 for CICS 5.5\n\u202273 for CICS 5.6\n\u202274 for CICS 6.1\nUpdate your CICS region startup JCL to include the following system initialization parameters:\nISC=YES\nAllow programs for intersystem communications.\nIRCSTRT=YES\nAllow IRC to start up at the system initialization.\n(Optional) Configure the Testing Tools Server for Secure Connection\nTo configure the Testing Tools Server for a secure connection, set up security for your CCS Apache Tomcat environment.\nTIP\nUse a secure connection if the UI is accessible from outside a secure private network.\nFollow these steps:\n1.Stop the Apache Tomcat server.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "db93685f9c01-1", "text": "Follow these steps:\n1.Stop the Apache Tomcat server.\n2.Follow the instructions in the Deploy CCS Apache Tomcat and Configure Security section of the Common\nComponents and Services  for z/OS  documentation.\n3.Restart the Apache Tomcat server.\nThe Testing Tools Server is configured for a secure connection.\nIntegrate REST API with the Mediation Layer\nThe API Mediation Layer provides a single point of access for mainframe service REST APIs, and offers the following\nenterprise, cloud-like features:\n 306", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3ff69633f375-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022High-availability\n\u2022Scalability\n\u2022Dynamic API discovery\n\u2022Consistent security\n\u2022A single sign-on experience\n\u2022Documentation\nThe API Mediation Layer facilitates secure communication across loosely coupled microservices through the API\nGateway. The API Mediation Layer includes an API Catalog that provides a user-friendly interface to view all discovered\nmicroservices, their associated APIs, and Swagger documentation. The Discovery Service lets you determine the location\nand status of microservice instances that run inside the ecosystem.\nIntegration with the API Mediation Layer is optional and provides additional benefits. You can still use\nthe SymDump Batch REST API without the API Mediation Layer.\nAPI Mediation Layer Key Features\nConsistent Access\nAPI call routing, and the normalization of API service URLs through the built-in Gateway component, provide API\nMediation Layer users with a consistent way to access mainframe APIs at a static IP location.\nDynamic Discovery\nThe Discovery Service component frees clients from having to determine the location and status of API service\ninstances that run inside the ecosystem.\nHigh Availability\nThe API Mediation Layer is designed with high availability and scalability through DVIPA running on z/OS.\nRedundancy and Scalability\nThe Gateway increases API service throughput without the need for API consumers to change configuration\nsettings by simply starting multiple API service instances.\nPresentation of Services\nThe API Catalog component provides easy, user-friendly access to discovered API services and their associated\nAPI documentation. Access to the contents of the API catalog is controlled through z/OS security.\nEncrypted Communication\nAPI Mediation Layer facilitates secure communication across internal components and discovered API services\nthrough the Gateway.\n 307", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e15ad9e5d017-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPlatform Independence\nSince the API Mediation Layer is implemented in Java, the Layer targets z/OS as a platform, but can also run on\nother platforms as needed.\nInstall the API Mediation Layer\nDownload the API Mediation Layer package pax file from Broadcom Support under Download Management.\nIntegrate with the API Mediation Layer\nIntegrate a REST API with the API Mediation Layer to make a REST API discoverable through the API catalog.\nFollow these steps:\n1.Enable HTTPS connection between the API Mediation Layer and the Testing Tools Server.\nIMPORTANT\nYou must import the public certificate of the Certificate Authority (CA) that signed the service certificate\ninto the API Mediation Layer trustStore. For more information about the Testing Tools Server HTTPS\nconfiguration, see Deploy and Configure CCS Apache Tomcat. For more information about the API\nMediation Layer HTTPS configuration, see Import an API ML CA Certificate to a Browser  in the Brightside\ndocumentation\n2.(Optional) To use the Single Sign-On feature of the API Mediation Layer, configure PassTickets to be used by the API\nMediation Layer. For more information, see Configure PassTickets for the API Mediation Layer.\n3.Modify the CAVHJCL  data set member CAVHRAGC  as described within the JCL, and execute to successful completion.\nThe SymDump  Batch REST API is registered with the API Mediation Layer.\nNOTE\nEnsure that you install the SymDump Batch REST API before you integrate with the API Mediation Layer.\n4.To verify that the integration is successful, go to the API Catalog home page and ensure that the SymDump Batch\nREST API service is displayed.\nThe SymDump Batch REST API is integrated with the API Mediation Layer.\nConfigure PassTickets for the API Mediation Layer\nConfigure API Mediation Layer PassTickets for SymDump .", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e15ad9e5d017-1", "text": "Configure API Mediation Layer PassTickets for SymDump .\nA PassTicket is a temporary substitute for a password. PassTickets are encoded and encrypted and are only valid for a\nfew minutes after they are generated. Use PassTickets to enable z/OS components and products to authenticate a user\nID without storing or caching z/OS passwords, or sending the passwords through the network.\nConfigure PassTickets for the z/OS security product on each z/OS system that hosts a Testing Tools Server and API\nMediation Layer. As a system programmer, you are responsible for security administration in your environment. You can\nuse the following tools to configure PassTicket to enhance and optimize user ID authentication:\n\u2022IBM Resource Access Control Facility (RACF)\n\u2022Top Secret\n\u2022ACF2\nBefore you proceed, confirm with your security administrator whether these processes require modification to\naccommodate your environment and standards.\n 308", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "83b50788e505-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nConfigure the Application ID\nPassTickets enable you to access a specific application only, corresponding to the application ID used during\nconfiguration. By default, the SymDump application ID is SDAPPL. To change this application ID, modify FMM_APPLID in\nthe CAWAUOPT options in CDBIOPTN.\nUse ACF2  to configure PassTickets.\nFollow these steps:\n1.Define profiles for the application in the PTKTDATA class and specify the session key.\nSubmit the following commands:\nSET PROFILE(PTKTDATA) DIVISION(SSIGNON)\nINSERT applid SSKEY(key) MULT-USE\nF ACF2,REBUILD(PTK),CLASS(P)\napplid\nSpecifies the application ID used for PassTicket validation to authenticate connections to the server.\nDefault:  SDAPPL\nkey\nSpecifies a 16-digit hexadecimal encryption key for the application. Ensure that the application key is the same\nacross all systems in the configuration, and that the key is secret and secured.\n2.Permit the started tasks for Zowe and the Testing Tools Server to generate and evaluate PassTickets, respectively.\nSubmit the following commands:\nSET RESOURCE(PTK)\nRECKEY IRRPTAUTH ADD(applid.userid UID(sdtask) SERVICE(READ) ALLOW)\nRECKEY IRRPTAUTH ADD(applid.userid UID(zowetask) SERVICE(UPDATE) ALLOW)\napplid\nSpecifies the application ID used for PassTicket validation to authenticate connections to the server.\nDefault:  SDAPPL\nuserid\nSpecifies the user ID for which you want to grant server access. This value can be wildcarded. To grant access to\nall users, specify * .\nsdtask\nSpecifies the started task ID for your Testing Tools Server instance.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "83b50788e505-1", "text": "sdtask\nSpecifies the started task ID for your Testing Tools Server instance.\nzowetask\nSpecifies your Zowe started task ID.\nDefault:  IZUSVR\nYou have configured Single Sign-On for the SymDump Batch REST API on the API Mediation Layer.\nUse Top Secret to configure PassTickets.\nFollow these steps:\n1.Define profiles for the application in the PTKTDATA class and specify the session key.\nSubmit the following command:\nTSS ADDTO(NDT) PSTKAPPL(applid) SESSKEY(key) SIGNMULTI\napplid\nSpecifies the application ID used for PassTicket validation to authenticate connections to the server.\nDefault:  SDAPPL\n 309", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d85fdd0503bb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nkey\nSpecifies a 16-digit hexadecimal encryption key for the application. Ensure that the application key is the same\nacross all systems in the configuration, and that the key is secret and secured.\n2.Permit the started tasks for Zowe and the Testing Tools Server to generate and evaluate PassTickets, respectively.\nSubmit the following commands:\nTSS PERMIT(sdtask) PTKTDATA(IRRPTAUTH.applid.userid) ACCESS(READ)\nTSS PERMIT(zowetask) PTKTDATA(IRRPTAUTH.applid.userid) ACCESS(UPDATE)\nTSS REFRESH\nsdtask\nSpecifies the started task ID for your Testing Tools Server instance.\napplid\nSpecifies the application ID used for PassTicket validation to authenticate connections to the server.\nDefault:  SDAPPL\nuserid\nSpecifies the user ID for which you want to grant server access. This value can be wildcarded. To grant access to\nall users, specify * .\nzowetask\nSpecifies your Zowe started task ID.\nDefault:  IZUSVR\nYou have configured Single Sign-On for the Symdump Batch REST API on the API Mediation Layer.\nUse IBM RACF to configure PassTickets.\nFollow these steps:\n1.If the PTKTDATA class is not activated, activate it.\nSubmit the following commands:\nSETROPTS CLASSACT(PTKTDATA)\nSETROPTS RACLIST(PTKTDATA)\n2.Define profiles for the application in the PTKTDATA class and specify the session keys.\nSubmit the following commands:\nRDEFINE PTKTDATA applid SSIGNON(KEYMASKED(key)) APPLDATA('NO REPLAY PROTECTION') UACC(NONE)\nSETROPTS RACLIST(PTKTDATA) REFRESH", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d85fdd0503bb-1", "text": "SETROPTS RACLIST(PTKTDATA) REFRESH\napplid\nSpecifies the application ID used for PassTicket validation to authenticate connections to the server.\nDefault:  SDAPPL\nkey\nSpecifies a 16-digit hexadecimal encryption key for the application. Ensure that the application key is the same\nacross all systems in the configuration and that the key is kept secret and secured.\n3.Permit the started tasks for Zowe and the Testing Tools Server to generate and evaluate PassTickets, respectively.\nSubmit the following commands:\nRDEF PTKTDATA IRRPTAUTH.applid.* UACC(NONE)\nPERMIT IRRPTAUTH.applid.userid CLASS(PTKTDATA) ACCESS(READ) ID(sdtask)\nPERMIT IRRPTAUTH.applid.userid CLASS(PTKTDATA) ACCESS(UPDATE) ID(zowetask)\nSETROPTS RACLIST(PTKTDATA) REFRESH\napplid\nSpecifies the application ID used for PassTicket validation to authenticate connections to the server.\nDefault:  SDAPPL\n 310", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e9ab4499edad-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nuserid\nSpecifies the user ID for which you want to grant server access. This value can be wildcarded. To grant access to\nall users, specify * .\nsdtask\nSpecifies the started task ID for your Testing Tools Server instance.\nzowetask\nSpecifies your Zowe started task ID.\nDefault:  IZUSVR\nYou have configured Single Sign-On for the SymDump Batch REST API on the API Mediation Layer.\n 311", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "243a8b6d0e45-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nGetting Started\nGet started with an overview of the features and basic use of the product.\nThis section contains information that helps you get started using the InterTest products. The Assembler, COBOL, and\nPL/I primers walk you through the basic and advanced features of InterTest for CICS. To learn more about how to use the\nbatch tools, use the basic and advanced demo sessions for InterTest Batch as described here.\nThis section also contains quick reference cards for the InterTest products that you can view, download, or print.\nInterTest for CICS Primers\nLearn how to use the basic and advanced InterTest for CICS features.\nThe best way to learn about InterTest for CICS is to use the COBOL, PL/I, and Assembler primers. Use the demo\nsessions for step-by-step instructions on how to use these features. For complete information on the product features and\nfunctionality, see Using CICS Tools.\nAssembler Primer\nLearn the basic product test and debug programs features, and advanced features of InterTest for CICS.\nThis section provides information that is designed to train new users in the basic product features that are used to test and\ndebug programs. This article also introduces some of the advanced features of InterTest for CICS.\nAll users should take the demo sessions in this article and should become familiar with the features explained here. For\ncomplete information about these and other features, see  CICS Debugging. The best way to begin learning about your\nproduct is to read the Assembler Basic Demo Session first.\nGetting Help\nThe Help facility is online documentation of product features. The Help facility makes it easy to learn and to use the\nproduct. Help is available from all product screens.\nTo view an online summary of new features for this release, use ITST Option 8 What's New.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "243a8b6d0e45-1", "text": "Assembler Basic Demo Session\nThis article takes you step by step through the basic demo session.\nThe best way to learn about this application is to Perform the demo at a terminal.\nThe basic demo session shows many of the testing and debugging tasks that you will use on your own programs. For\nmore information on these topics, see CICS Debugging.\nWe assume that the product is installed on your system. If not, contact your system programmer.\nDemo Session Objectives\nThe demo session teaches you how to:\n 312", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "64221a4de882-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Select a source listing for a program from the ITST menus\n\u2022Inform the application that you want to test a program (set monitoring)\n\u2022Respond to the information provided when a program error is detected\n\u2022Display the value of a program variable\n\u2022Dynamically change the value of a program variable\n\u2022Halt program execution at any point (set breakpoints)\n\u2022Resume program execution\nSelect the Source Program from the ITST Menus\nTo begin your session, select the source listing of the ASMDEMO demonstration program from the ITST Primary Option\nMenu.\n1.Sign on to CICS. Type ITST  on a clear screen.\n2.Press Enter.\nThe Primary Option Menu appears.\n      CA InterTest for CICS PRIMARY OPTION MENU      \nOPTION  ===>                                                                                                  \n                                                 \n     1  Source             - Display/select program source files/listings\n     2  Monitoring         - Display/modify CA InterTest monitoring/activity\n     3  Main storage       - Display/modify CICS storage areas              \n     4  Auxiliary storage  - Display/access databases/files/queues           \n     5  Dump analysis      - Invoke CA SymDump CICS dump/trace capture facility\n     6  Product help       - Invoke CA InterTest product help facility    \n     7  Status/Maintenance - Product status and maintenance functions          \n     8  What's new?        - Display information about CA InterTest for CICS \n     X  Exit               - Terminate menu processing                                                        \n                                                           \nPF1 Help       2            3 End        4 Return     5            6          \nPF7            8            9           10           11           12\nNotice that the PF keys have conventional assignments for ISPF-like navigation:\n\u2022PF1 Help accesses online help", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "64221a4de882-1", "text": "\u2022PF1 Help accesses online help\n\u2022PF3 End displays the previous panel\n\u2022PF4 Return returns to the top-level menu\nNow we can look at the source of the program we are debugging.\n1.Type 1 in the Option field.\n2.Press Enter.\nThe Source Menu displays.\n-------------------  CA InterTest for CICS SOURCE MENU  ------------------\nOPTION  ===> 1                                                                                            \n    \nSelect a member list type, specifying optional criteria below.                                            \n                                               \n1  Source listings    - Display/select program source listings                \n2  Symbolic files     - Display/select program source SYMBOLIC files                                      \n                                                  \nType specific or generic program/file name(s):                                   \n 313", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "55b3e932452a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n(Valid mask characters are  *  and/or  +)                                                                 \n                                              \nasm*____ ________ ________ ________ ________ ________ ________                                            \n                                                                               \n3.Type 1 in the Option field to search for program listings.\n4.Tab to the first entry field for program/file names, and type the full or partial name of the program to be monitored. Try\nusing a mask entry such as a*, as*, or asm* . The asterisk is a generic or wildcard character indicating that anything\nfrom this point on in a file name satisfies the search criteria.\n5.Press Enter.\nThe Source Listing Selection screen appears. This screen lists all program Source Listings that meet your search\ncriteria on the previous menu. In our example, the list shows all programs beginning with the letters asm, in all\nSymbolic files. Your list might have fewer or more entries.\n------------  CA InterTest for CICS SOURCE LISTING SELECTION  ------------\nCOMMAND ===>                                                                                              \n                                                   \nType S to select a source listing.                                                                        \n                                               \nName     File         Created       Size Attributes                         \n_ ASMDEMO  PROTSYM  08/16/2013 15:29    74 HLASM 3.0, no purge\n                  *** End of data ***                                                                     \n                                                                  \nPF1 Help       2 Refresh    3 End        4 Return     5            6          \nPF7 Backward   8 Forward    9           10           11           12\n6.Locate the demo program, ASMDEMO, in the Selection List. You might need to scroll the file list using PF7 and PF8.\nNOTE\nIf the file list does not contain the ASMDEMO demo program indicated previously, it could be because the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "55b3e932452a-1", "text": "person who did the installation changed the name of the sample programs. Check with that person to find out\nthe correct names.\n7.Type S in the field to the left of the program ASMDEMO. Press Enter.\nThe PROTSYM File Source Listing Display appears, it shows the compiled listing of ASMDEMO.\nCA InterTest for CICS  - PROTSYM FILE SOURCE LISTING DISPLAY\nCOMMAND ===>                                                                   \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01                            \n            Search=                                \n---------+---------------------------------------------------------------------\n     Active Usings: None                                                                                  \n                                                         \nLOC  OBJECT CODE    ADDR1 ADDR2  STMT        SOURCE STATEMENT\n                    00000        1 R0          EQU   0\n                    00001        2 R1          EQU   1\n                    00002        3 R2          EQU   2\n                    00003        4 R3          EQU   3\n                    00004        5 R4          EQU   4\n                                            \n                    00005        6 R5          EQU   5\n                    00006        7 R6          EQU   6\n 314", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eb0d1d016163-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                    00007        8 R7          EQU   7\n                    00008        9 R8          EQU   8\n                    00009        10 R9         EQU   9\n                    0000A        11 R10        EQU   10\n                    0000B        12 R11        EQU   11                                                   \n            \n                    0000C        13 R12        EQU   12                                                   \n            \n                    0000D        14 R13        EQU   13                                                   \n            \n                    0000E        15 R14        EQU   14\n                                                               \n                    0000F        16 R15        EQU   15                   \n\u2013The top section of the display identifies the program and provides fields for entering commands, options, statement\nnumbers, and search criteria. Depending on your defaults, it may also display PF key assignments and available\noptions. For clarity, these assignments and options are omitted from the Source Listing displays in this section.\n\u2013The bottom section contains the source listing for ASMDEMO.\nNOTE\nThe statement numbers on your screen might not match the numbers shown in the examples. This fact does\nnot hinder your ability to perform the test session.\nView the Source Listing Profile\nDepending on the configuration settings, the PF key assignments for the Source Listing display might not be shown at the\ntop of the screen. If they are not, type PROFILE on the Command line and press Enter (or, press PF4 Profile) to view the\nvarious options and PF key functions available from the Source Listing display.\nThe Source Listing Profile for your current session is displayed. This profile lists the PF keys, options, and current\nenvironment settings that relate to the Source Listing display.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eb0d1d016163-1", "text": "environment settings that relate to the Source Listing display.\n        CA InterTest for CICS   - PROTSYM FILE SOURCE LISTING PROFILE   \nCOMMAND ===>                                                                   \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01                                \n          Search=                                \nOPTS 1 1st CSECT 2           3            4            5 Macro Cat  6 Xref\n     7 Literals  8 Err msgs  9 Srch fwd  10 Srch bwd  11           12 Bkpt opts\nPFKS 1 Help      2           3 End        4 Auto prms  5 Monitor    6 Menu\n     7 Backward  8 Forward   9 Next Wnd  10           11           12 Status\n   ---------+---------------------------------------------------------------------\nDisplay window   = N         N (None), T (Titles), R (Registers),\n                             K (Keep), P (Program)                            \nPF7/8 amount     = PAGE      PAGE, HALF, STOP, or a number from 1 to 9999      \nStepping amount  = 001       The number of INSTR   to execute                  \nAuto-stepping    = OFF       ON to activate; press PF4 to change values        \nSource List BKPT = ON        OFF to use the detailed breakpoint display        \nFrom terminal ID = G001      Terminal ID where the program will execute        \nBKPT terminal ID = G001      Terminal ID to receive the breakpoint displays    \nUser ID          = .ANY      User ID who will execute this program             \nAutoKeep Display = OFF       ON to activate                                    \nCode Counting    = OFF       ON to activate Code Coverage\n 315", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "79030f7d6683-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nTo display the four lines that are labeled OPTS and PFKS at the top of your screen throughout your test session,\nchange the Display window field from N to T. Enter R in the Display window field if you want to have the contents\nof the registers shown at the top of the breakpoint display, as shown in the following screen:\nCA InterTest for CICS  - PROTSYM FILE SOURCE LISTING BREAKPOINT \nCOMMAND ===>                                                                   \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01                                \n                                          Search=                                \n------------------------------------------------------------------------------- \nR0-R7  0DB053E6 00180C10 0DB052F8 0DB062F8 0DB072F8 000001D5 00000232 0DB082F8 \nR8-R15 00000000 00000000 00055380 001800D0 008BD000 00180BA8 8DB053C4 00000000 \nCond. Code = 0   Amode = 31                                                   \n---------+---------------------------------------------------------------------\nSet Monitoring\nThe next step is to instruct the application to monitor ASMDEMO. As part of monitoring a CICS command-level program\nsuch as ASMDEMO, the application automatically prevents all CICS abends during execution. How this functionality is\nshown later when the application prevents ASMDEMO from abending because of an ASRA.\nIf you are viewing a program source listing, you can tell the application to monitor the program with the following actions:\n\u2022Type MONITOR on the Command line and press Enter.\n\u2022Press PF5 (notice PF5 is listed as Monitor in the earlier illustration).\n\u2022Press PF5 or use the MONITOR command while in the Source Listing Display or the Source Listing Profile screen.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "79030f7d6683-1", "text": "The screen momentarily flashes as the request is processed. The Source Listing Display screen then redisplays.\nView Monitoring Status\nTo verify that the demo program is being monitored:\n1.Type STATUS on the command line.\nCA InterTest for CICS  - PROTSYM FILE SOURCE LISTING DISPLAY \nCOMMAND ===> status                                                            \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01                            \n            Search=                                \n---------+---------------------------------------------------------------------     \nActive Usings: None                                                                                       \n                                                    \nLOC  OBJECT CODE    ADDR1 ADDR2  STMT        SOURCE STATEMENT\n                    00000           1 R0       EQU   0                                  \n                    00001           2 R1       EQU   1                 \n2.Press Enter.\nNOTE\nPF12 also displays the Monitoring Status display.\nThe Monitoring Status screen  appears.\n----------------  CA InterTest for CICS  MONITORING STATUS  --------------\nCOMMAND ===>                                                                                              \n                                                     \nType + to expand or - collapse option levels displayed below,                \n       or R to remove option(s).                                                                          \n                                                   \n 316", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f85cc87af5e5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n          Option     Description                Attributes                         \n      _ - ASMDEMO    Program monitor entry      Assembler                        \n      _ - |-.\n     ANY     User monitoring options    Active                          \n                    |        Symbolic listing file      PROTSYM                      \n      _     |-\n     SLB    Source listing breakpoints G001                                    \n                       *** End of data ***                                                                \n                                                                                                          \n        PF1 Help       2 Refresh    3 End        4 Return     5 Collapse   6 Expand    \nPF7 Backward   8 Forward    9           10           11           12\nThe monitoring status display gives you an up-to-date summary of how the application is monitoring your program, in\nan expandable/collapsible tree format. You can scroll the list, or you can use the indicated PF keys on the bottom of\nthe display to collapse and expand the list. The ASMDEMO entiries indicate the following information:\n\u2013The top entry tells you the application is monitoring the Assembler program ASMDEMO.\n\u2013The second entry (.ANY) indicates the application monitors ASMDEMO when executed by a user. If your status\ndisplay shows your CICS User ID instead of .ANY, this indicates monitoring and options taking effect when your ID\nexecutes the program, but not when someoneone else executes the program. When the user monitoring option is\nset to a specific CICS User ID, the application creates a personal debugging session for that user.\nNOTE\nFor details on using and switching the User ID Monitoring Option, see Monitoring Menu Options.\n\u2013The last entry shows that the SLB option for Source listing breakpoints is on. SLB means the application uses the\nSource Listing version of the breakpoint display throughout your test session, instead of the Detailed version. The\nSLB version is used throughout this article, and is recommended for all users.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f85cc87af5e5-1", "text": "SLB version is used throughout this article, and is recommended for all users.\nNOTE\nIf monitoring is not correctly, the Status display does not appear and the Program Monitoring menu\ndisplays a message that no entries (for ASMDEMO) were found. In this case, press PF3 to return to the\nSource Listing display, and then enter the MONITOR command or press PF5 to set monitoring. Use PF12\nto check the status again before you continue.\nOnce you verify that the correct demo program is being monitored, press PF3 to go back to the Source Listing.\nNow exit to CICS using the fastpath exit, as follows:\n1.Type =X in the Source Listing Command field and press Enter. This returns you to ITST menu processing.\n2.From the Source Selection Menu, type =X in the Command field and press Enter to exit to CICS.\nStart Program Execution\nNow you are ready to begin testing ASMDEMO.\nBefore performing the next action, clear the current screen.\n1.Type DEMA , the CICS transaction: identifier of the demo program.\n2.Press Enter.\nThe following welcome screen appears:\n******************************************************************************\n******************************************************************************\n*****                                                                    *****\n*****                             Welcome to the                         ***** \n*****                       CA InterTest Demo Session                    ***** \n*****                                                                    ***** \n*****                                                                    ***** \n 317", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "02ef9cdd9e49-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n*****              Before proceeding, please have on hand the            ***** \n*****              guide which accompanies the Demo Session.             ***** \n*****                                                                    ***** \n*****                                                                    ***** \n*****     Please make sure that the program ASMDEMO is monitored by      ***** \n*****     CA InterTest. This program will abend if it is not monitored.  ***** \n*****                                                                    ***** \n*****     To turn the monitor on, press CLEAR and follow the steps       ***** \n*****     outlined in the documentation.                                 ***** \n*****                                                                    ***** \n*****     If the monitor is already on, press ENTER to begin the         ***** \n*****     Basic Demo Session or PF2 to go to the Options Menu.           ***** \n*****                                                                    ***** \n****************************************************************************** \n******************************************************************************\n3.Press Enter.\nASMDEMO resumes execution.\nDetect and Prevent an Abend\nThe next screen that you see is not displayed by ASMDEMO. This screen is a diagnostic screen, called a breakpoint\ndisplay, that is produced by the application.\nCA InterTest for CICS  - PROTSYM FILE SOURCE LISTING BREAKPOINT \nCOMMAND ===>                                                                   \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01                                \n        Search=                                \n---------+---------------------------------------------------------------------\n     LOC  OBJECT CODE    ADDR1 ADDR2  STMT        SOURCE STATEMENT              \n_ 00016A 4050 D1B0            001B0  1355          STH   R5,MSGLEN             \nA 00016E FA20 D189 4AC0 00189 02AC0   ==>          AP    TASKNUM,=P'1'\n             ==>                                                              \n             ==> ASRA ABEND (0C7) detected and prevented. Caused by invalid decimal", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "02ef9cdd9e49-1", "text": "==> ASRA ABEND (0C7) detected and prevented. Caused by invalid decimal\n             ==> arithmetic data format.                                     \n             ==>                                                              \n             ==>      Press PF1 for a detailed description.                    \n             ==>                                                                       \n _ 000174 F920 D189 4AC1 00189 02AC1  1357          CP    TASKNUM,=P'2'         \n_ 00017A 4720 2300            00300  1358          BH    ENDMSG                \n_ 00017E F920 D189 4AC0 00189 02AC0  1359          CP    TASKNUM,=P'1'         \n_ 000184 4780 2256            00256  1360          BE    SENDSCR4              \n_ 000188 47F0 2300            00300  1361          B     ENDMSG                \n_ 00018C                             1363 RETURN   DS    0H                                                   \n                                        1364 *        EXEC CICS SEND FROM(OUTMSG                              \n                                           1365          DFHECALL =X'04043000080000\n  00018C 4110 D068            00068                      ),(FB_2,OUTLEN)                                      \n                                       1381 *        EXEC CICS SEND FROM(SCREE\nLook at the highlighted area. The application has highlighted an Add Packed (AP) instruction and displayed a message\nbelow it.\nExecution of that AP instruction triggered an ASRA. The application prevented the abend and then displayed the\ndiagnostic screen that you are currently viewing.\n 318", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2754fb85c4e7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWhen the application stops program execution, we say that the program is halted at a breakpoint . The appliction stops\nprogram execution automatically, as shown in the previous screen, or halts a program at a breakpoint set by you, the\nprogrammer. The A to the far left of the AP instruction indicates that the current halt in program execution is an Automatic\nbreakpoint; not a breakpoint set by you.\nNow look at the highlighted message. It explains that the ASRA was caused by improperly formatted data. Which data?\nSince the instruction that triggered the ASRA was adding a packed 1 (=P'1') to the data in TASKNUM, it is likely that\nTASKNUM contains improperly formatted data.\nThe application prevented ASMDEMO from abending and identified the problem.\nDetermine the Cause of the Error\nWe confirm that the value stored in TASKNUM is not in a valid arithmetic format by displaying its current value. That is, the\nvalue prior to the execution of the AP instruction that triggered the ASRA.\n1.Overtype the A with K (keep).\n2.Place the cursor under any character in TASKNUM (see the following screen).\n3.Press Enter.\nCA InterTest for CICS  - PROTSYM FILE SOURCE LISTING BREAKPOINT \nCOMMAND ===>                                                                   \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01                            \n                                             Search=                                \n---------+---------------------------------------------------------------------\n     LOC  OBJECT CODE    ADDR1 ADDR2  STMT        SOURCE STATEMENT\n               \n  _ 00016A 4050 D1B0            001B0  1355          STH   R5,MSGLEN", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2754fb85c4e7-1", "text": "k 00016E FA20 D189 4AC0 00189 02AC0   ==>          AP    TASKNUM,=P'1' <-- place cursor on any of the\n TASKNUM characters\n            ==>                                                                  \n            ==> ASRA ABEND (0C7) detected and prevented. Caused by invalid decimal\n            ==> arithmetic data format.                                        \n            ==>                                                               \n            ==>      Press PF1 for a detailed description.                      \n            ==>                                                                         \n  _ 000174 F920 D189 4AC1 00189 02AC1  1357          CP    TASKNUM,=P'2'       \n  _ 00017A 4720 2300            00300  1358          BH    ENDMSG            \n  _ 00017E F920 D189 4AC0 00189 02AC0  1359          CP    TASKNUM,=P'1'       \n  _ 000184 4780 2256            00256  1360          BE    SENDSCR4            \n  _ 000188 47F0 2300            00300  1361          B     ENDMSG               \n  _ 00018C                             1363 RETURN   DS    0H                                             \n                                          1364 *        EXEC CICS SEND FROM(OUTMSG                        \n                                             1365          DFHECALL =X'04043000080000     \n    00018C 4110 D068            00068                      ),(FB_2,OUTLEN)                                \n                                           1381 *        EXEC CICS SEND FROM(SCREE\nThe application displays the value of TASKNUM in a specially formatted Keep window, as shown in the following\nscreen.\n\u2013On the left is the name of the variable, preceded by the base register", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2754fb85c4e7-2", "text": "screen.\n\u2013On the left is the name of the variable, preceded by the base register\n\u2013On the right is its hexadecimal value and corresponding character representation\nThe application determines the base register from the generated object code of the AP instruction. In this case, it is\nregister 13 (D).\n  CA InterTest for CICS   - PROTSYM FILE  ABEND DETECTED BREAKPOINT       \n 319", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7d6a0bc932e2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCOMMAND ===>                                                                    \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01                                \n                                         Search=                                 \n-------------------------------------------------------------------------------\n  _____ R13.TASKNUM                     | ?00000.                                \n---------++--------------------------------------------------------------------\n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement               \n_ 000192 4050 D1B0            001B0  1456          STH   R5,MSGLEN              \nA 000196 FA20 D189 4AE8 00189 02AE8   ==>          AP    TASKNUM,=P'1'          \n_ 00019C F920 D189 4AE9 00189 02AE9  1458          CP    TASKNUM,=P'2'          \n_ 0001A2 4720 2328            00328  1459          BH    ENDMSG                 \n_ 0001A6 F920 D189 4AE8 00189 02AE8  1460          CP    TASKNUM,=P'1'          \n_ 0001AC 4780 227E            0027E  1461          BE    SENDSCR4               \n_ 0001B0 47F0 2328            00328  1462          B     ENDMSG                 \n_ 0001B4                             1464 RETURN   DS    0H                                                   \n                                        1465 *        EXEC CICS SEND FROM(OUTMSG                              \n                                           1466          DFHECALL =X'04043000080000\n  0001B4 4110 D068            00068                      ),(FB_2,OUTLEN)                                      \n                                       1482 *        EXEC CICS SEND FROM(SCREEN", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7d6a0bc932e2-1", "text": "1482 *        EXEC CICS SEND FROM(SCREEN                               \n                                          1483          DFHECALL =X'04043000080000\n  0001DA 4110 D068            00068                      2),(FB_2,MSGLEN)                                     \n                                        1499 *        EXEC CICS RETURN                                        \n                                           1500 *              TRANSID(EIBTRNID)    \nAny number of variables can be saved in a Keep window. However, only six variables display at a time. PF keys 19 and\n20 are provided to scroll forward and backward through the Keep window when it contains more than six variables. This\nfeature lets you see how the variable values change as your program executes. The Keep window remains until you\nremove all variables from it.\nTo display the value of a variable without keeping it in a Keep window, type D (display) rather than K (keep). This displays\nthe value of the variable and all variables below it in the same Assembler DSECT.\nNow look at the contents of TASKNUM. The contents do not contain a valid packed decimal value, as is indicated by a \"?\"\nin the left-most position of the field. Assembler does not allow you to add a value to a field without initializing it.\nChange the Value in TASKNUM Dynamically\nNow that we have identified and confirmed the cause of the problem, we will fix it.\n1.Tab the cursor to the place where the question mark appears.\n2.Type 0 over the question mark and erase to end of field (EOF).\n3.Press Enter.\n  CA InterTest for CICS   - PROTSYM FILE  ABEND DETECTED BREAKPOINT       \nCOMMAND ===>                                                                    \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01                            \n                                          Search=                                 \n-------------------------------------------------------------------------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7d6a0bc932e2-2", "text": "Search=                                 \n-------------------------------------------------------------------------------\n  _____ R13.TASKNUM                     | 0                                      \n---------++--------------------------------------------------------------------\n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement               \n_ 000192 4050 D1B0            001B0  1456          STH   R5,MSGLEN              \nA 000196 FA20 D189 4AE8 00189 02AE8   ==>          AP    TASKNUM,=P'1'          \n_ 00019C F920 D189 4AE9 00189 02AE9  1458          CP    TASKNUM,=P'2'          \n_ 0001A2 4720 2328            00328  1459          BH    ENDMSG                 \n_ 0001A6 F920 D189 4AE8 00189 02AE8  1460          CP    TASKNUM,=P'1'          \n 320", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d3138e49eda4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n_ 0001AC 4780 227E            0027E  1461          BE    SENDSCR4               \n_ 0001B0 47F0 2328            00328  1462          B     ENDMSG                 \n_ 0001B4                             1464 RETURN   DS    0H                                               \n                                        1465 *        EXEC CICS SEND FROM(OUTMSG                          \n                                           1466          DFHECALL =X'04043000080000     \n  0001B4 4110 D068            00068                      ),(FB_2,OUTLEN)                                  \n                                         1482 *        EXEC CICS SEND FROM(SCREEN                         \n                                            1483          DFHECALL =X'04043000080000     \n  0001DA 4110 D068            00068                      2),(FB_2,MSGLEN)                                 \n                                        1499 *        EXEC CICS RETURN                                    \n                                           1500 *              TRANSID(EIBTRNID)    \nThe application redisplays the screen. TASKNUM now contains a packed decimal zero.\nStructured Storage Display\nNow we request a structured storage display of TASKNUM and all the fields below it in the same DSECT.\n1.Type D to the left of TASKNUM in the Keep window, and press Enter.\nCA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \nCOMMAND ===>                                                                    \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01                            \n                                           Search=                                 \n-------------------------------------------------------------------------------\n d____ R13.TASKNUM                     |  00000.                                \n---------++--------------------------------------------------------------------\n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d3138e49eda4-1", "text": "Loc  Object Code    Addr1 Addr2  Stmt        Source Statement               \n_ 000192 4050 D1B0            001B0  1456          STH   R5,MSGLEN              \nA 000196 FA20 D189 4AE8 00189 02AE8   ==>          AP    TASKNUM,=P'1'          \n_ 00019C F920 D189 4AE9 00189 02AE9  1458          CP    TASKNUM,=P'2'          \n_ 0001A2 4720 2328            00328  1459          BH    ENDMSG                 \n_ 0001A6 F920 D189 4AE8 00189 02AE8  1460          CP    TASKNUM,=P'1'          \n_ 0001AC 4780 227E            0027E  1461          BE    SENDSCR4               \n_ 0001B0 47F0 2328            00328  1462          B     ENDMSG                 \n_ 0001B4                             1464 RETURN   DS    0H                                               \n                                        1465 *        EXEC CICS SEND FROM(OUTMSG                          \n                                           1466          DFHECALL =X'04043000080000     \n  0001B4 4110 D068            00068                      ),(FB_2,OUTLEN)                                  \n                                         1482 *        EXEC CICS SEND FROM(SCREEN                         \n                                            1483          DFHECALL =X'04043000080000     \n  0001DA 4110 D068            00068                      2),(FB_2,MSGLEN)                                 \n                                        1499 *        EXEC CICS RETURN", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d3138e49eda4-2", "text": "1499 *        EXEC CICS RETURN                                    \n                                           1500 *              TRANSID(EIBTRNID)    \nThe following screen appears. On the left are the Assembler labels; on the right are the hexadecimal values and\ncorresponding character representations of each field.\nCA InterTest for CICS  - MAIN STORAGE UTILITY - Termid = U026                                             \n                                          \nStarting at Address =  105018  Disp   Structure Display Format                  \nTASKNUM                         189 |  00000.                    |\n              \nTSTEXT                          18C | ............               |             \n                                    | ............               |\n 321", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "84e685a5afd1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                       \n                                    | ........                   |              \nMSGNAME                         1AC |  0000000000.               |              \nMSGLEN                          1B0 | +00469.                    |              \nRECRBA                          1B2 | ......                     |              \nRECPONT                         1B8 |  0000000000.               |                                        \n                                    1BC |  00000.                    |              \nDMAP04AS                        1BC |                            |                                        \n                                    1BC | ............               |              \nRECOUT1L                        1C8 | ..                         |              \nRECOUT1F                        1CA | .                          |              \nRECOUT1A                        1CA | .                          |              \nRECOUT1I                        1CB | .                          |              \nRECOUT1O                        1CB | ............               |               \n------------------------------------------------------------------------------  \nPF1 Help       2            3 End        4 Return     5            6 Dump       \nPF7 Backward   8 Forward    9 Caps Off  10           11 Redisplay 12 Structure  \nCORE='R13.TASKNUM'                                                              \nCAIN4713 R13 not found - have assumed its register value\nThe structured format of the main storage display is much easier to use than a traditional dump-formatted display.\nSince the application displays only those bytes belonging to a field, you do not have to know or remember the lengths\nof the fields to determine their contents.\nNOTE\nYou can change the contents of any field by overtyping the desired bytes on the main storage display. By\ndefault the application data appropriate translated values for each field. If you prefer you may toggle to hex/\nchar display mode by hitting the PF12 key, data alteration is allowed in either mode.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "84e685a5afd1-1", "text": "char display mode by hitting the PF12 key, data alteration is allowed in either mode.\nNow we return to the program listing so we can continue to test ASMDEMO.\n2.Press Clear or PF3.\nThe breakpoint screen redisplays.\nControl Program Execution\nNow that the value in TASKNUM has been properly initialized, the next step might be to continue testing by resuming\nprogram execution. However, this stage is a good opportunity to learn about an important feature -- the ability to control\nprogram execution by setting breakpoints.\nStop Your Program by Setting Breakpoints\nOne of the problems with traditional testing methods is that you have little or no control over program processing. You\nsimply initiate the task, and the program either runs to completion or abends.\nWith the application, you can control program execution in a few ways. For example, you can set stops, called\nbreakpoints , anywhere in your program. Four types of breakpoints you can set are unconditional, conditional, variable-\nchange, and request breakpoints.\n 322", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0b178f58fe68-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022When you set an unconditional  breakpoint at an instruction, the program stops before or just after the instruction is\nexecuted. (Depending on the type of unconditional breakpoint that you set.)\n\u2022When you set a conditional  breakpoint at an instruction, the program stops only if a condition you specified is met,\nsuch as a counter equaling or exceeding some value. You can also set a conditional breakpoint to stop at any\ninstruction when the condition you specified is met.\n\u2022When you set a variable-change  breakpoint, the program stops at any instruction if the value of the variable you\nspecify has changed. This is a special type of conditional breakpoint.\n\u2022When you set a request  breakpoint, the program stops before all CICS commands and macros and other program\ncalls (such as calls to DL/I or DB2) or just before specific CICS commands (such as all READ or WRITE commands)\nWhat You Can Do When Your Program Is Stopped\nOnce a program is stopped, you can use the testing and debugging facilities to:\n\u2022Examine the source listing\n\u2022Examine and modify main and auxiliary storage to detect and correct errors\n\u2022Set and remove breakpoints\n\u2022Keep variables in a Keep window to observe changes in their values\n\u2022Abend your task with or without a dump\n\u2022Go around a problem by resuming program execution from a location other than the one at which the program is\ncurrently stopped\n\u2022Execute the program in single-step mode ; that is, the program executes just one instruction and then stops\nNow we are going to demonstrate how easy it is to control program execution by setting an unconditional breakpoint.\nSet Unconditional Breakpoints\nYou can set unconditional breakpoints directly on the Source Listing screen just as easily as you displayed and modified", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0b178f58fe68-1", "text": "You can set unconditional breakpoints directly on the Source Listing screen just as easily as you displayed and modified\nTASKNUM. Enter U or ) to the left of each instruction where you want the application to halt program execution. The U\nsets a breakpoint that stops before  the instruction is executed. The ) sets a breakpoint that stops after the instruction is\nexecuted.\nLet us see how to set a \"before\" breakpoint at the following instruction:\nCP TASKNUM,=P'1'\n1.Type U to the left of the instruction CP TASKNUM,=P'1'. Press PF5 RESUME to continue execution from where the\nprogram is currently stopped at the AP instruction.\nCA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \nCOMMAND ===>                                                                    \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01                            \n                                            Search=                                 \n-------------------------------------------------------------------------------\n  _____ R13.TASKNUM                     |  00000.                                \n---------++--------------------------------------------------------------------\n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement               \n_ 000192 4050 D1B0            001B0  1456          STH   R5,MSGLEN              \nA 000196 FA20 D189 4AE8 00189 02AE8   ==>          AP    TASKNUM,=P'1'          \n_ 00019C F920 D189 4AE9 00189 02AE9  1458          CP    TASKNUM,=P'2'          \n_ 0001A2 4720 2328            00328  1459          BH    ENDMSG                u 0001A6 F920 D189 4AE8", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0b178f58fe68-2", "text": "00189 02AE8  1460          CP    TASKNUM,=P'1'          \n_ 0001AC 4780 227E            0027E  1461          BE    SENDSCR4               \n_ 0001B0 47F0 2328            00328  1462          B     ENDMSG                 \n 323", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "18f755450d31-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n_ 0001B4                             1464 RETURN   DS    0H                                               \n                                        1465 *        EXEC CICS SEND FROM(OUTMSG                          \n                                           1466          DFHECALL =X'04043000080000     \n  0001B4 4110 D068            00068                      ),(FB_2,OUTLEN)                                  \n                                         1482 *        EXEC CICS SEND FROM(SCREEN                         \n                                            1483          DFHECALL =X'04043000080000     \n  0001DA 4110 D068            00068                      2),(FB_2,MSGLEN)                                 \n                                        1499 *        EXEC CICS RETURN                                    \n                                           1500 *              TRANSID(EIBTRNID)\nThe application resumes program execution and continues until it reaches the breakpoint you just set. The program is\nhalted before the breakpoint instruction executes and the following screen appears.\nCA InterTest for CICS  - PROTSYM FILE  UNCOND  BEFORE BREAKPOINT         \nCOMMAND ===>                                                                    \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01                            \n                                           Search=                                 \n-------------------------------------------------------------------------------\n  _____ R13.TASKNUM                     | +00001.                                \n---------++--------------------------------------------------------------------\n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement               \n_ 0001A2 4720 2328            00328  1459          BH    ENDMSG                 \nU 0001A6 F920 D189 4AE8 00189 02AE8   ==>          CP    TASKNUM,=P'1'          \n_ 0001AC 4780 227E            0027E  1461          BE    SENDSCR4", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "18f755450d31-1", "text": "_ 0001B0 47F0 2328            00328  1462          B     ENDMSG                 \n_ 0001B4                             1464 RETURN   DS    0H                                               \n                                        1465 *        EXEC CICS SEND FROM(OUTMSG                          \n                                           1466          DFHECALL =X'04043000080000     \n  0001B4 4110 D068            00068                      ),(FB_2,OUTLEN)                                  \n                                         1482 *        EXEC CICS SEND FROM(SCREEN                         \n                                            1483          DFHECALL =X'04043000080000     \n  0001DA 4110 D068            00068                      2),(FB_2,MSGLEN)                                 \n                                        1499 *        EXEC CICS RETURN                                    \n                                           1500 *              TRANSID(EIBTRNID)                          \n                                               1501 *              COMMAREA(TSAREA)                       \n                                                  1502 *              LENGTH(COMLEN)                      \n                                                     1503          DFHECALL =X'0E08E00008000    \nNotice the U to the left of the highlighted instruction. It identifies the breakpoint as an unconditional \"before\"\nbreakpoint. For an \"after\" breakpoint, the application displays a \")\". For an automatic, conditional, variable-change, or\nrequest breakpoint, the application displays an A, C, V , or R, respectively.\nNOTE\nThe value of TASKNUM is now 1 because the AP instruction executed successfully.\nWhen you are stopped at a breakpoint, you can:\n\u2013Scroll or search through your source listing\n\u2013Examine and modify main and auxiliary storage\n\u2013Add a variable to the Keep window using the K line command\n\u2013Set and remove breakpoints using simple line commands such as U, ), and X", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "18f755450d31-2", "text": "\u2013Set and remove breakpoints using simple line commands such as U, ), and X\n\u2013Abend your task (with or without a dump)\n\u2013Go around a problem by resuming program execution from another location (Type G next to the instruction where\nyou want to resume.)\n 324", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fb0f4112db8f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWhen debugging your own programs, you typically perform one or more of these activities. ASMDEMO does not have\nmore errors, so we will complete the demo session.\nRemove the Keep Window and Breakpoints\nAs you continue testing and debugging, you should clean up by removing breakpoints you no longer need. Removing\nuneeded breakpoints prevents the program from stopping when you retest the program. Now remove the unconditional\nbreakpoint that you just set, and remove TASKNUM from the Keep window.\n1.Type X to the left of TASKNUM in the Keep window to remove it from the window.\n2.Overtype U with X to remove the breakpoint.\n3.Press Enter.\nCA InterTest for CICS  - PROTSYM FILE  UNCOND  BEFORE BREAKPOINT        \nCOMMAND ===>                                                                   \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01                            \n                                            Search=                                \n------------------------------------------------------------------------------- x____ R13.TASKNUM          \n           | +00001.                               \n---------++--------------------------------------------------------------------\n     Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n_ 0001A2 4720 2328            00328  1459          BH    ENDMSG               x 0001A6 F920 D189 4AE8\n 00189 02AE8   ==>          CP    TASKNUM,=P'1'         \n_ 0001AC 4780 227E            0027E  1461          BE    SENDSCR4              \n_ 0001B0 47F0 2328            00328  1462          B     ENDMSG                \n_ 0001B4                             1464 RETURN   DS    0H                                               \n                                        1465 *        EXEC CICS SEND FROM(OUTMSG", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fb0f4112db8f-1", "text": "1465 *        EXEC CICS SEND FROM(OUTMSG                          \n                                           1466          DFHECALL =X'04043000080000 \n  0001B4 4110 D068            00068                      ),(FB_2,OUTLEN)                                  \n                                         1482 *        EXEC CICS SEND FROM(SCREEN                         \n                                            1483          DFHECALL =X'04043000080000    \n  0001DA 4110 D068            00068                      2),(FB_2,MSGLEN)                                 \n                                        1499 *        EXEC CICS RETURN                                    \n                                           1500 *              TRANSID(EIBTRNID)                          \n                                               1501 *              COMMAREA(TSAREA)                       \n                                                  1502 *              LENGTH(COMLEN)                      \n                                                     1503          DFHECALL =X'0E08E00008000  \nThe application removes the Keep window and unconditional breakpoint, as shown in the following screen.\nCA InterTest for CICS  - PROTSYM FILE  UNCOND  BEFORE BREAKPOINT         \nCOMMAND ===>                                                                    \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01                            \n                                             Search=                                 \n----------+--------------------------------------------------------------------\n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement               \n_ 0001A2 4720 2328            00328  1459          BH    ENDMSG                 \n_ 0001A6 F920 D189 4AE8 00189 02AE8   ==>          CP    TASKNUM,=P'1'          \n_ 0001AC 4780 227E            0027E  1461          BE    SENDSCR4", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fb0f4112db8f-2", "text": "_ 0001B0 47F0 2328            00328  1462          B     ENDMSG                 \n_ 0001B4                             1464 RETURN   DS    0H                                               \n                                        1465 *        EXEC CICS SEND FROM(OUTMSG                          \n                                           1466          DFHECALL =X'04043000080000    \n 325", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ac181ecc1978-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  0001B4 4110 D068            00068                      ),(FB_2,OUTLEN)                                  \n                                         1482 *        EXEC CICS SEND FROM(SCREEN                         \n                                            1483          DFHECALL =X'04043000080000    \n  0001DA 4110 D068            00068                      2),(FB_2,MSGLEN)                                 \n                                        1499 *        EXEC CICS RETURN                                    \n                                           1500 *              TRANSID(EIBTRNID)                          \n                                               1501 *              COMMAREA(TSAREA)                       \n                                                  1502 *              LENGTH(COMLEN)                      \n                                                     1503          DFHECALL =X'0E08E000080000    \n  000200 4110 D068            00068                      EA),(FB_2,COMLEN)      \n_ 000226                             1518 SENDSCR3 DS    0H\nNOTE\nIf there were other variables in the Keep window, they would remain in the window after you removed\nTASKNUM.\nRemove Breakpoints from the Status Display\nYou can also remove a breakpoint from the Status display. Use the following steps to set another \"before\" breakpoint,\naccess the Monitoring Status display, and quickly remove the breakpoint from the Status display.\n1.Type U in front of the RETURN statement and press Enter.\nThe application sets the unconditional breakpoint at the RETURN.\n2.Type STATUS on the command line, and press Enter.\nCA InterTest for CICS   - PROTSYM FILE  UNCOND  BEFORE BREAKPOINT         \nCOMMAND ===>                                                                    \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01                            \n                                           Search=                                 \n----------+--------------------------------------------------------------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ac181ecc1978-1", "text": "Search=                                 \n----------+--------------------------------------------------------------------\n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement               \n_ 0001A2 4720 2328            00328  1459          BH    ENDMSG                 \n_ 0001A6 F920 D189 4AE8 00189 02AE8   ==>          CP    TASKNUM,=P'1'          \n_ 0001AC 4780 227E            0027E  1461          BE    SENDSCR4               \n_ 0001B0 47F0 2328            00328  1462          B     ENDMSG                u 0001B4                   \n          1464 RETURN   DS    0H                                                                          \n             1465 *        EXEC CICS SEND FROM(OUTMSG                                                     \n                1466          DFHECALL =X'04043000080000    \n  0001B4 4110 D068            00068                      ),(FB_2,OUTLEN)                                  \n                                         1482 *        EXEC CICS SEND FROM(SCREEN                         \n                                            1483          DFHECALL =X'04043000080000    \n  0001DA 4110 D068            00068                      2),(FB_2,MSGLEN)                                 \n                                        1499 *        EXEC CICS RETURN                                    \n                                           1500 *              TRANSID(EIBTRNID)                          \n                                               1501 *              COMMAREA(TSAREA)                       \n                                                  1502 *              LENGTH(COMLEN)                      \n                                                     1503          DFHECALL =X'0E08E000080000   \n  000200 4110 D068            00068                      EA),(FB_2,COMLEN)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ac181ecc1978-2", "text": "_ 000226                             1518 SENDSCR3 DS    0H\nThe Monitoring Status screen displays. The Monitoring Status display lists all breakpoints and monitoring options\nfor your program. You can easily remove one or all breakpoints without locating them in your listing, or remembering\nwhere you set them.\n----------------  CA InterTest for CICS  MONITORING STATUS  -------------- \n 326", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a890e2070e18-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCOMMAND ===>                                                                                              \n                                                   \n   Type + to expand or - collapse option levels displayed below,     \n                    or R to remove option(s).                                                             \n                                                              \n     Option     Description                Attributes                     \n _ - ASMDEMO    Program monitor entry      Assembler                          \n     |          Waiting at breakpoint      Task 00035, UBP since 10:00 a.m. \n _ - |-.ANY     User monitoring options    Active                              \n     |        Symbolic listing file      PROTSYM                            r -  |-UBP    Unconditional\n breakpoint   'RETURN'                                \n     |        Option ID                  D7B97FBE                               \n     |        From, to terminals         G001, G001                          \n_    |-SLB    Source listing breakpoints G001                             \n                  *** End of data ***                                                                     \n                                                                                                          \n                                                                                                      \nPF1 Help       2 Refresh    3 End        4 Return     5 Collapse   6 Expand   \nPF7 Backward   8 Forward    9           10           11           12         \n3.Type an r to the left of the unconditional breakpoint (UBP).\n4.Press Enter.\nAn asterisk appears next to the UBP breakpoint option, and the Attributes column reads ***REMOVED***.\n5.Press PF2 to refresh the screen.\nThe unconditional breakpoint entry (UBP) disappears from the status display.\n6.Press PF3 to return to the Source Listing Breakpoint screen.\nResume Program Execution\nFollow these steps:\n1.Press PF5 to continue program execution.\nThe application resumes program execution. ASMDEMO displays the following screen. This screen reminds you that\nwe have touched on just a few of the application's powerful, easy-to-use, testing and debugging facilities.\n**********************************************************************\n****                                                              ****", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a890e2070e18-1", "text": "**********************************************************************\n****                                                              ****    \n****                 CA InterTest Demo Session                    ****    \n****                                                              ****    \n**********************************************************************                                    \n                                                                                                          \n          You have completed the sample CA InterTest test session. As part of\n  this session, you:                                                                                      \n                  \n         * displayed program source code and compiler output online\n         * displayed and modified main storage\n         * controlled program execution                                                                   \n                                                     \n  This is just a fraction of CA InterTest's capabilities. You can also:                                   \n                                                \n         * display or modify any CICS file, or DL/1, DB2, or SQL/DS database\n         * set and remove many kinds of monitoring options                                                \n                                                                                                          \n                    Press ENTER or CLEAR to complete the termination.\n2.To complete this part of the sample test session, press Clear or Enter to clear your screen.\n 327", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c4bf265049d1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThis demo session taught you the basics of using the application to test and debug an assembler program.\nYou learned how to perform the following tasks:\nSelect a source program for display\nGo to ITST Menu Option 1.1. Select a program from the list.\nSet monitoring for a program\nUse the MONITOR command or PF5 from Source Listing.\nView a Monitoring Status display\nUse the STATUS command or PF12 from Source Listing.\nInterpret the information that the application provides when an error is detected\nView the Automatic Breakpoint and press PF1 for help.\nDisplay the value of a data item in a Keep window\nType K to the left of a variable, place the cursor under the variable and press Enter.\nModify main storage\nOvertype the value in the Keep Window or type D to the left of a variable. Place the cursor under the variable and\npress Enter for a CORE Main Storage display. On the CORE screen, overtype the values and press Enter.\nSet an uncondition\nal \"before\" breakpoint\nType U to the left of an instruction and press Enter.\nRemove a breakpoint from the Monitoring Status display\nUse PF12 to view Monitoring Status. Type R next to a UBP and press Enter.\nRemove a breakpoint from the Source Listing Display\nOn Source Listing, overtype U with X and press Enter.\nRemove a data item from a Keep window\nType X to the left of a Keep window entry and press Enter.\nResume program execution\nUse the RESUME command or PF5.\nAssembler Debugging Programs\nThis article provides an overview of CICS Debugging key functions.\nFor complete information, see CICS Debugging  and the Help facility.\nChecklist of Basic Debugging Tasks\nFollowing is a list of debugging tasks:\n\u2022Display the source listing\n\u2022Set monitoring for a program\n\u2022Set breakpoints", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c4bf265049d1-1", "text": "\u2022Display the source listing\n\u2022Set monitoring for a program\n\u2022Set breakpoints\n\u2022Set other monitoring options as needed\n\u2022Initiate the program\n\u2022End the test session\nWhen the program stops at a breakpoint, you can perform the following tasks:\n 328", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3e12e5a90961-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Inspect and modify main storage\n\u2022Inspect and modify auxiliary storage\n\u2022Set and remove breakpoints\n\u2022Keep variables in the Keep window to observe changes in their values\n\u2022Resume execution\n\u2022Abend the task\nDisplay Your Source Listing\nYou can display your source listing online at any time from CICS using the ITST menus (Option 1 Source). Use PF7 to\nscroll backward through the listing; use PF8 to scroll forward.\nAlternatively, enter the following command directly from CICS:\nLIST=progname \nprogname\nSpecifies the name of the program.\nEither method permits access to any InterTest for CICS function.\nNOTE\n\u2022The standard InterTest for CICS transaction IDs, such as LIST, ITST, CORE, and FILE, might have been\nchanged at your site. If any of the transactions that are mentioned in this article do not function as described,\ncontact the person who installed InterTest for CICS.\n\u2022Depending on your defaults, the options and PF keys available to you might not display at the top of the\nSource Listing Display. If this information is not displayed, you can view it by pressing PF4 to access the\nProfile screen, and then setting Display window to T.\nDisplay Sections of Your Program\nThe LOCATE command or option number (OPTS) listed on the header of the Source Listing screen make it easy to\ndisplay any section of your Assembler program. Enter the LOCATE command on the command line, or the number of the\nsection you want to display in the Option # field, and press Enter. For example, if you enter L .C1 in the command line or 1\nin the Option # field, InterTest for CICS displays the first CSECT.\nThe following table shows what Assembler areas are displayed when you use the LOCATE command or option numbers:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3e12e5a90961-1", "text": "Command Option # Assembler Area Displayed\nL .C1 1 1st CSECT\nL .MC 5 Macro and Copy Source Catalog for high-\nlevel output\nL .XR 6 Cross Reference\nL .LI 7 Literals Cross Reference\nL .EM 8 Error Messages\nSearch for Strings and Labels\nYou also can search for and can display a character string by entering a FIND string NEXT/PREV command on the\ncommand line or option 9 (Search forward) or 10 (Search backward) in the Option # field and entering the character string\nin the Search field. For example, the following screen shows you how to search backward for the string tasknum :\nCA InterTest for CICS  - PROTSYM FILE SOURCE LISTING DISPLAY\nCOMMAND ===> f tasknum prev  \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01\n 329", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b1da3791639a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                        Search=                                \n---------+---------------------------------------------------------------------\n     LOC  OBJECT CODE    ADDR1 ADDR2  STMT        SOURCE STATEMENT             \n _ 000000 90EC D00C            0000C  1177+         STM   14,12,12(13)         \n                                      1178+*********************************** \n                                      1179+*              ESTABLISH CODE ADDRE \n                                      1180+*********************************** \n                 R:2347  00000        1181+         USING *-4,2,3,4,7          \n _ 000004 182F                        1182+         LR    2,15                 \n _ 000006 1832                        1183+         LR    3,2                  \n _ 000008 4A30 2020            00020  1184+         AH    3,DFHEI4K            \n _ 00000C 1843                        1185+         LR    4,3                  \n _ 00000E 4A40 2020            00020  1186+         AH    4,DFHEI4K            \n _ 000012 1874                        1187+         LR    7,4                  \n _ 000014 4A70 2020            00020  1188+         AH    7,DFHEI4K            \n                                      1189+*********************************** \n                                      1190+*              OBTAIN DYNAMIC STORA \n                                      1191+*********************************** \n _ 000018 4510 2022            00022  1192+         BAL   1,*+10", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b1da3791639a-1", "text": "_ 00001C 0357                        1193+         DC    AL2(DFHEIEND-DFHEIST \n _ 00001E 0000                        1194+         DC    H'0'                \nExit the Source Listing Facility\nPress Clear to return to CICS. The application displays the following message:\nLister Function Terminated\nStart a Test Session\nThis section explains how to start a testing session.\nTurn on Monitoring\nTo test a program, you must instruct InterTest for CICS to monitor  it. When InterTest for CICS monitors a program, it\ndetects and prevents errors before they occur, including the following events:\n\u2022All storage violations\n\u2022All CICS abends\n\u2022Any instruction that would cause a program check or other abend\n\u2022All illegal or invalid instructions that would cause CICS to crash\n\u2022All wild branches\n\u2022All violations of CICS standards\nThe easiest way to turn on monitoring is from the program source listing. Follow these steps:\n1.Display the source listing as described in the preceding section. A sample Source Listing Display is shown in the\nprevious screen.\n2.Type MONITOR on the command line or Press PF5 to set monitoring, which remains in effect for the program until\nremoved.\n3.Press Clear to return to CICS.\nNOTE\nBefore pressing Clear to return to CICS, you might want to set breakpoints directly on the source listing.\n 330", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ad5d14bdc680-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nExecute a Program\nOnce you turn on monitoring for a program, you are ready to execute it. After you enter the program transaction ID, one of\nthe following occurs:\n\u2022Your program runs to completion. The results might not be correct.\n\u2022InterTest for CICS stops your program at a breakpoint; either one set by you or one automatically triggered by InterTest\nfor CICS because it detected an error.\nSet and Remove Breakpoints\nWhen you test a program, it is important to be able to halt program execution at specified locations. A halt in program\nexecution is called a breakpoint .\nWhat You Can Do at a Breakpoint\nWhen your program is stopped at a breakpoint, you can perform the following tasks:\n\u2022Examine the source listing\n\u2022Inspect and modify main storage\n\u2022Inspect and modify auxiliary storage\n\u2022Set and remove breakpoints\n\u2022Keep variables in the Keep window to observe changes in their values\n\u2022Set and remove monitoring options\n\u2022Resume execution\n\u2022Abend the task\nTypes of Breakpoints\nThe following list shows types of breakpoints:\nAutomatic\nThe program stops because InterTest for CICS detected and prevented an error.\nUnconditional\nThe program stops at the specified location.\nConditional\nThe program stops at the location that you specify if a condition is met. Optionally, conditional breakpoints can be\nset to stop at any instruction if a condition is met.\nVariable-change\nThe program stops whenever the value of a specified variable has changed.\nRequest\nThe program stops at every CICS command or macro, or at certain CICS commands or macros, or at calls to DL/\nI, DB2, or software.\nSingle-step\nThe program stops after executing one or more instructions.\nAn automatic breakpoint occurs when InterTest for CICS detects an error. When a program is stopped at an automatic", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ad5d14bdc680-1", "text": "breakpoint, you can either correct the error or you can go around it. You can press PF1 for help on what caused the error\nand how to use InterTest for CICS to fix it. You set the other breakpoints.\n 331", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3b716f6861ff-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSet Unconditional Breakpoints on the Source Listing\nTo set an unconditional breakpoint on the program source listing, perform the following task:\n1.Type U or ) in column 1 next to the offset where you want the breakpoint. The U sets a breakpoint that stops before  the\ninstruction is executed. The ) sets a breakpoint that stops after the instruction is executed.\n2.Press Enter.\nThe following screen shows how to set a \"before\" breakpoint at the CP instruction at 1A6.\nCA InterTest for CICS - PROTSYM FILE  SOURCE LISTING DISPLAY            \nCOMMAND ===>                                                                    \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01  \n                                        Search=                                 \n----------+-------------------------------------------------------------------- \n     Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n                    R:9  00000        1452          USING COMAREA,R9            \n _ 00018E                             1454 CONTINUE DS    0H                    \n _ 00018E 4150 01D5            001D5  1455          LA    R5,S2LEN              \n _ 000192 4050 D1B0            001B0  1456          STH   R5,MSGLEN             \n _ 000196 FA20 D189 4AE8 00189 02AE8  1457          AP    TASKNUM,=P'1'         \n _ 00019C F920 D189 4AE9 00189 02AE9  1458          CP    TASKNUM,=P'2'", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3b716f6861ff-1", "text": "_ 0001A2 4720 2328            00328  1459          BH    ENDMSG                u 0001A6 F920 D189 4AE8 00189\n 02AE8  1460          CP    TASKNUM,=P'1'         \n _ 0001AC 4780 227E            0027E  1461          BE    SENDSCR4              \n _ 0001B0 47F0 2328            00328  1462          B     ENDMSG                \n _ 0001B4                             1464 RETURN   DS    0H                    \n                                      1465 *        EXEC CICS SEND FROM(OUTMSG  \n                                      1466          DFHECALL =X'04043000080000  \n   0001B4 4110 D068            00068                      ),(FB_2,OUTLEN)       \n                                      1482 *        EXEC CICS SEND FROM(SCREEN  \n                                      1483          DFHECALL =X'04043000080000  \n   0001DA 4110 D068            00068                      2),(FB_2,MSGLEN)      \n                                      1499 *        EXEC CICS RETURN\nAfter you set a breakpoint, InterTest for CICS redisplays the screen with an uppercase U or a ). This character remains\nuntil you remove the breakpoint.\nWhen you execute the program, InterTest for CICS stops the program at the unconditional breakpoint.\nYou can set breakpoints at any time -- before you execute the program and when the program is stopped. Although where\nyou decide to set breakpoints depends on the specifics of your program, you may want to set breakpoints at the following\npoints:\n\u2022At the beginning of the program, so when the program executes you can set more breakpoints", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3b716f6861ff-2", "text": "\u2022At the beginning of the program, so when the program executes you can set more breakpoints\n\u2022At labels, so you can examine the contents of variables at the start of sections\n\u2022Before a CALL, so you can dynamically control the program path\n\u2022At each location named in an EXEC CICS HANDLE CONDITION, so you can verify error handling\nTo remove an unconditional breakpoint, type an X over the U or ) and press Enter, or type R next to the breakpoint entry\non the Monitoring Status display (PF12 from any Source display). Remove breakpoints that are no longer needed so\nthat you are not stopped when you retest the program.\nInspect and Modify Main Storage\nThe ability to inspect main storage at a breakpoint means you can determine the values of variables without using a\ndump. Logic errors are easy to find because you can display the value of a variable where the variable is defined, and at\n 332", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "368885c20536-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nany point in the code where the variable is referenced. You can also dynamically change the value to correct errors or test\nother program paths.\nChanges to program storage are dynamic and the change affects only the current test session. To correct program errors,\nyou must change the source code and must recompile the program.\nYou can use many ways to inspect and modify main storage. We are going to discuss one of the easiest methods of\nviewing and changing program storage here. For another easy way to display and modify the values of variables, see\nKeep Variables in the Keep Window.\nRemember, you can inspect system storage at any time, independent of program monitoring and execution.\nDisplay the Value of a Variable\nWhen you are stopped at a breakpoint, you can request the display of the value of a variable directly from the source\nlisting.\n\u2022To display the variable value where it is defined, type D to the left of the instruction that defines it and press Enter, as\nshown in the next screen.\n\u2022To display the value of a variable where it is referenced, type D to the left of the instruction that references it, place the\ncursor under any character in the variable, and press Enter.\nThe following screen shows how to display the value of a variable where it is defined.\nCA InterTest for CICS  - PROTSYM FILE  SOURCE LISTING DISPLAY            \nCOMMAND ===>                                                                    \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01  \n                                        Search=                                 \n----------+-------------------------------------------------------------------- \n     Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n _ 000188                              366 TSSWITCH DS    CL1                   d 000189                      \n        367 TASKNUM  DS    PL3", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "368885c20536-1", "text": "367 TASKNUM  DS    PL3                   \n _ 00018C                              368 TSTEXT   DS    CL32                  \n _ 0001AC                              369 MSGNAME  DS    F                     \n _ 0001B0                              370 MSGLEN   DS    H                     \n _ 0001B2                              371 RECRBA   DS    CL4'    '             \n _ 0001B8                              372 RECPONT  DS    F                     \n                                       373 ***********************************  \n                                       374          COPY IN25AMP                \n _ 0001BC                              375=             DS    0H                \n                         001BC         376=DMAP04AS  EQU  *      .              \n _ 0001BC                              377=         DS    12C .             TI  \n _ 0001C8                              379=RECOUT1L DS    CL2 .  INPUT DATA FI  \n _ 0001CA                              380=RECOUT1F DS    0C .   DATA FIELD FL  \n _ 0001CA                              381=RECOUT1A DS    C .    DATA FIELD AT  \n _ 0001CB                              382=RECOUT1I DS    0CL40 .  INPUT DATA   \n _ 0001CB                              383=RECOUT1O DS    CL40 .   OUTPUT DATA  \n _ 0001F3                              385=RECOUT2L DS    CL2 .  INPUT DATA FI\nInterTest for CICS responds by requesting the base register. Specify the register, as shown in the following screen.\nCA InterTest for CICS   - PROTSYM FILE  SOURCE LISTING DISPLAY           \nCOMMAND ===>                                                                   \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01 \n                                        Search=                                \n-------------------------------------------------------------------------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "368885c20536-2", "text": "Search=                                \n-------------------------------------------------------------------------------\n \n 333", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "414dc9c4a4da-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBASE ________ for TASKNUM                                                      \n \nOvertype Underscores with a Base register  For example: R1 or TIOABAR  \nInterTest for CICS then displays the contents of the variable, as shown in the following panel:\n    CA InterTest for CICS  - MAIN STORAGE UTILITY - Termid = U015        \n \nStarting at Address =  100CE8  Disp   Structure Display Format                  \nTASKNUM                         189 | ?00000.                    |              \nTSTEXT                          18C | ............               |              \n                                    | ............               |              \n                                    | ........                   |              \nMSGNAME                         1AC |  0000000000.               |              \nMSGLEN                          1B0 | +00469.                    |              \nRECRBA                          1B2 | ......                     |              \nRECPONT                         1B8 |  0000000000.               |              \n                                1BC |  00000.                    |              \nDMAP04AS                        1BC |                            |              \n                                1BC | ............               |              \nRECOUT1L                        1C8 | ..                         |              \nRECOUT1F                        1CA | .                          |              \nRECOUT1A                        1CA | .                          |              \nRECOUT1I                        1CB | .                          |              \nRECOUT1O                        1CB | ............               |              \n ------------------------------------------------------------------------------ \n PF1 Help       2            3 End        4 Return     5            6 Dump      \n PF7 Backward   8 Forward    9 Caps Off  10           11 Redisplay 12 Structure \n CORE='R13.TASKNUM'", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "414dc9c4a4da-1", "text": "CORE='R13.TASKNUM'                                                             \n CAIN4713 R13 not found - have assumed its register value\n \nModify the Value of a Variable\nYou can modify the value of a variable by overtyping the bytes in the main storage display and pressing Enter. For\nexample, you could change the contents of TASKNUM in the previous screen by overtyping the question mark with +0\nand press Erase End of Field (EOF) to change the value from binary zeros to a packed decimal value.\nPress Clear or PF3 to return to the Source Listing.\nKeep Variables in the Keep Window\nThe Keep window lets you display the values of an unlimited number of variables directly on the source listing. If more\nthan six variables are selected for the Keep window, PF keys 19 and 20 are available to scroll forward and backward\nthrough the Keep window. Keeping variables in the window lets you observe changes in their values as the program\nexecutes. You also can change values by overtyping the displayed bytes.\nWhen the Keep window is active, the options and PF key functions are not displayed. Press PF4 to refer to them. When\nall the variables in the Keep window are removed, the options and PF key functions are redisplayed. A command line is\navailable to help you perform InterTest for CICS functions when the Keep window is active.\nAdd a Variable to the Keep Window\nYou can add variables to the Keep window whenever your source listing is displayed. Identify the variables whose values\nyou want to observe either before you execute the program, or when you are at a breakpoint.\n 334", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dce25349f0a0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFollow these rules to add a variable to the Keep window:\n\u2022To add a variable where it is defined, type K to the left of the statement defining it and press Enter. You are asked to\nspecify the base register, as shown in the previous screen.\n\u2022To add a variable where it is referenced, type K to the left of the statement referencing it, place the cursor under any\ncharacter in the variable, and press Enter.\nWhen you add a variable to the Keep window, InterTest for CICS displays the variable in its data-type appropriate\ndisplayable form:\nCA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \nCOMMAND ===>                                                                    \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ R13.TASKNUM                     |  00000. \n---------++-------------------------------------------------------------------- \n     Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n _ 000192 4050 D1B0            001B0  1456          STH   R5,MSGLEN             \n A 000196 FA20 D189 4AE8 00189 02AE8   ==>          AP    TASKNUM,=P'1'         \n _ 00019C F920 D189 4AE9 00189 02AE9  1458          CP    TASKNUM,=P'2'         \n _ 0001A2 4720 2328            00328  1459          BH    ENDMSG                \n _ 0001A6 F920 D189 4AE8 00189 02AE8  1460          CP    TASKNUM,=P'1'", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dce25349f0a0-1", "text": "_ 0001AC 4780 227E            0027E  1461          BE    SENDSCR4              \n _ 0001B0 47F0 2328            00328  1462          B     ENDMSG                \n _ 0001B4                             1464 RETURN   DS    0H                    \n                                      1465 *        EXEC CICS SEND FROM(OUTMSG  \n                                      1466          DFHECALL =X'04043000080000  \n   0001B4 4110 D068            00068                      ),(FB_2,OUTLEN)       \n                                      1482 *        EXEC CICS SEND FROM(SCREEN  \n                                      1483          DFHECALL =X'04043000080000  \n   0001DA 4110 D068            00068                      2),(FB_2,MSGLEN)      \n                                      1499 *        EXEC CICS RETURN            \n                                      1500 *              TRANSID(EIBTRNID)\nDisplay the Variable Structure in a Keep Window\nTo display the entire DSECT, type D to the left of the variable in the window and press Enter, as shown next.\nCA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \nCOMMAND ===>                                                                    \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- d____ R13.TASKNUM             \n        |  00000.                                \n---------++-------------------------------------------------------------------- \n     Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n _ 000192 4050 D1B0            001B0  1456          STH   R5,MSGLEN", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dce25349f0a0-2", "text": "A 000196 FA20 D189 4AE8 00189 02AE8   ==>          AP    TASKNUM,=P'1'         \n _ 00019C F920 D189 4AE9 00189 02AE9  1458          CP    TASKNUM,=P'2'         \n _ 0001A2 4720 2328            00328  1459          BH    ENDMSG                \n _ 0001A6 F920 D189 4AE8 00189 02AE8  1460          CP    TASKNUM,=P'1'         \n _ 0001AC 4780 227E            0027E  1461          BE    SENDSCR4              \n _ 0001B0 47F0 2328            00328  1462          B     ENDMSG                \n _ 0001B4                             1464 RETURN   DS    0H                    \n 335", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0bcd3713ce47-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                      1465 *        EXEC CICS SEND FROM(OUTMSG  \n                                      1466          DFHECALL =X'04043000080000  \n   0001B4 4110 D068            00068                      ),(FB_2,OUTLEN)       \n                                      1482 *        EXEC CICS SEND FROM(SCREEN  \n                                      1483          DFHECALL =X'04043000080000  \n   0001DA 4110 D068            00068                      2),(FB_2,MSGLEN)      \n                                      1499 *        EXEC CICS RETURN            \n                                      1500 *              TRANSID(EIBTRNID)   \nInterTest for CICS responds by displaying the variable and all the items below it in the same DSECT.\nModify the Value of a Variable in a Keep Window\nModify the value of a variable in the Keep window by overtyping the displayed bytes, as you would overtype the bytes in a\nmain storage display. For more information, see Inspect and Modify Main Storage.\nNOTE\nIf you try to change password protected storage areas not owned by your program, InterTest for CICS prompts\nyou to enter the password.\nRemove a Variable from the Keep Window\nTo remove a variable from the Keep window, type X to the left of the variable, as shown next. In this example, four\nvariables are removed from the Keep window: MSGLEN, TSQTRAN, TSSWITCH, and TSQTERM.\nCA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \nCOMMAND ===>                                                                    \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01  \n                                        Search=                                 \n-------------------------------------------------------------------------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0bcd3713ce47-1", "text": "Search=                                 \n------------------------------------------------------------------------------- \n _____ R13.TASKNUM                     |  00000.                                x____ R13.MSGLEN           \n           | +00469.                                x____ R13.TSQTRAN                     | DEMA           \n                        x____ R13.TSSWITCH                    |                                        x____\n R13.TSQTERM                     | U015                                   \n---------++-------------------------------------------------------------------- \n     Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n _ 000180                              362 TSQNAME  DS    0CL8                  \n _ 000180                              363 TSQTRAN  DS    CL4                   \n _ 000184                              364 TSQTERM  DS    CL4                   \n _ 000188                              365 TSAREA   DS    0CL36                 \n _ 000188                              366 TSSWITCH DS    CL1                   \n _ 000189                              367 TASKNUM  DS    PL3                   \n _ 00018C                              368 TSTEXT   DS    CL32                  \n _ 0001AC                              369 MSGNAME  DS    F                     \n _ 0001B0                              370 MSGLEN   DS    H                     \n _ 0001B2                              371 RECRBA   DS    CL4'    '             \n _ 0001B8                              372 RECPONT  DS    F                     \n                                       373 *********************************** \nWhen all variables have been removed, the Keep window is replaced by the options and PF key functions.\n 336", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c96bd07cf453-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse Variable-Change Breakpoints to Detect Changing Values\nYou can request that the application halt execution whenever the value of a specified variable changes. This is called a\nvariable-change breakpoint. If you set a variable-change breakpoint while the variable is also listed in a Keep window,\nwhen the breakpoint is triggered, you immediately see the new value of the variable at the top of the breakpoint display.\nSet a Variable-Change Breakpoint\nA quick way to set a variable-change breakpoint is from a Keep window listing of the variable. Type V to the left of the\nvariable in the Keep window, and press Enter:\nCA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \nCOMMAND ===>                                                                    \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- v____ R13.TASKNUM             \n        |  00000.                                \n---------++-------------------------------------------------------------------- \n     Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n _ 000192 4050 D1B0            001B0  1456          STH   R5,MSGLEN             \n A 000196 FA20 D189 4AE8 00189 02AE8   ==>          AP    TASKNUM,=P'1'         \n _ 00019C F920 D189 4AE9 00189 02AE9  1458          CP    TASKNUM,=P'2'         \n _ 0001A2 4720 2328            00328  1459          BH    ENDMSG                \n _ 0001A6 F920 D189 4AE8 00189 02AE8  1460          CP    TASKNUM,=P'1'", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c96bd07cf453-1", "text": "_ 0001AC 4780 227E            0027E  1461          BE    SENDSCR4              \n _ 0001B0 47F0 2328            00328  1462          B     ENDMSG                \n _ 0001B4                             1464 RETURN   DS    0H                    \n                                      1465 *        EXEC CICS SEND FROM(OUTMSG  \n                                      1466          DFHECALL =X'04043000080000  \n   0001B4 4110 D068            00068                      ),(FB_2,OUTLEN)       \n                                      1482 *        EXEC CICS SEND FROM(SCREEN  \n                                      1483          DFHECALL =X'04043000080000  \n   0001DA 4110 D068            00068                      2),(FB_2,MSGLEN)      \n                                      1499 *        EXEC CICS RETURN            \n                                      1500 *              TRANSID(EIBTRNID)\nIn this example, InterTest for CICS sets a variable-change breakpoint for TASKNUM. This means InterTest for CICS halts\nexecution whenever the value of TASKNUM changes from its current value, as displayed in the Keep window.\nYou can also set variable-change breakpoints from various parts of your program listing using the letter V as follows:\n\u2022To set a variable-change breakpoint from where a variable is defined, type V to the left of the statement defining it, and\npress Enter.\n\u2022To set a variable-change breakpoint from where a variable is referenced, type V to the left of the statement referencing\nit, place the cursor under any character in the variable, and press Enter.\nYou can set a variable-change breakpoint any time during execution, or from a listing of your program before execution", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c96bd07cf453-2", "text": "begins. If you set the breakpoint before execution begins, the initial value of the variable is its value when it first becomes\nknown to InterTest for CICS during execution. Any change from the initial value triggers the variable-change breakpoint.\nView the Variable-Change Breakpoint\nThe uppercase V that appears to the left of the highlighted statement easily identifies a breakpoint display as a variable-\nchange breakpoint, as shown in the following panel:\nCA InterTest for CICS  - PROTSYM FILE   COND  BEFORE  BREAKPOINT         \n 337", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8996238fe2dc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCOMMAND ===>                                                                    \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ R13.TASKNUM                     | +00001.                                \n---------++-------------------------------------------------------------------- \n     Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n _ 000196 FA20 D189 4AE8 00189 02AE8  1457          AP    TASKNUM,=P'1'          V 00019C F920 D189 4AE9 00189\n 02AE9   ==>          CP    TASKNUM,=P'2'               ==>                                                 \n                             ==> CAIN3630 Conditional breakpoint    requested at offset .ANY                 \n ==> IF='R13.TASKNUM'.NE.'R13.TASKNUM'                                            ==>                        \n            \n _ 0001A2 4720 2328            00328  1459          BH    ENDMSG                \n _ 0001A6 F920 D189 4AE8 00189 02AE8  1460          CP    TASKNUM,=P'1'         \n _ 0001AC 4780 227E            0027E  1461          BE    SENDSCR4              \n _ 0001B0 47F0 2328            00328  1462          B     ENDMSG                \n _ 0001B4                             1464 RETURN   DS    0H                    \n                                      1465 *        EXEC CICS SEND FROM(OUTMSG  \n                                      1466          DFHECALL =X'04043000080000  \n   0001B4 4110 D068            00068                      ),(FB_2,OUTLEN)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8996238fe2dc-1", "text": "1482 *        EXEC CICS SEND FROM(SCREEN  \n                                      1483          DFHECALL =X'04043000080000\nThe lines below the highlighted line further identify the breakpoint. If you set more than one variable-change breakpoint,\nthis information lets you know which variable triggered the breakpoint.\nWhy does the breakpoint display refer to this as a conditional breakpoint? Because a variable-change breakpoint is\nactually a special type of conditional breakpoint. The condition InterTest for CICS checks for, at ANY statement, is shown\nas:\nIF'data-item'.NE.'data-item'\nThis is interpreted as:\nIF data-item (current) NOT EQUAL TO variable (value when breakpoint set)\nFor more information on using conditional breakpoints, see Using Breakpoints.\nRemove a Variable-Change Breakpoint\nTo remove a breakpoint from the variable-change breakpoint display, overtype the V with an X and press Enter.\nYou can also remove the breakpoint from the Monitoring Status display (PF12 from any Source display). The following\nscreen shows removing the variable-change-breakpoint set on the variable TSSWITCH in the program ASMDEMO.\n-----------------  CA InterTest for CICS MONITORING STATUS  --------------\nCOMMAND ===>                                                                  \n \n  Type + to expand or - collapse option levels displayed below,               \n         or R to remove option(s).                                          \n \n    Option     Description                Attributes                          \n_ - ASMDEMO    Program monitor entry      Assembler                           \n    |          Waiting at breakpoint      Task 00050, CBP since 10:30 a.m.  \n_ - |-.ANY     User monitoring options    Active                              \n      |        Symbolic listing file      PROTSYM                             \n 338", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "736274d5d231-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n_ -   |-UBP    Unconditional breakpoint   Offset=00000050                     \n      |        Option ID                  79113AFF                            \n      |        From, to terminals         G001, G001                          r -   |-VBP    Variable change\n breakpoint Location=.ANY                       \n      |        Condition                  IF='R13.TASKNUM'.NE.'R13.TASKNUM'   \n      |        Compare type               Pic X (character strings)           \n      |        From, to terminals         G001, G001                          \n_     |-SLB    Source listing breakpoints G001                                \n               *** End of data ***                                            \n \nPF7 Backward   8 Forward    9           10           11           12\nInspect and Modify Auxiliary Storage\nYou can use InterTest for CICS to inspect and modify the following items:\n\u2022VSAM and BDAM files\n\u2022DL/I, DB2, and SQL/DS databases\n\u2022Temporary storage\n\u2022Transient data\nYou can inspect and modify auxiliary storage at any time, regardless of whether a program is executing. This capability\nlets you maintain files and databases without writing one-time programs. You can perform any VSAM, BDAM, or DL/I\nfunction and most SQL functions.\nThe ability to inspect and modify auxiliary storage when a program is stopped at a breakpoint lets you change test data\nin the middle of a test session. Any changes you make are permanent; that is, changes to the file remain after the test\nsession ends.\nInspect Auxiliary Storage\n----------------  CA InterTest for CICS  MONITORING STATUS  --------------\nOPTION  ===> 1 \n \n    Select an auxiliary storage type, specifying optional criteria below.     \n \n    1  Files              - Display/select files for access", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "736274d5d231-1", "text": "1  Files              - Display/select files for access                     \n    2  DB2 database       - Invoke DB2 SQL interface facility                   \n    3  DL/I database      - Access DL/I database                                \n    4  TD queues          - Display/select transient data queues for access     \n    5  TS queues          - Display/select temporary storage queues for access  \n \n    Type specific or generic file/queue name(s):                                \n \n    filename ________ ________ ________ ________ ________ ________ ________   \nAlternatively, if you are at a clear CICS screen, you can invoke the FILE transaction. InterTest for CICS displays the\nfollowing panel:\n DATATYPE= FC FILEID=          MODE=      LOG=OFF TODEST=         PASSWORD=  \n FUNC=      SUBFUNC=      RETMETH=        ARGTYP=     SRCHTYP=                 \n MESSAGE=                                                                      \n  RETNRCID=                                                        CHGELEN=    \n 339", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "63c2b28fea34-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n     RCID=                                                                     \n     DATA=                                                         SIZE= 0000  \n FORMAT= D 00112233 44556677 8899AABB CCDDEEFF  *0123456789ABCDEF*             \n LOC 0000  ........ ........ ........ ........ ................               \n \n                      CA InterTest for CICS  \n                  Copyright \u00a9 SOLVE:Access  CA.  All rights reserved.      \n ----------------------------------------------------------------------------  \n 1 Help       2 Format C   3 End        4 BEGB       5            6 DataType DL \n 7 Page bwd   8 Page fwd   9 Caps Off  10 Top       11 Bottom    12            \nNOTE\nIf the FILE transaction does not display the previous screen, it is probably because the person who installed\nInterTest for CICS changed the name of the FILE transaction. Contact that person to find out the correct name.\nAfter you enter the file or database and, optionally, the record or segment, InterTest for CICS displays the data. A sample\nVSAM record in dump format follows.\n DATATYPE= FC FILEID= INVNTRY   MODE=     LOG=OFF  TODEST=        PASSWORD=\n FUNC=     SUBFUNC=      RETMETH=        ARGTYP=    SRCHTYP=                  \n MESSAGE= RECORD OBTAINED FOR VIEWING                                          \n  RETNRCID=F0F0F0F0F0F0F0F0F5                                     CHGELEN=     \n     RCID=C`000000005'                                                         \n     DATA=                                                        SIZE= 0050   \n FORMAT= D 00112233 44556677 8899AABB CCDDEEFF *0123456789ABCDEF*              \n LOC 0000  ........ ........ ........ ........ ................", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "63c2b28fea34-1", "text": "LOC 0000  ........ ........ ........ ........ ................               \n   0000    F0F0F0F0 F0F0F0F0 F0F54040 0087338F   0000000005       DSORG=VSKS   \n   0010    F0F3F9F9 0407835C 40404040 40404040   0399....       RECFM=VB       \n   0020    40404040 40404040 C1C2C340 C3D6D9D7           ABC CORP  LRECL=0050  \n   0030    F0F9F1F2 F8F74040 0000598C 40404040   091287           BLKSIZE=0000 \n   0040    D1D6C3D5 404040E2 D4C9E3C8 40404040   JOHN  SMITH      KEYPOS=0000  \n   0050                                                           KEYLEN=0A    \n   0060                                                           STRNO=01     \n   0070                                                                        \n   0080                                                           READ         \n   0090                                                           ADD          \n   00A0                                                           UPDATE       \n -----------------------------------------------------------------------------  \n 1 Help       2 Format C   3 End        4 BEGB       5 PREV      6 DataType DL \n 7 Page bwd   8 Page fwd   9 Caps Off  10 Top      11 Bottom    12            \nNOTE\nThe data displays in both hexadecimal and character format.\nTo return to the source listing, press Clear or PF3.\nModify Auxiliary Storage\nTo modify the record or segment, simply overtype the hexadecimal or character data and press Enter. For example, you", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "63c2b28fea34-2", "text": "could overtype JOHN SMITH with DALE COOPER on the sample display in the previous screen.\nTo rewrite the modified record, type PUT in the FUNC= field and press Enter.\n 340", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e85995dbf13f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDisplay Auxiliary Storage in Structured Format\nFILE can display file, transient data, and temporary storage records or DL/I segments field-by-field in structured format\nusing the Assembler DSECT. To display a record or segment in structured format, you must identify the program\ncontaining the structure. Symbolic information for this program must be saved in the InterTest for CICS Symbolic File.\nFollow these steps to display a record or segment in a structured format:\n1.If the FORMAT field does not contain S, press PF2 until FORMAT= S is appears. The USE=field now appears after the\nFORMAT field.\n2.Identify the program and structure in the USE= field. Specify the command as follows:\nUSE=symbolic-name.structure-name\nsymbolic-name  is the name of the program as defined in the InterTest for CICS Symbolic File.\nstructure-name is the Assembler DSECT.\n3.Press Enter.\nInterTest for CICS displays the record or segment in structured format. A sample VSAM record in structured format\nfollows.\nDATATYPE= FC FILEID= ORDERFIL MODE=      LOG=OFF TODEST=        PASSWORD=  \nFUNC=      SUBFUNC=      RETMETH=        ARGTYP=    SRCHTYP= \n MESSAGE= RECORD OBTAINED FOR VIEWING\n  RETNRCID=F0F0F0F0F0F0F0F0F0F2                                   CHGELEN= \n     RCID= C'0000000002' \n     DATA=                                                        SIZE= 0320 \n FORMAT= S USE= ASMDEMO.DFHEISTG \n LOC 00B8  Displacement               Hexadecimal                  Character \n ------------------------------------------------------------------------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e85995dbf13f-1", "text": "LOC 00B8  Displacement               Hexadecimal                  Character \n ------------------------------------------------------------------------------ \n DFHEIUSR            B8 | 00                                  | . \n TSQNAME             B8 | 00000000 00000000                   | ........ \n TSQTRAN             B8 | 00000000                            | .... \n TSQTERM             BC | 00000000                            | .... \n TSAREA              C0 | 00C3D6D9 D7F6F0F5 F4F40000 000000C7 | .CORP60544.....G \n                        | D6D6C440 D7D9C9C3 C5000000 00000000 | OOD PRICE....... \n                        | 000000C2                            | ...B \n TSSWITCH            C0 | 00                                  | . \n TASKNUM             C1 | C3D6D9                              | COR \n TSTEXT              C4 | D7F6F0F5 F4F40000 000000C7 D6D6C440 | P60544.....GOOD \n                        | D7D9C9C3 C5000000 00000000 000000C2 | PRICE..........B \n                        |                                     | \n ------------------------------------------------------------------------------ \n 1 Help       2 Format D   3 End        4 BEGB       5 PREV      6 DataType DL \n 7 Page bwd   8 Page fwd   9 Caps Off  10 Top      11 Bottom    12\nStructured format lists the contents of each data name in both hexadecimal and character format. To modify the record or\nsegment, overtype either the hexadecimal or character data and press Enter. To rewrite the modified record, type PUT in\nthe FUNC= field and press Enter.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e85995dbf13f-2", "text": "the FUNC= field and press Enter.\nWhen a program is stopped at a breakpoint, you can substitute an asterisk ( *) for the symbolic-name. For example, if\nprogram PAYROLL is stopped at a breakpoint and you enter:\nUSE=*.payrec\nInterTest for CICS uses the program named PAYROLL and the PAYREC structure.\nTo begin the structure with a specific data name, enter this command in the DATA field:\nFIND=data-name\n 341", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "95cddf1011b4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWhere data-name  is the data name to be displayed.\nResume Program Execution\nAfter you perform breakpoint activities, such as displaying and modifying main or auxiliary storage, you can do the\nfollowing actions:\n\u2022Resume program execution from a specific location\n\u2022Single-step through execution one instruction at a time\nResume Execution from a Specific Location\nTo resume program execution from the breakpoint location where your program is stopped, the source listing screen must\nbe displayed. Press Clear from any InterTest for CICS screen until the breakpoint screen reappears.\nEnter the GO command on the command line or Press PF5 to continue from the current breakpoint. Execution continues\nuntil the program is halted at another breakpoint or the task completes. If you do not want to halt the program at any of\nyour preset breakpoints, you can enter the RUN command on the command line and the program will continue execution\nfrom the current breakpoint and preserve all preset breakpoints.\nIf you are stopped at an automatic breakpoint, you must first correct the error that triggered the breakpoint before\ncontinuing execution from that point. Or, you can go around the error and continue execution from another location.\nTo resume program execution from another location, follow these steps:\n1.Display the instruction where you want to resume execution. For more information, see Resume and Execution\nOptions.\n2.Type G to the left of that instruction.\n3.Press Enter.\nOr\n\u2022Enter GO label or GO linenumber  on the command line and press enter\nProgram execution resumes from that instruction label or line number.\nThe following example shows how to resume execution from a location prior to an automatic breakpoint. This is useful\nif you corrected a record or if you dynamically modified an incorrect file name and now want the program to reread the\nrecord or file.\nCA InterTest for CICS  - PROTSYM FILE SOURCE LISTING BREAKPOINT", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "95cddf1011b4-1", "text": "CA InterTest for CICS  - PROTSYM FILE SOURCE LISTING BREAKPOINT\nCOMMAND ===>                                                                   \nProgram= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01  \n                                        Search=                                \n---------+---------------------------------------------------------------------\n     LOC  OBJECT CODE    ADDR1 ADDR2  STMT        SOURCE STATEMENT              \n _ 001B94 D201 48FA 4A0C 028FA 02A0C  2099          MVC   FIRST,=CL2'NO'        \n                                      2100 *        EXEC CICS SEND              \n                                      2101 *              MAP ('DMAP04')        \n                                      2102 *              MAPSET ('IN25AMP')    \n                                      2103 *              ERASE                 \n                                      2104 *              WAIT                  \n                                      2105          DFHECALL =X'1804D000080000  \n     Active Usings: ASMDEMO(X'4000'),R2,R3,R4,R8  COMAREA(X'1000'),R9 DFHEIBLK(\n   001B9A 4110 D068            00068                     ),(______RF,DMAP04O),,\n _ 001BC2 9200 B01A      0001A        2120          MVI   EIBAID,X'00'          \n                                      2121 *        EXEC CICS RECEIVE           \n _ 001BC6 4110 D068            00068  2122          DFHECALL =X'04020000080000  \n 342", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "35df05e2c483-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _ 001BDC 956D B01A      0001A        2132          CLI   EIBAID,DFHCLEAR       \n _ 001BE0 4780 2300            00300  2133          BE    ENDMSG                \n g 001BE4 47F0 3FAE            01FAE  2134          B     READATA               \n _ 001BE8                             2136 SENDMP02 DS    0H                    \n                                      2137 * SEND OUT A SCREEN                  \n _ 001BE8 D201 48FE 49FE 028FE 029FE  2138          MVC   MAPNUM,=CL2'03'\nWhen you press Enter, execution resumes from offset 1BE4, the location you identified with a G.\nSingle-Stepping\nSingle stepping enables your program to execute one Assembler instruction and then stop again. You can adjust the step\namount so that the program executes a specified number of instructions between stops.\nTo single-step: Type NEXT in the command line and press Enter, or press PF10 from the source listing. Your program\nexecutes the next instruction and then stops.\nTo single-step from a different program location, perform the following steps:\n1.Display the statement where you want to resume execution. For more information, see Display Your Source Listing.\n2.Type G to the left of that statement.\n3.Type NEXT in the command line and press Enter or press PF10.\nTo adjust the step amount, perform the following steps:\n1.Press PF4 to access the Source Listing Profile screen.\n2.Change the number in the Stepping amount field.\n3.Press Enter. InterTest for CICS changes the step amount and redisplays the source listing. If Titles are set to on (an", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "35df05e2c483-1", "text": "option on the Source Listing Profile screen), you see the new step amount displayed next to PF10 at the top of the\nSource Listing Breakpoint screen.\nAbend a Task\nWhen your program stops at a breakpoint, you can abend your task rather than resume execution. To abend a task, enter\nthe ABEND command from the breakpoint display and press Enter. InterTest for CICS displays the following screen.\n-----------------  CA InterTest  ABEND BREAKPOINTED TASK  ----------------\nCOMMAND ===>                                                                  \n \n   Type an abend code, then press ENTER.                                    \n \n \n   Abend Code  ____   Abend code options are:                                 \n \n                      blanks        Normal abend, no dump                     \n                      XXXX          Abend exits cancelled, no dump            \n                      your code     Your abend code, dump taken               \n\u2022To cancel the abend, press PF3 or Clear. InterTest for CICS redisplays the breakpoint screen.\n\u2022To abend without a dump:\n\u2013For a normal abend, press Enter\n\u2013To cancel all program exits, specify code XXXX and press Enter\n\u2022To abend with a dump, specify a four-character dump code and press Enter. The dump code that you specify cannot\nbe XXXX and cannot begin with the letter A.\n 343", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0333da417203-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nGet Help\nHelp is always available when you are using InterTest for CICS. You can also use Help to initiate InterTest for CICS, type\nin Help on a clear screen under CICS.\nGet Help Using InterTest for CICS\nWhen you are using InterTest for CICS, you can press PF1 at any time for information on InterTest for CICS functions. For\nexample, the following screen lists the Help topics for the Source Listing facility.\nCA INTERTEST - INTERACTIVE HELP FACILITY -\nTUTORIAL: SOURCE LISTING FACILITY - FOR ASSEMBLER PROGRAMS                     \n \n \n 05  Set Monitoring                    45  Set/Remove other Monitoring Options  \n 10  Locating areas in the listing     50  Displaying data items                \n 20  Search for a Data string          60  Resume TASK execution                \n 30  PF key definitions                65  Abending your task                   \n 32  Primary Line Commands             70  PROFILE, AUTOSTEP, AUTOKEEP Options  \n 35  Set the Display Margins           75  Code Coverage Option                 \n 40  Set/Remove Breakpoints            80  View Program Backtrace               \n \n \n \n \n \n \n \n                                                                          (end)\n ------------------------------------------------------------------------------\nENTER A SELECTION CODE FROM THE MENU, OR N FOR NEXT PAGE, P FOR PRECEDING PAGE, \n M FOR RETURN TO PREVIOUS MENU,  CLEAR TO EXIT, OR MESSAGE NUMBER. ==> 05     \nGet Help to Correct an Error\nWhen your program stops at an automatic breakpoint, InterTest for CICS displays a short message identifying the reason\nfor the breakpoint. Press PF1 for information on what caused the error that triggered the breakpoint and how to fix it. The", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0333da417203-1", "text": "following screen explains how to correct an AEIL abend.\nCA INTERTEST - INTERACTIVE HELP FACILITY -   \nTUTORIAL: ERROR MESSAGE AEIL                                                   \n \n The dataset name referred to in the DATASET option cannot be found in the FCT.\n Your program did not have a Handle Condition for this error. Or a second Handle\n Condition without a routine for this error superseded the one that had a       \n routine for this error.                                                      \n \n WHAT YOU CAN DO: If the named file was entered incorrectly and the one you     \n wanted exists, you may use the Replace File Option to dynamically replace the  \n file name and then use the resume task facilities to execute the CICS request  \n again. To perform the above functions from the Source Listing Breakpoint screen\n you would:                                                                     \n \n 1. Key =20s in the Option # field and press ENTER.                           \n 2. Tab to  Replace file name:   Key in the incorrect file name.              \n 344", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "96aef7ded5b2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 3. In the next field, key in the correct file name and press ENTER.          \n 4. Press CLEAR  to return to your Source Listing Breakpoint screen.          \n 5. Key in G to resume execution at the beginning of the EXEC CICS command      \n    and press ENTER.                                                          \n                                                                    (continued)\n ------------------------------------------------------------------------------\nENTER N FOR NEXT PAGE, P FOR PRECEDING PAGE, F FOR FIRST PAGE, OR -             \n M FOR RETURN TO PREVIOUS MENU,  CLEAR TO EXIT, OR MESSAGE NUMBER. ==> N\nNOTE\nWhen you leave and then return to an automatic breakpoint screen, the error message may no longer appear.\nFor help on the cause of the error, press Clear to redisplay the error message before pressing PF1.\nEnd a Test Session\nAfter your program completes execution or you abend your task, you return to CICS.\nStatus After Testing\nThe following table shows the status of your program after testing:\nProgram Part Any Changes\nprogram source code not modified\nfile/database updates by the program permanent\nfile/database updates that you made permanent\nInterTest for CICS monitoring, breakpoints, and other options set\nfor the programremain in effect\nCorrect the Source Code\nYou might want to correct the source code and continue testing from a clean version of the program.\nAfter you modified the source code and recompiled the program, you can load the new copy of the program by using the\nNew Program Copy option on the Program Monitoring menu (ITST 2.1).\nThe New Program Copy option resets symbolic breakpoints and other monitoring options for the recompiled program. It\nalso resets the PPT entry to the new library address of the program.\nAssembler Advanced Monitoring Features\nThis article describes commonly used Assembler Advanced Monitoring features.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "96aef7ded5b2-1", "text": "Assembler Advanced Monitoring Features\nThis article describes commonly used Assembler Advanced Monitoring features.\nFor information about all product features, see CICS Debugging  and the Help facility.\nThis article contains the following topics:\nSet Options from the Monitoring Menus\nThe InterTest for CICS monitoring menus are the easiest way to set many monitoring options. Access these menus from\nthe Primary Option Menu by selecting Option 2 - Monitoring, shown in the following panel:\n ---------------  CA InterTest for CICS PRIMARY OPTION MENU  -------------\n OPTION  ===> 2                                                                  \n  \n 345", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "daea6047f0fc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n     1  Source             - Display/select program source files/listings        \n     2  Monitoring         - Display/modify CA InterTest monitoring/activity     \n     3  Main storage       - Display/modify CICS storage areas                   \n     4  Auxiliary storage  - Display/access databases/files/queues               \n     5  Dump analysis      - Invoke CA SymDump CICS dump/trace capture facility  \n     6  Product help       - Invoke CA InterTest product help facility           \n     7  Status/Maintenance - Product status and maintenance functions   \n     8  What's new?        - Display information about CA InterTest for CICS  \n     X  Exit               - Terminate menu processing                          \n .\n .\n .\n \nInterTest for CICS displays the Monitoring Menu, from which you can select different monitoring options. For a detailed\nexplanation of each of these options, see Monitoring Menu Options.\n --------------  CA InterTest for CICS MONITORING MENU  ------------------\n OPTION  ===>                                                                  \n  \n     1  Programs           - Display/modify program monitoring options          \n     2  Transactions       - Display/modify transaction monitoring options      \n     3  Terminals          - Display/modify terminal monitoring options         \n     4  Status             - Display/remove current monitoring options          \n     5  Active tasks       - Display/reconnect/purge active monitored tasks     \n     6  System-wide        - Display/modify global system-wide options          \n .\n .\n .     \n \nOption 1 - Programs accesses the Program Monitoring Menu, where you can set and remove program options, and\nrequest a status display.\n --------------------  CA InterTest for CICS  PROGRAM MONITORING  ------------------\n  COMMAND ===>", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "daea6047f0fc-1", "text": "COMMAND ===>                                                                   \n  \n    Type information and S to set or R to remove option(s) below.               \n  \n    Program  . . asmdemo_     Program name (or .ALL, .OPTIONS or generic)        \n    User ID  . .     ____     User (or .ANY) for whom the program is monitored   \n  \n    Option       Description                                            More:   +\n  _ Status       Display and/or remove monitoring options (S only)               \n  _ Monitor      Monitoring (R removes monitoring and all options previously set)\n  _ UBP          Unconditional breakpoints (specific program only)               \n  _ CBP          Conditional breakpoints (specific program only)                 \n  _ RBP          Breakpoints for CICS, DB2, DL/I or external CALL requests       \n  _ Stmt Trace   Statement tracing and data monitoring (COBOL only) \n  _ New copy     Fetch new copy of program and reset monitoring options (S only) \n  _ Commands     Indirect commands defined for a specific COBOL or PL/1 program \n  _ Replace      CICS resource name replacement options                          \n  _ Protect      Storage protection monitoring options                          \n  _ Special      Other options (storage allocation, file updating, etc.)         \n 346", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "812b7e42f892-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  _ Composite    Monitor multi-CSECT program's separately compiled components \n  \n  PF1 Help       2            3 End        4 Return     5            6           \n  PF7 Backward   8 Forward    9           10           11           12       \n \nQuick access to the Program Monitoring menu is available before or during a session.\nThe following table contains the fastpath entries that you can use to access the Program Monitoring menu:\nFrom Fastpath entry\nCICS, clear screen ITST 2.1\nPrimary Option Menu, Option field 2.1\nSource Listing display, Command line =2.1\nBreakpoint display, Command line =1.2.1\nAfter processing any program options from this menu, press PF3 to exit back to your test session. If you entered directly\nfrom CICS, you exit back to the ITST Primary menu. From a Source Listing or breakpoint, PF3 takes you back to that\ndisplay.\nConditional Breakpoints\nConditional breakpoints are breakpoints that take effect when a specific condition is met, such as when a counter exceeds\na value. These breakpoints can help you isolate complex problems.\nSet Conditional Breakpoints\nTo set a conditional breakpoint, begin by typing c to the left of the offset where you want the breakpoint, as shown next,\nand press Enter.\n CA InterTest for CICS  - PROTSYM FILE  SOURCE LISTING DISPLAY           \n COMMAND ===>                                                                   \n Program= ASMDEMO  Option # 9     Stmt #        Displacement=        Margin= 01 \n                                         Search= GETCOM                         \n ----------+--------------------------------------------------------------------\n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "812b7e42f892-1", "text": "Loc  Object Code    Addr1 Addr2  Stmt        Source Statement             \n  _ 000100 4980 B018            00018  1380          CH    R8,EIBCALEN          \n  _ 000104 4740 218A            0018A  1381          BL    GETCOM               \n  _ 000108 957D B01A      0001A        1382          CLI   EIBAID,DFHENTER      \n  _ 00010C 4780 218E            0018E  1383          BE    CONTINUE             \n  c 000110 47F0 2142            00142  1384          B     SENDSCR1             \n  _ 000114 0024                        1386 TSQLEN   DC    H'36'                \n  _ 000116 0001                        1387 TSQITEM  DC    H'1'                 \n  _ 000118                             1389 WRITETSQ DS    0H                   \n  _ 000118 9240 D188      00188        1390          MVI   TSSWITCH,C' '        \n                                       1392 *        EXEC CICS WRITEQ TS        \n                                       1393 *              QUEUE(TSQNAME)       \n                                       1394 *              FROM(TSAREA)         \n                                       1395 *              LENGTH(TSQLEN)       \n                                       1396 *              MAIN                 \n                                       1397          DFHECALL =X'0A02E000080000 \n    00011C 4110 D068            00068                      A),(FB_2,TSQLEN)     \n  _ 000142                             1412 SENDSCR1 DS    0H                   \n 347", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "550d9d590124-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n      Active Usings: ASMDEMO,R2,R3,R4,R7  DFHEIBLK,R11  DFHEISTG,R13\n \nInterTest for CICS then displays the menu on which you define the condition. For example, the following screen sets the\nconditional breakpoint at the offset you identified in the previous screen only if TSSWITCH is equal to 3. The entries are\nas follows:\n LEFT SIDE of  condition:\n                Data Name  r13.tsswitch\n                OPERATOR:  eq\n RIGHT SIDE of condition:\n                  Literal  3\n \n          CA-InterTest MONITORING COMMAND BUILDER - CONDITIONAL BREAKPOINT       \n  \n  Enter LEFT SIDE of condition (select one):                                     \n      Data Name r13.tsswitch  __________________________________________________\n      Special keywords:                 ______   Register # __    COBOL BLL # __\n  \n  Enter OPERATOR (EQ, NE, GT, LT, GE, LE):  eq    Length:  Left  ___    Right __\n  \n  Enter RIGHT SIDE of condition (select one):                                    \n      Data Name ________________________________________________________________\n      Special keywords:                 ______   Register # __    COBOL BLL # __\n      Literal 3_________________________________________________________________\n  \n  Optional offset:  Enter + - @ OR % followed by a value.                      \n      Left side  _________________________   Right side ________________________\n  \n  _ ENTER  S  to Drop monitoring on a true condition                            \n  \n  For location:                                                                 \n             000110 47F0 2142            00142  1384          B     SENDSCR     \n  \n     Use Help or documentation for use of special keywords", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "550d9d590124-1", "text": "Use Help or documentation for use of special keywords                      \n  PF1 Help       2            3 End        4 Return     5            6          \n  PF7            8            9           10           11           12\n \nTo process the condition, press Enter. InterTest for CICS generates the command syntax for the conditional breakpoint,\nand returns you to the Source Listing screen.\nRemove Conditional Breakpoints\nTo remove a conditional breakpoint, type X over the C and press Enter, as shown in the following screen.\n CA InterTest for CICS - PROTSYM FILE  SOURCE LISTING DISPLAY           \n COMMAND ===>                                                                   \n Program= ASMDEMO  Option # 9     Stmt #        Displacement=        Margin= 01 \n                                         Search= GETCOM                         \n ----------+--------------------------------------------------------------------\n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement             \n  _ 000100 4980 B018            00018  1380          CH    R8,EIBCALEN          \n  _ 000104 4740 218A            0018A  1381          BL    GETCOM               \n  _ 000108 957D B01A      0001A        1382          CLI   EIBAID,DFHENTER      \n 348", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "47076f299929-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  _ 00010C 4780 218E            0018E  1383          BE    CONTINUE             \n  x 000110 47F0 2142            00142  1384          B     SENDSCR1             \n  _ 000114 0024                        1386 TSQLEN   DC    H'36'                \n  _ 000116 0001                        1387 TSQITEM  DC    H'1'                 \n  _ 000118                             1389 WRITETSQ DS    0H                   \n  _ 000118 9240 D188      00188        1390          MVI   TSSWITCH,C' '        \n                                       1392 *        EXEC CICS WRITEQ TS        \n                                       1393 *              QUEUE(TSQNAME)       \n                                       1394 *              FROM(TSAREA)         \n                                       1395 *              LENGTH(TSQLEN)       \n                                       1396 *              MAIN                 \n                                       1397          DFHECALL =X'0A02E000080000 \n    00011C 4110 D068            00068                      A),(FB_2,TSQLEN)     \n  _ 000142                             1412 SENDSCR1 DS    0H                   \n      Active Usings: ASMDEMO,R2,R3,R4,R7  DFHEIBLK,R11  DFHEISTG,R13\n \nIn addition, you can remove the conditional breakpoint from the Status Display, as shown in the following steps:\n1.Press PF12 from any Source screen to display the Monitoring Status display.\n2.Scroll to the line where the conditional breakpoint (CBP) option is listed for the program.\n3.Type R next to the entry and press Enter.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "47076f299929-1", "text": "3.Type R next to the entry and press Enter.\n4.Return to the Source screen using PF3 End.\nRequest Breakpoints\nRequest  breakpoints are breakpoints that take effect before CICS commands and macros, and other program calls, such\nas calls to DL/I or DB2. With one specification, you can set breakpoints at all CICS commands or at specific commands,\nsuch as all REWRITE commands.\nUse request breakpoints to stop a program before the following commands:\n\u2022Every CICS command or macro\n\u2022Specific types of CICS commands, such as all File Control or Program Control commands\n\u2022Specific commands, such as all READ or WRITE commands\nSet Request Breakpoints\nTo set request breakpoints, perform the following steps:\n1.Select option 2 - Monitoring on the Primary Option Menu. InterTest for CICS displays the Monitoring Menu.\n2.Select option 1 - Programs. InterTest for CICS displays the Program Monitoring screen.\n --------------------  CA InterTest PROGRAM MONITORING  ------------------\n  COMMAND ===>                                                                   \n  \n    Type information and S to set or R to remove option(s) below.               \n  \n    Program  . . asmdemo_     Program name (or .ALL, .OPTIONS or generic)        \n    User ID  . .     ____     User (or .ANY) for whom the program is monitored   \n  \n    Option       Description                                            More:   +\n  _ Status       Display and/or remove monitoring options (S only)               \n  _ Monitor      Monitoring (R removes monitoring and all options previously set)\n  _ UBP          Unconditional breakpoints (specific program only)               \n  _ CBP          Conditional breakpoints (specific program only)                 \n 349", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2efe7610b974-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  s RBP          Breakpoints for CICS, DB2, DL/I or external CALL requests       \n  _ Stmt Trace   Statement tracing and data monitoring (COBOL only) \n  _ New copy     Fetch new copy of program and reset monitoring options (S only) \n  _ Commands     Indirect commands defined for a specific COBOL or PL/1 program \n  _ Replace      CICS resource name replacement options                          \n  _ Protect      Storage protection monitoring options                          \n  _ Special      Other options (storage allocation, file updating, etc.)         \n  _ Composite    Monitor multi-CSECT program's separately compiled components \n  \n  PF1 Help       2            3 End        4 Return     5            6           \n  PF7 Backward   8 Forward    9           10           11           12          \n \n3.In the Program field, type the name of the program for which you want to set request breakpoints.\n4.Type S to the left of the RBP (request breakpoints) option. Press Enter.\nThe Request Breakpoint Selection menu appears on which you specify the type of request breakpoint, such as: all CICS\ncommands, File Control, Task Control, and so on, as shown in the following panel:\n CA InterTest MONITORING COMMAND BUILDER - REQUEST BREAKPOINT SELECTION 13       \n               Set  one or more types of Request Breakpoints in:                 \n                                 PROG=ASMDEMO                                    \n  \n  _ ALL commands                    _ DL/I    _ DB2     _ CALLs                  \n  \n    _ Address, Assign,         _ Storage Control    _ BMS                        \n        Handles, Push, Pop     _ Program Control    _ Trace Control              \n    _ Terminal Control         _ Interval Control   _ Dump Control", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2efe7610b974-1", "text": "_ Terminal Control         _ Interval Control   _ Dump Control               \n    _ File Control             _ Task Control       _ Batch Data Interchange     \n    _ TD Control               _ Journal Control    _ Built-In Functions         \n    _ TS Control               _ Syncpoints         _ Sys Prog Functions         \n    _ Web access               _ Business Trans     _ 3270 Bridge                \n  \n    Enter 'n' to stop only every n'th time:                         ____         \n    Term ID (or .ANY or .NO) where breakpoints will take effect:    ____         \n    Term ID (or .ANY) that will receive the breakpoints:            ____         \n  \n    User ID (or .ANY) who will execute the program:                 ________     \n  \n  PF1 Help       2            3 End        4 Return     5            6           \n  PF7            8            9           10           11           12\n \nSubsequent menus prompt you for the specific command, such as all File Control commands, READ, WRITE, REWRITE.\nNOTE\nType X in front of each type of command for which you want to set request breakpoints.\nAfter setting your request breakpoints, you are returned to the Program Monitoring menu. Use PF3 to return to the\nprevious menu or Source display, use PF4 to go to the Primary Option Menu.\nRemove Request Breakpoints\nTo remove request breakpoints, perform the following steps:\n1.From the Source Listing display or breakpoint display, type STATUS on the Command line and press Enter. InterTest\nfor CICS displays the Monitoring Status, showing all options for the current program.\n 350", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cb8164c91e24-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n2.Type R to the left of the request breakpoint (RBP) option you want to remove and press Enter. InterTest for CICS\nplaces an asterisk to the left of the breakpoint to indicate that the command has been processed.\n3.Press PF3 to return to the Source Listing or Breakpoint display.\nBacktrace Facility\nWhen your program is at a breakpoint, it is useful to examine the backtrace. The backtrace shows the logic of the program\nand explains how execution reached this point.\nTo enter the Backtrace facility, press PF11 from the Source Listing Breakpoint screen, or, type BTRACE in the Command\nline and press Enter. InterTest for CICS positions the Backtrace Summary Screen at the last executed statement, which is\nthe current breakpoint location.\nTo view your program backtrace, statement-by-statement, press PF2 from the Backtrace Summary screen to access the\nSource Listing Backtrace.\nNOTE\nWhen you are using the Backtrace facility, the execution PF keys are disabled and are replaced with special\nforward and backward tracing PF keys,\nThe following screen shows the Backtrace Summary screen:\n InterTest  for CICS  - BACKTRACE SUMMARY  \n  \n Program= ASMDEMO                                      From 0001 To 0006 Of 0006 \n  \n Specify  S then ENTER to display Source Listing BACKTRACE                       \n ------------------------------------------------------------------------------- \n PFKS 1 Help      2 Backtrace 3 End        4            5 1st Stmt   6 Last Stmt \n      7 Backward  8 Forward   9           10           11 Prev Bloc 12 Next Bloc \n ------------------------------------------------------------------------------- \n  S Bkmk Stmt Block  \u00a6 Source Listing", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cb8164c91e24-1", "text": "------------------------------------------------------------------------------- \n  S Bkmk Stmt Block  \u00a6 Source Listing  \n  _ ____       +0 ... +18 \u00a6 +         STM   14,12,12(13)        SAVE CALLER'S R \n  _ ____      +22 ... +26 \u00a6 +         L     15,=V(DFHEAI0)                      \n  _ ____      +28 ... +9E \u00a6 +         ST    13,DFHEISA-DFHEISTG+4(,1)  CHAIN TO \n  _ ____      +A0 ... +CA \u00a6                                                     \n  _ ____      +CC ... +E4 \u00a6           CLI   TSSWITCH,DFHCLEAR       CLEAR KEY S \n  * ____     +166 ... BKPT \u00a6           LA    R5,S2LEN                LENGTH OF V  CAIN2988 First and Last\n Backtrace Stmt Block  \nRead the Backtrace Summary\nThe Backtrace Summary summarizes the program execution path using statement blocks. By tracing the execution path,\nblock by block, you can follow the flow of your program logic. The statement block column is located on the left side of the\nscreen and contains two columns of numbers:\n\u2022Statement numbers in the left column received control from a branch, command level CALL, a PERFORM, or a GOTO.\n\u2022Statement numbers in the right column issued the branch to the next statement identified.\nFrom the Backtrace Summary screen you can do the following tasks:\n\u2022Reposition the display to view statement-by-statement details of the program execution path by:\n 351", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9182f25d77eb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2013Pressing PF2\n\u2013Marking a statement block with S, and then pressing Enter\n\u2022For faster and easier navigation through the Backtrace Summary, assign a bookmark  that consists of one to four\ncharacters to one or more backtrace positions x\n\u2022Trace program execution using the following PF keys:\nPF5\n1st Stmt\nRepositions the Backtrace Summary screen to the first or oldest entry in the Backtrace.\nPF6 Last Stmt\nRepositions the Backtrace Summary screen to the last or newest entry in the Backtrace.\nPF7 Backward\nScrolls the Backtrace Summary screen backward (up) a full screen.\nPF8 Forward\nScrolls the Backtrace Summary screen forward (down) a full screen.\nPF11 Prev Bloc\nDisplays the previous statement block.\nPF12 Next Bloc\nDisplays the next statement block.\nAccess the Source Listing Backtrace\nTo switch to the Source Listing Backtrace and to view the backtrace statement-by-statement, press PF2, or key S next to\na statement block in the Select column of the Backtrace Summary to select a starting position and press Enter.\nThe following screen shows the Source Listing Backtrace:\n CA InterTest for CICS - PROTSYM FILE SOURCE LISTING BACKTRACE  \n COMMAND ===>                                                                   \n Program= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01  \n                                         Search=                                \n ========> Backtrace at +0016E  (00166 -> curr. executed     1 times) <=========\n      LOC  OBJECT CODE    ADDR1 ADDR2  STMT        SOURCE STATEMENT              \n  _ 00016A 4050 D1B0            001B0  1355          STH   R5,MSGLEN               A <===== FA20 D189 4AC0", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9182f25d77eb-1", "text": "00189 02AC0  1356          AP    TASKNUM,=P'1'  \n  _ 000174 F920 D189 4AC1 00189 02AC1  1357          CP    TASKNUM,=P'2'         \n  _ 00017A 4720 2300            00300  1358          BH    ENDMSG                \n  _ 00017E F920 D189 4AC0 00189 02AC0  1359          CP    TASKNUM,=P'1'         \n  _ 000184 4780 2256            00256  1360          BE    SENDSCR4              \n  _ 000188 47F0 2300            00300  1361          B     ENDMSG                \n  _ 00018C                             1363 RETURN   DS    0H                    \n                                       1364 *        EXEC CICS SEND FROM(OUTMSG  \n                                       1365          DFHECALL =X'04043000080000  \n    00018C 4110 D068            00068                      ),(FB_2,OUTLEN)       \n                                       1381 *        EXEC CICS SEND FROM(SCREEN  \n                                       1382          DFHECALL =X'04043000080000  \n    0001B2 4110 D068            00068                      2),(FB_2,MSGLEN)      \n                                       1398 *        EXEC CICS RETURN            \n                                       1399 *              TRANSID(EIBTRNID)     \n                                       1400 *              COMMAREA(TSAREA)      \n                                       1401 *              LENGTH(COMLEN)\n \n 352", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7debe57387e5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nRead the Source Listing Backtrace\nTo clearly show the program execution path statement-by-statement, source statements that were executed from the\ncurrent backtrace position are highlighted. However, when you specify a non-backtrace Source Listing option, or use PF7\nor PF8 to reposition the Source Listing Backtrace, the highlighting of executed statements is temporarily suspended until a\nbacktrace PF key is entered.\nWhen in source listing backtrace mode, the current backtrace position always appears on the line just above the first\nsource statement. This line displays as follows:\n ======>BACKTRACE AT #nnnnn (nnnnn -> nnnnn executed nnnnn times)<=====\n \nThe information in this line indicates the following:\n#nnnnn\nSpecifies the program statement or offset the backtrace is currently positioned at\nnnnnn -> nnnnn\nSpecifies the first and last number of the statement block\nnnnnn times\nSpecifies how many times a statement block was executed\nOn the Source Listing Backtrace, each relevant backtrace position is indicated in the listing by an arrow or a line:\n====>\nIndicates the first statement in a statement block\n<====\nIndicates the last statement in a statement block\n====\nIndicates all other statements within a statement block\nThe order of the statements reflects the program's execution path.The Source Listing Backtrace displays the source of the\nfollowing statements:\n\u2022The top statement is the first statement executed; the bottom statement is the most recently executed statement\nNavigate Through Program Execution\nYou can trace your program's execution path by using the following PF keys:\n\u2022Using PF5, PF9 and PF11 to trace execution backward\n\u2022Using PF6, PF10, PF12 to trace execution forward", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7debe57387e5-1", "text": "\u2022Using PF6, PF10, PF12 to trace execution forward\n\u2022Setting the Source Listing Profile Stepping Amount , and then using PF9 and PF10 to automatically trace the execution\nbackward or forward\nEnd a Source Listing Backtrace Session\nTo exit the Backtrace facility, press Clear or PF3. InterTest for CICS redisplays the Source Listing Breakpoint screen,\npositioned at the last breakpoint.\nTo toggle between the Source Listing Backtrace and the Backtrace Summary, press PF2.\nSet the Code Counting Coverage Option\nInterTest for CICS has many options for specialized testing needs. The code coverage option enables you to see the\nnumber of times an Assembler statement was executed.\n 353", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a4c79390491e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe initial setting for Code Counting is OFF, which is the default. However, you can use the Source Listing Profile screen\nto turn Code Counting ON or OFF again at any time after you have selected monitoring for a program.\nHow the counts are displayed or not displayed is handled by the primary line command COUNTS and its associated\nparameters.\nThis feature causes overhead during program monitoring and should be turned off as soon as it is not longer needed.\nTo change the setting for Code Coverage, perform the following steps:\n1.Type PROFILE on the command line and press Enter, or press PF4 to access the Profile screen from any Source\nListing Screen. The Code Counting= field shows the current setting.\n2.Overtype the current value with one of the following values:\nYES\nEnables code counting and turns on the COUNTER display feature\nNO\nRemoves the COUNTER display and stops the counting feature\n3.Press Enter to process the new setting(s) and to return to the Source Listing Display.\n4.The following screen shows the Code Coverage feature:\n CA InterTest for CICS - PROTSYM FILE SOURCE LISTING BREAKPOINT  \n COMMAND ===>                                                                   \n Program= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01  \n                                         Search=                                \n ---------+---------------| COUNTER |-------------------------------------------\n      LOC  OBJECT CODE    ADDR1 ADDR2  STMT        SOURCE STATEMENT              \n  _ 00003E 58B0 D05C      | 0000001 |  1212+         L     DFHEIBR,DFHEIBP       \n                     R:B  |         |  1213+         USING DFHEIBLK,DFHEIBR      \n                          |         |  1214+***********************************", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a4c79390491e-1", "text": "|         |  1214+***********************************  \n                          |         |  1215+*              END OF PROLOG CODE F  \n                          |         |  1216+***********************************  \n                          |         |  1218          PRINT NOGEN                 \n  _ 000042 4160 0232      | 0000001 |  1219          LA    R6,HDRLEN             \n  _ 000046 4060 23A2      | 0000001 |  1220          STH   R6,OUTLEN             \n  _ 00004A D203 D180 B008 | 0000001 |  1221          MVC   TSQTRAN,EIBTRNID      \n  _ 000050 D203 D184 B010 | 0000001 |  1222          MVC   TSQTERM,EIBTRMID      \n  _ 000056 956D B01A      | 0000001 |  1223          CLI   EIBAID,DFHCLEAR       \n  _ 00005A 4780 2300      | 0000001 |  1224          BE    ENDMSG                \n  _ 00005E 95F2 B01A      | 0000001 |  1225          CLI   EIBAID,DFHPF2         \n  _ 000062 4780 399C      | 0000001 |  1226          BE    EXPANDEM              \n  _ 000066 95C2 B01A      | 0000001 |  1227          CLI   EIBAID,DFHPF14        \n  _ 00006A 4780 399C      | 0000001 |  1228          BE    EXPANDEM", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a4c79390491e-2", "text": "_ 00006E 95F2 D188      | 0000001 |  1229          CLI   TSSWITCH,DFHPF2\n \nReplacement, Protection, and Special Options\nInterTest for CICS has many options for specialized testing needs. Just a few are explained here.  For a description of all\nmonitoring options, see Monitoring Menu Options.\nYou can set or remove options from the Monitoring Command Builder menus.\n 354", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6a2f537ff737-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReplacement Options\nReplacement options let you dynamically change the names of CICS resources such as programs, files, transient data\nqueues, and temporary storage.\nOne reason to use replacement options is to correct errors so you can continue testing without recompiling. For example,\nsuppose InterTest for CICS halts your program at an automatic breakpoint to prevent an AEIL abend caused by an\nincorrect file name. You can use the Replace File Name option to dynamically change the file name so testing can\ncontinue.\nAnother reason for using replacement options is to use different resources during testing than those hard coded in the\nprogram. For example, you can specify that the program use a test file rather than the production file named in the\nprogram.\nProtection Options\nWhen InterTest for CICS monitors a program, it prevents the program from modifying storage areas it does not own and\nissuing non-CICS instructions.\nProtection options let you override the InterTest for CICS default rules for modifying main storage, the CSA, and load\nmodules. The protection options, which are password protected, provide extra flexibility for special testing needs. These\noptions allow a program to do the following modifications:\n\u2022Modify any area of main storage\n\u2022Modify areas in the CSA or CWA\n\u2022Modify a load module\nThese options can also prevent a program from modifying specific areas of storage not normally protected.\nSpecial Options\nSpecial options alter the InterTest for CICS standard monitoring procedures and help you design customized testing\nscenarios.\nThe No File Updating option prevents a monitored program from updating files. This option is very useful when you test a\nprogram because your file data will be unchanged at the end of each program execution. The following then happens:\n\u2022You can repeatedly test a program without restoring your files.\n\u2022Many programs can use the same file without interfering with each other's work.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6a2f537ff737-1", "text": "\u2022Many programs can use the same file without interfering with each other's work.\n\u2022A test program can use a production file without affecting data integrity.\nOther options provide additional functions. For example:\n\u2022The FOL option lets InterTest for CICS continue monitoring even after a program branches directly to another program\n(wild branch ).\n\u2022The MXS option limits the amount of CICS storage a program can use.\n\u2022The MXR option limits the number of CICS requests a program can issue.\nComposite Module Testing\nComposite support lets you test all InterTest for CICS functions when you test composite modules . A composite module\nconsists of separately compiled modules link-edited in one load module. These modules may be written in different\nlanguages and compiled at different times. Composite support lets you test and debug a called subroutine as if it were a\nseparate program, and with full symbolic support.\nFor example, suppose an Assembler program has several subroutines, some written in Assembler, some written in\nCOBOL. You can test and debug any of the subroutines just as if it were a main program by setting breakpoints, setting\nmonitoring options, displaying the source listing, and displaying and modifying main and auxiliary storage.\n 355", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cf7a10a79068-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nThe following screens are for example purposes only.\nComposite module monitoring is initiated by specifying the COMPOSITE command in the Source Listing Display before\nmonitoring (PF5) is activated for the program.\n CA InterTest for CICS -  PROTSYM FILE SOURCE LISTING DISPLAY \n  COMMAND ===> COMPOSITE\n  Program= ASMPROG  Option # =     Stmt #       Displacement=        Margin= 01 \n                                          Search=                               \n  ----------+-------------------------------------------------------------------- \n                                                  EXTERNAL SYMBOL DICTIONARY \n     SYMBOL   TYPE  ID  ADDR  LENGTH  LD ID FLAGS \n               PC 0001 000000 000000         00 \n   _ ASMPROG   SD 0002 000000 002C32         00 \n   _ DFHEAI0   ER 0003 \n   _ DFHEI1    ER 0004 \n  \n       LOC  OBJECT CODE    ADDR1 ADDR2  STMT       SOURCE STATEMENT \n                                 00000     1 R0       EQU  0 \n                                 00001     2 R1       EQU  1 \n                                 00002     3 R2       EQU  2 \n                                 00003     4 R3       EQU  3 \n                                 00004     5 R4       EQU  4 \n                                 00005     6 R5       EQU  5 \n                                 00006     7 R6       EQU  6\n \nWhen you specify the COMPOSITE command, InterTest for CICS displays the link-edit information for the main program\nand its subroutines. Monitor-names are specified for the programs you want to test separately. You can change this\ninformation online.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cf7a10a79068-1", "text": "information online.\n        CA InterTest for CICS - Composite Support Builder                   \n  COMMAND ===>                                                      SCROLL: PAGE\n  Define composite support for ASMPROG  and press PF5.        Row 00001 of 00003 \n  \n  \n  * *          *          *        *        *           *                        \n  _ Link name  Monitor    Offset   Length   Language    Comments                 \n  S ASMPROG    ASMPROG        28      66C   HLASM  6.0                          \n  S ASMSUB     ASMSUB        698      448   IBMCOB 4.2                          \n  S COBOLSUB   COBOLSUB     1640      16C   HLASM  6.0                \n  \n  \n  PF1 Help       2            3 End        4            5 Process    6 RFind     \n  PF7 Backward   8 Forward    9           10           11           12           \n \nPress PF5 to enable composite module monitoring.\nDump Analysis with SymDump  for CICS\nSymDump  for CICS, the  InterTest for CICS optional symbolic dump facility for z/OS users,  is a powerful online tool that\nautomatically pinpoints the source statement responsible for an abend. SymDump  can be accessed using the ITST\nPrimary Option Menu, Option 5 - Dump analysis.\n 356", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "04b6a9ed7288-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSymDump  for CICS was designed to complement InterTest for CICS, especially in production regions where programs\nare not usually monitored. Working together with InterTest for CICS, SymDump  for CICS lets you bring a dump back to\nlife. Familiar Source Listing screens and other facilities, such as the ability to view and modify main and auxiliary storage,\nmake it easy to resolve application dumps.\nWith SymDump  for CICS, you can perform the following tasks:\n\u2022Analyze dumps symbolically online, using InterTest for CICS source code listings\n\u2022Resolve CICS production dumps from any region; for example, debug production abends from your test region\n\u2022Manage your dump data set by selectively retaining the dumps you want to view and print, and discarding ones you do\nnot need\nWhen you use SymDump  for CICS to view a dump, you can display the following formatted displays:\n\u2022InterTest for CICS Source Breakpoint at the instruction that triggered the abend\n\u2022Abend code description and probable cause\n\u2022Last 3270 screen sent to the terminal\n\u2022Program call trace (program call sequence and registers)\n\u2022CICS trace table entries, complete or filtered\n\u2022Register contents\n\u2022Lists of files and programs referenced by the transaction\n\u2022Formatted System and Data areas\nExample\nSuppose a program not being monitored by InterTest for CICS abended with an ASRA. With SymDump  for CICS, you\ncan display the breakpoint at the statement that triggered the abend even though InterTest for CICS was not active in the\nregion when the abend occurred.\n CA InterTest for CICS - PROTSYM FILE SOURCE LISTING DUMP ANALYSIS \n COMMAND ===>                                                                    \n Program= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "04b6a9ed7288-1", "text": "Search=                                 \n OPTS 1 1st CSECT 2           3            4            5 Macro Cat  6 Xref      \n      7 Literals  8 Err msgs  9 Srch fwd  10 Srch bwd  11           12 Bkpt opts \n PFKS 1 Help      2           3 End        4 Profile    5 Monitor    6 Menu      \n      7 Backward  8 Forward   9           10           11 Backtrace 12 Status    \n ----------+-------------------------------------------------------------------- \n      LOC  OBJECT CODE    ADDR1 ADDR2  STMT        SOURCE STATEMENT              \n  _ 00016A 4050 D128            00128   937          STH   R5,MSGLEN             \n  A 00016E FA20 D101 4AC0 00101 02AC0   ==>          AP    TASKNUM,=P'1'         \n      ==>                                                                        \n      ==> CODE: ASRA                                                             \n      ==>                                                                        \n      ==>      Press PF1 for a detailed description.                          \n      ==>                                                                        \n  _ 000174 F920 D101 4AC1 00101 02AC1   939          CP    TASKNUM,=P'2'         \n  _ 00017A 4720 2300            00300   940          BH    ENDMSG                \n  _ 00017E F920 D101 4AC0 00101 02AC0   941          CP    TASKNUM,=P'1'         \n  _ 000184 4780 2256            00256   942          BE    SENDSCR4              \n  _ 000188 47F0 2300            00300   943          B     ENDMSG", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "04b6a9ed7288-2", "text": "_ 00018C                              945 RETURN   DS    0H                    \n                                        946 *        EXEC CICS SEND FROM(OUTMS  \n \n 357", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7c5ac6ce4708-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNow you can use InterTest for CICS to solve the problem. In this example, you might want to display the contents of\nTASKNUM. Or, you might want to inspect the file or look at the formatted trace table. InterTest for CICS provides all the\ntools you need to diagnose and resolve the dump.\nAssembler Advanced Demo Session\nThis article describes some of the advanced features of InterTest.\nInterTest for CICS has features that are designed to meet all your testing needs. The demo session in the second article\nillustrated the basics of working with InterTest for CICS.\nOnly a few InterTest for CICS features are demonstrated in this demo session. For more information, see CICS\nDebugging or refer to the Help facility.\nThis article consists of the following independent sections. Each section details a different advanced InterTest for CICS\nfeature.\nOption 01\nReplace a file name.\nOption 02\nLimit the number of CICS requests issued by a program. Limit the amount of storage that is obtained by a\nprogram.\nOption 03\nPrevent a program from updating a file.Use request breakpoints and the FILE facility.\nStartup\nPerform the following steps before initiating the advanced demo session:\n1.Turn on the Source Listing Breakpoint facility\n2.Set two unconditional breakpoints\n3.Set request breakpoints at all CICS REWRITE commands\n4.Execute program ASMDEMO\n5.Access the Options Menu\nTurn on the Source Listing Breakpoint Facility\nFirst, bring up the Source Listing display for the ASMDEMO program. This step was covered in the basic demo using\nITST Option 1 - Source. Then select the program ASMDEMO from the Source Selection list. The following steps provide a\nquick method to display a program source.\n1.Sign on to CICS. On a clear screen, enter the following:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7c5ac6ce4708-1", "text": "1.Sign on to CICS. On a clear screen, enter the following:\nlist=asmdemo\n2.Press Enter.\nThe Source Listing Display screen appears.\n CA InterTest for CICS - PROTSYM FILE  SOURCE LISTING DISPLAY           \n COMMAND ===>                                                                   \n Program= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01 \n                                         Search=                                \n ----------+--------------------------------------------------------------------\n      Active Usings: None                                                       \n  \n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement             \n 358", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8dbeabc1ef7f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                          00000           1 R0       EQU   0                    \n                          00001           2 R1       EQU   1                    \n                          00002           3 R2       EQU   2                    \n                          00003           4 R3       EQU   3                    \n                          00004           5 R4       EQU   4                    \n                          00005           6 R5       EQU   5                    \n                          00006           7 R6       EQU   6                    \n                          00007           8 R7       EQU   7                    \n                          00008           9 R8       EQU   8                    \n                          00009          10 R9       EQU   9                    \n                          0000A          11 R10      EQU   10                   \n                          0000B          12 R11      EQU   11                   \n                          0000C          13 R12      EQU   12                   \n                          0000D          14 R13      EQU   13                   \n                          0000E          15 R14      EQU   14                   \n                          0000F          16 R15      EQU   15\n \nWhen you are debugging an Assembler program, it is sometimes easier to change the margins to view more of the source\ncode.\n1.Enter MARGIN 28 on the command line and press Enter.\nor\n2.Tab to the Margin field.\n3.Type 28.\n4.Press Enter.\nInterTest for CICS adjusts the margin so that the display starts with column 28, as shown next.\n CA InterTest for CICS  - PROTSYM FILE  SOURCE LISTING DISPLAY            \n COMMAND ===>", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8dbeabc1ef7f-1", "text": "COMMAND ===>                                                                    \n Program= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 28  \n                                         Search=                                 \n ----------+-------------------------------------------------------------------- \n  \n  \n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n               1 R0       EQU   0                                                \n               2 R1       EQU   1                                                \n               3 R2       EQU   2                       BASE REG                 \n               4 R3       EQU   3                       BASE REG                 \n               5 R4       EQU   4                                                \n               6 R5       EQU   5                                                \n               7 R6       EQU   6                                                \n               8 R7       EQU   7                                                \n               9 R8       EQU   8                                                \n              10 R9       EQU   9                       COMMAREA REG             \n              11 R10      EQU   10                                               \n              12 R11      EQU   11                      EIB REG                  \n              13 R12      EQU   12                                               \n              14 R13      EQU   13                      DSA REG                  \n              15 R14      EQU   14                                               \n              16 R15      EQU   15\n \n 359", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7a2954961b9e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSet Unconditional Breakpoints\nNext, set two unconditional breakpoints. Setting unconditional breakpoints lets you halt the program so you can set\noptions and check the contents of variables.\nBegin by searching for the Assembler label NUPDTE.\n1.Perform one of the following steps:\n\u2013Type L NUPDTE  on the command line and press Enter.\n\u2013Tab to the Search = field, type nupdte , and press Enter.\n CA InterTest for CICS - PROTSYM FILE  SOURCE LISTING DISPLAY            \n COMMAND ===>                                                                    \n Program= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 28  \n                                         Search= nupdte                          \n ----------+-------------------------------------------------------------------- \n  \n  \n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n               1 R0       EQU   0                                                \n               2 R1       EQU   1                                                \n               3 R2       EQU   2                       BASE REG                 \n               4 R3       EQU   3                       BASE REG                 \n               5 R4       EQU   4                                                \n               6 R5       EQU   5                                                \n               7 R6       EQU   6                                                \n               8 R7       EQU   7                                                \n               9 R8       EQU   8                                                \n              10 R9       EQU   9                       COMMAREA REG             \n              11 R10      EQU   10                                               \n              12 R11      EQU   11                      EIB REG                  \n              13 R12      EQU   12                                               \n              14 R13      EQU   13                      DSA REG                  \n              15 R14      EQU   14", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7a2954961b9e-1", "text": "15 R14      EQU   14                                               \n              16 R15      EQU   15                                             \n \nInterTest for CICS displays the NUPDTE label.\n2.Set an unconditional breakpoint at instruction B SENDMP00:\na.Tab to the B SENDMP00 instruction.\nb.Type U to the left of the instruction, and press Enter. This command sets a breakpoint that stops before  the\ninstruction is executed. You could also type ) to set a breakpoint that stops after the instruction is executed.\n CA InterTest for CICS  - PROTSYM FILE  SOURCE LISTING DISPLAY            \n COMMAND ===>                                                                    \n Program= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 28  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n     00068                      REA),(FB_2,RECLEN)                               \n  \n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n  _ 001FA4  2653 NUPDTE   DS    0H                                               \n            2654 *        EXEC CICS START TRANSID(CNTLTRAN)                      \n            2655 *              FROM(NUPOFF) LENGTH(NUPOLEN) REQID(=X'9999')     \n            2656          DFHECALL =X'1008F8000800005400',(___4,=PL4'0'),(CHA8,  \n     00068                      ,(CHA4,CNTLTRAN),(______RF,NUPOFF),(FB_2,NUPOLEN)\n 360", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "58032d655887-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  u 001FD2  2672          B     SENDMP00                                         \n  _ 001FD6  2674 READATA  DS    0H                                               \n            2675 *        EXEC CICS HANDLE CONDITION                             \n            2676 *             DSIDERR                                           \n            2677 *             NOTOPEN (NOPEN)                                   \n            2678          DFHECALL =X'0204800008130C000000000000000000000000000  \n     00068                      ,NOPEN)                                          \n  _ 001FF0  2689          MVC   RECKEY,=CL10'0000000000'                         \n            2690 *        EXEC CICS STARTBR  RIDFLD(RECKEY) DATASET('PROTH')     \n            2691          DFHECALL =X'060CB000080020A000',(CHA8,=CL8'PROTH'),,(  \n     00068                      )),(______RF,RECKEY)\n \nInterTest for CICS sets the breakpoint.\nNow you are going to set a second unconditional breakpoint in ASMDEMO.\n1.Perform one of the following steps:\n\u2013Type L LOOPRTN  on the command line and press Enter.\n\u2013Tab to the Search = field, type looprtn , and press Enter.\n CA InterTest for CICS  - PROTSYM FILE  SOURCE LISTING DISPLAY            \n COMMAND ===>                                                                    \n Program= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 28  \n                                         Search= looprtn                         \n ----------+--------------------------------------------------------------------                       \n     \n \n2.The LOOPRTN label appears.\n3.Set an unconditional breakpoint at the LOOPRTN label:\na.Tab to LOOPRTN.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "58032d655887-1", "text": "3.Set an unconditional breakpoint at the LOOPRTN label:\na.Tab to LOOPRTN.\nb.Type U to the left of that label.\nc.Press Enter.\n CA InterTest for CICS  - PROTSYM FILE  SOURCE LISTING DISPLAY            \n COMMAND ===>                                                                    \n Program= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 28  \n                                         Search=                                 \n ----------+-------------------------------------------------------------------- \n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n  _ 00213E  2818          B     SENDMP00                                         \n  u 002142  2820 LOOPRTN  DS    0H                                               \n  _ 002142  2821          ZAP   LOOPCTR,=P'0'                                    \n            2822 *        PRINT NOGEN                                            \n  _ 002148  2824 CICSLOOP DS    0H                                               \n            2825 *        EXEC CICS ASKTIME                                      \n  _ 002148  2826          DFHECALL =X'100200000800001300'                        \n  _ 00215E  2836          CP    LOOPCTR,=P'+50'                                  \n  _ 002164  2837          BE    MXSOPTS                                          \n  _ 002168  2838          AP    LOOPCTR,=P'+1'                                   \n  _ 00216E  2839          B     CICSLOOP                                         \n  _ 002172  2841 MXSOPTS  DS    0H                                               \n            2842 *        EXEC CICS HANDLE CONDITION                             \n            2843 *             NOSTG(NOSTORG)                                    \n            2844          DFHECALL =X'02048000082A00000000000000000000000000000  \n 361", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8177121a70c3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n     00068                      ,NOSTORG)                                        \n  _ 00218C  2855          ZAP   LOOPCTR,=P'0'\n \nInterTest for CICS sets the unconditional breakpoint.\nSet Request Breakpoints\nNow you are going to set request breakpoints to halt ASMDEMO prior to all CICS REWRITE commands.\nYou can set request breakpoints to halt a program before CICS commands and macros and other calls, such as calls to\nDL/I or DB2. The Request Breakpoint Selection menu lets you select specific types of commands and macros at which to\nset request breakpoints.\nYou can set request breakpoints prior to all CICS commands, or prior to specific commands, such as File Control or\nProgram Control commands. Request breakpoints make it easy for you to halt your program at various points so you can\ncheck program processing. For example, you can halt the program before every READ command, single-step through the\nread instructions, and then check main storage to make sure that the program has read the correct record.\nFor option 03 of the advanced demo, you must set request breakpoints at all File Control REWRITE commands in\nASMDEMO. To do perform this step, use the ITST Primary Option Menus for monitoring, as discussed next.\n1.Enter the RBP command on the command line.\n2.Press Enter to continue.\nThe Request Breakpoint Selection menu appears. Specify the type of request breakpoint, such as all CICS\ncommands, File Control, Task Control, and so on.\n      CA InterTest MONITORING COMMAND BUILDER - REQUEST BREAKPOINT SELECTION  13\n  \n               Set  one or more types of Request Breakpoints in:                 \n                                 PROG=ASMDEMO                                    \n  \n  _ ALL commands                    _ DL/I    _ DB2     _ CALLs", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8177121a70c3-1", "text": "_ ALL commands                    _ DL/I    _ DB2     _ CALLs                  \n  \n    _ Address, Assign,         _ Storage Control    _ BMS                        \n        Handles, Push, Pop     _ Program Control    _ Trace Control              \n    _ Terminal Control         _ Interval Control   _ Dump Control               \n    s File Control             _ Task Control       _ Batch Data Interchange     \n    _ TD Control               _ Journal Control    _ Built-In Functions         \n    _ TS Control               _ Syncpoints         _ Sys Prog Functions         \n      Web access                 Business Trans       3270 Bridge              \n  \n    Enter 'n' to stop only every n'th time:                         ____         \n    Term ID (or .ANY or .NO) where breakpoints will take effect:    ____         \n    Term ID (or .ANY) that will receive the breakpoints:            ____         \n  \n    User ID (or .ANY) who will execute the program:                 ________     \n  \n  \n  PF1 Help       2            3 End        4 Return     5            6           \n  PF7            8            9           10           11           12          \n \n3.Tab to the File Control field and type an s.\n4.Press the Enter key.\n 362", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8e6759d3e5ed-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe File Control Request Breakpoint Selection menu appears. You use this menu to select the specific File Control\ncommands where you want to set request breakpoints. In this case, select REWRITE to halt the program prior to each\nFile Control REWRITE command.\n       CA InterTest MONITORING COMMAND BUILDER - REQUEST BREAKPOINT SELECTION  \n  \n             Set  one or more types of File Control COMMANDS IN:               \n                                 PROG=ASMDEMO                                  \n  \n               _ All commands                                                  \n  \n                     _ READ                                                    \n                     _ WRITE                                                   \n                     s REWRITE                                                 \n                     _ DELETE                                                  \n                     _ UNLOCK                                                 \n                     _ STARTBR                                                 \n                     _ READNEXT                                                \n                     _ READPREV                                                \n                     _ ENDBR                                                   \n                     _ RESETBR                                                 \n  \n               Enter 'n' to stop only every n'th time   ____                   \n  \n  \n  \n  \n  PF1 Help       2            3 End        4 Return     5            6         \n  PF7            8            9           10           11           12     \n \n5.Tab to the REWRITE command field.\n6.Type an s and press Enter.\nInterTest for CICS sets request breakpoints prior to each File Control REWRITE command in the demo program and\nredisplays the Source Listing screen.\nCheck the Monitoring Status Display\nBefore you continue, check the Monitoring Status display for the program ASMDEMO. You should see the options that\nyou set for the program. These options are required to complete the Demo Options discussed later.\n1.Enter STATUS on the command line and press Enter, or press PF12 to display the Monitoring Status screen.\n CA InterTest for CICS  - PROTSYM FILE  SOURCE LISTING DISPLAY            \n COMMAND ===> status", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8e6759d3e5ed-1", "text": "COMMAND ===> status                                                            \n Program= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 28  \n                                         Search=                                 \n ----------+-------------------------------------------------------------------- \n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n  _ 00213E  2818          B     SENDMP00                                         \n  u 002142  2820 LOOPRTN  DS    0H                                               \n  _ 002142  2821          ZAP   LOOPCTR,=P'0'                                    \n            2822 *        PRINT NOGEN                                            \n  _ 002148  2824 CICSLOOP DS    0H                                               \n            2825 *        EXEC CICS ASKTIME                                      \n  _ 002148  2826          DFHECALL =X'100200000800001300'                        \n 363", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5f3e035272b6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  _ 00215E  2836          CP    LOOPCTR,=P'+50'                                  \n  _ 002164  2837          BE    MXSOPTS                                          \n  _ 002168  2838          AP    LOOPCTR,=P'+1'                                   \n  _ 00216E  2839          B     CICSLOOP                                         \n  _ 002172  2841 MXSOPTS  DS    0H                                               \n            2842 *        EXEC CICS HANDLE CONDITION                             \n            2843 *             NOSTG(NOSTORG)                                    \n            2844          DFHECALL =X'02048000082A00000000000000000000000000000  \n     00068                      ,NOSTORG)                                        \n  _ 00218C  2855          ZAP   LOOPCTR,=P'0'\n \nThe Monitoring Status display for ASMDEMO should show the three breakpoints that are needed to perform the Demo\nSession Options; the Request Breakpoint (RBP) at all REWRITE commands, and the two Unconditional Breakpoints\n(UBPs).\n  ---------------  CA InterTest for CICS  MONITORING STATUS  -------------\n  COMMAND ===>                                                                   \n  \n    Type + to expand or - collapse option levels displayed below,                \n           or R to remove option(s).                                             \n  \n      Option     Description                Attributes                           \n  _ - ASMDEMO    Program monitor entry      Assembler                            \n  _ - |-.ANY     User monitoring options    Active                               \n        |        Symbolic listing file      PROTSYM                              \n  _ -   |-RBP    Request breakpoint(s)      REWRITE                              \n        |        Option ID                  EBAA2CEE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5f3e035272b6-1", "text": "|        Option ID                  EBAA2CEE                             \n        |        From, to terminals         U015, U015                           \n  _ -   |-UBP    Unconditional breakpoint   'LOOPRTN'                            \n        |        Option ID                  CDBE6584                             \n        |        From, to terminals         U015, U015                           \n  _ -   |-UBP    Unconditional breakpoint   Offset=00001FD2                      \n        |        Option ID                  6DF90E49                             \n        |        From, to terminals         U015, U015                           \n  _     |-SLB    Source listing breakpoints U015                                 \n  \n  \n  PF1 Help       2 Refresh    3 End        4 Return     5 Collapse   6 Expand    \n  PF7 Backward   8 Forward    9           10           11           12          \n \n2.Press PF3 to exit back to the Program Monitoring menu.\n3.Type =X in the Command field to exit the menus, then PF3 to exit Source Listing.\nExiting the menus and Source Listing returns you to CICS, where you can begin executing the ASMDEMO program.\nExecute the Demo Program\nNow you can execute ASMDEMO to perform the advanced options.\n1.On a clear CICS screen, type dema .\n2.Press Enter.\nASMDEMO displays the following Welcome Screen.\n ******************************************************************************\n ******************************************************************************\n *****                                                                    *****\n 364", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e9fe5d4e1870-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n *****                          Welcome to the                            *****\n *****                   CA InterTest Demo Session                        *****\n *****                                                                    *****\n *****                                                                    *****\n *****              Before proceeding, please have on hand the            *****\n *****              guide which accompanies the Demo Session.             *****\n *****                                                                    *****\n *****                                                                    *****\n *****     Please make sure that the program ASMDEMO is monitored by      *****\n *****     CA InterTest. This program will abend if not being monitored.  *****\n *****                                                                    *****\n *****     To turn the monitor on, press CLEAR and follow the steps       *****\n *****     outlined in the documentation.                                 *****\n *****                                                                    *****\n *****     If the monitor is already on, press ENTER to begin the         *****\n *****     Basic Demo Session or PF2 to go to the Options Menu.           *****\n *****                                                                    *****\n ******************************************************************************\n ******************************************************************************\n \nFrom the Welcome Screen, you can access the Options Menu.\n3.Press PF2 to start the demo options session.\nASMDEMO displays the Demo Session Options Menu.\n **********************************************************************\n ****                                                              ****\n ****                 CA InterTest Demo Session                    ****\n ****                         Options Menu                         ****\n ****                                                              ****\n **********************************************************************\n  \n      01  Replace file control ID                                      \n      02  Limit CICS storage and requests                              \n      03  No file updating                                             \n  \n  \n  \n                                   Type request:  01                      \n  \n           Press ENTER to continue or CLEAR to terminate                 \n \nEach of the options on the Options Menu is described in detail in the sections that follow.\nOption 01 Replace a File Control ID\nThis section of the demo session shows how to replace a File Control ID. Program ASMDEMO is attempts to read and\ndisplay a record, but the file name that is specified in the program is incorrect.\nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e9fe5d4e1870-1", "text": "display a record, but the file name that is specified in the program is incorrect.\nNOTE\nBefore you begin this section, complete the steps outlined in the Start-Up section (unless you did so earlier). The\nOptions Menu should be displayed.\n1.Select Option 01 to request Replace File Control ID and press Enter.\nASMDEMO displays a screen that describes what occurs in this part of the demo.\n 365", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a67a57ad4fe7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n **********************************************************************   \n ****                                                              ****   \n ****                 CA InterTest Demo Session                    ****   \n ****                Replace File Control ID Option                ****   \n ****                                                              ****   \n **********************************************************************  \n  \n The program attempts to read file PROTH. Because the file name has been  \n incorrectly specified, this would cause a DSIDERR condition which would  \n result in an AEIL abend. Instead, here is what will happen:             \n  \n 1. CA InterTest halts the program at an automatic breakpoint.           \n 2. You set the Replace File Control option to change the file name      \n    without recompiling.                                                 \n 3. You re-execute the program from the point at which it first tried    \n    to read the file.                                                    \n  \n  \n When this section of the demo completes, you will return to the        \n Options Menu.                                                          \n  \n          Press ENTER to continue or CLEAR to terminate               \n \n2.Press Enter.\nASMDEMO halts at an automatic breakpoint.\nPrevent an AEIL Abend\nAn example of the next screen follows. InterTest for CICS halted ASMDEMO at an automatic breakpoint (note the A)\nbefore an AEIL abend could occur. The abend would have resulted from the EXEC CICS STARTBR command. InterTest\nfor CICS highlighted the MVC instruction, the first instruction after the EXEC CICS STARTBR command.\nNOTE\nIf the screen you see does not match the following example, then someone else is probably trying to perform\nthis part of the demo session. In this case, press Enter to continue with the demo session or Clear to end the\nsession. You can return to the Replace File Control ID option later.\n CA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a67a57ad4fe7-1", "text": "COMMAND ===>                                                                    \n Program= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 28  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n     00068                      )),(______RF,RECKEY)                             \n   A 00201E   ==>          MVC   UNPCK,=CL4'    '                                       ==>                 \n                                                             ==> CICS abend intercepted. Abend code = AEIL.  \n EXEC CICS request was           ==> STARTBR. Now stopped AFTER the CALL.                                    \n     ==>                                                                              ==>      Press PF1 for a\n detailed description.                                   ==>                                                 \n                        \n            2707 *        EXEC CICS READNEXT SET(R6) RIDFLD(RECKEY)              \n            2708 *              LENGTH(RECLEN) DATASET('PROTH')                  \n            2709          DFHECALL =X'060EF400080100B000',(CHA8,=CL8'PROTH'),(P  \n     00068                      6),(FB_2__RF,RECLEN),(______RF,RECKEY),,(FB_2,=A(\n 366", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b8072fda720f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  _ 00205C  2729 MOVEREC  DS\n  \n  _ 00205C  2730          LH    R14,RECLEN                                       \n  _ 002060  2731          CVD   R14,CVDAREA                                      \n  _ 002064  2732          UNPK  UNPCK,CVDAREA+4(4)\n \nPage backward to see the data set name in the EXEC CICS STARTBR command.\n1.Press PF7.\nThe following screen appears.\n CA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \n COMMAND ===>                                                                    \n Program= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 28  \n                                         Search=                                 \n ----------+-------------------------------------------------------------------- \n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n            2638          DFHECALL =X'0606E0000800004000',(CHA8,CKPTNAME),(____  \n     00068                      REA),(FB_2,RECLEN)                               \n  _ 001FA4  2653 NUPDTE   DS    0H                                               \n            2654 *        EXEC CICS START TRANSID(CNTLTRAN)                      \n            2655 *              FROM(NUPOFF) LENGTH(NUPOLEN) REQID(=X'9999')     \n            2656          DFHECALL =X'1008F8000800005400',(___4,=PL4'0'),(CHA8,  \n     00068                      ,(CHA4,CNTLTRAN),(______RF,NUPOFF),(FB_2,NUPOLEN)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b8072fda720f-1", "text": "U 001FD2  2672          B     SENDMP00                                         \n  _ 001FD6  2674 READATA  DS    0H                                               \n            2675 *        EXEC CICS HANDLE CONDITION                             \n            2676 *             DSIDERR                                           \n            2677 *             NOTOPEN (NOPEN)                                   \n            2678          DFHECALL =X'0204800008130C000000000000000000000000000  \n     00068                      ,NOPEN)                                          \n  _ 001FF0  2689          MVC   RECKEY,=CL10'0000000000'                         \n            2690 *        EXEC CICS STARTBR  RIDFLD(RECKEY) DATASET('PROTH')     \n            2691          DFHECALL =X'060CB000080020A000',(CHA8,=CL8'PROTH'),,(  \n     00068                      )),(______RF,RECKEY)\n \nThe abend occurred because the data set name PROTH is wrong. The correct name is PROTHLF.\nChange the File Name\nInterTest for CICS lets you dynamically change an incorrect file name in the middle of your test session. This feature lets\nyou continue testing without recompiling your program. In this case, you can correct a simple typo in program ASMDEMO\nwithout interrupting your demo session.\nFollow these steps:\n1.Type RO on the command line.\n2.Press Enter.\nThe Replacement Options menu appears.\nThe Set Replacement Options menu lets you dynamically change a program name, file name, transient data queue\nname, or temporary storage ID. You can set multiple replacement options at the same time, for example, you can\nchange both a file name and a program name.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b8072fda720f-2", "text": "change both a file name and a program name.\nIn this case, you want to change a file name.\n3.Tab to the Replace file name field.\n 367", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b317a52f1ab3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n4.Specify the incorrect file name (proth) in the first column and the correct file name (prothlf) in the second column, as\nthe following screen shows.\n5.Press Enter.\n             CA InterTest MONITORING COMMAND BUILDER - REPLACEMENT OPTIONS     20\n  \n      SET one or more options to replace one CICS resource name with another in: \n                                 PROG=ASMDEMO                                    \n  \n  \n       Replace program name:         ________   with   ________                  \n       Replace file name:            proth___   with   prothlf__                  \n       Replace TD queue name:        ____       with   ____                      \n       TS selection mask:            ____________________________________        \n       TS replacement mask:          ____________________________________        \n  \n       Limit monitoring to your terminal - '*'  or TERMID:       ____            \n       User ID (or .ANY) who will execute the program:           ________        \n  \n  \n  \n  PF1 Help       2            3 End        4 Return     5            6           \n  PF7            8            9           10           11           12          \n \nInterTest for CICS processes the requested replacement option and displays the Program Monitoring menu. While\nInterTest for CICS replaces the incorrect file name during execution, the source listing is unchanged.\n6.Type PF4 until you return to the breakpoint.\nThe breakpoint for ASMDEMO appears.\nResume Execution\nTo resume execution of ASMDEMO at the MVC instruction prior to the EXEC CICS STARTBR command, type G to the left\nof that instruction.\n1.Tab the cursor to the MVC RECKEY,=CL10'0000000000' instruction.\n2.Type G to the left of the instruction.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b317a52f1ab3-1", "text": "2.Type G to the left of the instruction.\n3.Press Enter to resume task execution.\n CA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \n COMMAND ===>                                                                    \n Program= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 28  \n                                         Search=                                 \n ----------+-------------------------------------------------------------------- \n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n            2638          DFHECALL =X'0606E0000800004000',(CHA8,CKPTNAME),(____  \n     00068                      REA),(FB_2,RECLEN)                               \n  _ 001FA4  2653 NUPDTE   DS    0H                                               \n            2654 *        EXEC CICS START TRANSID(CNTLTRAN)                      \n            2655 *              FROM(NUPOFF) LENGTH(NUPOLEN) REQID(=X'9999')     \n            2656          DFHECALL =X'1008F8000800005400',(___4,=PL4'0'),(CHA8,  \n     00068                      ,(CHA4,CNTLTRAN),(______RF,NUPOFF),(FB_2,NUPOLEN)\n  U 001FD2  2672          B     SENDMP00                                         \n  _ 001FD6  2674 READATA  DS    0H                                               \n            2675 *        EXEC CICS HANDLE CONDITION                             \n            2676 *             DSIDERR                                           \n 368", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f2a67bf9f9b8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n            2677 *             NOTOPEN (NOPEN)                                   \n            2678          DFHECALL =X'0204800008130C000000000000000000000000000  \n     00068                      ,NOPEN)                                          \n  g 001FF0  2689          MVC   RECKEY,=CL10'0000000000'                         \n            2690 *        EXEC CICS STARTBR  RIDFLD(RECKEY) DATASET('PROTH')     \n            2691          DFHECALL =X'060CB000080020A000',(CHA8,=CL8'PROTH'),,(  \n     00068                      )),(______RF,RECKEY)\n \nNOTE\nTo allow ASMDEMO to read the correct file, you must back up to the instruction before the EXEC CICS\nSTARTBR command with the incorrect file name.\nASMDEMO successfully completes execution and displays the record that it read.\nASMDEMO Displays the Record\nProgram ASMDEMO succeeded in reading a record from file PROTHLF, which is the InterTest for CICS Help file.\nASMDEMO displays the first record in that file.\n      **********************************************************************     \n      ****                                                              ****     \n      ****                 CA InterTest Demo Session                    ****     \n      ****             Replace File Control Identifications             ****     \n      ****                                                              ****     \n      **********************************************************************     \n  \n  \n  \n           Record retrieved: * 0000000000    VE0301CA InterTest HELP Fa *        \n                             * cility Master Menu                       *        \n           Record length = 0960                                                  \n  \n  \n  \n           You have now successfully utilized the REPLACE option                 \n  \n  \n  \n          Press ENTER to continue or CLEAR to terminate", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f2a67bf9f9b8-1", "text": "Press ENTER to continue or CLEAR to terminate                         \n  \n \nReplacing the incorrect file name in program ASMDEMO allowed you to continue testing that program without recompiling\nit. If one of your programs had an incorrect file name, you would eventually have to correct the file name in the original\nprogram and recompile it.\nIn this case, the error was caused by a simple typo. However, the Replacement Options are useful in many situations. For\nexample, you can dynamically change a file name to test a program with a different file. This allows you to use a test file\nwithout altering the name of the production file coded in the program. You can also change a program name or transient\ndata queue name to test a program or queue other than the ones that are hard-coded.\nYou have now completed the Replace File Control ID section of the demo session. Press Enter to continue the test\nsession, or Clear to end the session.\n 369", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8278c582ea43-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nOption 02 Limit CICS Storage and Requests\nThis section of the demo session shows how to limit CICS main storage and CICS requests. Two different InterTest for\nCICS options are detailed in this part of the demo:\n\u2022The MXS option limits the amount of main storage that is obtained by a task. This option is useful in detecting program\nerrors that cause a task to acquire excessive amounts of storage.\n\u2022The MXR option limits the number of CICS requests, commands, and macros that a program can issue. This option is\nuseful in detecting program loops that generate an excessively large number of CICS requests.\nBefore you begin this section, complete the steps that are outlined in Start-up (unless you did so earlier in this session).\nThe Options Menu should be displayed.\n1.Select Option 02 to request Limit CICS Storage and Requests and press Enter.\nASMDEMO displays a screen that describes what will occur in this part of the demo.\n      **********************************************************************    \n      ****                                                              ****     \n      ****              CA InterTest Demo Session                       ****     \n      ****          MXR Option - Limit Number of CICS Requests          ****     \n      ****          MXS Option - Limit Amount of CICS Storage           ****     \n      ****                                                              ****     \n      **********************************************************************     \n  \n      The program has a loop containing a CICS request and another loop          \n      containing a GETMAIN request. Here is what will happen:                    \n  \n      1. The program is halted at an unconditional breakpoint before the loops. \n      2. You set the MXS and MXR options to limit storage and CICS requests.    \n      3. The program continues to execute.                                      \n      4. CA InterTest halts the program at automatic breakpoints when the       \n         limits are exceeded.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8278c582ea43-1", "text": "limits are exceeded.                                                   \n      5. You remove the options and the program completes execution.            \n  \n      When this section of the demo completes, you will return to the            \n      Options Menu.                                                             \n  \n                Press ENTER to continue or CLEAR to terminate                   \n \n2.Press Enter.\nInterTest for CICS halts the program at the first instruction following the label LOOPRTN because you set an\nunconditional breakpoint there during Start-Up.\nASMDEMO is halted at the first instruction after LOOPRTN. Because LOOPRTN does not have executable code, the\nunconditional breakpoint actually occurs before the first instruction; in this case, the highlighted ZAP instruction.\nNow you can access the Special Options menu to set options you need for testing.\nSet MXS and MXR Options\n1.Type the SO option in the command field.\n2.Press Enter.\nInterTest for CICS displays the Special Options menu.\nThe Special Options menu lets you set several options to change how InterTest for CICS monitors a program.\nYou are going to set two options:\n 370", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1f9018548565-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022MXS to limit the amount of CICS main storage acquired by the demo program\n\u2022MXR to limit the total number of CICS requests issued by the demo program\n\u2022Specify 50,000 bytes as the maximum amount of main storage that the demo program can obtain, and specify 20 as\nthe maximum number of CICS requests that the demo program can issue.\n\u2022Tab to the MXS field and type 50000, as shown in the following screen.\n\u2022Tab to the MXR field and type 20, as shown in the following screen.\n\u2022Press Enter.\n             CA InterTest MONITORING COMMAND BUILDER - SPECIAL OPTIONS        22 \n  \n        SET one or more options to override the default monitoring rules in:     \n                                  PROG=ASMDEMO                                    \n  \n             Enter X next to each option desired:                                 \n  \n                   Source Listing Breakpoint      (SLB) _                         \n                   No file updating               (NUP) _                         \n                   Reentrancy check               (RNT) _                         \n  \n             Follow monitoring (ON, name, NOPPT) (FOL) ________                   \n             Number of times to be monitored     (MUS) _____                      \n             Limit total size of CICS storage    (MXS) 50000__                    \n             Limit total number of CICS requests (MXR) 20_____                    \n  \n            Set local automatic breakpoint ('*', TERMID, .ANY, OFF)     ____     \n            Limit monitoring to your TERMINAL - '*' or TERMID:          ____     \n  \n  \n  Press ENTER key with data to process command or select PF key:                 \n  PF1 Help       2            3 End        4 Return     5            6", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1f9018548565-1", "text": "PF7            8            9           10           11           12          \n \nInterTest for CICS sets the MXS and MXR options and redisplays the breakpoint screen that is shown in the previous\nscreen example.\n\u2022Press PF4 until you are returned to the Source Listing Breakpoint.\n\u2022Press PF5 to continue program execution.\nASMDEMO resumes execution.\nLimit CICS Requests\nThe next screen that is displayed is the Automatic Breakpoint Display screen. InterTest for CICS halted ASMDEMO at an\nautomatic breakpoint because the maximum number of CICS requests (20) was exceeded.\nNOTE\nIf you are working on a system with LE 370 runtimes, you could reach the automatic breakpoint for the MXS\n(max storage size) first. If you do, perform the demo in the following order:\n1.InterTest for CICS Limits Acquisition of Storage removing the MXS Option\n2.InterTest for CICS Limits CICS Requests removing the MXR Option\n3.The Demo Program Executes to Completion\nThe instruction that triggered the automatic breakpoint is within a loop containing a CICS request.\n CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT          \n COMMAND ===>                                                                    \n 371", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4766a2651264-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n Program= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 28  \n                                         Search=                                 \n ----------+-------------------------------------------------------------------- \n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n  _ 002148  2826          DFHECALL =X'100200000800001300'                        \n  A 00215E   ==>          CP    LOOPCTR,=P'+50'                                  \n      ==>                                                                        \n      ==> MXR (max CICS requests) trigger value exceeded.                        \n      ==>                                                                        \n      ==>      Press PF1 for a detailed description.                             \n      ==>                                                                        \n  _ 002164  2837          BE    MXSOPTS                                          \n  _ 002168  2838          AP    LOOPCTR,=P'+1'                                   \n  _ 00216E  2839          B     CICSLOOP                                         \n  _ 002172  2841 MXSOPTS  DS    0H                                               \n            2842 *        EXEC CICS HANDLE CONDITION                             \n            2843 *             NOSTG(NOSTORG)                                    \n            2844          DFHECALL =X'02048000082A00000000000000000000000000000  \n     00068                      ,NOSTORG)                                        \n  _ 00218C  2855          ZAP   LOOPCTR,=P'0'                                    \n  _ 002192  2857 GETMLOOP DS    0H                                               \n \nRemove the MXR Option\nNow you can remove the MXR option so that ASMDEMO continues executing. If this is your program, you want to\nexamine the instructions that are generating excessive CICS requests.\n1.Type STATUS in the Command field and press Enter (or press PF12).", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4766a2651264-1", "text": "1.Type STATUS in the Command field and press Enter (or press PF12).\nInterTest for CICS displays the Monitoring Status display.\n2.To remove an option, tab to the Option, type R, and press Enter.\nNOTE\nOnly remove the MXR option; do not remove or modify the MXS option.\n3.Tab to the MXR entry.\n4.Type R.\n5.Press Enter.\n ----------------  CA InterTest for CICS MONITORING STATUS  ---------------\n  COMMAND ===>                                                                   \n  \n    Type + to expand or - collapse option levels displayed below,                \n           or R to remove option(s).                                            \n  \n      Option     Description                Attributes                           \n  _ - ASMDEMO    Program monitor entry      Assembler                            \n      |          Waiting at breakpoint      Task 00079, ABP since 02:20 p.m.    \n  _ - |-.ANY     User monitoring options    Active                               \n        |        Symbolic listing file      PROTSYM                              \n  r     |-MXR    Maximum CICS requests      20                                   \n  _     |-MXS    Maximum total storage      50000\n .\n . \n \n 372", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4aedd306c62a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterTest for CICS removes the MXR option.\n6.Press PF3 to return to the Source Listing Breakpoint screen.\nNotice that the explanation of the abend does not redisplay so that more of your source listing can be displayed.\nLimit Storage Acquisition\n1.Press PF5 to resume program execution.\nThe next screen is an automatic breakpoint display. InterTest for CICS halted ASMDEMO at an automatic breakpoint\nbecause the maximum main storage limit of 50,000 was exceeded.\nNOTE\nIn most cases, the instruction that triggered the automatic breakpoint is within a loop containing a GETMAIN\nrequest.\n CA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT        \n COMMAND ===>                                                                    \n Program= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 28  \n                                         Search=                                 \n ----------+-------------------------------------------------------------------- \n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n            2875 *        PRINT GEN                                              \n  A 0021B4   ==>          CP    LOOPCTR,=P'+10'                                  \n      ==>                                                                        \n      ==> MXS (max storage size) trigger value exceeded.                         \n      ==>                                                                        \n      ==>      Press PF1 for a detailed description.                             \n      ==>                                                                        \n  _ 0021BA  2877          BE    SENDMP00                                         \n  _ 0021BE  2878          AP    LOOPCTR,=P'+1'                                   \n  _ 0021C4  2879          B     GETMLOOP                                         \n  _ 0021C8  2881 NOSTORG  DS    0H                                               \n  _ 0021C8  2882          MVC   ERRORO,=CL10'NO STORAGE'", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4aedd306c62a-1", "text": "2883 *        EXEC CICS SEND                                         \n            2884 *        MAP('DERROR')                                          \n            2885 *        MAPSET('IN25AMP')                                      \n            2886 *        ERASE                                                  \n            2887          DFHECALL =X'1804D000080000000005E204000020',(CHA7,=CL  \n     00068                      ),(______RF,DERRORO),,(CHA7,=CL7'IN25AMP')       \n \nRemove the MXS Option\nRemove the MXS option so that ASMDEMO can continue executing. If this is your own program, examine the instructions\nthat are causing the program to obtain excessive amounts of storage.\n1.Type STATUS in the Command field and press Enter (or press PF12).\nThe Monitoring Status screen appears.\n2.To remove the MXS option, type R next to the MXS breakpoint entry and press Enter.\n ----------------  CA InterTest for CICS  MONITORING STATUS  --------------\n  COMMAND ===>                                                                   \n  \n    Type + to expand or - collapse option levels displayed below,                \n           or R to remove option(s).                                            \n  \n 373", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a9e3246baa94-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n      Option     Description                Attributes                           \n  _ - ASMDEMO    Program monitor entry      Assembler                            \n      |          Waiting at breakpoint      Task 00079, ABP since 02:25 p.m.    \n  _ - |-.ANY     User monitoring options    Active                               \n        |        Symbolic listing file      PROTSYM                              \n  r     |-MXS    Maximum total storage      50000\n .\n .\n . \n \nInterTest for CICS removes the MXS option.\n3.Press PF3 to return to the Source Listing Breakpoint screen.\nDemo Program Completes Execution\nPress PF5 to resume program execution.\nASMDEMO completes execution. InterTest for CICS returns you to the Demo Program Options Menu.\nNOTE\nASMDEMO continues to execute because you removed the option limiting the amount of main storage it can\nacquire.\nReview What Happened\nIn this part of the demo session you set two options to help test program ASMDEMO.\n\u2022The MXR option let you limit the number of CICS requests the program could issue. When ASMDEMO exceeded this\nlimit, InterTest for CICS halted the program. This feature helps you find program instructions within a loop that generate\nan excessive number of CICS requests.\n\u2022The MXS option let you limit the amount of main storage used by the program. When ASMDEMO exceeded the\namount of storage you specified, InterTest for CICS halted the program. This feature helps you find commands or\nmacros within a loop which are obtaining excessive amounts of storage.\nYou have now completed the Limit CICS Storage and Requests section of the demo session. Type another option number\nto continue with the demo session or press Clear to terminate the session.\nOption 03 Prevent a Program from Updating a File", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a9e3246baa94-1", "text": "Option 03 Prevent a Program from Updating a File\nThis section of the demo session shows you how to execute a program without having it update a file.\nThe No File Updating option is useful when you are testing a program. Preventing a program from updating a file\nmeans your test data remains unchanged at the end of each program execution. In this case, you can test the program\nrepeatedly without having to create test data.\nMany programs can use the same test file without interfering with the work of others. You can even allow a test program to\nuse a production file because the integrity of the file will be preserved.\nBefore you begin this section, complete the steps outlined earlier in this article in the section (unless you did so earlier in\nthis session). The Options Menu appears. Also be sure that the InterTest for CICS checkpoint file (PROTCPF) is defined\nto your CICS region, and that the status of the file is Open and Enabled.\n1.Select Option 03 to request No File Updating and press Enter.\nASMDEMO displays a screen that describes what will occur in this part of the demo session.\n **********************************************************************\n ****                                                              ****\n ****                  CA InterTest Demo Session                   ****\n 374", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4409a14731c8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n ****                    No File Updating Option                   ****\n ****                                                              ****\n **********************************************************************\n  \n The program reads a record and changes data in the record. Here is    \n what will happen:                                                     \n  \n 1. CA InterTest halts the program at a request breakpoint.            \n 2. You set the No File Updating option to prevent ASMDEMO from        \n    updating the file.                                                 \n 3. When ASMDEMO rewrites the file, the file is not updated.          \n 4. After the rewrite you use the FILE facility to confirm that the   \n    file has not been updated.                                      \n  \n    When this section of the demo completes, you will return to the  \n    Options Menu.                                                    \n  \n            Press ENTER to continue or CLEAR to terminate           \n \n2.Press Enter.\nInterTest for CICS displays the Request Breakpoint screen.\nHalt ASMDEMO at a Request Breakpoint\nInterTest for CICS halted ASMDEMO prior to the first File Control REWRITE command as you specified during startup.\nThe highlighted instruction is part of the generated EXEC CICS REWRITE command.\n CA InterTest for CICS  - PROTSYM FILE  SOURCE LISTING BREAKPOINT         \n COMMAND ===>                                                                    \n Program= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 28  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n     00068                      REA),(FB_2,RECLEN)                               \n  \n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n   R 001FA4   ==> NUPDTE   DS    0H                                \n            2655 *        EXEC CICS START TRANSID(CNTLTRAN)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4409a14731c8-1", "text": "2655 *        EXEC CICS START TRANSID(CNTLTRAN)                      \n            2656 *              FROM(NUPOFF) LENGTH(NUPOLEN) REQID(=X'9999')     \n            2657          DFHECALL =X'1008F8000800005400',(___4,=PL4'0'),(CHA8,  \n     00068                      ,(CHA4,CNTLTRAN),(______RF,NUPOFF),(FB_2,NUPOLEN)\n  U 001FD2  2673          B     SENDMP00                                         \n  _ 001FD6  2675 READATA  DS    0H                                               \n            2676 *        EXEC CICS HANDLE CONDITION                             \n            2677 *             DSIDERR                                           \n            2678 *             NOTOPEN (NOPEN)                                   \n            2679          DFHECALL =X'0204800008130C000000000000000000000000000  \n     00068                      ,NOPEN)                                          \n  _ 001FF0  2690          MVC   RECKEY,=CL10'0000000000'                         \n            2691 *        EXEC CICS STARTBR  RIDFLD(RECKEY) DATASET('PROTH')     \n            2692          DFHECALL =X'060CB000080020A000',(CHA8,=CL8'PROTH'),,(  \n     00068                      )),(______RF,RECKEY)\n \n 375", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2e703ac222e7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSetting request breakpoints lets you inspect the values of program variables and set options prior to all or specified CICS\ncommands and macros and other program calls.\n1.Page backward to look at the EXEC CICS REWRITE command.\n2.Press PF7 .\nThe following screen appears.\n CA InterTest for CICS - PROTSYM FILE  SOURCE LISTING BREAKPOINT         \n COMMAND ===>                                                                    \n Program= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 28  \n                                        Search=                                 \n ----------+-------------------------------------------------------------------- \n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n  _ 001F14  2594          MVC   FT,EIBTRMID                                      \n            2595 *        EXEC CICS START TRANSID(CNTLTRAN)                      \n            2596 *              FROM(NUPON) LENGTH(NUPONLEN) REQID(=X'9999')     \n            2597          DFHECALL =X'1008F8000800005400',(___4,=PL4'0'),(CHA8,  \n     00068                      ,(CHA4,CNTLTRAN),(______RF,NUPON),(FB_2,NUPONLEN)\n  _ 001F48  2614 NUPREAD  DS    0H                                               \n  _ 001F48  2615          MVC   RECLEN,=X'2A9'                                   \n            2616 *        EXEC CICS READ DATASET(CKPTNAME)                       \n            2617 *              INTO(NUPAREA) LENGTH(RECLEN)                     \n            2618 *              RIDFLD(NUPKEY) UPDATE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2e703ac222e7-1", "text": "2618 *              RIDFLD(NUPKEY) UPDATE                            \n            2619          DFHECALL =X'0602F0000800008400',(CHA8,CKPTNAME),(____  \n     00068                      REA),(FB_2__RF,RECLEN),(______RF,NUPKEY)         \n  _ 001F78  2635 NUPWRITE DS    0H                                               \n  _ 001F78  2636          MVC   NUPNME,=CL18'THIS IS NOT A NAME'                 \n            2637 *        EXEC CICS REWRITE DATASET(CKPTNAME) FROM(NUPAREA)      \n            2638 *              LENGTH(RECLEN)                                   \n            2639          DFHECALL =X'0606E0000800004000',(CHA8,CKPTNAME),(____  \n     00068                      REA),(FB_2,RECLEN)\n \nAccording to the EXEC CICS REWRITE command, ASMDEMO updates the file PROTCPF (contained in the\nCKPTNAME field as specified in the DATASET parameter of the EXEC CICS REWRITE command).\nIn this case, you want to set the No File Updating option to prevent ASMDEMO from updating PROTCPF. To set this\noption, access the Special Options menu.\nSet the No File Updating Option\nUse the followinf procedure to set the No File Updating Option:\n1.Type the SO option in the command field\n2.Press Enter.\nThe Special Options menu appears.\n3.Tab to the NUP field.\n4.Type X, and press Enter.\n             CA InterTest MONITORING COMMAND BUILDER - SPECIAL OPTIONS        22\n  \n       SET  one or more options to override the default monitoring rules in:     \n                                 PROG=ASMDEMO", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2e703ac222e7-2", "text": "PROG=ASMDEMO                                    \n  \n            Enter X next to each option desired:                                 \n  \n                  Source Listing Breakpoint      (SLB) _                         \n 376", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "47e08831a7ec-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                  No file updating               (NUP) x                    \n                  Reentrancy check               (RNT) _                         \n  \n            Follow monitoring (ON, name, NOPPT)  (FOL) ________                  \n            Number of times to be monitored      (MUS) _____                     \n            Limit total size of CICS storage     (MXS) _______                   \n            Limit total number of CICS requests  (MXR) _______                   \n  \n            Set local automatic breakpoint ('*', TERMID, .ANY, OFF)     ____     \n            Limit monitoring to your TERMINAL - '*' or TERMID:          ____     \n            User ID (or .ANY) who will execute the program:             .ANY     \n  \n  \n  PF1 Help       2            3 End        4 Return     5            6           \n  PF7            8            9           10           11           12          \n \nInterTest for CICS sets this option for the demo program.\n5.Press PF4 until you return to the Source Listing Breakpoint screen.\nBefore you resume program execution, look at the MVC instruction immediately before the EXEC CICS REWRITE\ncommand where ASMDEMO halts.\n CA InterTest for CICS  - PROTSYM FILE  SOURCE LISTING BREAKPOINT         \n COMMAND ===>                                                                    \n Program= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 28  \n                                         Search=                                 \n ----------+-------------------------------------------------------------------- \n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n  _ 001F14  2594          MVC   FT,EIBTRMID                                      \n            2595 *        EXEC CICS START TRANSID(CNTLTRAN)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "47e08831a7ec-1", "text": "2595 *        EXEC CICS START TRANSID(CNTLTRAN)                      \n            2596 *              FROM(NUPON) LENGTH(NUPONLEN) REQID(=X'9999')     \n            2597          DFHECALL =X'1008F8000800005400',(___4,=PL4'0'),(CHA8,  \n     00068                      ,(CHA4,CNTLTRAN),(______RF,NUPON),(FB_2,NUPONLEN)\n  _ 001F48  2614 NUPREAD  DS    0H                                               \n  _ 001F48  2615          MVC   RECLEN,=X'2A9'                                   \n            2616 *        EXEC CICS READ DATASET(CKPTNAME)                       \n            2617 *              INTO(NUPAREA) LENGTH(RECLEN)                     \n            2618 *              RIDFLD(NUPKEY) UPDATE                            \n            2619          DFHECALL =X'0602F0000800008400',(CHA8,CKPTNAME),(____  \n     00068                      REA),(FB_2__RF,RECLEN),(______RF,NUPKEY)         \n  _ 001F78  2635 NUPWRITE DS    0H                                               \n  _ 001F78  2636          MVC   NUPNME,=CL18'THIS IS NOT A NAME'                 \n            2637 *        EXEC CICS REWRITE DATASET(CKPTNAME) FROM(NUPAREA)      \n            2638 *              LENGTH(RECLEN)                                   \n            2639          DFHECALL =X'0606E0000800004000',(CHA8,CKPTNAME),(____", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "47e08831a7ec-2", "text": "00068                      REA),(FB_2,RECLEN)                            \n \nThe MVC instruction specifies to move the data string THIS IS NOT A NAME to the data field NUPNME. If ASMDEMO\nupdates the file, that data string appears in the record.\n6.Press PF5 to continue program execution.\nASMDEMO resumes execution.\n 377", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e27abc0747d0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse FILE to Inspect the Record\nInterTest for CICS halts ASMDEMO at an unconditional breakpoint that you specified in the Startup section, and displays\nthe following screen.\n CA InterTest for CICS  - PROTSYM FILE  UNCOND  BEFORE BREAKPOINT         \n COMMAND ===>                                                                    \n Program= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 28  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n     00068                      ,(CHA4,CNTLTRAN),(______RF,NUPOFF),(FB_2,NUPOLEN)\n  \n      Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n  U 001FD2   ==>          B     SENDMP00                                         \n  _ 001FD6  2675 READATA  DS    0H                                               \n            2676 *        EXEC CICS HANDLE CONDITION                             \n            2677 *             DSIDERR                                           \n            2678 *             NOTOPEN (NOPEN)                                   \n            2679          DFHECALL =X'0204800008130C000000000000000000000000000  \n     00068                      ,NOPEN)                                          \n  _ 001FF0  2690          MVC   RECKEY,=CL10'0000000000'                         \n            2691 *        EXEC CICS STARTBR  RIDFLD(RECKEY) DATASET('PROTH')     \n            2692          DFHECALL =X'060CB000080020A000',(CHA8,=CL8'PROTH'),,(  \n     00068                      )),(______RF,RECKEY)                             \n  _ 00201E  2707          MVC   UNPCK,=CL4'    '", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e27abc0747d0-1", "text": "2708 *        EXEC CICS READNEXT SET(R6) RIDFLD(RECKEY)              \n            2709 *              LENGTH(RECLEN) DATASET('PROTH')                  \n            2710          DFHECALL =X'060EF400080100B000',(CHA8,=CL8'PROTH'),(P  \n     00068                      6),(FB_2__RF,RECLEN),(______RF,RECKEY),,(FB_2,=A(\n \nTo demonstrate that InterTest for CICS prevented ASMDEMO from updating the file, you halted the program after\nthe REWRITE command was executed. Now use the powerful InterTest for CICS FILE facility to determine whether\nASMDEMO updated the file.\n1.Press PF6 Menu.\nThe Breakpoint Primary Option Menu appears.\n2.Select option 1 - Main Menu.\nInterTest for CICS displays the Primary Option Menu.\n3.Select 4 Auxiliary storage.\nThe Auxiliary Storage Menu appears.\n  ----------  CA InterTest for CICS AUXILIARY STORAGE MENU  --------------\n  OPTION  ===> 1                                                                 \n  \n     Select an auxiliary storage type, specifying optional criteria below.      \n  \n     1  Files              - Display/select files for access                     \n     2  DB2 database       - Invoke DB2 SQL interface facility                   \n     3  DL/I database      - Access DL/I database                                \n     4  TD queues          - Display/select transient data queues for access     \n     5  TS queues          - Display/select temporary storage queues for access  \n  \n     Type specific or generic file/queue name(s):                                \n  \n 378", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b74f99192bbb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n     protcpf_ ________ ________ ________ ________ ________ ________ ________     \n .\n  \n .                                                                              \n \n4.Type 1 in the Option field and protcpf for the file name.\n5.Press Enter.\nInterTest for CICS displays the File Selection menu.\n6.Type an s next to the file name and press Enter.\nThe initial File Facility screen appears.\n DATATYPE= FC FILEID= PROTCPF  MODE=      LOG=OFF TODEST=         PASSWORD=      \n FUNC=      SUBFUNC=      RETMETH=        ARGTYP=     SRCHTYP=                   \n MESSAGE=                                                                        \n  RETNRCID=                                                         CHGLEN=      \n     RCID=                                                                       \n     DATA=                                                          SIZE= 0000   \n FORMAT= D 00112233 44556677 8899AABB CCDDEEFF  *0123456789ABCDEF*               \n LOC 0000  ........ ........ ........ ........  ................               \n  \n  \n  \n  \n  \n  \n  \n  \n ------------------------------------------------------------------------------- \n 1 Help       2 Format C   3 End        4 BEGB       5            6 DataType DL  \n 7 Page bwd   8 Page fwd   9 Caps Off  10 Top       11 Bottom    12             \n \n7.Press PF4 to begin browsing the file.\nThe first record in the PROTCPF file is displayed.\nNOTE\nYour version of this screen might differ slightly.\n  DATATYPE= FC FILEID= PROTCPF  MODE=BROWSELOG=ON  TODEST=         PASSWORD=     \n FUNC= NEXT SUBFUNC=      RETMETH=        ARGTYP=     SRCHTYP=", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b74f99192bbb-1", "text": "MESSAGE= CAIN0601 RECORD OBTAINED FOR VIEWING                                   \n  RETNRCID=404040404040404040                                       CHGLEN=      \n     RCID=                                                                       \n     DATA=                                                          SIZE= 02A9   \n FORMAT= D 00112233 44556677 8899AABB CCDDEEFF  *0123456789ABCDEF*              \n LOC 0000  ........ ........ ........ ........  ................               \n   0000    40404040 40404040 4040405C 5C5C4040              ***    DSORG=VSKS    \n   0010    404040D9 C5C3D6D9 C440E3D6 40D7D9C9      RECORD TO PRI  RECFM=FB      \n   0020    D4C540E3 C8C540C3 C8C5C3D2 D7D6C9D5   ME THE CHECKPOIN  LRECL=02A9    \n   0030    E340C6C9 D3C54040 405C5C5C 5C404040   T FILE   ****     BLKSIZE=0000  \n   0040    40404040 40404040 F0F3F1F4 F0F0F0F0           03140000  KEYPOS=0000   \n   0050    00000000 00000000 00000000 00000000   ................ KEYLEN=09     \n   0060    00000000 00000000 00000000 00000000   ................ STRNO=02      \n   0070    00000000 00000000 00000000 00000000   ................", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b74f99192bbb-2", "text": "0080    00000000 00000000 00000000 00000000   ................ READ          \n 379", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fecd376ea3dd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n   0090    00000000 00000000 00000000 00000000   ................ ADD           \n   00A0    00000000 00000000 00000000 00000000   ................ UPDATE        \n   00B0    00000000 00000000 00000000 00000000   ................ BROWSE        \n   00C0    00000000 00000000 00000000 00000000   ................ DELETE        \n -------------------------------------------------------------------------------\n 1 Help       2 Format C   3 End        4 ENDB       5 PREV       6 DataType DL \n 7 Page bwd   8 Page fwd   9 Caps Off  10 Top       11 Bottom    12\n \nThe previous screen displays the contents of the first record in both hexadecimal and character formats. The character\ndisplay indicates that the data string THIS IS NOT A NAME was not moved into this record.\n\u2022Setting the No File Updating option prevented ASMDEMO from updating this file\n\u2022Before you return to ASMDEMO, we will discuss the capabilities of FILE\nFILE Facility\nThe FILE facility lets you view, update, add and delete records, and search for character strings. You can perform these\nfunctions at any time (for example, while your program is at a breakpoint). You can use FILE with VSAM and BDAM files,\nDL/1 and DB2 databases, temporary storage records, and transient data records. You can also use FILE to perform\nroutine file maintenance when no program is executing.\nNOTE\nGoing back and forth between the Source Listing facility and the FILE facility is as easy as pressing a single key.\nFILE displays records in dump format character format, vertical format, and structured format. To display the previous", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fecd376ea3dd-1", "text": "FILE displays records in dump format character format, vertical format, and structured format. To display the previous\nrecord in different formats, press PF2. For structured format, which displays records or DL/I segments on a field-by-field\nbasis, you also must identify the program containing the structure.\nUse the FILE facility when you are testing your own programs. For example, use FILE to change your test records or\nto create more records in the middle of a demo session. You also can use FILE to ensure your program successfully\nupdated a file. For more information on using FILE, see Accessing Auxiliary Storage FILE.\nNow return to testing ASMDEMO.\nDemo Program Completes Execution\n1.Press Clear.\nInterTest for CICS displays the File Selection List.\n2.Press PF4 until you are returned to the Source Listing Breakpoint.\n3.Press PF5 to resume program execution.\nThe demo program successfully completes execution, and returns you to the Demo Program Options Menu.\nReview What Happened\nIn this part of the demo session you took three important InterTest for CICS features. You were able to:\n\u2022Set request breakpoints prior to CICS commands\n\u2022Prevent a program from updating a file\n\u2022Display a record in a file\nSetting request breakpoints makes it easy for you to halt your program at various points, such as before all HANDLE\nCONDITION commands or all Terminal Control commands. When your program halts, you can inspect main storage or\nauxiliary storage to detect errors and review program logic.\n 380", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "85a48b0324fd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPreventing a program from updating a file means you can test a program repeatedly without having to create test data.\nMany programs can share the same test file because no program changes the file. Also, a test program can use a\nproduction file without corrupting the file.\nDisplaying a record in a file lets you see whether your program is working correctly. The FILE facility also lets you add,\ndelete, and update records to meet your individual testing needs and for easy file maintenance.\nYou have now completed the No File Updating section of the demo session. Type another option number to continue with\nthe demo session or press Clear to terminate the session.\nCOBOL Primer\nUse this COBOL Primer to train users in basic program test and debug features, and to introduce some advanced\nfeatures of InterTest for CICS.\nWe recommend that all users take the demo sessions in this article and become familiar with the features that are\nexplained here. For complete information about these and other features, see  CICS Debugging. The best way to begin\nlearning about your product is to read the COBOL Basic Demo Session first.\nGetting Help\nThe Help facility is online documentation of product features. The Help facility makes it easy to learn and use the product.\nHelp is available from all product screens.\nTo view an online summary of new features for this release, use ITST Option 8 What's New.\nCOBOL Basic Demo Session\nThe best way to begin learning about InterTest is to perform the demo at a terminal.\nThe basic demo session illustrates many of the testing and debugging tasks that you will use on your programs.\nWe assume that InterTest for CICS has been installed on your system. If not, contact your systems programmer.\nThis article describes the following topics:\nMaintain Synchronized Processing", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "85a48b0324fd-1", "text": "This article describes the following topics:\nMaintain Synchronized Processing\nBefore you begin testing, note that when InterTest searches the symbolic files for the COBOL programs that are specified\nfor testing, it tries to match the date and time of the symbolic file and the load module. If no match is found, one of the\nfollowing messages types is displayed:\n\u2022A symbolic version list\n\u2022A warning message\nThis feature lets you always maintain synchronized processing by letting you select the correct symbolic version of the\nprogram that you want to test.\nSymbolic Version Processing\nNOTE\nWhen you request a COBOL program that has no previously declared breakpoints or monitoring options set,\nInterTest matches the most recently compiled symbolic file date/time to the load module date/time.\n\u2022If an exact match is found, InterTest automatically selects and displays the program. However, if an exact match is\nfound and a more recently compiled version of the program is in a PROTSYM file, InterTest displays the symbolic\nversion list. You can perform following actions from the symbolic version list:\n 381", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4661bd8873d9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2013Select the matching listing and debug the program.\n\u2013Not select the matching listing and cancel monitoring. Then place a new copy the latest version of the program into\nyour CICS region and select the latest program version for monitoring.\n\u2022If a match is not found, InterTest displays the symbolic version list from which you can perform following actions:\n\u2013Select the appropriate symbolic file\n\u2013Ignore symbolic processing for the program\nThe Symbolic Version List screen also explains the cause of the mismatch.\nDuring automatic breakpoint processing, if a program has no previously selected symbolic file, InterTest matches the load\nmodule date/time to a symbolic file.\n\u2022If an exact match is found, InterTest automatically selects and displays the program.\n\u2022If a match is not found, InterTest automatically selects the first symbolic file that contains the program and displays it\nwith a warning message on the first Source Listing Breakpoint screen indicating the mismatch.\nThe following figure shows the Symbolic Version List screen:\n   CA InterTest for CICS - SYMBOLIC VERSION LIST                          \n  \n    Program = COBDEMO     Load Module Date/Time =  11/12/2000 09:02:03           \n    Loadlib = your.program.loadlib                      Volume = volser\n  \n    File ID     Date       Time    Language     Comments                         \n  _ PROTSYM  11/12/2000  09.52.23  COBOL  LATEST VERSION                     \n  _ PROTDMO  08/31/2000  14.12.15  COBOL \n .\n .\n . \n          S - Select which Symbolic file to use                                 \n  -------------------------------------------------------------------------------\n  PFKEYS:  1 Help      2           3 No file   4           5           6", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4661bd8873d9-1", "text": "7           8           9          10          11          12         \n  CAIN8000 The latest Symbolic version does not match the current load module\n \nNOTE\nOnce a symbolic file has been selected for a program, InterTest continues to use the selected file and bypasses\nsubsequent date/time matching until all declared breakpoints and monitoring options are removed for the\nprogram, or until a CNTL=NEW, PROG=program command is executed.\nDemo Session Objectives\nThis demo session teaches you how to perform the following actions:\n\u2022Select a source listing for a program from the ITST menus\n\u2022Inform InterTest that you want to test a program (set monitoring)\n\u2022Respond to the information provided when a program error is detected\n\u2022Examine the value of a data item\n\u2022Dynamically change the value of a data item\n\u2022Halt program execution at any point (set breakpoints)\n\u2022Resume program execution\n 382", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9e932e7c64f7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDemo Session Scenario\nThe InterTest basic demo session takes you through the following scenario:\n1.You use the ITST menus to select and view the source listing of the sample program to be executed. A sample IBM\nEnterprise COBOL program that is named COBDEMO is provided for you to use.\n2.You set monitoring for the sample program and view the status display of your monitoring request.\n3.You exit ITST menus and initiate COBDEMO by specifying the DEMC transaction.\n4.InterTest for CICS intercepts and prevents an ASRA abend in COBDEMO. InterTest halts COBDEMO at an ADD\nstatement and displays a diagnostic message indicating that the cause of the problem is improperly formatted data.\n5.You examine the current value of TASKNUM, the receiving field in the ADD statement which you suspect may be the\ncause of the problem. You find that TASKNUM does not contain a valid packed decimal number.\n6.You move a packed decimal zero into TASKNUM to correct the error.\n7.You set a breakpoint to halt COBDEMO at another statement. This step is purely instructional -- it has nothing to do\nwith correcting the ASRA.\n8.You resume program execution. InterTest halts the program at the breakpoint you set in Step 7. When the ADD\nstatement executed, the value of TASKNUM is changed.\n9.Clean up by removing the breakpoint that you set. Then resume program execution, and COBDEMO runs to\ncompletion.\nDB2 Demo Program\nDB2DEMO is a sample program that helps you to set up and verify your DB2 support for InterTest for CICS and\nSymDump  for CICS. The demo program is written in COBOL and uses basic read-only SQL statements. The table that is", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9e932e7c64f7-1", "text": "used for queries is SYSIBM.SYSTABLES, thus, no particular database for this demo is needed. The DB2DEMO program\nand DEMD transaction can be used in place of the COBDEMO program and DEMC transaction as described in the Demo\nSession Scenario.\nFollow these steps:\n1.To support DB2, ensure that you successfully complete all steps that are described in Install DB2 Support section in\nConfiguring. Also ensure that DB2DEMO is properly installed.\n2.Set up monitoring:\n\u2013To use InterTest for CICS to monitor the DB2 demo program, make sure InterTest is started and DB2DEMO\nprogram is monitored by it.\n\u2013To use SymDump  for CICS to capture the dump of the DB2 demo program, make sure SymDump is started. If\nInterTest for CICS is also installed, make sure it does not monitor DB2DEMO.\n3.Run the DB2DEMO program by invoking the DEMD transaction.\nThe welcome screen is displayed.\n4.Perform one of the following steps:\n\u2013To abend your program without any SQL statement executed, press PF2 on the welcome screen.\n\u2013To continue and perform SQL select from SYSIBM.SYSTABLES, press Enter.\n5.After you press Enter on the welcome screen, the following errors are possible:\n\u2013DB2 connection error -- Connection between the CICS region and DB2 subsystem is not established correctly.\nTo correct this error, ensure that the CICS region is connected to the proper DB2 subsystem, then run the DEMD\ntransaction again.\n\u2013SQL error -- Error occurs during the execution of a SQL statement.\nTo resolve this error, use the information that is provided on the screen (SQLCA). Find the error in the appropriate\nDB2 documentation and do all necessary corrections. Then run DEMD transaction again.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9e932e7c64f7-2", "text": "DB2 documentation and do all necessary corrections. Then run DEMD transaction again.\n6.See output of SELECT SQL statement from SYSIBM.SYSTABLES table.\n 383", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "90d2ed557853-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2013Press Enter to get the next screen.\n\u2013Press PF3 or CLEAR to end the demo.\n\u2013Press PF2 to abend the program.\n7.Abend the program:\n\u2013If DB2DEMO program is monitored by InterTest for CICS, the automatic breakpoint appears at \"ADD 1 TO\nTASKNUM\" statement.\n\u2013If DB2DEMO program is not monitored by InterTest for CICS ASRA, the abend occurs and DB2DEMO program is\nterminated.\n8.If DB2DEMO is monitored for InterTest for CICS, and a breakpoint appears at ADD 1 TO TASKNUM' statement, you\ncan correct the abending statement.\n\u2013Display TASKNUM variable using KEEP or DISPAY command.\n\u2013Edit value in TASKNUM so that it is a valid packed decimal number.\n\u2013Continue program execution using GO command.\n\u2013DB2DEMO program end screen is displayed and program ends.\nSelect the Source Program from the ITST Menus\nTo begin your session, select the source listing of the COBDEMO demonstration program from the ITST Primary Option\nMenu.\n1.Sign on to CICS.\n2.Type ITST on a clear screen.\n3.Press Enter.\nInterTest for CICS displays the Primary Option Menu:\n  --------------- CA InterTest for CICS PRIMARY OPTION MENU  --------------\n  OPTION  ===>\n    1  Source             - Display/select program source files/listings       \n    2  Monitoring         - Display/modify CA InterTest monitoring/activity    \n    3  Main storage       - Display/modify CICS storage areas                  \n    4  Auxiliary storage  - Display/access databases/files/queues              \n    5  Dump analysis      - Invoke CA SymDump CICS dump/trace capture facility", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "90d2ed557853-1", "text": "5  Dump analysis      - Invoke CA SymDump CICS dump/trace capture facility \n    6  Product help       - Invoke CA InterTest product help facility          \n    7  Status/Maintenance - Product status and maintenance functions           \n    8  What's new?        - Display information about CA InterTest for CICS\n    X  Exit               - Terminate menu processing                          \n  \n  \n  \n  \n  \n  \n  \n PF1 Help       2            3 End        4 Return     5            6          \n PF7            8            9           10           11           12         \n \nNote that the PF keys have conventional assignments for ISPF-like navigation:\nPF1 Help accesses online help\n\u2022PF3 End displays the previous panel\n\u2022PF4 Return returns to the top-level menu\n 384", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8a5472be4ada-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNow we look at the source listing of the program we will debug.\n1.Type 1 in the Option field.\n2.Press Enter.\nThe InterTest Source Menu is displayed.\n ----------------  CA InterTest for CICS  SOURCE MENU  ---------------\n OPTION  ===> 1                                                                \n  \n    Select a member list type, specifying optional criteria below.            \n  \n    1  Source listings    - Display/select program source listings             \n    2  Symbolic files     - Display/select program source SYMBOLIC files       \n  \n    Type specific or generic program/file name(s):                             \n       (Valid mask characters are  *  and/or  +)                               \n  \n    c*______ ________ ________ ________ ________ ________ ________ ________    \n  \n .\n .\n .\n \nSince we know that the COBOL demo programs all start with a c, we can filter for all members that begin with that\nletter.\n3.Type 1 in the Option field to search for program listings.\n4.Tab to the first entry field for file/program names, and type c*. The asterisk is a generic or wildcard character and\nindicates that anything from this point in a file name will satisfy the search criteria.\n5.Press Enter.\nThe Source Listing Selection screen is displayed. The screen lists all program Source Listings beginning with the letter\nc.\n ------------  CA InterTest for CICS   SOURCE LISTING SELECTION  ----------\n  COMMAND ===>                                                                   \n  \n    Type S to select a source listing.                                           \n                                                                        More:   +\n    Name     File         Created       Size Attributes                              \n  _ COBDEML  PROTSYM  08/01/2013 16:18    31 IBMCOB 3.2, no purge, composite", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8a5472be4ada-1", "text": "s COBDEMO  PROTSYM  08/01/2013 16:03   132 IBMCOB 3.2, no purge                                 \n  _ CSBIN25  PROTSYM  08/01/2013 16:12    21 IBMCOB 3.2, no purge                \n  \n  PF1 Help       2 Refresh    3 End        4 Return     5            6           \n  PF7 Backward   8 Forward    9           10           11           12          \n \n6.Type S in the field to the left of the program name and press Enter.\nNOTE\nIf the list does not contain the name of the previously indicated demo program, the cause may be that the user\nwho installed InterTest changed the name of the available InterTest sample programs. Check with that user to\nfind the correct names.\n    CA InterTest for CICS   - PROTSYM FILE  SOURCE LISTING DISPLAY         \n COMMAND ===>                                                                   \n Program= COBDEMO  Option #       Stmt #                             Margin= 01\n 385", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "941e3a1c6e79-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                          Search=                                \n -------------------------------------------------------------------------------      \n         YEARWINDOW(1900)                                                               \n         ZWB                                                                         \n      000001 ID DIVISION.                                                            \n      000002 PROGRAM-ID. COBDEMO.                                                    \n      000003 ENVIRONMENT DIVISION.                                                   \n      000004 DATA DIVISION.                                                        \n    _ 000005 WORKING-STORAGE SECTION.                                             \n    _ 000006 77  S999-FIELD1             PIC S9(3).                                \n    _ 000007 77  S999-FIELD2             PIC S9(3)       VALUE +50.                \n    _ 000008 77  999-FIELD1              PIC 9(3).                                 \n    _ 000009 77  999-FIELD2              PIC 9(3)        VALUE 50.                 \n    _ 000010 77  COMMAREA-LEN            PIC S9(4) COMP  VALUE +59.                \n    _ 000011 77  LINK-COMMAREA-LEN       PIC S9(4) COMP  VALUE +59.                \n    _ 000012 77  TSQ-LEN                 PIC S9(4) COMP  VALUE +59.                \n    _ 000013 77  REC-LEN                 PIC S9(4) COMP.                           \n    _ 000014 77  NUM-CHOICES             PIC S9(4) COMP  VALUE +7.                 \n    _ 000015 77  SUB                     PIC S9(4) COMP.                         \n \n\u2022The top half of the display identifies the program and provides fields for entering commands, options, statement\nnumbers, and search criteria. Depending on your session defaults, PF key assignments and available options might", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "941e3a1c6e79-1", "text": "numbers, and search criteria. Depending on your session defaults, PF key assignments and available options might\nalso be displayed. For clarity, these items are omitted from the Source Listing displays in this article.\n\u2022The bottom half contains the source listing.\nNOTE\nThe statement numbers on your screen might not match the numbers in the illustrations. This fact does not\nprevent you from performing the test session.\nView the Source Listing Profile\n1.Type PROFILE on the Command line and press Enter (or, press PF4 Profile) to view the PF key assignments and\nother session options.\nInterTest for CICS displays the Source Listing Profile for your current session. This list contains the PF keys, options,\nand current environment settings that relate to the Source Listing display.\n    CA InterTest for CICS   - PROTSYM FILE  SOURCE LISTING PROFILE         \n COMMAND ===>                                                                    \n Program= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n OPTS 1 Proc div  2 Work-stor 3 Link sect  4 D-map      5 Clst/Pmap More:   +    \n      6 Data xref 7 Proc xref 8 Err msgs   9 Srch fwd  10 Srch bwd               \n PFKS 1 Help      2           3 End        4 Auto prms  5 Monitor    6 Menu      \n      7 Backward  8 Forward   9 Next Wnd  10           11           12 Status    \n ------------------------------------------------------------------------------- \n Display window   = N         N (None), T (Titles), R (Registers),               \n                              K (Keep), P (Program)                              \n PF7/8 amount     = PAGE      PAGE, HALF, STOP, or a number from 1 to 9999", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "941e3a1c6e79-2", "text": "Step Timing      = BEFORE    Stop  Before  or  After  the next verb  is executed\n Stepping amount  = 001       The number of verbs   to execute                   \n Auto-stepping    = OFF       ON to activate; press PF4 to change values         \n Source List BKPT = ON        OFF to use the detailed breakpoint display         \n From terminal ID = U084      Terminal ID where the program will execute        \n BKPT terminal ID = U084      Terminal ID to receive the breakpoint displays     \n 386", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5ae9362b30e5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n User ID          = .ANY      User ID who will execute this program             \n AutoKeep Display = ON        OFF to deactivate                                  \n Code Counting    = OFF       ON to activate Code Coverage                       \n SDF              = DATA      HEX  for Hexadecimal/Character Format            \n \nNOTE\nVerify that the AutoKeep Display feature is activated for this demo session. If not, change it from OFF to ON\nand press Enter.\nSet Monitoring\nThe next step is to instruct InterTest to monitor COBDEMO. As part of monitoring a CICS command-level program such as\nCOBDEMO, InterTest automatically prevents all CICS abends during execution. This functionality is explained later when\nInterTest prevents COBDEMO from abending because of an ASRA.\nThere are different ways to tell InterTest to monitor the program. If you are viewing a program source listing, you can\nperform one of the following actions:\n1.Type MONITOR on the Command line and press Enter.\nor\n2.Press PF5 (notice PF5 is listed as Monitor in the previous screen).\n3.Press PF5, or use the monitor command, to begin monitoring the demo program. You can do this from either the\nSource Listing Profile or from the Source Listing Display.\nThe screen momentarily flashes as the request is processed. The Source Listing Display screen then reappears.\nView Monitoring Status\nTo verify that the demo program is being monitored:\n1.Type STATUS on the command line, as shown in the following screen:\n    CA InterTest for CICS   - PROTSYM FILE  SOURCE LISTING DISPLAY          \n COMMAND ===> status                                                                    \n Program= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5ae9362b30e5-1", "text": "Search=                                 \n OPTS 1 Proc div  2 Work-stor 3 Link sect  4 D-map      5 Clst/Pmap More:   +    \n      6 Data xref 7 Proc xref 8 Err msgs   9 Srch fwd  10 Srch bwd               \n PFKS 1 Help      2           3 End        4 Profile    5 Monitor    6 Menu      \n      7 Backward  8 Forward   9 Next Wnd  10           11           12 Status    \n ------------------------------------------------------------------------------- \n       YEARWINDOW(1900)                                                          \n       ZWB                                                                       \n    000001 ID DIVISION.                                                          \n    000002 PROGRAM-ID. COBDEMO.                                                 \n \n2.Press Enter\nInterTest for CICS displays the Monitoring Status screen. This status shows the monitoring entry for the current\nprogram only.\n ---------------  CA InterTest for CICS   MONITORING STATUS  --------------\n  COMMAND ===>                                                                   \n  \n    Type + to expand or - collapse option levels displayed below,                \n           or R to remove option(s).                                             \n  \n      Option     Description                Attributes                           \n 387", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "51b6bf4b0095-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  _ - COBDEMO    Program monitor entry      IBMCOB 3.2                           \n  _ - |-.ANY     User monitoring options    Active                               \n        |        Symbolic listing file      PROTSYM                              \n  _     |-SLB    Source listing breakpoints U023                                 \n                 *** End of data ***                                             \n  \n  \n  PF1 Help       2 Refresh    3 End        4 Return     5 Collapse   6 Expand    \n  PF7 Backward   8 Forward    9           10           11           12          \n \nNOTE\nIf the Status display is not visible, monitoring is not set correctly. To set monitoring, press PF3 to return to\nthe Source Listing display and type MONITOR on the command line, or press PF5 . Check the status again\nbefore you continue.\n3.Once you have verified that the correct demo program is being monitored, press PF3 to go back to the Source Listing.\nNow exit to CICS using the fastpath entry (=x), as follows:\n4.Type =X in the Source Listing Command field and press Enter. You return to the ITST menu processing.\n5.From the Source Selection Menu, type =X in the Command field and press Enter to exit to CICS.\nStart Program Execution\nNow you are ready to begin testing COBDEMO.\n1.Clear the CICS display and type DEMC, the transaction that executes COBDEMO.\n2.Press  Enter.\nThe following Welcome screen displays.\n ****************************************************************************** \n ****************************************************************************** \n *****                                                                    ***** \n *****                             Welcome to the                         ***** \n *****                       CA InterTest Demo Session                    ***** \n *****                                                                    ***** \n *****                                                                    ***** \n *****              Before proceeding, please have on hand the            *****", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "51b6bf4b0095-1", "text": "*****                                                                    ***** \n *****              Before proceeding, please have on hand the            ***** \n *****              guide which accompanies the Demo Session.             ***** \n *****                                                                    ***** \n *****                                                                    ***** \n *****     Please make sure that the program COBDEMO is monitored by      ***** \n *****     CA InterTest. This program will abend if it is not monitored.  ***** \n *****                                                                    ***** \n *****     To turn the monitor on, press CLEAR and follow the steps       ***** \n *****     outlined in the documentation.                                 ***** \n *****                                                                    ***** \n *****     If the monitor is already on, press ENTER to begin the         ***** \n *****     Basic Demo Session or PF2 to go to the Options Menu.           ***** \n *****                                                                    ***** \n ****************************************************************************** \n ******************************************************************************\n \n3.Press Enter.\nCOBDEMO resumes execution.\n 388", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "26c20df3f5ff-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDetect and Prevent an Abend\nThe next screen that you see is not displayed by the COBOL demo. This is a diagnostic screen that is called a breakpoint\ndisplay. This screen is displayed by InterTest when an error is detected.\n    CA InterTest for CICS   - PROTSYM FILE  ABEND DETECTED BREAKPOINT      \n COMMAND ===>                                                                    \n Program= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n  _____ TASKNUM                         | ?00000.                                \n ---------+--------------------------------------------------------------------- \n  _ 000477 CONTINUE-TASK.                                                        \n    000478**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED                          \n   A    ==>     ADD +1 TO TASKNUM.                                                      ==>                   \n                                                           ==> ASRA ABEND (0C7) detected and prevented. Caused\n by invalid decimal           ==> arithmetic data format.                                                   \n   ==>                                                                              ==>      Press PF1 for a\n detailed description.        \n      ==>                                                                        \n  _ 000480     IF TASKNUM = 1                                                    \n  _ 000481         MOVE 'DMAPASR'  TO MAPNAME.                                   \n  _ 000482     IF TASKNUM = 2                                                    \n  _ 000483         MOVE 'DMAPSUM'  TO MAPNAME.                                   \n  _ 000484     IF TASKNUM GREATER 2                                              \n  _ 000485         GO TO SEND-END-MSG.                                           \n  _ 000486     GO TO REWRITE-TSQ.                                                \n  _ 000487 REWRITE-TSQ.                                                          \n    000488*EXEC CICS WRITEQ TS                                                  \n \nNotice that InterTest has highlighted an ADD instruction and displayed a message below it.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "26c20df3f5ff-1", "text": "Notice that InterTest has highlighted an ADD instruction and displayed a message below it.\nExecution of that ADD instruction triggered an ASRA abend. InterTest prevented the abend and then displayed the\ndiagnostic screen that you are viewing.\nWhen InterTest stops program execution, we say that it halts the program at a breakpoint. This can be done automatically,\nor InterTest halts a program at a breakpoint that was set by you, the programmer. The A to the left of the ADD statement\nindicates that the current halt in program execution is an Automatic breakpoint -- not one set by you.\nNow look at the highlighted message. This message explains that the problem is caused by improperly formatted data.\nSince ADD +1 TO TASKNUM triggered the breakpoint, TASKNUM likely contains improperly formatted data.\nSo far, InterTest has prevented COBDEMO from abending and identified the problem.\nNext, perform the following steps:\n1.Determine the cause of the error.\n2.Dynamically correct the error by changing the value of TASKNUM.\nDetermine the Cause of the Error\nNext, confirm that the value stored in TASKNUM is not in valid arithmetic format. Examine the current value, that is the\nvalue prior to the execution of the ADD statement that triggered the ASRA.\nInterTest for CICS displays the current value of TASKNUM, as shown in the following screen:\n    CA InterTest for CICS   - PROTSYM FILE  ABEND DETECTED BREAKPOINT      \n 389", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "24e9f3f36b94-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n COMMAND ===>                                                                    \n Program= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n  _____ TASKNUM                         | ?00000.                                \n ---------+--------------------------------------------------------------------- \n  _ 000477 CONTINUE-TASK.                                                        \n    000478**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED                          \n  A    ==>     ADD +1 TO TASKNUM.                                                \n      ==>                                                                        \n      ==> ASRA ABEND (0C7) detected and prevented. Caused by invalid decimal     \n      ==> arithmetic data format.                                                \n      ==>                                                                        \n      ==>      Press PF1 for a detailed description.                             \n      ==>                                                                        \n  _ 000480     IF TASKNUM = 1                                                    \n  _ 000481         MOVE 'DMAPASR'  TO MAPNAME.                                   \n  _ 000482     IF TASKNUM = 2                                                    \n  _ 000483         MOVE 'DMAPSUM'  TO MAPNAME.                                   \n  _ 000484     IF TASKNUM GREATER 2                                              \n  _ 000485         GO TO SEND-END-MSG.                                           \n  _ 000486     GO TO REWRITE-TSQ.                                                \n  _ 000487 REWRITE-TSQ.                                                          \n    000488*EXEC CICS WRITEQ TS                                                  \n \nWhen the AutoKeep Display feature is active, InterTest automatically displays the values of the variables associated with\na line of code. In this case, TASKNUM is displayed in this specially formatted Keep window. The data item name is on\nthe left, and the field datatype appropriate display format is on the right. The question mark in the beginning of the field\nindicates that it contains incorrect values for its datatype.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "24e9f3f36b94-1", "text": "indicates that it contains incorrect values for its datatype.\nUp to six data items are displayed at a time in the scrollable Keep window. This feature lets you see how the values of\ndata items change as your program executes. The Keep window remains until you remove all data items.\nNOTE\nA full discussion of the Keep window is described in COBOL Debugging Programs. Now look at the contents\nof TASKNUM. It does not contain a valid packed decimal value. Instead, it contains low-values (binary zeros).\nCOBOL does not allow you to add a value to a field without initializing it.\nDynamically Change the Value in TASKNUM\nNow that we have identified and confirmed the cause of the problem, we can fix it.\n1.Type M (modify) to the left of TASKNUM in the Keep window, as shown in the following screen.\n2.Press Enter.\n    CA InterTest for CICS   - PROTSYM FILE  ABEND DETECTED BREAKPOINT       \n COMMAND ===>                                                                    \n Program= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n  _____ TASKNUM                         | ?00000.                                \n ---------+--------------------------------------------------------------------- \n  _ 000477 CONTINUE-TASK.                                                        \n    000478**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED                          \n 390", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c83feadd4cb9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  A    ==>     ADD +1 TO TASKNUM.                                                                         \n                      \n \nInterTest for CICS generates a fill-in-the-blanks MOVE statement, as shown in the following screen.\n3.Type zeros in the MOVE field, as shown next, and press Enter.\nNOTE\nYou do not have to know the type of data (binary, packed, and so on) or the length of TASKNUM. The\nInterTest COBOL-like MOVE statement automatically manages the details for you.\n    CA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT      \n COMMAND ===>                                                                    \n Program= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n  _____ TASKNUM                         | ?00000.                                \n ---------+--------------------------------------------------------------------- \n  \n MOVE zeros____________________________________________________________           \n  \n  to                                                                             \n  \n      TASKNUM                                                                    \n  \n Overtype Underscores with a Data-Name, Figurative Constant,                     \n Alphanumeric Literal, or Numeric Literal                                        \n \nInterTest for CICS executes the MOVE statement. As a result, TASKNUM now contains a packed decimal zero.\nInterTest also displays a main storage display that shows the new value of TASKNUM, as shown in the following\nscreen.\n        CA InterTest for CICS   - MAIN STORAGE UTILITY - Termid = U002     \n  \n Starting at Address =2080A138         Structure Display Format                  \n  02 TASKNUM                         |  00000.                    |              \n  02 TASKNUM-CHAR                    | ...                        |              \n  02 TASK-TEXT                       |                            |              \n   03 TASK-ID-NO                     |  000.                      |              \n   03 FILLER                         |                            |", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c83feadd4cb9-1", "text": "03 FILLER                         |                            |              \n   03 TASK-MESG                      | THIS IS A ME               |           \n                                     | SSAGE                      |             \n   03 FILLER                         |                            |             \n   03 TASK-DATE                      |                            |              \n    04 TASK-MM                       | 12                         |              \n    04 TASK-SL1                      | /                          |              \n    04 TASK-DD                       | 25                         |              \n    04 TASK-SL2                      | /                          |              \n    04 TASK-YY                       | 99                         |              \n  \n  \n  ------------------------------------------------------------------------------ \n  PF1 Help       2            3 End        4 Return     5            6 Dump      \n  PF7 Backward   8 Forward    9 Caps Off  10           11 Redisplay 12 Structure \n  CORE=MOVE ZEROS TO TASKNUM                                                     \n 391", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9e81f50d9d80-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  CAIN0201 RECEIVING FIELD has been changed as shown                            \n \nYou can change the contents of a field simply by overtyping the desired bytes in the Keep window or on the main\nstorage display. Overtyping is faster than using an InterTest-generated MOVE statement. However, with the MOVE\nstatement, you do not have to know the internal representation of the data. InterTest automatically takes care of the\ndetails for you.\nNow we return to the program listing to continue to test COBDEMO.\n4.Press Clear.\nInterTest for CICS redisplays the breakpoint screen without the explanation of the abend. Note the new value of\nTASKNUM in the Keep window.\nNOTE\nYou also can correct this bug using indirect commands, which are described Advanced Monitoring Features.\nCOBOL Control Program Execution\nNow that the value in TASKNUM has been properly initialized, the next step might be to continue testing by resuming\nprogram execution. However, this is a good opportunity to learn about another important InterTest feature - the ability to\ncontrol program execution by setting breakpoints.\nHow to Stop Your Program by Setting Breakpoints\nOne of the problems with traditional testing methods is that you have little or no control over program processing. You\ninitiate the task, and the program either runs to completion or abends.\nWith InterTest, you can control program execution in several ways. For example, you can set stops, called breakpoints,\nanywhere in your program. Four types of breakpoints you can set are unconditional, conditional, variable-change, and\nrequest breakpoints.\n\u2022When you set an unconditional  breakpoint at a statement, the program stops before or after the statement is\nexecuted. (Depending on the type of unconditional breakpoint that you set.)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9e81f50d9d80-1", "text": "executed. (Depending on the type of unconditional breakpoint that you set.)\n\u2022When you set a conditional  breakpoint at a statement, the program stops only if a condition you specified is met,\nsuch as a counter equaling or exceeding a specified value. You can also set a conditional breakpoint to stop at an\ninstruction when the condition you specified is met.\n\u2022When you set a variable-change  breakpoint, the program stops at an instruction if the value of the variable you specify\nchanges. This is a special type of conditional breakpoint.\n\u2022When you set a request breakpoint , the program stops before all CICS commands, macros, and other program calls,\nsuch as calls to DL/I or DB2. The program also stops before specific CICS commands, such as all READ or WRITE\ncommands.\nWhat You Can Do When Your Program Is Stopped\nOnce a program is stopped, you can use the InterTest testing and debugging facilities to do the following tasks:\n\u2022Examine the source listing\n\u2022Examine and modify main and auxiliary storage to detect and correct errors\n\u2022Set and remove breakpoints\n\u2022Examine a program backtrace, or execution path\n\u2022Keep data items in a Keep window to observe changes in their values\n\u2022Abend your task with or without a dump\n\u2022To go around a problem, resume program execution from a location other than the one at which the program is\nstopped\n\u2022Execute the program in single-step mode; that is, the program executes one verb and then stops\n 392", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a96cd1054987-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNow we are going to demonstrate how easy it is to control program execution by setting an unconditional breakpoint.\nCOBOL Set Unconditional Breakpoints\nYou can set unconditional breakpoints directly on the Source Listing screen as easily as you displayed and modified\nTASKNUM. Enter U or ) to the left of each statement where you want the application to halt program execution. The U\nsets a breakpoint that stops before  the instruction is executed. The ) sets a breakpoint that stops after the instruction is\nexecuted.\nHere is how to set a \"before\" breakpoint at the following IF statement:\n IF TASKNUM GREATER 2\n \n1.Type U to the left of the statement number on the IF TASKNUM GREATER 2 line, as shown in the following screen.\n2.Press Enter.\n    CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT      \n COMMAND ===>                                                                    \n Program= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n  _____ TASKNUM                         |  00000.                                \n ---------+--------------------------------------------------------------------- \n  _ 000477 CONTINUE-TASK.                                                        \n    000478**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED                          \n   A    ==>     ADD +1 TO TASKNUM.  \n  _ 000480     IF TASKNUM = 1                                                    \n  _ 000481         MOVE 'DMAPASR'  TO MAPNAME.                                   \n  _ 000482     IF TASKNUM = 2                                                    \n  _ 000483         MOVE 'DMAPSUM'  TO MAPNAME.                                  \n  u 000484     IF TASKNUM GREATER 2    \n \n3.Type the GO command on the command line or press PF5 to continue execution from where the program is currently", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a96cd1054987-1", "text": "stopped (at the statement ADD +1 TO TASKNUM).\nInterTest for CICS resumes program execution and continues until the breakpoint that you set is reached. InterTest\nhalts the program before that statement is executed and displays the following screen:\n    CA InterTest for CICS  - PROTSYM FILE  UNCOND  BEFORE BREAKPOINT      \n COMMAND ===>                                                                   \n Program= COBDEMO  Option #       Stmt #                             Margin= 01 \n                                         Search=                                \n -------------------------------------------------------------------------------\n  _____ TASKNUM                         | +00001.                               \n ---------+---------------------------------------------------------------------\n  _ 000482     IF TASKNUM = 2    \n  _ 000483         MOVE 'DMAPSUM'  TO MAPNAME.                                  \n   U    ==>     IF TASKNUM GREATER 2   \n  _ 000485         GO TO SEND-END-MSG. \n .\n .\n .\n \nNote the U to the left of the highlighted statement. The U identifies the breakpoint as an unconditional \"before\"\nbreakpoint. For an \"after\" breakpoint, the application displays a ). For an automatic, conditional, variable-change, or\nrequest breakpoint, the application displays an A, C, V , or R, respectively.\n 393", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "59c3985fe488-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nThe value of TASKNUM is now 1 because the ADD +1 TO TASKNUM statement executed successfully.\nWhen you are stopped at a breakpoint, you can do the following tasks:\n\u2022Scroll or search through your source listing\n\u2022Examine and modify main and auxiliary storage\n\u2022Add a data item to the Keep window using the K line command\n\u2022Set and remove breakpoints\n\u2022Examine the program backtrace summary\n\u2022Abend your task (with or without a dump)\n\u2022Go around a problem by resuming program execution from another location. (Type G next to the instruction where you\nwant to resume.)\nWhen debugging your own programs, you will typically perform one or more of these activities, which are described in\ndetail in the next article. However, COBDEMO does not have any more errors, so we are going to complete the demo\nsession.\nAs you continue testing and debugging, clean up by removing unneeded breakpoints so that the program does not\nstop when you retest. Next, remove the unconditional breakpoint that you set so that COBDEMO does not stop at this\nstatement when re-executed.\nRemove Breakpoints from the Status Display\nIf you want, you can also remove a breakpoint from the Status display:\n1.Type STATUS on the command line.\n2.Press Enter.\nInterTest for CICS displays the Monitoring Status screen:\n ---------------  CA InterTest for CICS   MONITORING STATUS  -------------\n  COMMAND ===>                                                                  \n  \n    Type + to expand or - collapse option levels displayed below,               \n           or R to remove option(s).                                            \n  \n      Option     Description                Attributes                          \n  _ - COBDEMO    Program monitor entry      IBMCOB 3.2", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "59c3985fe488-1", "text": "_ - COBDEMO    Program monitor entry      IBMCOB 3.2                          \n      |          Waiting at breakpoint      Task 00040, UBP since 06:48 p.m.    \n  _ - |-.ANY     User monitoring options    Active                              \n        |        Symbolic listing file      PROTSYM                             \n  _ -   |-UBP    Unconditional breakpoint   #484                                \n        |        Option ID                  80258747                            \n        |        From, to terminals         U002, U002                          \n  _     |-SLB    Source listing breakpoints U002                                \n                 *** End of data ***                                            \n  \n  \n PF1 Help       2 Refresh    3 End        4 Return     5 Collapse   6 Expand   \n PF7 Backward   8 Forward    9           10           11           12         \n \n3.Type R to the left of the unconditional breakpoint (UBP).\n4.Press Enter.\nAn asterisk displays next to the breakpoint, indicating that a command has been processed for it.\n5.Press PF2 to refresh the screen.\n 394", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c0d8bb105b02-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe unconditional breakpoint is no longer displayed.\n6.Press PF3 to return to the Source Listing Breakpoint screen.\nResume Program Execution\n1.Press PF5 to continue program execution.\nInterTest for CICS resumes program execution. COBDEMO displays a screen confirming that you have successfully\ncorrected the ASRA.\n2.Press Enter.\nCOBDEMO displays the following screen.\n **********************************************************************    \n ****                                                              ****    \n ****             CA InterTest Demo Session                        ****    \n ****                                                              ****    \n **********************************************************************    \n  \n  \n     You have completed the sample CA InterTest test session.As part of    \n this session, you:                                                        \n  \n       * displayed program source code and compiler output online          \n       * displayed and modified main storage                               \n       * controlled program execution                                      \n  \n     This is just a fraction of CA InterTest's capabilities. You can also: \n  \n       * display or modify any CICS file, or DL/1, DB2, or SQL/DS database \n       * set and remove many kinds of monitoring options                   \n  \n  \n  \n         Press ENTER or CLEAR to complete the termination.                \n  \n \nThis screen reminds you that we have touched on just a few of InterTest's powerful yet easy-to-use testing and\ndebugging facilities.\n3.To complete this part of the sample test session, press Clear or Enter to clear your screen.\nWhat You Have Learned\nThis demo session has taught you the basics of using InterTest to test a program.\nYou learned how to perform the following tasks:\nSelect a source program for display\nGo to ITST Menu Option 1.1. Select a program from the list.\nSet monitoring for a program\nUse the MONITOR command or PF5 from Source Listing.\nView a Monitoring Status display", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c0d8bb105b02-1", "text": "Use the MONITOR command or PF5 from Source Listing.\nView a Monitoring Status display\nUse the STATUS command or PF12 from Source Listing.\nInterpret the information that the application provides when an error is detected\nView the Automatic Breakpoint and press PF1 for help.\n 395", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bf382f31a99d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nExamine the value of a data item in a Keep window\nView the data in the AutoKeep Display window.\nModify main storage\nOvertype the value in the Keep Window or type D to the left of a variable. Place the cursor under the variable and\npress Enter for a CORE Main Storage display. On the CORE screen, overtype the values and press Enter.\nSet an uncondition\nal \"before\" breakpoint\nType U to the left of an instruction and press Enter.\nRemove a breakpoint from the Monitoring Status display\nUse PF12 to view Monitoring Status. Type R next to a UBP and press Enter.\nRemove a breakpoint from the Source Listing Display\nOn Source Listing, overtype U with X and press Enter.\nResume program execution\nUse the RESUME command or PF5.\nCOBOL Debugging Programs\nThis article provides an overview of key InterTest for CICS functions.\nFor complete information, see CICS Debugging and the Help facility.\nChecklist of Basic Debugging Tasks\nThe following list highlights basic debugging tasks:\n\u2022Display the source listing.\n\u2022Set monitoring for the program.\n\u2022Set breakpoints.\n\u2022Set other monitoring options as needed.\n\u2022Initiate the program.\n\u2022End the test session.\nWhen the program is stopped at a breakpoint, you can perform the following procedures:\n\u2022Inspect and modify main storage\n\u2022Inspect and modify auxiliary storage\n\u2022Set and remove breakpoints\n\u2022Keep data items in the Keep window to observe changes in their values\n\u2022Resume execution\n\u2022Abend the task\nNOTE\nBefore you read this article, you should have performed the Basic Demo Session described in the previous\narticle. The demo session provides a basic introduction to InterTest and illustrates many of the functions\ndiscussed in this article.\nDisplay Your Source Listing", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bf382f31a99d-1", "text": "discussed in this article.\nDisplay Your Source Listing\nYou can display your source listing online at any time from CICS through the ITST transaction or the LIST=progname\ntransaction (where progname  is the program name). The Basic Demo explains how to display a source listing using the\nITST transaction. For additional information on how to use LIST=, see CICS Debugging.\n 396", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4188ef30eb1a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nThe standard InterTest transaction IDs, such as LIST, ITST, CORE, and FILE, might have been changed at your\nsite. If any of the transactions mentioned in this article do not function as described, contact the person who\ninstalled InterTest.\nNOTE\nDepending on your defaults, the options and PF keys available to you might not be displayed at the top of the\nSource Listing Display. If this information is not displayed, you can view it by pressing PF4 to access the Profile\nscreen, and then setting Display window to T.\nDisplay Sections of Your Program\nThe options (OPTS) available at the Source Listing screen make it easy to display any section of your COBOL program.\nThe following table shows what program sections are displayed when you use the LOCATE command or option numbers:\nCommand Option # Section\nL .PD 1 Procedure Division\nL .WS 2 Working Storage Section\nL .LS 3 Linkage Section\nL .DM 4 Data Division Map\nL .PM 5 Clist/Pmap\nL .DX 6 Data Name Cross Reference\nL .PX 7 Procedure Cross Reference\nL .EM 8 Error Messages\nL .LC 13 Local-Storage Section\nSearch for Strings and Labels\nYou can also search for and display a character string by typing a FIND string NEXT/PREV command on the command\nline or option 9 (Search forward) or 10 (Search backward) in the Option # field and typing the character string in the\nSearch field. For example, the following screen illustrates how you would search backward for the string custname .\n    CA InterTest for CICS   - PROTSYM FILE  SOURCE LISTING DISPLAY         \n COMMAND ===> f custname prev                                                    \n Program= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4188ef30eb1a-1", "text": "Search=                                 \n ---------+--------------------------------------------------------------------- \n  _ 000911 VSAM-REWRITE.                                                         \n  _ 000912     MOVE 'THIS IS NOT A NAME  ' TO VSAM-NAME.                         \n    000913*EXEC CICS REWRITE                                                     \n    000914*     DATASET(TASK-PROTCPF)                                            \n    000915*     FROM(VSAM-AREA)                                                  \n    000916*     LENGTH(REC-LEN)                                                  \n    000917*     END-EXEC.                                                        \n  _ 000918     Call 'DFHEI1' using by content x'0606e0000700004000f0f0f5f2f4    \n \nStart a Test Session\nTo start a test session, follow these steps:\n1.Turn on monitoring.\n 397", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dc26302f1b09-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n2.Execute the program.\nTurn on Monitoring\nTo test a program, you must instruct InterTest for CICS to monitor it. When InterTest for CICS monitors a program, it\ndetects and prevents errors before they occur, including the following violations:\n\u2022All storage violations\n\u2022All CICS abends\n\u2022Any statement that would cause a program check or other abend\n\u2022All illegal or invalid instructions that would cause CICS to crash\n\u2022All wild branches\n\u2022All violations of CICS standards\nThe easiest way to turn on monitoring is from the program's source listing. Perform the following steps:\n1.Display the source listing as described previously. InterTest displays the Source Listing Display screen for the\nprogram.\n2.Press PF5 to set monitoring, which remains in effect for the program until specifically removed.\nExecute a Program\nOnce you have turned on monitoring for a program, you are ready to execute it. Perform the following actions:\n1.Press PF3 to exit the Source Listing facility. If you entered Source Listing from an ITST menu, you return to that menu.\n2.To exit the ITST menus, type =X in the top field and press Enter. The ITST transaction ends and you return to CICS.\nNOTE\nBefore returning to CICS, you may want to set breakpoints directly on the source listing, as described in\nSetting and Removing Breakpoints.\n3.On a clear CICS screen, type the transaction identifier of the program you are monitoring.\nOnce you enter the program's transaction ID, one of the following occurs:\n\u2022Your program runs to completion. The results might not be correct.\n\u2022InterTest for CICS stops your program at a breakpoint -- either one set by you or one automatically triggered by\nInterTest for CICS because it detected an error.\nSet and Remove Breakpoints", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dc26302f1b09-1", "text": "InterTest for CICS because it detected an error.\nSet and Remove Breakpoints\nWhen you test a program, it is important to be able to halt program execution at specified locations. A halt in program\nexecution is called a breakpoint .\nWhat You Can Do at a Breakpoint\nWhen your program is stopped at a breakpoint, you can do the following actions:\n 398", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c5fe7aa65e00-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Examine the source listing\n\u2022Inspect and modify main storage\n\u2022Inspect and modify auxiliary storage\n\u2022Set and remove breakpoints\n\u2022Examine the backtrace\n\u2022Keep data items in the Keep window to observe changes in their values\n\u2022Set and remove monitoring options\n\u2022Specify indirect commands\n\u2022Resume execution\n\u2022Abend the task\nWe have already discussed how you can examine your source listing. The other breakpoint activities are discussed in this\nand the next article.\nTypes of Breakpoints\nThere are six types of breakpoints, as shown in the following table:\nAutomatic\nThe program stops because InterTest detected and prevented an error.\nUnconditional\nThe program stops at the location you specify.\nConditional\nThe program stops at the location you specify if a condition is met. Optionally, conditional breakpoints can be set\nto stop at any instruction if a condition is met.\nVariable-change\nThe program stops at any location if the value of a specified variable has changed.\nRequest\nThe program stops at every CICS command or macro, or at certain CICS commands or macros, or at calls to DL/\nI, DB2, or software.\nSingle-step\nThe program stops after executing one or more verbs.\nIn this section we are going to explain how to set and remove unconditional breakpoints as well as variable-change\nbreakpoints, because you will use these the mostAn automatic breakpoint occurs when InterTest for CICS detects an\nerror. When a program is stopped at an automatic breakpoint, you can either correct the error or go around it. You can\npress PF1 to find out what caused the error and how to use InterTest to fix it. You set all other breakpoints.\nFor more information on conditional and request breakpoints and on single-stepping, see COBOL Advanced Monitoring\nFeatures. The following sections explain how to set breakpoints:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c5fe7aa65e00-1", "text": "Features. The following sections explain how to set breakpoints:\n\u2022Set breakpoints at statements on the source listing\n\u2022Set breakpoints at all references to a data name\n\u2022Set breakpoints at all or selected paragraph names\nSet Unconditional Breakpoints at Statements on the Source Listing\nTo set an unconditional breakpoint on the program source listing, follow these steps:\n1.Type U or ) next to the statement where you want the breakpoint. The U sets a breakpoint that stops before  the\nstatement is executed. The ) sets a breakpoint that stops after the statement is executed.\n2.Press Enter.\nThe following screen shows how to set an unconditional \"before\" breakpoint.\n 399", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "25b4eb56c004-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    CA InterTest for CICS  - PROTSYM FILE  SOURCE LISTING DISPLAY        \n COMMAND ===>                                                                    \n Program= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n OPTS 1 Proc div  2 Work-stor 3 Link sect  4 D-map      5 Clst/Pmap More:   +    \n      6 Data xref 7 Proc xref 8 Err msgs   9 Srch fwd  10 Srch bwd               \n PFKS 1 Help      2           3 End        4 Profile    5 Monitor    6 Menu      \n      7 Backward  8 Forward   9 Next Wnd  10           11           12 Status    \n ------------------------------------------------------------------------------- \n  _ 000475     IF EIBAID = DFHPF14  GO TO EXPANDED-DEMO.                         \n  _ 000476     GO TO SEND-FIRST-SCREEN.                                          \n  _ 000477 CONTINUE-TASK.                                                        \n    000478**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED                          \n  _ 000479     ADD +1 TO TASKNUM.                                                \n  u 000480     IF TASKNUM = 1                                                 \n \nAfter you set a breakpoint, InterTest for CICS redisplays the screen with an uppercase U or a ). This character remains\nuntil you remove the breakpoint.\nYou can set breakpoints at any time -- before you execute the program and when the program is stopped. Although\nwhere you decide to set breakpoints depends on the specifics of your program, you might want to set breakpoints in\nthe following places:\n\u2013At the beginning of the Procedure Division, so when the program executes you can set additional breakpoints", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "25b4eb56c004-1", "text": "\u2013At the beginning of the Procedure Division, so when the program executes you can set additional breakpoints\n\u2013At paragraph names, so you can examine the contents of variables at the start of sections\n\u2013Before a call, so you can dynamically control the program path\n\u2013At each location named in an EXEC CICS HANDLE CONDITION, so you can verify error handling\nTo remove an unconditional breakpoint, overtype the U or ) with an X, or type R next to the breakpoint entry on the\nMonitoring Status display (PF12 from Source Listing). You will want to remove breakpoints no longer needed so that\nwhen retesting the program, you are not stopped unnecessarily.\nSet Unconditional Breakpoints at All References to a Data Name\nYou can set unconditional breakpoints at all references to a data name from the Cross Reference section.\n1.Type L .DX  in the command line or 6 in the Option # field on the Source Listing screen, as shown next, and press\nEnter.\n    CA InterTest for CICS - PROTSYM FILE  SOURCE LISTING DISPLAY        \n COMMAND ===> l .dx                                                              \n Program= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n OPTS 1 Proc div  2 Work-stor 3 Link sect  4 D-map      5 Clst/Pmap More:   +    \n      6 Data xref 7 Proc xref 8 Err msgs   9 Srch fwd  10 Srch bwd               \n PFKS 1 Help      2           3 End        4 Profile    5 Monitor    6 Menu      \n      7 Backward  8 Forward   9 Next Wnd  10           11           12 Status    \n ------------------------------------------------------------------------------- \n  _ 000477 CONTINUE-TASK.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "25b4eb56c004-2", "text": "------------------------------------------------------------------------------- \n  _ 000477 CONTINUE-TASK.                                                        \n    000478**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED                          \n  _ 000479     ADD +1 TO TASKNUM.                                                \n \nInterTest displays the Dataname Cross Reference section, as shown next.\n2.Now type U or ) to the left of the data names for which you want to set unconditional breakpoints and press Enter. The\nU sets a breakpoint that stops before  the statement is executed. The ) sets a breakpoint that stops after the statement\nis executed.\n 400", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f9e3fe049ed9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe following screen shows how to set an unconditional \"before\" breakpoint.\n    CA InterTest for CICS - PROTSYM FILE  SOURCE LISTING DISPLAY        \n COMMAND ===>                                                                    \n Program= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n OPTS 1 Proc div  2 Work-stor 3 Link sect  4 D-map      5 Clst/Pmap More:   +    \n      6 Data xref 7 Proc xref 8 Err msgs   9 Srch fwd  10 Srch bwd               \n PFKS 1 Help      2           3 End        4 Profile    5 Monitor    6 Menu      \n      7 Backward  8 Forward   9 Next Wnd  10           11           12 Status    \n ----------------------------------------+-------------------------------------- \n  _   DEF DATA NAMES                     REFERENCES                              \n  _     32 TASK-PROTCPF                  M421 909 919                            \n  _     33 TASK-PROTHLF                  M422 761                                \n  _     47 TASK-SL1                                                              \n  _     49 TASK-SL2                                                              \n  u     30 TASK-STRUCTURE                391 448 496 520 658 867 879 925 993     \n  _     51 TASK-STRUCTURE-2              659                                     \n  u     34 TASK-SWITCH                   398 M438 M556                          \n \n3.To remove  the breakpoints, overtype the U with X. You can remove all the breakpoints for a data name from the Cross\nReference section, or you can selectively remove breakpoints at specific statements. You can also remove individual", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f9e3fe049ed9-1", "text": "Reference section, or you can selectively remove breakpoints at specific statements. You can also remove individual\nor multiple breakpoints from the Monitoring Status display. You might want to do this when you have a number of\nbreakpoints set throughout a large program and do not want to hunt through the source listing for them.\nIf your source listing does not include the Cross Reference section, you can also set a breakpoint at all references to a\ndata name from the Working-Storage section where the data name is defined.\n1.To display the definition, type the data name in the Search= field and press Enter.\n2.When InterTest displays the definition, type U to the left of the statement, as shown next, and press Enter .\n    CA InterTest for CICS - PROTSYM FILE  SOURCE LISTING DISPLAY         \n COMMAND ===>                                                                    \n Program= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n OPTS 1 Proc div  2 Work-stor 3 Link sect  4 D-map      5 Clst/Pmap More:   +    \n      6 Data xref 7 Proc xref 8 Err msgs   9 Srch fwd  10 Srch bwd               \n PFKS 1 Help      2           3 End        4 Profile    5 Monitor    6 Menu      \n      7 Backward  8 Forward   9 Next Wnd  10           11           12 Status    \n ------------------------------------------------------------------------------- \n  _ 000035     03 TASK-SWITCH2          PIC 99.                                  \n  _ 000036     03 TASK-SWITCH3          PIC X.                                   \n  u 000037     03 TASKNUM               PIC S9(5)  COMP-3.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f9e3fe049ed9-2", "text": "_ 000038     03 TASKNUM-CHAR REDEFINES TASKNUM PIC X(3).                       \n  _ 000039     03 TASK-TEXT.                                                     \n  _ 000040        05 TASK-ID-NO         PIC 9(3)  COMP-3  VALUE 0.              \n \nIn this example, InterTest sets \"before\" breakpoints at all references to TASKNUM.\n3.To remove the breakpoints, overtype the U with X, or remove the breakpoints from the Monitoring Status display.\nSet Unconditional Breakpoints at Paragraph Names\nYou can set unconditional breakpoints at all procedures and all labels.\n 401", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "addbef8471fb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFollow these steps:\n1.To set unconditional breakpoints at all Procedure Names and All Labels, display the Cross Reference Table using\nOption # 1 (or L .DX command), type a U or a ) next to the DCL heading line, and press Enter. The U sets a breakpoint\nthat stops before  the specified location. The ) sets a breakpoint that stops after the specified location.\nA message prompts you to confirm the request for setting many breakpoints by pressing PF3.\nIt is easy to set unconditional breakpoints at all or selected paragraph names from the Procedure Names section.\n2.To display the Procedure Names, type L .PX  in the command line or a 7 in the Option # field on the Source Listing\nscreen, as shown next, and press Enter.\n    CA InterTest for CICS - PROTSYM FILE  SOURCE LISTING DISPLAY         \n COMMAND ===>  l .px                                                             \n Program= COBDEMO Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n OPTS 1 Proc div  2 Work-stor 3 Link sect  4 D-map      5 Clst/Pmap More:   +    \n      6 Data xref 7 Proc xref 8 Err msgs   9 Srch fwd  10 Srch bwd               \n PFKS 1 Help      2           3 End        4 Profile    5 Monitor    6 Menu      \n      7 Backward  8 Forward   9 Next Wnd  10           11           12 Status    \n ---------+--------------------------------------------------------------------- \n       XREF(FULL)                                                                \n       ZWB                                                                       \n    000001 ID DIVISION.                                                          \n    000002 PROGRAM-ID. COBDEMO.                                                 \n    000003 ENVIRONMENT DIVISION.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "addbef8471fb-1", "text": "000003 ENVIRONMENT DIVISION.                                                 \n    000004 DATA DIVISION.                                                        \n  _ 000005 WORKING-STORAGE SECTION.                                              \n  _ 000006 77  S999-FIELD1             PIC S9(3).                             \n \nInterTest displays the Procedure Names section.\n3.Type U or ) to the left of the paragraph names for which you want to set unconditional breakpoints. You can also type\nU or ) on the PROCEDURE NAMES line, to set breakpoints at all paragraph names, as shown in the following screen:\n    CA InterTest for CICS  - PROTSYM FILE  SOURCE LISTING DISPLAY         \n COMMAND ===>                                                                    \n Program= COBDEMO Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ----------------------------------------+-------------------------------------- \n  _ DEFINED      PROCEDURE NAMES         REFERENCES                              \n  _    982 AFTER-REWRITE                                                         \n  _    858 CICS-LOOP                     P856                                \n \n4.To remove the breakpoints, overtype the U or ) with X. You can also remove the breakpoints from the Monitoring\nStatus display.\nNOTE\nA message warns you if your specification sets more than 20 breakpoints. You can then either confirm or\ncancel the breakpoints.\nInspect and Modify Main Storage\nThe ability to inspect main storage at a breakpoint means you can determine the values of data items without using a\ndump. It is easy to find logic errors because you can display the value of a data item where it is defined and at any point in\nthe code where it is referenced. And, you can dynamically change its value to correct errors or test other program paths.\nRemember that changes to program storage are dynamic ; that is, the change affects only the current test session. To\ncorrect program errors, you must change the source code and recompile the program.\n 402", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dc69f46ca3b7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThere are many ways to inspect and modify main storage. We are going to discuss one of the easiest methods of viewing\nand changing program storage here. Keeping Data Items in the Keep window explains another easy way to display and\nmodify the values of data items.\nRemember, you can inspect system storage at any time, independent of program monitoring and execution.\nDisplay the Value of a Data Item\nWhen you are stopped at a breakpoint, you can request the display of the value of a data item directly from the source\nlisting.\n1.To display its value where it is defined , type D to the left of the statement defining it and press Enter, as shown in the\nfollowing screen.\n    CA InterTest for CICS - PROTSYM FILE  UNCOND  BEFORE BREAKPOINT       \n COMMAND ===>                                                                    \n Program= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n  _____ TASKNUM                         | ?00000.                                \n ---------+--------------------------------------------------------------------- \n  _ 000035     03 TASK-SWITCH2          PIC 99.                                  \n  _ 000036     03 TASK-SWITCH3          PIC X.                                   \n  U 000037     03 TASKNUM               PIC S9(5)  COMP-3.                       \n  _ 000038     03 TASKNUM-CHAR REDEFINES TASKNUM PIC X(3).                       \n  _ 000039     03 TASK-TEXT.                                                     \n  _ 000040        05 TASK-ID-NO         PIC 9(3)  COMP-3  VALUE 0. \n .\n .\n .         \n \n2.To display the value of a data item where it is referenced , type D to the left of the statement referencing it, place the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dc69f46ca3b7-1", "text": "cursor under any character in the data item, and press Enter .\nInterTest responds by displaying the contents of the data item in structured format, as shown next.\n       CA InterTest for CICS - MAIN STORAGE UTILITY - Termid = U087      \n  \n Starting at Address =2080A138         Structure Display Format                  \n  02 TASKNUM                         | ?00000.                    |              \n  02 TASKNUM-CHAR                    | ...                        |              \n  02 TASK-TEXT                       |                            |              \n   03 TASK-ID-NO                     |  000.                      |              \n   03 FILLER                         |                            |              \n   03 TASK-MESG                      | THIS IS A ME               |              \n                                     | SSAGE                      |              \n   03 FILLER                         |                            |              \n   03 TASK-DATE                      |                            |              \n    04 TASK-MM                       | 12                         |              \n    04 TASK-SL1                      | /                          |              \n    04 TASK-DD                       | 25                         |              \n    04 TASK-SL2                      | /                          |              \n    04 TASK-YY                       | 99                         |              \n  \n  \n  ------------------------------------------------------------------------------ \n  PF1 Help       2            3 End        4 Return     5            6 Dump      \n 403", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "202eaad90b19-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  PF7 Backward   8 Forward    9 Caps Off  10           11 Redisplay 12 Structure \n  CORE='TASKNUM'                                                                 \n  CAIN0452 FIELD DOES NOT CONTAIN A VALID PACKED DECIMAL (COMP-3) VALUE      \n \nNOTE\nInterTest displays more than just the contents of the specified data item (TASKNUM); it also displays all the\nitems below it in the same COBOL structure.\n3.Press Clear or PF3 to return to the source listing.\nModify the Value of a Data Item\nYou can modify the value of a data item by overtyping the bytes in the main storage display and pressing Enter. For\nexample you could change the contents of TASKNUM in the previous figure by overtyping the question mark with a zero,\nInterTest takes care of the datatype appropriate internal conversion automatically.\nModify the Value of a Data Item Using the MOVE Statement\nOvertyping the main storage display is the easiest way to change the value of a data item. However, you want to use the\nInterTest COBOL-like MOVE statement to modify a data item when you do not know the type of data (binary, packed, and\nso on) or its length. The MOVE statement takes care of all the details for you. Use the MOVE statement as follows:\n1.To modify a data item where it is defined , type M to the left of the statement defining it and press Enter. For example,\nto modify the value of TASKNUM, you would type M instead of D.\n2.If you type  M to the left of multiple lines, InterTest generates multiple MOVE statements.\n3.To modify a data item where it is referenced , type M to the left of the statement referencing it, place the cursor under\nany character in the data item, and press Enter.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "202eaad90b19-1", "text": "any character in the data item, and press Enter.\nInterTest generates and displays a fill-in-the-blanks MOVE statement, as shown in the following screen:\n    CA InterTest for CICS - PROTSYM FILE  UNCOND  BEFORE BREAKPOINT      \n COMMAND ===>                                                                    \n Program= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n  _____ TASKNUM                         | ?00000.                                \n ---------+--------------------------------------------------------------------- \n  \n MOVE ________________________________________________________________           \n  \n  to                                                                             \n  \n      TASKNUM                                                                    \n  \n Overtype Underscores with a Data-Name, Figurative Constant,                     \n Alphanumeric Literal, or Numeric Literal                                       \n \n4.Type one of the following items in the MOVE field:\n\u2013A variable name, such as NEXT-TASKNUM\n\u2013One of the following COBOL-like keywords: ZEROS, SPACES, LOW-VALUES, HIGH-VALUES, QUOTES\n\u2013An alphanumeric literal enclosed in single quotes, such as 'YES'\n\u2013A numeric literal, with or without a leading plus, +, or minus sign, -, such as -8.\n5.Press Enter to execute the MOVE statement. InterTest displays a main storage display showing the new value of the\ndata item. If you execute several MOVE statements, InterTest shows the main storage displays one at a time. Press\nClear to see the next one.\n 404", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aff1cb6e1f0f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n6.From the main storage display, press Clear or PF3 to return to the source listing.\nKeeping Data Items in the Keep Window\nThe Keep window lets you display the values of an unlimited number of data items directly on the source listing. If more\nthan six variables are selected for the Keep window, PF19 and PF20 are available to scroll forward and backward\nthroughout the Keep window. Keeping data items in the window lets you observe changes in their values as the program\nexecutes. You also can change values by overtyping the displayed bytes.\nThe Keep window consists of two parts. Dynamic  keep elements are those that consist of the variables based on the\ncurrent line of code. They are automatically displayed using the AutoKeep Display profile feature. They are shown in a\nhighlighted fashion. Static  keep elements are those that remain in the Keep window for the duration of the execution of\nthe program until you remove them. The static  keep elements are displayed before the dynamic  elements. Use scrolling\nto view all the elements. You can change any dynamic  element to a static  element simply by following the rules mentioned\nnext.\nWhen the Keep window is active, the options and PF key functions are not displayed. Press PF4 if you need to refer to\nthem. When all the data items in the Keep window are removed, the options and PF key functions are redisplayed. A\ncommand line is available to help you perform InterTest functions when the Keep window is active.\nAdd a Data Item to the Keep Window (static keep element)\nYou can add data items to the Keep window whenever your source listing is displayed. Identify the data items whose\nvalues you want to observe either before you execute the program, or when you are at a breakpoint.\nFollow these rules to add a data item to the Keep window:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aff1cb6e1f0f-1", "text": "Follow these rules to add a data item to the Keep window:\n\u2022To add a data item where it is defined, type K to the left of the statement defining it, and press Enter.\n\u2022To add a data item where it is referenced, type K to the left of the statement referencing it, place the cursor under any\ncharacter in the item, and press Enter.\nWhen you add a data item to the Keep window, InterTest responds by displaying the data item, as shown next.\n     CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT    \n  \n COMMAND ===>                                                                   \n Program= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n  _____ EIBTRNID                        | DEMC                                  \n  _____ EIBTRMID                        | U087                                   \n  _____ TASKNUM                         | ?00000.                                \n ---------+--------------------------------------------------------------------- \n  _ 000477 CONTINUE-TASK.                                                        \n    000478**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED                          \n  A    ==>     ADD +1 TO TASKNUM. \n \nDisplay the Data Item Structure\nTo display the entire COBOL structure of a data item, type a d to the left of the data item in the window and press Enter,\nas shown next.\n    CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT      \n COMMAND ===>                                                                   \n Program= COBDEMO  Option #       Stmt #                             Margin= 01 \n                                         Search=                                \n 405", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5bae7a828afd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n -------------------------------------------------------------------------------\n  _____ EIBTRNID                        | DEMC                                  \n  _____ EIBTRMID                        | U087                                  \n  d____ TASKNUM                         | ?00000.                               \n ---------+---------------------------------------------------------------------\n  _ 000477 CONTINUE-TASK.                                                       \n    000478**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED                         \n  A    ==>     ADD +1 TO TASKNUM.                               \n \nInterTest responds by displaying the data item and all the items below it in the same COBOL structure.\nModify the Value of a Data Item\nModify the value of a data item in the Keep window by doing the following actions:\n\u2022Overtyping the displayed bytes, just as you would overtype the bytes in a main storage display\n\u2022Typing M to the left of the data item to use the InterTest MOVE statement. Both methods of modifying a data item are\ndiscussed in the section, Inspecting and Modifying Main Storage.\nNOTE\nIf you try to change password-protected storage areas not owned by your program, InterTest prompts you to\nenter the password.\nRemove a Data Item from the Keep Window\nTo remove a data item from the Keep window, type X to the left of the data item, as shown in the following screen:\n    CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT      \n COMMAND ===>                                                                    \n Program= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n  x____ EIBTRNID                        | DEMC                                   \n  x____ EIBTRMID                        | U087                                   \n  _____ TASKNUM                         | ?00000.                                \n ---------+--------------------------------------------------------------------- \n  _ 000477 CONTINUE-TASK.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5bae7a828afd-1", "text": "---------+--------------------------------------------------------------------- \n  _ 000477 CONTINUE-TASK.                                                        \n    000478**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED                          \n  A    ==>     ADD +1 TO TASKNUM.                            \n \nIn this example two data items (EIBTRNID and EIBTRMID) will be removed from the Keep window.\nWhen all data items have been removed, the Keep window no longer displays.\nUse Variable-Change Breakpoints to Detect Changing Values\nYou can request that InterTest for CICS halt execution whenever the value of a specified data item changes. This is called\na variable-change breakpoint.\nSet a Variable-Change Breakpoint\nA quick way to set a variable-change breakpoint is from the point in the listing where it is defined. In the following\nexample, you will set a variable-change breakpoint on TSQ-TERMID.\n 406", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "177ca70823a4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFollow these steps:\n1.Position the listing at the definition for TSQ-TERMID by typing L TSQ-TERMID in the Command line field, and press\nEnter.\n    CA InterTest for CICS  - PROTSYM FILE  SOURCE LISTING DISPLAY          \n COMMAND ===> L TSQ-TERMID                                                       \n Program= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n OPTS 1 Proc div  2 Work-stor 3 Link sect  4 D-map      5 Clst/Pmap More:   +    \n      6 Data xref 7 Proc xref 8 Err msgs   9 Srch fwd  10 Srch bwd               \n PFKS 1 Help      2           3 End        4 Profile    5 Monitor    6 Menu      \n      7 Backward  8 Forward   9 Next Wnd  10           11           12 Status    \n ------------------------------------------------------------------------------- \n       YEARWINDOW(1900)                                                          \n       ZWB                                                                       \n    000001 ID DIVISION.                                                          \n    000002 PROGRAM-ID. COBDEMO.                                                  \n    000003 ENVIRONMENT DIVISION.                                                 \n    000004 DATA DIVISION.                                                        \n  _ 000005 WORKING-STORAGE SECTION.                                           \n \n2.The listing is then positioned at the definition for the TSQ-TERMID. Type V to the left of the statement defining the\nTSQ-TERMID field, position the cursor on the TSQ-TERMID field, and press Enter .\n    CA InterTest for CICS - PROTSYM FILE  SOURCE LISTING DISPLAY         \n COMMAND ===>                                                                   \n Program= COBDEMO  Option #       Stmt #                             Margin= 01 \n                                         Search=", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "177ca70823a4-1", "text": "Search=                                \n OPTS 1 Proc div  2 Work-stor 3 Link sect  4 D-map      5 Clst/Pmap More:   +   \n      6 Data xref 7 Proc xref 8 Err msgs   9 Srch fwd  10 Srch bwd              \n PFKS 1 Help      2           3 End        4 Profile    5 Monitor    6 Menu     \n      7 Backward  8 Forward   9 Next Wnd  10           11           12 Status   \n -------------------------------------------------------------------------------\n  _ 000027 01  TSQ-NAME.                                                        \n  _ 000028     03 TSQ-TRANID            PIC XXXX.                               \n  v 000029     03 TSQ-TERMID            PIC XXXX.                               \n  _ 000030 01  TASK-STRUCTURE.                                                  \n  _ 000031     03 TASK-CNTL             PIC X(4)  VALUE 'CNTL'.                 \n  _ 000032     03 TASK-PROTCPF          PIC X(8)  VALUE 'PROTCPF'.              \n  _ 000033     03 TASK-PROTHLF          PIC X(8)  VALUE 'PROTHLF'.              \n  _ 000034     03 TASK-SWITCH           PIC X. \n \n3.Type the DEMC transaction. The following breakpoint displays:Type the DEMC transaction. The following breakpoint\ndisplays:\n    CA InterTest for CICS - PROTSYM FILE   COND  BEFORE  BREAKPOINT    \n COMMAND ===>                                                                  \n Program= COBDEMO  Option #       Stmt #                             Margin= 01\n                                         Search=                               \n -- More:   + ----------------------------------- PFKS 19 Backward 20 Forward -", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "177ca70823a4-2", "text": "-- More:   + ----------------------------------- PFKS 19 Backward 20 Forward -\n  _____ DMAP04AI                        | .....................................\n  _____ DMAPBEGI                        | ............                         \n  _____ DMAPASRI                        | ............                         \n  _____ DMAPSUMI                        | ............                         \n  _____ DMAPENDI                        | .....................................\n 407", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "749a714ba35c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  _____ DMAP00I                         | .....................................\n ---------+--------------------------------------------------------------------\n  _ 000353     MOVE EIBTRMID TO TSQ-TERMID.                                    \n    000354*** THIS CODE INITIALIZES THE MAPS BECAUSE COBOL2 DOESN'T ***        \n  V    ==>     MOVE LOW-VALUES TO DMAP04AI                                     \n      ==>                                                                      \n      ==> CAIN3630 Conditional breakpoint    requested at offset .ANY          \n      ==> IF='TSQ-TERMID'.NE.'TSQ-TERMID'                                      \n      ==>                                                                      \n  _ 000356                  DMAPBEGI                                           \n  _ 000357                  DMAPASRI                                           \n  _ 000358                  DMAPSUMI                                           \n  _ 000359                  DMAPENDI                                           \n  _ 000360                  DMAP00I                             \n \nNOTE\nthe listing is positioned on the statement following that which actually changed TSQ-TERMID, because the\nfield is examined at the beginning of each new COBOL statement.The listing is positioned on the statement\nfollowing that which actually changed TSQ-TERMID, because the field is examined at the beginning of each\nnew COBOL statement.\nA variable-change-breakpoint may be set any time during execution, or from a listing of your program before execution\nbegins. You may find it useful to also set a static keep on the field which you are interested in watching for a change.\nIn this way you will be able see how it changed automatically each time a variable change breakpoint occurs.\nEach variable change breakpoint is identified by the abbreviation VBP on the Status Report and Monitoring Status\ndisplay.\nVariable-change breakpoints are actually a special type of conditional breakpoint. InterTest for CICS checks for the\ncondition at any statement, as shown in the following example:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "749a714ba35c-1", "text": "condition at any statement, as shown in the following example:\n IF 'data-item'.NE.data-item'\n \nwhich means:\n IF data-item (current) NOT EQUAL TO data-item (value when breakpoint set)\n \nTo explore additional ways to set and use conditional breakpoints, see the later articles in this primer.\nRemove a Variable-Change Breakpoint\nFrom the variable-change breakpoint display, overtype the V with an X and press Enter to remove the breakpoint. You can\nalso remove the breakpoint from the Monitoring Status display. Type R next to the VBP option to be removed, and press\nEnter. The following screen shows removing the variable-change breakpoint set on the variable TASKNUM in the program\nCOBDEMO.\n ----------------  CA InterTest for CICS  MONITORING STATUS  ------------\n  COMMAND ===>                                                                   \n  \n    Type + to expand or - collapse option levels displayed below,                \n           or R to remove option(s).                                            \n  \n      Option     Description                Attributes                           \n  _ - COBDEMO    Program monitor entry      COBOL                                \n      |          Waiting at breakpoint      Task 00059, CBP since 10:54 a.m.    \n  _ - |-.ANY     User monitoring options    Active                               \n        |        Symbolic listing file      PROTSYM                              \n 408", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c3572fd091a1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  r -   |-VBP    Variable change breakpoint Location=.ANY                        \n        |        Option ID                  23DEBD7B                             \n        |        Condition                  IF='TASKNUM'.NE.'TASKNUM'            \n        |        Compare type               Comp-3 (packed decimal)              \n        |        From, to terminals         G001, G001                           \n  _     |-SLB    Source listing breakpoints G001                                 \n                 *** End of data ***                                             \n  \n  \n  \n  \n  PF1 Help       2 Refresh    3 End        4 Return     5 Collapse   6 Expand    \n  PF7 Backward   8 Forward    9           10           11           12\n \nInspect and Modify Auxiliary Storage\nYou can use InterTest to inspect and modify the following items:\n\u2022VSAM and BDAM files\n\u2022DL/I, DB2, and SQL/DS databases\n\u2022Temporary storage\n\u2022Transient data\nYou can inspect and modify auxiliary storage at any time, even if a program is executing. This capability lets you maintain\nfiles and databases without writing one-time programs. You can perform any VSAM, BDAM, or DL/I function and most\nSQL functions. The ability to inspect and modify auxiliary storage when a program is stopped at a breakpoint lets you\nchange test data in the middle of a test session.\nAny changes you make are permanent; that is, changes to the file remain after the test session ends.\nInspect Auxiliary Storage\nTo access the auxiliary storage facility, select 4 Auxiliary storage from the InterTest Primary Option Menu, then specify the\nfile you want to examine on the Auxiliary Storage Menu.\n -------------CA InterTest for CICS  AUXILIARY STORAGE MENU  -------------\n  OPTION  ===> 1", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c3572fd091a1-1", "text": "OPTION  ===> 1                                                                 \n  \n     Select an auxiliary storage type, specifying optional criteria below.      \n  \n     1  Files              - Display/select files for access                     \n     2  DB2 database       - Invoke DB2 SQL interface facility                   \n     3  DL/I database      - Access DL/I database                                \n     4  TD queues          - Display/select transient data queues for access     \n     5  TS queues          - Display/select temporary storage queues for access  \n  \n     Type specific or generic file/queue name(s):                                \n        (Valid mask characters are  *  and/or  +)                                \n  \n     file____ ________ ________ ________ ________ ________ ________ ________\n \nAlternatively, if you are at a clear CICS screen, you can invoke the FILE transaction. InterTest displays the following:\n DATATYPE= FC FILEID=          MODE=      LOG=ON  TODEST=         PASSWORD=     \n 409", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6f0154ff880b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n FUNC=      SUBFUNC=      RETMETH=        ARGTYP=     SRCHTYP=                   \n MESSAGE=                                                                        \n  RETNRCID=                                                         CHGLEN=      \n     RCID=                                                                       \n     DATA=                                                          SIZE= 0000   \n FORMAT= D 00112233 44556677 8899AABB CCDDEEFF  *0123456789ABCDEF*              \n LOC 0000  ........ ........ ........ ........  ................               \n  \n  \n  \n  \n                       CA InterTest for CICS  \n  \n                   Copyright \u00a9 SOLVE:Access  CA. All rights reserved         \n  \n  \n -------------------------------------------------------------------------------\n 1 Help       2 Format C   3 End        4 BEGB       5            6 DataType DL \n 7 Page bwd   8 Page fwd   9 Caps Off  10 Top       11 Bottom    12\n \nNOTE\nIf the FILE transaction does not display the previous screen, it is probably because the person who installed\nInterTest changed the name of the FILE transaction. Contact that person to find out the correct name.\nAfter you type the file or database and, optionally, the record or segment, InterTest displays the data. A sample VSAM\nrecord in dump format follows.\n  DATATYPE= FC FILEID= INVNTRY   MODE=     LOG=OFF  TODEST=        PASSWORD= \n  FUNC=     SUBFUNC=      RETMETH=        ARGTYP=    SRCHTYP=                   \n  MESSAGE= RECORD OBTAINED FOR VIEWING                                          \n   RETNRCID=F0F0F0F0F0F0F0F0F5                                     CHGELEN=     \n      RCID=C`000000005'", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6f0154ff880b-1", "text": "RCID=C`000000005'                                                         \n      DATA=                                                        SIZE= 0050   \n  FORMAT= D 00112233 44556677 8899AABB CCDDEEFF *0123456789ABCDEF*                \n  LOC 0000  ........ ........ ........ ........ ................                \n    0000    F0F0F0F0 F0F0F0F0 F0F54040 0087338F   0000000005       DSORG=VSKS   \n    0010    F0F3F9F9 0407835C 40404040 40404040   0399....        RECFM=VB     \n    0020    40404040 40404040 C1C2C340 C3D6D9D7           ABC CORP  LRECL=0050  \n    0030    F0F9F1F2 F8F74040 0000598C 40404040   091287           BLKSIZE=0000 \n    0040    D1D6C3D5 404040E2 D4C9E3C8 40404040   JOHN  SMITH      KEYPOS=0000  \n    0050                                                           KEYLEN=0A    \n    0060                                                           STRNO=01     \n    0070                                                                        \n    0080                                                           READ         \n    0090                                                           ADD          \n    00A0                                                           UPDATE       \n  -------------------------------------------------------------------------------  \n  1 Help       2 Format C   3 End        4 BEGB       5 PREV      6 DataType DL \n  7 Page bwd   8 Page fwd   9 Caps Off  10 Top      11 Bottom    12            \n \nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6f0154ff880b-2", "text": "NOTE\nThe data appears in both hexadecimal and character format.\n 410", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "72515b3ed709-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo return to the source listing, press Clear or PF3.\nModify Auxiliary Storage\nTo modify the record or segment, overtype the hexadecimal or character data and press Enter. For example, you could\novertype JOHN SMITH with DALE COOPER on the sample display in the previous figure.\nTo rewrite the modified record, type PUT in the FUNC= field and press Enter.\nDisplay Auxiliary Storage in Structured Format\nInterTest can display file, transient data, and temporary storage records or DL/I segments field-by-field in structured format\nusing 01 level data names.\nTo display a record or segment in structured format, you must identify the program containing the structure. Symbolic\ninformation for this program must be saved in the InterTest Symbolic File. Follow these steps to display a record or\nsegment in structured format:\n1.If the FORMAT field does not contain S, press PF2 until FORMAT= S is displayed. The USE=field now appears after\nthe FORMAT field.\n2.Identify the program and structure in the USE= field. Specify the command as follows:\n USE=symbolic-name.structure-name\n \nsymbolic-name   is the name of the program as defined in the InterTest Symbolic File\nstructure-name   is the COBOL 01 level name\n3.Press Enter. InterTest displays the record or segment in structured format. A sample VSAM record in structured format\nis shown next.\n  DATATYPE= FC FILEID= INVNTRY  MODE=      LOG=OFF TODEST=        PASSWORD= \n  FUNC=      SUBFUNC=      RETMETH=        ARGTYP=    SRCHTYP= \n  MESSAGE= RECORD OBTAINED FOR VIEWING", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "72515b3ed709-1", "text": "MESSAGE= RECORD OBTAINED FOR VIEWING \n   RETNRCID=F1D7D9D6E3E2E8D440000000000000000000000000000000       CHGELEN= \n      RCID= C'1' \n      DATA=                                                        SIZE= 02D8 \n  FORMAT= S USE= PRODUCT.PRODREC \n  LOC 0050           Name                      Hexadecimal           Character \n  ------------------------------------------------------------------------------- \n  01 PRODREC                           |                           |\n   02 PRODUCT-TYPE                     | D3                        | L\n   02 PRODUCT-CODE                     | C2D4D5C8 40404040         | BMNH \n   02 PRODUCT-DESCRIPTION              | E6D9C5D5 C3C8             | WRENCH\n   02 PRODUCT-SITE                     | D1                        | J \n                                       |                           |\n                                       |                           |\n                                       |                           |\n                                       |                           |\n                                       |                           |\n                                       |                           |\n                                       |                           |\n  ------------------------------------------------------------------------------- \n  1 Help       2 Format D   3 End        4 BEGB       5           6 DataType DL \n  7 Page bwd   8 Page fwd   9 Caps Off  10 Top      11 Bottom    12\n \nStructured format lists the contents of each data name in both hexadecimal and character format.\n 411", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0f3bd24b92c5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n4.To modify the record or segment, overtype either the hexadecimal or character data and press Enter. To rewrite the\nmodified record, type PUT in the FUNC= field and press Enter.\nWhen a program is stopped at a breakpoint, you can substitute an asterisk ( *) for the symbolic-name. For example, if\nprogram PAYROLL is stopped at a breakpoint and you type:\n USE=*.payrec\n \nInterTest uses the program named PAYROLL and the PAYREC structure.\nTo begin the structure with a specific data name, specify the following command in the DATA field:\n FIND=data-name\n \nwhere data-name   is the data name to be displayed.\nResume Program Execution\nWhen you are finished performing breakpoint activities such as displaying and modifying main or auxiliary storage, you\ncan resume program execution. You can do the following actions:\n\u2022Resume execution from a specific location\n\u2022Single-step execution one verb at a time\nResume Execution from a Specific Location\nTo resume program execution from the breakpoint location where your program is stopped, the source listing screen must\nbe displayed. Press PF3 from any InterTest screen until the breakpoint screen redisplays.\nPress PF5 to continue from the current breakpoint. Execution continues until the program is halted at another breakpoint\nor the task completes.\nIf you are stopped at an automatic breakpoint, you must first correct the error that triggered the breakpoint before\ncontinuing execution from that point. Or, you can go around the error and continue execution from another location.\nTo resume program execution from another location, perform the following steps:\n1.Display the statement where you want to resume execution.\n2.Type GO READ-DATASET in the command line or G to the left of that statement.\n3.Press Enter .\nProgram execution resumes from that statement.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0f3bd24b92c5-1", "text": "3.Press Enter .\nProgram execution resumes from that statement.\nThe following example shows how to resume execution from a location prior to an automatic breakpoint. This might be\nuseful if you corrected a record or dynamically modified an incorrect file name and now want the program to re-read the\nrecord or file.\n    CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT      \n COMMAND ===>                                                                    \n Program= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n  _____ RECORD-KEY                      | 00000000000000000000000000000000000000 \n ---------+--------------------------------------------------------------------- \n  _ 000695         GO TO SEND-REWRITE-RETURN.                                    \n  _ 000696     IF  TASK-SWITCH3 EQUAL 'A'                                        \n  _ 000697         GO TO READ-DATASET                                            \n  _ 000698     ELSE                                                              \n  _ 000699         GO TO SEND-MAP00.                                             \n  g 000700 READ-DATASET.                                                         \n    000701*EXEC CICS HANDLE CONDITION                                            \n 412", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "025753067267-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    000702*          DSIDERR                                                     \n    000703*          NOTOPEN(NOT-OPEN)                                           \n    000704*          END-EXEC.                                                   \n  _ 000705     Call 'DFHEI1' using by content x'0204800007130c00000000000000     \n  _ 000706-    '0000000000000000f0f0f3f8f7404040' end-call  \n .\n .\n .                                           \n \nWhen you press Enter, execution resumes from READ-DATASET, the location you identified with G.\nSingle-Stepping\nSingle-stepping lets your program execute one COBOL verb and then stop again. You can adjust the step amount so the\nprogram executes a specified number of verbs between stops.\nTo single-step, type NEXT in the command line and press Enter or press PF10 from the source listing. Your program\nexecutes the next verb and then stops.\nTo single-step from a different program location:\n1.Display the statement where you want to resume execution. For more information, see Display Your Source Listing.\n2.Type G to the left of that statement.\n3.Type NEXT in the command line and press Enter or press PF10.\nTo adjust the step amount, perform the following steps:\n1.Press PF4 to access the Source Listing Profile screen.\n2.Change the number in the Stepping amount field.\n3.Press Enter. InterTest changes the step amount and redisplays the source listing. If Titles are set to on (an option\non the Source Listing Profile screen), you see the new step amount displayed next to PF10 at the top of the Source\nListing Breakpoint screen.\nAbend a Task", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "025753067267-1", "text": "Listing Breakpoint screen.\nAbend a Task\nWhen your program is stopped at a breakpoint, you can abend your task rather than resume execution. Type ABEND in\nthe Command line of any Breakpoint display. InterTest displays the screen shown next.\n -----------------  CA InterTest for CICS ABEND BREAKPOINTED TASK  ----------------\n  COMMAND ===>                                                                   \n  \n     Type an abend code, then press ENTER.                                      \n  \n  \n     Abend Code  ____   Abend code options are:                                  \n  \n                        blanks        Normal abend, no dump                      \n                        XXXX          Abend exits cancelled, no dump             \n                        your code     Your abend code, dump taken                \n .\n .\n .\n \n 413", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c0fab64eb798-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022To cancel the abend, press PF3. InterTest redisplays the Primary Option Menu.\n\u2022To abend without  a dump:\n- For a normal abend, press Enter .\n- To cancel all program exits, specify code XXXX and press Enter.\n\u2022To abend with a dump, specify a four-character dump code and press Enter. The dump code you specify cannot be\nXXXX and cannot begin with the letter A.\nFor more information on the status of your program after abending, see End a Test Session.\nGet Help\nHelp is always available when you are using InterTest. You can use Help to initiate InterTest. Type Help on a clear screen\nunder CICS.\nGet Help in Using InterTest for CICS\nWhen you are using InterTest, you can press PF1 at any time for information on InterTest functions. For example, the\nfollowing screen lists the Help topics for the Source Listing facility.\n                     CA INTERTEST  - INTERACTIVE HELP FACILITY -     \n TUTORIAL: SOURCE LISTING FACILITY - FOR COBOL PROGRAMS                         \n  \n  \n  05  Set Monitoring                    45  Set/Remove other monitoring Options  \n  10  Locating areas in the listing     50  Displaying data items                \n  20  Search for a Character string     55  Modify the value of data items       \n  25  Specify Indirect Commands         60  Resume TASK execution                \n  30  PF key definitions                65  Abending your TASK                   \n  32  Primary Line Commands             70  PROFILE, AUTOSTEP, AUTOKEEP Options  \n  35  Set the Display Margins           75  Code Coverage Option                 \n  40  Set/Remove Breakpoints            80  View Program Backtrace", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c0fab64eb798-1", "text": "40  Set/Remove Breakpoints            80  View Program Backtrace               \n  \n  \n  \n  \n                                                                           (end)\n  ------------------------------------------------------------------------------\n ENTER A SELECTION CODE FROM THE MENU, OR N FOR NEXT PAGE, P FOR PRECEDING PAGE, \n  M FOR RETURN TO PREVIOUS MENU,  CLEAR TO EXIT, OR MESSAGE NUMBER. ==> 05\n \nHelp for Line Commands\nNotice that selection code 32 lists Line Commands. These are the simple commands that you can enter on the Command\nline of a Source Listing Display, Breakpoint Display, or SymDump  Breakpoint display, and include the commands abend,\nmonitor, and status.\nGet Help to Correct an Error\nWhenever your program is stopped at an automatic breakpoint, InterTest displays a short message identifying the reason\nfor the breakpoint. You can request help by pressing PF1 for information on what caused the error that triggered the\nbreakpoint and how to fix it. The following screen explains how to correct an AEIL abend:\n                     CA INTERTEST  - INTERACTIVE HELP FACILITY -     \n TUTORIAL: ERROR MESSAGE AEIL                                                   \n 414", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "35218eadc029-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  \n  The dataset name referred to in the DATASET option cannot be found in the FCT.\n  Your program did not have a Handle Condition for this error. Or a second Handle\n  Condition without a routine for this error superseded the one that had a       \n  routine for this error.                                                       \n  \n  WHAT YOU CAN DO: If the named file was entered incorrectly and the one you     \n  wanted exists, you may use the Replace File Option to dynamically replace the  \n  file name and then use the resume task facilities to execute the CICS request  \n  again. To perform the above functions from the Source Listing Breakpoint screen\n  you would:                                                                     \n  \n  1. Key =20s in the Option # field and press ENTER.                            \n  2. Tab to  Replace file name:   Key in the incorrect file name.               \n  3. In the next field, key in the correct file name and press ENTER.           \n  4. Press CLEAR  to return to your Source Listing Breakpoint screen.           \n  5. Key in G to resume execution at the beginning of the EXEC CICS command      \n     and press ENTER.                                                           \n                                                                     (continued)\n  ------------------------------------------------------------------------------\n ENTER N FOR NEXT PAGE, P FOR PRECEDING PAGE, F FOR FIRST PAGE, OR -             \n  M FOR RETURN TO PREVIOUS MENU,  CLEAR TO EXIT, OR MESSAGE NUMBER. ==> N\n \nNOTE\nWhen you leave and then return to an automatic breakpoint screen, the error message may no longer appear.\nFor help on the cause of the error, press Clear to redisplay the error message before pressing PF1.\nEnd a Test Session\nAfter your program completes execution or you abend your task, you return to CICS.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "35218eadc029-1", "text": "After your program completes execution or you abend your task, you return to CICS.\nThe following table shows the status after testing of a program area:\nProgram Area Status after Testing\nprogram source code not modified\nfile/database updates by the program permanent\nfile/database updates you made permanent\nInterTest monitoring, breakpoints, and other options set for the program remain in effect until they are specifically\nremoved.\nCorrect the Source Code\nAt some point you might want to correct the source code and continue testing from a clean version of the program.\nAfter you have modified the source code and recompiled the program, you can load the new copy of the program by using\nthe New Program Copy option on the Program Monitoring menu (ITST 2.1). The next article explains how to set options\non the Program Monitoring menu.\nThe New Program Copy option resets symbolic breakpoints and other monitoring options for the recompiled program. It\nalso resets the PPT entry to the program's new library address.\n 415", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ff9ad1f0f9f1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCOBOL Advanced Monitoring Features\nThis article describes commonly used InterTest features.\nFor information about InterTest features, see CICS Debugging and the Help facility.\nSet Options from the Monitoring Menus\nThe InterTest monitoring menus are the easiest way to set many monitoring options. You can access these menus from\nthe Primary Option Menu by selecting option 2 - Monitoring, as shown in the following screen:\n --------------- CA InterTest for CICS PRIMARY OPTION MENU  --------------\n OPTION  ===>  2\n   1  Source             - Display/select program source files/listings       \n   2  Monitoring         - Display/modify CA InterTest monitoring/activity    \n   3  Main storage       - Display/modify CICS storage areas                  \n   4  Auxiliary storage  - Display/access databases/files/queues              \n   5  Dump analysis      - Invoke CA SymDump CICS dump/trace capture facility \n   6  Product help       - Invoke CA InterTest product help facility          \n   7  Status/Maintenance - Product status and maintenance functions           \n   8  What's new?        - Display information about CA InterTest for CICS \n   X  Exit               - Terminate menu processing                          \n                                                                              \n                                                                             \nInterTest displays the Monitoring Menu (shown next), from which you can select a wide variety of different monitoring\noptions. Use online help or CICS Debugging for a detailed explanation of each of these options.\n-----------------  CA InterTest for CICS  MONITORING MENU  ---------------\n OPTION  ===>                                                                   \n                                                                                \n    1  Programs           - Display/modify program monitoring options           \n    2  Transactions       - Display/modify transaction monitoring options       \n    3  Terminals          - Display/modify terminal monitoring options", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ff9ad1f0f9f1-1", "text": "3  Terminals          - Display/modify terminal monitoring options          \n    4  Status             - Display/remove current monitoring options           \n    5  Active tasks       - Display/purge active monitored tasks                \n    6  System-wide        - Display/modify global system-wide options           \n.\n.\n.      \nOption 1 Programs access the Program Monitoring Menu, from which you can set and remove any option for a program,\nand request a status display.\nThe Program Monitoring menu, shown in the following screen, is probably the most frequently used menu during a testing\nsession:\n--------------------  CA InterTest for CICS  PROGRAM MONITORING  ------------------\n COMMAND ===>                                                                   \n                                                                                \n   Type information and S to set or R to remove option(s) below.               \n                                                                                \n   Program  . . cobdemo_     Program name (or .ALL, .OPTIONS or generic)        \n 416", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f1cc7b7511a3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n   User ID  . . _______      User (or .ANY) for whom the program is monitored   \n                                                                                \n   Option       Description                                            More:  +\n _ Status       Display and/or remove monitoring options (S only)               \n _ Monitor      Monitoring (R removes monitoring and all options previously set)\n _ UBP          Unconditional breakpoints (specific program only)               \n _ CBP          Conditional breakpoints (specific program only)                 \n _ RBP          Breakpoints for CICS, DB2, DL/I or external CALL requests       \n _ Stmt Trace   Statement tracing and data monitoring (COBOL only) \n _ New copy     Fetch new copy of program and reset monitoring options (S only) \n _ Commands     Indirect commands defined for a specific COBOL or PL/1 program \n _ Replace      CICS resource name replacement options                          \n _ Protect      Storage protection monitoring options                          \n _ Special      Other options (storage allocation, file updating, etc.)         \n _ Composite    Monitor multi-CSECT program's separately compiled components \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7 Backward   8 Forward    9           10           11           12          \nQuick access to this menu is available before or during a session, as described in the following table.\nThe following list contains the fastpath entries that you can use to access the Program Monitoring menu:\n\u2022CICS, clear screen: ITST 2.1\n\u2022Primary Option Menu, Option field: 2.1\n\u2022Source Listing display, Command field: =2.1\n\u2022Breakpoint display, Command field: =1.2.1\nAfter prrocessing any program options from this menu, press PF3 to exit back to your test session. If you entered directly", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f1cc7b7511a3-1", "text": "from CICS, you will exit back to the ITST Primary menu. From a source listing or breakpoint, PF3 takes you back to that\ndisplay.\nSet and Remove Conditional Breakpoints\nConditional   breakpoints are breakpoints that take effect when a specific condition is met, such as when a counter\nexceeds a value. These breakpoints can help you isolate complex problems.\nTo set a conditional breakpoint, type C to the left of the statement where you want to set the breakpoint, as shown next,\nand press Enter.\n   CA InterTest for CICS  - PROTSYM FILE  SOURCE LISTING DISPLAY         \nCOMMAND ===>                                                                   \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01 \n                                        Search=                                \nOPTS 1 Proc div  2 Work-stor 3 Link sect  4 D-map      5 Clst/Pmap More:   +   \n     6 Data xref 7 Proc xref 8 Err msgs   9 Srch fwd  10 Srch bwd              \nPFKS 1 Help      2           3 End        4 Profile    5 Monitor    6 Menu     \n     7 Backward  8 Forward   9 Next Wnd  10           11           12 Status   \n-------------------------------------------------------------------------------\n _ 000435      Go to  GEN-ERR depending on dfheigdi.                            \n   000436                                                                       \n _ 000437 NO-OPTS.                                                              \n c 000438     MOVE SPACE TO TASK-SWITCH.                                        \n _ 000439     MOVE ZERO  TO TASK-SWITCH2.                                      \n 417", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8a09b91cdbe0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _ 000440     MOVE SPACE TO TASK-SWITCH3. \nInterTest displays the menu on which you define the condition. For the following example, the breakpoint halts program\nexecution only if TASK-SWITCH is equal to 3.\n         CA-InterTest MONITORING COMMAND BUILDER - CONDITIONAL BREAKPOINT      \n                                                                               \n Enter LEFT SIDE                                                               \n     Data Name task-switch_____________________________________________________\n                                                                               \n                                                                               \n Enter OPERATOR (EQ, NE, GT, LT, GE, LE):  eq                                  \n                                                                               \n Enter RIGHT SIDE                                                              \n     Data Name ________________________________________________________________\n        OR                                                                     \n     Literal 3_________________________________________________________________\n                                                                               \n                                                                               \n                                                                               \n                                                                               \n _ ENTER  S  to Drop monitoring on a true condition                            \n                                                                               \n For location:                                                                 \n            000498     MOVE SPACE TO TASK-SWITCH.                              \n                                                                               \n Press PF9 to go to complex conditional screen if necessary                    \n PF1 Help       2            3 End        4 Return     5            6          \n PF7            8            9 Complex   10           11           12         \nConditional breakpoints are indicated by a C next to the line of code in your source listing.\nRemove Conditional Breakpoints from the Source Listing\nYou can easily remove a conditional breakpoint from where it is displayed in your source listing or from the monitoring\nstatus report. To remove a conditional breakpoint from your source listing, overtype the C with an x and press Enter, as\nshown in the following screen :\n   CA InterTest for CICS   - PROTSYM FILE  SOURCE LISTING DISPLAY         \nCOMMAND ===>                                                                   \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01 \n                                        Search=", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8a09b91cdbe0-1", "text": "Search=                                \nOPTS 1 Proc div  2 Work-stor 3 Link sect  4 D-map      5 Clst/Pmap More:   +   \n     6 Data xref 7 Proc xref 8 Err msgs   9 Srch fwd  10 Srch bwd              \nPFKS 1 Help      2           3 End        4 Profile    5 Monitor    6 Menu     \n     7 Backward  8 Forward   9 Next Wnd  10           11           12 Status   \n-------------------------------------------------------------------------------\n _ 000435      Go to  GEN-ERR depending on dfheigdi.                           \n   000436                                                                      \n _ 000437 NO-OPTS.                                                             \n x 000438     MOVE SPACE TO TASK-SWITCH.                                       \n _ 000439     MOVE ZERO  TO TASK-SWITCH2.                                      \n _ 000440     MOVE SPACE TO TASK-SWITCH3.                                      \n 418", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d9ee40313cff-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nRemove Conditional Breakpoints from the Status Report\nYou can always remove any breakpoint from the Monitoring Status report. To remove this conditional breakpoint from your\nprogram, perform the following steps:\n1.Type STATUS on the Command line to display the Monitoring Status report for the current program.\n2.Tab to the entry for the Conditional Breakpoint (CBP option) you want to remove, type R to the left of its entry, and\npress Enter.\n---------------  CA InterTest for CICS  MONITORING STATUS  --------------\n COMMAND ===>                                                                   \n                                                                                \n   Type + to expand or - collapse option levels displayed below,                \n          or R to remove option(s).                                             \n                                                                                \n     Option     Description                Attributes                           \n _ - COBDEMO    Program monitor entry      IBMCOB 3.2                           \n _ - |-.ANY     User monitoring options    Active                               \n       |        Symbolic listing file      PROTSYM                              \n r -   |-CBP    Conditional breakpoint     #438                                 \n       |        Option ID                  2E72B0DD                             \n       |        Condition                  IF='TASK-SWITCH'.EQ.C'3'             \n       |        Compare type               Pic X (character strings)            \n       |        From, to terminals         U056, U056                           \n _     |-SLB    Source listing breakpoints U056                                 \n                *** End of data ***                                             \n                                                                                \n PF1 Help       2 Refresh    3 End        4 Return     5 Collapse   6 Expand    \n PF7 Backward   8 Forward    9           10           11           12\nInterTest places an asterisk to the left of the breakpoint to indicate that the removal was processed.\n3.Press PF3 to return to your Source.\nRequest Breakpoints", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d9ee40313cff-1", "text": "3.Press PF3 to return to your Source.\nRequest Breakpoints\nRequest  breakpoints are breakpoints that take effect prior to CICS commands and macros and other program calls, such\nas calls to DL/I or DB2. With one specification, you can set breakpoints at all CICS commands or at specific commands,\nsuch as all REWRITE commands.\nUse request breakpoints to stop a program before the following commands:\n\u2022Every CICS command or macro\n\u2022Specific types of CICS commands, such as all File Control or Program Control commands\n\u2022Specific commands, such as all READ or WRITE commands\nSet Request Breakpoints\nTo set request breakpoints, perform the following steps:\n1.Select option - 2 Monitoring on the Primary Option Menu. InterTest displays the Monitoring Menu.\n2.Select option - 1 Programs. InterTest displays the Program Monitoring screen.\n--------------------  CA InterTest for CICS  PROGRAM MONITORING  -------------------\n COMMAND ===>                                                                   \n                                                                                \n   Type information and S to set or R to remove option(s) below.               \n 419", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "252f40c939f4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                                                                \n   Program  . . cobdemo_     Program name (or .ALL, .OPTIONS or generic)        \n   User ID  . . _______      User (or .ANY) for whom the program is monitored   \n                                                                                \n   Option       Description                                            More:   +\n _ Status       Display and/or remove monitoring options (S only)               \n _ Monitor      Monitoring (R removes monitoring and all options previously set)\n _ UBP          Unconditional breakpoints (specific program only)               \n _ CBP          Conditional breakpoints (specific program only)                 \n s RBP          Breakpoints for CICS, DB2, DL/I or external CALL requests       \n _ Stmt Trace   Statement tracing and data monitoring (COBOL only) \n _ New copy     Fetch new copy of program and reset monitoring options (S only) \n _ Commands     Indirect commands defined for a specific COBOL or PL/1 program \n _ Replace      CICS resource name replacement options                          \n _ Protect      Storage protection monitoring options                          \n _ Special      Other options (storage allocation, file updating, etc.)         \n _ Composite    Monitor multi-CSECT program's separately compiled components \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7 Backward   8 Forward    9           10           11           12          \n3.In the Program field, type the name of the program for which you want to set request breakpoints.\n4.Type S to the left of the RBP option (request breakpoints). Press Enter.\nInterTest displays the Request Breakpoint Selection menu on which you specify the type of request breakpoint, such\nas: all CICS commands, File Control and Task Control.\nCA InterTest MONITORING COMMAND BUILDER - REQUEST BREAKPOINT SELECTION  13", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "252f40c939f4-1", "text": "CA InterTest MONITORING COMMAND BUILDER - REQUEST BREAKPOINT SELECTION  13\n                                                                                \n              Set  one or more types of Request Breakpoints in:                 \n                                PROG=COBDEMO                                    \n                                                                                \n _ ALL commands                    _ DL/I    _ DB2     _ CALLs                  \n                                                                                \n   _ Address, Assign,         _ Storage Control    _ BMS                        \n       Handles, Push, Pop     _ Program Control    _ Trace Control              \n   _ Terminal Control         _ Interval Control   _ Dump Control               \n   _ File Control             _ Task Control       _ Batch Data Interchange     \n   _ TD Control               _ Journal Control    _ Built-In Functions         \n   _ TS Control               _ Syncpoints         _ Sys Prog Functions         \n   _ Web access               _ Business Trans     _ 3270 Bridge                \n                                                                                \n   Enter 'n' to stop only every n'th time:                         ____         \n   Term ID (or .ANY or .NO) where breakpoints will take effect:    ____         \n   Term ID (or .ANY) that will receive the breakpoints:            ____         \n   Statement no. of indirect command(s) to be executed:            _____        \n   User ID (or .ANY) who will execute the program:                 ________     \n                                                                                \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7            8            9           10           11           12\nSubsequent menus prompt you for the specific command, such as all File Control commands, READ, WRITE,\nREWRITE, and so on.\n 420", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ba6bf1f777d9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nType X in front of each type of command for which you want to set request breakpoints.\nAfter setting your request breakpoints, PF4 returns you to the Primary Option Menu. If you came from a Source\nListing, PF3  returns you to your source.\nRemove Request Breakpoints\nTo remove request breakpoints, perform the following steps:\n1.From the Source Listing Display screen or breakpoint display, type STATUS on the Command line and press Enter.\nInterTest displays the Monitoring Status display showing all options for the current program.\n2.Type an r to the left of the request breakpoint (RBP) you want to remove and press Enter. InterTest places an asterisk\nto the left of the breakpoint to indicate that the command has been processed.\n3.Press PF3 to return to the Source Listing screen or Breakpoint display.\nBacktrace Facility\nWhen your program stops at a breakpoint, you might find it useful to examine the Backtrace Summary and the Source\nListing Backtrace . The backtrace facility shows the logic flow of the program and explains how processing reached this\npoint.\nThe backtrace facility lets you do the following actions:\n\u2022View the backtrace summary screen for a (high-level) summary of the program's execution\n\u2022Use special PF keys to step through the program's execution path\n\u2022Reposition the source listing to view the program's execution path from a different backtrace position\nIn addition to the Backtrace PF keys, all other source listing options, such as the Keep window, setting and removing\nbreakpoints, and the ability to scroll backward and forward from the current source listing position are available from the\nSource Listing Backtrace screen.\nAccess the Backtrace Summary\nTo view the Backtrace Summary, press PF11 from the Source Listing Breakpoint screen, or, type BTRACE in the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ba6bf1f777d9-1", "text": "Command line and press Enter. InterTest positions the Backtrace Summary Screen at the last executed statement, as\nshown in the following screen:\n InterTest  for CICS - BACKTRACE SUMMARY                              \n                                                                                \nProgram= COBDEMO                                      From 0005 To 0017 Of 0017 \n                                                                                \nSpecify  S then ENTER to display Source Listing BACKTRACE                       \n------------------------------------------------------------------------------- \nPFKS 1 Help      2 Backtrace 3 End        4            5 1st Stmt   6 Last Stmt \n     7 Backward  8 Forward   9 Next Wnd  10           11 Prev Bloc 12 Next Bloc \n------------------------------------------------------------------------------- \n S Bkmk       Stmt Block  \u00a6 Source Listing                                       \n _ ____    #375.0...#378.0\u00a6      Call 'DFHEI1' using by content x'0204c000072c0 \n _ ____    #378.0...#378.0\u00a6       Go to  WRITE-TSQ GEN-ERR depending on dfheigd \n _ ____    #407.0...#407.0\u00a6      Call 'DFHEI1' using by content x'02048000071b0 \n _ ____    #407.0...#410.0\u00a6      Call 'DFHEI1' using by content x'02048000071b0 \n _ ____    #416.0...#416.0\u00a6      Call 'DFHEI1' using by content x'0e06c00007000 \n _ ____    #416.0...#426.0\u00a6      Call 'DFHEI1' using by content x'0e06c00007000 \n _ ____    #426.0...#432.0\u00a6      Call 'DFHEI1' using by content x'0e0a800007000", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ba6bf1f777d9-2", "text": "421", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "875d6dee6a5f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _ ____    #432.0...#435.0\u00a6      Call 'DFHEI1' using by content x'02048000071b0 \n _ ____    #438.0...#447.0\u00a6      MOVE SPACE TO TASK-SWITCH.                    \n _ ____    #447.0...#460.0\u00a6      Call 'DFHEI1' using by content x'0a02e00007000 \n _ ____    #460.0...#468.0\u00a6      Call 'DFHEI1' using by content x'1804f00007000 \n _ ____    #468.0...#470.1\u00a6      Call 'DFHEI1' using by content x'0402000007000 \n * ____    #479.0... BKPT \u00a6      ADD +1 TO TASKNUM.  CAIN2987 Last Backtrace Stmt Block  \nRead the Backtrace Summary\nThe Backtrace Summary screen summarizes the program's execution. This screen displays the statement number and\nsource of the first statement in each contiguous group of executed program statements.\n\u2022The order of the statements reflects the program's execution path\n\u2022The top statement is the first statement executed; the bottom statement is the most recently executed statement.\nFrom the Backtrace Summary screen, you can do the following actions:\n\u2022Reposition the display to view statement-by-statement details of the program's execution path by:\n\u2013Pressing PF2\n\u2013Marking a statement block with s, then pressing Enter\n\u2022Assign a bookmark, consisting of one to four characters, to one or more backtrace positions for faster and easier\nnavigation through the Backtrace Summary\n\u2022Trace program execution using the following PF keys:\nPF5 1st Stmt", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "875d6dee6a5f-1", "text": "\u2022Trace program execution using the following PF keys:\nPF5 1st Stmt\nRepositions the Backtrace Summary screen to the 1st or oldest entry in the Backtrace.\nPF6 Last Stmt\nRepositions the Backtrace Summary screen to the last or newest entry in the Backtrace.\nPF7 Backward\nScrolls the Backtrace Summary screen backward (up) a full screen.\nPF8 Forward\nScrolls the Backtrace Summary screen forward (down) a full screen.\nPF11 Prev Bloc\nDisplays the previous statement block.\nPF12 Next Bloc\nDisplays the next statement block.\nAccess the Source Listing Backtrace\nTo display the Source Listing Backtrace screen, press PF2 or type s next to a statement block in the Select column of\nthe Backtrace Summary screen, as shown in the previous screen. The following screen is the Source Listing Backtrace\nscreen.\n   CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BACKTRACE        \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ TASKNUM                         | ?00000.                                \n======= Backtrace at #000407  (000407 -> 000407 executed     1 times) <=======  \n   000405*          PGMIDERR(NO-OPTS)                                           \n   000406*          END-EXEC.                                                   \n _ 000407     Call 'DFHEI1' using by content x'02048000071b0000000000000000      \n 422", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "84dbeffb156c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _ 000408-    '0000000000000000f0f0f1f7f6404040' end-call                       \n _ 000409      Service label                                                    \n _ 000410      Go to  NO-OPTS depending on dfheigdi.                            \n   000411                                                                       \n   000412*EXEC CICS LOAD                                                        \n   000413*          PROGRAM('IN25OPTS')                                         \n   000414*          SET(ADDRESS OF IN25OPTS-AREA)                               \n   000415*          END-EXEC.                                                   \n _ 000416     Call 'DFHEI1' using by content x'0e06c0000700000400f0f0f1f7f9     \n _ 000417-    '404040' by content 'IN25OPTS' by reference ADDRESS OF            \n _ 000418     IN25OPTS-AREA end-call.                                           \n   000419                                                                       \n _ 000420     MOVE OPTS-CNTL TO TASK-CNTL.                                      \n _ 000421     MOVE OPTS-PROTCPF TO TASK-PROTCPF.                               \nRead the Source Listing Backtrace\nTo clearly detail the program's execution path, statement by statement, source statements that were executed from the\ncurrent backtrace position are highlighted. When you specify a non-backtrace source listing option or use PF7 or PF8 to\nreposition the source listing, the highlighting of executed statements is temporarily suspended until a backtrace-related PF\nkey (next block, previous block, and so on) is entered.\nWhen in source listing backtrace mode, the current backtrace position always appears on the line just above the first\nsource statement. This line displays as follows:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "84dbeffb156c-1", "text": "source statement. This line displays as follows:\n======>BACKTRACE AT #nnnnn (nnnnn -> nnnnn executed nnnnn times)<=====\nThe information in this line indicates the following:\n#nnnnn\nSpecifies the program statement or offset the backtrace is currently positioned at\nnnnnn -> nnnnn\nSpecifies the first and last number of the statement block\nnnnnn times\nSpecifies how many times a statement block was executed\nOn the Source Listing Backtrace screen, each relevant backtrace position is indicated in the listing by an arrow or a line:\n====>\nIndicates the first statement in a statement block\n<====\nIndicates the last statement in a statement block\n====\nIndicates all other statements within a statement block\nThe Source Listing Backtrace screen displays the source of each statement:\n\u2022The order of the statements reflects the program's execution path.\n\u2022The top statement is the first statement executed; the bottom statement is the most recently executed statement.\nNavigate through Program Execution\nYou can trace your program's execution path by using the following commands:\n 423", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "549b09c9595a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Using PF5, PF9 and PF11 to trace execution backward\n\u2022Using PF6, PF10, PF12 to trace execution forward\n\u2022Setting the source listing profile Stepping Amount, and then using PF9 and PF10 to automatically trace the execution\nbackward or forward\nEnd a Source Listing Backtrace Session\nTo turn off the source listing backtrace display mode, press Clear or PF3. InterTest redisplays the Source Listing\nBreakpoint screen, positioned at the last breakpoint.\nTo toggle between the Source Listing Backtrace screen and the Backtrace Summary screen, press PF2.\nSet the Code Counting Coverage Option\nInterTest has many options for specialized testing needs. The code coverage option lets you see the number of times an\nassembler statement was executed.\nThe initial setting for code counting is OFF, which is the default. However, you can use the Source Listing Profile screen to\nturn it ON or OFF again at any time after you have selected monitoring for a program.\nHow the counts are displayed or not displayed is handled by the primary line command COUNTS and its associated\nparameters.\nThis feature causes overhead during program monitoring and should be turned off as soon as it is no longer needed.\nTo change the setting for code coverage, perform the following steps:\n1.Type PROFILE on the command line and press Enter, or press PF4 to access the Profile screen from any Source\nListing screen. The Code Counting= field shows the current setting.\n2.Overtype the current value with one of the following values:\nYES\nEnables code counting and turns on the COUNTER display feature.\nNO\nRemoves the COUNTER display and stops the counting feature.\n3.Press Enter to process the new settings and to return to the Source Listing Display screen.\n4.The following screen details the code coverage feature:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "549b09c9595a-1", "text": "4.The following screen details the code coverage feature:\n   CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT       \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ TASKNUM                         | ?00000.                                \n---------+--------------------------------------------------------| COUNTER |-- \n _ 000351 PROCEDURE DIVISION using dfheiblk dfhcommarea.          |         |   \n _ 000352     MOVE EIBTRNID TO TSQ-TRANID.                        | 0000001 |   \n _ 000353     MOVE EIBTRMID TO TSQ-TERMID.                        | 0000001 |   \n   000354*** THIS CODE INITIALIZES THE MAPS BECAUSE COBOL2 DOESN'T|         |   \n _ 000355     MOVE LOW-VALUES TO DMAP04AI                         | 0000001 |   \n _ 000356                  DMAPBEGI                               |         |   \n _ 000357                  DMAPASRI                               |         |   \n _ 000358                  DMAPSUMI                               |         |   \n _ 000359                  DMAPENDI                               |         |   \n _ 000360                  DMAP00I                                |         |   \n _ 000361                  DMAP01I                                |         |   \n 424", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "85cc6871a246-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _ 000362                  DMAP02I                                |         |   \n _ 000363                  DMAP03I                                |         |   \n _ 000364                  DMAP04I                                |         |   \n _ 000365                  DMAP05I                                |         |   \n _ 000366                  DMAP06I                                |         |   \n _ 000367                  DMAP07I                                |         | \nStatement Trace Facility\nThe Statement Trace Facility lets you view the logic flow of your program at a statement level.  When used in conjunction\nwith the Datamon command, it allows you to view the values of data items at the time that the statement was executed.\nNOTE\nThis feature is only valid for COBOL programs. Use the Backtrace facility for tracing information for other\nlanguages.\nEnable Statement Tracing and Data Monitoring\nUse the TRACE command to enable the statement tracing facility. This creates a table whose number of entries is defined\nby the STMTTRCE option in IN25OPTS. This is a wraparound table, meaning that when all of the entries are used, the\noldest entry is used for the current statement.\nUse the DATAMON command, or DM, to enable data monitoring for the given program. If the Statement Trace facility was\nnot in effect when data monitoring is set, a statement trace table is created.\nNavigate the Statement Trace Table\nWhen at a breakpoint, and statement tracing is in effect, you can use the PREV and ADVANCE commands to determine\nthe execution path of the program prior to this point. Use the PREV command to cause the display to back up one\nstatement. Consider the following breakpoint:\n   CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT       \nCOMMAND ===>", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "85cc6871a246-1", "text": "COMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ TASKNUM                         | ?00000.                                \n---------+--------------------------------------------------------------------- \n _ 000477 CONTINUE-TASK.                                                        \n   000478**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED                          \n A    ==>     ADD +1 TO TASKNUM.                                                \n     ==>                                                                        \n     ==> ASRA ABEND (0C7) detected and prevented. Caused by invalid decimal     \n     ==> arithmetic data format.                                                \n     ==>                                                                        \n     ==>      Press PF1 for a detailed description.                             \n     ==>                                                                        \n _ 000480     IF TASKNUM = 1                                                    \n _ 000481         MOVE 'DMAPASR'  TO MAPNAME.                                   \n _ 000482     IF TASKNUM = 2                                                    \n _ 000483         MOVE 'DMAPSUM'  TO MAPNAME.                                   \n _ 000484     IF TASKNUM GREATER 2                                              \n _ 000485         GO TO SEND-END-MSG.                                           \n _ 000486     GO TO REWRITE-TSQ.                                                \n 425", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dc41a2c36838-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _ 000487 REWRITE-TSQ.                                                  \nUsing the PREV command on the previous screen results in the next screen:\n   CA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT       \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \nOPTS 1 Proc div  2 Work-stor 3 Link sect  4 D-map      5 Clst/Pmap More:   +    \n     6 Data xref 7 Proc xref 8 Err msgs   9 Srch fwd  10 Srch bwd               \nPFKS 1 Help      2           3 Det Bkpt   4 Profile    5 RESUME     6 Menu      \n     7 Backward  8 Forward   9 Next Wnd  10 001 Verb  11 Backtrace 12 Status    \n------------------------------------------------------------------------------- \n _ 000468     Call 'DFHEI1' using by content x'0402000007000000140000400000     \n _ 000469-    '00f0f0f2f0f9404040' end-call.                                    \n _ 000470     IF EIBAID = DFHENTER GO TO CONTINUE-TASK.                         \n _ 000471     IF EIBAID = DFHCLEAR GO TO SEND-END-MSG.                          \n _ 000472     IF EIBAID = DFHPF3   GO TO SEND-END-MSG.                          \n _ 000473     IF EIBAID = DFHPF15  GO TO SEND-END-MSG.                          \n _ 000474     IF EIBAID = DFHPF2   GO TO EXPANDED-DEMO.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dc41a2c36838-1", "text": "_ 000475     IF EIBAID = DFHPF14  GO TO EXPANDED-DEMO.                         \n _ 000476     GO TO SEND-FIRST-SCREEN.                                          \n _ 000477 CONTINUE-TASK.                                                        \n   000478**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED                          \n A    ==>     ADD +1 TO TASKNUM.                                                \n _ 000480     IF TASKNUM = 1                                                    \n _ 000481         MOVE 'DMAPASR'  TO MAPNAME.                                   \n _ 000482     IF TASKNUM = 2                                                    \n _ 000483         MOVE 'DMAPSUM'  TO MAPNAME.                                  \nStatement number 470 was the statement executed just before the abend at the statement number 479. Similarly the\nADVANCE command advances the statement trace pointer.\nView Past Data Values\nWhen data monitoring is enabled, the user is able to view past data values when navigating the trace table. Using the\nPREV and ADVANCE commands, data item values reflect the values from when that statement was executed. These\nvalues are protected -- you cannot update data items while viewing past data values.\nThe DATAMON command can be very CPU intensive -- it requires a significant amount of storage. Therefore, this\ncommand should be used with caution.\nIndirect Commands\nThe InterTest Indirect Commands facility lets you specify a set of indirect commands to be executed in one of two ways:\n\u2022Automatically, when a breakpoint pointing to that set of commands is reached\n\u2022On demand, when you are at a breakpoint and use the Breakpoint Primary Option menu to resume execution with an\nindirect command (the fastpath is =4.5 from any breakpoint)\nBy using indirect commands, you can dynamically modify or correct programs without having to leave your test session to\nrecompile your program.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dc41a2c36838-2", "text": "recompile your program.\nWith the indirect commands facility, you can do the following actions:\n 426", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5571d0dcd924-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Change the flow of control in your program\n\u2022Test conditions based on specified variables\n\u2022Change the value of specified variables\n\u2022Create and execute commands as a group, like adding a new subroutine\n\u2022Automatically resume execution of your program at the same or different location\n\u2022Define abbreviations for variables with long names\nNOTE\nIndirect commands are not supported in a CICSPlex environment and they are not saved in the MLOG when\nsession logging is turned on. \nCode Indirect Commands\nInterTest provides an indirect commands facility for coding the statements. You can access it from the source listing or\nfrom the ITST menus.\n1.To access the indirect commands facility from the Source Listing Display screen, type ICMDS in the command line or\n11 in the Option # field and press Enter, as shown in the following screen:\nCA InterTest for CICS  - PROTSYM FILE SOURCE LISTING DISPLAY             \nCOMMAND ===> icmds                                                             \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01\n                                        Search=                                \n---------+---------------------------------------------------------------------\n   00001 ID DIVISION.                                                         \n   00002 PROGRAM-ID. COBDEMO.                                                 \n   00003 ENVIRONMENT DIVISION.                                                \n   00004 DATA DIVISION.                                                       \n _ 00005 WORKING-STORAGE SECTION.                                             \n _ 00006 77  S999-FIELD1             PIC S9(3).                               \n _ 00007 77  S999-FIELD2             PIC S9(3)       VALUE +50.               \n _ 00008 77  999-FIELD1              PIC 9(3).                                \n _ 00009 77  999-FIELD2              PIC 9(3)        VALUE 50.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5571d0dcd924-1", "text": "To access the Indirect Commands facility from the menus, access the Program Monitoring menu (fastpath is ITST 2.1),\nand select the Commands option. Perform the following steps:\n1.Select option 2 - Monitoring on the Primary Option Menu. InterTest displays the Monitoring Menu.\n2.Select option 1 - Programs. InterTest displays the Program Monitoring screen.\n3.In the Program field, type the name of the program for which you want to create indirect commands.\n4.Type an s to the left of the Commands option (Indirect commands), as shown in the following screen. Press Enter.\n--------------------  CA InterTest for CICS  PROGRAM MONITORING  -------------------\n COMMAND ===>                                                                   \n                                                                                \n   Type information and S to set or R to remove option(s) below.               \n                                                                                \n   Program  . . cobdemo_     Program name (or .ALL, .OPTIONS or generic)        \n   User ID  . . _______      User (or .ANY) for whom the program is monitored   \n                                                                                \n   Option       Description                                            More:   + \n _ Status       Display and/or remove monitoring options (S only)               \n _ Monitor      Monitoring (R removes monitoring and all options previously set)\n 427", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "760425022d6c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _ UBP          Unconditional breakpoints (specific program only)               \n _ CBP          Conditional breakpoints (specific program only)                 \n _ RBP          Breakpoints for CICS, DB2, DL/I or external CALL requests       \n _ Stmt Trace   Statement tracing and data monitoring (COBOL only) \n _ New copy     Fetch new copy of program and reset monitoring options (S only) \n s Commands     Indirect commands defined for a specific COBOL or PL/1 program \n _ Replace      CICS resource name replacement options                          \n _ Protect      Storage protection monitoring options                          \n _ Special      Other options (storage allocation, file updating, etc.)         \n _ Composite    Monitor multi-CSECT program's separately compiled components \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7 Backward   8 Forward    9           10           11           12          \nEither access method takes you to the Indirect Commands screen shown in the following example.\nThis example shows the indirect commands that you use to fix the ASRA condition in our COBDEMO demo program,\nwithout recompiling. Setting TASKNUM to 1 alters the demo results.\nUse the clear key to complete the termination of the demo when the \"You have completed the sample InterTest test\nsession\" screen appears.\n  CA InterTest MONITOR COMMAND BUILDER -   COBDEMO  INDIRECT COMMANDS       24 \n                                                                               \n  Term ID (or .ANY or .NO): U039                    Delete ALL: NO             \n                                                                               \n LINE  COMMAND                                                                 \n----- ------------------------------------------------------------------------ \n00010 /* INITIALIZE TASKNUM */                                                 \n00020 MOVE 1 TO TASKNUM                                                        \n00030 EXIT", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "760425022d6c-1", "text": "00020 MOVE 1 TO TASKNUM                                                        \n00030 EXIT                                                                     \n                                                                               \n                                                                               \n                                                                                \n 1 Help       2            3 End        4           5                6         \n 7 Backward   8 Forward    9 Top       10 Bottom   11               12         \nCAIN1261 Indirect command(s) added.                                           \nTo code the indirect commands for your own programs, perform the following steps:\n1.Specify the terminal ID (terminal ID, .ANY or .NO) where the indirect commands will take effect. The default terminal\nvaries according to how you are monitoring the program.\n\u2013If you are monitoring under a User ID of .ANY, the default terminal is the terminal you are using to specify the\nindirect commands.\n\u2013If you are monitoring under your own User ID, the default terminal is .ANY.\n2.Type the statement numbers and the text of the indirect commands as shown previously on the Indirect Commands\nscreen. For more information, see Indirect Commands in Breakpoint Activities and Online Help.\n3.After coding the statements, press PF3 to exit the Indirect Commands facility. If you accessed the facility from the ITST\nmenus, use =X to exit the menus.\nHow to Control the Flow of Execution\nWhen you run your program,if a breakpoint points to indirect commands, the commands are automatically executed\nwithout stopping first. Execution is returned to the program according to the exit command that you specified in your\nindirect commands.\nTo return execution to your program following indirect command processing, use one of the following exit commands:\n 428", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8ef9bf0901b4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBREAK\nInterTest halts indirect command processing and issues a breakpoint display from where the indirect commands\nwere invoked in the program.\nGOTO\nInterTest resumes execution at the program statement number, offset, paragraph name, or indirect command\nstatement number specified after the GOTO command.\nEXIT\nInterTest resumes program execution at the breakpoint location from which the indirect commands were invoked\nand continues debugging the program until the next breakpoint.\nRUN\nInterTest resumes program execution at the breakpoint location from which the indirect commands were invoked\nand ignores all subsequent breakpoints.\nAttach the Indirect Command to Breakpoints\nTo have the indirect commands automatically executed by your program, set an unconditional, conditional, or request\nbreakpoint that points to the first indirect command statement number. When you set a breakpoint with this option, each\ntime the breakpoint takes effect the indirect commands are executed.\nFrom the Source Listing Display screen, set the unconditional or conditional breakpoint as follows:\n1.Display the line in your source code where you want to set the breakpoint to execute the indirect commands.\n2.Type BPO in the command line or 12 in the Option # field (Breakpoint Options), tab down to the line where you want to\nset the breakpoint, type U for unconditional or C for conditional, and press Enter.\nThe Breakpoint Locations menu displays, which lets you set a number of breakpoint options.\n3.Tab to the following option near the bottom of the panel:\nStatement no. of indirect command(s) to be executed:    _____\nand type the first indirect command statement number (leading zeroes are optional), as shown in the following screen.\n    CA InterTest MONITORING COMMAND BUILDER - COBOL BREAKPOINT LOCATIONS      11\n                                                                                \n    SET breakpoint options for   PROG=COBDEMO  for location:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8ef9bf0901b4-1", "text": "SET breakpoint options for   PROG=COBDEMO  for location:                    \n                                                                                \n            000479 Execute indirect command 100                                 \n                                                                                \n                                                                                \n                                                                       After: _ \n                                                                                \n            Enter 'n' to stop only every n'th time:                         ____\n            Term ID (or .ANY or .NO) where breakpoints will take effect:    U080\n            Term ID (or .ANY) that will receive the breakpoints:            U080\n            Statement no. of indirect command(s) to be executed:           10___\n            User ID (or .ANY) who will execute the program:             .ANY    \n                                                                                \n                                                                                \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7            8            9           10           11           12          \n4.Press Enter to process this menu.\n5.If you are setting a conditional breakpoint, enter the condition on the Conditional Breakpoint screen and press Enter.\nYour source listing display shows the indirect command to be executed on the line above the statement with the U or C\nindicator.\n 429", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "92385597eca0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo set a request breakpoint that executes an indirect command, follow the usual steps to set the request breakpoint from\nthe menus. On the Request Breakpoint Selection menu, also type the statement number of the indirect command to\nexecute, as shown in the following screen.\nCA InterTest MONITORING COMMAND BUILDER - REQUEST BREAKPOINT SELECTION  13\n                                                                                \n              Set  one or more types of Request Breakpoints in:                 \n                                PROG=COBDEMO                                    \n                                                                                \n _ ALL commands                    _ DL/I    _ DB2     _ CALLs                  \n                                                                                \n   _ Address, Assign,         _ Storage Control    _ BMS                        \n       Handles, Push, Pop     _ Program Control    _ Trace Control              \n   _ Terminal Control         _ Interval Control   _ Dump Control               \n   x File Control             _ Task Control       _ Batch Data Interchange     \n   _ TD Control               _ Journal Control    _ Built-In Functions         \n   _ TS Control               _ Syncpoints         _ Sys Prog Functions         \n   _ Web access               _ Business Trans     _ 3270 Bridge                \n                                                                                \n   Enter 'n' to stop only every n'th time:                         ____         \n   Term ID (or .ANY or .NO) where breakpoints will take effect:    ____         \n   Term ID (or .ANY) that will receive the breakpoints:            ____         \n   Statement no. of indirect command(s) to be executed:            0010_        \n   User ID (or .ANY) who will execute the program:                 .any____     \n                                                                                \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7            8            9           10           11           12\nReview, Change or Delete Indirect Commands", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "92385597eca0-1", "text": "Review, Change or Delete Indirect Commands\nTo change, add, delete or review indirect commands directly from the Source Listing Display screen, type ICMDS in the\ncommand line or 11 in the Option # field and press Enter. InterTest displays the indirect commands for the default terminal,\nwhich is either the terminal you are working at or the terminal specified on the source listing profile.\nFor more information on the Indirect Commands facility, see Breakpoint Activities.\nReplacement, Protection, and Special Options\nInterTest has many options for specialized testing needs. Just a few are explained here; for more information on all the\nmonitoring options, see CICS Debugging.\nYou can set or remove options from the Monitoring Command Builder menus.\nReplacement Options\nReplacement options allow you to dynamically change the names of CICS resources such as programs, files, transient\ndata queues, and temporary storage.\nOne reason to use replacement options is to correct errors so you can continue testing without recompiling. For example,\nsuppose InterTest halts your program at an automatic breakpoint to prevent an AEIL abend caused by an incorrect file\nname. You can use the Replace File Name option to dynamically change the file name so testing can continue.\n 430", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "935082d8a120-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAnother reason for using replacement options is to use different resources during testing than those hard-coded in the\nprogram. For example, you can specify that the program use a test file rather than the production file named in the\nprogram.\nProtection Options\nWhen InterTest monitors a program, it prevents the program from modifying storage areas it does not own and issuing\nnon-CICS instructions. Protection options let you override the InterTest default rules for modifying main storage, the CSA,\nand load modules. You can do the following procedures with these options:\n\u2022Modify any area of main storage\n\u2022Modify areas in the CSA or CWA\n\u2022Modify a load module\nThese options also prevent a program from modifying specific areas of storage not normally protected.\nThe protection options, which are password protected, provide extra flexibility for special testing needs.\nSpecial Options\nSpecial options alter the InterTest standard monitoring procedures and help you design customized testing scenarios.\nThe No File Updating option prevents a monitored program from updating files. This option is in testing because your file\ndata is unchanged at the end of program execution. This means:\n\u2022You can repeatedly test a program without restoring your files\n\u2022Programs can share the same file without interfering with each other's work\n\u2022A test program can use a production file without affecting data integrity\nOther options provide additional functions. For example:\n\u2022The FOL option lets InterTest continue monitoring even after a program branches directly to another program (wild\nbranch)\n\u2022The MXS option limits the amount of CICS storage a program can use\n\u2022The MXR option limits the number of CICS requests a program can issue\nComposite Module Testing\nComposite support lets you take advantage of all InterTest functions when you test composite modules. A composite\nmodule consists of separately compiled modules link-edited in one load module. These modules may be written in", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "935082d8a120-1", "text": "module consists of separately compiled modules link-edited in one load module. These modules may be written in\ndifferent languages and compiled at different times. Composite support lets you test and debug a called subroutine as if it\nwere a separate program with full symbolic support.\nExample\nSuppose a COBOL program has several subroutines, some written in COBOL, some written in Assembler and PL/I. You\ncan test and debug any of the subroutines just as if it were a main program by setting breakpoints, setting monitoring\noptions, displaying the source listing, and displaying and modifying main and auxiliary storage.\nComposite module monitoring is initiated by specifying the COMPOSITE command in the Source Listing Display screen\nbefore monitoring is activated (PF5) for the program.\nCA InterTest for CICS  - PROTSYM FILE SOURCE LISTING DISPLAY            \nCOMMAND ===> COMPOSITE                                                         \nProgram= COBDEML  Option #       Stmt #                             Margin= 01 \n                                      Search=                                  \n-------------------------------------------------------------------------------\n 431", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "80a01fcec804-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n   00004 DATA DIVISION.                                                        \n _ 00005 WORKING-STORAGE SECTION.                                              \n _ 00006 77  NUM-CHOICES             PIC S9(4) COMP  VALUE +2.                 \n _ 00007 01  DFHAID COPY DFHAID.                                               \n   00008*                                                                      \n   00009*   COPYRIGHT = 5655-018 (C) COPYRIGHT IBM CORP. 1985  =               \n   00010*               THIS MODULE IS \"RESTRICTED MATERIALS OF=IBM\"           \n   00011*               LICENSED MATERIALS - PROPERTY OF IBM   =               \n   00012*               REFER TO COPYRIGHT INSTRUCTIONS        =               \n   00013*               FORM NUMBER G120-2083                  =               \n   00014*                                                                      \n _ 00015 01  DFHAID.                                                           \n _ 00016   02  DFHNULL   PIC  X  VALUE IS ' '.                                 \n _ 00017   02  DFHENTER  PIC  X  VALUE IS ''''.                                \n _ 00018   02  DFHCLEAR  PIC  X  VALUE IS '_'.                                 \n _ 00019   02  DFHCLRP   PIC  X  VALUE IS '\u00a6'.                                \nWhen you specify the COMPOSITE command, InterTest displays the link-edit information for the main program and its\nsubroutines. You can change this information online, as shown in the following screen:\n       CA InterTest for CICS - Composite Support Builder                   \n COMMAND ===>                                                      SCROLL: PAGE\n Define composite support for COBDEML  and press PF5.        Row 00001 of 00003 \n                                                                                \n                                                                                \n * *          *          *        *        *           *", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "80a01fcec804-1", "text": "* *          *          *        *        *           *                        \n _ Link name  Monitor    Offset   Length   Language    Comments                 \n S COBDEML    COBDEML        20      748   IBMCOB 4.2                          \n S ASBIN25    ASBIN25       768      17C   HLASM  6.0                          \n S CSBIN25    CSBIN25       8E8      674   IBMCOB 4.2                          \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n PF1 Help       2            3 End        4            5 Process    6 RFind     \n PF7 Backward   8 Forward    9           10           11           12           \nPress PF5 to enable composite module monitoring so each program can be tested separately.\nDump Analysis with SymDump\nSymDump  for CICS -- the InterTest companion symbolic dump facility for z/OS users -- is a powerful online tool that\nautomatically pinpoints the source statement responsible for an abend. SymDump  was designed to complement InterTest,\nespecially in production regions where programs are not usually monitored. Working with InterTest for CICS, SymDump\n 432", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1b8f500fbccd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nfor CICS lets you bring a dump back to life. Familiar InterTest source listing screens and other facilities, such as the ability\nto view and modify main and auxiliary storage, make it easy to resolve application dumps.\nSymDump  is option  5 - Dump analysis on the InterTest Primary Option Menu.\nWith SymDump , you can do the following actions:\n\u2022Analyze dumps symbolically online, using InterTest source code listings\n\u2022Resolve CICS production dumps from any region; for example, debug production abends from your test region\n\u2022Manage your dump data set, selectively retaining the dumps you want to view and print, and discarding ones you do\nnot need\nWhen you use SymDump  to view a dump, you can display the following items:\n\u2022InterTest breakpoint at the instruction that triggered the abend\n\u2022Formatted system areas\n\u2022Formatted trace table\n\u2022Registers and displacement at the abend\nExample\nSuppose a program not being monitored by InterTest for CICS abended with an ASRA. With SymDump  for CICS, you\ncan display the breakpoint at the statement that triggered the abend even though InterTest for CICS was not active in the\nregion when the abend occurred.\n   CA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED DUMP ANALYSIS    \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #        Displacement=        Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _ 000477 CONTINUE-TASK.                                                        \n   000478**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED                          \n A    ==>     ADD +1 TO TASKNUM.                                                \n     ==>                                                                        \n     ==> ABEND/DUMP CODE: ASRA                                                  \n     ==>", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1b8f500fbccd-1", "text": "==>                                                                        \n     ==> ABEND/DUMP CODE: ASRA                                                  \n     ==>                                                                        \n     ==>      Press PF1 for a detailed description.                             \n     ==>                                                                        \n _ 000480     IF TASKNUM = 1                                                   \n _ 000481         MOVE 'DMAPASR'  TO MAPNAME.                                   \n _ 000482     IF TASKNUM = 2                                                    \n _ 000483         MOVE 'DMAPSUM'  TO MAPNAME.                                   \n _ 000484     IF TASKNUM GREATER 2                                              \n _ 000485         GO TO SEND-END-MSG.                                           \n _ 000486     GO TO REWRITE-TSQ.                                                \n _ 000487 REWRITE-TSQ.                                                          \n   000488*EXEC CICS WRITEQ TS                                                   \n   000489*          REWRITE                                                     \n   000490*          QUEUE(TSQ-NAME)                                          \nNow you can use SymDump  to solve the problem. In this example, you might want to display the contents of TASKNUM,\nor you might want to inspect a file or look at the formatted trace table. SymDump  provides all the tools you need to\ndiagnose and resolve the dump.\n 433", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f7620cf25508-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCOBOL Advanced Demo Session\nThis article contains some advanced features of InterTest for CICS.\nFor more information about the advanced features of InterTest for CICS, see CICS Debugging or the Help facility.\nNew users can postpone this advanced demo session until they are more comfortable with the basic features of InterTest\nfor CICS.\nThis article consists of the following independent sections. Each details a different advanced InterTest for CICS feature:\nOption 01\nReplace a file name.\nOption 02\nLimit the number of CICS requests issued by a program. Limit the amount of storage obtained by a program.\nOption 03\nPrevent a program from updating a file.Use request breakpoints and the FILE facility.\nOption 04\nDisplay variable length data.\nOption 05\nDisplay indexed COBOL table items.\nOption 06\nDetect and prevent a storage violation.\nOption 07\nTest a composite module.\nBefore you proceed with the demo session, you must complete the steps that are outlined in the next section.\nDemo Preliminaries\nThe advanced demo session uses COBDEMO as in the basic session. Before you begin, you must set breakpoints to use\nin different sections of the advanced demo session.\nSet Unconditional Breakpoints\nTo begin, you must bring up the Source Listing display for the COBOL demo program as covered in the basic demo\nsession.\n1.Press PF4 to display the Profile panel. Verify that the Display window is set to \"N\" and that the AutoKeep Display is\n\"ON\". If not, change either or both of them and press Enter.\n   CA InterTest for CICS   - PROTSYM FILE  SOURCE LISTING PROFILE         \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f7620cf25508-1", "text": "Search=                                 \nOPTS 1 Proc div  2 Work-stor 3 Link sect  4 D-map      5 Clst/Pmap More:    +   \n     6 Data xref 7 Proc xref 8 Err msgs   9 Srch fwd  10 Srch bwd               \nPFKS 1 Help      2           3 End        4 Auto prms  5 Monitor    6 Menu      \n     7 Backward  8 Forward   9 Next Wnd  10           11           12 Status    \n------------------------------------------------------------------------------- \nDisplay window   = N         N (None), T (Titles), R (Registers),               \n                             K (Keep), P (Program)                              \nPF7/8 amount     = PAGE      PAGE, HALF, STOP, or a number from 1 to 9999       \n 434", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "729abd65c649-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nStep Timing      = BEFORE    Stop  Before  or  After  the next verb  is executed\nStepping amount  = 001       The number of verbs   to execute                   \nAuto-stepping    = OFF       ON to activate; press PF4 to change values         \nSource List BKPT = ON        OFF to use the detailed breakpoint display         \nFrom terminal ID = U049      Terminal ID where the program will execute         \nBKPT terminal ID = U049      Terminal ID to receive the breakpoint displays     \nUser ID          = .ANY      User ID who will execute this program              \nAutoKeep Display = ON        OFF to deactivate                                  \nCode Counting    = OFF       ON to activate Code Coverage                       \nSDF              = DATA      HEX  for Hexadecimal/Character Format             \n2.Press PF3 to return to the listing.\nNow you are going to set unconditional breakpoints at three procedure names. Setting unconditional breakpoints lets\nyou halt the program so that you can set options and check the contents of data items.\nThe quickest way to set breakpoints at several procedure names is to display a list of all procedure names, and type\nU or ) next to the ones where you want breakpoints. Because a procedure name does not have executable code, the\nunconditional breakpoint halts execution before or after the first verb in the paragraph. The U sets a breakpoint that\nstops before  the first verb. The ) sets a breakpoint that stops after the first verb.\n3.Type L .PX  in the command line or 7 in the Option # field, and press Enter.\nCA InterTest for CICS - PROTSYM FILE SOURCE LISTING DISPLAY             \nCOMMAND ===> l .px                                                             \nProgram= COBDEMO  Option #       Stmt #                                       \n                                        Search=                                \n---------+---------------------------------------------------------------------\n   00001 ID DIVISION.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "729abd65c649-1", "text": "Search=                                \n---------+---------------------------------------------------------------------\n   00001 ID DIVISION.                                                         \n   00002 PROGRAM-ID. COBDEMO.                                              \nInterTest for CICS displays a list of the demo program procedure names, as shown in the following figure.\nYou are going to set unconditional \"before\" breakpoints at three procedure names: AFTER-REWRITE, DO-READ-\nVAR, and LOOP-RTN.\n4.Type U to the left of AFTER-REWRITE, DO-READ-VAR, and LOOP-RTN.\n5.Press Enter.\n   CA InterTest for CICS   - PROTSYM FILE  SOURCE LISTING DISPLAY          \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n----------------------------------------+-------------------------------------- \n _ DEFINED      PROCEDURE NAMES         REFERENCES                              \n u    923 AFTER-REWRITE                                                         \n _    800 CICS-LOOP                     P798                                    \n _    477 CONTINUE-TASK                 G402 G470                               \n _    667 DATA-NAME                                                             \n u    686 DO-READ-VAR                   G683                                    \n _    555 EXPANDED-DEMO                 G399 G474 G475                          \n _    884 GEN-ERR                       D378 D435 D633                          \n _    821 GETMAIN-LOOP                  P819                                    \n _    661 INITIALIZE-TABLE              P648                                    \n _    538 LAST-SCREEN                   D530                                    \n _    982 LINK-DEML                     D979                                    \n u    797 LOOP-RTN                                                              \n _    737 MOVE-RECORD                                                           \n _    792 MXR-OPTION                    D974                                    \n 435", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8d53045bb2e0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _    806 MXS-OPTION                    G799                                    \n _    437 NO-OPTS                       D410                                    \n _    830 NO-STORAGE                    D817                                    \n _    777 NOT-OPEN                      D708           \nInterTest for CICS sets the breakpoints and re-displays the screen with uppercase Us.\nSet Request Breakpoints\nRequest breakpoints make it easy for you to halt your program at various points so you can check program processing.\nFor example, you can halt the program before every READ command, single-step through the read instructions, and then\ncheck main storage to make sure the program read the correct record.\nYou can set request breakpoints to halt a program before CICS commands and macros and other calls, such as calls to\nDL/I or DB2. You can set request breakpoints prior to all CICS commands as you might have done with IBM CEDF. You\ncan also set request breakpoints prior to specific commands, such as File Control or Program Control commands.\nFor option 03 of the advanced demo session, you must set request breakpoints at all File Control REWRITE commands in\nthe demo program. To set request breakpoints in the demo program, use the following procedure:\n1.Specify the RBP command on the command line.\nInterTest for CICS displays the Request Breakpoint Selection menu on which you specify the type of request\nbreakpoint, such as all CICS commands, File Control, and Task Control.\nCA InterTest MONITORING COMMAND BUILDER - REQUEST BREAKPOINT SELECTION  13\n                                                                                \n              Set  one or more types of Request Breakpoints in:                 \n                                PROG=COBDEMO                                    \n                                                                                \n _ ALL commands                    _ DL/I    _ DB2     _ CALLs                  \n                                                                                \n   _ Address, Assign,         _ Storage Control    _ BMS", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8d53045bb2e0-1", "text": "_ Address, Assign,         _ Storage Control    _ BMS                        \n       Handles, Push, Pop     _ Program Control    _ Trace Control              \n   _ Terminal Control         _ Interval Control   _ Dump Control               \n   s File Control             _ Task Control       _ Batch Data Interchange     \n   _ TD Control               _ Journal Control    _ Built-In Functions         \n   _ TS Control               _ Syncpoints         _ Sys Prog Functions         \n   _ Web access               _ Business Trans     _ 3270 Bridge                \n                                                                                \n   Enter 'n' to stop only every n'th time:                         ____         \n   Term ID (or .ANY or .NO) where breakpoints will take effect:    ____         \n   Term ID (or .ANY) that will receive the breakpoints:            ____         \n   Statement no. of indirect command(s) to be executed:            _____        \n   User ID (or .ANY) who will execute the program:                 ________     \n                                                                                \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6      \n PF7            8            9           10           11           12\n2.Tab to the File Control field and type S.\n3.Press Enter.\nInterTest for CICS displays the File Control Request Breakpoint Selection menu that is shown in the following screen.\nCA InterTest MONITORING COMMAND BUILDER - REQUEST BREAKPOINT SELECTION    \n                                                                                \n            Set  one or more types of File Control COMMANDS IN:                 \n 436", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "48c87d491bc0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                PROG=COBDEMO                                    \n                                                                                \n              _ All commands                                                    \n                                                                                \n                    _ READ                                                      \n                    _ WRITE                                                     \n                    _ REWRITE                                                   \n                    _ DELETE                                                    \n                    _ UNLOCK                                                    \n                    _ STARTBR                                                   \n                    _ READNEXT                                                  \n                    _ READPREV                                                  \n                    _ ENDBR                                                     \n                    _ RESETBR                                                   \n                                                                                \n              Enter 'n' to stop only every n'th time   ____\n                                                                                \n                                                                                \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7            8            9           10           11           12          \nOn this menu, you can select the specific File Control commands where you want to set request breakpoints. In this\ncase, select REWRITE to halt the program prior to each File Control REWRITE command.\n4.Tab to the REWRITE command field.\n5.Type S and press Enter.\nCA InterTest MONITORING COMMAND BUILDER - REQUEST BREAKPOINT SELECTION    \n                                                                                \n            Set  one or more types of File Control COMMANDS IN:                 \n                                PROG=COBDEMO                                    \n                                                                                \n              _ All commands                                                    \n                                                                                \n                    _ READ                                                      \n                    _ WRITE                                                     \n                    s REWRITE  \u00e7                     \n                    _ DELETE\nInterTest for CICS sets request breakpoints prior to each File Control REWRITE command in the demo program and\nredisplays the Program Monitoring Menu.\nThe next topic is necessary only if you want to use the composite support option. Composite support is an InterTest for\nCICS feature designed to aid programmers who are responsible for testing and debugging called subroutines.\n\u2022If you do not want to use the composite support option, skip to ExecutetheDemoProgram .", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "48c87d491bc0-1", "text": "\u2022If you do want to use the composite support option, perform the steps in Composite Support that follows.\nComposite Support\nComposite support lets you use InterTest for CICS to test and debug composite modules. A composite module  is a load\nmodule, defined to CICS as a program, which consists of separately compiled or assembled parts brought together\nwhen the module is link-edited. In the demo session, the part of the composite module that receives control from CICS\nis referred to as the main program ; the remaining programs are referred to as subroutines . The main program and\nsubroutines can be written in the same or different languages.\n 437", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d8901a41eeef-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nComposite support lets you test and debug a subroutine, such as an external procedure, as if the subroutine were\na separate program with full symbolic support. In this case, you can set breakpoints and other monitoring options\nindividually for any subroutine. InterTest for CICS generates automatic breakpoints in the subroutine when it detects an\nerror that would otherwise cause the program to abend.\nTo demonstrate this feature, you set composite support for a composite module, to which the demo program links. The\ncomposite module that you use is COBDEML.\nThe composite module has two called subroutines that you want InterTest for CICS to monitor -- subroutine CSBIN25\nwritten in COBOL, and subroutine ASBIN25 written in Assembler.\nFollow these steps:\n1.In the Program Monitoring Menu, press PF4 until the Source Listing Display is redisplayed.\n2.In the Program field, overtype the name of the demo program with the name of the composite module COBDEML, and\npress Enter.\n   CA InterTest for CICS  - PROTSYM FILE  SOURCE LISTING DISPLAY          \nCOMMAND ===>                                                                    \nProgram= COBDEML  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n      YEARWINDOW(1900)                                                          \n      ZWB                                                                       \n   000001 ID DIVISION.                                                          \n   000002 PROGRAM-ID. COBDEML.                                                  \n   000003 ENVIRONMENT DIVISION.                                                 \n   000004 DATA DIVISION.                                                        \n _ 000005 WORKING-STORAGE SECTION.                                              \n _ 000006 77  NUM-CHOICES             PIC S9(4) COMP  VALUE +2.                 \n _ 000007 COPY DFHAID.                                                          \n   000008*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d8901a41eeef-1", "text": "_ 000007 COPY DFHAID.                                                          \n   000008*                                                                      \n   000009*               @BANNER_START@                                         \n   000010*               Licensed Materials - Property of IBM                   \n   000011*                                                                      \n   000012*               \"Restricted Materials of IBM\"                          \n   000013*                                                                      \n   000014*               5655-147                                               \n   000015*                                                                      \n   000016*               (C) Copyright IBM Corp. 1985                           \n   000017*                                                                     \nInterTest for CICS displays the source listing for the composite module.\n3.Press PF5 to activate program monitoring for COBDEML.\nNOTE\nThese steps are only to monitor COBDEML as a simple program. To set composite monitoring, see Option\n07 How to Test a Composite Module.\nCheck the Monitoring Status Display\nBefore you continue, check the Monitoring Status display for the program COBDEMO. You should see the options that\nyou set for the program. These options are needed to complete the Demo Options in the rest of this article.\n1.On the Program Monitoring menu, scroll the Options list to the beginning. Either enter the TOP command and press\nEnter or press PF7.\n 438", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1f8f5cccfe52-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n--------------------  CA InterTest for CICS  PROGRAM MONITORING  ------------------\n COMMAND ===>                                                                   \n                                                                                \n \n                                                                                \n   Program  . . cobdemo_     Program name (or .ALL, .OPTIONS or generic)        \n   User ID  . . _______      User (or .ANY) for whom the program is monitored   \n                                                                                \n   Option       Description                                            More:   +\n s Status       Display and/or remove monitoring options (S only)               \n _ Monitor      Monitoring (R removes monitoring and all options previously set)\n _ UBP          Unconditional breakpoints (specific program only)               \n _ CBP          Conditional breakpoints (specific program only)                 \n _ RBP          Breakpoints for CICS, DB2, DL/I or external CALL requests       \n _ Stmt Trace   Statement tracing and data monitoring (COBOL only) \n _ New copy     Fetch new copy of program and reset monitoring options (S only) \n _ Commands     Indirect commands defined for a specific COBOL or PL/1 program \n _ Replace      CICS resource name replacement options                          \n _ Protect      Storage protection monitoring options                          \n _ Special      Other options (storage allocation, file updating, etc.)         \n _ Composite    Monitor multi-CSECT program's separately compiled components \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7 Backward   8 Forward    9           10           11           12          \n2.Type an s next to the Status option to obtain a Monitoring Status display of the COBDEMO program.\nThe Monitoring Status display for COBDEMO should show the three breakpoints that are needed to perform the Demo\nSession Options; the Request Breakpoint (RBP) at all REWRITE commands, and the two Unconditional Breakpoints", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1f8f5cccfe52-1", "text": "(UBPs).\n---------------  CA InterTest for CICS  MONITORING STATUS  --------------\n COMMAND ===>                                                                   \n                                                                                \n   Type + to expand or - collapse option levels displayed below,                \n          or R to remove option(s).                                             \n                                                                       More:   +\n     Option     Description                Attributes                           \n _ - COBDEMO    Program monitor entry      IBMCOB 3.2                           \n _ - |-.ANY     User monitoring options    Active                               \n       |        Symbolic listing file      PROTSYM                              \n _ -   |-UBP    Unconditional breakpoint   'LOOP-RTN'                           \n       |        Option ID                  EFDD08F4                             \n       |        From, to terminals         U045, U045                           \n _ -   |-RBP    Request breakpoint(s)      REWRITE                              \n       |        Option ID                  E17C6B11                             \n       |        From, to terminals         U045, U045                           \n _ -   |-UBP    Unconditional breakpoint   'DO-READ-VAR'                        \n       |        Option ID                  87D8D74C                             \n       |        From, to terminals         U045, U045                           \n _ -   |-UBP    Unconditional breakpoint   'AFTER-REWRITE'                      \n       |        Option ID                  5B7ED470                             \n                                                                                \n 439", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c64d94162fdc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n PF1 Help       2 Refresh    3 End        4 Return     5 Collapse   6 Expand    \n PF7 Backward   8 Forward    9           10           11           12          \n3.Press PF3 to exit back to the Program Monitoring menu.\n4.Type =X in the Command field to exit the menus, then PF3 to exit Source Listing.\nExiting the menus and Source Listing returns you to CICS, where you can begin executing the COBDEMO program.\nExecute the Demo Program\nNow you are ready to execute the demo program.\n1.Exit to CICS using PF3 End. You might need to press PF3 several times.\n2.On a clear CICS screen, enter the transaction identifier DEMC of the COBDEMO program.\n3.Press Enter.\nThe following Welcome Screen appears.\n****************************************************************************** \n****************************************************************************** \n*****                                                                    ***** \n*****                             Welcome to the                         ***** \n*****                       CA InterTest Demo Session                    ***** \n \n*****                                                                    ***** \n*****                                                                    ***** \n*****              Before proceeding, please have on hand the            ***** \n*****              guide which accompanies the Demo Session.             ***** \n*****                                                                    ***** \n*****                                                                    ***** \n*****     Please make sure that the program COBDEMO is monitored by      ***** \n*****     CA InterTest. This program will abend if it is not monitored.  ***** \n*****                                                                    ***** \n*****     To turn the monitor on, press CLEAR and follow the steps       ***** \n*****     outlined in the documentation.                                 ***** \n*****                                                                    ***** \n*****     If the monitor is already on, press ENTER to begin the         ***** \n*****     Basic Demo Session or PF2 to go to the Options Menu.           ***** \n*****                                                                    ***** \n******************************************************************************", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c64d94162fdc-1", "text": "*****                                                                    ***** \n****************************************************************************** \n******************************************************************************\nFrom the Welcome Screen, you can access the Options Menu. The options are described in detail in the following\nsection.\n4.Press PF2 to go to the Options Menu of the demo .\nThe demo program displays the Options Menu, as shown next.\n    **********************************************************************     \n    ****                                                              ****      \n    ****                  CA InterTest Demo Session                   ****      \n    ****                         Options Menu                         ****      \n    ****                                                              ****      \n    **********************************************************************      \n                                                                                \n    01  Replace file control ID                                                 \n    02  Limit CICS storage and requests                                         \n 440", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ecf69e63b95f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    03  No file updating                                                        \n    04  Display variable length data                                            \n    05  Work with table items                                                   \n    06  Storage violation detection                                             \n    07  Composite support                                                       \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                 Key in request:  01                            \n                                                                                \n         Press ENTER to continue or CLEAR to terminate.                       \nOption 01 Replace a File Control ID\nThis section of the demo session illustrates how to replace a File Control ID. The demo program is attempting to read and\ndisplay a record, but the file name that is specified in the program is incorrect, possibly due to misspelling.\nNOTE\nBefore proceeding, ensure you complete the steps outlined in the Demo Preliminaries  section, and that the\nInterTest Demo Session Options Menu is displayed on your screen.\n1.Select option 01  and press Enter.\nThe demo program displays the following screen, which describes what occurs in this part of the demo session.\n    **********************************************************************      \n    ****                                                              ****      \n    ****                  CA InterTest Demo Session                   ****      \n    ****                Replace File Control ID Option                ****      \n    ****                                                              ****      \n    **********************************************************************      \n                                                                                \n    The program attempts to read file PROTH. Because the file name has been     \n    incorrectly specified, this would cause a DSIDERR condition which would     \n    result in an AEIL abend. Instead, here is what will happen:                 \n                                                                                \n    1. CA InterTest halts the program at an automatic breakpoint.              \n    2. You set the Replace File Control option to change the file name          \n       without recompiling.                                                    \n    3. You re-execute the program from the point at which it first tried        \n       to read the file.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ecf69e63b95f-1", "text": "to read the file.                                                       \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n    When this section of the demo completes, you will return to the             \n    Options Menu.                                                              \n                                                                                \n              Press ENTER to continue or CLEAR to terminate.\n2.Press Enter.\nInterTest for CICS halts the demo program at an automatic breakpoint.\n 441", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "13d8bec29a46-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPrevent an AEIL Abend\nThe following screen shows that InterTest for CICS has halted the demo program at an automatic breakpoint before an\nAEIL abend could occur.\n   CA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT       \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ RECORD-KEY                      | 00000000000000000000000000000000000000 \n---------+--------------------------------------------------------------------- \n   000711*EXEC CICS STARTBR DATASET('PROTH') RIDFLD(RECORD-KEY)                 \n   000712*          END-EXEC.                                                   \n  A    ==>     Call 'DFHEI1' using by content x'060cb000070020a000f0f0f3f9f3           ==>                  \n                                                            ==> CICS abend intercepted. Abend code = AEIL.  \n EXEC CICS request was           ==> STARTBR. Now stopped AFTER the CALL.                                    \n     ==>                                                                              ==>      Press PF1 for a\n detailed description.                             \n     ==>                                                                        \n _ 000714-    '404040' by content 'PROTH   ' by content x'0000' by content      \n _ 000715     x'0000' by reference RECORD-KEY end-call.                         \n   000716                                                                       \n _ 000717     MOVE +1 TO SUB.                                                   \n   000718*EXEC CICS READNEXT DATASET('PROTH')                                   \n   000719*          SET(ADDRESS OF RECORD-AREA)                                 \n   000720*          LENGTH(REC-LEN) RIDFLD(RECORD-KEY) END-EXEC.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "13d8bec29a46-1", "text": "_ 000721     Call 'DFHEI1' using by content x'060ef400070100b000f0f0f3f9f6   \nThe abend that InterTest for CICS prevented would have resulted from the EXEC CICS STARTBR command. InterTest for\nCICS highlighted the CALL statement that is part of the generated EXEC CICS STARTBR command.\nWhat is the problem?\nThe data set name PROTH is wrong; it should be PROTHLF.\nHow can it be fixed?\nInterTest for CICS lets you dynamically correct the file name and continue testing. The following section explains this\nprocess.\nChange the File Name\nInterTest for CICS lets you dynamically change an incorrect file name in the middle of your test session. This feature lets\nyou continue testing without recompiling your program. In this case, you can correct a simple typo in the demo program\nwithout interrupting your test session or changing your File Control Table.\nTo change the file name, you must access the Replacement Options menu.\n1.Specify the RO command on the Source Listing Display command line.\nInterTest displays the Replacement Options menu.\nThe Set Replacement Options menu lets you dynamically change a program name, file name, transient data queue\nname, or temporary storage ID.\n2.Tab to the Replace file name field.\n3.Specify the incorrect file name (proth) in the first column and the correct file name (prothlf) in the second column, and\npress Enter.\n 442", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1b0c97f6bbf1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n            CA InterTest MONITORING COMMAND BUILDER - REPLACEMENT OPTIONS     20\n                                                                                \n     SET one or more options to replace one CICS resource name with another in: \n                                PROG=COBDEMO                                    \n                                                                                \n                                                                                \n      Replace program name:         ________   with   ________                  \n      Replace file name:            PROTH___   with   PROTHLF_                  \n      Replace TD queue name:        ____       with   ____                      \n      TS selection mask:            ____________________________________        \n      TS replacement mask:          ____________________________________        \n                                                                                \n      Limit monitoring to your terminal - '*'  or TERMID:       ____            \n      User ID (or .ANY) who will execute the program:           .ANY            \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7            8            9           10           11           12          \nInterTest dynamically replaces the incorrect file name when the program executes. InterTest then redisplays the\nProgram Monitoring menu.\n4.Press PF4 until the Source Listing Breakpoint Screen is redisplayed.\nResume Execution\nNow that you have dynamically corrected the file name, you are ready to resume program execution. Be aware however\nthat when an error occurs in a paragraph that contains a CICS command, you should back up to the paragraph-name\nrather than resume execution at the specific instruction. Some CICS internal processing might have occurred prior to the\nbreakpoint. In this case, it is important to resume execution at READ-DATASET to ensure that the demo proceeds as\nexpected.\n1.To position the listing so the READ-DATASET label is displayed on the source listing breakpoint screen, press PF7,", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1b0c97f6bbf1-1", "text": "tab to READ-DATASET, and enter G (go).\n2.Press Enter  to resume program execution.\n   CA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT       \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ RECORD-KEY                      | 00000000000000000000000000000000000000 \n---------+--------------------------------------------------------------------- \n _ 000695         GO TO SEND-REWRITE-RETURN.                                    \n _ 000696     IF  TASK-SWITCH3 EQUAL 'A'                                        \n _ 000697         GO TO READ-DATASET                                            \n _ 000698     ELSE                                                              \n _ 000699         GO TO SEND-MAP00.                                             \n 443", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8d378e4a4a51-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n g 000700 READ-DATASET.                                                         \n   000701*EXEC CICS HANDLE CONDITION                                            \n   000702*          DSIDERR                                                     \n   000703*          NOTOPEN(NOT-OPEN)                                           \n   000704*          END-EXEC.                                                   \n _ 000705     Call 'DFHEI1' using by content x'0204800007130c00000000000000     \n _ 000706-    '0000000000000000f0f0f3f8f7404040' end-call                       \n _ 000707      Service label                                                    \n _ 000708      Go to  NOT-OPEN depending on dfheigdi.                           \n _ 000709     MOVE ZEROES TO RECORD-KEY.                                        \n   000710**** NOTE * DATASET NAME IS WRONG ****                                 \n   000711*EXEC CICS STARTBR DATASET('PROTH') RIDFLD(RECORD-KEY)             \nThe program resumes execution and displays the record that it has read on your screen, as illustrated in the following\nexample. The demo program successfully read a record from file PROTHLF (the InterTest for CICS Help file). The\ndemo program displays the first record in that file.\n    **********************************************************************     \n    ****                                                              ****     \n    ****                  CA InterTest Demo Session                   ****      \n    ****             Replace File Control Identifications             ****      \n    ****                                                              ****      \n    **********************************************************************      \n                                                                              \n         Record retrieved: * 0000000000    VE0301I....T... ZELP F.... *         \n                           * ... M..... M...                          *         \n                           *                                          *         \n                           *                                          *         \n         Record length = 0960                                                   \n                                                                                \n         You have now successfully utilized the REPLACE option", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8d378e4a4a51-1", "text": "You have now successfully utilized the REPLACE option                  \n \n                                                                                \n         Press ENTER to continue or CLEAR to terminate.\nReview What Happened\nIn this part of the demo session, the following events occurred:\n\u2022The demo program was stopped at an automatic breakpoint caused by an incorrect file name.\n\u2022You dynamically corrected the file name and resumed program execution.\nReplacing the incorrect file name in the demo program allowed you to continue testing that program without recompiling it.\nOf course, if one of your programs or the CICS FCT has an incorrect file name, you must correct the source code.\nIn this case, the error was caused by a simple typo. However, the Replacement Options are useful in many situations. For\nexample:\n\u2022You can dynamically change a file name to test a program using a different file. Perform this action to use a test file\nwithout altering the name of the production file that is hard-coded in the program.\n\u2022You can change a program name or transient data queue name to test a program or queue other than the ones that\nare hard-coded.\nThis concludes Option 01 of the advanced demo session. Press Enter to continue with the demo session, or press Clear\nto terminate the session.\n 444", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d6e04df99e0c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nOption 02 Limit CICS Storage and Requests\nThis section of the demo session shows how to limit CICS main storage and CICS requests for a specific program (the\ndemo program).\nTwo InterTest for CICS options are detailed in this part of the demo session:\n\u2022The MXS option limits the amount of main storage that is obtained by a task. This option is useful in detecting program\nerrors that cause a task to acquire an excessive amount of storage.\n\u2022The MXR option limits the number of CICS requests, commands, and macros that a program can issue. This option is\nuseful in detecting program loops that generate an excessive number of CICS requests.\nNOTE\nBefore you proceed, ensure that you complete the steps that are outlined in the Demo Preliminaries section, and\nthat the InterTest Demo Session Options Menu is displayed on your screen.\n1.Select option 02, and press Enter.\nThe demo program displays a screen that describes what occurs in this part of the demo session.\n    **********************************************************************      \n    ****                                                              ****      \n    ****                  CA InterTest Demo Session                   ****      \n    ****          MXR Option - Limit Number of CICS Requests          ****      \n    ****          MXS Option - Limit Amount of CICS Storage           ****      \n    ****                                                              ****      \n    **********************************************************************      \n                                                                                \n    The program has a loop containing a CICS request and another loop           \n \n    containing a GETMAIN request. Here is what will happen:                     \n                                                                                \n    1. The program is halted at an unconditional breakpoint before the loops.  \n    2. You set the MXS and MXR options to limit storage and CICS requests.     \n    3. The program continues to execute.                                       \n    4. CA InterTest halts the program at automatic breakpoints when the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d6e04df99e0c-1", "text": "4. CA InterTest halts the program at automatic breakpoints when the         \n       limits are exceeded.                                                    \n    5. You remove the options and the program completes execution.             \n                                                                                \n                                                                                \n                                                                                \n    When this section of the demo completes, you will return to the             \n    Options Menu.                                                              \n                                                                                \n              Press ENTER to continue or CLEAR to terminate.\n2.Press Enter.\nInterTest for CICS halts the program at the procedure name LOOP-RTN (because you set an unconditional breakpoint\nthere as part of the Demo Preliminaries). Because a procedure name does not have executable code, the breakpoint\nyou set halts execution before the first verb in the paragraph.\nIn this case, InterTest for CICS halts the demo program at the highlighted PERFORM command. Now you can access\nthe Special Options menu to set the options you need for testing.\nSet the MXS and MXR Options\n1.In the Command field, specify the SO command.\n 445", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "403d0e986251-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterTest for CICS displays the Special Options menu. The Special Options menu lets you set several options to\nchange how InterTest for CICS monitors a program.\nThe following shows how to set two options:\n\u2013MXS, to limit the amount of CICS main storage acquired by the demo program\n\u2013MXR, to limit the total number of CICS requests issued by the demo program\n2.Specify 50,000 bytes as the maximum amount of main storage the demo program obtains. Also specify 20 as the\nmaximum number of CICS requests the demo program issues.\n3.Tab to the MXS field and type in 60000, as shown in the following screen.\n4.Tab to the MXR field and type in 20, as shown in the following screen.\n5.Press Enter.\n            CA InterTest MONITORING COMMAND BUILDER - SPECIAL OPTIONS         22\n                                                                                \n      SET  one or more options to override the default monitoring rules in:     \n                                PROG=COBDEMO                                    \n                                                                                \n           Enter X next to each option desired:                                 \n                                                                                \n                 Source Listing Breakpoint      (SLB) _                         \n                 No file updating               (NUP) _                         \n                 Reentrancy check               (RNT) _                         \n                                                                                \n           Follow monitoring (ON, name, NOPPT)  (FOL) ________                  \n           Number of times to be monitored      (MUS)                           \n           Limit total size of CICS storage     (MXS) 60000__                   \n           Limit total number of CICS requests  (MXR) 20_____                   \n           Structure Display Format (HEX,DATA)  (SDF) ____                      \n                                                                                \n           Set local automatic breakpoint ('*', TERMID, .ANY, OFF)     ____", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "403d0e986251-1", "text": "Set local automatic breakpoint ('*', TERMID, .ANY, OFF)     ____     \n           Limit monitoring to your TERMINAL - '*' or TERMID:          ____     \n           User ID (or .ANY) who will execute the program:             .ANY     \n                                                                                \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7            8            9           10           11           12        \nInterTest for CICS limits main storage and CICS requests for the demo program and redisplays the Program\nMonitoring screen.\n6.Press PF4 until you return to the Source Listing Breakpoint screen.\n7.Press PF5 to continue program execution.\nThe demo program resumes execution.\nLimit CICS Requests\nThe next screen that you see is an automatic breakpoint display screen. InterTest for CICS halted the demo program at an\nautomatic breakpoint because the maximum number of CICS requests (20) is exceeded.\n 446", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2cb8bddebb2b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nIf you are working on a system with LE 370 runtimes, you might reach the automatic breakpoint for the MXS\n(max storage size) first. If you do, simply perform the demo in the following order:\n1.Remove the MXS options by typing STATUS, in the command line then 'R' next to the MXS option, and hit enter.\nResume execution.\n2.After stopping for the MXR trigger value, remove it the same as the MXS and continue.\n3.The demo executes to completion.\nThe instruction that triggered the automatic breakpoint is within a loop containing a CICS request.\n   CA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT       \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n   000801*EXEC CICS ASKTIME                                                     \n   000802*          END-EXEC.                                                   \n A    ==>     Call 'DFHEI1' using by content x'100200000700001300f0f0f4f5f4     \n     ==>                                                                        \n     ==> MXR (max CICS requests) trigger value exceeded.                        \n \n     ==>                                                                        \n     ==>      Press PF1 for a detailed description.                             \n     ==>                                                                        \n _ 000804-    '404040' end-call.                                                \n   000805                                                                       \n _ 000806 MXS-OPTION.                                                                                 \nRemove the MXR Option\nNow you can remove the MXR option so that the demo program continues executing. In your program, you would\nexamine the instructions that are generating excessive CICS requests.\n1.Type STATUS on the command line and press Enter.\nInterTest for CICS displays the Monitoring Status screen.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2cb8bddebb2b-1", "text": "InterTest for CICS displays the Monitoring Status screen.\n---------------  CA InterTest for CICS   MONITORING STATUS  --------------\nCOMMAND ===>                                                                   \n                                                                               \n  Type + to expand or - collapse option levels displayed below,                \n         or R to remove option(s).                                             \n                                                                      More:   +\n    Option     Description                Attributes                           \n_ - COBDEMO    Program monitor entry      IBMCOB 3.2                           \n    |          Waiting at breakpoint      Task 00156, ABP since 10:33 a.m.     \n_ - |-.ANY     User monitoring options    Active                               \n      |        Symbolic listing file      PROTSYM                              \n_     |-MXR    Maximum CICS requests      20                                   \n_     |-MXS    Maximum total storage      50000                                \n_ -   |-RBP    Request breakpoint(s)      REWRITE                              \n      |        Option ID                  ECEAD6CB                             \n      |        From, to terminals         U061, U061                           \n_ -   |-UBP    Unconditional breakpoint   'AFTER-REWRITE'                      \n      |        Option ID                  D87A3D68                             \n 447", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bf31b9b81780-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n      |        From, to terminals         U061, U061                           \n_ -   |-UBP    Unconditional breakpoint   'LOOP-RTN'                           \n      |        Option ID                  6CD871EC                            \n2.Remove the MXR option by typing an r next to the MXR breakpoint entry and pressing Enter.\nInterTest for CICS removes the breakpoint.\n3.Press PF3 to return to the Source Listing Breakpoint screen.\n4.Press PF5 to resume program execution.\nLimit Acquisition of Storage\nThe next screen that you see is an automatic breakpoint display. InterTest for CICS halts the demo program at an\nautomatic breakpoint because the maximum main storage limit of 60,000 has been exceeded. Usually, the instruction that\ntriggered the automatic breakpoint is within a loop, which contains a GETMAIN request.\n   CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT       \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ DFHB0020                        | +06144.                                \n---------+--------------------------------------------------------------------- \n   000825*          END-EXEC.                                                   \n _ 000826     Move 6144 to dfhb0020                                             \n A    ==>     Call 'DFHEI1' using by content x'0c02c0000700008c00f0f0f4f6f8     \n     ==>                                                                        \n     ==> MXS (max storage size) trigger value exceeded.                         \n     ==>                                                                        \n     ==>      Press PF1 for a detailed description.                             \n     ==>                                                                        \n _ 000828-    '404040' by reference ADDRESS OF GETMAIN-AREA by reference", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bf31b9b81780-1", "text": "_ 000829     dfhb0020 end-call.                                                \n _ 000830 NO-STORAGE.                                                           \n _ 000831     MOVE 'B' TO TASK-SWITCH3.                                         \n _ 000832     MOVE 'NO STORAGE' TO ERRORO.                                      \n   000833*EXEC CICS SEND                                                        \n   000834*          MAP ('DERROR')                                              \n   000835*          MAPSET ('IN25CMP')                                          \n   000836*          ERASE                  \nRemove the MXS Option\nNow you can remove the MXS option so that the demo program continues executing. In your program, you would\nexamine the instructions that are causing the program to obtain excessive amounts of storage.\n1.Type STATUS on the command line and press Enter.\nInterTest for CICS displays the Monitoring Status screen.\n----------------  CA InterTest for CICS MONITORING STATUS  ----\n COMMAND ===>                                                        \n                                                                      \n   Type + to expand or - collapse option levels displayed below      \n          or R to remove option(s).                                \n                                                                   More:   +\n 448", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d6e9067b13bc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n     Option     Description                Attributes              \n _ - COBDEMO    Program monitor entry      COBOL                    \n     |          Waiting at breakpoint      Task 00083, ABP since 03:50p.m.\n _ - |-.ANY     User monitoring options    Active                       \n       |        Symbolic listing file      PROTSYM                  \n r     |-MXS    Maximum total storage      50000\n2.Remove the MXS option by typing an R next to the MXS breakpoint entry and pressing Enter.\nInterTest for CICS removes the breakpoint.\n3.Press PF3 to return to the Source Listing Breakpoint screen.\nDemo Program Completes Execution\nPress PF5 to resume program execution.\nThe demo program completes execution. InterTest for CICS returns to the demo Options Menu.\nReview What Happened\nIn this part of the test session, set two options to help test the demo program, as shown following:\n\u2022The MXR option lets you limit the number of CICS requests the program could issue. When the demo program\nexceeded this limit, InterTest for CICS halted the program. This feature helps you find program instructions within a\nloop that generate an excessive number of CICS requests.\n\u2022The MXS option let you limit the amount of main storage that is used by the program. When the demo program\nexceeded the amount of storage that you specified, InterTest for CICS halted the program.\nThis feature helps you find commands or macros within a loop that are obtaining excessive amounts of storage.\nThis concludes Option 02 of the advanced demo session. Press Enter to continue with the demo session or press Clear to\nterminate the session.\nOption 03 Prevent a Program from Updating a File\nThis section of the demo session details how to execute a program without having it update a file.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d6e9067b13bc-1", "text": "This section of the demo session details how to execute a program without having it update a file.\nThe No File Updating option is useful when you are testing a program. Preventing a program from updating a file means\nthat your test data remains unchanged at the end of each program execution. You can test the program repeatedly without\nhaving to recreate test data.\nMany programs can use the same test file without interfering with the work of others. You can even allow a test program to\nuse a production file because the integrity of the file is preserved.\nNOTE\nBefore you proceed, complete the steps that are outlined in Demo Preliminaries,  and ensure that InterTest\nDemo Session Options Menu is displayed on your screen.\nAlso verify that the InterTest for CICS checkpoint file (PROTCPF) is defined to your CICS region, and that the file status is\nOpen and Enabled.\n1.Select option 03, and press Enter.\nThe demo program displays the following screen that describes what occurs in this part of the demo session.\n    **********************************************************************      \n    ****                                                              ****      \n    ****                  CA InterTest Demo Session                   ****      \n    ****                    No File Updating Option                   ****      \n    ****                                                              ****      \n    **********************************************************************      \n 449", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "60bb4d25338e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                                                                \n    The program reads a record and changes data in the record. Here is          \n    what will happen:                                                           \n                                                                                \n    1. CA InterTest halts the program at a request breakpoint.                 \n    2. You set the No File Updating option to prevent COBDEMO from              \n       updating the file.                                                      \n    3. When COBDEMO rewrites the file, the file is not updated.                \n    4. After the rewrite you use the FILE facility to confirm that the          \n       file has not been updated.                                              \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n    When this section of the demo completes, you will return to the             \n    Options Menu.                                                              \n                                                                                \n              Press ENTER to continue or CLEAR to terminate.\n2.Press Enter.\nInterTest for CICS displays a request breakpoint screen.\nHalt the Demo Program at a Request Breakpoint\nInterTest for CICS has halted the demo program prior to the first File Control REWRITE command as you specified\nduring the Demo Preliminaries section. The highlighted CALL instruction is part of the generated EXEC CICS REWRITE\ncommand.\n   CA InterTest for CICS  - PROTSYM FILE  SOURCE LISTING BREAKPOINT       \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ TASK-PROTCPF                    | PROTCPF                                \n _____ VSAM-AREA                       |          THIS IS NOT A NAME  PRIME THE \n _____ REC-LEN                         | +00681.                                \n---------+--------------------------------------------------------------------- \n   000916*     LENGTH(REC-LEN)                                                  \n   000917*     END-EXEC.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "60bb4d25338e-1", "text": "000917*     END-EXEC.                                                        \n  R    ==>     Call 'DFHEI1' using by content x'0606e0000700004000f0f0f5f2f4     \n _ 000919-    '404040' by reference TASK-PROTCPF by reference VSAM-AREA by      \n _ 000920     reference REC-LEN end-call.                                       \n   000921                                                                       \n   000922                                                                       \n U 000923 AFTER-REWRITE.                                                        \n _ 000924     MOVE 'THIS IS AFTER REWRITE' TO TASK-TEXT                         \n _ 000925           OF TASK-STRUCTURE.                                          \n _ 000926     GO TO SEND-MAP00.                                                 \n _ 000927 SET-UP-READ.                                                          \n _ 000928     MOVE 681 TO REC-LEN.                                              \n   000929*EXEC CICS HANDLE CONDITION NOTOPEN(OPENFIL) END-EXEC.                 \n _ 000930     Call 'DFHEI1' using by content x'0204800007130000000000000000    \n 450", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6a1e58b50837-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSetting request breakpoints lets you inspect the values of program variables and set options prior to all or specified CICS\ncommands and macros and other program calls.\n1.Scroll backward to look at the EXEC CICS REWRITE command.\n2.Press PF7.\nInterTest for CICS displays the following screen.\n   CA InterTest for CICS  - PROTSYM FILE  SOURCE LISTING BREAKPOINT       \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ TASK-PROTCPF                    | PROTCPF                                \n _____ VSAM-AREA                       |          THIS IS NOT A NAME  PRIME THE \n _____ REC-LEN                         | +00681.                                \n---------+--------------------------------------------------------------------- \n _ 000902         GO TO SEND-REWRITE-RETURN.                                    \n _ 000903 NUP-READ.                                                             \n _ 000904     PERFORM SET-UP-READ.                                              \n   000905*EXEC CICS READ DATASET(TASK-PROTCPF) INTO(VSAM-AREA) EQUAL            \n   000906*     LENGTH(REC-LEN) RIDFLD(REC-RBA) UPDATE                           \n   000907*     END-EXEC.                                                        \n _ 000908     Call 'DFHEI1' using by content x'0602f0000700008400f0f0f5f1f9     \n _ 000909-    '404040' by reference TASK-PROTCPF by reference VSAM-AREA by      \n _ 000910     reference REC-LEN by reference REC-RBA end-call.                  \n _ 000911 VSAM-REWRITE.                                                         \n _ 000912     MOVE 'THIS IS NOT A NAME  ' TO VSAM-NAME.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6a1e58b50837-1", "text": "000913*EXEC CICS REWRITE                                                     \n   000914*     DATASET(TASK-PROTCPF)                                            \n   000915*     FROM(VSAM-AREA)                                                  \n   000916*     LENGTH(REC-LEN)                                                               \nAccording to the EXEC CICS REWRITE command, the demo program updates the file PROTCPF (specified in the\nDATASET parameter of the EXEC CICS REWRITE command).\nNOTE\nTo view the contents of DATASET(TASK-PROTCPF) If the AutoKeep Display facility is not running, you can\nenter Search=TASK-PROTCPF to position the listing where it is defined, and add it to the Keep window (type\nK next to the line defining TASK-PROTCPF, position the cursor in the field name, and press Enter).\nHowever, you are going to set the No File Updating option to prevent the demo program from updating the file.\nTo do so, access the Special Options menu.\nSet the No File Updating Option\n1.As we did when we set and removed the MXR and MXS options, bring up the Program Monitoring screen by\nspecifying the SO option on the command line.\nInterTest for CICS displays the Special Options menu.\n2.Tab to the NUP field.\n3.Type an X, and press Enter.\nCA InterTest MONITORING COMMAND BUILDER - SPECIAL OPTIONS         22\n                                                                                \n      SET  one or more options to override the default monitoring rules in:     \n                                PROG=COBDEMO                                    \n 451", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d854c417f341-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                                                                \n           Enter X next to each option desired:                                 \n                                                                                \n                 Source Listing Breakpoint      (SLB) _                         \n                 No file updating               (NUP) x                         \n                 Reentrancy check               (RNT) _                         \n                                                                                \n           Follow monitoring (ON, name, NOPPT)  (FOL) ________                  \n           Number of times to be monitored      (MUS) _____                     \n           Limit total size of CICS storage     (MXS) _______                   \n           Limit total number of CICS requests  (MXR) _______                   \n                                                                                \n           Set local automatic breakpoint ('*', TERMID, .ANY, OFF)     ____     \n           Limit monitoring to your TERMINAL - '*' or TERMID:          ____     \n           User ID (or .ANY) who will execute the program:             ________\n                                                                                \n                                                                                \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7            8            9           10           11           12\nInterTest for CICS sets this option for the demo program.\n4.Press PF4 until you return to the Source Listing Breakpoint screen.\nBefore resuming program execution, look at the MOVE instruction just before the EXEC CICS REWRITE command.\nIt specifies that the data string THIS IS NOT A NAME be moved to the data field VSAM-NAME. If the demo program\nactually updates the file, that data string displays at the beginning of the first record in that file.\n5.Press PF5 to continue program execution.\nThe demo program resumes execution.\nUse FILE to Inspect the Record\nInterTest for CICS now halts the demo program at an unconditional breakpoint you set at procedure name AFTER-\nREWRITE in the Demo Preliminaries section.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d854c417f341-1", "text": "REWRITE in the Demo Preliminaries section.\n   CA InterTest for CICS  - PROTSYM FILE  UNCOND  BEFORE BREAKPOINT       \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ TASK-TEXT OF TASK-STRUCTURE     | .. THIS IS A MESSAGE    12/25/99       \n---------+--------------------------------------------------------------------- \n   000922                                                                       \n U 000923 AFTER-REWRITE.                                                        \n  U    ==>     MOVE 'THIS IS AFTER REWRITE' TO TASK-TEXT                         \n _ 000925           OF TASK-STRUCTURE.                                          \n _ 000926     GO TO SEND-MAP00.                                                 \n _ 000927 SET-UP-READ.                                                          \n _ 000928     MOVE 681 TO REC-LEN.                                              \n   000929*EXEC CICS HANDLE CONDITION NOTOPEN(OPENFIL) END-EXEC.                 \n _ 000930     Call 'DFHEI1' using by content x'0204800007130000000000000000     \n _ 000931-    '0000000000000000f0f0f5f3f5404040' end-call                       \n _ 000932      Service label                                                    \n _ 000933      Go to  OPENFIL depending on dfheigdi.                            \n 452", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "358389664650-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n   000934                                                                       \n _ 000935 OPENFIL.                                                              \n _ 000936     IF TASK-SWITCH3 = 'B' GO TO SEND-MAP00.                           \n _ 000937     MOVE 'B' TO TASK-SWITCH3.                                         \n _ 000938     MOVE 'PROTCPF NOT OPEN' TO ERRORO.                               \nBecause a procedure name does not have executable code, the unconditional breakpoint halts execution before the first\nverb -- in this case, the highlighted MOVE command.\nYou set the breakpoint at the paragraph immediately following the REWRITE command, so you can use the InterTest for\nCICS FILE facility to confirm that the demo program did not update the file.\n1.Press PF6.\nInterTest for CICS displays the Breakpoint Primary Option Menu.\n2.Select option 1 Main Menu.\nInterTest displays the Primary Option Menu.\n3.Select 4 Auxiliary storage.\nInterTest for CICS displays the Auxiliary Storage Menu.\n-------------  CA InterTest for CICS AUXILIARY STORAGE MENU  -------------\n OPTION  ===> 1                                                                 \n                                                                                \n    Select an auxiliary storage type, specifying optional criteria below.      \n                                                                                \n    1  Files              - Display/select files for access                     \n    2  DB2 database       - Invoke DB2 SQL interface facility                   \n    3  DL/I database      - Access DL/I database                                \n    4  TD queues          - Display/select transient data queues for access     \n    5  TS queues          - Display/select temporary storage queues for access  \n                                                                                \n    Type specific or generic file/queue name(s):                                \n       (Valid mask characters are  *  and/or  +)                                \n                                                                                \n    protcpf_ ________ ________ ________ ________ ________ ________ ________\n.                                                                               \n.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "358389664650-1", "text": ".                                                                               \n.\n4.Type 1 in the Option field and PROTCPF for the file name.\n5.Press Enter.\nInterTest for CICS displays the File Selection menu.\n6.Type S next to the file name and press Enter.\nInterTest for CICS displays the initial File Facility screen.\nDATATYPE= FC FILEID= PROTCPF  MODE=      LOG=ON  TODEST=         PASSWORD=     \nFUNC=      SUBFUNC=      RETMETH=        ARGTYP=     SRCHTYP=                   \nMESSAGE=                                                                        \n RETNRCID=                                                         CHGLEN=      \n    RCID=                                                                       \n    DATA=                                                          SIZE= 0000   \nFORMAT= D 00112233 44556677 8899AABB CCDDEEFF  *0123456789ABCDEF*              \nLOC 0000  ........ ........ ........ ........  ................               \n                                                                                \n                                                                               \n                                                                                \n 453", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a3f73617a2cc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                            CA InterTest for CICS                         \n                                                                                \n                   Copyright \u00a9 SOLVE:Access  CA. All rights reserved           \n                                                         \n                                                          \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n-------------------------------------------------------------------------------\n1 Help       2 Format C   3 End        4 BEGB       5            6 DataType DL \n7 Page bwd   8 Page fwd   9 Caps Off  10 Top       11 Bottom    12\n7.Press PF4.\nInterTest for CICS displays the first record in the PROTCPF file.\nDATATYPE= FC FILEID= PROTCPF  MODE=BROWSELOG=ON  TODEST=         PASSWORD=     \nFUNC= NEXT SUBFUNC=      RETMETH=        ARGTYP=     SRCHTYP=                   \nMESSAGE= CAIN0601 RECORD OBTAINED FOR VIEWING                                   \n RETNRCID=404040404040404040                                       CHGLEN=      \n    RCID=                                                                       \n    DATA=                                                          SIZE= 02A9   \nFORMAT= D 00112233 44556677 8899AABB CCDDEEFF  *0123456789ABCDEF*              \nLOC 0000  ........ ........ ........ ........  ................               \n  0000    40404040 40404040 4040405C 5C5C4040              ***    DSORG=VSKS    \n  0010    404040D9 C5C3D6D9 C440E3D6 40D7D9C9      RECORD TO PRI  RECFM=FB", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a3f73617a2cc-1", "text": "0020    D4C540E3 C8C540C3 C8C5C3D2 D7D6C9D5   ME THE CHECKPOIN  LRECL=02A9    \n  0030    E340C6C9 D3C54040 405C5C5C 5C404040   T FILE   ****     BLKSIZE=0000  \n  0040    40404040 40404040 F0F3F1F4 F0F0F0F0           03140000  KEYPOS=0000   \n  0050    00000000 00000000 00000000 00000000   ................ KEYLEN=09     \n  0060    00000000 00000000 00000000 00000000   ................ STRNO=02      \n  0070    00000000 00000000 00000000 00000000   ................               \n  0080    00000000 00000000 00000000 00000000   ................ READ          \n  0090    00000000 00000000 00000000 00000000   ................ ADD           \n  00A0    00000000 00000000 00000000 00000000   ................ UPDATE        \n  00B0    00000000 00000000 00000000 00000000   ................ BROWSE        \n  00C0    00000000 00000000 00000000 00000000   ................ DELETE        \n-------------------------------------------------------------------------------\n1 Help       2 Format C   3 End        4 ENDB       5 PREV       6 DataType DL", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a3f73617a2cc-2", "text": "7 Page bwd   8 Page fwd   9 Caps Off  10 Top       11 Bottom    12\nThe previous screen displays the contents of the first record in both hexadecimal and character formats.  The\ncharacter display indicates that the data string THIS IS NOT A NAME has not been moved to the beginning of this\nrecord\nNOTE\nSetting the No File Updating option prevented the demo program from updating this file, without affecting the\ndemo program source code.\nBefore returning to the demo program, we will discuss some capabilities of FILE.\nFILE Facility\nThe FILE facility lets you view, update, add, and delete records, and search for character strings. You can perform these\nfunctions at any time (for example, while your program is at a breakpoint). You can also use FILE when no program is\nexecuting to perform routine file maintenance.\n 454", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2112b46043b2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFILE, as shown in the previous screen, displays records in dump format, character format, vertical format, and structured\nformat. To display the record in different formats, press PF2. For structured format, which displays records or DL/I\nsegments on a field-by-field basis, you also must identify the program containing the structure.\nYou can use FILE with VSAM and BDAM files, DL/I and DB2 databases, temporary storage records, and transient data\nrecords.\nTake advantage of the FILE facility when testing your programs. Use FILE to change your test records or to create more\nrecords in the middle of a test session. You can also use FILE to make sure that your program successfully updates a file.\nNow we return to testing the demo program.\nDemo Program Completes Execution\n1.Press Clear.\nInterTest for CICS redisplays the File Selection screen.\n2.Press PF4 until you return to the Source Listing Breakpoint screen.\n3.Press PF5 to resume program execution.\nYou return to the demo program Options Menu.\nReview What Happened\nIn this part of the demo session, you took advantage of several InterTest for CICS features. You performed the following\nactions:\n\u2022Use a request breakpoint to halt the demo program prior to the first File Control REWRITE command.\nRequest breakpoints make it easy for you to halt your program at various points, such as before all HANDLE\nCONDITION commands or all Terminal Control commands. When your program is halted, you can inspect main\nstorage or auxiliary storage to detect errors and review program logic.\n\u2022Use the No File Updating option to prevent a program from updating a file.\nPreventing a program from updating a file means you can test a program repeatedly without having to recreate test", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2112b46043b2-1", "text": "Preventing a program from updating a file means you can test a program repeatedly without having to recreate test\ndata. Many programs can share test file because no program changes the file. And, a test program can even use a\nproduction file without corrupting it.\n\u2022Display a record in a file.\nDisplaying a record in a file lets you see whether your program is working correctly. The FILE facility also lets you add,\ndelete, and update records to meet your individual testing needs, and maintain files without special one-time programs.\nThis concludes Option 03 of the advanced demo session. Press Enter to continue with the demo session or press Clear to\nterminate the session.\nOption 04 How to Display Variable Length Data\nThis section of the demo session details how you can see the current length of variable length records.\nNOTE\nBefore you begin this section, complete the steps that are outlined in Demo Preliminaries  (unless you did so\nearlier in this session). The InterTest Demo Session Options Menu should be displayed.\n1.Select option 04, and press Enter.\nThe demo program displays a screen that describes what occurs in this part of the demo session.\n    **********************************************************************      \n    ****                                                              ****      \n    ****                  CA InterTest Demo Session                   ****      \n    ****                 Display Variable Length Data                 ****      \n    ****                                                              ****      \n 455", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8886184dc137-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    **********************************************************************      \n                                                                                \n    This feature lets you see the current length and contents of variable       \n    length data and records at any point in your program. Here is what          \n    will happen:                                                                \n                                                                                \n    1. CA InterTest halts COBDEMO at an unconditional breakpoint.              \n    2. You use the CORE facility to see the original record.                   \n    3. COBDEMO continues to execute and changes the length of the record.      \n    4. You use CORE again to see the updated record.                           \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n    When this section of the demo completes, you will return to the             \n    Options Menu.                                                              \n                                                                                \n              Press ENTER to continue or CLEAR to terminate.\n2.Press Enter.\nInterTest for CICS halts the execution of the demo program at an unconditional breakpoint set during the Demo\nPreliminaries section.\n   CA InterTest for CICS   - PROTSYM FILE  UNCOND  BEFORE BREAKPOINT       \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ VAR-REC-LEN                     | +00100.                                \n---------+--------------------------------------------------------------------- \n   000687**** THIS SECTION OF THE DEMO SHOWS HOW YOU ****                       \n   000688**** CAN LOOK AT VARIABLE LENGTH DATA **********                       \n  U    ==>     MOVE +48 TO VAR-REC-LEN.                                          \n _ 000690     GO TO SEND-MAP00.                                                 \n _ 000691 REPLACE-FILE.                                                         \n _ 000692     IF  TASK-SWITCH3 EQUAL SPACE                                      \n _ 000693         MOVE 'A' TO TASK-SWITCH3", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8886184dc137-1", "text": "_ 000693         MOVE 'A' TO TASK-SWITCH3                                      \n _ 000694         MOVE 'DMAP04' TO MAPNAME                                      \n _ 000695         GO TO SEND-REWRITE-RETURN.                                    \n _ 000696     IF  TASK-SWITCH3 EQUAL 'A'                                        \n _ 000697         GO TO READ-DATASET                                            \n _ 000698     ELSE                                                              \n _ 000699         GO TO SEND-MAP00.                                             \n _ 000700 READ-DATASET.                                                         \n   000701*EXEC CICS HANDLE CONDITION                                            \n   000702*          DSIDERR                                                     \n   000703*          NOTOPEN(NOT-OPEN)                                          \nThe unconditional breakpoint was set at procedure name DO-READ-VAR. Because a procedure name does not have\nexecutable code, the unconditional breakpoint halts execution before the first verb in the paragraph. In this case, the\nfirst verb is the highlighted MOVE command below the comment lines. Halting execution at this point in the program\nlets you see the contents of a variable length record before the demo program changes its length.\n 456", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "854d52b6c417-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nExecution of the highlighted MOVE statement changes the length of the 01-level record VARIABLE-LENGTH-\nRECORD. Its definition tells us why.\n3.Type L VARIABLE-LENGTH-RECORD into the command line, and press Enter.\n  CA InterTest for CICS  - PROTSYM FILE  UNCOND  BEFORE BREAKPOINT       \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ VAR-REC-LEN                     | +00100.                                \n---------+--------------------------------------------------------------------- \n   000687**** THIS SECTION OF THE DEMO SHOWS HOW YOU ****                       \n   000688**** CAN LOOK AT VARIABLE LENGTH DATA **********                       \n U    ==>     MOVE +48 TO VAR-REC-LEN.                                          \n _ 000690     GO TO SEND-MAP00.                                                 \n _ 000691 REPLACE-FILE. \n.\n.\n.                                      \nInterTest for CICS finds the definition of VARIABLE-LENGTH-RECORD in Working-Storage and displays that portion\nof the compile listing.\n  CA InterTest for CICS - PROTSYM FILE  UNCOND  BEFORE BREAKPOINT       \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ VAR-REC-LEN                     | +00100.                                \n---------+--------------------------------------------------------------------- \n _ 000097                              OCCURS 5 TIMES                           \n _ 000098                              INDEXED BY DISTRICT-X.                   \n _ 000099 01  VARIABLE-LENGTH-RECORD.                                           \n _ 000100     03  VAR-REC-LEN          PIC S9(4) COMP.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "854d52b6c417-1", "text": "_ 000101     03  VAR-LENGTH-DATA      PIC X                                    \n _ 000102                              OCCURS 1 TO 100 TIMES                    \n _ 000103                              DEPENDING ON VAR-REC-LEN.                \n _ 000104     COPY DFHAID.                                                     \nThe definition of VARIABLE-LENGTH-RECORD shows two fields: VAR-REC-LEN and VAR-LENGTH-DATA. Note that\nthe length of VAR-LENGTH-DATA depends on the value of VAR-REC-LEN.\nNow we look at the current contents of VARIABLE-LENGTH-RECORD. You can do this directly from the Working-\nStorage listing.\n4.Tab to the line containing VARIABLE-LENGTH-RECORD.\n5.Type D (for display), and press Enter.\n  CA InterTest for CICS  - PROTSYM FILE  UNCOND  BEFORE BREAKPOINT       \nCOMMAND ===>                                                                  \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01\n                                        Search=                               \n------------------------------------------------------------------------------\n _____ VAR-REC-LEN                     | +00100.                              \n---------+--------------------------------------------------------------------\n _ 000097                              OCCURS 5 TIMES                         \n 457", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4dd121ac3fd4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _ 000098                              INDEXED BY DISTRICT-X.                 \n d 000099 01  VARIABLE-LENGTH-RECORD.                                         \n _ 000100     03  VAR-REC-LEN          PIC S9(4) COMP.                        \n _ 000101     03  VAR-LENGTH-DATA      PIC X                                  \n _ 000102                              OCCURS 1 TO 100 TIMES                  \n _ 000103                              DEPENDING ON VAR-REC-LEN.              \n _ 000104     COPY DFHAID. \n.\n.\n.               \nInterTest for CICS displays the contents of VARIABLE-LENGTH-RECORD in a structured format.\n        CA InterTest for CICS  - MAIN STORAGE UTILITY - Termid = U031     \n                                                                                \nStarting at Address =2080A6F0         Structure Display Format                  \n01 VARIABLE-LENGTH-RECORD           |                            |              \n 02 VAR-REC-LEN                     | +00100.                    |              \n 02 VAR-LENGTH-DATA                 | +                          |              \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n ------------------------------------------------------------------------------ \n PF1 Help       2            3 End        4 Return     5            6 Dump      \n PF7 Backward   8 Forward    9 Caps Off  10           11 Redisplay 12 Structure \n CORE='000099:VARIABLE-LENGTH-RECORD'                                           \n CAIN0467 AT LAST ENTRY IN STRUCTURE                                           \nAs you can see, the structured format gives only one occurrence of each field; it does not tell you the record length. To\nsee the length of a 01-level record, switch from the structured format to the dump format.\n6.Press Enter.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4dd121ac3fd4-1", "text": "6.Press Enter.\nInterTest for CICS displays the contents of VARIABLE-LENGTH-RECORD in a hexadecimal dump format.\n       CA InterTest for CICS  - MAIN STORAGE UTILITY - Termid = U032     \nOffset                                                            Address  Task\n+   0  00644E4E 4E4E4E4E 4E4E4E4E 4E4E4E4E  * ..++++++++++++++ * 2030A6F0   184\n+  10  4E4E4E4E 4E4E4E4E 4E4E4E4E 4E4E4E4E  * ++++++++++++++++ * 2030A700      \n+  20  4E4E4E4E 4E4E4E4E 4E4E4E4E 4E4E4E4E  * ++++++++++++++++ * 2030A710  Page\n+  30  4E4E4E4E 4E4E4E4E 4E4E4E4E 4E4E4E4E  * ++++++++++++++++ * 2030A720  +000\n+  40  4E4E4E4E 4E4E4E4E 4E4E4E4E 4E4E4E4E  * ++++++++++++++++ * 2030A730      \n+  50  4E4E4E4E 4E4E4E4E 4E4E4E4E 4E4E4E4E  * ++++++++++++++++ * 2030A740", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4dd121ac3fd4-2", "text": "+  60  4E4E4E4E 4E4E                        * ++++++           * 2030A750      \n                                                                               \n                                                                               \n                                                                               \n ------------------------------------------------------------------------------\n PF1 Help       2            3 End        4 Return     5            6 Dump     \n PF7 Backward   8 Forward    9 Caps Off  10           11           12 SDF      \n 458", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "950f876d505d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n CORE='000099:VARIABLE-LENGTH-RECORD'                                 \nThe dump format shows all occurrences of lower-level fields and thus the 01-level record length. This display shows\nthat the record length is 64 hexadecimal (or 100 decimal) bytes. The first two bytes are the field VAR-REC-LEN, and\nthe rest of the bytes are repeated occurrences of the field VAR-LENGTH-DATA.\nNow return to the breakpoint to continue execution\n7.Press Clear to return to Source Listing Breakpoint screen.\nNow you will execute one verb and stop. This lets you see the contents of the record after the demo program changes\nits length.\n8.Press PF10.\nThe demo program executes one verb (the MOVE statement, which moves 48 to VAR-REC-LEN). Then InterTest for\nCICS immediately stops the program and displays another breakpoint.\nNow the program is halted at the next statement, as shown next.\n   CA InterTest for CICS  - PROTSYM FILE   STEP  BEFORE  BREAKPOINT       \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n-------------------------------------------------------------------------------\n   000688**** CAN LOOK AT VARIABLE LENGTH DATA **********                       \n _ 000689     MOVE +48 TO VAR-REC-LEN.                                          \n _    ==>     GO TO SEND-MAP00.                                                 \n _ 000691 REPLACE-FILE.                                                         \n _ 000692     IF  TASK-SWITCH3 EQUAL SPACE  \n.\n.\n9.To display the contents of VARIABLE-LENGTH-RECORD from the Source Listing screen, find a line that contains the\nfield (such as the definition), type D, and press Enter. You this did the first time. Another method is to use a CORE\nmenu:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "950f876d505d-1", "text": "menu:\n10.Press PF6.\nInterTest for CICS displays the Breakpoint Primary Option Menu.\n11.Select option  1 Main Menu .\nInterTest for CICS displays the Primary Option Menu.\n12.From the Primary Option Menu, select option 3 Main Storage.\nInterTest for CICS displays the Main Storage Menu.\n13.Select option 3 Breakpoint areas.\nInterTest for CICS displays a CORE menu for breakpoint-related data.\nCA InterTest CORE COMMAND BUILDER - BREAKPOINT-RELATED AREAS  (CORE=Bkpt)  \n                                                                                \n Specify area to be displayed, changed or moved:              Task number: 00094\n                                                                                \n   COBOL name: variable-length-record________                                   \n                                                                                \n   Special element: ________   (Enter highlighted keyword)                      \n     SSCR Saved screen image   BMSG Breakpoint message       CMAR Commarea      \n     FCAR Facility cntl area   EIB  Exec interface block     TUAR TCT user area \n     BLLS COBOL BLL cells      CWK  COBOL working storage    TGT  COBOL TGT     \n     LCL  COBOL local storage  DSA  COBOL DSA\n                                                                                \n SCAN VALUE: _________________________________________           DATA  FORMATS  \n SCAN RANGE: ______             B to scan backwards: _         -----------------\n 459", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a4fec390aad9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                                               | P' ' = Packed |\n To VERIFY and/or CHANGE Data:                                 | X' ' = Hex    |\n Existing data: ______________________________________         | C' ' = Char   |\n      New data: ______________________________________         -----------------\n                                                                                \n MOVE From ______________________________    To   ______________________________\n                                                                                \n                                                                                \nPF1 Help       2            3 End        4 Return     5            6           \nPF7            8            9 Complex   10           11           12\n14.Type VARIABLE-LENGTH-RECORD in the COBOL name field, and press Enter.\nInterTest for CICS displays the modified contents of VARIABLE-LENGTH- RECORD in structured format.\n     CA InterTest for CICS - MAIN STORAGE UTILITY - Termid = U031      \n                                                                                \nStarting at Address =2080A6F0         Structure Display Format                  \n01 VARIABLE-LENGTH-RECORD           |                            |              \n 02 VAR-REC-LEN                     | +00048.                    |              \n 02 VAR-LENGTH-DATA                 | +                          |              \n                                                                    \n.\n.\n.\n \n                                                                                \n ------------------------------------------------------------------------------ \n PF1 Help       2            3 End        4 Return     5            6 Dump      \n PF7 Backward   8 Forward    9 Caps Off  10           11 Redisplay 12 Structure \n CORE(00050)='VARIABLE-LENGTH-RECORD'                                           \n CAIN0467 AT LAST ENTRY IN STRUCTURE\n15.Press Enter to display the record in dump format.\nThe record is now only 30 hexadecimal (or 48 decimal) bytes long because the variable field is reduced from a length\nof decimal 100 to decimal 48 when the program moved 48 to VAR-REC-LEN.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a4fec390aad9-1", "text": "16.Press Clear.\nInterTest for CICS displays the Main Storage Menu.\n17.Press PF4 until the Source Listing Breakpoint screen displays.\n18.Press PF5.\nThe demo program resumes execution and displays the Options Menu.\nReview What Happened\nIn this part of the demo session, you displayed the length and contents of a variable length record.\n\u2022You used an unconditional breakpoint to halt program execution before the demo program changed the length of a\nvariable length record.\n\u2022You inspected the contents of the record.\n\u2022You executed one verb, halted program execution, and again inspected the contents of the record. This enabled you to\nconfirm the new length.\nThis concludes Option 04 of the advanced demo session. Press Enter to continue with the demo session or press Clear to\nterminate the session.\n 460", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6e633cb013b8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nOption 05 How to Work with Indexed Table Items\nThis section of the demo session shows you a fast and easy way to inspect and modify the contents of indexed data\nitems.\nNOTE\nBefore you begin this section, complete the steps that are outlined in Demo Preliminaries (unless you did so\nearlier in this session). The InterTest Demo Session Options Menu should be displayed.\n1.Select option 05, and press Enter.\nThe demo program displays a screen that describes what occurs in this part of the demo session.\n    **********************************************************************      \n    ****                                                              ****      \n    ****                  CA InterTest Demo Session                   ****      \n    ****                    Work with Table Items                     ****      \n    ****                                                              ****      \n    **********************************************************************      \n                                                                                \n    CA InterTest makes it easy to display values for indexed, subscripted       \n    and qualified data areas. A table defined in  WORKING-STORAGE has not       \n    been fully initialized. Here is what will happen:                           \n                                                                                \n    1. CA InterTest halts the program at an automatic breakpoint when it        \n       detects an uninitialized table item.                                    \n    2. You display the table item and correct the contents on the CORE          \n       display. You also display the contents of the indexes to                \n       determine which table entry caused the error.                           \n    3. COBDEMO successfully completes execution.                               \n                                                                                \n                                                                                \n                                                                                \n    When this section of the demo continues, you will return to the             \n    Options Menu.                                                              \n                                  \n                                              \n              Press ENTER to continue or CLEAR to terminate.\n2.Press Enter.\nThe demo program resumes execution.\nThe next screen that is displayed is an automatic breakpoint screen. InterTest for CICS halted the demo program\nbecause it detected a data exception in the highlighted ADD instruction.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6e633cb013b8-1", "text": "because it detected a data exception in the highlighted ADD instruction.\n   CA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT       \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ DISTRICT-POP(STATE-X COUNTY-X D | ?000.                                  \n _____ STATE-X                         | ....                                   \n _____ COUNTY-X                        | ....                                   \n _____ DISTRICT-X                      | ....                                   \n---------+--------------------------------------------------------------------- \n _ 000655     SET COUNTY-X TO 3.                                                \n _ 000656     SET DISTRICT-X TO 5.                                              \n 461", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "69bfe7096f50-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  A    ==>     ADD +1 TO DISTRICT-POP (STATE-X, COUNTY-X, DISTRICT-X).                 ==>                \n                                                              ==> ASRA ABEND (0C7) detected and prevented.\n Caused by invalid decimal           ==> arithmetic data format.                                       \n               ==>                                                                              ==>     \n Press PF1 for a detailed description.                             \n     ==>                                                                        \n _ 000658     MOVE SPACES TO TASK-TEXT OF TASK-STRUCTURE.                       \n _ 000659     MOVE ALL '*' TO TASK-TEXT OF TASK-STRUCTURE-2.                    \n _ 000660     GO TO SEND-MAP00.                                                 \n _ 000661 INITIALIZE-TABLE.                                                     \n _ 000662     MOVE SUB-1 TO STATE-NUMBER (SUB-1),                    \nIf you recall, this error is the same type of error detected and corrected in the basic demo session. To continue\nexecution, find the data item causing the ASRA and dynamically modify it.\nLooking at the highlighted breakpoint statement, you might suspect the variable is at fault; it probably was not\ninitialized correctly. The variable in this case is an indexed table entry.\nDisplay an Indexed Table Entry\nYou can quickly inspect and correct the value of the field DISTRICT-POP (STATE-X, COUNTY-X, DISTRICT-X) directly\nfrom this screen in the AutoKeep display at the top, or by entering D and positioning the cursor under the field name within\nthe code.\n1.Overtype the A to the left of the highlighted statement with D (for display).\n2.Place the cursor under any letter in DISTRICT-POP, and press Enter.\n  CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT       \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "69bfe7096f50-1", "text": "Program= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ DISTRICT-POP(STATE-X COUNTY-X D | ?000.                                  \n _____ STATE-X                         | ....                                   \n _____ COUNTY-X                        | ....                                   \n _____ DISTRICT-X                      | ....                                   \n---------+--------------------------------------------------------------------- \n _ 000655     SET COUNTY-X TO 3.                                                \n _ 000656     SET DISTRICT-X TO 5.                                              \n  d    ==>     ADD +1 TO DISTRICT-POP (STATE-X, COUNTY-X, DISTRICT-X).                 ==>                \n                                                              ==> ASRA ABEND (0C7) detected and prevented.\n Caused by invalid decimal           ==> arithmetic data format.                                       \n               ==>                                                                              ==>     \n Press PF1 for a detailed description.                             \n     ==>                                                                        \n _ 000658     MOVE SPACES TO TASK-TEXT OF TASK-STRUCTURE.                       \n _ 000659     MOVE ALL '*' TO TASK-TEXT OF TASK-STRUCTURE-2.                    \n _ 000660     GO TO SEND-MAP00.                                                 \n _ 000661 INITIALIZE-TABLE.                                                     \n _ 000662     MOVE SUB-1 TO STATE-NUMBER (SUB-1),              \nInterTest for CICS displays the current value of DISTRICT-POP in a\nstructured format.\n 462", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "43367bd079f9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe error message on the bottom line in the following screen tells us this field does not contain a valid value,\naccording to the definition. This error triggered the automatic breakpoint.\nCorrect an Uninitialized Table Item Dynamically\nTo dynamically correct this error, modify main storage so the field contains a packed decimal zero. This is the hexadecimal\nvalue: 000C. Do this by overtyping the value displayed.\n1.Tab once to go to the hexadecimal display area.\n2.Move the cursor to the final 0, overtype it with C, and press Enter.\n      CA InterTest for CICS - MAIN STORAGE UTILITY - Termid = U031      \n                                                                                \nStarting at Address =2080A626         Structure Display Format                  \n   04 DISTRICT-POP                  | ?000.                      |  \n.\n.\n.            \n                                                                                \n                                                                                \n ------------------------------------------------------------------------------ \n PF1 Help       2            3 End        4 Return     5            6 Dump      \n PF7 Backward   8 Forward    9 Caps Off  10           11 Redisplay 12 Structure \n CORE='DISTRICT-POP(STATE-X, COUNTY-X, DISTRICT-X)'                             \n CAIN0452 FIELD DOES NOT CONTAIN A VALID PACKED DECIMAL (COMP-3) VALUE         \nInterTest for CICS dynamically modifies the value in main storage for DISTRICT-POP (STATE-X, COUNTY-X,\nDISTRICT-X), and displays the new value.\nThe previous error message no longer displays. You could now resume execution from the breakpoint because you\ndynamically corrected the error.\nBefore you do, first look at the CORE command displayed above the message line:\n CORE='DISTRICT-POP(STATE-X, COUNTY-X, DISTRICT-X)'", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "43367bd079f9-1", "text": "CORE='DISTRICT-POP(STATE-X, COUNTY-X, DISTRICT-X)' \nInterTest for CICS formatted this command when you used the d and the cursor to display the table item. Using the\nd and the cursor meant you did not have to type the complex name. Whenever you can, let InterTest for CICS do the\nwork for you.\nDisplay Values of Indexes\nAlthough you corrected the error, you do not know exactly which table entry was at fault. To identify the table entry, you\nmust know the current contents of STATE-X, COUNTY-X and DISTRICT-X and their occurrences in the table.\n1.Return to the breakpoint display to request a display of STATE-X.\n2.Press PF3.\nInterTest for CICS displays the previous Source Listing Breakpoint screen.\nThe program code directly above the breakpoint line shows the values of COUNTY-X and DISTRICT-X. You also\ncould page backward to see the value of STATE-X. However, how would you find the values of STATE-X, COUNTY-X\nand DISTRICT-X if this code was not there? First, look at how to display the contents of the variable STATE-X.\n3.Tab to the AutoKeep line containing STATE-X.\n4.Type D.\n5.Press Enter.\n   CA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT       \nCOMMAND ===>                                                                    Program= COBDEMO  Option #\n       Stmt #                             Margin= 01  \n 463", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fb8b4dd46916-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ DISTRICT-POP(STATE-X COUNTY-X D | ?000.                                  \n d____ STATE-X                         | ....                                   \n _____ COUNTY-X                        | ....                                   \n _____ DISTRICT-X                      | ....                                   \n---------+--------------------------------------------------------------------- \n _ 000655     SET COUNTY-X TO 3. \n.\n.\n.\nInterTest for CICS displays the current contents of STATE-X in dump format, as illustrated in the following figure.\nInterTest for CICS displays the values of indexes in dump format rather than structured format because indexes are\nnot defined in a structure.\n       CA InterTest for CICS - MAIN STORAGE UTILITY - Termid = U032      \nOffset                                                            Address  Task \n+   0  00000000                             * ....             * 20309FC0   189 \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n ------------------------------------------------------------------------------ \n PF1 Help       2            3 End        4 Return     5            6 Dump      \n PF7 Backward   8 Forward    9 Caps Off  10           11           12 Structure \n CORE='STATE-X'                                                                 \n CAIN4727 Data item is an index set to occurrence 1                            \nSTATE-X has a value of hexadecimal zero.\nThe command InterTest for CICS generated is simply CORE='STATE-X', as shown on the bottom of the previous\nfigure. This confirms that the dump display is showing you the main storage contents of STATE-X, which is what you\nwanted.\nThe last line on the screen indicates that STATE-X is set to occurrence 1.\nTo see the contents of the remaining index variables, COUNTY-X and DISTRICT-X, you could return to the breakpoint", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fb8b4dd46916-1", "text": "display and repeat the request using the d and the cursor method. However, a quicker method is to modify the CORE\ncommand on the bottom of the screen. Just change the STATE-X in the CORE command to COUNTY-X.\n6.Move the cursor to the CORE command.\n7.Overtype 'STATE-X' with 'COUNTY-X', and press Enter.\nInterTest for CICS displays the contents of COUNTY-X in dump format and informs you that it is set to occurrence 3,\nas shown in the following screen. (Note the modified command.)\n       CA InterTest for CICS - MAIN STORAGE UTILITY - Termid = U032     \nOffset                                                            Address  Task\n+   0  0000001A                             * ....             * 20309FC4   189\n                                                                               \n                                                                               \n                                                                               \n ------------------------------------------------------------------------------\n PF1 Help       2            3 End        4 Return     5            6 Dump     \n PF7 Backward   8 Forward    9 Caps Off  10           11           12 Structure\n CORE='COUNTY-X'                                                               \n CAIN4727 Data item is an index set to occurrence 3                           \n8.To see the value of DISTRICT-X, modify the CORE command to specify DISTRICT-X instead of COUNTY-X.\n 464", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6a1f109aeeef-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n9.Move the cursor to the CORE command.\n10.Overtype 'COUNTY-X' with 'DISTRICT-X', and press Enter.\nInterTest for CICS displays the contents of DISTRICT-X and informs you that it is set to occurrence 5. (Note the\nmodified command.)\n       CA InterTest for CICS - MAIN STORAGE UTILITY - Termid = U032      \nOffset                                                            Address  Task \n+   0  00000008                             * ....             * 20309FC8   189 \n                                                                                \n                                                                                \n \n                                                                                \n ------------------------------------------------------------------------------ \n PF1 Help       2            3 End        4 Return     5            6 Dump      \n PF7 Backward   8 Forward    9 Caps Off  10           11           12 Structure \n CORE='DISTRICT-X'                                                              \n CAIN4727 Data item is an index set to occurrence 5                            \nBy displaying the contents of STATE-X, COUNTY-X, and DISTRICT-X, you determine that DISTRICT-POP (1, 3, 5) is\nthe exact position in the table of the invalid table item.\nNow return to the breakpoint display.\n11.Press Clear.\nThe Source Listing Breakpoint screen redisplays.\n12.Press PF5.\nThe demo program resumes execution and returns you to the Options Menu.\nReview What Happened\nIn this part of the demo session the following occurred:\n\u2022The demo program was halted at an automatic breakpoint because a table item contained invalid data.\n\u2022You corrected the invalid data. However, you did not know the exact position in the table of the invalid table item.\n\u2022You used CORE to display the contents of the indexes and their occurrences. This enabled you to pinpoint the position\nof the invalid table item.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6a1f109aeeef-1", "text": "of the invalid table item.\nWith InterTest for CICS, it is easy to debug problems involving indexed, qualified, or subscripted data items because you\ncan display and modify their contents just as you would any other COBOL data item.\nThis concludes Option 05 of the advanced demo session. Press Enter to continue with the demo session or press Clear to\nterminate the session.\nOption 06 How to Detect a Storage Violation\nThis section of the test session details how InterTest for CICS detects and prevents a storage violation and lets you\ncontinue testing.\nNOTE\nTo perform this section, you should have completed the steps that are outlined in Demo Preliminaries . The\nInterTest Demo Session Options Menu should be displayed.\n1.Select option 06, and press Enter.\nThe demo program displays a screen that describes what occurs in this part of the test session.\n    **********************************************************************      \n    ****                                                              ****      \n    ****                  CA InterTest Demo Session                   ****      \n 465", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6c98aa4453f3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    ****               Storage Violation Detection Option             ****      \n    ****                                                              ****      \n    **********************************************************************      \n                                                                                \n The program attempts to move data from one field to another. However, because \n the program has relinquished storage for the receiving field, a storage        \n violation would occur. Instead, here is what will happen:                     \n                                                                                \n 1. CA InterTest halts the program at an automatic breakpoint.                \n 2. You inspect the FREEMAIN instruction which released the storage for        \n     the field.                                                                \n 3. You return to the breakpoint display. Then you go around the problem,     \n     continuing program execution from the statement following the one that     \n     triggered the breakpoint.                                                 \n \n                                                                                \n When this section of the demo completes, you will return to the Options Menu  \n                                                                                \n                                                                                \n                                                                                \n              Press ENTER to continue or CLEAR to terminate.\n2.Press Enter.\nInterTest for CICS halts the demo program at an automatic breakpoint.\nPrevent a Storage Violation\nDisplayed next is a breakpoint screen. InterTest for CICS halted the demo program at an automatic breakpoint. InterTest\nfor CICS prevented the storage violation that would have resulted if the highlighted MOVE statement had been executed.\nInterTest for CICS also inserted an A next to the statement to indicate an automatic breakpoint.\n   CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT       \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ NEW-DATA                        | 00000000 00000000 00000000 00000000    \n _____ STG-AREA1                       | 00000000 00000000 00000000 00000000", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6c98aa4453f3-1", "text": "---------+--------------------------------------------------------------------- \n   000968**** NOW MOVE NEW DATA INTO ACQUIRED AREA                              \n   000969*                                                                      \n  A    ==>     MOVE NEW-DATA TO STG-AREA1.                                             ==>                 \n                                                             ==> an attempt to change an area that does not\n belong to this task.              ==> Possible system damage has been prevented.                          \n         ==>                                                                              ==>      Press PF1\n for a detailed description.                             \n     ==>                                                                        \n _ 000971     GO TO SEND-MAP00.                                                 \n _ 000972 WHICH-ONE.                                                    \n 466", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "28280d424c98-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe ability of InterTest for CICS to prevent storage violations is one of the most important reasons to monitor programs.\nStorage violations are notorious CICS errors that can do the following:.\n1.Bring down your CICS system.\n2.Cause a program to produce erroneous data.\n3.Cause one program to corrupt the data of another program. In this case, tracking down the problem without InterTest\nfor CICS is almost impossible because the error is not in the affected program.\nBy stopping the program before the storage violation occurs, InterTest for CICS protects your system and helps you to\ndiagnose and correct the error.\nIn this example, the statement that would have caused the storage violation is: MOVE NEW-DATA TO STG-AREA1. This\nstatement moves data from NEW-DATA to STG-AREA1. Perhaps the program does not own the area of storage that is\ndefined as STG-AREA1, so the program cannot move data to that field.\nInspect the FREEMAN Statement\nWe will page back to find out what caused the error.\n1.Press PF7.\nInterTest for CICS displays the following screen.\n  CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT       \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ NEW-DATA                        | .............V......                   \n _____ STG-AREA1                       | ....................                   \n---------+--------------------------------------------------------------------- \n   000968**** NOW MOVE NEW DATA INTO ACQUIRED AREA                              \n   000969*                                                                      \n A    ==>     MOVE NEW-DATA TO STG-AREA1.                                       \n     ==>", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "28280d424c98-1", "text": "A    ==>     MOVE NEW-DATA TO STG-AREA1.                                       \n     ==>                                                                        \n     ==> an attempt to change an area that does not belong to this task.        \n     ==> Possible system damage has been prevented.                             \n     ==>                                                                        \n     ==>      Press PF1 for a detailed description.                             \n     ==>                                                                        \n _ 000971     GO TO SEND-MAP00.                                                 \n _ 000972 WHICH-ONE.                                                            \n _ 000973     GO TO REPLACE-FILE                                                \n _ 000974           MXR-OPTION                                                  \n _ 000975           READ-FOR-UPDATE                                             \n _ 000976           SET-VAR-REC                                                 \n _ 000977           PROCESS-TABLE              \nLook at the FREEMAIN statement that releases the storage for STG-AREA. Now it is clear why the storage violation\noccurred. The demo program released the storage for STG-AREA. After releasing the storage, the program tried to\nmove data to STG-AREA1, which is part of STG-AREA.\nTo correct the problem, you would have to remove the FREEMAIN statement or change its location, and then\nrecompile the program. However, one of the benefits of InterTest for CICS is that you do not have to correct a problem\nwhen you discover it. Instead, you can go around the problem and continue testing the program.\nNow we will redisplay the breakpoint.\n2.Press Clear.\n 467", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4e862e140be3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterTest for CICS redisplays the automatic breakpoint.\nResume Program Execution\nWe will continue program execution at the first instruction after the statement that triggered the breakpoint. In the COBOL\ndemo, this is GO TO SEND-MAP00. In the COBOL/II and COBOL/370 demos, this is a GOBACK statement.\n1.Tab to the first statement following the breakpoint.\n2.Type G (go).\n3.Press Enter to continue program execution.\n CA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT       \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ NEW-DATA                        | .............V......                   \n _____ STG-AREA1                       | ....................                   \n---------+--------------------------------------------------------------------- \n   000968**** NOW MOVE NEW DATA INTO ACQUIRED AREA                              \n   000969*                                                                      \n A    ==>     MOVE NEW-DATA TO STG-AREA1.                                       \n     ==>                                                                        \n     ==> an attempt to change an area that does not belong to this task.        \n     ==> Possible system damage has been prevented.                             \n     ==>                                                                        \n     ==>      Press PF1 for a detailed description.                             \n     ==>                                                                        \n g 000971     GO TO SEND-MAP00.                                                 \n _ 000972 WHICH-ONE.                                                            \n _ 000973     GO TO REPLACE-FILE                                                \n _ 000974           MXR-OPTION                                                  \n _ 000975           READ-FOR-UPDATE                                             \n _ 000976           SET-VAR-REC                                                 \n _ 000977           PROCESS-TABLE                                        \nInterTest for CICS resumes program execution. The demo program successfully completes execution and displays", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4e862e140be3-1", "text": "InterTest for CICS resumes program execution. The demo program successfully completes execution and displays\nthe Options Menu. By going around the storage violation, you have allowed the demo program to continue executing\ndespite the problem InterTest for CICS detected.\nReview What Happened\nIn this part of the demo session, the following events occurred:\n\u2022InterTest for CICS detected and prevented a storage violation and halted the demo program at an automatic\nbreakpoint.\n\u2022The ability of InterTest for CICS to prevent storage violations protects your CICS system and prevents one program\nfrom corrupting another.\n\u2022By inspecting the statement that would have caused the storage violation, you saw which field was in error. By\ninspecting the FREEMAIN statement, you were able to determine why the program did not own the storage area.\n\u2022Using InterTest for CICS to examine the source code surrounding an error makes it easy to learn what caused the\nproblem.\n\u2022You went around the problem and continued program execution.\n\u2022The ability to go around a problem lets you continue testing and correct many errors in a single test session.\n 468", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c74235b40455-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThis concludes Option 06 of the advanced demo session. Press Enter to continue with the demo session or press Clear to\nterminate the session.\nOption 07 How to Test a Composite Module\nThis option details how you can use InterTest for CICS to test and debug a composite module. Composite support is\nan InterTest for CICS feature designed to help programmers who are responsible for testing and debugging called\nsubroutines. Skip this option if you are not responsible for these subroutines.\nTo perform this option, you should have set monitoring for the composite module as described in Composite Support\npart of Demo Preliminaries.\nIn this section you will test three programs:\n\u2022The main program, COBDEML, the composite module is invoked by the same DEMC transaction as the demo\nprogram COBDEMO.\n\u2022Two subroutines ASBIN25 and CSBIN25 that are part of composite module COBDEML. However, composite modules\nat your site could have many called subroutines. You must tell InterTest for CICS only about the ones that you want to\ntest or debug.\nFollow these steps:\n1.In the InterTest Demo Session Options Menu, select option 07, and press Enter.\nThe following screen appears:\n    **********************************************************************      \n    ****                                                              ****      \n    ****                  CA InterTest Demo Session                   ****      \n    ****                      Composite Support                       ****      \n    ****                                                              ****      \n    **********************************************************************      \n                                                                                \n Program COBDEML calls two subroutines:  ASBIN25 and CSBIN25.                  \n                                                                                \n 1. CA InterTest halts the program at an automatic breakpoint caused by an     \n     ASRA. Without composite support, you will see only that you are stopped    \n     at the CALL to ASBIN25.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c74235b40455-1", "text": "at the CALL to ASBIN25.                                                   \n 2. You abend the task, and then set composite support for COBDEML.           \n 3. Type in transaction id DEMC again. This time you will see the actual      \n     instruction causing the ASRA within the subroutine.                       \n 4. You correct the problem that caused the automatic breakpoint.             \n 5. You then set an unconditional breakpoint in CSBIN25. When you resume      \n     execution, the program is halted at that breakpoint.                      \n 6. You remove the breakpoint and the program completes execution.            \n                                                                            \n When this section of the demo completes, you will return to the Options Menu. \n                                                                              \nPress ENTER to continue or CLEAR to terminate.             \n2.Press Enter.\nThe composite module halts at an automatic breakpoint at statement CALL ASBIN25.\nNOTE\nIf a screen other than the following screen displays, someone at your site has already set composite support\nfor the composite module. In this case, skip to Re-execute the Demo Program .\n 469", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0ea1c184c12a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCA InterTest for CICS - PROTSYM FILE SOURCE LISTING BREAKPOINT           \nCOMMAND ===>                                                                   \nProgram= COBDEML  Option #       Stmt #                             Margin= 01  \n                                        Search=                                \n---------+---------------------------------------------------------------------\n   00154                                                                        \n _ 00155 CALL-ASSEMBLER.                                                       \n A   ==>     CALL 'ASBIN25' USING DFHEIBLK.                                    \n     ==>                                                                        \n     ==> ASRA ABEND (0C7) detected and prevented. Caused by invalid decimal     \n     ==> arithmetic data format.                                               \n     ==>                                                                        \n     ==>      Press PF1 for a detailed description.                            \n     ==>                                                                        \n _ 00157     MOVE COMM-SW2 TO NUM-CHOICES.                                     \n   00158                                                                        \n _ 00159 CALL-COBOL.\n.\n.\n.                                                    \nInterTest for CICS halted the composite module at an automatic breakpoint because it detected and prevented an error\nin ASBIN25 when control passed to that subroutine. However, so far you do not know where in ASBIN25 the error\noccurred.\nNOTE\nThe name in the Program field is the name of the composite module COBDEML. InterTest for CICS is\nmonitoring the program which is the main composite program you set monitoring for before you began the\nadvanced demo session.\nSetting composite support lets you test and debug a called subroutine as if it were a separate program, with full\nsymbolic support. That means you can set breakpoints and other monitoring options for that subroutine. When\nInterTest for CICS detects an error, an automatic breakpoint is generated at the statement that triggered the abend, not\nat the CALL.\nYou can set composite support before you begin to test a program or at any time during testing. In this case, you are", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0ea1c184c12a-1", "text": "going to abend the task, set composite support, and then resume testing.\nAbend the Task\nWhen your program is stopped at a breakpoint, you can abend the task rather than resume execution.\n1.Type abend in the Command line of the Breakpoint display, and press Enter.\nNote: This action is the same as selecting option 3 Abend, from the Breakpoint Menu.\nInterTest for CICS displays the screen shown next.\n-----------------  CA InterTest for CICS ABEND BREAKPOINTED TASK  ----------------\n COMMAND ===>                                                                \n                                                                             \n    Type an abend code, then press ENTER.                                   \n                                                                             \n                                                                             \n    Abend Code  ____   Abend code options are:                               \n                                                                             \n                       blanks        Normal abend, no dump                   \n                       XXXX          Abend exits cancelled, no dump          \n 470", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e6328cc889cf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                       your code     Your abend code, dump taken\n.\n.\n.                                                                       \nBecause you do not need a dump, you do not need to enter an abend code.\n2.Press Enter.\nCICS informs you the task has been abended.\n3.Press Clear.\nSetting Composite Support\nTo set composite support, access the main CNTL menu from which you can set all of InterTest for CICS monitoring\noptions.\n1.Type ITST on a clear screen, and press Enter.\nInterTest for CICS displays the Primary Option Menu.\n2.Select option 2 Monitoring.\nInterTest for CICS displays the Monitoring Menu.\n3.Select option 1 Programs.\nInterTest for CICS displays the Program Monitoring Menu.\n---------------  CA InterTest for CICS  PROGRAM MONITORING  ------------------\n COMMAND ===>                                                            \n                                                                     \n   Type information and S to set or R to remove option(s) below.        \n                                                                    \n   Program  . . cobdeml_     Program name (or .ALL, .OPTIONS or generic)        \n   User ID  . . _______      User (or .ANY) for whom the program is monitored   \n                                                                                \n   Option       Description                                      More:   +\n _ Status       Display and/or remove monitoring options (S only)        \n _ Monitor      Monitoring (R removes monitoring and all options previously set)\n _ UBP          Unconditional breakpoints (specific program only)        \n _ CBP          Conditional breakpoints (specific program only)          \n _ RBP          Breakpoints for CICS, DB2, DL/I or external CALL requests       \n _ Stmt Trace   Statement tracing and data monitoring (COBOL only) \n _ New copy     Fetch new copy of program and reset monitoring options (S only)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e6328cc889cf-1", "text": "_ New copy     Fetch new copy of program and reset monitoring options (S only) \n _ Commands     Indirect commands defined for a specific COBOL or PL/1 program \n _ Replace      CICS resource name replacement options               \n _ Protect      Storage protection monitoring options             \n _ Special      Other options (storage allocation, file updating, etc.)      \n s Composite    Monitor multi-CSECT program's separately compiled components \n                                                                     \n PF1 Help       2            3 End        4 Return     5          6       \n PF7 Backward   8 Forward    9           10           11         12       \n4.In the Program field, type the name of the composite module you are using COBDEML.\n5.Type S to the left of Composite.\nInterTest for CICS displays the Composite Support menu.\n       CA InterTest for CICS - Composite Support Builder                   \n COMMAND ===>                                                      SCROLL: PAGE\n Define composite support for COBDEML  and press PF5.        Row 00001 of 00003 \n 471", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e6651a3d028e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                                                                \n                                                                                \n * *          *          *        *        *           *                        \n _ Link name  Monitor    Offset   Length   Language    Comments                 \n S COBDEML    COBDEML        20      748   IBMCOB 4.2                          \n S ASBIN25    ASBIN25       768      17C   HLASM  6.0                          \n S CSBIN25    CSBIN25       8E8      674   IBMCOB 4.2                          \n                                                                                \n                                                                                \n                                                                                 \n                                                                                \n                                                                                \n PF1 Help       2            3 End        4            5 Process    6 RFind     \n PF7 Backward   8 Forward    9           10           11           12           \nThis menu displays link-edit information for the composite program and its subroutines; for example, ASBIN25 and\nCSBIN25. This information is received from a batch job, executed after the composite module was link-edited.\nThe batch job that provides the link-edit information identifies all called subroutines of a program. For efficiency,\nhowever, it is a good idea to specify monitor-names just for the subroutines you want to test. You can always set\nmonitoring for more subroutines by assigning monitor-names on the Composite Support menu.\n6.Press PF5 to enable composite module monitoring.\nInterTest for CICS sets composite support for COBDEML and returns you to the Program Monitoring menu.\nNow InterTest for CICS monitors the subroutines and the composite module. This lets you can take advantage of all\nInterTest for CICS facilities to test and debug each of the programs.\nTIP\nYou can also set composite monitoring by issuing the COMPOSITE command from the Program Monitoring\nmenu.\nRe-execute the Demo Program", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e6651a3d028e-1", "text": "menu.\nRe-execute the Demo Program\nNow you can re-execute the demo program.\n1.Press PF4.\n2.InterTest for CICS displays the Primary Option Menu.\n3.Select option X Exit to exit to CICS.\n4.Clear the screen and type the transaction ID DEMC for the COBOL demo program and press Enter.\nInterTest for CICS displays the automatic breakpoint at which you were initially halted. However, now the breakpoint\noccurs at the actual statement in ASBIN25 that triggered the abend, not at the CALL to ASBIN25.\nCA InterTest for CICS - PROTSYM FILE SOURCE LISTING BREAKPOINT      \nCOMMAND ===>                                                             \nProgram= ASBIN25  Option #       Stmt #        Displacement=   Margin= 01  \n                                        Search=                          \n---------+---------------------------------------------------------\n     LOC  OBJECT CODE    ADDR1 ADDR2  STMT        SOURCE STATEMENT        \n _ 0000BA                              280 CONTINUE DS    0H             \n A 0000BA FA20 D1A0 211B 001A0 0011B   ==>          AP    TASKNUM,=P'1'  \n     ==>                                                         \n     ==> ASRA ABEND (0C7) detected and prevented. Caused by invalid decimal     \n     ==> arithmetic data format.                                \n     ==>                                                           \n     ==>      Press PF1 for a detailed description.               \n     ==>                                                          \n 472", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5be83de49e5b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _ 0000C0 F920 D1A0 211C 001A0 0011C   282          CP    TASKNUM,=P'2'\n.\n.\n.            \nNOTE\nThe name in the Program field is ASBIN25. When control passes to ASBIN25, InterTest for CICS starts\nmonitoring that program because you set composite support. Setting composite support enables InterTest to\nidentify and display the statement in the subroutine where the error occurred.\nThe error occurred because of improperly formatted data in TASKNUM. The AP instruction tries to move a packed\ndecimal 1 to TASKNUM. TASKNUM is defined as a packed decimal field, but it contains binary zeros instead of a valid\npacked decimal value. This error is the same type of error that you corrected in the basic demo session.\nDisplay the Data in TASKNUM\nTo correct this error, display the contents of TASKNUM and dynamically change the value.\n1.Tab to the AP instruction, and overtype the A with D.\n2.Position the cursor under any character in TASKNUM, and press Enter.\nInterTest for CICS displays the contents of TASKNUM.\nOn the left of the screen are the Assembler data field names; on the right are the corresponding hexadecimal and\ncharacter representations of each field.\nInterTest for CICS displays more than just the contents of TASKNUM. TASKNUM and all the subsequent fields in the\nsame data structure, that is in the same DSECT, are also displayed.\nCorrect the Data in TASKNUM\nAs you can see, TASKNUM does not contain a packed decimal value. TASKNUM in the COBOL version contains binary\nzeros rather than a packed decimal value; for COBOL II and COBOL/370 programs, TASKNUM contains other, incorrect\nvalues.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5be83de49e5b-1", "text": "values.\nYou can correct the error by overtyping the incorrect value with a correct value.\n1.Tab to the top line and move the cursor to the Hexadecimal value of TASKNUM.\n2.Overtype the current value; set it to a packed decimal zero by tying zero over the \"?\" and erase the remaining data\n(erase EOF).\n3.Press Enter.\n       CA InterTest for CICS - MAIN STORAGE UTILITY - Termid = U031      \n                                                                                \nStarting at Address =  101DA8  Disp   Structure Display Format                  \nTASKNUM                         1A0 | ?00000.                    |              \nTSTEXT                          1A3 | .. THIS IS A               |              \n                                    |  MESSAGE                   |              \n                                    | 12/25/99....               |              \n                                    | ............               |              \n                                    | ............               |              \n                                    | ............               |              \n                                    | .                          |              \nTSQLEN                          1EC | +0003866624.               |              \nMSGNAME                         1F0 |  0000000000.               |              \nMSGLEN                          1F4 |  00000.                    |              \nRECRBA                          1F6 | ......                     |              \nRECPONT                         1FC |  0000000000.               |              \n 473", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9a891754dc28-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                                                                \n                                                                                \n                                                                                \n ------------------------------------------------------------------------------ \n PF1 Help       2            3 End        4 Return     5            6 Dump      \n PF7 Backward   8 Forward    9 Caps Off  10           11 Redisplay 12 Structure \n CORE='R13.TASKNUM'                                                             \n CAIN4713 R13 not found - have assumed its register value\nInterTest for CICS redisplays the screen, changing your entries to uppercase.\nNow TASKNUM contains a packed decimal zero. You have corrected the error that triggered the automatic breakpoint.\n4.Press Clear.\nInterTest for CICS redisplays the previous Source Listing Breakpoint screen. However, the explanation of the abend no\nlonger displays.\nSet a Breakpoint in Subroutine CSBIN25\nNow you are going to set a breakpoint at the first statement in subroutine CSBIN25, the other subroutine you asked\nInterTest for CICS to monitor. Then, when you resume execution, InterTest for CICS halts execution at the breakpoint in\nthis subroutine.\nWhen you are stopped in a subroutine, you can use all InterTest for CICS features, including the features in the following\nlist:\n\u2022View the program listing and compiler output\n\u2022Display and modify main and auxiliary storage\n\u2022Set and remove breakpoints and other monitoring options\n\u2022Request single-step execution\n\u2022Display the backtrace that brought the program to its current point\n\u2022Tab back to the Program field.\n\u2022Overtype the current name with the COBOL subroutine name CSBIN25 and press Enter.\n   CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT       \nCOMMAND ===>                                                                    \nProgram= csbin25  Option #       Stmt #        Displacement=        Margin= 01  \n                                        Search=", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9a891754dc28-1", "text": "Search=                                 \n----------+-------------------------------------------------------------------- \n     Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n _ 0000E2                              365 CONTINUE DS    0H                    \n A 0000E2 FA20 D1A0 2143 001A0 00143   ==>          AP    TASKNUM,=P'1' \n.\n.\n.   \nInterTest for CICS displays the source listing for COBOL program, for example, CSBIN25.\nNow you are going to set an unconditional breakpoint at the first statement in the Procedure Division.\n\u2022Tab to the MOVE ZERO TO DIVCT statement.\n\u2022Type U to the left of that statement, and press Enter. The U sets a breakpoint that stops before  the statement\nexecutes. You could also enter a ) to set a breakpoint that stops after the statement executes.\nCA InterTest for CICS - PROTSYM FILE  ABEND DETECTED DISPLAY            \nCOMMAND ===>                                                                    \nProgram= CSBIN25  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n 474", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1d1b0d3770c9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n------------------------------------------------------------------------------- \n _ 000017     05  COMM-DATE.                                                    \n _ 000018         10  COMM-MM         PIC 99.                                  \n_ 000019         10  FILLER          PIC X.                                    \n _ 000020         10  COMM-DD         PIC 99.                                   \n _ 000021         10  FILLER          PIC X.                                    \n _ 000022         10  COMM-YY         PIC 99.                                   \n _ 000023 PROCEDURE DIVISION USING COMM-TEXT.                                   \n u 000024     MOVE ZERO TO DIVCT.                                               \n _ 000025 GET-DATE.                                                             \n _ 000026     MOVE COMM-YY TO PROGYY.                                           \n _ 000027     MOVE COMM-MM TO PROGMM.                                           \n _ 000028     MOVE COMM-DD TO PROGDD.                                           \n _ 000029     DIVIDE PROGYY BY 4 GIVING DIVYY REMAINDER YY-REM.                 \n _ 000030     MOVE PROGMM TO DIVMM.                                             \n _ 000031     GOBACK.                                                           \nAn \"M\" preceding a data-name reference indicates that the data-name is modified \n                                                                                \n _   DEF DATA NAMES                     REFERENCES                              \n _     17 COMM-DATE \nInterTest for CICS sets an unconditional breakpoint at the MOVE statement.\n\u2022Press Clear.\nInterTest for CICS redisplays the previous Source Listing Breakpoint screen.\nResume Program Execution\nNow you are going to continue program execution.\nPress PF5.\nThe program resumes execution. When the control passes to subroutine CSBIN25, InterTest for CICS halts the program\nat the unconditional breakpoint you set.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1d1b0d3770c9-1", "text": "at the unconditional breakpoint you set.\nAt this point, you can use InterTest for CICS to examine the program listing of CSBIN25 or the values of any program\nvariables. However, you are simply going to remove the breakpoint and resume program execution.\nRemove the Breakpoint and Resume Execution\nOvertype the U with X, and press PF5.\nInterTest for CICS removes the unconditional breakpoint and program execution resumes. COBDEML completes\nexecution and the Options Menu is displayed.\nReview What Happened\nIn this part of the demo session the following events occurred:\n\u2022When you executed COBDEML, InterTest for CICS detected and prevented an abend caused by invalid data in one of\nits called subroutines.\nInterTest for CICS displayed the automatic breakpoint at the statement that called the subroutine, rather than the\nstatement that triggered the breakpoint, because InterTest for CICS was not monitoring the subroutine.\n\u2022You set composite support for COBDEML so that InterTest for CICS would monitor its subroutines: ASBIN25 and\nCSBIN25.\n 475", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a0130ccf7b80-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSetting composite support lets you test and debug a called subroutine with full symbolic support and use all InterTest\nfor CICS features.\n\u2022When you re-executed COBDEML, InterTest for CICS redisplayed the automatic breakpoint; this time at the actual\nstatement in subroutine ASBIN25 that caused the error.\n\u2022You corrected the error by overtyping the contents of the invalid field.\n\u2022You then set an unconditional breakpoint in the other subroutine, CSBIN25, and resumed program execution. When\ncontrol passed to CSBIN25, InterTest for CICS halted execution at the breakpoint you set.\nThe ability to halt execution at any statement in a subroutine means you can test a subroutine as if it were a main\nprogram.\n\u2022You removed the unconditional breakpoint and continued program execution.\nThis concludes Option 07 of the advanced demo session. Press Enter to continue with the demo session or press Clear to\nterminate the session.\nPL/I Primer\nUse this PL/I Primer to train new users in basic InterTest test and debug programs features.\nThe primer also introduces some of the advanced features of InterTest for CICS.\nWe recommend that all users take the demo sessions in this article and become familiar with the features explained here.\nFor complete information about these and other features, see CICS Debugging. Read the PL/I Basic Demo Session first,\nbecause it is the best way to begin learning about your product.\nGetting Help\nThe Help facility is online documentation of product features. The Help facility makes it easy to learn and use the product.\nHelp is available from all product screens.\nTo view an online summary of new features for this release, use ITST Option 8 What's New.\nPL/I Basic Demo Session\nThis article provides a basic InterTest for CICS user demo session.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a0130ccf7b80-1", "text": "PL/I Basic Demo Session\nThis article provides a basic InterTest for CICS user demo session.\nThe best way to start learning about InterTest for CICS is to perform the demo at a terminal.\nThe basic demo session illustrates many of the testing and debugging tasks that you will use on your programs. These\ntasks are discussed in more detail in the next article. For more information on any of these topics, see CICS Debugging.\nWe are assuming that InterTest for CICS has been installed on your system. If not, contact your systems programmer.\nMaintain Synchronized Processing\nBefore you begin testing, be aware that when InterTest for CICS searches the symbolic files for the PL/I programs that you\nspecify for testing, the product tries to match the load module and the symbolic file date and time. If no match is found,\none of the following items is displayed:\n\u2022A Symbolic Version List\n\u2022A warning message\nThis feature lets you always maintain synchronized processing by enabling you to select the correct symbolic version of\nthe program that you want to test.\n 476", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bba9ef02bc3e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSymbolic Version Processing\nWhen you request a PL/I program that has no previously declared breakpoints or monitoring options set, InterTest for\nCICS matches the most recently compiled symbolic file date and time to the load module date and time.\n\u2022If an exact match is found, InterTest for CICS automatically selects and displays the program. However, if an exact\nmatch is found, and a more recently compiled version of the program is in a PROTSYM file, InterTest displays the\nsymbolic version list from which you can provide the following responses:\n\u2013Select the matching listing and debug the program.\n\u2013Do not select the matching listing and cancel monitoring. Then new copy the latest version of the program into your\nCICS region and select the latest program version for monitoring.\n\u2022If a match is not found, InterTest for CICS displays the Symbolic Version List from which you can:\n\u2013Select the appropriate symbolic file.\n\u2013Ignore symbolic processing for the program.\nThe Symbolic Version List screen also explains the cause of the mismatch.\nDuring Automatic Breakpoint processing, if a program has no previously selected symbolic file, InterTest for CICS\nmatches the load module date and time to a symbolic file.\n\u2022If an exact match is found, InterTest for CICS automatically selects and displays the program.\n\u2022If a match is not found, InterTest for CICS automatically selects the first symbolic file that contains the program and\ndisplays it with a warning message on the first Source Listing Breakpoint screen. This message, which is shown on the\nfollowing screen, indicates the mismatch.\n CA InterTest for CICS - SYMBOLIC VERSION LIST                            \n  \n    Program = PL1DEMO     Load Module Date/Time =  11/12/2000 09:02:03", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bba9ef02bc3e-1", "text": "File ID     Date       Time    Language     Comments                         \n  _ PROTSYM  11/12/2000  09.52.23  PLI        LATEST VERSION                     \n  _ PROTDMO  08/31/2000  14.12.15  PLI \n .\n .\n . \n          S - Select which Symbolic file to use                                   \n  -------------------------------------------------------------------------------\n  PFKEYS:  1 Help      2           3 No file   4           5           6         \n           7           8           9          10          11          12         \n  CAIN8000 The latest Symbolic version does not match the current load module\n \nNOTE\nOnce a symbolic file is selected for a program, InterTest for CICS continues to use the selected file and\nbypasses subsequent date and time matching until all declared breakpoints and monitoring options are removed\nfor the program, or until a NEWCOPY command is executed. This can be done from ITST Option 2.1 by\nselecting the Option for New copy, or by typing the following command from CICS:\n CNTL=NEW,PROG=progname\n \nDemo Session Objectives\nThis demo session, teaches you how to perform the following tasks:\n 477", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "28c151184c36-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Select a source listing from the InterTest for CICS ITST menus\n\u2022Inform InterTest for CICS that you want to test a program (set monitoring)\n\u2022Respond to the information InterTest for CICS provides when it detects an error\n\u2022Examine the value of a variable\n\u2022Dynamically change the value of a variable\n\u2022Halt program execution at any point (set breakpoints)\n\u2022Resume program execution\nDemo Session Scenario\nThe InterTest for CICS basic demo session takes you through the following scenario:\n1.You use the InterTest for CICS Primary Option Menu to select and view the source listing of PL1DEMO, the sample\nprogram to execute.\n2.You set monitoring for the sample program and view the status display of your monitoring request.\n3.You exit InterTest for CICS menus and initiate PL1DEMO.\n4.InterTest for CICS intercepts and prevents an ASRA abend in PL1DEMO. InterTest for CICS halts PL1DEMO at an\nassignment statement and displays a diagnostic message informing you that the problem is caused by improperly\nformatted data.\n5.You examine the current value of TASKNUM, the receiving field in the assignment statement that you suspect might be\nthe cause of the problem. You find that TASKNUM does not contain a valid packed decimal number.\n6.You move a packed decimal zero into TASKNUM to correct the error.\n7.You set a breakpoint to halt PL1DEMO at another statement. This step is purely instructional; it has nothing to do with\ncorrecting the ASRA.\n8.You resume program execution. InterTest for CICS halts the program at the breakpoint you set in Step 7. You can see\nthat, when the assignment statement was executed, the value of TASKNUM changed.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "28c151184c36-1", "text": "that, when the assignment statement was executed, the value of TASKNUM changed.\n9.Clean up by removing the breakpoint that you set. Then resume program execution and PL1DEMO runs to\ncompletion.\nSelect the Source Program from the ITST Menus\nStart your session by selecting the source listing of the InterTest for CICS demonstration program from the ITST Primary\nOption Menu.\n1.Sign on to CICS.\nType ITST on a clear screen.\n2.Press Enter.\nThe Primary Option Menu appears.\n ---------------  CA InterTest for CICS PRIMARY OPTION MENU  --------------\n OPTION  ===>                                                                  \n    1  Source             - Display/select program source files/listings       \n    2  Monitoring         - Display/modify CA InterTest monitoring/activity    \n    3  Main storage       - Display/modify CICS storage areas                  \n    4  Auxiliary storage  - Display/access databases/files/queues              \n    5  Dump analysis      - Invoke CA SymDump CICS dump/trace capture facility \n    6  Product help       - Invoke CA InterTest product help facility          \n    7  Status/Maintenance - Product status and maintenance functions           \n    8  What's new?        - Display information about CA InterTest for CICS  \n    X  Exit               - Terminate menu processing                          \n  \n  \n  \n 478", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5c0b496651ae-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n PF1 Help       2            3 End        4 Return     5            6          \n PF7            8            9           10           11           12         \n \nNote that the PF keys have conventional assignments for ISPF-like navigation:\n\u2022PF1 Help accesses online help\n\u2022PF3 End returns one panel\n\u2022PF4 Return returns to the top-level menu\nNow look at the source listing of the program that we will debug.\n1.Type 1 in the Option field.\n2.Press Enter.\nThe InterTest for CICS Source Menu appears.\n -------------------  CA InterTest for CICS SOURCE MENU  -------------------\n OPTION  ===> 1                                                                \n  \n    Select a member list type, specifying optional criteria below.            \n  \n    1  Source listings    - Display/select program source listings             \n    2  Symbolic files     - Display/select program source SYMBOLIC files       \n  \n    Type specific or generic program/file name(s):                             \n       (Valid mask characters are  *  and/or  +)                               \n  \n    p*______ ________ ________ ________ ________ ________ ________ ________    \n  \n .\n .\n .\n \n3.Type 1 in the Option field to search for program listings.\n4.Tab to the first entry field for file/program names, and type P*. The asterisk is a generic or wildcard character. The\nasterisk indicates that anything from this point in a file name satisfies the search criteria.\n5.Press Enter.\nThe Source Listing Selection screen displays. The screen lists all program Source Listings beginning with the letter P,\nin all symbolic files. Your list might have fewer or more entries.\n ------------  CA InterTest for CICS   SOURCE LISTING SELECTION ------------\n  COMMAND ===>", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5c0b496651ae-1", "text": "------------  CA InterTest for CICS   SOURCE LISTING SELECTION ------------\n  COMMAND ===>                                                                   \n  \n    Type S to select a source listing.                                           \n  \n  \n    Name     File         Created       Size Attributes                          \n  _ PL1DEML  PROTSYM  09/06/2013 14:03    43 PL/I 3.2, composite                 \n  _ PL1DEMO  PROTSYM  09/06/2013 14:01   268 PL/I 3.2                                           \n  _ PROTCI63 PROTSYM  05/25/2013 12:53   637 HLASM 5.0, no purge                 \n  _ PROTCI64 PROTSYM  05/25/2013 12:53   642 HLASM 5.0, no purge                 \n  _ PROTIN62 PROTSYM  05/25/2013 12:53   257 HLASM 5.0, no purge                 \n  _ PROTIN63 PROTSYM  05/25/2013 12:53   258 HLASM 5.0, no purge                 \n  _ PROTIN64 PROTSYM  05/25/2013 12:54   259 HLASM 5.0, no purge                 \n  _ PSBIN25  PROTSYM  09/06/2013 16:15    25 PL/I 3.2                            \n    *** End of data ***                                                          \n 479", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8ddbf0401740-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  \n  \n  \n  \n  PF1 Help       2 Refresh    3 End        4 Return     5            6           \n  PF7 Backward   8 Forward    9           10           11           12\n \n6.Locate the demo program, PL1DEMO, in the Selection List. You can scroll the file list using PF7 and PF8, or optionally,\nyou can use the following command:\n LOCATE program-name\n \nNOTE\nIf the file list does not contain the name of the demo program indicated above, the person who installed\nInterTest for CICS might have changed the name of the InterTest for CICS sample programs available to you.\nCheck with that person to find out the correct names.\n7.Type S in the field to the left of the program name to select it for Source Listing Display.\n8.Press Enter.\nInterTest for CICS displays the PROTSYM File Source Listing Display, which shows the compiled listing of PL1DEMO.\n\u2013The top half of the display identifies the program and provides fields for entering commands, option numbers (to\njump to different parts of your source listing), statement numbers, and search criteria.\nDepending on your session defaults, you might not see lines identifying the PF key and Option # field titles. These\nfields were omitted from the images in this article for clarity.\n\u2013The bottom half of the display contains the source listing.\n CA InterTest for CICS - PROTSYM FILE  SOURCE LISTING DISPLAY            \n COMMAND ===>                                                                    \n Program= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ---------+---------------------------------------------------------------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8ddbf0401740-1", "text": "Search=                                 \n ---------+--------------------------------------------------------------------- \n  _    18.1            /*   INTERTEST PL/I DEMO PROGRAM   10/01/89  3.1.200      \n  _    19.1            PL1DEMO:  PROC(DFHEIPTR,COMMAREA_PTR) OPTIONS(MAIN REENT  \n  _    20.1     1      DCL 1 DFHCNSTS  STATIC,  /* CONSTANTS USED BY TRANSLATOR  \n  _    21.1                   2  DFHLDVER CHAR(22) INIT('LD TABLE DFHEITAB 530.  \n  _    22.1                   2  DFHEIB0 FIXED BIN(15) INIT(0),                  \n  _    23.1                   2  DFHEID0 FIXED DEC(7) INIT(0),                   \n  _    24.1                   2  DFHEICB CHAR(8) INIT('        ');               \n  _    25.1     1      DCL DFHEPI ENTRY, DFHEIPTR PTR;                           \n  _    26.1     1      DCL 1 DFHEIBLK BASED (DFHEIPTR),                          \n  _    27.1                  02    EIBTIME  FIXED DEC(7),                        \n  _    28.1                  02    EIBDATE  FIXED DEC(7),                        \n  _    29.1                  02    EIBTRNID CHAR(4),                             \n  _    30.1                  02    EIBTASKN FIXED DEC(7),                        \n  _    31.1                  02    EIBTRMID CHAR(4),", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8ddbf0401740-2", "text": "_    32.1                  02    EIBFIL01 FIXED BIN(15),                       \n  _    33.1                  02    EIBCPOSN FIXED BIN(15),                       \n  _    34.1                  02    EIBCALEN FIXED BIN(15),                       \n  _    35.1                  02    EIBAID   CHAR(1),                             \n  _    36.1                  02    EIBFN    CHAR(2),                              \n \n 480", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b6c80f65aff0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nThe statement numbers on your screen might not match the numbers that are shown in the illustrations. This\nfact does not affect your ability to perform the test session.\nView the Source Listing Profile\nType PROFILE on the Command line and press Enter (or, press PF4 Profile) to view the PF key assignments and other\nsession options.\nInterTest for CICS displays the Source Listing Profile for your current session. This lists the PF keys, options, and current\nenvironment settings relating to the Source Listing display.\n CA InterTest for CICS - PROTSYM FILE  SOURCE LISTING PROFILE            \n COMMAND ===>                                                                    \n Program= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n OPTS 1 Data xref 2 Aggregate 3 Stor reqs  4 Stat stor  5 Var stor   More:   +   \n      6 Offsets   7 Gend code 8 Err msgs   9 Srch fwd  10 Srch bwd               \n PFKS 1 Help      2           3 End        4 Auto prms  5 Monitor    6 Menu      \n      7 Backward  8 Forward   9 Next Wnd  10           11           12 Status    \n ---------+--------------------------------------------------------------------- \n Display window   = N         N (None), T (Titles), R (Registers),               \n                              K (Keep), P (Program)                              \n PF7/8 amount     = PAGE      PAGE, HALF, STOP, or a number from 1 to 9999       \n Step Timing      = BEFORE    Stop  Before  or  After  the next STMTS is executed\n Stepping amount  = 001       The number of STMTS   to execute", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b6c80f65aff0-1", "text": "Stepping amount  = 001       The number of STMTS   to execute                   \n Auto-stepping    = OFF       ON to activate; press PF4 to change values         \n Source List BKPT = ON        OFF to use the detailed breakpoint display         \n From terminal ID = U006      Terminal ID where the program will execute         \n BKPT terminal ID = U006      Terminal ID to receive the breakpoint displays     \n User ID          = .ANY      User ID who will execute this program              \n AutoKeep Display = ON        OFF to deactivate                                  \n Code Counting    = OFF       ON to activate Code Coverage                       \n SDF              = DATA      DATA for Structure Display Format                  \n \nNOTE\nVerify that the AutoKeep Display feature is activated for this demo session. If not, change it from OFF to ON and\npress Enter.\nSet Monitoring\nThe next step is to instruct InterTest for CICS to monitor PL1DEMO. As part of monitoring a CICS command-level program\nsuch as PL1DEMO, InterTest for CICS automatically prevents all CICS abends during execution. This functionality is\ndescribed later when InterTest for CICS prevents PL1DEMO from abending because of an ASRA.\nThere are a few ways to tell InterTest for CICS to monitor the program. If you are viewing a program source listing, you\ncan do the following actions:\n\u2022Type MONITOR on the Command line and press Enter.\n\u2022Press PF5 (notice PF5 is listed as Monitor on the Source Listing Profile illustration).\nPress PF5 or use the monitor command to begin monitoring the demo program. This functionality is available from the\nSource Listing Profile or from the Source Listing Display.\nThe screen momentarily flashes as the request processes. The Source Listing Display screen then reappears.\n 481", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "06a420a4426d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nView Monitoring Status\nTo verify that the demo program is being monitored, display the Monitoring Status report for the current program.\n1.Press PF12 , or type STATUS on the command line and press Enter.\n CA InterTest for CICS - PROTSYM FILE  SOURCE LISTING DISPLAY            \n COMMAND ===> status                                                            \n Program= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ---------+--------------------------------------------------------------------- \n  _    18.1            /*   INTERTEST PL/I DEMO PROGRAM   10/01/89  3.1.200      \n  _    19.1            PL1DEMO:  PROC(DFHEIPTR,COMMAREA_PTR) OPTIONS(MAIN REENT  \n .\n .\n .\n \nInterTest for CICS displays the Monitoring Status screen. This status shows the monitoring entry for the current\nprogram only.\nThis display gives you an up-to-date summary of how InterTest for CICS is monitoring your program in an expandable/\ncollapsible tree format. You can scroll the list, or collapse and expand the list using the indicated PF keys at the bottom\nof the display.\n ---------------  CA InterTest for CICS  MONITORING STATUS ----------------\n  COMMAND ===>                                                                   \n  \n    Type + to expand or - collapse option levels displayed below,                \n           or R to remove option(s).                                             \n  \n      Option     Description                Attributes                           \n  _ - PL1DEMO    Program monitor entry      PL/I                                 \n  _ - |-.ANY     User monitoring options    Active                               \n        |        Symbolic listing file      PROTSYM                              \n  _     |-SLB    Source listing breakpoints U006                                 \n                 *** End of data ***", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "06a420a4426d-1", "text": "*** End of data ***                                             \n  \n  \n  \n  \n  \n  PF1 Help       2 Refresh    3 End        4 Return     5 Collapse   6 Expand    \n  PF7 Backward   8 Forward    9           10           11           12          \n \nEach entry in the monitoring status display for PL1DEMO indicates the following information:\n\u2013The top entry tells you InterTest for CICS is monitoring the PL/I program PL1DEMO.\n\u2013The second entry (.ANY) indicates InterTest for CICS monitors PL1DEMO when executed by a user. If your status\ndisplay shows your CICS User ID instead of .ANY, that is fine. This information indicates monitoring and options\ntake effect when your ID is executing the program, but not when someone else executes the program. In effect,\nwhen the user monitoring option is set to a specific CICS User ID, InterTest for CICS creates a personal debugging\nsession for that user.\n 482", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6550dc93987d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nFor details on using and switching the User ID Monitoring Option, see Monitoring Menu Options.\n\u2013The last entry shows that the SLB option for Source Listing breakpoints is on. SLB means InterTest for CICS uses\nthe Source Listing version of the breakpoint display throughout your test session, instead of the detailed version.\nThe SLB version is the one used throughout this article and is recommended for all users.\nNOTE\nIf the Status display does not appear, monitoring is not set correctly and the Program Monitoring menu\ndisplays a message that no entries (for PL1DEMO) were found. In this case, press  PF3 to return to the\nSource Listing display, and then press PF5 to set monitoring. Use PF12 to check the status again before\ncontinuing.\n2.Once you verify that the correct demo program is being monitored, press PF3 to go back to the Source Listing.\nNow exit to CICS using the fastpath entry (=X), as follows:\n3.Type =X in the Source Listing Command field and press Enter. This entry returns you to ITST menu processing.\n4.From the Source Selection Menu, type =X in the Command field and press Enter to exit to CICS.\nBegin Program Execution\nNow you are ready to start testing PL1DEMO.\n1.Clear the CICS display and type DEMP , the transaction identifier of the demo program.\n2.Press  Enter.\nThe following Welcome screen appears.\n ****************************************************************************** \n ****************************************************************************** \n *****                                                                    ***** \n *****                             Welcome to the                         ***** \n *****                       CA InterTest Demo Session                    ***** \n *****                                                                    ***** \n *****                                                                    ***** \n *****              Before proceeding, please have on hand the            ***** \n *****              guide which accompanies the Demo Session.             ***** \n *****                                                                    ***** \n *****                                                                    *****", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6550dc93987d-1", "text": "*****                                                                    ***** \n *****                                                                    ***** \n *****     Please make sure that the program PL1DEMO is monitored by      ***** \n *****     CA InterTest. This program will abend if it is not monitored.  ***** \n *****                                                                    ***** \n *****     To turn the monitor on, press CLEAR and follow the steps       ***** \n *****     outlined in the documentation.                                 ***** \n *****                                                                    ***** \n *****     If the monitor is already on, press ENTER to begin the         ***** \n *****     Basic Demo Session or PF2 to go to the Options Menu.           ***** \n *****                                                                    ***** \n ****************************************************************************** \n ******************************************************************************\n \n3.Press Enter.\nPL1DEMO resumes execution.\nDetect and Prevent an Abend\nThe next screen is not displayed by the PL/I demo. This screen is a diagnostic screen that is called a breakpoint display,\nand is displayed by InterTest for CICS when an error is detected.\n 483", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "079263076141-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT        \n COMMAND ===>                                                                   \n Program= PL1DEMO  Option #       Stmt #                             Margin= 01 \n                                         Search=                                \n -------------------------------------------------------------------------------\n  _____ TASKNUM                         | ?00000.                               \n ---------+---------------------------------------------------------------------\n  _   636.1            CONTINUE_TASK:                                           \n  _   637.1               MAPNUM  = '00';                                       \n   A   ==>.1     1         TASKNUM = TASKNUM + 1;      ==>                             ==> ASRA ABEND (0C7)\n detected and prevented. Caused by invalid decimal          ==> arithmetic data format.                      \n                               ==>                                                                            \n ==>      Press PF1 for a detailed description.   \n      ==>                                                                       \n  \n  _   639.1     1         IF TASKNUM > 2 THEN                                   \n  _   640.1     1            GOTO END_SESSION;                                  \n  _   641.1     1         IF TASKNUM = 1 THEN                                   \n  _   642.1     1            GOTO SENDSCR3;                                     \n  _   643.1     1         GOTO END_SESSION;                                     \n  _   644.1                                                                     \n  _   645.1     1      SENDSCR3:                           /** ASRA CONGRATULAT \n  _   646.1                   /* EXEC CICS SEND MAP('DASRA'\n \nNotice that InterTest for CICS has highlighted an ADD instruction and displayed a message below it. Execution of that\nADD instruction triggered an ASRA abend. InterTest for CICS prevented the abend and displayed the diagnostic screen\nthat you are viewing.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "079263076141-1", "text": "that you are viewing.\nWhen InterTest for CICS stops program execution, we say that it halts the program at a breakpoint. This occurs\nautomatically, as in the example, or the program halts at a breakpoint set by you, the programmer. The A to the left of the\nassignment statement indicates that the current halt in program execution is an Automatic breakpoint - not a breakpoint\nthat you set.\nNow look at the highlighted message. This message explains that the problem is caused by improperly formatted data.\nWhich data? Since TASKNUM = TASKNUM + 1 triggered the breakpoint, it is likely that TASKNUM contains improperly\nformatted data.\nSo far, InterTest for CICS has prevented PL1DEMO from abending and identified the problem. Next, perform the following\nprocedures:\n1.Determine the cause of the error.\n2.Dynamically correct the error by changing the value of TASKNUM.\nDetermine the Cause of the Error\nConfirm that the value stored in TASKNUM is not in valid arithmetic format by displaying the current value; the value prior\nto the execution of the assignment statement that triggered the ASRA.\nInterTest for CICS displays the current value of TASKNUM, as shown in the following screen.\n CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT        \n COMMAND ===>                                                                   \n Program= PL1DEMO  Option #       Stmt #                             Margin= 01 \n                                         Search=                                \n -------------------------------------------------------------------------------\n 484", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e7f0cdf31534-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  _____ TASKNUM                         | ?00000.                               \n ---------+---------------------------------------------------------------------\n  _   636.1            CONTINUE_TASK:                                           \n  _   637.1               MAPNUM  = '00';                                       \n  A   ==>.1     1         TASKNUM = TASKNUM + 1;      ==>                       \n      ==> ASRA ABEND (0C7) detected and prevented. Caused by invalid decimal    \n      ==> arithmetic data format.                                               \n      ==>                                                                       \n      ==>      Press PF1 for a detailed description.                            \n      ==>                                                                       \n  \n  _   639.1     1         IF TASKNUM > 2 THEN                                   \n  _   640.1     1            GOTO END_SESSION;                                  \n  _   641.1     1         IF TASKNUM = 1 THEN                                   \n  _   642.1     1            GOTO SENDSCR3;                                     \n  _   643.1     1         GOTO END_SESSION;                                     \n  _   644.1                                                                     \n  _   645.1     1      SENDSCR3:                           /** ASRA CONGRATULAT \n  _   646.1                   /* EXEC CICS SEND MAP('DASRA')                   \n \nWhen the AutoKeep Display feature is active, InterTest for CICS automatically displays the values of the variables that\nare associated with a line of code. In this case, TASKNUM displays in this specially formatted Keep window. On the left is\nthe name of the data item; on the right, the question mark in the first position indicates incorrect data content for the field\ndatatype, in this case low values (binary zeros).", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e7f0cdf31534-1", "text": "datatype, in this case low values (binary zeros).\nUp to six data items at a time display within the scrollable Keep window. This feature lets you see how the values of data\nitems change as your program executes. The Keep window remains until you remove all data items from it.\nNow, look at the contents of TASKNUM. TASKNUM does not contain a valid packed decimal value. Instead, it contains\nlow-values (binary zeros). PL/I does not let you assign a value to a field without initializing it.\nChange the Value in TASKNUM Dynamically\nNow that we have identified and confirmed the cause of the problem, we can fix it.\n1.Type M (modify) to the left of TASKNUM in the Keep window.\n2.Press Enter.\n CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \n COMMAND ===>                                                                    \n Program= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n  m____ TASKNUM                         | ?00000.                                \n ---------+--------------------------------------------------------------------- \n  _   636.1            CONTINUE_TASK:                                            \n  _   637.1               MAPNUM  = '00';                                        \n  A   ==>.1     1         TASKNUM = TASKNUM + 1;      ==>  \n .\n .\n .\n \nInterTest for CICS generates a fill-in-the-blanks MOVE statement, as illustrated in the following figure. The generated\nMOVE statement is equivalent to the PL/I assignment statement:\n 485", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5f0e55a7d58a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n TASKNUM = _________________\n \n3.Type zeros in the MOVE field, as shown next, and press Enter.\nNOTE\nThe InterTest for CICS MOVE statement automatically eliminates the need for you to know the type of data\n(For example binary or packed), or the length of TASKNUM.\n CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \n COMMAND ===>                                                                    \n Program= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n  _____ TASKNUM                         | ?00000.                                \n ---------+--------------------------------------------------------------------- \n  \n MOVE zeros___________________________________________________________           \n  \n  to                                                                             \n  \n      TASKNUM                                                                    \n  \n Overtype Underscores with a Data-Name, Figurative Constant,                     \n Alphanumeric Literal, or Numeric Literal\n \nInterTest for CICS executes the MOVE statement. As a result, TASKNUM now contains a packed decimal zero.\nInterTest for CICS also displays a main storage display that shows the new value of TASKNUM, as shown in the\nfollowing screen.\n CA InterTest for CICS - MAIN STORAGE UTILITY - Termid = U006        \n  \n Starting at Address =20804231         Structure Display Format                  \n  02 TASKNUM                         |  00000.                    |              \n  02 TS_TEXT                         | ............               |              \n                                     | ............               |              \n                                     | ........                   |              \n  \n  \n  \n  \n  \n  \n  \n  ------------------------------------------------------------------------------ \n  PF1 Help       2            3 End        4 Return     5            6 Dump      \n  PF7 Backward   8 Forward    9 Caps Off  10           11 Redisplay 12 Structure", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5f0e55a7d58a-1", "text": "CORE=MOVE ZEROS TO TASKNUM                                                     \n  CAIN0201 RECEIVING FIELD has been changed as shown\n \nYou can change the contents of a field by overtyping the desired bytes in the Keep window or on the main storage\ndisplay. Overtyping is faster than using an InterTest for CICS-generated MOVE statement. However, with the MOVE\nstatement you do not have to know the internal representation of the data. InterTest for CICS automatically takes care\nof the details for you.\nNow we return to the program listing so that we can continue to test PL1DEMO.\n 486", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7e0009f6d059-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n4.Press Clear.\nInterTest for CICS redisplays the breakpoint screen without the explanation of the abend. Note the new value of\nTASKNUM in the Keep window.\nNOTE\nYou also can correct this bug using indirect commands, which are described in PL/I Advanced Monitoring\nFeatures.\nControl Program Execution\nNow that the value in TASKNUM has been properly initialized, the next step might be to continue testing by resuming\nprogram execution. However, this is a good opportunity to learn about another important feature of InterTest for CICS, the\nability to control program execution by setting breakpoints.\nStop Your Program by Setting Breakpoints\nOne of the problems with traditional testing methods is that you have little or no control over program processing. You\ninitiate the task, and the program either runs to completion or abends.\nWith InterTest for CICS, you can control program execution in several ways. For example, you can set stops, called\nbreakpoints, anywhere in your program. The types of breakpoints you can set for PL/I programs are unconditional,\nconditional, and request breakpoints.\n\u2022When you set an unconditional  breakpoint at a statement, the program stops before or after the statement is\nexecuted. (Depending on the type of unconditional breakpoint that you set.)\n\u2022When you set a conditional  breakpoint at a statement, the program stops only if a condition you specified is met,\nsuch as a counter equaling or exceeding a specified value. You can also set a conditional breakpoint to stop at any\ninstruction when the condition you specified is met.\n\u2022When you set a request breakpoint , the program stops before all CICS commands, macros, and other program calls\n(such as calls to DL/I or DB2), or just before specific commands (such as all READ or WRITE commands).\nWhat You Can Do When Your Program Is Stopped", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7e0009f6d059-1", "text": "What You Can Do When Your Program Is Stopped\nOnce a program is stopped, you can use the InterTest for CICS testing and debugging facilities to do the following tasks:\n\u2022Examine the source listing\n\u2022Examine and modify main and auxiliary storage to detect and correct errors\n\u2022Set and remove breakpoints\n\u2022Examine a program backtrace, or execution path\n\u2022Keep variables in a Keep window to observe changes in their values\n\u2022Abend your task with or without a dump\n\u2022Go around a problem by resuming program execution from a location other than the one at which the program is\nstopped\n\u2022Execute the program in single-step mode; that is, the program executes one verb and then stops\nNow we demonstrate how easy it is to control program execution by setting an unconditional breakpoint.\nSet Unconditional Breakpoints\nYou can set unconditional breakpoints directly on the Source Listing screen as easily as you displayed and modified\nTASKNUM. Enter U or ) to the left of each statement where you want the application to halt program execution. The U\nsets a breakpoint that stops before  the statement is executed. The ) sets a breakpoint that stops after the statement is\nexecuted.\nLet us see how to set a \"before\" breakpoint at the following IF statement:\n 487", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "381c1166ebfe-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n IF TASKNUM = 1 THEN\n \n1.Type U to the left of the statement number on the IF TASKNUM = 1 THEN line.\n2.Press Enter.\n CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \n COMMAND ===>                                                                    \n Program= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n  _____ TASKNUM                         |  00000.                                \n ---------+--------------------------------------------------------------------- \n  _   636.1            CONTINUE_TASK:                                            \n  _   637.1               MAPNUM  = '00';                                        \n  A   ==>.1     1         TASKNUM = TASKNUM + 1;                                 \n  _   639.1     1         IF TASKNUM > 2 THEN                                    \n  _   640.1     1            GOTO END_SESSION;                                   \n  u   641.1     1         IF TASKNUM = 1 THEN                                    \n  _   642.1     1            GOTO SENDSCR3;                                      \n  _   643.1     1         GOTO END_SESSION;                                      \n  _   644.1                                                                      \n  _   645.1     1      SENDSCR3:                           /** ASRA CONGRATULAT  \n  _   646.1                   /* EXEC CICS SEND MAP('DASRA')                     \n  _   647.1                                     MAPSET('IN25PMP')                \n  _   648.1                                     WAIT                             \n  _   649.1                                     ERASE */                         \n  _   650.1                   DO;", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "381c1166ebfe-1", "text": "_   650.1                   DO;                                                \n  _   651.1     1  1          DCL DFHENTRY_BF5EF358_068E978B BASED(ADDR(DFHEI0)  \n  _   652.1             ASSEMBLER) ENTRY(*,CHAR(7),*,FIXED BIN(15),CHAR(7));\n \n3.Press PF5 (Resume) to continue execution from where the program is stopped (at the statement TASKNUM =\nTASKNUM + 1).\nInterTest for CICS resumes program execution and continues until it reaches the breakpoint you set. InterTest for CICS\nhalts the program before that statement executes and displays the following screen.\n CA InterTest for CICS - PROTSYM FILE  UNCOND  BEFORE BREAKPOINT         \n COMMAND ===>                                                                    \n Program= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n  _____ TASKNUM                         | +00001.                                \n ---------+--------------------------------------------------------------------- \n  _   639.1     1         IF TASKNUM > 2 THEN                                    \n  _   640.1     1            GOTO END_SESSION;                                   \n   U   ==>.1     1         IF TASKNUM = 1 THEN   \n  _   642.1     1            GOTO SENDSCR3;                                      \n  _   643.1     1         GOTO END_SESSION;   \n .\n .\n .                                          \n \nNotice the U to the left of the highlighted statement. The U identifies the breakpoint as an unconditional \"before\"\nbreakpoint. For an \"after\" breakpoint, the application displays a ).\n 488", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "db7a4d1b9f82-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nThe value of TASKNUM is now 1 because the TASKNUM = TASKNUM + 1 statement executed successfully.\nWhen you are stopped at a breakpoint, you have many choices. You can do the following tasks:\n\u2022Scroll or search through your source listing\n\u2022Examine and modify main and auxiliary storage\n\u2022Add a variable to the Keep window using the k line command\n\u2022Set and remove breakpoints\n\u2022Examine the program Backtrace Summary\n\u2022Abend your task (with or without a dump)\n\u2022Go around a problem by resuming program execution from another location (type G next to the instruction where you\nwant to resume)\nIn fact, a special Breakpoint Primary Option menu displays when you press PF6 Menu at a breakpoint. This menu makes\nit easy to choose a breakpoint activity to accomplish your testing goal. When debugging your own programs, you typically\nperform one or more of these activities, which are detailed in the next article. Since PL1DEMO has no more errors, the\ndemo session is complete.\nAs you continue testing and debugging, clean up by removing breakpoints that are not needed so that the program does\nit will not stop when you retest. Next, remove the unconditional breakpoint that you set so that PL1DEMO does not stop at\nthis statement when it re-executes.\n1.Overtype U with X to remove the breakpoint.\n CA InterTest for CICS - PROTSYM FILE  UNCOND  BEFORE BREAKPOINT         \n COMMAND ===>                                                                    \n Program= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n  _____ TASKNUM                         | +00001.                                \n ---------+--------------------------------------------------------------------- \n  _   639.1     1         IF TASKNUM > 2 THEN", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "db7a4d1b9f82-1", "text": "_   639.1     1         IF TASKNUM > 2 THEN                                    \n  _   640.1     1            GOTO END_SESSION;                                   \n  x   ==>.1     1         IF TASKNUM = 1 THEN                                    \n  _   642.1     1            GOTO SENDSCR3;                                      \n  _   643.1     1         GOTO END_SESSION; \n .\n .\n .                                          \n \n2.Press Enter.\nInterTest for CICS removes the unconditional breakpoint.\nRemove Breakpoints from the Status Display\nYou can also remove a breakpoint from the Status display:\n1.Type STATUS on the command line.\n2.Press Enter.\nInterTest for CICS displays the Monitoring Status screen.\n ---------------  CA InterTest for CICS  MONITORING STATUS ----------------\n  COMMAND ===>                                                                   \n  \n    Type + to expand or - collapse option levels displayed below,                \n 489", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4d14e44a7151-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n           or R to remove option(s).                                             \n  \n      Option     Description                Attributes                           \n  _ - PL1DEMO    Program monitor entry      PL/I                                 \n      |          Waiting at breakpoint      Task 00065, UBP since 12:10 p.m.     \n  _ - |-.ANY     User monitoring options    Active                               \n        |        Symbolic listing file      PROTSYM                              \n  r -   |-UBP    Unconditional breakpoint   #641                                 \n        |        Option ID                  8F7A1400                             \n        |        From, to terminals         U006, U006                           \n  _     |-SLB    Source listing breakpoints U006                                 \n                 *** End of data ***                                             \n  \n  \n  \n  PF1 Help       2 Refresh    3 End        4 Return     5 Collapse   6 Expand    \n  PF7 Backward   8 Forward    9           10           11           12         \n \n3.Type R to the left of the unconditional breakpoint (UBP) to remove it.\n4.Press Enter.\nAn asterisk appears next to the breakpoint, indicating that a command has been processed for it.\n5.Press PF2 to refresh the screen.\nThe unconditional breakpoint no longer displays.\n6.Press PF3 to return to the Source Listing Breakpoint screen.\nResume Program Execution\n1.Press PF5 to continue program execution.\nInterTest for CICS resumes program execution. PL1DEMO displays a screen confirming that you successfully\ncorrected the ASRA.\n2.Press Enter.\nPL1DEMO displays the following screen.\n     **********************************************************************      \n     ****                                                              ****      \n     ****                  CA InterTest Demo Session                   ****      \n     ****                                                              ****      \n     **********************************************************************", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4d14e44a7151-1", "text": "****                                                              ****      \n     **********************************************************************      \n  \n  \n     You have completed the sample CA InterTest test session. As part of this   \n     session, you:                                                               \n  \n        * displayed program source code and compiler output online               \n        * displayed and modified main storage                                    \n        * controlled program execution                                           \n  \n     This is just a fraction of CA InterTest's capabilities. You can also:      \n  \n        * display or modify any CICS file, or DL/1, DB2, or SQL/DS database      \n        * set and remove many kinds of monitoring options                        \n  \n  \n 490", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2ef74c41c226-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  \n          Press ENTER or CLEAR to complete the termination.                     \n  \n \nThis screen reminds you that we have touched on just a few of InterTest for CICS powerful, easy-to-use testing and\ndebugging facilities.\nTo complete this part of the sample test session, press Clear or Enter to clear your screen.\nWhat You Learned\nThe demo session has taught you the basics of using InterTest for CICS to test a program.\nYou have learned how to perform the following tasks:\nSelect a source program for display\nGo to ITST Menu Option 1.1. Select a program from the list.\nSet monitoring for a program\nUse the MONITOR command or PF5 from Source Listing.\nView a Monitoring Status display\nUse the STATUS command or PF12 from Source Listing.\nInterpret the information that the application provides when it detects an error\nView the Automatic Breakpoint and press PF1 for help.\nExamine the value of a data item in a Keep window\nView the data in the AutoKeep Display window\nModify main storage\nOvertype the value in the Keep Window or type D to the left of a variable. Place the cursor under the variable and\npress Enter for a CORE Main Storage display. On the CORE screen, overtype the values and press Enter.\nSet an uncondition\nal \"before\" breakpoint\nType U to the left of an instruction and press Enter.\nRemove a breakpoint from the Monitoring Status display\nUse PF12 to view Monitoring Status. Type R next to a UBP and press Enter.\nRemove a breakpoint from the Source Listing Display\nOn Source Listing, overtype U with X and press Enter.\nRemove a data item from a Keep window\nType X to the left of a Keep window entry and press Enter.\nResume program execution\nUse the RESUME command or PF5.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2ef74c41c226-1", "text": "Resume program execution\nUse the RESUME command or PF5.\nNow read the next article to learn how to use these and other basic InterTest for CICS functions to test your own\nprograms.\nPL/I Debugging Programs\nThis article provides an overview of key InterTest for CICS functions.\nFor complete information, see CICS Debugging,  and the Help facility.\n 491", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "476b978ec09b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBasic Debugging Tasks Checklist\nThe following list describes the debugging tasks:\n\u2022Display the source listing\n\u2022Set monitoring for the program\n\u2022Set breakpoints\n\u2022Set other monitoring options as needed\n\u2022Initiate the program\n\u2022End the test session\nWhen the program is stopped at a breakpoint, you can do the following tasks:\n\u2022Inspect and modify main storage\n\u2022Inspect and modify auxiliary storage\n\u2022Set and remove breakpoints\n\u2022Keep variables in the Keep window to observe changes in their values\n\u2022Resume execution\n\u2022Abend the task\nDisplay Your Source Listing\nYou can display your source listing online at any time from CICS through the ITST transaction or the LIST=progname\ntransaction (where program  is the program name). The Basic Demo explains how to display a source listing using the\nITST transaction. For additional information on how to use LIST=, see CICS Debugging.\nNOTE\n\u2022The standard InterTest for CICS transaction IDs, such as LIST, ITST, CORE, and FILE, could have been\nchanged at your site. If transactions mentioned in this article do not function as described, contact the person\nwho installed InterTest for CICS.\n\u2022Depending on your defaults, the options and PF keys available to you might not be displayed at the top of\nthe Source Listing Display. If this information is not displayed, you can view it by pressing PF4 to access the\nProfile screen, and then setting Display window to T.\nDisplay Sections of Your Program\nThe options (OPTS) available at the Source Listing screen make it easy to display any section of your PL/I program.\nHowever, all OPTS labels cannot be displayed at once. Tab to the More field and press Enter to view options not currently\ndisplayed.\nThe following table shows what program sections are displayed when you use the LOCATE command or option numbers:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "476b978ec09b-1", "text": "The following table shows what program sections are displayed when you use the LOCATE command or option numbers:\nCommand Option # Section\nL .DX 1 Data Name Cross Reference\nL .AG 2 Aggregate Length Table\nL .SR 3 Storage Registers\nL .SS 4 Static Storage Map\nL .VS 5 Variable Storage Map\nL .OF 6 Offsets\nL .GC 7 Generated Code (Assembler-like)\nL .EM 8 Error Messages\nL .PX 13 Procedure Cross-Reference\n 492", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "72e8a01dea31-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nL .LX 14 Label Cross-Reference\nSearch for Strings and Labels\nYou can also search for and display a character string by typing a FIND string NEXT/PREV command on the command\nline or option 9 (Search forward) or 10 (Search backward) in the Option # field and typing the character string in the\nSearch field. For example, the following screen shows how you would search backward for the string custname .\n CA InterTest for CICS - PROTSYM FILE SOURCE LISTING DISPLAY              \n COMMAND ===> f custname prev                                                   \n Program= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                \n ---------+---------------------------------------------------------------------\n  _                  CONTINUE_TASK:                                              \n  _                     MAPNUM  = '00';                                          \n  _    95  1  0     TASKNUM = TASKNUM + 1;                                       \n  _    96  1  0     IF TASKNUM > 2 THEN                                          \n  _                        GOTO END_SESSION;                                     \n  _    97  1  0     IF TASKNUM = 1 THEN                                          \n  _                        GOTO SENDSCR3;                                        \n  _    98  1  0     GOTO END_SESSION;\n \nStart a Test Session\nThis section describes how to start a test session.\nTurn on Monitoring\nTo test a program, you must instruct InterTest for CICS to monitor it. When InterTest for CICS monitors a program, it\ndetects and prevents errors before they occur, including the following violations:\n\u2022All storage violations\n\u2022All CICS abends\n\u2022Any statement that would cause a program check or other abend\n\u2022All illegal or invalid instructions that would cause CICS to crash\n\u2022All wild branches\n\u2022All violations of CICS standards", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "72e8a01dea31-1", "text": "\u2022All wild branches\n\u2022All violations of CICS standards\nThe easiest way to turn on monitoring is from the program source listing. Perform the following steps:\n1.Display the source listing as described in Display Your Source Listing. InterTest for CICS displays the Source Listing\nDisplay screen for the program.\n2.Press  PF5 to set monitoring, which remains in effect for the program until removed.\nExecute a Program\nOnce you have turned on monitoring for a program, you are ready to execute it. Perform the following procedure to\nexecute the program:\n1.Press PF3 to exit the Source Listing facility. If you entered Source Listing from an ITST menu, you are returned to that\nmenu.\n2.To exit the ITST menus, type =X in the top field and press Enter. The ITST transaction ends and you are returned to\nCICS.\n 493", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "034fe78839f0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nBefore you return to CICS, you might want to set breakpoints directly on the source listing. This process is\ndescribed in Set and Remove Breakpoints.\n3.On a clear CICS screen, type the transaction identifier of the program you are monitoring.\nWhen you type the program transaction ID, one of the following events occurs:\n\u2022Your program runs to completion. The results might not be correct.\n\u2022InterTest for CICS stops your program at a breakpoint -- either one set by you or one automatically triggered by\nInterTest for CICS because it detected an error.\nSet and Remove Breakpoints\nWhen you test a program, it is important to be able to halt program execution at specified locations. A halt in program\nexecution is called a breakpoint .\nWhat You Can Do at a Breakpoint\nWhen your program is stopped at a breakpoint, you can do the following actions:\n\u2022Examine the source listing\n\u2022Inspect and modify main storage\n\u2022Inspect and modify auxiliary storage\n\u2022Set and remove breakpoints\n\u2022Examine the backtrace\n\u2022Keep variables in the Keep window to observe changes in their values\n\u2022Set and remove monitoring options\n\u2022Specify indirect commands\n\u2022Resume execution\n\u2022Abend the task\nWe have already discussed how you can examine your source listing. The other breakpoint activities are discussed\nhere and the next article.\nTypes of Breakpoints\nPL/I programs have the following breakpoint types:\nAutomatic\nThe program stops because InterTest for CICS detected and prevented an error.\nUnconditional\nThe program stops at the location that you specify.\nConditional\nThe program stops at the location that you specify if a condition is met. Optionally, conditional breakpoints can be\nset to stop at any instruction if a condition is met.\nRequest", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "034fe78839f0-1", "text": "set to stop at any instruction if a condition is met.\nRequest\nThe program stops at every CICS command or macro, or at certain CICS commands or macros, or at calls to DL/\nI, DB2, or software.\nSingle-step\nThe program stops after executing one or more verbs.\n 494", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bec1b0e00312-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAn automatic breakpoint occurs when InterTest for CICS detects an error. When a program is stopped at an automatic\nbreakpoint, you can either correct the error, or you can go around the error. You can press PF1 to find out what caused\nthe error and how to use InterTest for CICS to fix it. You set all other breakpoints.\nIn this article, we explain how to set and remove unconditional  breakpoints. Unconditional breakpoints used the most. For\ninformation on conditional and request breakpoints, see PL/I Advanced Monitoring Features. Single-stepping is discussed\nin Resume Program Execution.\nThe next sections explain how to do the following tasks:\n\u2022Set breakpoints at statements on the source listing\n\u2022Set breakpoints at all references to a data name\n\u2022Set breakpoints at all or selected paragraph names or labels\nSet Unconditional Breakpoints at Statements on the Source Listing\nTo set an unconditional breakpoint on the program source listing, perform the following procedure:\n1.Enter U or ) in column 1 next to the statement where you want the breakpoint. The U sets a breakpoint that stops\nbefore  the statement is executed. The ) sets a breakpoint that stops after the statement is executed.\n2.Press Enter.\nThe following screen shows how to set a \"before\" breakpoint.\n CA InterTest for CICS - PROTSYM FILE  SOURCE LISTING DISPLAY            \n COMMAND ===>                                                                    \n Program= PL1DEMO  Option #      Stmt #                             Margin= 01  \n                                         Search=                        \n OPTS 1 Data xref 2 Aggregate 3 Stor reqs  4 Stat stor  5 Var stor   More:   +   \n      6 Offsets   7 Gend code 8 Err msgs   9 Srch fwd  10 Srch bwd", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bec1b0e00312-1", "text": "PFKS 1 Help      2           3 End        4 Profile    5 Monitor    6 Menu      \n      7 Backward  8 Forward   9 Next Wnd  10           11           12 Status    \n ---------+--------------------------------------------------------------------- \n  _   637.1               MAPNUM  = '00';                                        \n  _   638.1     1         TASKNUM = TASKNUM + 1;                                 \n  _   639.1     1         IF TASKNUM > 2 THEN                                    \n  _   640.1     1            GOTO END_SESSION;                                   \n  u   641.1     1         IF TASKNUM = 1 THEN                                    \n  _   642.1     1            GOTO SENDSCR3;                                      \n  _   643.1     1         GOTO END_SESSION;  \n .\n .\n .                                          \n \nAfter you set a breakpoint, InterTest for CICS redisplays the screen with an uppercase U or a ). This character remains\nuntil you remove the breakpoint.\nYou can set breakpoints at any time; either before executing the program or when the program is stopped. Although\nwhere you decide to set breakpoints depends on the specifics of your program, you might want to set breakpoints:\n\u2013At the beginning of the program, so when the program executes you can set more breakpoints\n\u2013At labels, so you can examine the contents of variables at the start of sections\n\u2013Before a CALL, so you can dynamically control the program path\n\u2013At each location named in an EXEC CICS HANDLE CONDITION, so you can verify error handling\nTo remove  an unconditional breakpoint, overtype the U with an X, or type an R next to the breakpoint entry on the\nMonitoring Status display (PF12 from Source Listing). Remove breakpoints which are no longer needed so that you", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bec1b0e00312-2", "text": "Monitoring Status display (PF12 from Source Listing). Remove breakpoints which are no longer needed so that you\nare not stopped when retesting the program.\n 495", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "58ce080a0d35-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSet Unconditional Breakpoints from Cross-Reference Sections\nThe Cross Reference sections of the PL/I listing allow you to set many breakpoints at once. You can set unconditional\nbreakpoints from the sections in the listing:\n\u2022Data Name Cross Reference Table (L .DX or Option 1)\n\u2022Procedures Cross-Reference (L .PX or Option 13)\n\u2022Labels Cross-Reference (L .LX or Option 14)\nTo display a section, type the command on the command line or the number in the Option # field on the Source Listing\nscreen, as shown next, and press  Enter.\n CA InterTest for CICS - PROTSYM FILE  SOURCE LISTING DISPLAY            \n COMMAND ===> l .dx                                                              \n Program= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ---------+--------------------------------------------------------------------- \n  _   636.1            CONTINUE_TASK:                                            \n  _   637.1               MAPNUM  = '00';                                        \n  _   638.1     1         TASKNUM = TASKNUM + 1;                                 \n  _   639.1     1         IF TASKNUM > 2 THEN                                    \n  _   640.1     1            GOTO END_SESSION;                                   \n  U   641.1     1         IF TASKNUM = 1 THEN                                    \n  _   642.1     1            GOTO SENDSCR3;                                      \n  _   643.1     1         GOTO END_SESSION;   \n .\n .\n .                                          \n \nInterTest for CICS displays the Data Name Cross Reference Table section, as follows.\n CA InterTest for CICS - PROTSYM FILE  SOURCE LISTING DISPLAY            \n COMMAND ===>", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "58ce080a0d35-1", "text": "COMMAND ===>                                                                    \n Program= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n --------------+---------------------------------------------------------------- \n  u                     ATTRIBUTE/XREF TABLE-                                    \n         LINE.FILE IDENTIFIER                      ATTRIBUTES                    \n          515.1    ADDR                            BUILTIN                       \n                                                   Refs: 252.1 252.1 252.1 361+  \n                                                         389.1 402.1 409.1 416+  \n                                                         423.1 430.1 437.1 444+  \n                                                         451.1 458.1 468.1 478+  \n                                                         485.1 492.1 499.1 509+  \n                                                         525.1 528.1 529.1 530+  \n                                                         531.1 532.1 533.1 534+  \n                                                         556.1 558.1 568.1 570+  \n                                                         570.1 583.1 585.1 591+  \n                                                         593.1 593.1 608.1 610+  \n                                                         610.1 619.1 621.1 621+  \n                                                         621.1 627.1 629.1 651+  \n                                                         653.1 653.1 653.1 660+  \n                                                         662.1 673.1 675.1 675+  \n                                                         675.1 686.1 688.1 688+  \n 496", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0faaf348e393-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                                         696.1 698.1 707.1 709+\n \nSetting Unconditional Breakpoints at All Procedures and All Labels\nTo set unconditional breakpoints at all Procedure Names and All Labels, display the Cross Reference table using Option\n# 1 (or L .DX command), type U or ) next to the \"ATTRIBUTE/XREF TABLE\" heading line and press Enter. A message\nprompts you to confirm the request for setting many breakpoints by pressing PF3.\nTo set breakpoints at all Procedure names only, go to the Procedures Xref section using Option # 13 (or L .PX command),\nand then type U or ) next to the \"PROCEDURE ATTRIBUTE/XREF TABLE\" header line and press Enter.\nTo set breakpoints at all Labels only, display the Labels Cross Reference section using Option # 14 (or L .LX command),\nand then type a U or ) next to the \"LABEL ATTRIBUTE/XREF TABLE\" header line and press Enter.\nYou can remove all of these breakpoints at once by typing an X on the appropriate heading line and pressing Enter. You\ncan also remove these breakpoints individually from the Status display (type R next to an entry) or from one of the Cross\nReference Sections of the Source Listing (type X).\nSetting Unconditional Breakpoints at Data Items\nFrom the Data Name Cross Reference Table section (Option 1) you can also set breakpoints next to individual data items.\nDisplay the section, scroll forward using PF8, and type U or ) next to the data item.\nYou can remove  the breakpoints from either the Source Listing display (overtype the U or ) with X) or the Status display\n(type R next to the breakpoint entry).\nInspect and Modify Main Storage\nThe ability to inspect main storage at a breakpoint lets you determine the values of variables without using a dump. You", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0faaf348e393-1", "text": "can easily find logic errors because you can display the value of a variable where the variable is defined, and at any point\nin the code where the variable is referenced. You can also dynamically change the variable value to correct errors or test\nother program paths.\nRemember that changes to program storage are dynamic and the change affects only the current test session. To correct\nprogram errors, you must change the source code and recompile the program.\nThere are many ways to inspect and modify main storage. We are going to discuss one of the easiest methods of viewing\nand changing program storage here. Keep Variables in the Keep Window explains another easy way to display and\nmodify the values of variables.\nRemember, you can inspect system storage at any time, independent of program monitoring and execution.\nDisplay the Value of a Variable\nWhen you are stopped at a breakpoint, you can request the display of a variable value directly from the source listing.\n1.To display the value of a variable where the variable is defined , type D to the left of the statement that defines the\nvariable and press Enter, as shown in the following screen.\n CA InterTest for CICS - PROTSYM FILE  UNCOND  BEFORE BREAKPOINT         \n COMMAND ===>  \n Program= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n  _____ DMAP00O.DFHMS9                  | ............                           \n ---------+--------------------------------------------------------------------- \n  _   514.1                     UNSPEC, SUBSTR,                                  \n  _   515.1                     LENGTH, ADDR)      BUILTIN;                      \n 497", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f9c528d38867-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  _   516.1     1      DCL 1 TS_AREA,                                            \n  _   517.1                  2 TS_SWITCH           CHAR(1),                      \n  d   518.1                  2 TASKNUM      FIXED DEC(5),                        \n  _   519.1                  2 TS_TEXT             CHAR(32);                     \n  _   520.1     1      DCL   (TS_ITEM,TS_LEN)      FIXED BIN(15,0);              \n  _   521.1     1      DCL   REC_RBA               CHAR(4) INIT('    ');  \n .\n .\n .\n \n2.To display the value of a variable where the variable is referenced , type D to the left of the statement that references\nthe variable, place the cursor under any character in the variable, and press Enter.\nInterTest for CICS responds by displaying the contents of the variable in structured format, as shown next.\n CA InterTest for CICS - MAIN STORAGE UTILITY - Termid = U057        \n  \n Starting at Address =20304231         Structure Display Format                  \n  02 TASKNUM                         | ?00000.                    |              \n  02 TS_TEXT                         | ............               |              \n                                     | ............               |              \n                                     | ........                   |              \n  \n  \n  \n  \n  \n  \n  \n  ------------------------------------------------------------------------------ \n  PF1 Help       2            3 End        4 Return     5            6 Dump      \n  PF7 Backward   8 Forward    9 Caps Off  10           11 Redisplay 12 Structure \n  CORE='TASKNUM'                                                                 \n  CAIN0478 AUTOMATIC DECIMAL FIELD CONTAINS INVALID PACKED DATA                 \n \nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f9c528d38867-1", "text": "NOTE\nInterTest for CICS displays more than just the contents of the specified variable (TASKNUM); it also displays\nall the items below it in the same PL/I structure.\n3.Press Clear or PF3 to return to the source listing.\nModify the Value of a Variable\nYou can modify the value of a variable by over typing the bytes in the main storage display and pressing Enter. For\nexample, you could change the contents of TASKNUM in the previous figure by overtyping the question mark (Indicating\nthat the field contains an invalid value for its type), with a 0 and hitting EOF (Erase to end of field).\nModify the Value of a Variable with the MOVE Statement\nOvertyping the main storage display is the easiest way to change the value of a variable. However, you want to use the\nInterTest for CICS generated MOVE statement to modify a variable when you do not know the type of data (For example,\nbinary or packed) or the length. The MOVE statement takes care of all the details for you.\n1.To modify a variable where the variable is defined, type M to the left of the statement that defines the variable, and\npress Enter. For example, to modify the value of TASKNUM, type M instead of D.\n2.If you type  M to the left of multiple lines, InterTest for CICS generates multiple MOVE statements.\n 498", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "be5ed8dec33c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n3.To modify a variable where the variable is referenced, type M to the left of the statement that references the variable,\nplace the cursor under any character in the variable, and press Enter.\nInterTest for CICS generates and displays a fill-in-the-blanks MOVE statement, which is shown in the following\nexample.\n CA InterTest for CICS - PROTSYM FILE  UNCOND  BEFORE BREAKPOINT         \n COMMAND ===>                                                                    \n Program= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n  _____ DMAP00O.DFHMS9                  | ............                           \n ---------+--------------------------------------------------------------------- \n  \n MOVE ________________________________________________________________           \n  \n  to                                                                             \n  \n      TASKNUM                                                                    \n  \n Overtype Underscores with a Data-Name, Figurative Constant,                     \n Alphanumeric Literal, or Numeric Literal                                    \n \n4.Type one of the following values in the MOVE field:\n\u2013A variable name, such as NEXT_TASKNUM\n\u2013One of the following keywords: ZEROS, SPACES, LOW-VALUES, HIGH-VALUES, QUOTES\n\u2013An alphanumeric literal enclosed in single quotes, such as 'YES'\n\u2013A numeric literal, with or without a leading plus, +, or minus sign, -, such as -8.\n5.Press Enter to execute the MOVE statement.\nInterTest for CICS displays a main storage display showing the new value of the variable. If you execute several\nMOVE statements, InterTest for CICS shows the main storage displays one-at-a-time. Press Clear to see the next one.\n6.From the main storage display, press Clear or PF3 to return to the source listing.\nKeep Variables in the Keep Window", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "be5ed8dec33c-1", "text": "Keep Variables in the Keep Window\nThe Keep window lets you display the values of an unlimited number of data items directly on the source listing. If more\nthan six variables are selected for the Keep window, PF19 and PF20 are available to scroll forward and backward through\nthe Keep window. Keeping data items in the window lets you observe changes in their values as the program executes.\nYou also can change values by overtyping the displayed bytes.\nThe Keep window consists of two parts:\n\u2022Dynamic  keep elements consist of the variables based on the current line of code. They are automatically displayed\nusing the AutoKeep Display profile feature. They are shown in highlighted text.\n\u2022Static  keep elements are elements that remain in the Keep window during the execution of the program until you\nremove them. The static  keep elements are displayed before the dynamic  elements. Use scrolling to view all the\nelements.\nYou can change any dynamic  element to a static  element simply by following these rules:\nWhen the Keep window is active, the options and PF key functions are not displayed. Press PF4 to refer to the functions.\nWhen all the data items in the Keep window are removed, the options and PF key functions are redisplayed. A command\nline is available to help you perform InterTest for CICS functions when the Keep window is active.\n 499", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8c8737568b0c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAdd a Variable to the Keep Window (static keep element)\nYou can add variables to the Keep window whenever your source listing is displayed. Identify the variables values that you\nwant to observe either before you execute the program, or when you are at a breakpoint.\nFollow these rules to add a variable to the Keep window:\n\u2022To add a variable where the variable is defined , type K to the left of the statement that defines the variable, and press\nEnter.\n\u2022To add a variable where the variable is referenced , type K to the left of the statement that references the variable,\nplace the cursor under any character in the item, and press Enter.\nWhen you add a variable to the Keep window, InterTest for CICS responds by displaying the first 12 bytes of the variable\nin hexadecimal and character format. This display is shown in the following example.\n CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \n COMMAND ===>                                                                    \n Program= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n  _____ EIBTRNID                        | DEMP                                   \n  _____ EIBTRMID                        | U057                                   \n  _____ TASKNUM                         | ?00000.                                \n ---------+--------------------------------------------------------------------- \n  _   636.1            CONTINUE_TASK:                                            \n  _   637.1               MAPNUM  = '00';                                        \n  A   ==>.1     1         TASKNUM = TASKNUM + 1;                                 \n  _   639.1     1         IF TASKNUM > 2 THEN                                    \n  _   640.1     1            GOTO END_SESSION;                                   \n  _   641.1     1         IF TASKNUM = 1 THEN", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8c8737568b0c-1", "text": "_   641.1     1         IF TASKNUM = 1 THEN                                    \n  _   642.1     1            GOTO SENDSCR3;                                      \n  _   643.1     1         GOTO END_SESSION;   \n .\n .\n .\n \nDisplay Variable Structure\nTo display the entire PL/I structure of a variable, type D to the left of the variable in the window and press Enter.\n CA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \n COMMAND ===>                                                                    \n Program= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n  _____ EIBTRNID                        | DEMP                                   \n  _____ EIBTRMID                        | U057                                   \n  d____ TASKNUM                         | ?00000.                                \n ---------+--------------------------------------------------------------------- \n  _   636.1            CONTINUE_TASK:                                            \n  _   637.1               MAPNUM  = '00';                                        \n  A   ==>.1     1         TASKNUM = TASKNUM + 1;                                 \n  _   639.1     1         IF TASKNUM > 2 THEN                                    \n  _   640.1     1            GOTO END_SESSION;                                   \n 500", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e26c46c839f8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  _   641.1     1         IF TASKNUM = 1 THEN                                    \n  _   642.1     1            GOTO SENDSCR3;                                      \n  _   643.1     1         GOTO END_SESSION;   \n .\n .\n .                                   \n \nInterTest for CICS responds by displaying the variable and all the items below it in the same structure.\nModify the Value of a Variable\nModify the value of a variable in the Keep window by performing the following procedure:\n1.Overtype the displayed bytes, as you would overtype the bytes in a main storage display\n2.Type M to the left of the variable to use the InterTest for CICS MOVE statement. Both methods of modifying a variable\nare discussed in Inspect and Modify Main Storage.\nNOTE\nIf you try to change password protected storage areas not owned by your program, InterTest for CICS\nprompts you to enter the password.\nRemove a Variable from the Keep Window\nTo remove a variable from the Keep window, type X to the left of the variable. In this example, two variables (EIBTRNID\nand EIBTRMID) are removed from the Keep window.\n CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \n COMMAND ===>                                                                    \n Program= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n ------------------------------------------------------------------------------- \n  x____ EIBTRNID                        | DEMP                                   \n  x____ EIBTRMID                        | U057                                   \n  _____ TASKNUM                         | ?00000.                                \n ---------+--------------------------------------------------------------------- \n  _   636.1            CONTINUE_TASK:                                            \n  _   637.1               MAPNUM  = '00';", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e26c46c839f8-1", "text": "_   637.1               MAPNUM  = '00';                                        \n  A   ==>.1     1         TASKNUM = TASKNUM + 1;                                 \n  _   639.1     1         IF TASKNUM > 2 THEN                                    \n  _   640.1     1            GOTO END_SESSION;                                   \n  _   641.1     1         IF TASKNUM = 1 THEN                                    \n  _   642.1     1            GOTO SENDSCR3;                                      \n  _   643.1     1         GOTO END_SESSION;\n \nWhen all variables are removed, the Keep window no longer displays. If your Profile had Display window set to T, the\nOption and PF key title lines are re-displayed.\nWork with Arrays and Qualified Variables\nThis release let you view or modify the following items:\n\u2022Array elements, both structured and non-structured\n\u2022Qualified variables within a procedure, block, or program with up to 15 levels of qualification\n 501", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "92a2e1288108-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nArray Elements\nYou can view or change elements of arrays that are up to 15 dimensions deep.\nNOTE\nArrays with unknown boundaries at compile time are not supported.\nWhen you use the D or K line commands from Source Listing, place the cursor under the element and InterTest for CICS\nautomatically picks up the dimensions.\nWhen you are entering an array element for a formatted move command, or CNTL or CORE command, use the syntax:\n FIELDA(A,B,C)\n \nTo modify the storage of an array element using a CORE command, use the syntax:\n CORE=MOVE 1 TO 'FIELDA(A,B,C)'\n \nQualified Variables\nYou can view or change elementary variables, even if they are defined as the same name in different procedures or\nblocks, using qualified variable syntax in a CNTL or CORE command or Source Listing Search criteria.\n CORE=MOVE 1 to 'procname:Q1.Q2.Q3.Q4.Q5.Q6.Q7'\n \nIf you are using the M line command from the Source Listing facility and select a non-unique variable, the generated\nMOVE command qualifies the selected variable with the Procedure name.\nInspect and Modify Auxiliary Storage\nYou can use InterTest for CICS to inspect and modify the following storage:\n\u2022VSAM and BDAM files\n\u2022DL/I, DB2, and SQL/DS databases\n\u2022Temporary storage\n\u2022Transient data\nYou can inspect and modify auxiliary storage at any time, regardless of whether a program is executing. This capability\nlets you maintain files and databases without writing one-time programs. You can perform any VSAM, BDAM, or DL/I\nfunction and most SQL functions. The ability to inspect and modify auxiliary storage when a program stops at a breakpoint", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "92a2e1288108-1", "text": "lets you change test data in the middle of a test session. Changes are permanent and changes to the file remain after the\ntest session ends.\nInspect Auxiliary Storage\n1.To access the auxiliary storage facility, select 4 Auxiliary storage from the InterTest for CICS Primary Option Menu, and\nthen specify the file that you want to examine on the Auxiliary Storage Menu.\n -----------------  CA InterTest for CICS AUXILIARY STORAGE MENU  ------------------\n OPTION  ===> 1                                                                \n  \n     Select an auxiliary storage type, specifying optional criteria below.      \n  \n     1  Files              - Display/select files for access                     \n     2  DB2 database       - Invoke DB2 SQL interface facility                   \n     3  DL/I database      - Access DL/I database                                \n 502", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "35ef59e180a7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n     4  TD queues          - Display/select transient data queues for access     \n     5  TS queues          - Display/select temporary storage queues for access  \n  \n     Type specific or generic file/queue name(s):                                \n        (Valid mask characters are  *  and/or  +)                                \n  \n     file____ ________ ________ ________ ________ ________ ________ ________\n .\n .\n .\n \n2.Alternatively, if you are at a clear CICS screen, you can invoke the FILE transaction.\nInterTest for CICS displays the following screen:\n DATATYPE= FC FILEID=          MODE=      LOG=ON  TODEST=         PASSWORD=     \n FUNC=      SUBFUNC=      RETMETH=        ARGTYP=     SRCHTYP=                   \n MESSAGE=                                                                        \n  RETNRCID=                                                         CHGLEN=      \n     RCID=                                                                       \n     DATA=                                                          SIZE= 0000   \n FORMAT= D 00112233 44556677 8899AABB CCDDEEFF  *0123456789ABCDEF*              \n LOC 0000  ........ ........ ........ ........  ................               \n  \n  \n                       CA InterTest for CICS  \n  \n                 Copyright \u00a9 SOLVE:Access  CA. All rights reserved.                                        \n  \n  \n  \n  \n -------------------------------------------------------------------------------\n 1 Help       2 Format C   3 End        4 BEGB       5            6 DataType DL \n 7 Page bwd   8 Page fwd   9 Caps Off  10 Top       11 Bottom    12\n \nNOTE\nIf the FILE transaction does not display the previous screen, it is probably because the person who installed", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "35ef59e180a7-1", "text": "If the FILE transaction does not display the previous screen, it is probably because the person who installed\nInterTest for CICS changed the name of the FILE transaction. Contact that person to find out the correct\nname.\nAfter you enter the file or database and, optionally, the record or segment, InterTest for CICS displays the data. A\nsample VSAM record in dump format follows.\n  DATATYPE= FC FILEID= INVNTRY   MODE=     LOG=OFF  TODEST=        PASSWORD= \n  FUNC=     SUBFUNC=      RETMETH=        ARGTYP=    SRCHTYP=                    \n  MESSAGE= RECORD OBTAINED FOR VIEWING                                            \n   RETNRCID=F0F0F0F0F0F0F0F0F5                                     CHGELEN=       \n      RCID=C`000000005'                                                           \n      DATA=                                                        SIZE= 0050     \n  FORMAT= D 00112233 44556677 8899AABB CCDDEEFF *0123456789ABCDEF*                \n  LOC 0000  ........ ........ ........ ........ ................                \n    0000    F0F0F0F0 F0F0F0F0 F0F54040 0087338F   0000000005       DSORG=VSKS     \n    0010    F0F3F9F9 0407835C 40404040 40404040   0399....        RECFM=VB       \n    0020    40404040 40404040 C1C2C340 C3D6D9D7           ABC CORP  LRECL=0050   \n 503", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3a0e5cbf8bb6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    0030    F0F9F1F2 F8F74040 0000598C 40404040   091287           BLKSIZE=0000   \n    0040    D1D6C3D5 404040E2 D4C9E3C8 40404040   JOHN  SMITH      KEYPOS=0000    \n    0050                                                           KEYLEN=0A      \n    0060                                                           STRNO=01       \n    0070                                                                          \n    0080                                                           READ           \n    0090                                                           ADD            \n    00A0                                                           UPDATE         \n  -------------------------------------------------------------------------------  \n  1 Help       2 Format C   3 End        4 BEGB       5 PREV      6 DataType DL   \n  7 Page bwd   8 Page fwd   9 Caps Off  10 Top      11 Bottom    12              \n \nNOTE\nThe data appears in both hexadecimal and character format.\n3.To return to the source listing, press Clear or PF3.\nModify Auxiliary Storage\n1.To modify the record or segment, overtype the hexadecimal or character data and press Enter. For example, you could\novertype JOHN SMITH with DALE COOPER on the sample display in the previous figure.\n2.To rewrite the modified record, type PUT in the FUNC= field and press Enter.\nDisplay Auxiliary Storage in Structured Format\nInterTest for CICS can display file, transient data, and temporary storage records or DL/I segments field-by-field in\nstructured format using 01 level data names.\nTo display a record or segment in structured format, you must identify the program containing the structure. Symbolic\ninformation for this program must be saved in the InterTest for CICS Symbolic File.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3a0e5cbf8bb6-1", "text": "information for this program must be saved in the InterTest for CICS Symbolic File.\nPerform the following steps to display a record or segment in structured format:\n1.If the FORMAT field does not contain S, press PF2 until FORMAT= S appears. The USE=field now appears after the\nFORMAT field.\n2.Identify the program and structure in the USE= field. Specify the command as follows:\n USE=symbolic-name.structure-name\n \nsymbolic-name   is the name of the program as defined in the InterTest for CICS Symbolic File\nstructure-name   is the PL/I 01 level name\n3.Press Enter.\nInterTest for CICS displays the record or segment in structured format. A sample VSAM record in structured format\nappears next.\n  DATATYPE= FC FILEID= INVNTRY  MODE=      LOG=OFF TODEST=        PASSWORD= \n  FUNC=      SUBFUNC=      RETMETH=        ARGTYP=    SRCHTYP= \n  MESSAGE= RECORD OBTAINED FOR VIEWING \n   RETNRCID=F1D7D9D6E3E2E8D440000000000000000000000000000000       CHGELEN= \n      RCID= C'1' \n      DATA=                                                        SIZE= 02D8 \n  FORMAT= S USE= PRODUCT.PRODREC \n  LOC 0050           Name                      Hexadecimal           Character \n  ------------------------------------------------------------------------------- \n   01 PRODREC                          |                           |\n   02 PRODUCT-TYPE                     | D3                        | L\n 504", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4e0acab290fe-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n   02 PRODUCT-CODE                     | C2D4D5C8 40404040         | BMNH \n   02 PRODUCT-DESCRIPTION              | E6D9C5D5 C3C8             | WRENCH\n   02 PRODUCT-SITE                     | D1                        | J \n                                       |                           |\n                                       |                           |\n  ------------------------------------------------------------------------------- \n  1 Help       2 Format D   3 End        4 BEGB       5           6 DataType DL \n  7 Page bwd   8 Page fwd   9 Caps Off  10 Top      11 Bottom    12\n \n4.Structured format lists the contents of each data name in both hexadecimal and character format. To modify the record\nor segment, overtype either the hexadecimal or character data and press Enter. To rewrite the modified record, type\nPUT in the FUNC= field and press Enter.\n5.When a program is stopped at a breakpoint, you can substitute an asterisk ( *) for the symbolic-name. For example, if\nprogram PAYROLL is stopped at a breakpoint and you type:\n USE=*.payrec\n \nInterTest for CICS uses the program named PAYROLL and the PAYREC structure.\n6.To begin the structure with a specific data name, specify the following command in the DATA field:\n FIND=data-name\n \nWhere data-name   is the data name to be displayed.\nResume Program Execution\nAfter you perform breakpoint activities, such as displaying and modifying main or auxiliary storage, you can resume\nprogram execution. Perform the following procedures:\n1.Resume execution from a specific location\n2.Single-step execution one verb at a time\nSee the End a Test Session for information on the status of your program after it completes execution.\nResume Execution from a Specific Location", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4e0acab290fe-1", "text": "Resume Execution from a Specific Location\nTo resume program execution from the breakpoint location where your program stops, the Source Listing screen must\ndisplay.\n1.Press PF3 from any InterTest for CICS screen until the breakpoint screen appears.\n2.Press PF5 to continue from the current breakpoint. You can also type RESUME on the Command line and press Enter.\nExecution continues until the program halts at another breakpoint or the task completes.\nIf you are stopped at an automatic  breakpoint, you must first correct the error that triggered the breakpoint before\ncontinuing execution from that point. You can also go around the error and continue execution from another location.\nTo resume program execution from another location, perform the following steps:\n1.Display the statement where you want to resume execution. For details, see Display Your Source Listing.\n2.Type G to the left of that statement.\n3.Press Enter. Program execution resumes from that statement.\nThe following example shows how to resume execution from a location prior to an automatic breakpoint. This action\nis useful if you corrected a record or dynamically modified an incorrect file name and want the program to re-read the\nrecord or file.\n CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \n COMMAND ===>                                                                    \n Program= PL1DEMO  Option # 9     Stmt #                             Margin= 01  \n 505", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5345a598dbd9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                        Search= READATA                         \n ------------------------------------------------------------------------------ \n _____ TASKNUM                         | ?00000.                                \n --------+--------------------------------------------------------------------- \n _  1308.1     1             GOTO SENDMP00;                                     \n _  1309.1                                                                      \n g  1310.1     1      READATA:                                                  \n _  1311.1                   /* EXEC CICS HANDLE CONDITION  DSIDERR             \n _  1312.1                                                  ERROR    (GENERR)   \n _  1313.1                                                  NOTOPEN  (NOPEN) *  \n _  1314.1                   DO;    \n .\n .\n .\n \n4.When you press Enter, execution resumes from READ-DATASET, the location you identified with G.\nSingle-Stepping\nSingle-stepping lets your program execute one COBOL verb and then stop again. You can adjust the step amount so that\nthe program executes a specified number of verbs between stops.\nTo single-step, type NEXT in the command line and press Enter or press PF10 from the source listing.\nYour program executes the next verb and then stops.\nUse the following procedure to single-step from a different program location:\n1.Display the statement where you want to resume execution. For details, see Display Your Source Listing.\n2.Type G to the left of that statement.\n3.Type NEXT in the command line and press Enter or press PF10.\nTo adjust the step amount, perform the following steps:\n1.Press PF4 to access the Source Listing Profile screen.\n2.Change the number in the Stepping amount field.\n3.Press Enter.\nInterTest for CICS changes the step amount and redisplays the source listing. If Titles are set to on (an option on the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5345a598dbd9-1", "text": "Source Listing Profile screen), the new step amount appears next to PF10 at the top of the Source Listing Breakpoint\nscreen.\nAbend a Task\nWhen your program is stopped at a breakpoint, you can abend your task rather than resume execution.\n1.Type ABEND (or, =3) in the Command line of any Breakpoint display.\nInterTest for CICS displays the following screen.\n ----------------- CA InterTest for CICS ABEND BREAKPOINTED TASK  -------------------\n COMMAND ===>                                                                   \n  \n     Type an abend code, then press ENTER.                                      \n  \n  \n     Abend Code  ____   Abend code options are:                                  \n  \n                        blanks        Normal abend, no dump                      \n 506", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3b75e77ba7ea-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                        XXXX          Abend exits cancelled, no dump             \n                        your code     Your abend code, dump taken                \n  \n .\n .\n .\n \n2.To cancel the abend, press PF3.\nInterTest for CICS redisplays the Primary Option Menu.\n3.To abend without  a dump:\na.For a normal abend, press Enter.\nb.To cancel all program exits, specify code XXXX and press Enter.\n4.To abend with a dump, specify a four-character dump code and press Enter. The dump code that you specify cannot\nbe XXXX and cannot begin with the letter A.\nFor information on the status of your program after abending, see End a Test Session.\nGet Help\nHelp is always available when you are using InterTest for CICS. You can also use Help to initiate InterTest for CICS. Type\nHelp on a clear screen under CICS.\nGet Help in Using InterTest for CICS\nWhen you are using InterTest for CICS, you can press PF1 at any time for information about InterTest for CICS functions.\nFor example, the following screen lists the Help topics for the Source Listing facility.\n               CA INTERTEST - INTERACTIVE HELP FACILITY -        \n TUTORIAL: SOURCE LISTING FACILITY - FOR PL/I PROGRAMS                          \n  \n  \n  05  Set Monitoring                    45  Set/Remove other monitoring Options  \n  10  Locating areas in the listing     50  Displaying data items                \n  20  Search for a Character string     55  Modify the value of data items       \n  25  Setting Indirect Commands         60  Resume TASK execution                \n  30  PF key definitions                65  Abending your TASK", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3b75e77ba7ea-1", "text": "30  PF key definitions                65  Abending your TASK                   \n  32  Primary/Line Commands             70  PROFILE, AUTOSTEP, AUTOKEEP Options  \n  35  Set the Display Margins           75  Code Coverage Option                 \n  40  Set/Remove Breakpoints            80  View Program Backtrace               \n  \n  \n  \n  \n                                                                           (end)\n  ------------------------------------------------------------------------------\n ENTER A SELECTION CODE FROM THE MENU, OR N FOR NEXT PAGE, P FOR PRECEDING PAGE, \n  M FOR RETURN TO PREVIOUS MENU,  CLEAR TO EXIT, OR MESSAGE NUMBER. ==> 05     \n \nHelp for Line Commands\nNote that selection code 32 lists Line Commands. These are the simple commands that you can enter on the Command\nline of a Source Listing Display, Breakpoint Display, or SymDump  Breakpoint display, and include the commands abend,\nmonitor, and status.\n 507", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "03fef96fe295-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nGet Help to Correct an Error\nWhenever your program stops at an automatic breakpoint, InterTest for CICS displays a short message identifying the\nreason for the breakpoint. You can request help by pressing PF1 for information on what caused the error that triggered\nthe breakpoint and how to fix it. The following screen explains how to correct an AEIL abend.\n              CA INTERTEST - INTERACTIVE HELP FACILITY -       \n TUTORIAL: ERROR MESSAGE AEIL                                                   \n  \n  The dataset name referred to in the DATASET option cannot be found in the FCT.\n  Your program did not have a Handle Condition for this error. Or a second Handle\n  Condition without a routine for this error superseded the one that had a       \n  routine for this error.                                                       \n  \n  WHAT YOU CAN DO: If the named file was entered incorrectly and the one you     \n  wanted exists, you may use the Replace File Option to dynamically replace the  \n  file name and then use the resume task facilities to execute the CICS request  \n  again. To perform the above functions from the Source Listing Breakpoint screen\n  you would:                                                                     \n  \n  1. Key =20s in the Option # field and press ENTER.                            \n  2. Tab to  Replace file name:   Key in the incorrect file name.               \n  3. In the next field, key in the correct file name and press ENTER.           \n  4. Press CLEAR  to return to your Source Listing Breakpoint screen.           \n  5. Key in G to resume execution at the beginning of the EXEC CICS command      \n     and press ENTER.                                                           \n                                                                     (continued)\n  ------------------------------------------------------------------------------\n ENTER N FOR NEXT PAGE, P FOR PRECEDING PAGE, F FOR FIRST PAGE, OR -", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "03fef96fe295-1", "text": "M FOR RETURN TO PREVIOUS MENU,  CLEAR TO EXIT, OR MESSAGE NUMBER. ==> N\n \nNOTE\nWhen you leave and then return to an automatic breakpoint screen, the error message may no longer appear.\nFor help on the cause of the error, press Clear to redisplay the error message before pressing PF1.\nEnd a Test Session\nAfter your program completes execution or you abend your task, you are returned to CICS.\nThe following table shows the status of your program after testing:\nProgram Area Status after Testing\nprogram source code not modified\nfile/database updates by the program permanent\nfile/database updates that you made permanent\nInterTest for CICS monitoring, breakpoints, and other options set for the program remain in effect until they are removed.\nCorrect the Source Code\nAt some point, you might want to correct the source code and continue testing from a clean version of the program.\nAfter you modified the source code and recompiled the program, you can load the new copy of the program by using the\nNew Program Copy option on the Program Monitoring menu (ITST 2.1). The New Program Copy option resets symbolic\n 508", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a6ff29a0e591-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nbreakpoints and other monitoring options for the recompiled programThe option also resets the PPT entry to the new\nprogram library address.\nPL/I Advanced Monitoring Features\nUse InterTest for CICS advanced features to help you detect and correct errors.\nWhatever your specific testing needs, InterTest for CICS has the necessary tools.\nThis article describes just a few of the more commonly used features. For information about all InterTest features, see\nCICS Debugging and the Help facility.\nSet Options from the Monitoring Menus\nThe monitoring menus of InterTest are the easiest way to set many monitoring options.\n1.Access these menus from the Primary Option Menu by selecting 2 Monitoring:\n-------------- CA InterTest for CICS PRIMARY OPTION MENU  ----------------\nOPTION  ===> 2                                                                 \n                                                                                \n    1  Source             - Display/select program source files/listings        \n    2  Monitoring         - Display/modify CA InterTest monitoring/activity   \n    3  Main storage       - Display/modify CICS storage areas                   \n    4  Auxiliary storage  - Display/access databases/files/queues               \n    5  Dump analysis      - Invoke CA SymDump CICS dump/trace capture facility  \n    6  Product help       - Invoke CA InterTest product help facility           \n    7  Status/Maintenance - Product status and maintenance functions            \n    8  What's new?        - Display information about CA InterTest for CICS\n    X  Exit               - Terminate menu processing\n.\n.\n.\nThe Monitoring Menu appears, from which you can select a wide variety of different monitoring options. For a detailed\nexplanation of each of these options, use the online help or CICS Debugging.\n-------------- CA InterTest for CICS MONITORING MENU  ------------------\nOPTION  ===>", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a6ff29a0e591-1", "text": "OPTION  ===>                                                                   \n                                                                                \n    1  Programs           - Display/modify program monitoring options           \n    2  Transactions       - Display/modify transaction monitoring options       \n    3  Terminals          - Display/modify terminal monitoring options          \n    4  Status             - Display/remove current monitoring options           \n    5  Active tasks       - Display/purge active monitored tasks                \n    6  System-wide        - Display/modify global system-wide options\n.\n.\n.     \nOption 1 Programs accesses the Program Monitoring Menu, where you can set and remove any option for a program,\nand request a status display.\nThe Program Monitoring menu is probably the most frequently used menu during a testing session.\n-------------------- CA InterTest for CICS  PROGRAM MONITORING  --------------------\n 509", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "15c6a2ad9d3f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n COMMAND ===>                                                                   \n                                                                                \n   Type information and S to set or R to remove option(s) below.               \n                                                                                \n   Program  . . PL1DEMO_     Program name (or .ALL, .OPTIONS or generic)        \n   User ID  . . _______      User (or .ANY) for whom the program is monitored   \n                                                                                \n   Option       Description                                            More:   +\n _ Status       Display and/or remove monitoring options (S only)               \n _ Monitor      Monitoring (R removes monitoring and all options previously set)\n _ UBP          Unconditional breakpoints (specific program only)               \n _ CBP          Conditional breakpoints (specific program only)                 \n _ RBP          Breakpoints for CICS, DB2, DL/I or external CALL requests       \n _ Stmt Trace   Statement tracing and data monitoring (COBOL only) \n _ New copy     Fetch new copy of program and reset monitoring options (S only) \n _ Commands     Indirect commands defined for a specific COBOL or PL/I program \n _ Replace      CICS resource name replacement options                          \n _ Protect      Storage protection monitoring options                          \n _ Special      Other options (storage allocation, file updating, etc.)         \n _ Composite    Monitor multi-CSECT program's separately compiled components \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7 Backward   8 Forward    9           10           11           12           \nQuick access to this menu is available before or during a session, as described in the following table.\n2.Type the fastpath entry in the indicated field and press Enter.\nThe following list contains the fastpath entries that you can use to access the Program Monitoring menu:\n\u2013CICS, clear screen: ITST 2.1", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "15c6a2ad9d3f-1", "text": "\u2013CICS, clear screen: ITST 2.1\n\u2013Primary Option Menu, Option field: 2.1\n\u2013Source Listing display, Command field: =2.1\n\u2013Breakpoint display, Command field: =1.2.1\n3.After processing any program options from this menu, press PF3 to exit back to your test session. If you entered\ndirectly from CICS, you will exit back to the ITST Primary menu. From a Source Listing or breakpoint, PF3 takes you\nback to that display.\nSet and Remove Conditional Breakpoints\nConditional   breakpoints are breakpoints that take effect when a specific condition is met, such as when a counter\nexceeds a value. These breakpoints can help you isolate complex problems.\nTo set a conditional breakpoint, type C to the left of the statement where you want to set the breakpoint, as shown in the\nfollowing screen, and press Enter .\nCA InterTest for CICS   - PROTSYM FILE  SOURCE LISTING DISPLAY            \nCOMMAND ===>                                                                    \nProgram= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n---------+--------------------------------------------------------------------- \n _   599.1     1            GOTO SENDSCR1;                                      \n _   600.1                                                                      \n c   601.1     1      WRITETSQ:                                                 \n _   602.1               TS_SWITCH = ' ';                                       \n _   603.1               /* EXEC CICS WRITEQ TS QUEUE   (TSQ_NAME)              \n 510", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4f2fa1e18fe5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _   604.1                                      LENGTH  (TS_LEN)                \n _   605.1                                      FROM    (TS_AREA)               \n _   606.1                                      MAIN */\nInterTest for CICS then displays the menu on which you define the condition. In the following example, the breakpoint\nhalts program execution only if TS_SWITCH is equal to 3.\n        CA-InterTest MONITORING COMMAND BUILDER - CONDITIONAL BREAKPOINT       \n                                                                                \n Enter LEFT SIDE of condition (select one):                                     \n     Data Name ts-switch_______________________________________________________\n     Special keywords:                 ______   Register # __    COBOL BLL # __\n                                                                                \n Enter OPERATOR (EQ, NE, GT, LT, GE, LE):  eq    Length:  Left  ___    Right ___\n                                                                                \n Enter RIGHT SIDE of condition (select one):                                    \n     Data Name ________________________________________________________________\n     Special keywords:                 ______   Register # __    COBOL BLL # __\n     Literal 3_________________________________________________________________\n                                                                               \n Optional offset:  Enter + - @ OR % followed by a value.                       \n     Left side  _________________________   Right side ________________________\n                                                                               \n _ ENTER  S  to Drop monitoring on a true condition                            \n                                                                               \n For location:                                                                 \n              601.1     1      WRITETSQ:                                       \n                                                                               \n    Use Help or documentation for use of special keywords                      \n PF1 Help       2            3 End        4 Return     5            6          \n  PF7            8            9           10           11           12          \nConditional breakpoints are indicated by a C next to the line of code in your Source Listing.\nYou can easily remove a conditional breakpoint from where it displays in your Source Listing or from the Monitoring Status\nreport.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4f2fa1e18fe5-1", "text": "report.\nRemove Conditional Breakpoints from the Source Listing\nTo remove a conditional breakpoint from your Source Listing, overtype the C with an X and press Enter, as shown in the\nfollowing screen:\nCA InterTest for CICS   - PROTSYM FILE  SOURCE LISTING DISPLAY            \nCOMMAND ===>                                                                    \nProgram= PL1DEMO  Option # 9     Stmt #                             Margin= 01  \n                                        Search= WRITETSQ                        \n---------+--------------------------------------------------------------------- \n _   599.1     1            GOTO SENDSCR1;                                      \n _   600.1                                                                      \n x   601.1     1      WRITETSQ:                                               \n _   602.1               TS_SWITCH = ' ';                                       \n _   603.1               /* EXEC CICS WRITEQ TS QUEUE   (TSQ_NAME)              \n _   604.1                                      LENGTH  (TS_LEN)                \n 511", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b0b4099f630e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _   605.1                                      FROM    (TS_AREA)               \n _   606.1                                      MAIN */     \n.\n.\n.\nRemove Conditional Breakpoints from the Status Report\nAlternatively, you can always remove any breakpoint from the Monitoring Status report. To remove this conditional\nbreakpoint from your program, perform the following procedure:\n1.Type STATUS on the Command line to display the Monitoring Status report for the current program.\n2.Tab to the entry for the Conditional Breakpoint (CBP option) you want to remove, type R to the left of its entry, and\npress Enter.\n--------------- CA InterTest for CICS   MONITORING STATUS  ----------------\n COMMAND ===>                                                                   \n                                                                                \n   Type + to expand or - collapse option levels displayed below,                \n          or R to remove option(s).                                             \n                                                                                \n     Option     Description                Attributes                           \n _ - PL1DEMO    Program monitor entry      PL/I                                 \n _ - |-.ANY     User monitoring options    Active                               \n       |        Symbolic listing file      PROTSYM                              \n r -   |-CBP    Conditional breakpoint     #601                                 \n       |        Option ID                  0EC11E65                             \n       |        Condition                  CORE=IF='TS_SWITCH'.EQ.C'3'          \n       |        Compare type               CORE command comparison              \n       |        From, to terminals         U057, U057                           \n _     |-SLB    Source listing breakpoints U057                                 \n                *** End of data ***                                             \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n PF1 Help       2 Refresh    3 End        4 Return     5 Collapse   6 Expand    \n PF7 Backward   8 Forward    9           10           11           12", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b0b4099f630e-1", "text": "PF7 Backward   8 Forward    9           10           11           12\nInterTest for CICS places an asterisk to the left of the breakpoint to indicate that the removal was processed.\n3.Press PF3 to return to your Source.\nRequest Breakpoints\nRequest  breakpoints are breakpoints that take effect prior to CICS commands and macros and other program calls, such\nas calls to DL/I or DB2. With one specification, you can set breakpoints at all CICS commands or at specific commands,\nsuch as all REWRITE commands.\nUse request breakpoints to stop a program before the following commands:\n\u2022Every CICS command or macro\n\u2022Specific types of CICS commands, such as all File Control or Program Control commands\n\u2022Specific commands, such as all READ or WRITE commands\n 512", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7b94d5298848-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSet Request Breakpoints\nTo set request breakpoints, perform the following steps:\n1.Select option 2.1 Program Monitoring on the Primary Option Menu.\n-------------------- CA InterTest for CICS  PROGRAM MONITORING  --------------------\n COMMAND ===>                                                                   \n                                                                                \n   Type information and S to set or R to remove option(s) below.               \n                                                                                \n   Program  . . PL1DEMO_     Program name (or .ALL, .OPTIONS or generic)        \n   User ID  . . ________     User (or .ANY) for whom the program is monitored   \n                                                                                \n   Option       Description                                            More:   +  \n _ Status       Display and/or remove monitoring options (S only)               \n _ Monitor      Monitoring (R removes monitoring and all options previously set)\n _ UBP          Unconditional breakpoints (specific program only)               \n _ CBP          Conditional breakpoints (specific program only)                 \n s RBP          Breakpoints for CICS, DB2, DL/I or external CALL requests       \n _ Stmt Trace   Statement tracing and data monitoring (COBOL only) \n _ New copy     Fetch new copy of program and reset monitoring options (S only) \n _ Commands     Indirect commands defined for a specific COBOL or PL/I program \n _ Replace      CICS resource name replacement options                          \n _ Protect      Storage protection monitoring options                          \n _ Special      Other options (storage allocation, file updating, etc.)         \n _ Composite    Monitor multi-CSECT program's separately compiled components \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6\n PF7 Backward   8 Forward    9           10           11           12            \n2.In the Program field, type the name of the program for which you want to set request breakpoints.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7b94d5298848-1", "text": "3.Type S to the left of the RBP option (request breakpoints). Press Enter.\nThe Request Breakpoint Selection menu appears. Using this menu specify the type of request breakpoint, such as all\nCICS commands, File Control and Task Control.\nCA InterTest MONITORING COMMAND BUILDER - REQUEST BREAKPOINT SELECTION  13\n                                                                            \n              Set one or more types of Request Breakpoints in:             \n                                PROG=PL1DEMO                                \n                                                                            \n _ ALL commands                    _ DL/I    _ DB2     _ CALLs              \n                                                                            \n   _ Address, Assign,         _ Storage Control    _ BMS                    \n       Handles, Push, Pop     _ Program Control    _ Trace Control          \n   _ Terminal Control         _ Interval Control   _ Dump Control           \n   _ File Control             _ Task Control       _ Batch Data Interchange \n   _ TD Control               _ Journal Control    _ Built-In Functions     \n   _ TS Control               _ Syncpoints         _ Sys Prog Functions     \n   _ Web access               _ Business Trans     _ 3270 Bridge            \n                                                                            \n   Enter 'n' to stop only every n'th time:                         ____     \n   Term ID (or .ANY or .NO) where breakpoints will take effect:    ____     \n   Term ID (or .ANY) that will receive the breakpoints:            ____     \n 513", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0bf9c4494d03-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n   Statement no. of indirect command(s) to be executed:            _____    \n   User ID (or .ANY) who will execute the program:                 ________ \n                                                                            \n                                                                            \n PF1 Help       2            3 End        4 Return     5            6       \n PF7            8            9           10           11           12\nSubsequent menus prompt you for the specific command, such as all File Control commands, READ, WRITE and\nREWRITE.\n4.Type X in front of each type of command for which you want to set request breakpoints.\nAfter setting your request breakpoints, PF4 returns you to the Primary Option Menu. If you came from a Source\nListing, PF3 returns you to your Source.\nRemove Request Breakpoints\nTo remove request breakpoints, perform the following steps:\n1.From the Source Listing display or breakpoint display, type STATUS on the Command line and press Enter. InterTest\nfor CICS displays the Monitoring Status display showing all options for the current program.\n2.Type R to the left of the request breakpoint (RBP) you want to remove and press Enter . InterTest for CICS places an\nasterisk to the left of the breakpoint to indicate that the command has been processed.\n3.Press PF3 to return to the Source Listing or Breakpoint display.\nThe Backtrace Facility\nWhen your program stops at a breakpoint, you might find it useful to examine the Backtrace Summary  and the Source\nListing Backtrace. The Backtrace facility shows the logic flow of the program and explains how processing reached this\npoint.\nThe Backtrace facility enables you to do the following tasks:\n\u2022View the Backtrace Summary screen for a (high-level) summary of the program's execution\n\u2022Use special PF keys to step through the program's execution path", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0bf9c4494d03-1", "text": "\u2022Use special PF keys to step through the program's execution path\n\u2022Reposition the source listing to view the program's execution path from a different backtrace position\nIn addition to the Backtrace PF keys, all other Source Listing options, such as the Keep window, setting and removing\nbreakpoints, and the ability to scroll backward and forward from the current source listing position are available from the\nSource Listing Backtrace screen.\nAccess the Backtrace Summary\nTo view the Backtrace Summary, press PF11 from the Source Listing Breakpoint screen, or, type BTRACE in the\nCommand line and press Enter.\nInterTest for CICS positions the Backtrace Summary Screen at the last executed statement, as follows.\n InterTest  for CICS   - BACKTRACE SUMMARY                                \n                                                                                \nProgram= PL1DEMO                                      From 0002 To 0014 Of 0014 \n                                                                                \nSpecify  S then ENTER to display Source Listing BACKTRACE                       \n------------------------------------------------------------------------------- \nPFKS 1 Help      2 Backtrace 3 End        4            5 1st Stmt   6 Last Stmt \n     7 Backward  8 Forward   9 Next Wnd  10           11 Prev Bloc 12 Next Bloc \n------------------------------------------------------------------------------- \n S Bkmk       Stmt Block  \u00a6 Source Listing                                      \n _ ____      #19 ...  #19 \u00a6            PL1DEMO:  PROC(DFHEIPTR,COMMAREA_PTR) OP \n 514", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9f6d1a9d6fdf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _ ____      #19 ...  #19 \u00a6            PL1DEMO:  PROC(DFHEIPTR,COMMAREA_PTR) OP \n _ ____      #19 ...  #19 \u00a6            PL1DEMO:  PROC(DFHEIPTR,COMMAREA_PTR) OP \n _ ____     #525 ... #541 \u00a6     1      START_OF_PGM:                            \n _ ____     #544 ... #544 \u00a6     1         IF EIBAID = DFHPF2  |            /**  \n _ ____     #548 ... #548 \u00a6     1         IF TS_SWITCH = DFHPF5    THEN         \n _ ____     #555 ... #555 \u00a6     1         DO;                                   \n _ ____     #561 ... #561 \u00a6     1  1      END;                                  \n _ ____     #573 ... #573 \u00a6     1  1      END;                                  \n _ ____     #578 ... #580 \u00a6     1         IF EIBCALEN > 0 |                     \n _ ____     #588 ... #588 \u00a6     1  2            END;                            \n _ ____     #595 ... #595 \u00a6     1  2            END;                            \n * ____     #635 ... BKPT \u00a6     1      NOPROB:  CAIN2987 Last Backtrace Stmt Block  \nRead the Backtrace Summary\nThe Backtrace Summary screen summarizes the program's execution. This screen displays the statement number and\nsource of the first statement in each contiguous group of executed program statements.\n\u2022The order of the statements reflects the program's execution path.\n\u2022The top statement is the first statement executed; the bottom statement is the most recently executed statement.\nFrom the Backtrace Summary screen, you can do the following tasks:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9f6d1a9d6fdf-1", "text": "From the Backtrace Summary screen, you can do the following tasks:\n\u2022Reposition the display to view statement-by-statement details of the program's execution path by:\n- Pressing PF2\n- Marking a statement block with s, then pressing Enter\n\u2022Assign a bookmark, consisting of one to four characters, to one or more backtrace positions for faster and easier\nnavigation through the Backtrace Summary\n\u2022Trace program execution using:\nPF5 1st Stmt\nRe-positions the Backtrace Summary screen to the first or oldest entry in the Backtrace.\nPF6 Last Stmt\nRe-positions the Backtrace Summary screen to the last or newest entry in the Backtrace.\nPF7 Backward\nScrolls the Backtrace Summary screen backward (up) a full screen.\nPF8 Forward\nScrolls the Backtrace Summary screen forward (down) a full screen.\nPF11 Prev Bloc\nDisplays the previous statement block.\nPF12 Next Bloc\nDisplays the next statement block.\nAccess the Source Listing Backtrace\nTo display the Source Listing Backtrace, press PF2 or type S next to a statement block in the Select column of the\nBacktrace Summary screen as shown in the previous screen.\nThe next screen shows the Source Listing Backtrace screen that displays.\nCA InterTest for CICS   - PROTSYM FILE  ABEND DETECTED BACKTRACE          \nCOMMAND ===>                                                                    \nProgram= PL1DEMO  Option #       Stmt #                             Margin= 01  \n 515", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "290a0fb34964-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ TASKNUM                         | ?00000.                                \n======= Backtrace at #000635  (000635 -> 000638 executed     1 times) <=======  \n _   633.1     1  1      END;                                                   \n _   634.1                                                                      \n  _ ====>.1     1      NOPROB:                                                  _   636.1           \n CONTINUE_TASK:                                           _   637.1               MAPNUM  = '00';             \n                          A   638.1     1         TASKNUM = TASKNUM + 1;                               \n _   639.1     1         IF TASKNUM > 2 THEN                                    \n _   640.1     1            GOTO END_SESSION;                                   \n _   641.1     1         IF TASKNUM = 1 THEN                                    \n _   642.1     1            GOTO SENDSCR3;                                      \n _   643.1     1         GOTO END_SESSION;                                      \n _   644.1                                                                      \n _   645.1     1      SENDSCR3:                           /** ASRA CONGRATULAT  \n _   646.1                   /* EXEC CICS SEND MAP('DASRA')                     \n _   647.1                                     MAPSET('IN25PMP')                \n _   648.1                                     WAIT                             \n _   649.1                                     ERASE */\nRead the Source Listing Backtrace\nTo clearly detail the program's execution path, statement by statement, source statements that were executed from the\ncurrent backtrace position are highlighted. When you specify a non-backtrace Source Listing option or use PF7 or PF8 to", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "290a0fb34964-1", "text": "reposition the Source Listing, the highlighting of executed statements temporarily suspends until a backtrace-related PF\nkey (next block, previous block, and so on) is entered.\nWhen in Source Listing Backtrace mode, the current backtrace position always displays on the line just above the first\nsource statement. This line displays as follows:\n======>BACKTRACE AT #nnnnn (nnnnn -> nnnnn executed nnnnn times)<=====\nThe information in this line indicates the following information:\n#nnnnn\nSpecifies where the program statement or offset the backtrace is currently positioned.\nnnnnn -> nnnnn\nSpecifies the first and last number of the statement block.\nnnnnn times\nSpecifies the number of times a statement block was executed.\nOn the Source Listing Backtrace, each relevant backtrace position is indicated in the listing by an arrow or a line:\n====>\nIndicates the first statement in a statement block\n<====\nIndicates the last statement in a statement block\n====\nIndicates all other statements within a statement block\nThe Source Listing Backtrace displays the source of the each statement:\n\u2022The order of the statements reflect the program's execution path.\n\u2022The top statement is the first statement executed; the bottom statement is the most recently executed statement.\n 516", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e1c4164b604f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNavigate Through Program Execution\nYou can trace your program's execution path by using the following PF keys:\n\u2022Using PF5, PF9, and PF11 to trace execution backward\n\u2022Using PF6, PF10, and PF12 to trace execution forward\n\u2022Setting the Source Listing Profile Stepping Amount, and then using PF9 and PF10 to automatically trace the execution\nbackward or forward\nEnd a Source Listing Backtrace Session\n1.To turn off the Source Listing Backtrace display mode, press Clear or PF3. InterTest for CICS redisplays the Source\nListing Breakpoint screen positioned at the last breakpoint.\n2.To toggle between the Source Listing Backtrace and the Backtrace Summary, press PF2.\nSet the Code Counting Coverage Option\nInterTest for CICS has many options for specialized testing needs. The code coverage option lets you see the number of\ntimes an Assembler statement was executed.\nThe initial setting for Code Counting is OFF, which is the default. However, you can use the Source Listing Profile screen\nto turn it ON or OFF again at any time after you have selected monitoring for a program.\nHow the counts are displayed or not displayed is handled by the primary line command COUNTS and its associated\nparameters.\nThis feature does cause overhead during program monitoring and should be turned off as soon as it is no longer needed.\nTo change the setting for Code Coverage, perform the following steps:\n1.Type PROFILE on the command line and press Enter, or press PF4 to access the Profile screen from any Source\nListing Screen. The Code Counting= field shows the current setting.\n2.Overtype the current value with one of the following:\nYES\nEnables code counting and turns on the COUNTER display feature.\nNO\nRemoves the COUNTER display and stops the counting feature.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e1c4164b604f-1", "text": "NO\nRemoves the COUNTER display and stops the counting feature.\n3.Press Enter to process the new setting(s) and to return to the Source Listing Display.\nThe following screen shows the Code Coverage feature.\nCA InterTest for CICS  - PROTSYM FILE ABEND DETECTED BREAKPOINT         \nCOMMAND ===>                                                                    \nProgram= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ TASKNUM                         | ?00000.                                \n---------+--------------------------------------------------------| COUNTER |-- \n _   587.1            0 F0 F0 F6 F0 F0 F0 F0 F0 'X */,NOPROB);    |         |   \n _   588.1     1  2            END;                               | 0000001 |   \n _   589.1                     /* EXEC CICS DELETEQ TS QUEUE(TSQ_N|         |   \n _   590.1     1  1            DO;                                | 0000001 |   \n _   591.1     1  2            DCL DFHENTRY_BF6577CC_AC4F3B6B BASE|         |I  \n _   592.1            ER ASSEMBLER) ENTRY(*,CHAR(8));             |         |   \n _   593.1     1  2           CALL DFHENTRY_BF6577CC_AC4F3B6B('   | 0000001 |0  \n _   594.1            80 00 03 00 00 21 00 F0 F0 F6 F1 F0 F0 F0 F0|         |N  \n 517", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7a467172e7ea-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _   595.1     1  2            END;                               | 0000001 |   \n _   596.1     1  1            GOTO CONTINUE_TASK;                | 0000001 |   \n _   597.1     1  1         END;                                  | 0000000 |   \n _   598.1                                                        |         |   \n _   599.1     1            GOTO SENDSCR1;                        | 0000000 |   \n _   600.1                                                        |         |   \n _   601.1     1      WRITETSQ:                                   | 0000001 |   \n _   602.1               TS_SWITCH = ' ';                         |         |\nIndirect Commands\nThe InterTest Indirect Commands facility lets you specify a set of indirect commands to be executed in one of two ways:\n\u2022Automatically, when a breakpoint pointing to that set of commands is reached\n\u2022On demand, when you are at a breakpoint and use the Breakpoint Primary Option menu to resume execution with an\nindirect command (the fastpath is =4.5 from any breakpoint)\nBy using indirect commands, you can dynamically modify or correct programs without having to leave your test session to\nrecompile your program.\nWith the indirect commands facility, you can do the following actions:\n\u2022Change the flow of control in your program\n\u2022Test conditions based on specified variables\n\u2022Change the value of specified variables\n\u2022Create and execute commands as a group, like adding a new subroutine\n\u2022Automatically resume execution of your program at the same or different location\n\u2022Define abbreviations for variables with long names\nCode Indirect Commands\nInterTest for CICS provides an Indirect Commands facility for coding the statements. You can access it from the Source", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7a467172e7ea-1", "text": "Listing or from the ITST menus.\nTo access the Indirect Commands facility from the Source Listing facility, type ICMDS in the command line or 11 in the\nOption # field and press Enter.\nNOTE\nTab to the More: + field and press Enter to view labels of Options 6 to 15. Notice Option 11 is Indirect\ncommands, and Option 12 is Breakpoint options.\nCA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \nCOMMAND ===> ICMDS                                                             \nProgram= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ TASKNUM                         | ?00000.                                \n---------+--------------------------------------------------------------------- \n _   636.1            CONTINUE_TASK:                                            \n _   637.1               MAPNUM  = '00';                                        \n A   ==>.1     1         TASKNUM = TASKNUM + 1; \n.\n.\n.\n 518", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ad205b04b176-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo access the Indirect Commands facility from the menus, access the Program Monitoring menu (fastpath is ITST 2.1),\nand select the Commands option. Detailed steps follow.\n1.Select option 2 Monitoring on the Primary Option Menu. The Monitoring Menu appears.\n2.Select option 1 Programs. The Program Monitoring screen appears.\n3.In the Program field, type the name of the program for which you want to create Indirect Commands.\n4.Type S to the left of the Command option (Indirect commands). Press Enter.\n-------------------- CA InterTest for CICS  PROGRAM MONITORING  --------------------\n COMMAND ===>                                                                   \n                                                                                \n   Type information and S to set or R to remove option(s) below.               \n                                                                                \n   Program  . . PL1DEMO_     Program name (or .ALL, .OPTIONS or generic)        \n   User ID  . . ________     User (or .ANY) for whom the program is monitored   \n                                                                                \n   Option       Description                                            More:   + \n _ Status       Display and/or remove monitoring options (S only)               \n _ Monitor      Monitoring (R removes monitoring and all options previously set)\n _ UBP          Unconditional breakpoints (specific program only)               \n _ CBP          Conditional breakpoints (specific program only)                 \n _ RBP          Breakpoints for CICS, DB2, DL/I or external CALL requests       \n _ Stmt Trace   Statement tracing and data monitoring (COBOL only) \n _ New copy     Fetch new copy of program and reset monitoring options (S only) \n s Commands     Indirect commands defined for a specific COBOL or PL/I program \n _ Replace      CICS resource name replacement options                          \n _ Protect      Storage protection monitoring options                          \n _ Special      Other options (storage allocation, file updating, etc.)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ad205b04b176-1", "text": "_ Special      Other options (storage allocation, file updating, etc.)         \n _ Composite    Monitor multi-CSECT program's separately compiled components \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6\n PF7 Backward   8 Forward    9           10           11           12           \nWhen you choose Commands from the Program Monitoring menu, another screen lets you set the terminal ID\n(terminal ID, .ANY or .NO) where the indirect commands take effect, and the user ID who executes the program (.ANY\nor a specific ID).\nNormally you can accept the defaults. However, these entries need to match any existing monitoring entry for the\nprogram, which can be viewed on the Monitoring Status display.\nCA InterTest MONITORING COMMAND BUILDER - INDIRECT COMMANDS       24\n                                                                                \n     SET option to  EDIT  indirect commands defined for execution in:           \n                                PROG=PL1DEMO                                    \n                                                                                \n                                                                                \n      Term ID (or .ANY or .NO) where commands will take effect:       ____      \n      User ID (or .ANY) who will execute the program:                 ________  \n                                                                                \n \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7            8            9           10           11           12\n5.Press Enter to display the Indirect Commands facility.\n 519", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "baba88277d3c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe Indirect Commands Facility\nEither access method brings you to the Indirect Commands facility shown in the following screen. This example shows the\nindirect commands that can be used to fix the ASRA condition in our PL1DEMO demo program, without recompiling. To\ndo so, follow these steps:\n1.Type the statement numbers and the text of the indirect commands on the Indirect Commands screen, as shown in the\nfollowing screen. For details, see the Indirect Commands section in Breakpoint Activities and online Help.\n2.After coding the statements, press PF3 to exit the Indirect Commands facility. If you accessed the facility from the ITST\nmenus, use =X to exit the menus.\nCA InterTest MONITOR COMMAND BUILDER -   PL1DEMO  INDIRECT COMMANDS       24 \n                                                                                \n   Term ID (or .ANY or .NO): G001                    Delete ALL: NO             \n                                                                                \n  LINE  COMMAND                                                                 \n ----- ------------------------------------------------------------------------ \n 00010 /* INITIALIZE TASKNUM */                                                 \n 00020 MOVE 0 TO TASKNUM                                                        \n 00030 EXIT                                                                     \n                                                                                \n \n                                                                                \n  1 Help       2            3 End        4           5                6         \n  7 Backward   8 Forward    9 Top       10 Bottom   11               12         \nCAIN1261 Indirect command(s) added.\nControl the Flow of Execution\nWhen running your program, if a breakpoint points to indirect commands, the commands are automatically executed\nwithout stopping first. Execution is returned to the program according to the exit command that you specified in your\nindirect commands.\nTo return execution to your program following indirect command processing, use one of the following exit commands:\nBREAK", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "baba88277d3c-1", "text": "BREAK\nInterTest for CICS halts indirect command processing and issues a breakpoint display from where the indirect\ncommands were invoked in the program.\nGOTO\nInterTest for CICS resumes execution at the program statement number, offset, paragraph name, or indirect\ncommand statement number specified after the GOTO command.\nEXIT\nInterTest for CICS resumes program execution at the breakpoint location from which the indirect commands were\ninvoked and continues debugging the program until the next breakpoint.\nRUN\nInterTest for CICS resumes program execution at the breakpoint location from which the indirect commands were\ninvoked and ignores all subsequent breakpoints.\nAttach the Indirect Command to Breakpoints\nTo have the indirect commands automatically executed by your program, set an unconditional, conditional, or request\nbreakpoint that points to the first indirect command statement number. When you set a breakpoint with this option, each\ntime the breakpoint takes effect the indirect commands execute.\n 520", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "be2860ce25cc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFrom the Source Listing facility, set the unconditional or conditional breakpoint as follows:\n1.Display the line in your Source Code where you want to set the breakpoint to execute the indirect commands.\n2.Type BPO in the command line or 12 in the Option # field (Breakpoint Options), tab down to the line where you want\nto set the breakpoint, type U for unconditional or C for conditional, and press Enter. The Breakpoint Locations menu\nappears, letting you set a number of breakpoint options.\n3.Tab to the following option near the bottom of the panel:\nStatement no. of indirect command(s) to be executed:     _____\n4.Type the first indirect command statement number (leading zeroes are optional), as shown in the following screen.\nCA InterTest MONITORING COMMAND BUILDER - PL/I BREAKPOINT LOCATIONS       11\n                                                                                \n    SET breakpoint options for   PROG=PL1DEMO  for location:                    \n                                                                                \n              635.1     1      NOPROB:                                          \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                       After: _ \n            All Procedure Names:  _                                             \n            Enter 'n' to stop only every n'th time:                         ____\n            Term ID (or .ANY or .NO) where breakpoints will take effect:    U057\n            Term ID (or .ANY) that will receive the breakpoints:            U057\n            Statement no. of indirect command(s) to be executed:           10__\n            User ID (or .ANY) who will execute the program:             .ANY    \n                                                                                \n                                                                                \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7            8            9           10           11           12\n5.Press Enter to process this menu.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "be2860ce25cc-1", "text": "5.Press Enter to process this menu.\n6.If you are setting a conditional breakpoint, type the condition on the Conditional Breakpoint screen and press Enter.\nYour Source Listing display shows the indirect command to execute on the line above the statement with the U or C\nindicator.\n7.To set a request breakpoint that executes an indirect command, follow the usual steps to set the request breakpoint\nfrom the menus. On the Request Breakpoint Selection menu, also type the statement number of the indirect command\nto be executed, as shown in the following screen.\nCA InterTest MONITORING COMMAND BUILDER - REQUEST BREAKPOINT SELECTION  13\n                                                                                \n              Set one or more types of Request Breakpoints in:                 \n                                PROG=PL1DEMO                                    \n                                                                                \n _ ALL commands                    _ DL/I    _ DB2     _CALLs                  \n                                                                                \n   _ Address, Assign,         _ Storage Control    _ BMS                        \n       Handles, Push, Pop     _ Program Control    _ Trace Control              \n   _ Terminal Control         _ Interval Control   _ Dump Control               \n   x File Control             _ Task Control       _ Batch Data Interchange     \n   _ TD Control               _ Journal Control    _ Built-In Functions         \n 521", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c553c8dfe3f6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n   _ TS Control               _ Syncpoints         _ Sys Prog Functions         \n   _ Web access               _ Business Trans     _ 3270 Bridge                \n                                                                                \n   Enter 'n' to stop only every n'th time:                         ____         \n   Term ID (or .ANY or .NO) where breakpoints will take effect:    ____         \n   Term ID (or .ANY) that will receive the breakpoints:            ____         \n   Statement no. of indirect command(s) to be executed:            100__        \n   User ID (or .ANY) who will execute the program:                 ________     \n                                                                                \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7            8            9           10           11           12\nIdentify Indirect Commands on the Monitoring Status Display\nThe following monitoring status display shows the entries for an unconditional breakpoint set at statement #635 that will\nexecute indirect command statement number 10. The indirect commands are listed as a CMD option to the program.\n--------------- CA InterTest for CICS   MONITORING STATUS  ----------------\n COMMAND ===>                                                                   \n                                                                                \n   Type + to expand or - collapse option levels displayed below,                \n          or R to remove option(s).                                             \n                                                                                \n     Option     Description                Attributes                           \n _ - PL1DEMO    Program monitor entry      PL/I                                 \n     |          Waiting at breakpoint      Task 00066, ABP since 03:17 p.m.     \n _ - |-.ANY     User monitoring options    Active                               \n       |        Symbolic listing file      PROTSYM                             \n _ -   |-UBP    Unconditional breakpoint   #635                              \n       |        Option ID                  DB6BDAD0", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c553c8dfe3f6-1", "text": "|        Option ID                  DB6BDAD0                          \n       |        From, to terminals         U057, U057                        \n       |        Execute indirect command   10                                \n _ -   |-CMD    Indirect commands defined  U057                              \n       |        Option ID                  57208DFD                          \n _     |-SLB    Source listing breakpoints U057                                 \n                *** End of data ***                                             \n                                                                                \n                                                                                \n                                                                                \n PF1 Help       2 Refresh    3 End        4 Return     5 Collapse   6 Expand    \n PF7 Backward   8 Forward    9           10           11           12\nReview, Change or Delete Indirect Commands\nFrom the Monitoring Status display, you can remove any monitoring entry.\n1.Type R next to the UBP option and press Enter to remove the breakpoint executing the indirect commands. Type R\nnext to the CMD option to remove the indirect commands.\n2.To change, add, delete, or review indirect commands directly from the Source Listing facility, type ICMDS in the\ncommand line or 11 in the Option # field.\nInterTest for CICS displays the indirect commands for the default terminal, which is either the terminal you are working\nat, or the terminal specified on the Source Listing Profile.\n 522", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d32c73a03c6e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFor more information on the Indirect Commands facility, see Breakpoint Activities.\nReplacement, Protection, and Special Options\nInterTest for CICS has many options for specialized testing needs. A few are explained here. For an explanation of all the\nmonitoring options, see Monitoring Menu Options.\nYou can set or remove options from the Monitoring Command Builder menus. For details, see Set Options from the\nMonitoring Menus.\nReplacement Options\nReplacement options let you dynamically change the names of CICS resources such as programs, files, transient data\nqueues, and temporary storage.\nOne reason to use replacement options is to correct errors so you can continue testing without recompiling. For example,\nsuppose InterTest for CICS halts your program at an automatic breakpoint to prevent an AEIL abend caused by an\nincorrect file name. You can use the Replace File Name option to dynamically change the file name so testing can\ncontinue.\nAnother reason for using replacement options is to use different resources during testing than those hard coded in the\nprogram. For example, you can specify that the program use a test file rather than the production file named in the\nprogram.\nProtection Options\nWhen InterTest for CICS monitors a program, it prevents the program from modifying storage areas it does not own and\nissuing non-CICS instructions.\nProtection options let you override the InterTest for CICS default rules for modifying main storage, the CSA, and load\nmodules. The protection options, which are password protected, provide extra flexibility for special testing needs. These\noptions let a program to do the following modifications:\n\u2022Modify any area of main storage\n\u2022Modify areas in the CSA or CWA\n\u2022Modify a load module\nThese options can also prevent a program from modifying specific areas of storage not normally protected.\nSpecial Options", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d32c73a03c6e-1", "text": "These options can also prevent a program from modifying specific areas of storage not normally protected.\nSpecial Options\nSpecial options alter the InterTest for CICS standard monitoring procedures and help you design customized testing\nscenarios.\nThe No File Updating option prevents a monitored program from updating files. This option is in testing because your file\ndata is unchanged at the end of program execution. This means:\n\u2022You can repeatedly test a program without restoring your files.\n\u2022Programs can share the same file without interfering with each other's work.\n\u2022A test program can use a production file without affecting data integrity.\nOther options provide additional functions. For example:\n\u2022The FOL option lets InterTest for CICS continue monitoring even after a program branches directly to another program\n(wild branch).\n\u2022The MXS option limits the amount of CICS storage a program can use.\n\u2022The MXR option limits the number of CICS requests a program can issue.\n 523", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ad8e645e5f50-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nComposite Module Testing\nComposite support lets you take advantage of all InterTest for CICS functions when you test composite modules. A\ncomposite module  consists of separately compiled modules link-edited in one load module. These modules can be written\nin different languages and compiled at different times. Composite support lets you test and debug a called subroutine as if\nit were a separate program -- with full symbolic support.\nExample\nSuppose a PL/I program has several subroutines, some written in PL/I, some written in Assembler and PL/I. You can test\nand debug any of the subroutines just as if it were a main program by setting breakpoints, setting monitoring options,\ndisplaying the source listing, and displaying and modifying main and auxiliary storage.\nA composite module can be defined using one of two methods:\n\u2022Execute batch program IN25LINK after the link-edit step for the composite module\n\u2022Specify the COMPOSITE command in the Source Listing Display before monitoring is activated for the program\nWhen you set monitoring for a composite module defined by the IN25LINK method, InterTest for CICS informs you that\ncomposite support can be set, as shown in the following message:\nCAIN4561 Press PF3 to display composite menu for PLICOMP1\nWhen you press PF3, InterTest for CICS displays the link-edit information for the main program and its subroutines. You\ncan change this information online.\n       CA InterTest for CICS - Composite Support Builder                 \n COMMAND ===>                                                      SCROLL: PAGE\n Define composite support for PL1DEML  and press PF5.        Row 00001 of 00006 \n CAIN2620 Not all subprograms are selected                                      \n                                                                                \n * *          *          *        *        *           *                        \n _ Link name  Monitor    Offset   Length   Language    Comments", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ad8e645e5f50-1", "text": "_ Link name  Monitor    Offset   Length   Language    Comments                 \n S PL1DEML1   PL1DEML        80      248   PL/I   4.3                           \n S PSBIN251   PSBIN25       EE8      1B0   PL/I   4.3                           \n S ASBIN25    ASBIN25      1098      17C   HLASM  6.0                           \n _ @PL1DEML   ________     1218       10               Symbolics NOT available  \n _ PLIXOPT    ________     1228        8               Symbolics NOT available  \n _ @PSBIN25   ________     1230        8               Symbolics NOT available  \n                                                                                \n                                                                                \n                                                                                \n PF1 Help       2            3 End        4            5 Process    6 RFind     \n PF7 Backward   8 Forward    9           10           11           12           \nPress PF5 to set composite support so that each program can be tested separately.\nDump Analysis with SymDump\nSymDump  for CICS, the InterTest for CICS optional symbolic dump facility, is a powerful online tool that automatically\npinpoints the source statement responsible for an abend. SymDump  for CICS was designed to complement InterTest,\nespecially in production regions where programs are not usually monitored. Working with InterTest, SymDump  for CICS\nlets you bring a dump back to life. Familiar InterTest for CICS Source Listing screens and other facilities, such as the\nability to view and modify main and auxiliary storage, make it easy to resolve application dumps.\nSymDump  for CICS is option 5 Dump analysis on the InterTest for CICS Primary Option Menu.\n 524", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f3dfe6ca1793-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n---------------- CA SymDump for CICS  PRIMARY OPTION MENU -----------------\n OPTION  ===>                                                                   \n                                                                                \n1 Analysis           - Display/select captured CICS dumps/traces           \n2 Tracing            - Capture CICS internal trace for analysis            \n3 Configuration      - Display/modify CA SymDump initialization parameters \n4 Start              - Start dump capture facility                         \n5 Stop               - Stop dump capture facility                          \n6 Source             - Display/select program source files/listings     \n7 Status/Maintenance  -  Product status and maintenance functions\n8 What's new?        - Display information about CA SymDump for CICS\nX Exit               - Terminate CA SymDump menu processing                \n                                                                                \n                             \n                       CA SymDump for CICS \n                           \n             Copyright \u00a9 SOLVE:Access  CA.  All rights reserved.\n                            \n                                                                              \n PF1 Help       2            3 End        4 Return     5            6  \n PF7            8            9           10           11           12         \nWith SymDump  for CICS, you can do the following tasks:\n\u2022Analyze dumps symbolically online, using InterTest for CICS source code listings\n\u2022Resolve CICS production dumps from any region (for example, debug production abends from your test region)\n\u2022Manage your dump data set, selectively retaining the dumps you want to view and print, and set configuration\nparameters to discard ones you do not need and suppress capture of duplicate dumps\nWhen you use SymDump  for CICS to view a dump, you can select any of the following displays for immediate viewing:\nFormatted Displays\nIntelligently formatted displays of the dump contents, that often pinpoints the reason for the abend. Displays\ninclude: analysis, source, abend help, program call trace, registers, last CICS screen, files accessed, and", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f3dfe6ca1793-1", "text": "programs, transactions and terminals referenced.\nTask Areas\nInterTest for CICS CORE displays for such areas as the Commarea, the EXEC Interface Block, and the\nTransaction Work Area.\nLanguage Areas\nInterTest for CICS CORE displays for such areas as COBOL working storage and COBOL BLL cells.\nDatabase Areas\nInterTest for CICS CORE displays for DB2 and DL/I.\nCICS System Areas\nInterTest for CICS CORE displays for such areas as the Common System Area and the Common Work Area.\nExample\nSuppose a program not being monitored by InterTest for CICS abends with an ASRA. With SymDump , you can select\nAbend analysis display and frequently identify the problem immediately. In the following screen, you can see that abend\nanalysis gives abending instruction and operands -- even without symbolics.\n------------CA SymDump for CICS ABEND ANALYSIS  -----------------\n 525", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d656aeb73193-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n COMMAND ===>                                                                   \n                                                                                \n   Type S to display main storage at the data location address.               \n                                                                                \n   Prog: PL1DEMO    Code: ASRA    Tran: DEMP   Appl: A01IC9NL   Date: 11/28/2000\n   User: CICSUSER   Task: 00094   Term: G001   Node: A55TG001   Time: 12:04:06  \n                                                                                \n   Data Type             Location   Value                                       \n   Abended by                       Operating system                            \n   Abend type                       Program check, data exception (0C7)         \n   Abend in CSECT                   PL1DEMO1 + 00000536                         \n   AMODE, EXECKEY                   31, USER                                    \n   PSW at time of abend             078D0E00 8C1068EC 00060007 0B99A000         \n _ Abending instruction  0C1068E6   FA20D5DD3334                                \n                                    AP    X'5DD'(3,R13),X'334'(1,R3)            \n                                    Add decimal instruction                     \n _ Operand 1 storage     0BA0A46D   000000                                   \n                                    Invalid packed decimal data              \n _ Operand 2 storage     0C108A1C   1C                                          \n                                    Packed decimal data                         \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7 Backward   8 Forward    9           10           11           12\nThe Abend Analysis identifies exactly why and where the abend occurred. It gives the abending instruction and storage", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d656aeb73193-1", "text": "values for each operand of the instruction. Abend analysis information is available whether or not you have symbolics\navailable for the abending program.\nIn the previous example, the description of Operand 1 tells you its storage value is invalid for its data type. It should be a\npacked decimal. Using this display only, you know what triggered the ASRA!\nIf you get symbolics for the abending program (either before or after the abend) you can select the Source display and see\nthe breakpoint at the statement that triggered the abend. This is available even though InterTest for CICS was not active in\nthe region when the abend occurred.\nCA SymDump for CICS - PROTSYM FILE SOURCE LISTING DUMP ANALYSIS        \nCOMMAND ===>                                                                   \nProgram= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                \n---------+---------------------------------------------------------------------\n _                  CONTINUE_TASK:                                              \n _                     MAPNUM  = '00';                                          \n A   ==>  1  0     TASKNUM = TASKNUM + 1;                                    \n     ==>                                                                     \n     ==> ABEND/DUMP CODE: ASRA                                               \n     ==>                                                                     \n     ==>      Press PF1 for a detailed description.                          \n     ==>                                                                     \n _    96  1  0     IF TASKNUM > 2 THEN                                          \n _                        GOTO END_SESSION;                                     \n _    97  1  0     IF TASKNUM = 1 THEN                                          \n _                        GOTO SENDSCR3;                                        \n _    98  1  0     GOTO END_SESSION;                                            \n                                                                                \n 526", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "23d4856a95b0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _    99  1  0  SENDSCR3:                           /** ASRA CONGRATULATION SC  \n _                         /* EXEC CICS SEND MAP('DASRA')                       \n _                                           MAPSET('IN25PMP')                  \n _                                           WAIT                               \n _                                           ERASE */\nNow you can use InterTest for CICS features to solve the problem. In this example, you already know the contents of\nTASKNUM are invalid from the Abend Analysis display. However, if you need to, you can display the contents of any data\nitem. You might want use the backtrace facility to trace the program's execution path, or you might want to inspect the file.\nInterTest for CICS provides all the tools you need to diagnose and resolve the dump.\nPL/I Advanced Demo Session\nThe advanced demo session demonstrates solutions to several scenarios including limiting CICS requests, detecting\nstorage violations, debugging composite modules. \nIf you are a new user, you might want to postpone this advanced demo session until you are more comfortable with the\nbasic features of InterTest for CICS.\nNOTE\nOnly a handful of InterTest for CICS features are demonstrated in this demo session. For more information, see\nCICS Debugging  or the Help facility.\nThis article consists of the following independent sections, each detailing a different advanced InterTest for CICS feature:\nOption 01\nReplace a file name.\nOption 02\nLimit the number of CICS requests issued by a program.Limit the amount of storage obtained by a program.\nOption 03\nPrevent a program from updating a file. Use request breakpoints and the FILE facility.\nOption 04\nDetect and prevent a storage violation.\nOption 05\nTest a composite module.\nBefore proceeding with the demo session, you must complete the steps outlined in the following section.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "23d4856a95b0-1", "text": "Before proceeding with the demo session, you must complete the steps outlined in the following section.\nDemo Preliminaries\nThe advanced demo session uses PL1DEMO just as the basic session did. Before beginning, you need to set some\nbreakpoints that will be used in different sections of the advanced demo session. The three breakpoints you need to set\nfor PL1DEMO are shown on the following Monitoring Status screen.\n---------------  CA InterTest for CICS   MONITORING STATUS  -------------\n COMMAND ===>                                                                \n                                                                             \n   Type + to expand or - collapse option levels displayed below,             \n          or R to remove option(s).                                          \n                                                                             \n     Option     Description                Attributes                        \n _ - PL1DEMO    Program monitor entry      PL/I                              \n 527", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c16cece80a8e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _ - |-.ANY     User monitoring options    Active                            \n       |        Symbolic listing file      PROTSYM                           \n _ -   |-UBP    Unconditional breakpoint   #1308                             \n       |        Option ID                  99B13F53                          \n       |        From, to terminals         U057, U057                        \n _ -   |-RBP    Request breakpoint(s)      REWRITE                           \n       |        Option ID                  8E495266                          \n       |        From, to terminals         U057, U057                        \n _ -   |-UBP    Unconditional breakpoint   'LOOPRTN'                         \n       |        Option ID                  7D41117C                          \n       |        From, to terminals         U057, U057                        \n _     |-SLB    Source listing breakpoints U057                              \n                *** End of data ***                                          \n                                                                             \n PF1 Help       2 Refresh    3 End        4 Return     5 Collapse   6 Expand \n PF7 Backward   8 Forward    9           10           11           12          \nThe details of setting these breakpoints are provided in the next sections.\nSet Unconditional Breakpoints\nTo begin, you will need to bring up the Source Listing display for the PL/I demo program. This was covered in the basic\ndemo session.\n1.Press PF4 to display the Profile panel. Verify that the Display window is set to N and that the AutoKeep Display is ON.\nIf not, change either or both of them and press Enter.\nCA InterTest for CICS   - PROTSYM FILE  SOURCE LISTING PROFILE            \nCOMMAND ===>                                                                    \nProgram= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c16cece80a8e-1", "text": "Search=                                 \nOPTS 1 Data xref 2 Aggregate 3 Stor reqs  4 Stat stor  5 Var stor   More:   +   \n     6 Offsets   7 Gend code 8 Err msgs   9 Srch fwd  10 Srch bwd               \nPFKS 1 Help      2           3 End        4 Auto prms  5 Monitor    6 Menu      \n     7 Backward  8 Forward   9 Next Wnd  10           11           12 Status    \n---------+--------------------------------------------------------------------- \nDisplay window   = N         N (None), T (Titles), R (Registers),               \n                             K (Keep), P (Program)                              \nPF7/8 amount     = PAGE      PAGE, HALF, STOP, or a number from 1 to 9999       \nStep Timing      = BEFORE    Stop  Before  or  After  the next STMTS is executed\nStepping amount  = 001       The number of STMTS   to execute                   \nAuto-stepping    = OFF       ON to activate; press PF4 to change values         \nSource List BKPT = ON        OFF to use the detailed breakpoint display         \nFrom terminal ID = U006      Terminal ID where the program will execute         \nBKPT terminal ID = U006      Terminal ID to receive the breakpoint displays     \nUser ID          = .ANY      User ID who will execute this program              \nAutoKeep Display = ON        OFF to deactivate                                  \nCode Counting    = OFF       ON to activate Code Coverage                       \nSDF              = DATA      DATA for Structure Display Format                 \n2.Press PF3 to return to the listing.\nNow you will set unconditional breakpoints at three procedure names. Setting unconditional breakpoints lets you halt\nthe program so that you can set options and check the contents of data items.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c16cece80a8e-2", "text": "the program so that you can set options and check the contents of data items.\n3.Start by searching for the label READATA. Tab to the Search= field, type l readata  in the command line and press\nEnter.\n 528", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6e144da6e0b4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCA InterTest for CICS  - PROTSYM FILE  SOURCE LISTING DISPLAY            \nCOMMAND ===> l readata                                                          \nProgram= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _    18.1            /*   INTERTEST PL/I DEMO PROGRAM   10/01/89  3.1.200      \n _    19.1            PL1DEMO:  PROC(DFHEIPTR,COMMAREA_PTR) OPTIONS(MAIN REENT  \n _    20.1     1      DCL 1 DFHCNSTS  STATIC,  /* CONSTANTS USED BY TRANSLATOR  \n _    21.1                   2  DFHLDVER CHAR(22) INIT('LD TABLE DFHEITAB 530.  \n _    22.1                   2  DFHEIB0 FIXED BIN(15) INIT(0),                  \n _    23.1                   2  DFHEID0 FIXED DEC(7) INIT(0),                   \n _    24.1                   2  DFHEICB CHAR(8) INIT('        ');               \n _    25.1     1      DCL DFHEPI ENTRY, DFHEIPTR PTR;                           \n _    26.1     1      DCL 1 DFHEIBLK BASED (DFHEIPTR),                          \n _    27.1                  02    EIBTIME  FIXED DEC(7),                        \n _    28.1                  02    EIBDATE  FIXED DEC(7),                        \n _    29.1                  02    EIBTRNID CHAR(4),", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6e144da6e0b4-1", "text": "_    29.1                  02    EIBTRNID CHAR(4),                             \n _    30.1                  02    EIBTASKN FIXED DEC(7),                        \n _    31.1                  02    EIBTRMID CHAR(4),                             \n _    32.1                  02    EIBFIL01 FIXED BIN(15),                       \n _    33.1                  02    EIBCPOSN FIXED BIN(15),                       \n _    34.1                  02    EIBCALEN FIXED BIN(15),                       \n _    35.1                  02    EIBAID   CHAR(1),                             \n _    36.1                  02    EIBFN    CHAR(2),                            \nThe READATA label appears.\nYou will set unconditional breakpoints at the statement:\nGOTO SENDMP00\n4.Tab to the GOTO SENDMP00 statement.\n5.Type U to the left of the statement, and press Enter. The U sets a breakpoint that stops before  the statement executes.\nYou could also type a ) to set a breakpoint that stops after the statement executes.\nCA InterTest for CICS   - PROTSYM FILE  SOURCE LISTING DISPLAY            \nCOMMAND ===>                                                                    \nProgram= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n---------+--------------------------------------------------------------------- \n u  1308.1     1             GOTO SENDMP00;                                     \n _  1309.1                                                                      \n _  1310.1     1      READATA:                                                  \n _  1311.1                   /* EXEC CICS HANDLE CONDITION  DSIDERR             \n _  1312.1                                                  ERROR    (GENERR)   \n _  1313.1                                                  NOTOPEN  (NOPEN) *", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6e144da6e0b4-2", "text": "_  1313.1                                                  NOTOPEN  (NOPEN) *  \n _  1314.1                   DO; \n.\n.\n.                                              \nInterTest for CICS sets the breakpoint and redisplays the screen with an uppercase U.\n 529", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f9e10094e4d4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSet an Unconditional Breakpoint for a Label\nNow you will set a second unconditional breakpoint at the LOOPRTN label from the Labels Cross-Reference section.\nWhen you set the breakpoint from the Labels Cross-Reference section, it is set at the label name and not at the statement\nnumber. This is a good method to use if you want to use the breakpoint after recompiling -- the breakpoint is transferred to\nthe new program by label-name, and not by statement-number (which might change between compiles).\n1.Type L .LX  in the command line or type 14 in the Option # field, and press Enter .\nThe Labels Cross-Reference section of PL1DEMO appears.\nCA InterTest for CICS   - PROTSYM FILE  SOURCE LISTING DISPLAY            \nCOMMAND ===>                                                                    \nProgram= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _                   LABEL ATTRIBUTE/XREF TABLE                                 \n        LINE.FILE IDENTIFIER                      ATTRIBUTES                    \n _      1646.1    CALLCOMP                        CONSTANT LABEL                \n                                                  Refs: 1643.1                  \n _       857.1    CONTINUE                        CONSTANT LABEL                \n                                                  Refs: 846.1                   \n _       635.1    CONTINUE_TASK                   CONSTANT LABEL                \n                                                  Refs: 596.1                   \n _      1193.1    DSIDERR                         CONSTANT LABEL                \n                                                  Refs: 558.1 1269.1            \n _       704.1    END_SESSION                     CONSTANT LABEL                \n                                                  Refs: 542.1 576.1 640.1 643+  \n                                                        666.1 859.1 868.1 882+", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f9e10094e4d4-1", "text": "666.1 859.1 868.1 882+  \n                                                        944.1 969.1 994.1 101+  \n                                                        1044.1 1068.1 1091.1    \n                                                        1114.1 1137.1 1160.1    \n                                                        1191.1 1391.1 1487.1    \n                                                        1644.1                  \n _       744.1    EXPANDEM                        CONSTANT LABEL\n2.Press PF8 to page forward.\n3.Type U to the left of the LOOPRTN label, and press Enter. The U sets a breakpoint that stops before  the label name.\nYou could also type a ) to set a breakpoint that stops after the label name.\nCA InterTest for CICS   - PROTSYM FILE  SOURCE LISTING DISPLAY            \nCOMMAND ===>                                                                    \nProgram= PL1DEMO  Option # 9     Stmt #                             Margin= 01  \n                                        Search= LOOPRTN                         \n--------------+---------------------------------------------------------------- \n _                     ATTRIBUTE/XREF TABLE-                                    \n        LINE.FILE IDENTIFIER                      ATTRIBUTES                    \n                                                  Refs: 709.1 1213.1 1235.1 1+  \n         515.1    LENGTH                          BUILTIN                       \n u      1435.1    LOOPRTN                         CONSTANT LABEL                \n                                                  Refs: 970.1 995.1             \n _       773.1    MAPNUM                          AUTOMATIC CHARACTER(2) UNAL+  \n                                                  Refs: 906.1                   \n                                                  Sets: 635.1 860.1 922.1 947+  \n                                                        972.1 997.1 1022.1 16+  \n 530", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f1ec57e70583-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _      1536.1    MORE_ENTRY                      CONSTANT LABEL                \n                                                  Refs: 903.1    \n.\n..\nInterTest for CICS sets the breakpoint at the LOOPRTN label and redisplays the screen with an uppercase U.\nHow to Set Request Breakpoints\nYou can set request breakpoints to halt a program before CICS commands and macros and other calls, such as calls to\nDL/I or DB2. You can set request breakpoints prior to all CICS commands (as you might have done with IBM's CEDF) or\nprior to specific commands, such as File Control or Program Control commands. Request breakpoints make it easy for\nyou to halt your program at various points so you can check program processing. For example, you can halt the program\nbefore every READ command, single-step through the read instructions, and then check main storage to make sure the\nprogram has read the correct record.\nFor option 03 of the advanced demo session, you need to set request breakpoints at all File Control REWRITE commands\nin the demo program. To do this, access the Request Breakpoint Selection menu.\n1.Press PF6 to return to the Primary Option Menu.\n2.Select  2 Monitoring .\nThe Monitoring Menu appears.\n3.Select 1 Programs.\nThe Program Monitoring screen appears.\n-------------------- CA InterTest for CICS  PROGRAM MONITORING  --------------------\n COMMAND ===>                                                                   \n                                                                                \n   Type information and S to set or R to remove option(s) below.               \n                                                                                \n   Program  . . PL1DEMO_     Program name (or .ALL, .OPTIONS or generic)        \n   User ID  . . ________     User (or .ANY) for whom the program is monitored   \n                                                                                \n   Option       Description                                            More:   +", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f1ec57e70583-1", "text": "Option       Description                                            More:   +\n _ Status       Display and/or remove monitoring options (S only)               \n _ Monitor      Monitoring (R removes monitoring and all options previously set)\n _ UBP          Unconditional breakpoints (specific program only)               \n _ CBP          Conditional breakpoints (specific program only)                 \n s RBP          Breakpoints for CICS, DB2, DL/I or external CALL requests       \n _ Stmt Trace   Statement tracing and data monitoring (COBOL only) \n _ New copy     Fetch new copy of program and reset monitoring options (S only) \n _ Commands     Indirect commands defined for a specific COBOL or PL/I program \n _ Replace      CICS resource name replacement options                          \n _ Protect      Storage protection monitoring options                          \n _ Special      Other options (storage allocation, file updating, etc.)         \n _ Composite    Monitor multi-CSECT program's separately compiled components \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6     \n PF7 Backward   8 Forward    9           10           11           12      \n4.In the Program field, type the name of the program for which you want to set a request breakpoint.\n5.Type S to the left of RBP (request breakpoints) and press Enter.\nThe Request Breakpoint Selection menu appears on which you specify the type of request breakpoint, such as all\nCICS commands, File Control, Task Control, and so on.\n6.Tab to the File Control field and type S.\n 531", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5655f81a67c9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n7.Press Enter.\nCA InterTest MONITORING COMMAND BUILDER - REQUEST BREAKPOINT SELECTION  13\n                                                                               \n             Set  one or more types of Request Breakpoints in:                 \n                               PROG=PL1DEMO                                    \n                                                                               \n_ ALL commands                    _ DL/I              _ CALLs                  \n                                                                               \n  _ Address, Assign,         _ Storage Control    _ BMS                        \n      Handles, Push, Pop     _ Program Control    _ Trace Control              \n  _ Terminal Control         _ Interval Control   _ Dump Control               \n  s File Control             _ Task Control       _ Batch Data Interchange     \n  _ TD Control               _ Journal Control    _ Built-In Functions         \n  _ TS Control               _ Syncpoints         _ Sys Prog Functions         \n  _ Web access               _ Business Trans     _ 3270 Bridge                \n  _ Channel/Container                                                          \n                                                                               \n  Enter 'n' to stop only every n'th time:                         ____         \n  Term ID (or .ANY or .NO) where breakpoints will take effect:    ____         \n  Term ID (or .ANY) that will receive the breakpoints:            ____         \n  Statement no. of indirect command(s) to be executed:            _____        \n  User ID (or .ANY) who will execute the program:                 ________     \n                                                                               \nPF1 Help       2            3 End        4 Return     5            6           \nPF7            8            9           10           11           12\nThe File Control Request Breakpoint Selection menu appears.\n8.On this menu you can select the specific File Control commands where you want to set request breakpoints. In this\ncase, select REWRITE to halt the program prior to each File Control REWRITE command.\n9.Tab to the REWRITE command field.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5655f81a67c9-1", "text": "9.Tab to the REWRITE command field.\n10.Type an s and press Enter.\nCA InterTest for CICS MONITORING COMMAND BUILDER - REQUEST BREAKPOINT SELECTION \n                                                                                \n            Set  one or more types of File Control COMMANDS IN:                 \n                                PROG=PL1DEMO                                    \n                                                                                \n              _ All commands                                                    \n                                                                                \n                    _ READ                                                      \n                    _ WRITE                                                     \n                    s REWRITE                                                   \n                    _ DELETE\n.\n.\n. \nInterTest for CICS sets request breakpoints prior to each File Control REWRITE command in the demo program and\nredisplays the Program Monitoring Menu.\nThe next topic is necessary only if you want to use the composite support option. Composite support is an InterTest for\nCICS feature designed to aid programmers who are responsible for testing and debugging called subroutines.\n 532", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3c2861402b17-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022If you do not want to use the composite support option, skip to Execute the Demo Program.\n\u2022If you do want to use the composite support option, perform the steps in Composite Support that follows.\nComposite Support\nComposite support lets you use InterTest for CICS to test and debug composite modules. A composite module   is a load\nmodule (defined in the PPT) that consists of separately compiled or assembled parts brought together when the module\nis link-edited. In the demo session, the part of the composite module that receives control from CICS is referred to as the\nmain program ; the remaining programs are referred to as subroutines . The main program and subroutines can be written\nin the same or different languages.\nComposite support lets you test and debug a subroutine, such as an external procedure, as if it were a separate\nprogram with full symbolic support. This means you can set breakpoints and other monitoring options individually for any\nsubroutine. InterTest for CICS also generates automatic breakpoints in the subroutine when it detects an error that would\notherwise cause the program to abend.\nTo demonstrate this feature, you will set composite support for the composite module PL1DEML, to which PL1DEMO\nlinks. PL1DEML has two called subroutines that you want InterTest for CICS to monitor -- subroutine PSBIN25 written in\nPL/I, and subroutine ASBIN25 written in Assembler.\nFollow these steps:\n1.In the Program Monitoring Menu, type =X in the Command line, and press Enter to exit the menus and return to the\nSource Listing Display.\n2.In the Program field, overtype PL1DEMO with PL1DEML , and press Enter.\nCA InterTest for CICS  - PROTSYM FILE SOURCE LISTING DISPLAY              \nCOMMAND ===>", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3c2861402b17-1", "text": "COMMAND ===>                                                                   \nProgram= PL1DEML  Option #       Stmt #                             Margin= 01  \n                                        Search=                                \n---------+---------------------------------------------------------------------\n.\n.\n. \nThe source listing for the composite module PL1DEML appears.\n3.Type COMPOSITE on the command line and press Enter.\n       CA InterTest for CICS - Composite Support Builder                   \n COMMAND ===>                                                      SCROLL: PAGE\n Define composite support for PL1DEML  and press PF5.        Row 00001 of 00006 \nCAIN2620 Not all subprograms are selected                                      \n                                                                                \n * *          *          *        *        *           *                        \n _ Link name  Monitor    Offset   Length   Language    Comments                 \n S PL1DEML1   PL1DEML        80      248   PL/I   4.3                           \n S PSBIN251   PSBIN25       EE8      1B0   PL/I   4.3                           \n S ASBIN25    ASBIN25      1098      17C   HLASM  6.0                           \n _ @PL1DEML   ________     1218       10               Symbolics NOT available  \n _ PLIXOPT    ________     1228        8               Symbolics NOT available  \n _ @PSBIN25   ________     1230        8               Symbolics NOT available  \n                                                                                \n                                                                                \n PF1 Help       2            3 End        4            5 Process    6 RFind     \n PF7 Backward   8 Forward    9           10           11           12           \n 533", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7b6cdbd6717b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n4.Press PF5 to activate composite program monitoring for PL1DEML.\nExecute the Demo Program\nNow you are ready to execute the demo program PL1DEMO.\n1.Type =X in the Command field to exit the menus, and then use PF3 to exit Source Listing.\nYou return to CICS.\n2.On a clear CICS screen, type the transaction identifier of the PL/I demo program you will be using: DEMP. Press Enter.\nThe following Welcome Screen appears.\n  ******************************************************************************\n  ******************************************************************************\n  *****                                                                    *****\n  *****                        Welcome to the                              *****\n  *****                  CA InterTest Demo Session                         *****\n  *****                                                                    *****\n  *****                                                                    *****\n  *****             Before proceeding, please have on hand the             *****\n  *****             guide which accompanies the Demo Session.              *****\n  *****                                                                    *****\n  *****                                                                    *****\n  *****    Please make sure that the program PL1DEMO is monitored by       *****\n  *****    CA InterTest. This program will abend if not being monitored.   *****  \n  *****                                                                    *****\n  *****    To turn the monitor on, press CLEAR and follow the steps        *****\n  *****    outlined in the documentation.                                  *****\n  *****                                                                    *****\n  *****    If the monitor is already on, press ENTER to begin the          *****\n  *****    Basic Demo Session or PF2 to go to the Options Menu.            *****\n  *****                                                                    *****\n  ******************************************************************************\n  ******************************************************************************\nFrom the Welcome Screen you can access the Options Menu. Each of the options is detailed in the sections that\nfollow\n3.Press PF2 to go to the Options Menu of the demo .\nThe demo program displays the Options Menu, as shown next.\n    **********************************************************************\n    ****                                                              **** \n    ****             CA InterTest Demo Session                        ****", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7b6cdbd6717b-1", "text": "****                                                              **** \n    ****             CA InterTest Demo Session                        ****   \n    ****                         Options Menu                         ****      \n    ****                                                              ****      \n    **********************************************************************      \n                                                                                \n    01  Replace file control ID                                                 \n    02  Limit CICS storage and requests                                         \n    03  No file updating                                                        \n    04  Storage violation detection                                             \n    05  Composite support                                                       \n                                                                                \n                                                                               \n                                                                                \n 534", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ab1857483f46-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                 Key in request:  01                            \n                                                                                \n         Press ENTER to continue or CLEAR to terminate                          \n                                                                                \n                                                                               \nOption 01 Replace a File Control ID\nThis section of the demo session details how to replace a File Control ID. The demo program PL1DEMO is attempting to\nread and display a record, but the file name specified in the program is incorrect, possibly because it was misspelled.\nWARNING\nBefore proceeding, be sure you have completed the steps outlined in the Demo Preliminaries section, and that\nyou have the InterTest for CICS Demo Session Options Menu displayed on your screen.\n1.Select option 01  and press Enter.\nThe demo program displays the following screen, which describes what occurs in this part of the demo session.\n    **********************************************************************      \n    ****                                                              ****      \n    ****                 CA InterTest Demo Session                    ****      \n    ****                Replace File Control ID Option                ****      \n    ****                                                              ****      \n    **********************************************************************      \n                                                                                \n    The program attempts to read file PROTH. Because the file name has been     \n    incorrectly specified, this would cause a DSIDERR condition which would     \n    result in an AEIL abend. Instead, here is what will happen:                 \n                                                                                \n    1. CA InterTest halts the program at an automatic breakpoint.             \n    2. You set the Replace File Control option to change the file name          \n       without recompiling.                                                   \n    3. You re-execute the program from the point at which it first tried        \n       to read the file.                                                      \n                                                                                \n                                                                                \n    When this section of the demo completes, you will return to the             \n    Options Menu.                                                             \n                                                                                \n              Press ENTER to continue or CLEAR to terminate\n2.Press Enter.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ab1857483f46-1", "text": "Press ENTER to continue or CLEAR to terminate\n2.Press Enter.\nInterTest for CICS halts the demo program at an automatic breakpoint.\nPrevent an AEIL Abend\nThe following screen shows that InterTest for CICS halted the demo program at an automatic breakpoint (note the A in\ncolumn 1) before an AEIL abend could occur.\nCA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \nCOMMAND ===>                                                                    \nProgram= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n---------+--------------------------------------------------------------------- \n 535", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "614269deb453-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _  1321.1     1             RECKEY = '0000000000';                             \n _  1322.1                   /* EXEC CICS STARTBR DATASET('PROTH') RIDFLD(RECK  \n A   ==>.1     1             DO;      ==>                                    \n     ==> CICS abend intercepted. Abend code = AEIL.   EXEC CICS request was  \n     ==> STARTBR. Now stopped AFTER the CALL.                                \n     ==>                                                                     \n     ==>      Press PF1 for a detailed description.                          \n     ==>                                                                     \n                                                                             \n _  1324.1     1  1          DCL DFHENTRY_BF6577CC_B2C81A6B BASED(ADDR(DFHEI0)  \n _  1325.1             ASSEMBLER) ENTRY(*,CHAR(8),*,FIXED BIN(15),*);           \n _  1326.1     1  1          CALL DFHENTRY_BF6577CC_B2C81A6B(' .^. . \u00b5.0433000  \n _  1327.1             00 03 00 20 A0 00 F0 F4 F3 F3 F0 F0 F0 F1 'X */,'PROTH'  \n _  1328.1            FHEIB0,RECKEY);                                           \n _  1329.1     1  1          END;                                               \n _  1330.1     1             REC_LEN = 0;                                       \n _  1331.1                   /* EXEC CICS READNEXT DATASET('PROTH')             \n _  1332.1                                     SET(REC_PTR)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "614269deb453-1", "text": "_  1332.1                                     SET(REC_PTR)                     \n _  1333.1                                     RIDFLD(RECKEY)\nWhat's the problem?\nThe data set name PROTH is wrong; it should be PROTHLF.\nHow can it be fixed?\nInterTest for CICS lets you dynamically correct the file name and continue testing. The following section explains how.\nChange the File Name\nInterTest for CICS lets you dynamically change an incorrect file name in the middle of your test session, allowing you\nto continue testing without recompiling your program. In this case, you can correct a simple typo in the demo program\nwithout interrupting your test session or changing your File Control Table.\nTo change the file name, you need to access the Program Monitoring Replacement Options menu.\n1.Specify RO on the command line.\n2.Press Enter.\nThe Replacement Options menu appears.\nThe Set Replacement Options menu lets you dynamically change a program name, file name, transient data queue\nname, or temporary storage ID.\n3.Tab to the Replace file name field.\n4.Specify the incorrect file name (proth) in the first column and the correct file name (prothlf) in the second column, and\npress Enter.\nCA InterTest for CICS MONITORING COMMAND BUILDER - REPLACEMENT OPTIONS     20\n                                                                                \n     SET one or more options to replace one CICS resource name with another in: \n                                PROG=PL1DEMO                                    \n                                                                                \n                                                                                \n      Replace program name:         ________   with   ________                  \n      Replace file name:            proth___   with   prothlf_                  \n      Replace TD queue name:        ____       with   ____                      \n      TS selection mask:            ____________________________________        \n 536", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b6033e499409-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n      TS replacement mask:          ____________________________________        \n                                                                                \n      Limit monitoring to your terminal - '*'  or TERMID:       ____            \n      User ID (or .ANY) who will execute the program:           ________\n.\n.\n.                                                                            \nInterTest for CICS dynamically replaces the incorrect file name when the program executes. InterTest for CICS then\nredisplays the Program Monitoring menu.\n5.Press PF4 until the Source Listing Breakpoint Screen reappears.\nResume Execution\nNow that you have dynamically corrected the file name, you are ready to resume program execution. However, you must\nback up to and execute the statement that contains the EXEC CICS STARTBR command with the incorrect file name,\nrather than resume execution at the statement that triggered the breakpoint.\n1.On the Source Listing Breakpoint screen,  tab to the DO statement following the EXEC CICS STARTBR command and\ntype G (go).\n2.Press Enter  to resume program execution.\nCA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \nCOMMAND ===>                                                                    \nProgram= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n---------+--------------------------------------------------------------------- \n _  1321.1     1             RECKEY = '0000000000';                             \n _  1322.1                   /* EXEC CICS STARTBR DATASET('PROTH') RIDFLD(RECK  \n g   ==>.1     1             DO;                                              \n _  1324.1     1  1          DCL DFHENTRY_BF6577CC_B2C81A6B BASED(ADDR(DFHEI0)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b6033e499409-1", "text": "_  1325.1             ASSEMBLER) ENTRY(*,CHAR(8),*,FIXED BIN(15),*);           \n _  1326.1     1  1          CALL DFHENTRY_BF6577CC_B2C81A6B(' .^. . \u00b5.0433000  \n _  1327.1             00 03 00 20 A0 00 F0 F4 F3 F3 F0 F0 F0 F1 'X */,'PROTH'  \n _  1328.1            FHEIB0,RECKEY);                                           \n _  1329.1     1  1          END;                                               \n _  1330.1     1             REC_LEN = 0;                                       \n _  1331.1                   /* EXEC CICS READNEXT DATASET('PROTH')             \n _  1332.1                                     SET(REC_PTR)                     \n _  1333.1                                     RIDFLD(RECKEY)                   \n _  1334.1                                     LENGTH(REC_LEN) */               \n _  1335.1     1             DO;                                                \n _  1336.1     1  1          DCL DFHENTRY_BF6577CC_B2D0406B BASED(ADDR(DFHEI0)  \n _  1337.1             ASSEMBLER) ENTRY(*,CHAR(8),POINTER,FIXED BIN(15),*,*,FI  \n _  1338.1     1  1          CALL DFHENTRY_BF6577CC_B2D0406B('0000011000001110", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b6033e499409-2", "text": "_  1339.1            00000001100000001000000001011000000000000111100001111010 \nThe program resumes execution and displays the record it has read on your screen as shown in the following screen.\nThe demo program has succeeded in reading a record from file PROTHLF (the InterTest for CICS Help file). The demo\nprogram displays the first record in that file.\n    ********************************************************************** \n    ****                                                              ****      \n    ****                  CA InterTest Demo Session                   ****      \n    ****             Replace File Control Identifications             ****      \n 537", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a61aecf85880-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    ****                                                              ****      \n    **********************************************************************      \n                                                                                \n                                                                                \n                                                                                \n         Record retrieved: * 0000000000    VE0301InterTest ZELP Facil *         \n                           * ity Master Menu                          *         \n                           *                                          *         \n                           *                                          *         \n         Record length = 0960                                                   \n                                                                                \n                                                                                \n                                                                                \n         You have now successfully utilized the REPLACE option                  \n                                                                                \n                                                                                \n         Press ENTER to continue or CLEAR to terminate                         \nReview What Happened\nIn this part of the demo session:\n\u2022InterTest for CICS halted the demo program at an automatic breakpoint caused by an incorrect file name\n\u2022You dynamically corrected the file name and resumed program execution.\nReplacing the incorrect file name in the demo program allowed you to continue testing that program without recompiling it.\nOf course, if one of your programs or the CICS FCT has an incorrect file name, you would eventually have to correct the\nsource code.\nIn this case the error was caused by a typo. However, the Replacement Options are useful in many situations. For\nexample:\n\u2022You can dynamically change a file name to test a program using a different file. This allows you to use a test file\nwithout altering the name of the production file hard coded in the program.\n\u2022You can change a program name or transient data queue name to test a program or queue other than the ones that\nare hard coded.\nThis concludes Option 01 of the advanced demo session. Press Enter to continue with the demo session or press Clear to\nterminate the session.\nOption 02 Limit CICS Storage and Requests\nThis section of the demo session shows how to limit CICS main storage and CICS requests for a specific program (the\ndemo program). Two InterTest for CICS options are detailed in this part of the demo session:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a61aecf85880-1", "text": "demo program). Two InterTest for CICS options are detailed in this part of the demo session:\n\u2022The MXS option limits the amount of main storage obtained by a task. This option is useful in detecting program errors\nthat cause a task to acquire an excessive amount of storage.\n\u2022The MXR option limits the number of CICS requests, commands, and macros that a program can issue. This option is\nuseful in detecting program loops that generate an excessive number of CICS requests.\nWARNING\nBefore proceeding, be sure you have completed the steps outlined earlier in this article in Demo Preliminaries,\nand that you have the InterTest for CICS Demo Session Options Menu displayed on your screen.\n1.Select option 02, and press Enter.\nThe demo program displays a screen that describes what will occur in this part of the demo session.\n 538", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1aa8398a7ea1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    **********************************************************************     \n    ****                                                              ****     \n    ****                 CA InterTest Demo Session                    ****     \n    ****          MXR Option - Limit Number of CICS Requests          ****     \n    ****          MXS Option - Limit Amount of CICS Storage           ****     \n    ****                                                              ****     \n    **********************************************************************     \n                                                                               \n    The program has a loop containing a CICS request and another loop          \n    containing a GETMAIN request. Here is what will happen:                    \n                                                                               \n    1. The program is halted at an unconditional breakpoint before the loops. \n    2. You set the MXS and MXR options to limit storage and CICS requests.    \n    3. The program continues to execute.                                      \n    4. CA InterTest halts the program at automatic breakpoints when the         \n       limits are exceeded.                                                   \n    5. You remove the options and the program completes execution.            \n                                                                                \n                                                                                \n                                                                                \n    When this section of the demo completes, you will return to the             \n    Options Menu.                                                             \n                                                                                \n              Press ENTER to continue or CLEAR to terminate\n2.Press Enter.\nInterTest for CICS halts the program at the procedure name LOOPRTN label because you set an unconditional\nbreakpoint there as part of the Demo Preliminaries.\nNow you can access Special Options from the Program Monitoring menu to set the options you need for testing.\nSet the MXS and MXR Options\n1.Type SO in the command line.\n2.Press Enter.\nThe Special Options menu appears.\nThe Special Options menu lets you set several options to change how InterTest for CICS monitors a program. You are\ngoing to set two options:\n\u2013MXS, to limit the amount of CICS main storage acquired by the demo program", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1aa8398a7ea1-1", "text": "\u2013MXS, to limit the amount of CICS main storage acquired by the demo program\n\u2013MXR, to limit the total number of CICS requests issued by the demo program\n3.Specify 50,000 bytes as the maximum amount of main storage the demo program can get, and specify 20 as the\nmaximum number of CICS requests the demo program can issue.\n4.Tab to the MXS field and type in 135000, as shown next.\n5.Tab to the MXR field and type in 20, as shown next.\n6.Press Enter.\nCA InterTest MONITORING COMMAND BUILDER - SPECIAL OPTIONS         22\n                                                                                \n      SET  one or more options to override the default monitoring rules in:     \n                                PROG=PL1DEMO                                    \n                                                                                \n           Enter X next to each option desired:                                 \n                                                                                \n                 Source Listing Breakpoint      (SLB) _                         \n 539", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "abbaa301b93b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                 No file updating               (NUP) _                         \n                 Reentrancy check               (RNT) _                         \n                                                                                \n           Follow monitoring (ON, name, NOPPT)  (FOL) ________                  \n           Number of times to be monitored      (MUS) _____                     \n           Limit total size of CICS storage     (MXS) 135000                   \n           Limit total number of CICS requests  (MXR) 20_____                   \n           Structure Display Format (HEX,DATA)  (SDF) ____                      \n                                                                                \n           Set local automatic breakpoint ('*', TERMID, .ANY, OFF)     ____     \n           Limit monitoring to your TERMINAL - '*' or TERMID:          ____     \n           User ID (or .ANY) who will execute the program:             .ANY     \n                                                                                \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7            8            9           10           11           12\nInterTest for CICS limits main storage and CICS requests for the demo program and redisplays the Program\nMonitoring screen.\n7.Press PF4 until you are returned to the Source Listing Breakpoint screen.\n8.Press PF5 to continue program execution.\nThe demo program resumes execution.\nLimit CICS Requests\nThe next screen is an automatic breakpoint display screen. InterTest for CICS halted the demo program at an automatic\nbreakpoint because the maximum number of CICS requests (20) was exceeded.\nNOTE\nIf you are working on a system with LE 370 runtimes, you might reach the automatic breakpoint for the MXS\n(max storage size) first.\nIf you do, perform the demo in the following order:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "abbaa301b93b-1", "text": "(max storage size) first.\nIf you do, perform the demo in the following order:\n1.Remove the MXS options by typing STATUS, in the command line then 'R' next to the MXS option, and press enter.\nResume execution.\n2.After stopping for the MXR trigger value, remove it the same as the MXS and continue.\n3.The Demo will execute to completion.\nThe instruction that triggered the automatic breakpoint is within a loop containing a CICS request.\nCA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \nCOMMAND ===>                                                                    \nProgram= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n---------+--------------------------------------------------------------------- \n _  1436.1                   DO I = 1 TO 50;                                    \n _  1437.1                      /* EXEC CICS ASKTIME */                         \n A   ==>.1     1  1             DO;      ==>                                 \n     ==> MXR (max CICS requests) trigger value exceeded.                     \n     ==>                                                                     \n     ==>      Press PF1 for a detailed description.                          \n     ==>                                                                     \n                                                                             \n _  1439.1     1  2             DCL DFHENTRY_BF6577CC_B372BAE6 BASED(ADDR(DFHE \n.\n 540", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "453ebb6ee9eb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n.\n.               \nRemove the MXR Option\nNow you can remove the MXR option so that the demo program continues executing. If this were your own program, you\nwould want to examine the instructions that are generating excessive CICS requests.\n1.Press PF12 , or type STATUS on the command line and press Enter.\nThe Monitoring Status appears.\n--------------- CA InterTest for CICS  MONITORING STATUS  ----------------\n COMMAND ===>                                                                   \n                                                                                \n   Type + to expand or - collapse option levels displayed below,                \n          or R to remove option(s).                                             \n                                                                       More:   +\n     Option     Description                Attributes                           \n _ - PL1DEMO    Program monitor entry      PL/I                                 \n     |          Waiting at breakpoint      Task 00087, ABP since 01:02 p.m.     \n _ - |-.ANY     User monitoring options    Active                               \n       |        Symbolic listing file      PROTSYM                              \n _     |-MXR    Maximum CICS requests      20                                   \n _     |-MXS    Maximum total storage      135000                               \n _ -   |-RBP    Request breakpoint(s)      REWRITE                              \n       |                                   DELETE                               \n       |        Option ID                  88A2A671                             \n       |        From, to terminals         U068, U068                           \n _ -   |-UBP    Unconditional breakpoint   #1308                                \n       |        Option ID                  813C8815                             \n       |        From, to terminals         U068, U068                           \n _ -   |-UBP    Unconditional breakpoint   'LOOPRTN'                            \n                                                                                \n PF1 Help       2 Refresh    3 End        4 Return     5 Collapse   6 Expand", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "453ebb6ee9eb-1", "text": "PF7 Backward   8 Forward    9           10           11           12          \n2.Remove the MXR option by typing an r next to the MXR breakpoint's entry and pressing Enter.\nInterTest for CICS removes the breakpoint.\n3.Press PF3 to return to the Source Listing Breakpoint screen.\n4.Press PF5 to resume program execution.\nLimit Acquisition of Storage\nThe next screen is an automatic breakpoint display. InterTest for CICS halted the demo program at an automatic\nbreakpoint because the maximum main storage limit of 135,000 was exceeded. In most cases, the instruction that\ntriggered the automatic breakpoint is within a loop that contains a GETMAIN request.\n    CA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT      \nCOMMAND ===>                                                                    \nProgram= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n---------+--------------------------------------------------------------------- \n _  1461.1     1  2             CALL DFHENTRY_BF6577CC_B381D92B('. {. ..\u00f0.0476  \n _  1462.1             C0 00 03 00 00 8C 00 F0 F4 F7 F6 F0 F0 F0 F0 'X */,GET_  \n 541", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d4e5dd2434ff-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n A   ==>.1     1  2             END;      ==>                                 \n     ==> MXS (max storage size) trigger value exceeded.                       \n     ==>                                                                      \n     ==>      Press PF1 for a detailed description.                           \n     ==>                                                                      \n                                                                              \n _  1464.1     1  1          END;                                               \n _  1465.1     1             GOTO SENDMP00;                                     \n _  1466.1     1      NOSTORG:  \n.\n.\n.                                                                   \nRemove the MXS Option\nNow you can remove the MXS option so that the demo program continues executing. If this were your own program, you\nwould want to examine the instructions that are causing the program to obtain excessive amounts of storage.\n1.Press PF12, or type STATUS on the command line and press Enter.\nThe Monitoring Status screen appears.\n --------------- CA InterTest for CICS  MONITORING STATUS ----------------\n COMMAND ===>                                                                   \n                                                                                \n   Type + to expand or - collapse option levels displayed below,                \n          or R to remove option(s).                                             \n                                                                       More:   +\n     Option     Description                Attributes                           \n _ - PL1DEMO    Program monitor entry      PL/I                                 \n     |          Waiting at breakpoint      Task 00087, ABP since 01:13 p.m.     \n _ - |-.ANY     User monitoring options    Active                               \n       |        Symbolic listing file      PROTSYM                              \n r     |-MXS    Maximum total storage      135000   \n.\n.\n.\n2.Remove the MXS option by typing an r next to the MXS breakpoint's entry and pressing Enter.\nInterTest for CICS removes the breakpoint.\n3.Press PF3 to return to the Source Listing Breakpoint screen.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d4e5dd2434ff-1", "text": "3.Press PF3 to return to the Source Listing Breakpoint screen.\nDemo Program Completes Execution\nPress PF5 to resume program execution.\nThe demo program completes execution. InterTest for CICS returns to the demo's Options Menu.\nReview What Happened\nIn this part of the test session you set two options to help test the demo program:\n 542", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0124fb3d8ff2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022The MXR option lets you limit the number of CICS requests the program could issue. When the demo program\nexceeded this limit, InterTest for CICS halted the program. This feature helps you find program instructions within a\nloop that generate an excessive number of CICS requests.\n\u2022The MXS option lets you limit the amount of main storage used by the program. When the demo program exceeded\nthe amount of storage you specified, InterTest for CICS halted the program.\nThis feature helps you find commands or macros within a loop that are getting excessive amounts of storage.\nThis concludes Option 02 of the advanced demo session. Press Enter to continue with the demo session or press Clear to\nterminate the session.\nOption 03 Prevent a Program from Updating a File\nThis section of the demo session details how to execute a program without having it update a file.\nThe No File Updating option is useful when you are testing a program. Preventing a program from updating a file means\nyour test data remains unchanged at the end of each program execution, so you can test the program repeatedly without\nhaving to recreate test data.\nMany programs can use the same test file without interfering with each other's work. You can even allow a test program to\nuse a production file because the integrity of the file is preserved.\nWARNING\nBefore proceeding, be sure you have completed the steps outlined earlier in this article in Demo\nPreliminaries and that InterTest for CICS Demo Session Options Menu is displayed on your screen. Also be sure\nthat the InterTest for CICS checkpoint file (PROTCPF) has been defined to your CICS region and that the file's\ncurrent status is Open and Enabled.\n1.Select option 03, and press Enter.\nThe demo program displays the following screen that describes what will occur in this part of the demo session.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0124fb3d8ff2-1", "text": "The demo program displays the following screen that describes what will occur in this part of the demo session.\n    **********************************************************************      \n    ****                                                              ****      \n    ****                   CA InterTest Demo Session                  ****      \n    ****                    No File Updating Option                   ****      \n    ****                                                              ****      \n    **********************************************************************      \n                                                                                \n    The program reads a record and changes data in the record. Here is          \n    what will happen:                                                           \n                                                                                \n    1. CA InterTest halts the program at a request breakpoint.                \n    2. You set the No File Updating option to prevent PL1DEMO from              \n       updating the file.                                                     \n    3. When PL1DEMO rewrites the file, the file is not updated.               \n    4. After the rewrite you use the FILE facility to confirm that the          \n       file has not been updated.                                             \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n    When this section of the demo completes, you will return to the             \n    Options Menu.                                                             \n                                                                                \n              Press ENTER to continue or CLEAR to terminate.                  \n2.Press Enter.\n 543", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f7853d5d3b47-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterTest for CICS displays a request breakpoint (note the R in column 1) shown in the following section's screen.\nHalt the Demo Program at a Request Breakpoint\nInterTest for CICS halted the demo program prior to the first File Control REWRITE command as you specified during the\nDemo Preliminaries section. The highlighted CALL instruction is part of the generated EXEC CICS REWRITE command.\nSetting request breakpoints lets you inspect the values of program variables and set options prior to all or specified CICS\ncommands and macros and other program calls.\nThe following screen shows InterTest for CICS halting the program prior to a REWRITE Statement.\nCA InterTest for CICS  - PROTSYM FILE   STEP  BEFORE  BREAKPOINT         \nCOMMAND ===>                                                                    \nProgram= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ CKPTNAME                        | PROTCPF                                \n _____ NUP_AREA                        |          THIS IS NOT A NAME  PRIME THE \n _____ REC_LEN                         | +00681.                                \n---------+--------------------------------------------------------------------- \n _  1289.1                                        FROM(NUP_AREA)                \n _  1290.1                                        LENGTH(REC_LEN) */            \n _  1291.1     1             DO;                                                \n _  1292.1     1  1          DCL DFHENTRY_BF6577CC_B2AB522B BASED(ADDR(DFHEI0)  \n _  1293.1             ASSEMBLER) ENTRY(*,CHAR(8),*,FIXED BIN(15));             \n  R   ==>.1     1  1          CALL DFHENTRY_BF6577CC_B2AB522B('  \\. .. .0423000", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f7853d5d3b47-1", "text": "_  1295.1             00 03 00 00 40 00 F0 F4 F2 F3 F0 F0 F0 F0 'X */,CKPTNAM  \n _  1296.1     1  1   LEN);  END;                                               \n _   ==>.1     1      REMBKPT: \n.\n.\n.\n1.Scroll backward to look at the EXEC CICS REWRITE command.\n2.Press PF7.\nThe following screen appears.\nCA InterTest for CICS - PROTSYM FILE   STEP  BEFORE  BREAKPOINT         \nCOMMAND ===>                                                                    \nProgram= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ CKPTNAME                        | PROTCPF                                \n _____ NUP_AREA                        |          THIS IS NOT A NAME  PRIME THE \n _____ REC_LEN                         | +00681.                                \n---------+--------------------------------------------------------------------- \n _  1282.1     1  1          CALL DFHENTRY_BF6577CC_B2A39FEB('  0. ..d.0416000  \n _  1283.1             00 03 00 00 84 00 F0 F4 F1 F6 F0 F0 F0 F0 'X */,CKPTNAM  \n _  1284.1            LEN,NUP_KEY);                                             \n _  1285.1     1  1          END;                                               \n _  1286.1     1      NUPWRITE:                                                 \n _  1287.1                   NUP_NAME = 'THIS IS NOT A NAME';                   \n 544", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3362e65866df-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _  1288.1                   /* EXEC CICS REWRITE DATASET(CKPTNAME)             \n _  1289.1                                        FROM(NUP_AREA)                \n _  1290.1                                        LENGTH(REC_LEN) */            \n _  1291.1     1             DO;                                                \n _  1292.1     1  1          DCL DFHENTRY_BF6577CC_B2AB522B BASED(ADDR(DFHEI0) \n.\n.\n. \nAccording to the EXEC CICS REWRITE command, the demo program updates the file PROTCPF (specified in the\nDATASET parameter of the EXEC CICS REWRITE command).\nWARNING\nIf you do not have the AutoKeep Display function running, to view the contents of DATASET(CKPTNAME),\nyou can type Search=ckptname to scroll to where it is defined, and then add it to the Keep window (type K\nnext to the line defining CKPTNAME and press Enter).\nThe Keep window shows the current value of CKPTNAME is indeed PROTCPF. To return to a breakpoint location,\npress Clear.\nHowever, you are going to set the No File Updating option to prevent the demo program from updating the file. To do\nso, access the Special Options menu as explained in the following section.\nThe No File Updating Option\nAs we did when we set and removed the MXR and MXS options, bring up the Program Monitoring screen. For\nconvenience, use the InterTest for CICS fast path feature to navigate to this screen.\n1.Type SO on the command line and press Enter.\nThe Special Options menu appears.\n2.Tab to the NUP field.\n3.Type X, and press Enter.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3362e65866df-1", "text": "2.Tab to the NUP field.\n3.Type X, and press Enter.\nCA InterTest for CICS MONITORING COMMAND BUILDER - SPECIAL OPTIONS         22\n                                                                                \n      SET  one or more options to override the default monitoring rules in:     \n                                PROG=PL1DEMO                                    \n                                                                                \n           Enter X next to each option desired:                                 \n                                                                                \n                 Source Listing Breakpoint      (SLB) _                         \n                 No file updating               (NUP) x                         \n                 Reentrancy check               (RNT) _                         \n                                                                                \n           Follow monitoring (ON, name, NOPPT)  (FOL) ________                  \n           Number of times to be monitored      (MUS) _____                     \n           Limit total size of CICS storage     (MXS) _______                   \n           Limit total number of CICS requests  (MXR) _______                   \n                                                                                \n           Set local automatic breakpoint ('*', TERMID, .ANY, OFF)     ____     \n           Limit monitoring to your TERMINAL - '*' or TERMID:          ____     \n           User ID (or .ANY) who will execute the program:             ________\n                                                                                \n                                                                                \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n 545", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d6a633c480bb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n PF7            8            9           10           11           12\nInterTest for CICS sets this option for the demo program.\n4.Type =X in the Command field and press Enter to return to the Source Listing Breakpoint screen.\nBefore resuming program execution, look at the statement just before the EXEC CICS REWRITE command:\nNUP_NAME = 'THIS IS NOT A NAME'\nPL1DEMO is supposed to move the data string THIS IS NOT A NAME to the data field NUP_NAME. If PL1DEMO\nactually updates the file, this data string displays at the beginning of the first record in that file.\n5.Press PF5 to continue program execution.\nThe demo program resumes execution.\nUse FILE to Inspect the Record\nInterTest for CICS now halts the demo program at an unconditional breakpoint that you set in the Demo Preliminaries\nsection.\n CA InterTest for CICS - PROTSYM FILE  UNCOND  BEFORE BREAKPOINT        \nCOMMAND ===>                                                                   \nProgram= PL1DEMO  Option #       Stmt #                             Margin= 01 \n                                        Search=                                \n-------------------------------------------------------------------------------\n _____ CKPTNAME                        | PROTCPF                               \n _____ NUP_AREA                        |          THIS IS NOT A NAME  PRIME THE\n _____ REC_LEN                         | +00681.                               \n---------+---------------------------------------------------------------------\n _  1305.1             00 03 00 00 50 00 F0 F4 F1 F1 F0 F0 F0 F0 'X */,DFHEID0 \n _  1306.1            NTLTRAN,NUPOFFCM,NUPONLEN);                              \n U   ==>.1     1  1          END;", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d6a633c480bb-1", "text": "U   ==>.1     1  1          END;                                            \n _  1308.1     1             GOTO SENDMP00;                                    \n _  1309.1                                                                     \n _  1310.1     1      READATA:                                                 \n _  1311.1                   /* EXEC CICS HANDLE CONDITION  DSIDERR            \n _  1312.1                                                  ERROR    (GENERR)  \n _  1313.1                                                  NOTOPEN  (NOPEN) * \n _  1314.1                   DO;         \n.\n.\n.                                      \nYou set the breakpoint at the paragraph immediately following the REWRITE command so you could use the InterTest for\nCICS FILE facility to confirm that the demo program did not, in fact, update the file.\n1.Press PF6.\nThe Breakpoint Primary Option Menu appears.\n2.Select option 1 Main Menu.\nThe Primary Option Menu appears.\n3.Select 4 Auxiliary storage.\nThe Auxiliary Storage Menu appears.\n4.Type a 1 in the Option field and protcpf for the file name.\n------------- CA InterTest for CICS  AUXILIARY STORAGE MENU  --------------\n OPTION  ===> 1                                                                 \n                                                                                \n 546", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e8487b30f87e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    Select an auxiliary storage type, specifying optional criteria below.     \n                                                                                \n    1  Files              - Display/select files for access                     \n    2  DB2 database       - Invoke DB2 SQL interface facility                   \n    3  DL/I database      - Access DL/I database                                \n    4  TD queues          - Display/select transient data queues for access     \n    5  TS queues          - Display/select temporary storage queues for access  \n                                                                                \n    Type specific or generic file/queue name(s):                                \n       (Valid mask characters are  *  and/or  +)                                \n                                                                                \n    protcpf_ ________ ________ ________ ________ ________ ________ ________\n.\n.\n.                                                                             \n5.Press Enter.\nThe File Selection menu appears.\n6.Type S next to the file name and press Enter.\nThe initial File Facility screen appears.\nDATATYPE= FC FILEID= PROTCPF  MODE=      LOG=ON  TODEST=         PASSWORD=     \nFUNC=      SUBFUNC=      RETMETH=        ARGTYP=     SRCHTYP=                   \nMESSAGE=                                                                        \n RETNRCID=                                                         CHGLEN=      \n    RCID=                                                                       \n    DATA=                                                          SIZE= 0000   \nFORMAT= D 00112233 44556677 8899AABB CCDDEEFF  *0123456789ABCDEF*              \nLOC 0000  ........ ........ ........ ........ ................              \n                                                                                \n                         \n  \n                      CA InterTest for CICS               \n                  Copyright \u00a9 SOLVE:Access  CA.  All rights reserved.                \n                                                                            \n \n-------------------------------------------------------------------------------\n1 Help       2 Format C   3 End        4 BEGB       5            6 DataType DL", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e8487b30f87e-1", "text": "7 Page bwd   8 Page fwd   9 Caps Off  10 Top       11 Bottom    12\n7.Press PF4  to begin a browse of the file.\nInterTest for CICS displays the first record in the PROTCPF file.\nDATATYPE= FC FILEID= PROTCPF  MODE=BROWSELOG=ON  TODEST=         PASSWORD=     \nFUNC= NEXT SUBFUNC=      RETMETH=        ARGTYP=     SRCHTYP=                   \nMESSAGE= CAIN0601 RECORD OBTAINED FOR VIEWING                                   \n RETNRCID=404040404040404040                                       CHGLEN=      \n    RCID=                                                                       \n    DATA=                                                          SIZE= 02A9   \nFORMAT= D 00112233 44556677 8899AABB CCDDEEFF  *0123456789ABCDEF*              \nLOC 0000  ........ ........ ........ ........ ................              \n  0000    40404040 40404040 4040405C 5C5C4040              ***    DSORG=VSKS    \n  0010    404040D9 C5C3D6D9 C440E3D6 40D7D9C9      RECORD TO PRI  RECFM=FB      \n  0020    D4C540E3 C8C540C3 C8C5C3D2 D7D6C9D5   ME THE CHECKPOIN  LRECL=02A9    \n 547", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "768bd1239baf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  0030    E340C6C9 D3C54040 405C5C5C 5C404040   T FILE   ****     BLKSIZE=0000  \n  0040    40404040 40404040 F0F3F1F4 F0F0F0F0           03140000  KEYPOS=0000   \n  0050    00000000 00000000 00000000 00000000   ................ KEYLEN=09     \n  0060    00000000 00000000 00000000 00000000   ................ STRNO=02      \n  0070    00000000 00000000 00000000 00000000   ................              \n  0080    00000000 00000000 00000000 00000000   ................ READ          \n  0090    00000000 00000000 00000000 00000000   ................ ADD           \n  00A0    00000000 00000000 00000000 00000000   ................ UPDATE        \n  00B0    00000000 00000000 00000000 00000000   ................ BROWSE        \n  00C0    00000000 00000000 00000000 00000000   ................ DELETE        \n-------------------------------------------------------------------------------\n1 Help       2 Format C   3 End        4 ENDB       5 PREV       6 DataType DL \n7 Page bwd   8 Page fwd   9 Caps Off  10 Top       11 Bottom    12\nThe previous screen displays the contents of the first record in both hexadecimal and character formats. It is clear from", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "768bd1239baf-1", "text": "looking at the character display that the data string THIS IS NOT A NAME has not been moved to the beginning of this\nrecord.\nNOTE\nSetting the No File Updating option prevented the demo program from updating this file, without affecting the\ndemo program's source code.\nBefore returning to the demo program, we will discuss some of FILE's capabilities.\nFILE Facility\nThe FILE facility lets you view, update, add and delete records, and search for character strings. You can perform these\nfunctions at any time (for example, while your program is at a breakpoint). You can use FILE with VSAM and BDAM files,\nDL/I and DB2 databases, temporary storage records, and transient data records. You can also use FILE when no program\nis executing to perform routine file maintenance.\nFILE displays records in dump format, character format, vertical format, and structured format. To display the record in\ndifferent formats, press PF2. For structured format, which displays records or DL/I segments on a field-by-field basis, you\nalso must identify the program containing the structure.\nExample\nTake advantage of the FILE facility when you are testing your own programs. You can use FILE to change your test\nrecords or to create additional records in the middle of a test session. You can also use FILE to make sure your program\nhas successfully updated a file.\nThe Demo Program Completes Execution\n1.Press Clear.\nInterTest for CICS redisplays the File Selection screen.\n2.Type =X in the Command field and press Enter to return to the Source Listing Breakpoint screen.\n3.Press PF5 to resume program execution.\nInterTest for CICS returns you to the demo program's Options Menu.\nReview What Happened\nIn this part of the demo session you took advantage of several InterTest for CICS features. You were able to:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "768bd1239baf-2", "text": "\u2022Use a request breakpoint to halt the demo program prior to the first File Control REWRITE command.\n 548", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b1e05b9d2a83-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nRequest breakpoints make it easy for you to halt your program at various points, such as before all HANDLE\nCONDITION commands or all Terminal Control commands. When your program halts, you can inspect main storage or\nauxiliary storage to detect errors and review program logic.\n\u2022Use the No File Updating option to prevent a program from updating a file.\nPreventing a program from updating a file means you can test a program repeatedly without having to recreate test\ndata. Many programs can share the same test file because no program will actually change it. A test program can even\nuse a production file without corrupting it.\n\u2022Display a record in a file.\nDisplaying a record in a file lets you see whether your program is working correctly. The FILE facility also lets you add,\ndelete, and update records to meet your individual testing needs and maintain files without special one-time programs.\nThis concludes Option 03 of the advanced demo session. Press Enter to continue with the demo session or press Clear to\nterminate the session.\nOption 04 How to Detect a Storage Violation\nThis section of the test session details how InterTest for CICS detects and prevents a storage violation and lets you\ncontinue testing.\nWARNING\nTo perform this section, you should have completed the steps outlined earlier in this article in Demo\nPreliminaries. The InterTest for CICS Demo Session Options Menu should be displayed.\n1.Select option 04, and press Enter.\nThe demo program displays a screen that describes what will occur in this part of the test session.\n    **********************************************************************      \n    ****                                                              ****      \n    ****                   CA InterTest Demo Session                  ****      \n    ****               Storage Violation Detection Option             ****      \n    ****                                                              ****      \n    **********************************************************************      \n                                                                                \n The program attempts to move data from one field to another. However,", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b1e05b9d2a83-1", "text": "The program attempts to move data from one field to another. However,         \n because the program has relinquished storage for the receiving field, a        \n storage violation would occur. Instead, here is what will happen:             \n                                                                                \n 1. CA InterTest halts the program at an automatic breakpoint.               \n 2. You inspect the FREEMAIN instruction which released the storage            \n     for the field.                                                           \n 3. You return to the breakpoint display. Then you go around the problem      \n     by continuing program execution from the statement following the one       \n     that triggered the breakpoint.                                           \n                                                                                \n                                                                                \n When this section of the demo completes, you will return to the Options Menu. \n                                                                                \n                                                                                \n                                                                                \n              Press ENTER to continue or CLEAR to terminate\n2.Press Enter.\nInterTest for CICS halts the demo program at an automatic breakpoint.\n 549", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d2f7f7042b20-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPrevent a Storage Violation\nThe next screen is a breakpoint display screen. InterTest for CICS halted the demo program at an automatic breakpoint.\nInterTest for CICS prevented the storage violation that would have resulted if the highlighted MOVE statement had been\nexecuted. InterTest for CICS has also inserted an A next to the statement to indicate an automatic breakpoint.\nCA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT        \nCOMMAND ===>                                                                   \nProgram= PL1DEMO  Option #       Stmt #                             Margin= 01 \n                                        Search=                                \n-------------------------------------------------------------------------------\n _____ CKPTNAME                        | PROTCPF                               \n _____ NUP_AREA                        |          THIS IS NOT A NAME  PRIME THE\n _____ REC_LEN                         | +00681.                               \n _____ INPUT_REC_2                     | .........................             \n _____ OUTPUT_REC_2                    | .........................             \n---------+---------------------------------------------------------------------\n _  1431.1     1  1          END;                                              \n _  1432.1     1             OUTPUT_REC_2     =  INPUT_REC_2;                  \n  A   ==>.1     1             INPUT_REC_2      =  OUTPUT_REC_2;      ==>            ==> an attempt to change\n an area that does not belong to this task.           ==> Possible system damage has been prevented.         \n                       ==>                                                                           ==>     \n Press PF1 for a detailed description.                          \n     ==>                                                                       \n                                                                               \n _  1434.1     1             GOTO SENDMP00;                                    \n _  1435.1     1      LOOPRTN:                                                 \n _  1436.1                   DO I = 1 TO 50;                                   \n _  1437.1                      /* EXEC CICS ASKTIME */", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d2f7f7042b20-1", "text": "_  1437.1                      /* EXEC CICS ASKTIME */\nPreventing storage violations is one of the most important reasons to monitor programs. Storage violations are notorious\nCICS errors that can:\n\u2022Bring down your CICS system.\n\u2022Cause a program to produce erroneous data.\n\u2022Cause one program to corrupt the data of another program. In this case, tracking down the problem without InterTest\nfor CICS is almost impossible because the error is not in the affected program.\nBy stopping the program before the storage violation can occur, InterTest for CICS protects your system and helps you\ndiagnose and correct the error.\nIn this example, the statement that would have caused the storage violation is:\nINPUT_REC_2 = OUTPUT_REC_2\nThis statement moves data from OUTPUT_REC_2 TO INPUT_REC_2. The program may not own the area of storage\ndefined as INPUT_REC_2, so the program cannot move data to that field.\nInspect the FREEMAIN Statement\n1.Page back to find out what caused the error.\n2.Press PF7.\nThe following screen appears.\nCA InterTest for CICS   - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \n 550", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "889b891d0a21-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCOMMAND ===>                                                                    \nProgram= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ CKPTNAME                        | PROTCPF                                \n _____ NUP_AREA                        |          THIS IS NOT A NAME  PRIME THE \n _____ REC_LEN                         | +00681.                                \n _____ INPUT_REC_2                     | .........................              \n _____ OUTPUT_REC_2                    | .........................              \n---------+--------------------------------------------------------------------- \n _  1416.1     1      STORVIOL:                                                 \n _  1417.1                   /* EXEC CICS GETMAIN  SET(INPUT_REC_PTR)           \n _  1418.1                                         LENGTH(6144) */              \n _  1419.1                   DO;                                                \n _  1420.1     1  1          DCL DFHENTRY_BF6577CC_B36530EB BASED(ADDR(DFHEI0)  \n _  1421.1             ASSEMBLER) ENTRY(*,POINTER,FIXED BIN(15));               \n _  1422.1     1  1          CALL DFHENTRY_BF6577CC_B36530EB('. {. ..\u00f0.0462000  \n _  1423.1             00 03 00 00 8C 00 F0 F4 F6 F2 F0 F0 F0 F0 'X */,INPUT_R  \n _  1424.1     1  1          END;                                               \n _  1425.1                   /* EXEC CICS FREEMAIN DATA(INPUT_REC) */        \n _  1426.1     1             DO;", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "889b891d0a21-1", "text": "_  1426.1     1             DO;                                                \n _  1427.1     1  1          DCL DFHENTRY_BF6577CC_B36C7BE6 BASED(ADDR(DFHEI0)  \n _  1428.1             ASSEMBLER) ENTRY(*,*);\nLook at the FREEMAIN statement that releases the storage for INPUT_REC.\nNow it is clear why the storage violation occurred. The demo program released the storage for INPUT_REC. After\nreleasing the storage, the program tried to move data to INPUT_REC_2, which is part of INPUT_REC.\nTo correct the problem, you have to remove the FREEMAIN statement or change its location, and then recompile the\nprogram. However, one of the benefits of InterTest for CICS is that you do not have to correct a problem when you\ndiscover it. Instead, you can go around the problem and continue testing the program.\nNow we will redisplay the breakpoint.\n3.Press Clear.\nInterTest for CICS redisplays the automatic breakpoint.\nResume Program Execution\nContinue program execution at the first instruction after the statement that triggered the breakpoint. In the PL/I demo, this\nis GOTO SENDMP00.\n1.Tab to the GOTO SENDMP00 statement following the breakpoint.\n2.Type G (go).\n3.Press Enter to continue program execution.\nCA InterTest for CICS   - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \nCOMMAND ===>                                                                    \nProgram= PL1DEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n _____ CKPTNAME                        | PROTCPF                                \n _____ NUP_AREA                        |          THIS IS NOT A NAME  PRIME THE \n _____ REC_LEN                         | +00681.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "889b891d0a21-2", "text": "_____ REC_LEN                         | +00681.                                \n _____ INPUT_REC_2                     | .........................              \n _____ OUTPUT_REC_2                    | .........................              \n---------+--------------------------------------------------------------------- \n 551", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f04f5ba3e443-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _  1431.1     1  1          END;                                               \n _  1432.1     1             OUTPUT_REC_2     =  INPUT_REC_2;                   \n A   ==>.1     1             INPUT_REC_2      =  OUTPUT_REC_2;      ==>      \n     ==> an attempt to change an area that does not belong to this task.     \n     ==> Possible system damage has been prevented.                          \n     ==>                                                                     \n     ==>      Press PF1 for a detailed description.                          \n     ==>                                                                     \n                                                                                \n g  1434.1     1             GOTO SENDMP00;                                     \n U  1435.1     1      LOOPRTN:                                                  \n _  1436.1                   DO I = 1 TO 50;                                    \n _  1437.1                      /* EXEC CICS ASKTIME */  \nInterTest for CICS resumes program execution. PL1DEMO successfully completes execution and the Options Menu\nappears.\nBy going around the storage violation, you have allowed PL1DEMO to continue executing despite the problem\nInterTest for CICS detected.\nReview What Happened\nIn this part of the demo session:\n\u2022InterTest for CICS detected and prevented a storage violation and halted the demo program at an automatic\nbreakpoint.\n\u2022InterTest for CICS' ability to prevent storage violations protects your CICS system and prevents one program from\ncorrupting another.\n\u2022By inspecting the statement that would have caused the storage violation, you saw which field was in error. By\ninspecting the FREEMAIN statement, you were able to determine why the program did not own the storage area.\n\u2022Using InterTest for CICS to examine the source code surrounding an error makes it easy to learn what caused the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f04f5ba3e443-1", "text": "problem.\n\u2022You went around the problem and continued program execution.\n\u2022The ability to go around a problem lets you continue testing and correct many errors in a single test session.\nThis concludes Option 04 of the advanced demo session. Press Enter to continue with the demo session or press Clear to\nterminate the session.\nOption 05 How to Test a Composite Module\nThis option details how you can use InterTest for CICS to test and debug a composite module. Composite support is\nan InterTest for CICS feature designed to help programmers who are responsible for testing and debugging called\nsubroutines. Skip this option if you are not responsible for these subroutines.\nTo perform this option, you should have set monitoring for the composite module as described earlier in this article in\nComposite Support.\nIn this section you will test three programs:\n\u2022The main program, PL1DEML, which like PL1DEMO, is invoked by the DEMP transaction.\n\u2022Two subroutines called by PL1DEML:\n\u2013ASBIN25, written in Assembler\n\u2013PSBIN25, written in PL/I\nPL1DEML has several subroutines; however, you need to test only two of them.\n 552", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e6815cb1c3e4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSimilarly, composite modules at your site might have many called subroutines, but you need to tell InterTest for CICS only\nabout the ones you want to test.\n1.Display the InterTest for CICS Demo Session Options Menu.\n2.Select option 05, and press Enter.\nThe demo program displays a description of what will occur in this part of the demo.\n    **********************************************************************      \n    ****                                                              ****      \n    ****                  CA InterTest Demo Session                   ****      \n    ****                     Composite Support                        ****      \n    ****                                                              ****      \n    **********************************************************************      \n                                                                                \n Program PL1DEML calls two subroutines:  ASBIN25 and PSBIN25.                 \n                                                                                \n 1. CA InterTest halts the program at an automatic breakpoint caused by \n    an ASRA. Without composite support, you will see only that you are stopped \n    at the CALL to ASBIN25.                                                  \n 2. You abend the task, and then set composite support for PL1DEML.          \n 3. Type in transaction id DEMP again. This time you will see the actual      \n    instruction causing the ASRA within the subroutine.                      \n 4. You correct the problem that caused the automatic breakpoint.            \n 5. You then set an unconditional breakpoint in PSBIN25. When you resume      \n    execution, the program is halted at that breakpoint.                     \n 6. You remove the breakpoint and the program completes execution.           \n                                                                                \n                                                                                \n When this section of the demo completes, you will return to the Options Menu. \n                                                                                \n              Press ENTER to continue or CLEAR to terminate\n3.Press Enter.\nThe composite module halts at an automatic breakpoint at statement CALL ASBIN25.\nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e6815cb1c3e4-1", "text": "The composite module halts at an automatic breakpoint at statement CALL ASBIN25.\nNOTE\nIf a screen other than the one below appears, someone at your site has already set composite support for\nthe composite module.\nCA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \nCOMMAND ===>                                                                    \nProgram= PL1DEML  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n---------+--------------------------------------------------------------------- \n _  1644.1     1                GOTO END_SESSION;                               \n _  1645.1                                                                      \n A   ==>.1     1      CALLCOMP:      ==>                                     \n     ==> CICS abend intercepted. Abend code = ASRA.   EXEC CICS request was  \n     ==> LINK. Abend in program ASBIN25  at offset 000000E8.                 \n     ==>                                                                     \n     ==>      Press PF1 for a detailed description.                          \n     ==>                                                                     \n                                                                                \n _  1647.1                       /* EXEC CICS LINK PROGRAM ('PL1DEML') */       \n 553", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5f4c23889c7b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _  1648.1                       DO;                                            \n _  1649.1     1  1              DCL DFHENTRY_BF6577CC_B52431E6 BASED(ADDR(DFH  \n _  1650.1            NTER ASSEMBLER) ENTRY(*,CHAR(8));                         \n _  1651.1     1  1              CALL DFHENTRY_BF6577CC_B52431E6('000011100000  \n _  1652.1            00000000000110000000000000000000000010000000011110000111  \n _  1653.1            11011011110000111100001111000011110000'B /* '0E 02 80 00  \n _  1654.1             F0 F5 F9 F6 F0 F0 F0 F0 'X */,'PL1DEML');                \n _  1655.1     1  1              END;                                           \n _  1656.1     1                 GOTO SENDMP00;                              \nInterTest for CICS halted the composite module at an automatic breakpoint because it detected and prevented an error\nin ASBIN25 when control passed to that subroutine. However, so far you do not know where in ASBIN25 the error\noccurred.\nNotice that the name in the Program field is PL1DEML, the name of the composite module. This is the program\nInterTest for CICS is monitoring; the program for which you set monitoring before you began the advanced demo\nsession.\nSetting composite support lets you test and debug a called subroutine as if it were a separate program, with full", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5f4c23889c7b-1", "text": "symbolic support . This means you can set breakpoints and other monitoring options for that subroutine, and when\nInterTest for CICS detects an error, it generates an automatic breakpoint at the statement that triggered the abend, not\nat the CALL.\nYou can set composite support before you begin to test a program or at any time during testing. In this case, you will\nabend the task, set composite support, and then resume testing.\nAbend the Task\nWhen your program is stopped at a breakpoint, you can abend the task rather than resume execution.\n1.Type ABEND in the Command line of the Breakpoint display, and press Enter.\nNOTE\nThis is the same as selecting option 3 Abend, from the Breakpoint Menu. Because you do not need a dump,\nyou do not need to type an abend code.\nThe following screen appears.\n------------CA InterTest for CICS  ABEND BREAKPOINTED TASK  ---------------\n COMMAND ===>                                                                   \n                                                                                \n    Type an abend code, then press ENTER.                                     \n                                                                                \n                                                                                \n    Abend Code  ____   Abend code options are:                                  \n                                                                                \n                       blanks        Normal abend, no dump                      \n                       XXXX          Abend exits cancelled, no dump             \n                       your code     Your abend code, dump taken\n.\n.\n.                                                                             \n2.Press Enter.\nCICS informs you the task has been abended.\n3.Press Clear.\n 554", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ba1d3b1b8301-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSet Composite Support\nTo set composite support, access the main CNTL menu from which you can set all of InterTest for CICS' monitoring\noptions.\n1.Type ITST 2.1 on a clear screen, and press Enter.\nThis is the fastpath entry from CICS to invoke the Main Menu and select the Program Monitoring Option.\nThe Program Monitoring Menu appears.\n---------------CA InterTest for CICS PROGRAM MONITORING  ---------------\n COMMAND ===>                                                                   \n                                                                                \n   Type information and S to set or R to remove option(s) below.                \n                                                                                \n   Program  . . PL1DEML_     Program name (or .ALL, .OPTIONS or generic)        \n   User ID  . . ________     User (or .ANY) for whom the program is monitored   \n                                                                                \n   Option       Description                                            More:   +\n _ Status       Display and/or remove monitoring options (S only)               \n _ Monitor      Monitoring (R removes monitoring and all options previously set)\n _ UBP          Unconditional breakpoints (specific program only)               \n _ CBP          Conditional breakpoints (specific program only)                 \n _ RBP          Breakpoints for CICS, DB2, DL/I or external CALL requests       \n _ Stmt Trace   Statement tracing and data monitoring (COBOL only)              \n _ New copy     Fetch new copy of program and reset monitoring options (S only) \n _ Commands     Indirect commands defined for a specific COBOL or PL/I program  \n _ Replace      CICS resource name replacement options                          \n _ Protect      Storage protection monitoring options                           \n _ Special      Other options (storage allocation, file updating, etc.)         \n s Composite    Monitor multi-CSECT program's separately compiled components", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ba1d3b1b8301-1", "text": "s Composite    Monitor multi-CSECT program's separately compiled components    \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7 Backward   8 Forward    9           10           11           12      \n2.In the Program field, type the name of the composite module you are using, PL1DEML.\n3.Type S to the left of Composite, and press Enter.\nThe Composite Support menu appears.\n       CA InterTest for CICS - Composite Support Builder                   \n COMMAND ===>                                                      SCROLL: PAGE\n Define composite support for PL1DEML  and press PF5.        Row 00001 of 00006 \n CAIN2620 Not all subprograms are selected                                      \n                                                                                \n * *          *          *        *        *           *                        \n _ Link name  Monitor    Offset   Length   Language    Comments                 \n S PL1DEML1   PL1DEML        80      248   PL/I   4.3                           \n S PSBIN251   PSBIN25       EE8      1B0   PL/I   4.3                           \n S ASBIN25    ASBIN25      1098      17C   HLASM  6.0                           \n _ @PL1DEML   ________     1218       10               Symbolics NOT available  \n _ PLIXOPT    ________     1228        8               Symbolics NOT available  \n _ @PSBIN25   ________     1230        8               Symbolics NOT available  \n                                                                                \n                                                                                \n                                                                                \n 555", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8daed03618f2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n PF1 Help       2            3 End        4            5 Process    6 RFind     \n PF7 Backward   8 Forward    9           10           11           12           \nThis menu displays link-edit information for the composite program and its subroutines. A batch job, executed after the\ncomposite module was link-edited, gave InterTest for CICS this information.\nThree monitor-names  are listed: PL1DEML, ASBIN25, and PSBIN25. These are the names under which InterTest for\nCICS monitors the main program and two of the subroutines.\nThe batch job that provides the link-edit information identifies all of a program's called subroutines. For efficiency,\nhowever, it is a good idea to specify monitor-names just for the subroutines you want to test. You can always set\nmonitoring for additional subroutines by assigning monitor-names on the Composite Support menu.\n4.Press PF5 to set composite support.\nInterTest for CICS sets composite support for PL1DEML and returns you to the Program Monitoring menu.\nNow InterTest for CICS monitors the subroutines and the composite module PL1DEML so you can take advantage of\nall InterTest for CICS facilities to test and debug each  of the programs.\nRe-execute the Demo Program\nNow you can re-execute the demo program.\n1.Press PF4.\nThe Primary Option Menu appears.\n2.Select option X Exit to exit to CICS.\n3.Clear the screen and type the transaction ID DEMP, and press Enter.\n4.Press PF2 for the Options Menu.\nWithin the Options Menu, choose Option 05 (Composite Support) and press Enter.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8daed03618f2-1", "text": "Within the Options Menu, choose Option 05 (Composite Support) and press Enter.\n5.Press Enter again at the explanation screen.\nInterTest for CICS displays the automatic breakpoint where you initially halted. However, now the breakpoint occurs at\nthe actual statement  in ASBIN25 that triggered the abend, not at the CALL to ASBIN25.\nNOTE\nThe name in the Program field is ASBIN25. When control passes to ASBIN25, InterTest for CICS begins\nmonitoring that program because you set composite support.\nCA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \nCOMMAND ===>                                                                    \nProgram= ASBIN25  Option #       Stmt #        Displacement=        Margin= 01  \n                                        Search=                                 \n----------+-------------------------------------------------------------------- \n     Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n _ 0000E2                              365 CONTINUE DS    0H                    \n A 0000E2 FA20 D1A0 2143 001A0 00143   ==>          AP    TASKNUM,=P'1'      \n     ==>                                                                     \n     ==> ASRA ABEND (0C7) detected and prevented. Caused by invalid decimal  \n     ==> arithmetic data format.                                             \n     ==>                                                                     \n     ==>      Press PF1 for a detailed description.                          \n     ==>                                                                     \n _ 0000E8 F920 D1A0 2144 001A0 00144   367          CP    TASKNUM,=P'2'         \n 556", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "820a34cb5882-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _ 0000EE 4720 20FC            000FC   368          BH    RETCICS               \n _ 0000F2 F920 D1A0 2143 001A0 00143   369          CP    TASKNUM,=P'1'         \n _ 0000F8 4780 214E            0014E   370          BE    RETURN                \n _ 0000FC                              372 RETCICS  DS    0H                    \n                                       373 *        EXEC CICS RETURN            \n _ 0000FC 4110 D068            00068   374          DFHECALL =X'0E080000080000  \n                                       384 *                                    \n _ 000118                              385          LTORG                       \n _ 000118 00000000                     386                =V(DFHEAI0)          \nSetting composite support enables InterTest for CICS to identify and display the statement in the subroutine where the\nerror occurred.\nThe error occurred because of improperly formatted data in TASKNUM. The AP instruction tries to move a packed\ndecimal 1 to TASKNUM. TASKNUM is defined as a packed decimal field, but it contains binary zeros instead of a valid\npacked decimal value. This is the same type of error you corrected in the basic demo session.\nDisplay the Data in TASKNUM\nTo correct this error, display the contents of TASKNUM and dynamically change the value.\n\u2022Tab to the AP instruction, and overtype the A with D. Position the cursor under any character in TASKNUM, and then\npress Enter.\nInterTest for CICS displays the contents of TASKNUM.\nOn the left of the screen are the Assembler data field names; on the right are the corresponding data-type appropriate", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "820a34cb5882-1", "text": "representations of each field, note that fields that contain incorrect data for their type have a question mark in the first\ndigit (TASKNUM).\nInterTest for CICS displays more than just the contents of TASKNUM. It displays TASKNUM and all the fields below it\nin the same data structure; that is, in the same DSECT.\nCorrect the Data in TASKNUM\nAs you can see, TASKNUM contains binary zeros rather than a packed decimal value. You can correct the error by\novertyping the incorrect value with a correct value.\n\u2022Tab to the top line and move the cursor to the question mark in the value portion for TASKNUM.\n\u2022Overtype the current value with all zeros.\n\u2022Press Enter.\nCA InterTest for CICS - MAIN STORAGE UTILITY - Termid = U030        \n                                                                                \nStarting at Address =  101DA8  Disp   Structure Display Format                  \nTASKNUM                         1A0 | ?00000.                    |              \nTSTEXT                          1A3 | ............               |              \n                                    | ............               |              \n                                    | ............               |              \n                                    | ............               |              \n                                    | ............               |              \n                                    | ............               |              \n                                    | .                          |              \nTSQLEN                          1EC | +0006553600.               |              \nMSGNAME                         1F0 |  0000000000.               |              \nMSGLEN                          1F4 |  00000.                    |              \nRECRBA                          1F6 | ......                     |              \nRECPONT                         1FC |  0000000000.               |              \n                                                                                \n 557", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5addb17e05a4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                                                                \n                                                                                \n ------------------------------------------------------------------------------ \n PF1 Help       2            3 End        4 Return     5            6 Dump      \n PF7 Backward   8 Forward    9 Caps Off  10           11 Redisplay 12 Structure \n CORE='R13.TASKNUM'                                                             \n CAIN4713 R13 not found - have assumed its register value                  \nInterTest for CICS redisplays the screen, changing your entries to uppercase.\nNow TASKNUM contains a packed decimal zero. You have corrected the error that triggered the automatic breakpoint.\n\u2022Press Clear.\nInterTest for CICS redisplays the previous Source Listing Breakpoint screen. However, the explanation of the abend no\nlonger appears.\nSet a Breakpoint in Subroutine PSBIN25\nNow you are going to set a breakpoint at the first statement in subroutine PSBIN25, the other subroutine you asked\nInterTest for CICS to monitor. Then, when you resume execution, InterTest for CICS halts execution at the breakpoint in\nthis subroutine.\nWhen you are stopped in a subroutine, you can use all of these InterTest for CICS features:\n\u2022View the program listing and compiler output\n\u2022Display and modify main and auxiliary storage\n\u2022Set and remove breakpoints and other monitoring options\n\u2022Request single-step execution\n\u2022Display the backtrace that brought the program to its current point\n\u2022Tab back to the Program field.\n\u2022Overtype ASBIN25 with PSBIN25 and press Enter.\nCA InterTest for CICS   - PROTSYM FILE  ABEND DETECTED BREAKPOINT         \nCOMMAND ===>                                                                    \nProgram= psbin25  Option #       Stmt #        Displacement=        Margin= 01  \n                                        Search=                                 \n----------+--------------------------------------------------------------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5addb17e05a4-1", "text": "Search=                                 \n----------+-------------------------------------------------------------------- \n     Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              \n_   0000E2                              365 CONTINUE DS    0H\n  A 0000E2 FA20 D1A0 2143 001A0 00143   ==>          AP    TASKNUM,=P'1'\n  _ 0000E8 F920 D1A0 2144 001A0 00144   367          CP    TASKNUM,=P'2'\n  _ 0000EE 4720 20FC            000FC   368          BH    RETCICS\n  _ 0000F2 F920 D1A0 2143 001A0 00143   369          CP    TASKNUM,=P'1'\n  _ 0000F8 4780 214E            0014E   370          BE    RETURN.\n.   \nInterTest for CICS displays the source listing for PSBIN25.\nNow you will set an unconditional breakpoint at the first statement in PSBIN25.\n\u2022Tab to the first statement.\n\u2022Type U to the left of that statement, and press Enter.\nCA InterTest for CICS - PROTSYM FILE  ABEND DETECTED DISPLAY            \nCOMMAND ===>                                                                    \nProgram= PSBIN25  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \n------------------------------------------------------------------------------- \n 558", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "90cf0ba85986-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n u    18.1            PSBIN25:  PROC(INPUT_REC_PTR, STOR_SIZE) OPTIONS(REENTRA  \n _    19.1     1      DCL 1 DFHCNSTS  STATIC,  /* CONSTANTS USED BY TRANSLATOR  \n _    20.1                   2  DFHLDVER CHAR(22) INIT('LD TABLE DFHEITAB 530.  \n _    21.1                   2  DFHEIB0 FIXED BIN(15) INIT(0),                  \n _    22.1                   2  DFHEID0 FIXED DEC(7) INIT(0),                   \n _    23.1                   2  DFHEICB CHAR(8) INIT('        ');               \n _    24.1     1      DCL DFHEPI ENTRY, DFHEIPTR PTR;                           \n _    25.1     1      DCL 1 DFHEIBLK BASED (DFHEIPTR),                          \n _    26.1                  02    EIBTIME  FIXED DEC(7),                        \n _    27.1                  02    EIBDATE  FIXED DEC(7),                        \n _    28.1                  02    EIBTRNID CHAR(4),                             \n _    29.1                  02    EIBTASKN FIXED DEC(7),                        \n _    30.1                  02    EIBTRMID CHAR(4),                             \n _    31.1                  02    EIBFIL01 FIXED BIN(15),                       \n _    32.1                  02    EIBCPOSN FIXED BIN(15),                       \n _    33.1                  02    EIBCALEN FIXED BIN(15),", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "90cf0ba85986-1", "text": "_    33.1                  02    EIBCALEN FIXED BIN(15),                       \n _    34.1                  02    EIBAID   CHAR(1),                             \n _    35.1                  02    EIBFN    CHAR(2),                             \n _    36.1                  02    EIBRCODE CHAR(6),\nInterTest for CICS sets an unconditional \"before\" breakpoint at the statement.\n\u2022Press Clear.\nInterTest for CICS redisplays the previous Source Listing Breakpoint screen.\nResume Program Execution\nNow you are going to continue program execution.\nPress PF5.\nThe program resumes execution. When the control passes to subroutine PSBIN25, InterTest for CICS halts the program\nat the unconditional breakpoint you just set.\nAt this point you could use InterTest for CICS to examine the program listing of PSBIN25 or the values of any program\nvariables. However, will remove the breakpoint and resume program execution.\nRemove the Breakpoint and Resuming Execution\nOvertype the U with X, and press PF5.\nInterTest for CICS removes the unconditional breakpoint and program execution resumes. PL1DEML completes execution\nand the Options Menu is displayed.\nReview What Happened\nIn this part of the demo session:\n\u2022When you executed PL1DEML, InterTest for CICS detected and prevented an abend caused by invalid data in one of\nits called subroutines.\nInterTest for CICS displayed the automatic breakpoint at the statement which called the subroutine, rather than the\nstatement that triggered the breakpoint, because InterTest for CICS was not monitoring the subroutine.\n\u2022You set composite support for PL1DEML so that InterTest for CICS would monitor its subroutines: ASBIN25 and\nPSBIN25.\n 559", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e0d045bbe1d0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSetting composite support lets you test and debug a called subroutine with full symbolic support and take advantage of\nall InterTest for CICS features.\n\u2022When you re-executed PL1DEML, InterTest for CICS redisplayed the automatic breakpoint, this time at the actual\nstatement in subroutine ASBIN25 that caused the error.\n\u2022You corrected the error by overtyping the contents of the invalid field.\n\u2022You then set an unconditional breakpoint in the other subroutine, PSBIN25, and resumed program execution. When\ncontrol passed to PSBIN25, InterTest for CICS halted execution at the breakpoint you set.\nThe ability to halt execution at any statement in a subroutine means you can test a subroutine just as if it were a main\nprogram.\n\u2022You removed the unconditional breakpoint and continued program execution.\nThis concludes Option 05 of the advanced demo session. Press Enter to continue with the demo session or press Clear to\nterminate the session.\nInterTest Batch Demo Sessions\nUse the InterTest Batch Demo sessions to train new users in the basic product test and debug features.\nThese demos also introduce some of the advanced features of InterTest Batch.\nWe recommend that all InterTest Batch users take these demo sessions and become familiar with the features that are\nexplained here.\nBasic Foreground Demo Session\nThis section takes you step-by-step through the basic Foreground demo session.\nPerforming the demo at a terminal is the best way to begin learning about this product.\nDemo Session Objectives\nThis demo session, teaches you how to:\n\u2022Access the application and specify a program that you want to test.\n\u2022Begin program execution from an Initial Intercept panel.\n\u2022Respond to the information provided when the application detects an error.\n\u2022Display and dynamically change the value of a data item.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e0d045bbe1d0-1", "text": "\u2022Display and dynamically change the value of a data item.\n\u2022Resume and control program execution at any point, by setting and removing breakpoints.\nBefore You Start the Demo\nThe examples in this article use default library names and generic references to keystrokes, which differ from installation\nto installation (for example, the Roscoe  END key or SPLIT command sequence).\nThis article cannot anticipate differences at your installation. You must have information specific to your product\ninstallation before attempting the examples in this demo.\nAccess the Product\nTo run the application, you need to know the ISPF option or the CLIST name that calls the application. The examples\nassume a default ISPF option. Consult your installer to determine the procedure for invoking the application at your\ninstallation.\n 560", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "044e17595e53-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe Demo Source\nThe source for the demo programs: CAMRPLI, CAMRASM, CAMRCOB, CAMRCOB2, CAMRDMR, CAMRDMR2,\nand CAMRCOBB are in CAI.CAVHSAMP. Use your compile procedures created during installation to compile a demo\nprogram, populate the PROTSYM, and link the program.\nRoscoe  Split Screen Sequence\nFor the advanced demo session, see Advanced Demo Session. Roscoe  users need to know the key sequence that is\nrequired to split their one session into two sessions. Consult your Roscoe  documentation or system programmer.\nBegin the Basic Demo\nBegin the demo session by accessing the application and selecting the Foreground option from the menu. The sample\ndemo programs are:\nCAMRCOB\nOS/VS COBOL demo for ISPF users\nCAMRCOB2\nCOBOL II demo for ISPF users\nCAMRPLI\nPL/I Demo for ISPF users\nCAMRASM\nAssembler demo for ISPF users\nCAMRDMR\nOS/VS COBOL demo for Roscoe  users\nCAMRDMR2\nCOBOL II demo for Roscoe  users\nCAMRCOBB\nCOBOL II Batch Link Demo\nThe panels in this article illustrate a COBOL II demo session using CAMRCOB2. The screen images of other demos vary\nfrom the panels that are shown in this article, but the steps for performing the demo are the same.\nWhen testing a program such as CAMRCOB2 or CAMRCOB, the application automatically intercepts all abends. This\nfunctionality is explained later when the application prevents the demo program from abending because of an S0C7.\nAccess the Primary Option Menu", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "044e17595e53-1", "text": "Access the Primary Option Menu\nTo access the application, select the option for InterTest Batch on your ISPF/PDF Primary Option Menu or enter the name\nof the CLIST from ISPF Option 6. Roscoe  users can select the InterTest Batch option on the Roscoe  menu or enter the\nfollowing commands:\n [xxx.]IBALLOC [xxx.]IBRUN \nWhere xxx is the prefix of the library where the application is installed.\nTake a quick look at each of these options before beginning the Demo Session:\n1\nForeground\nLets you test the execution of an application.\n2\nCore\n 561", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6e27f5b8e3a5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nLets you display and alter virtual memory in hexadecimal and character format.\n3\nAllocation\nLets you allocate the files that you use in your test session. This option is not available for Roscoe  users, who\nshould use the IBCONV RPF for file allocations.\n4\nMap\nLets you view task control blocks for help in debugging complex system-related problems.\n5\nBatch\nLets you test an application to be executed in batch.\nU\nUtilities\nLets you display and update the contents of a PROTSYM.\nX\nExit\nTerminates the application.\nIn addition, you can access the tutorial from the Primary Option Menu by pressing your HELP PFkey (normally PF1). The\ntutorial gives a summary of application facilities and commands.\nFile Allocation\nEach demo program requires certain DDs to be allocated before they can be executed correctly. These DDs can be\nallocated by converting CAI.CAVHJCL(DEMOJCL) to ALIB format and using that ALIB. Use the ALLOC command from\nwithin the ALIB editor to allocate those files, or the TSO ALLOC command. The SYSOUT, SYSPRINT, and REPORT are\nthe required DD names and can all be allocated to a SYSOUT class. For more information about allocating DDs to your\nTSO session or converting JCL to ALIB format, see Allocations Facility for ISPF.\nNOTE\nFor instructions on converting JCL to Roscoe  RPF format, see JCL Conversion for Roscoe .\nSpecify the Program to be Tested\nBegin by selecting the Foreground option.\nFollow these steps:\n1.In the Primary Option Menu, type 1 and press Enter. The Execution Control Panel displays. This is where you specify\nthe name of the application to be tested.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6e27f5b8e3a5-1", "text": "the name of the application to be tested.\n2.In the PGM field, enter the name of the program that you are going to debug (CAMRCOB, CAMRCOB2, and so on).\nIn the first Task Libraries field, enter the load library that you linked the demo program into. The Monitor Control panel\ndisplays. The Monitor Control panel lets you specify the name of the programs you are testing, and the name of the\nPROTSYM files where the symbolics for those programs are stored.\n3.Enter the name of the demo program and the PROTSYM file that was used when the program was compiled. The\napplication accesses the listing for the COBOL program that you specified, and displays the *Initial* Intercept panel.\nThe Initial Intercept Panel\nEach time that you begin testing, the application displays an *Initial* Intercept (or Breakpoint) panel upon entry to the\nfirst program to be tested. The *Initial* breakpoint displays the program listing that is positioned at the first executable\nstatement. Look at the different parts of this panel.\n 562", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e9f75a04b98d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nThe text and panels in this article reference the COBOL II program CAMRCOB2.\nThe statement line numbers that are shown here may not exactly match the line numbers that you see on your screen.\nCAMRCOB2 ---------- CA InterTest Batch *INITIAL* Intercept -------------------\nCOMMAND ===>                                                  SCROLL ===> CUR \nTRACE=> 000876                                                            \n      000875        PROCEDURE DIVISION USING PARAMETER-AREA.                  \n      000876        START-PROGRAM.                                            \n      000877            OPEN OUTPUT REPORT-OUT.                               \n      000878       * -----------------------------------------------*         \n      000879       * Welcome to the CA InterTest COBOL II     *         \n      000880       * Demonstration Program. You are now at the      *         \n      000881       * Initial Breakpoint panel which is displayed    *         \n      000882       * upon entry to the first program to be tested.  *         \n      000883       * At this point, other breakpoints can be set    *         \n      000884       * and control commands can be issued before  the *         \n      000885       * program is executed.                           *         \n      000886       * -----------------------------------------------*         \n      000887            MOVE  R1498-TIMEI TO R1498-TIME.                      \n      000888            PERFORM TIME-EDIT THRU TIME-EDIT-EX.                  \n      000889       *                                                          \n      000890            MOVE  R1498-TIMEO TO R1498-TIME.                      \n      000891            PERFORM TIME-EDIT THRU TIME-EDIT-EX.                  \n      000892            GO TO DISPLAY-1ST-PANEL.                              \n      000893       * -----------------------------------------------*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e9f75a04b98d-1", "text": "000893       * -----------------------------------------------*       \n      000894       *    THIS ROUTINE EDITS INPUT TIME FOR VALIDITY  *\nThe top line of this panel contains three parts:\n\u2022The left corner displays the name of the program being tested (in this case, CAMRCOB2).\n\u2022The middle portion displays the status. In this case, the status is *INITIAL* since it is the initial entry into the program.\n\u2022The right portion is a message display area.\nThe command Line is where you enter application control commands.\nThe Trace Line displays up to 10 statement numbers. The first number is the statement about to be executed, followed by\nthe last nine statements executed. The previous example shows only the statement number about to be executed and the\nstatement number of START-PROGRAM.\nThe Line Command field is where you enter a single-character command that relates to a specific line of code.\nThe listing displays and the statement about to be executed is highlighted.\nTurn the Frequency Display On\nThe Frequency Counter indicates how many times an instruction was executed in this session. The first time that you use\nthe Foreground option, the frequency counter is turned on but may not be displayed.\nTo enable the display, type the FREQ command and press Enter.\n      000881       * Initial Breakpoint panel which is displayed    *         \n      000882       * upon entry to the first program to be tested.  *         \n      000883       * At this point, other breakpoints can be set    *         \n      000884       * and control commands can be issued before  the *         \n 563", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fdbb1871a16e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n      000885       * program is executed.                           *         \n      000886       * -----------------------------------------------*         \n *--> 000887            MOVE  R1498-TIMEI TO R1498-TIME.                      \n *--> 000888            PERFORM TIME-EDIT THRU TIME-EDIT-EX.                  \n      000889       *                                                          \n *--> 000890            MOVE  R1498-TIMEO TO R1498-TIME.                      \n *--> 000891            PERFORM TIME-EDIT THRU TIME-EDIT-EX.                  \n *--> 000892            GO TO DISPLAY-1ST-PANEL.                              \n      000893       * -----------------------------------------------*\n      000894       *    THIS ROUTINE EDITS INPUT TIME FOR VALIDITY  *         \nResult:\nA message ? indicates that the frequency counter was turned on, and the frequency counter arrows ?  are displayed along\nthe left side of the program statements. Since the program has not executed any statements, the frequency counter does\nnot display any numbers.\nBegin Program Execution\nNow you are ready to execute the demo program. The command to execute a program is GO.\nFollow these steps:\n1.Type the GO command and Press Enter.\nCAMRCOB2 begins execution and displays the \"Welcome Panel\" panel.\n2.Press Enter to continue the demo.CAMRCOB2 resumes execution.\nDetect and Intercept an Abend\nThe next screen that you see is another type of Intercept panel, an Abend Intercept panel. This panel indicates that the\napplication halted your program because an error was detected.\nCAMRCOB2  ---------- CA InterTest Batch ABEND S0C7 Intercept ------------------ \nCOMMAND ===>                                                  SCROLL ===> PAGE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fdbb1871a16e-1", "text": "COMMAND ===>                                                  SCROLL ===> PAGE \nTRACE=> 000938 000935 000933 000931 000925 000920 001291 001290 001283 001282 0\n      00937                                                                    \n 0001 00938             ADD +1 TO TASKNUM.                                     \n      00939                                                                    \n          -----------------------------------------------------------------    \n          |        THE FOLLOWING AUTOMATIC BREAKPOINT OCCURRED:           |    \n          |   INTERCEPT IN PROGRAM CAMRCOB  AT #000938 REASON: ABEND S0C7 |    \n          |        PRESS ENTER TO REMOVE THIS MESSAGE.                    |    \n          -----------------------------------------------------------------    \n ---> 00945         DISPLAY-2ND-PANEL.                                         \n ---> 00946             CALL 'ISPLINK' USING DSPLY,                            \n      00947                                  SECOND-PANEL.                     \n      00948        * ---------------------------------------------- *          \n      00949        * .. Now to send the third panel which explains  *          \n      00950        * what we have done so far .. ..                 *          \n      00951        *                                                *          \n      00952        * ---------------------------------------------- *          \n ---> 00953         DISPLAY-3RD-PANEL.                                         \n       \n 564", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2c547ae04e8d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nLook at the top line of the screen. This line indicates that the application stopped execution due to an S0C7 ABEND. The\napplication stops program execution automatically at a breakpoint, as in the case illustrated. The application can also stop\nprogram execution at a breakpoint that was set by you, the programmer.\nNow look at the highlighted ADD instruction. Execution of that ADD instruction triggered the S0C7 ABEND. The\napplication intercepted the abend and then displayed the diagnostic screen that you are currently viewing.\nThe abend type indicates that the problem was caused by improperly formatted data. Which data? Since ADD +1 TO\nTasknum triggered the breakpoint, it is likely that Tasknum contains improperly formatted data.\nNOTE\nThe application intercepted CAMRCOB2 after the abend and identified the problem.\nNext:\n1.Determine the cause of the error by displaying the current value in Tasknum.\n2.Dynamically correct the error by changing the value in Tasknum.\nDetermine the Cause of the Error\nConfirm our guess that the value that is stored in Tasknum is not valid by displaying its current value.\nTab down to the line containing the highlighted ADD statement. Type K to the left of the statement, and press Enter.\nCAMRCOB2 ---------- CA InterTest Batch ABEND S0C7 Intercept ------------------ \nCOMMAND ===>                                                  SCROLL ===> CUR \nTRACE=> 000939 000936 000934 000932 000926 000921 001292 001291 001284 001283 0\n      000938                                                                   \n k0001 000939            ADD +1 TO Tasknum.                                     \n      000940                                                                   \n      000941       * -----------------------------------------------*          \n      000942       *                                                *", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2c547ae04e8d-1", "text": "000941       * -----------------------------------------------*          \n      000942       *                                                *          \n      000943       * The above statement causes a 0C7.. ..          *          \n      000944       *                                                *          \n      000945       * -----------------------------------------------*          \n ---> 000946        DISPLAY-2ND-PANEL.                                         \n ---> 000947            CALL 'ISPLINK' USING DSPLY,                            \n      000948                                 SECOND-PANEL.                     \n      000949       * -----------------------------------------------*          \n      000950       * .. Now to send the third panel which explains  *          \n      000951       *    what we have done so far .. ..              *          \n      000952       *                                                *          \n      000953       * -----------------------------------------------*          \n ---> 000954        DISPLAY-3RD-PANEL. \n ---> 000955        CALL 'ISPLINK' USING DSPLY,                                \nA Keep Window displays containing the current value of Tasknum, as illustrated in the next panel.\nCAMRCOB2 ---------- CA InterTest Batch ABEND S0C7 Intercept ------------------ \nCOMMAND ===>                                                  SCROLL ===> CUR \nTRACE=> 000939 000936 000934 000932 000926 000921 001292 001291 001284 001283 0\n      -------------------------------------------------------------------------\n      0E7F24D0 NP-S  000498 03 TASKNUM                      ?00000.           \n      -------------------------------------------------------------------------\n      000938                                                                   \n 565", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "392a1a6e7e0b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 0001 000939            ADD +1 TO Tasknum.                                     \n      000940                                                                   \n      000941       * -----------------------------------------------*          \n      000942       *                                                *          \n      000943       * The above statement causes a 0C7.. ..          *          \n      000944       *                                                *          \n      000945       * -----------------------------------------------*          \n ---> 000946        DISPLAY-2ND-PANEL.                                         \n ---> 000947            CALL 'ISPLINK' USING DSPLY,                            \n      000948                                 SECOND-PANEL.                     \n      000949       * -----------------------------------------------*          \n      000950       * .. Now to send the third panel which explains  *     \n      000951       *    what we have done so far....                *       \nIf you look at the contents of Tasknum, you see that the first character is a question mark. The application displays the\nquestion mark when the field does not contain properly formatted data. The value of Tasknum triggered the S0C7 ABEND.\nDynamically Change the Value in Tasknum\nNow that you have identified that the value in Tasknum caused the S0C7 ABEND, let us fix it dynamically.\nNOTE\nIn real testing, you might search the program listing or program execution path to investigate the source of\nthe error, and perhaps update your program code using a split-screen. These tasks are all performed in the\nAdvanced Demo Session. For now, assume that zero was the intended value, correct the value of Tasknum, and\ncontinue testing.\nType the following command: set tasknum = 0, and press Enter. The application dynamically sets the value of Tasknum", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "392a1a6e7e0b-1", "text": "to zero, as indicated in the message that displays in the top-right corner of the screen: SET COMPLETE. You can see the\nnew value of Tasknum in the Keep Window (+00000.).\nCAMRCOB2 ---------- CA InterTest Batch ABEND S0C7 Intercept ------ SET COMPLETE\n COMMAND ===>                                                  SCROLL ===> CUR \n TRACE=> 000939 000936 000934 000932 000926 000921 001292 001291 001284 001283 \n       ------------------------------------------------------------------------\n       0E7F24D0 NP-S  000498 03 TASKNUM                      +00000.           \n       ------------------------------------------------------------------------\n       000938                                                                   \n  0001 000939            ADD +1 TO Tasknum.                                     \n       000940                                                                   \n       000941       * -----------------------------------------------*          \n       000942       *                                                *          \n       000943       * The above statement causes a 0C7.. ..          *          \n       000944       *                                                *          \n       000945       * -----------------------------------------------*          \n  ---> 000946        DISPLAY-2ND-PANEL.                                         \n  ---> 000947            CALL 'ISPLINK' USING DSPLY,                            \n       000948                                 SECOND-PANEL.                     \n       000949       * -----------------------------------------------*          \n       000950       * .. Now to send the third panel which explains  *          \n       000951       *    what we have done so far .. ..              *          \n       000952       *                                                *          \n       000953       * -----------------------------------------------*          \n  ---> 000954        DISPLAY-3RD-PANEL.                                         \n 566", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2fff011ab949-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  ---> 000955            CALL 'ISPLINK' USING DSPLY,                            \n       000956                                 THIRD-PANEL.\n       000957       *                 \nNOTE\nYou do not have to know the type of data (binary, packed, and so on) or the length of Tasknum to correctly set\nits value. The SET command is comparable to a MOVE statement that automatically takes care of different data\ntypes and their lengths.\nControl Program Execution\nNow that the value in Tasknum has been properly initialized to zero, you could continue testing by resuming program\nexecution.\nThis is also a good opportunity to learn about an important feature, the ability to control program execution by setting\nbreakpoints.\nStop Your Program by Setting Breakpoints\nOne of the problems with traditional testing methods is that you have little or no control over program processing. You\nsimply initiate the program, and the program either runs to completion, loops, or abends.\nWith this product, you can control program execution in several ways. For example, you can set \"stops,\" called\nbreakpoints, anywhere in your program. You can set two types of breakpoints: unconditional and conditional.\n\u2022When you set an unconditional breakpoint at a statement, the program stops just before or just after the statement is\nexecuted. (Depending on the type of unconditional breakpoint that you set.)\n\u2022When you set a conditional breakpoint at a statement, the program stops only if the value of a data item changes, or if\na condition that you specified is met, such as a data-item equaling or exceeding some value.\nWhat You Can Do When Your Program Is Stopped\nOnce a program is stopped, you can use the application testing and debugging facilities to do the following actions:\n\u2022Examine the listing.\n\u2022Examine and modify main storage to detect and correct errors.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2fff011ab949-1", "text": "\u2022Examine the listing.\n\u2022Examine and modify main storage to detect and correct errors.\n\u2022Set and remove breakpoints.\n\u2022\u201cGo around a problem\u201d by skipping one or more statements, or by resuming execution from a location other than where\nthe program is stopped.\n\u2022Execute the program in single-step mode. The program executes only one verb (or the number of verbs that are\nspecified in the step count), and stops again.\n\u2022Terminate program execution.\nNOTE\nAll of these activities are described in detail in the Advanced Demo Session.\nThe next section demonstrates how easy it is to control program execution by setting an unconditional breakpoint.\nSet Unconditional Breakpoints\nYou can set unconditional breakpoints directly on any breakpoint display using the U line command, the ) line command,\nor the UNCOND control command. The U command sets a breakpoint that stops before  the statement is executed. The )\ncommand sets a breakpoint that stops after the statement is executed. The UNCOND command lets you specify whether\nthe breakpoint stops before or after the statement is executed.\nSee how to set a breakpoint before the execution of the DISPLAY-2ND-PANEL using the U line command.\n 567", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8c98a4594010-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nType U to the left of the paragraph name DISPLAY-2ND-PANEL.\nType GO to continue execution from where the program is stopped (at the statement ADD +1 TO Tasknum).\nCAMRCOB2 ---------- CA InterTest Batch ABEND S0C7 Intercept ------ SET COMPLETE\nCOMMAND ===>                                                  SCROLL ===> CUR \nTRACE=> 000939 000936 000934 000932 000926 000921 001292 001291 001284 001283 0\n      -------------------------------------------------------------------------\n      0E7F24D0 NP-S  000498 03 TASKNUM                      +00000.           \n      -------------------------------------------------------------------------\n      000938                                                                   \n 0001 000939            ADD +1 TO Tasknum.                                     \n      000940                                                                   \n      000941       * -----------------------------------------------*          \n      000942       *                                                *          \n      000943       * The above statement causes a 0C7.. ..          *          \n      000944       *                                                *          \n      000945       * -----------------------------------------------*          \nu---> 000946        DISPLAY-2ND-PANEL.                                         \n ---> 000947            CALL 'ISPLINK' USING DSPLY,                            \n      000948                                 SECOND-PANEL.                     \n      000949       * -----------------------------------------------*          \n      000950       * .. Now to send the third panel which explains  *          \n      000951       *    what we have done so far .. ..              *          \n      000952       *                                                *          \n      000953       * -----------------------------------------------*      \n ---> 000954        DISPLAY-3RD-PANEL.    \nThe application resumes program execution and continues until reaching the breakpoint that you set.\nCAMRCOB2 ---------- CA InterTest Batch UNCOND BEFORE Intercept ---------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8c98a4594010-1", "text": "CAMRCOB2 ---------- CA InterTest Batch UNCOND BEFORE Intercept ---------------\nCOMMAND ===>                                                  SCROLL ===> PAGE\nTRACE=> 000949 000948 000941 000938 000936 000934 000928 000923 001294 001293 0\n      -------------------------------------------------------------------------\n      001507E0 NP-S  000500 02 TASKNUM                     +00001.            \n      -------------------------------------------------------------------------\n        000940                                                                \n 0001   000941                    ADD +1 TO Tasknum.                          \n        000942                                                                \n        000943               * -----------------------------------------------*\n        000944               *                                                *\n        000945               * The above statement causes a 0C7.. ..          *\n        000946               *                                                *\n        000947               * -----------------------------------------------*\nU--->   000948                DISPLAY-2ND-PANEL.                             \n --->   000949                    CALL 'ISPLINK' USING DSPLY,                \n        000950                                         SECOND-PANEL.          \n        000951               * -----------------------------------------------*\n        000952               * .. Now to send the third panel which explains  *\n        000953               *    what we have done so far .. ..              *\n        000954               *                                                *\n        000955               * -----------------------------------------------*\n --->   000956                DISPLAY-3RD-PANEL.                              \n 568", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2701a8943141-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n --->   000957                    CALL 'ISPLINK' USING DSPLY,                 \n        000958                                         THIRD-PANEL.           \nThe application halts the program before the first executable statement in the paragraph is executed and displays the\nscreen.\nNote that the top line of the screen now identifies the reason for stopping as UNCOND BEFORE INTERCEPT. This\nindicates that the application has halted the program at a breakpoint you set.\nNotice the U to the left of the paragraph DISPLAY-2ND-PANEL. The U identifies the breakpoint as an unconditional\n\"before\" breakpoint. The first executable statement in that paragraph is the CALL statement. This statement is the current\nstatement  which is about to be executed.\nWhen you are stopped at a breakpoint, you can do the following actions:\n\u2022Scroll or search through your source listing.\n\u2022Examine and modify storage.\n\u2022Set and remove breakpoints using line commands such as U, ), and X.\n\u2022Go around a problem by resuming program execution from another location.\n\u2022Terminate program execution and stop the test session.\nWhen debugging your own programs, you typically perform one or more of these activities. However, CAMRCOB2 does\nnot have any more errors, so we are just going to complete the demo session.\nRemove the Breakpoint and Keep Window\nAs you continue testing and debugging, it is a good practice to remove breakpoints that you no longer need. Removing\nthese breakpoints prevents the program stopping unnecessarily. Remove the unconditional breakpoint that you just set so\nCAMRCOB2 does not stop before each execution of DISPLAY-2ND-PANEL in our test session. To reset the display, we\nare also going to remove the Keep Window.\nType the following command to remove the Keep Window: remove all. Tab down and type over the U with an X to remove\nthe breakpoint and press Enter.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2701a8943141-1", "text": "the breakpoint and press Enter.\nCAMRCOB2 ---------- CA InterTest Batch UNCOND BEFORE Intercept --------------- \nCOMMAND ===>                                                  SCROLL ===> CUR \nTRACE=> 000946 000939 000936 000934 000932 000926 000921 001292 001291 001284 0\n      -------------------------------------------------------------------------\n      0E7F24D0 NP-S  000498 03 TASKNUM                      +00001.           \n      -------------------------------------------------------------------------\n      000938                                                                   \n 0001 000939            ADD +1 TO Tasknum.                                     \n      000940                                                                   \n      000941       * -----------------------------------------------*          \n      000942       *                                                *          \n      000943       * The above statement causes a 0C7.. ..          *          \n      000944       *                                                *          \n      000945       * -----------------------------------------------*          \nx---> 000946        DISPLAY-2ND-PANEL.                                         \n ---> 000947            CALL 'ISPLINK' USING DSPLY,                            \n      000948                                 SECOND-PANEL.                     \n      000949       * -----------------------------------------------*          \n      000950       * .. Now to send the third panel which explains  *          \n      000951       *    what we have done so far .. ..              *          \n      000952       *                                                *          \n 569", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cd84b196a840-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n      000953       * -----------------------------------------------*          \n ---> 000954        DISPLAY-3RD-PANEL.\nThe application removes the Keep Window and the unconditional breakpoint.\nNOTE\n:\n\u2022If you have more than one data item displayed in the Keep Window, you can specify a single item to be\nremoved. For example, to remove just the line that displays Tasknum, you enter the command: remove\ntasknum.\n\u2022The R line command also removes all items in the Keep Window that are contained in the statement to the\nright of the line command. For example, you tab down to the statement containing Tasknum, type R, and\npress Enter.\nContinue Execution\nFollow these steps:\n1.Type GO to continue program execution.CAMRCOB2 next displays a screen confirming that you have successfully\ncorrected the problem in the demo program.\n2.Press Enter.CAMRCOB2 displays the following demo summary screen.\n3.To complete this part of the sample test session, press Enter.CAMRCOB2 displays the demo exit screen.\n4.Exit the demo program by pressing Enter. The Execution Control Panel displays. Each time that you complete or quit\na foreground test session, the application returns you to the Execution Control Panel with the message: ENDED,\nRETURN CODE=XX\nNOTE\nTo end the demo session, exit the application using the Roscoe  END-key (usually PF3) or the ISPF END-key or\ncommand.\nWhat You Have Learned\nThe demo session has taught you the basics of using this product to test a program. You have learned how to:\n\u2022Specify the program that you want to test.\n\u2022Begin program execution.\n\u2022Interpret the diagnostic information that the application provides when an error is detected.\n\u2022Display and modify main storage.\n\u2022Set and remove a breakpoint.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cd84b196a840-1", "text": "\u2022Display and modify main storage.\n\u2022Set and remove a breakpoint.\n\u2022Resume program execution.\nBasic Batch Link Demo\nThis section takes you step-by-step through the basic Link demo session.\nPerforming the demo at a terminal is the best way to begin learning about the application.\nThe basic demo session illustrates many of the testing and debugging tasks that you use on your own programs.\nDemo Session Objectives\nThis demo session builds on what you have learned in the Basic Foreground Demo Session. The focus in this section is\non using the Batch Link features:\n 570", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7f1cc8b10297-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Select JCL to execute the program you want to debug.\n\u2022Select a running job that is waiting to be debugged.\n\u2022Connect your terminal to a batch job and begin debugging that program.\nBefore You Begin\nThe source for the Batch Link Demo program, CAMRCOBB, is in CAI.CAVHSAMP. Use the compile procedure that you\ncustomized during the installation to compile, link, and post-process the COBOL program CAMRCOBB.\nBegin the Batch Link Demo\nTo begin the demo session, access the application and select the Batch Link Facility option from the menu. This brings\nyou to the Batch Link Option Menu.\nFrom this point, you can select the JCL that executes the program that you want to run in batch. Select Option 1. The\nBatch Link JCL Conversion panel displays.\nOn this panel, you can provide the JCL member that you want to execute in batch. For the demo, enter\nCAI.CAVHJCL(DEMOJCL) in the Other Partitioned Data Set field. Note that your installer might change CAI to another\nhigh-level qualifier. Ensure that the data set name is correct.\nAfter entering the JCL that you want to submit, the Batch Link Conversion Options panel displays.\nHere you can specify conversion options. For a full description of these options, see Batch Link Facility. For the\npurposes of the demo, no changes are required on this panel. Press Enter. For a multi-step job, you would see a STEP\nSELECTION panel where you could select one or more steps to be debugged. This JCL stream, however, contains just\none step.\nThe next panel shows the converted JCL:\n//DEMOJCL  JOB  (UNKNOWN),UNKNOWN  *** JOB STATEMENT SUPPLIED ***", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7f1cc8b10297-1", "text": "//INSTRUCT DD   *                                                     \n*----------------------------------------------------------------     \n*    BATCH LINK DEMO INSTRUCTIONS                               *     \n*                                                               *     \n*    AFTER MODIFYING THIS JCL TO CONFORM TO YOUR INSTALLATION   *     \n*    STANDARDS, PLEASE DELETE THIS INSTRUCT DD STATEMENT.       *     \n*                                                               *     \n*    1. MODIFY THE JOB CARD FOR YOUR INSTALLATION.              *     \n*                                                               *     \n*    2. MODIFY THE HIGH LEVEL QUALIFIER FOR THE IVP.LOAD        *     \n*       LIBRARY IN STEPLIB.                                     *     \n*                                                               *     \n*---------------------------------------------------------------*     \n//STEP1    EXEC PGM=CAMRBL01,REGION=4M                                \n//INT1OPTS DD *                                                       \n  EXEC=CAMRCOBB,PROFILE=USER01                                       \n/*                                                                    \n//INT1PARM DD DISP=SHR,DSN=CAI.CAVHSAMP                     \n//INT1LOAD DD DISP=SHR,DSN=CAI.CAVHLOAD                       \n//INT1PNLL DD DISP=SHR,DSN=CAI.CAVHPNL1                       \n//INT1MSGL DD DISP=SHR,DSN=CAI.CAVHMSG0                      \n//INT1PROF DD DISP=SHR,DSN=CAI.PROFLIB                      \n//INT1CLIB DD DISP=SHR,DSN=CAI.CAVHSRC                     \n//INT1CLOG DD SYSOUT=*                                                \n//INT1REPT DD SYSOUT=*                                                \n 571", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c283fcf06d36-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n//STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD                       \n//         DD   DISP=SHR,DSN=CAI.IVP.LOAD    <=== CHANGE              \n//SYSPRINT DD   SYSOUT=*                                              \n//SYSOUT   DD   SYSOUT=*           \nMake the necessary changes to the JCL as documented in the JCL. The changes include adding a job card to the\nJCL, changing the \u201cCAI\u201d high-level qualifier of the IVP load library to the correct high-level qualifier and removing the\nINSTRUCT DD. When these changes are complete, submit the JCL. You return to the Batch Link Option menu. The demo\nprogram, CAMRCOBB, is now waiting to be debugged. Select option 2 to link your ID to the batch job. If you select option\n2 and you get a message NO BATCH JOBS AVAILABLE, the job you just submitted has not started executing.\nWhen it does execute, you see a screen that looks similar to the following panel:\n----------------- CA InterTest Batch Link Selection --------------------\nCOMMAND INPUT ===>                                          SCROLL ===> PAGE\n           *         *         *         *         *        *         *                            \n     #     Jobname   Stepname  Program   Owner     User     Trans     SYSID                 \n     **************************** TOP OF DATA *********************************\n     1     JOB01A    STEP1     TESTPGM   USER01                       TSO01                     \n     2     JOB02A    STEP1     CAMRCOBB  USER02                       TSO02    \n     3     JOB03X    RUN       PAYROLL   USER03   LINKED BY USER03    TSO01    \n     ************************* BOTTOM OF DATA *********************************", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c283fcf06d36-1", "text": "************************* BOTTOM OF DATA *********************************  \nThis screen lists programs that are either currently being debugged or waiting to be linked to a terminal. In this case, there\nare three programs executing, two waiting to be debugged. Select the job that you submitted in batch by typing S next to it\nand pressing Enter. The Monitor Control panel displays.\nEnter CAMRCOBB in the monitored programs list and enter the PROTSYM that contains the symbolics for CAMRCOBB\nin the Symbolic Files list. As with the foreground demo, after pressing Enter, the Initial Intercept panel displays. From this\npoint, the use of the Batch Link feature does not differ from using the product in foreground. You can set breakpoints,\nchange the value of data items, control program execution, split your screen, and so on.\nType GO to begin execution of the program. You stop at COBOL statement ADD 1 TO TASKNUM due to an S0C7\nABEND Intercept. Set the value of TASKNUM to a valid value using the SET command: SET TASKNUM = 1\nType GO and the program runs to completion.\nYou return to the Batch Link Option panel. The completion code of the step is indicated in the upper right corner of the\nscreen.\nTest Your Programs Using Batch Link\nNOTE\nYou must first populate a PROYSYM to create the symbolics for a program you want to debug. This can be done\nby compiling and post-processing the program using the procs customized during the install, or by using the\nUtility option 2, ADD. For more information about the Utility option, see InterTest Batch Utilities. \nAccess InterTest Batch and select the Batch Link Facility option from the menu. The Batch Link Option Menu displays.\nSelect Option 1, which lets you prepare existing JCL to be submitted in batch for debugging. The Batch Link JCL\nConversion panel displays.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c283fcf06d36-2", "text": "Conversion panel displays.\nSpecify where the JCL is located. If your JCL is stored in a Panvalet  or a Librarian  data set, indicate that on this panel.\nPress Enter. The Batch Link Conversion Options panel displays.\nEnter any system PROCs that are required for this JCL to execute or provide a pre-allocated DD that contains these\nPROCs. For a description of the fields on this panel, see Batch Link Facility. Press Enter.\nThe Step Selection List panel displays:\n 572", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c36fb2b71fec-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n--------------------- CA InterTest/Batch Step Selection List -------------------\nCOMMAND INPUT ===>                                            SCROLL ===> PAGE\n     Select one or more of the following Steps:\n     **************************** TOP OF DATA ********************************\n     1 //STEP1 EXEC PGM=ISFBR14\n     2 //STEP2 EXEC PGM=TEST2,REGION=4M\n   S 3 //RUN   EXEC PGM=COB0C7,REGION=4M,PARM='/RPTOPTS(ON)'\n     *************************** BOTTOM OF DATA ******************************\nThe Step Selection List panel displays a list of steps from the JCL that you selected to execute. Select the steps that you\nwant to debug. In the previous example, there is a compile step, a linkstep, and an execute step. To display the converted\nJCL, select the execute step and press Enter.\nReview the JCL to make sure it is the job that you want to submit in batch. Type SUB to submit the job. Pressing PF3\ntakes you to the Batch Link Option Menu.\nSelect option 2. This option displays a list of programs that are either currently being debugged, or that are waiting to\nbe linked to a terminal. Select the job that you submitted in batch by typing S next to it and pressing Enter. The Monitor\nControl panel displays.\nEnter your program in the Monitored Programs list and your PROTSYM in the Symbolic Files list. Press Enter to debug\nyour program.\nWhat You Have Learned\nThis Batch Link Demo has taught you the basics of using this product to test a program running in batch. You have\nlearned how to:\n\u2022Submit converted JCL in batch.\n\u2022Link a program running in batch to your terminal.\n\u2022Debug a program running in batch.\n\u2022Test a program running in batch.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c36fb2b71fec-1", "text": "\u2022Debug a program running in batch.\n\u2022Test a program running in batch.\nAdvanced Demo Session\nThis demo covers more advanced Foreground and Basic Batch Link features.\nThe Basic Foreground Demo Session and Basic Batch Link Demo illustrate the basics of working with the application. The\nsessions presented here let you use some of the more advanced features. This part of the demo is modular and lets you\nchoose the option from a menu. Each option illustrates a different feature from the following list:\nOption 1\nPerform time-driven execution.\nOption 2\nSet conditional breakpoints.\nOption 3\nUpdate source code.\nOption 4\nInterrupt a program loop.\nOption 5\nTrace program execution.\nOption 6\nWork with indexed tables.\n 573", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d6e901e340d4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nThis option is not available in the Assembler demo.\nOption 7\nGenerate a histogram report.\nNOTE\nBefore accessing the Demo Session Options Menu, you must complete the setup steps that are outlined in the\nAdvanced Demo Preliminaries. You also must know if the names of the following libraries have been changed at\nyour installation:\n\u2022CAVHPROC\n\u2022CAVHSAMP\n\u2022ALIB\n\u2022INCLI\nAdvanced Demo Preliminaries\nThis session is an advanced Foreground and Batch Link demo that uses the same program as the basic demo session.\nThe advanced demo session uses the same program that is used in the basic demo:\n\u2022CAMRCOB2 or CAMRDMR2 for COBOL II and higher users\n\u2022CAMRCOB or CAMRDMR for COBOL/VS users\n\u2022CAMRPLI for PL/I users\nTo begin the advanced demo session, perform the following setup steps:\n\u2022Allocate data sets to your test session.\n\u2022Set several breakpoints from the Initial Intercept panel.\nAfter you execute the program, branch to the Demo Session Options Menu. The setup steps are described next.\nAccess the Initial Intercept Panel for the Demo Program\nIf you just completed the basic demo, the application brings you to the Execution Control panel, with your previous entries\nfor the Basic Demo displayed. From this point, perform the following actions:\n1.Press  Enter. The Monitor Control Entry panel is displayed with your previous entries.\n2.Press  Enter. The Initial Intercept panel is displayed. Continue with the section, Split Your Screen.\nBeginning the basic demoIf you have not just completed the basic demo, follow the beginning section of the Basic\nForeground Demo Session to get to the Initial Intercept panel. The sections to follow include:\n\u2022Accessing the Primary Option Menu\n\u2022File allocation", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d6e901e340d4-1", "text": "\u2022Accessing the Primary Option Menu\n\u2022File allocation\n\u2022Specifying the program to be tested\nSplit Your Screen\nISPF users\nTab a few lines down your screen and press the SPLIT PF key that is defined in your ISPF profile (normally PF2).\nThe ISPF Primary Option Menu displays in the bottom half of your screen.\nRoscoe  users\nEnter the Roscoe  SPLIT sequence.\nA second Roscoe  panel displays.\n 574", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8e30b0d24f2b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe CAMRCOB2 Initial Intercept Panel with split-screen (ISPF users) is shown next.\nCAMRCOB2 ---------- CA InterTest Batch *INITIAL* Intercept -------------------\nCOMMAND ===>                                                  SCROLL ===> CUR \nTRACE=> 000876                                                                \n      000875        PROCEDURE DIVISION USING PARAMETER-AREA.                  \n *--> 000876        START-PROGRAM.                                            \n *--> 000877            OPEN OUTPUT REPORT-OUT.                               \n      000878       * -----------------------------------------------*         \n      000879       * Welcome to the <productname> COBOL II     *         \n      000880       * Demonstration Program. You are now at the      *         \n      000881       * Initial Breakpoint panel which is displayed    *         \n      000882       * upon entry to the first program to be tested.  *         \n      000883       * At this point, other breakpoints can be set    *         .  .  .  .  .  .  .  .  .  .  .\n  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . \n-----  -------  ------  ISPF/PDF PRIMARY OPTION MENU                           \n-----------------------       VERSION 3 RELEASE 1         ------------------- \nOPTION  ===>                                                                   \n                                                            USERID   -xxxxxxx  \n   0  ISPF PARMS  - Specify terminal and user parameters    TIME     -14:37    \n   1  BROWSE      - Display source data or output listings  TERMINAL -3278     \n   2  EDIT        - Create or change source data            PF KEYS  -24", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8e30b0d24f2b-1", "text": "2  EDIT        - Create or change source data            PF KEYS  -24       \n   3  UTILITIES   - Perform utility functions               DATE(G)  -14/12/18 \n   4  FOREGROUND  - Invoke lang. processors in foreground   DATE(J)  -14.352   \n   5  BATCH       - Submit job for language processing                         \n   6  COMMAND     - Enter TSO command or CLIST                                 \n   7  DIALOG TEST - Perform dialog testing                                     \nAdvanced Demo Data Sets\nThe advanced demo also requires the following two extra data sets:\n\u2022User report data set (ddname: INT1REPT)\n\u2022Command library data set (ddname: INT1CLIB)\nUse the user report data set to store the HISTOGRAM and XSUM reports, which are used in Option 7 of the advanced\ndemo.\nCreate and Allocate INT1REPT Data Sets\nUsers must define their own INT1REPT data set. Create the INT1REPT data set using one of the following methods.\nMethod 1\n1.Use ISPF or Roscoe  to enter the JCL shown in the sample INT1REPT Create in the following example:\n //yourjob   JOB                                       \n //ALLOC     EXEC PGM=IEFBR14\n //INT1REPT  DD DSN=userid.INT1REPT,DISP=(,CATLG), \n //          DCB=(RECFM=FBA,LRECL=131,BLKSIZE=6157),\n //          UNIT=SYSDA,\n //          SPACE=(TRK,(30,5))\n1.Submit the job to create the data set.\n 575", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "acef52b7ee98-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n2.Check the condition code of the job to verify that the INT1REPT data set was created.\n3.Perform one of the following commands to allocate the data set:\nISPF users\nSelect Option 6 (command) from the ISPF Primary Menu and key in the command:\n     ALLOC DD(INT1REPT)DATASET('userid.INT1REPT')SHR  \n\u2013Roscoe  users\n     ALLOC INT1REPT DSN=userid.INT1REPT DISP=SHR  \n4.Press Enter.\nTSO or Roscoe  allocates the data set.\nMethod 2\n1.Use option 3.2 from the ISPF/PDF Primary Option Menu to create the INT1REPT data set.\nUse the information in the Method 1 JCL when allocating INT1REPT. In the Method 1 JCL, in the SPACE definition, 30\nis the primary space and 5 is the secondary.\nFor more help using option 3.2, ISPF provides excellent online help that is accessible with the PF1 key.\n2.Check to verify that the INT1REPT data set was created.\n3.Perform one of the following commands to allocate the data set:\nISPF users\nSelect Option 6 (command) from the ISPF Primary Menu and key in the command:\n    ALLOC DD(INT1REPT)DATASET('userid.INT1REPT')SHR \n    ALLOC INT1REPT DSN=userid.INT1REPT DISP=SHR \n\u2013Roscoe  users\n4.Press Enter.\nTSO or Roscoe  allocates the data set.\nMethod 3\n\u2022Select Option 6 (command) from the ISPF Primary Menu and allocate INT1REPT to a SYSOUT class with the\nfollowing command:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "acef52b7ee98-1", "text": "following command:\n ALLOCATE FI(INT1REPT) SYSOUT(x) \nx is the sysout class that you want the reports to be written to.\nINT1REPT is allocated to SYSOUT.\nNOTE\nA CLIST, INT1REPT, exists that creates a user report data set.\nINT1CLIB\nThe command library data set, which was created during the installation, can be shared by all users. The default name for\nthis data set is CAI.CAVHSAMP, but this name may have been changed by the installer. INT1CLIB should be allocated\nautomatically. Consult your installer to verify.\nThree of the members in the command library contain include commands to set the breakpoints required for the advanced\ndemos. They are:\n\u2022ASMINCL commands for Assembler demo\n\u2022DEMOINCL commands for COBOL demos\n\u2022PLIINCL commands for PL/I demo\n 576", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b79d4ce1871d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAllocate INT1CLIB Data Sets\nINT1CLIB data sets should be allocated automatically. In case the allocation does not occur automatically, these\ninstructions describe how to allocate command library data sets.\nFollow these steps:\n1.Key in one of the following commands:\nISPF users\nSelect Option 6 (command) from the ISPF Primary Menu and key in the command:\n     ALLOC DD(INT1CLIB) DATASET('CAI.CAVHSAMP') SHR    \n\u2013Roscoe  users\n     ALLOC INT1CLIB DSN=CAI.CAVHSAMP DISP=SHR  \n2.Press Enter.\nTSO or Roscoe  allocates the data set.\nNOTE\nYour system installer may have changed CAI to another high-level qualifier. Check with your installer.\nAdvanced Demo Session for COBOL\nThis section illustrates a COBOL advanced demo session using CAMRCOB2.\nThe screen images for the other COBOL demos may vary from the images that are shown here, but the steps for\nperforming the demo are the same.\nInclude Unconditional Breakpoints\nNow you are going to set unconditional breakpoints at several procedure names in the demo program. In the COBOL\nBasic Demo Session, you set an unconditional breakpoint by using the U or ) line command, which are both equivalent\nto the UNCOND command. However, a quicker way to include unconditional breakpoints for a test session is to place the\nbreakpoint commands in a data set member, and simply include that member when the Initial Intercept panel displays.\nThe DEMOINCL data set member of CAI.CAVHSAMP contains the application commands that set the breakpoints that\nare required to use the Advanced Options Demo for COBOL. Include this data set member as follows:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b79d4ce1871d-1", "text": "Type the following command at the *Initial* Intercept panel: include demoincl and press Enter .\nThe application processes the commands in the demoincl data set, and returns the following message in the upper-right\ncorner of the screen: BREAKPOINT SET.\n CAMRCOB2 ---------- CA InterTest Batch *INITIAL* Intercept ----- BREAKPOINT SET\n COMMAND ===>                                                  SCROLL ===> CUR \n TRACE=> 000876                                                                 \n       000875        PROCEDURE DIVISION USING PARAMETER-AREA.                   \n  *--> 000876        START-PROGRAM.                                             \n  *--> 000877            OPEN OUTPUT REPORT-OUT.                                \n       000878       * -----------------------------------------------*          \n       000879       * Welcome to the <productname> COBOL II     *          \n       000880       * Demonstration Program. You are now at the      *          \n       000881       * Initial Breakpoint panel which is displayed    *          \n       000882       * upon entry to the first program to be tested.  *          \n       000883       * At this point, other breakpoints can be set    *          \n       000884       * and control commands can be issued before  the *          \n       000885       * program is executed.                           *          \n 577", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ebfbd61f1c25-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n       000886       * -----------------------------------------------*          \n  *--> 000887            MOVE  R1498-TIMEI TO R1498-TIME.                       \n  *--> 000888            PERFORM TIME-EDIT THRU TIME-EDIT-EX.                   \n       000889       *                                                           \n  *--> 000890            MOVE  R1498-TIMEO TO R1498-TIME.                       \n  *--> 000891            PERFORM TIME-EDIT THRU TIME-EDIT-EX.                   \n  *--> 000892            GO TO DISPLAY-1ST-PANEL.                               \n       000893       * -----------------------------------------------*          \n       000894       *    THIS ROUTINE EDITS INPUT TIME FOR VALIDITY  *          \nAccess the Demo Session Options Menu\nAfter you set the required breakpoints, you can access the Demo Session Options Menu by executing the demo program\nand choosing the Advanced Options Menu from the Welcome panel.\nFollow these steps:\n1.From the Initial Intercept panel, type GO and press Enter to execute the program.\nThe demo program begins execution and displays the Welcome panel.\n2.Press PF2 to access the Options Menu for the Advanced Demo Session.\nThe Advanced Options Preliminary Screen is displayed. This screen reminds you not to access the Options Menu\nwithout including the data set member DEMOINCL.\n3.Press Enter to continue.\nThe Demo Session Options Menu displays.\nEach of the Options on the menu is independent and can be performed in any order. To use an Option, follow the\nappropriate section. Upon completing an Option, you return to the Menu.\nBefore you start, you should know that to interrupt a loop you must press the ATTN or PA1 key. Try the ATTN key first. If", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ebfbd61f1c25-1", "text": "that does not interrupt the loop, your testing environment requires you to use the PA1 key. If you use PA1, you may need\nto press RESET first.\nExit the Advanced Options Demo\nYou can exit the demo from the Options Menu at any time.\nFollow these steps:\n1.Press PF3.\nThe End Demo Session screen displays.\n2.Press Enter. The Program Exit Intercept panel displays.\n3.Type GO and press Enter to execute the program. The demo program ends, and the Entry panel displays.\nReturn to the Advanced Options Demo Session\nIf you exit the demo, you can return at any time to perform another Advanced Option. Repeat the steps in the Access the\nDemo Sessions Options Menu. Remember to enter the following command at the Initial Breakpoint screen:\n include demoincl \nOption 1 Time-Controlled Execution\nThis option illustrates how you can slow the execution of your program. The SLOW command executes one verb in your\nprogram every few seconds. The exact time interval is specified when you issue the SLOW command. Using the SLOW\ncommand together with a keep window is an effective testing technique. This technique lets you halt the program when\nyou see a problem without having to determine the breakpoint in advance.\n 578", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7b54b42a5854-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nBefore you proceed, complete the steps that are outlined in Advanced Demo Preliminaries, and have the Demo\nSession Options Menu that is displayed on your screen.\nThis option requires you to interrupt the program by pressing the ATTENTION key or the PA1 key. Before you proceed,\nlocate each of these keys on your keyboard. If you need help to find the keys, ask a technical support person before you\nbegin.\nType Option 1 and Press Enter.\nCAMRCOB2 displays the panel that describes what occurs in this part of the demo session.\nPress  Enter. The application halts CAMRCOB2 at an unconditional breakpoint set at the paragraph PAY-CALC. The first\nexecutable statement in that paragraph is the current statement, and is highlighted.\nType the following command: k ytd; k x-axis.\nInterTest Batch displays a keep window showing the current values of YTD and X-AXIS.\nThe following sample screen shows the keep window for YTD and X-AXIS. Open a keep window that displays the values\nof YTD and X-AXIS by entering commands shown. You can use the short form of the keep command (k), and the TSO\ncommand delimiter (normally a semi-colon), to string multiple commands on a single command line.\nCAMRCOB2 ---------- CA InterTest Batch UNCOND BEFORE Intercept --------------- \nCOMMAND ===>                                                  SCROLL ===> CUR \nTRACE=> 001055 001053 001052 001051 001049 001043 001042 001040 001035 001017 0\n      -------------------------------------------------------------------------\n      1F08CB11 ND-OT 000683 03 YTD                          +0000000.00       \n      1F08C8E0 AN    000553 05 X-AXIS                                         \n      -------------------------------------------------------------------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7b54b42a5854-1", "text": "-------------------------------------------------------------------------\n      001054       *                                                           \nU---> 001055        PAY-CALC.                                                  \n ---> 001056            PERFORM POPULATE-GRAPH THRU POPULATE-GRAPH-EX          \n      001057                VARYING SUB-4 FROM 1 BY 1                          \n      001058                    UNTIL SUB-4 GREATER THAN NO-OF-HOURS.          \n ---> 001059        PAY-CALC-EX.                                               \n ---> 001060            MOVE SPACES      TO CHEQUE-LINE.                       \n ---> 001061            MOVE TOTAL-GROSS TO CHEQUE-AMOUNT.                     \n ---> 001062        PAY-RETURN.                                                \n ---> 001063            GO TO OPTIONS.                                         \n      001064       *                                                           \n ---> 001065        POPULATE-GRAPH.                                            \n ---> 001066            MOVE MONTH-ITEM(SUB-4)     TO X-AXIS-YTD.              \n ---> 001067            MOVE TOKEN-ITEM            TO X-AXIS-R(SUB-4).         \n ---> 001068            ADD  MONTHLY-AMOUNT(SUB-4) TO YTD.                     \n ---> 001069            MOVE YTD                   TO TOTAL-GROSS.             \nIssue the SLOW command to execute one verb every 2 seconds. As the program resumes execution, you are able to see\nthe changing values of YTD and X-AXIS. In this demo, you are going to halt execution when the X-AXIS value is MAR by\npressing the ATTENTION key.\nType the following command: slow 2 and press Enter.\nThe application initiates a time-controlled execution of CAMRCOB2, at a rate of one verb every 2 seconds.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7b54b42a5854-2", "text": "When the value of X-AXIS in the keep window is MAR, press the ATTN or PA1 key. Try the ATTN key first. The Attention\nIntercept panel displays, as shown in the following panel.\nA sample Attention Intercept panel follows:\n 579", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0c9d19682008-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAMRCOB2 ---------- CA InterTest Batch ATTENTION Intercept ------------------- \nCOMMAND ===>                                                  SCROLL ===> CUR \nTRACE=> 001069 001068 001067 001066 001065 001071 001070 001069 001068 001067 0\n      -------------------------------------------------------------------------\n      1F08CB11 ND-OT 000683 03 YTD                          +0255273.52       \n      1F08C8E0 AN    000553 05 X-AXIS                       Mar ->->->        \n      -------------------------------------------------------------------------\n      001054       *                                                           \nU0001 001055        PAY-CALC.                                                  \n 0001 001056            PERFORM POPULATE-GRAPH THRU POPULATE-GRAPH-EX          \n      001057                VARYING SUB-4 FROM 1 BY 1                          \n      001058                    UNTIL SUB-4 GREATER THAN NO-OF-HOURS.          \n ---> 001059        PAY-CALC-EX.                                               \n ---> 001060            MOVE SPACES      TO CHEQUE-LINE.                       \n ---> 001061            MOVE TOTAL-GROSS TO CHEQUE-AMOUNT.                     \n ---> 001062        PAY-RETURN.                                                \n ---> 001063            GO TO OPTIONS.                                         \n      001064       *                                                           \n 0003 001065        POPULATE-GRAPH.                                            \n 0003 001066            MOVE MONTH-ITEM(SUB-4)     TO X-AXIS-YTD.              \n 0003 001067            MOVE TOKEN-ITEM            TO X-AXIS-R(SUB-4).         \n 0003 001068            ADD  MONTHLY-AMOUNT(SUB-4) TO YTD.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0c9d19682008-1", "text": "0002 001069            MOVE YTD                   TO TOTAL-GROSS.             \n 0002 001070        POPULATE-GRAPH-EX.                                         \nReview what you just did.\n\u2022You opened a keep window for two variables whose values you wished to view and compare.\n\u2022You used the command slow 2 to have the application slowly execute the program. However, during the program\nexecution, you could monitor the values of the variables in the keep window.\n\u2022You used the ATTENTION or PA1 key to stop program execution, and the Attention Intercept panel displays.\nThis combination of using keep windows, the slow command, and an Attention Intercept allows you to carefully control\nand monitor your program execution, while tracking the values of specific variables.\nNOTE\nThe Attention Intercept panel is only displayed when you press the ATTN or PA1 key after which the application\nexecutes a statement in a program that is being monitored.\nRemove the Keep Window\nBefore returning to the Options Menu of the advanced demo, remove the keep window.\nType the following command: remove all and press Enter.\nThe application removes the keep window for YTD and X-AXIS on the Attention Intercept panel.\nContinue Execution\nType GO and press Enter to continue execution. CAMRCOB2 resumes execution, and displays the Options Menu.\nThis concludes Option 1: Time Controlled Execution. Select another option and go to the appropriate section in this article,\nor exit the demo using PF3.\n 580", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "445f3c02619e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nOption 2 Set Conditional Breakpoints\nThis option shows you how to set and use conditional breakpoints.\nNOTE\nBefore you proceed, complete the steps that are outlined in Advance Demo Preliminaries, and have the Demo\nSession Options Menu displayed on your screen.\nFollow these steps:\n1.Type Option 2 and press Enter.\nCAMRCOB2 displays the screen that describes what occurs in this part of the demo session.\n2.Press  Enter. The application halts CAMRCOB2 at an unconditional breakpoint. The first executable statement in the\nparagraph is highlighted.\n3.Access the screen used to set conditional breakpoints. From this screen, you can set both the conditions and any\ncommands you want executed when the specified condition is met.\n4.Type the COND command and press Enter.\nThe application displays the When panel. WHEN is a synonym for COND.\n5.Make the entries on the When panel and Press Enter.\nThe application displays the following message in the top-right corner of the When panel: WHEN CONDITION SET.\n----------------------- CA InterTest Batch WHEN PANEL -------------------------\nOPTION ===>S\n \n   S - SET A WHEN CONDITION                                                  \n   R - RESET A WHEN CONDITION                                                \n   L - OR BLANK, LIST THE WHEN CONDITIONS                                    \n                                                                             \nSPECIFY DATA AREA NAME(S) AND COMPARISON CONDITION:       \n   WHEN-NAME    ===> ytdcond                                                \n   DATA-AREA-1  ===> sub-total                                              \n   OPERATOR     ===> ge       (EQ, NE, LT, GT, LE, GE, =, <>, <, >, <=, >=) \n   DATA-AREA-2  ===> 600.00                                                 \n   AFTER        ===> N         (Y/N)                                         \n                                                                             \nCOMMANDS TO BE EXECUTED AT WHEN CONDITION:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "445f3c02619e-1", "text": "COMMANDS TO BE EXECUTED AT WHEN CONDITION:                                   \n===>  k sub-total; set total-gross=2000; k total-gross  \n6.Press PF3 to exit the When panel. The application brings you to the previous Breakpoint Intercept panel.\n7.Continue execution by typing GO and pressing Enter. CAMRCOB2 resumes execution until the condition that you set\nfor the YTDCOND breakpoint is met. When the value of SUB-TOTAL is greater than or equal to 600, the application\nhalts execution, and executes the commands that you entered for the conditional breakpoint. The application displays\na keep window for SUB-TOTAL, sets TOTAL-GROSS to 2000, and then displays TOTAL-GROSS in the keep window.\nYour screen should look like the Intercept panel in the following panel.\nCAMRCOB2 ---------- CA InterTest Batch WHEN YTDCOND BEFORE Intercept --------- \n COMMAND ===>                                                  SCROLL ===> CUR \n TRACE=> 001102 001101 001100 001104 001103 001102 001101 001100 001104 001103 \n       ------------------------------------------------------------------------\n       1F08CAFC ND-OT 000679 03 SUB-TOTAL                    +0000971.68       \n       1F08CB08 ND-OT 000682 03 TOTAL-GROSS                  +0002000.00       \n       ------------------------------------------------------------------------\n  0003 001101            ADD BILLING-AMOUNT(SUB-7) TO SUB-TOTAL.                \n  0002 001102            MOVE SUB-TOTAL            TO BILL-YTD.                 \n 581", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1a4be0c690fc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  0002 001103        BILL-CALC-EX.                                              \n  0002 001104            EXIT.                                                  \n       001105                                                                   \n       001106                                                                   \n  ---> 001107        DEMONSTRATE-SPLIT-SCREEN.                                  \n       001108       * -----------------------------------------------*          \n       001109       *    This section of the Demo shows you how to   *          \n       001110       *    SPLIT the screen .. ..                      *          \n       001111       * -----------------------------------------------*          \n  ---> 001112            CALL 'ISPLINK' USING DSPLY,                            \n       001113                                 COBDPN73.                         \n  ---> 001114            MOVE  4        TO    COBDPN71-LENGTHS.                 \n  ---> 001115            CALL 'ISPLINK' USING VCOPY,                            \n       001116                                 VCOPY-COBDPN71,                   \nA sample Intercept panel showing condition YTDCOND has been met follows:\nNow remove the conditional breakpoint before continuing.\nFollow these steps:\n1.Using the WHEN command to return to the When panel.\nThe When panel displays.\n2.Type the following values on the When panel and press Enter:\nOPTION: ===> r\nWHEN NAME ===> ytdcond\nThe application displays the following message in the top-right corner of the When panel: WHEN DELETED.\n3.Press PF3 to exit the When panel. The application brings you to the previous Intercept panel.\nRemove the Keep Window and Continue Execution\nRemove the keep window before continuing execution.\nFollow these steps:\n1.Type the REMOVE ALL command and Press Enter.\nThe keep window is removed.\n2.Type GO and press Enter. CAMRCOB2 resumes execution and displays the Options Menu.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1a4be0c690fc-1", "text": "2.Type GO and press Enter. CAMRCOB2 resumes execution and displays the Options Menu.\nThis concludes Option 2: Conditional Breakpoints. Select another option and go to the appropriate section, or exit the\ndemo using PF3.\nOption 3 Update Source Code\nThis option illustrates how you can use the ISPF or Roscoe  split-screen capability from any screen. One way to use this\nfeature is to update your source code when you find errors during your test session.\nNOTE\nBefore you proceed, completed the steps that are outlined in Advanced Demo Preliminaries, and have the Demo\nSession Options Menu displayed on your screen.\nFollow these steps:\n1.Type Option 3 and press Enter.\nCAMRCOB2 displays the screen that describes what occurs in this part of the demo session.\n2.Press Enter. The application halts CAMRCOB2 at an unconditional breakpoint at the paragraph SPLIT-SCREEN.\n3.ISPF users: Tab about halfway down your screen and press the SPLIT PF key that is defined in your ISPF profile\n(normally PF2).\n 582", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "505c67ab5e81-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe ISPF Primary Option Menu displays in the bottom half of your screen.\nRoscoe  users: Enter the Roscoe  SPLIT sequence.\nA second Roscoe  panel displays.\nA sample showing using a split-screen from an Intercept Panel (ISPF Users) follows:\nCAMRCOB2 ---------- CA InterTest Batch UNCOND BEFORE Intercept --------------- \n COMMAND ===>                                                  SCROLL ===> CUR \n TRACE=> 001123 001121 001115 001114 001112 001107 001021 001020 001018 001016 \n  ---> 001122               GO TO OPTIONS.                                      \n U---> 001123        SPLIT-SCREEN.                                              \n  ---> 001124            MOVE  R1498-TIMEO TO R1498-TIME.                       \n  ---> 001125            GO TO OPTIONS.                                         \n       001126       * -----------------------------------------------*          \n       001127       * From this Unconditional Breakpoint you can     *          \n       001128       * press the PF key assigned to the SPLIT command *          \n       001129       * which takes you to the ISPF Main Menu.         *          \n       001130       * -----------------------------------------------*          \n       001131                                                                   \n       001132                                                                   \n.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . \n-----------------------  ISPF/PDF PRIMARY OPTION MENU     ISPF HELP - 461-1005  \n-----------------------       VERSION 3 RELEASE 1         --------------------  \nOPTION  ===>                                                                    \n                                                            USERID   - PHUMPHR", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "505c67ab5e81-1", "text": "OPTION  ===>                                                                    \n                                                            USERID   - PHUMPHR  \n   0  ISPF PARMS  - Specify terminal and user parameters    TIME     - 14:37    \n   1  BROWSE      - Display source data or output listings  TERMINAL - 3278     \n   2  EDIT        - Create or change source data            PF KEYS  - 24       \n   3  UTILITIES   - Perform utility functions               DATE(G)  - 14/12/18 \n   4  FOREGROUND  - Invoke lang. processors in foreground   DATE(J)  - 14.352   \n   5  BATCH       - Submit job for language processing                          \n   6  COMMAND     - Enter TSO command or CLIST                                  \n   7  DIALOG TEST - Perform dialog testing                                      \nUpdate Your Source Code\nIf you found an error in your program code, use the ISPF menu or Roscoe  to access and edit your source code before\ncontinuing with your test session.\nFor example, in the basic demo, the application stopped execution of the program because it detected an S0C7 ABEND.\nYou were able to continue execution by dynamically changing the value of Tasknum to zero. This was a one-time patch.\nTo correct the problem, update your source code so that Tasknum is properly initialized. You can do this from any\nIntercept panel by splitting your screen to edit your source code.\nContinue Execution\nFollow these steps:\n1.ISPF users: Remove your ISPF split-screen using the command: =X\nRoscoe  users: Use the Roscoe  END key to end the second session.\nYou return to a full-screen display of the Unconditional Breakpoint shown in the previous panel.\n2.Type GO and press Enter to continue execution. You return to the Demo Options Menu.\n 583", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "238a2c0b0e61-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThis concludes Option 3: Update Source Code. Select another option and go to the appropriate section, or exit the demo\nusing PF3.\nOption 4 Interrupt a Looping Program\nThis option illustrates how to interrupt and verify that you have a looping program. The option also illustrates the use of the\nskip command.\nNOTE\nBefore you proceed, completed the steps that are outlined in Advanced Demo Preliminaries, and have the Demo\nSession Options Menu that is displayed on your screen.\nThis option requires you to interrupt the program by pressing the ATTENTION key or the PA1 key. Before you proceed,\nlocate each of these keys on your keyboard. If you need help, ask a technical support person before you begin.\nFollow these steps:\n1.Key in Option 4. Press Enter.CAMRCOB2 displays the screen that describes what occurs in this part of the demo\nsession.\n2.Press Enter. The application halts CAMRCOB2 at an unconditional breakpoint set at ORDER-CALC. A sample screen\nshowing the CAMRCOB2 stopped at ORDER-CALC follows:\nCAMRCOB2 ---------- CA InterTest Batch UNCOND BEFORE Intercept --------------- \n COMMAND ===>                                                  SCROLL ===> CUR \n TRACE=> 001232 001225 001219 001218 001216 001210 001023 001022 001020 001018 \n       001231       * -----------------------------------------------*          \n U---> 001232        ORDER-CALC.                                                \n  ---> 001233            MOVE CUSTOMER-VALUES TO CUSTOMER-ORDER.                \n  ---> 001234            MOVE ZEROES TO ORDER-SUB-TOTAL, SUB-6, LOOP-OUT.       \n  ---> 001235            PERFORM TOTAL-ORDER THRU TOTAL-ORDER-EX", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "238a2c0b0e61-1", "text": "---> 001235            PERFORM TOTAL-ORDER THRU TOTAL-ORDER-EX                \n       001236                UNTIL SUB-6 EQUAL 5.                               \n U---> 001237        ORDER-CALC-EX.                                             \n  ---> 001238            GO TO OPTIONS.                                         \n  ---> 001239        TOTAL-ORDER.                                               \n  ---> 001240            ADD 1 TO SUB-6.                                        \n  ---> 001241            ADD 1 TO LOOP-OUT.                                     \n  ---> 001242            MULTIPLY UNIT-PRICE(SUB-6) BY NO-OF-WIDGETS(SUB-6)     \n       001243                GIVING ITEM-TOTAL.                                 \n  ---> 001244            ADD ITEM-TOTAL TO ORDER-SUB-TOTAL.                     \n  ---> 001245            MOVE 1 TO SUB-6.                                       \n  ---> 001246        TOTAL-ORDER-EX.                                            \n       001247       *------------------------------------------------*          \n       001248       * The code above will loop. The loop can be      *        \nNOTE\nIf the Frequency Counter arrows and numbers are not displayed along the left side of your screen, turn on\nthe frequency display by entering the command: freq.\n3.Continue execution by typing GO and pressing Enter. CAMRCOB2 resumes execution. Note that the system light\nremains on. There are other breakpoints, and screen panels in the demo program code, yet all you see is the system\nlight. This behavior is symptomatic of a looping program.\n4.Halt the program to see what is going on. Press the ATTN or PA1 key. Try the ATTN key first. If that does not work,\nyour testing environment requires you to use the PA1 key. Press RESET before pressing the PA1 key to unlock the\nterminal keyboard. The Attention Intercept panel displays.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "238a2c0b0e61-2", "text": "terminal keyboard. The Attention Intercept panel displays.\nContinue with the Continuing from the Attention Routine section.\n 584", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9afaf0a11a31-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nIf you do not successfully stop execution with the ATTN or PA1 key before 5000 executions of the demo\nprogram loop, you reach a safety net conditional breakpoint. If you reach this breakpoint, follow the instructions\nin the next session to continue.\nContinue from the \u201cSafety Net\u201d Conditional Breakpoint\nFollow this section only if you see the breakpoint in the following panel. If you do not, continue with Continuing from the\nAttention Routine.\nA sample screen showing a Safety Net Conditional Breakpoint of a Demo Loop follows:\nCAMRCOB2 ---------- CA InterTest Batch WHEN LOOPCOND BEFORE Inter- SET COMPLETE\n COMMAND ===>                                                  SCROLL ===> CUR \n TRACE=> 001242 001241 001240 001239 001253 001246 001245 001244 001242 001241 \n       001231       * -----------------------------------------------*          \n U0001 001232        ORDER-CALC.                                                \n  0001 001233            MOVE CUSTOMER-VALUES TO CUSTOMER-ORDER.                \n  0001 001234            MOVE ZEROES TO ORDER-SUB-TOTAL, SUB-6, LOOP-OUT.       \n  0001 001235            PERFORM TOTAL-ORDER THRU TOTAL-ORDER-EX                \n       001236                UNTIL SUB-6 EQUAL 5.                               \n U---> 001237        ORDER-CALC-EX.                                             \n  ---> 001238            GO TO OPTIONS.                                         \n  5001 001239        TOTAL-ORDER.                                               \n  5001 001240            ADD 1 TO SUB-6.                                        \n  5001 001241            ADD 1 TO LOOP-OUT.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9afaf0a11a31-1", "text": "5001 001241            ADD 1 TO LOOP-OUT.                                     \n  5000 001242            MULTIPLY UNIT-PRICE(SUB-6) BY NO-OF-WIDGETS(SUB-6)     \n       001243                GIVING ITEM-TOTAL.                                 \n  5000 001244            ADD ITEM-TOTAL TO ORDER-SUB-TOTAL.                     \n  5000 001245            MOVE 1 TO SUB-6.                                       \n  5000 001246        TOTAL-ORDER-EX.                                            \n       001247       *------------------------------------------------*          \nTo continue with the looping program demo, you must press the ATTN or PA1 key before 5000 executions of the loop this\ntime. To continue the program loop, use the following steps:\n1.Type G to the left of the line:\nMOVE ZEROES TO ORDER-SUB-TOTAL, SUB-6, LOOP-0\n2.Press Enter to continue the loop execution.\n3.Press the ATTN key or the RESET, then PA1 keys. Try the ATTN key first. If that does not work, your testing\nenvironment requires you to use the PA1 key.\nNOTE\nEven if PA1 stopped the slow execution in option 1, you might need to press ATTN to stop a loop.\nYou should see the Attention Intercept panel.\nTo return to the Options Menu:\n1.Enter the command: go options\n2.Press Enter.\nYou return to the Options Menu. You can try the same option again, even if you did not complete it the first time, or\nselect another option from the menu.\n 585", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "64e389393766-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nContinue from the Attention Routine\nThe Attention Intercept panel displays. A sample showing an Attention Intercept in TOTAL-ORDER Routine follows:\nCAMRCOB2 ----------- CA InterTest Batch ATTENTION INTERCEPT ------------------- \nCOMMAND ===>                                                  SCROLL ===> PAGE  \nTRACE=> 001244 001243 001242 001241 001255 001248 001247 001246 001244 001243 0 \n       001231       * -----------------------------------------------*          \n U0001 001232        ORDER-CALC.                                                \n  0001 001233            MOVE CUSTOMER-VALUES TO CUSTOMER-ORDER.                \n  0001 001234            MOVE ZEROES TO ORDER-SUB-TOTAL, SUB-6, LOOP-OUT.       \n  0001 001235            PERFORM TOTAL-ORDER THRU TOTAL-ORDER-EX                \n       001236                UNTIL SUB-6 EQUAL 5.                               \n U---> 001237        ORDER-CALC-EX.                                             \n  ---> 001238            GO TO OPTIONS.                                         \n  1926 001239        TOTAL-ORDER.                                               \n  1926 001240            ADD 1 TO SUB-6.                                        \n  1926 001241            ADD 1 TO LOOP-OUT.                                     \n  1925 001242            MULTIPLY UNIT-PRICE(SUB-6) BY NO-OF-WIDGETS(SUB-6)     \n       001243                GIVING ITEM-TOTAL.                                 \n  1925 001244            ADD ITEM-TOTAL TO ORDER-SUB-TOTAL.                     \n  1925 001245            MOVE 1 TO SUB-6.                                       \n  1925 001246        TOTAL-ORDER-EX.                                            \n       001247       *------------------------------------------------*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "64e389393766-1", "text": "001247       *------------------------------------------------*          \nCAMRCOB2 never left the TOTAL-ORDER routine, as you can see from your Attention Intercept screen display. The\ncurrent statement is highlighted.\nLook at the frequency counters to the left of the program statements. The counters show repeated execution of the\nTOTAL-ORDER statements, indicating a loop. To investigate the logic in TOTAL-ORDER, you can set a keep window for\nSUB-6 and then execute slowly using the SLOW command. This time, use the abbreviated form of the keep command: k.\nFollow these steps:\n1.Type the following command to set the keep window: k sub-6 and press Enter.\nThe application displays a keep window for the variable SUB-6.A sample screen showing the keep window to view\nSUB-6 follows:\nCAMRCOB2 ----------- CA InterTest Batch ATTENTION INTERCEPT ------------------ \nCOMMAND ===>                                                  SCROLL ===> PAGE  \nTRACE=> 001244 001243 001242 001241 001255 001248 001247 001246 001244 001243 0 \n      -------------------------------------------------------------------------\n      001424D8 NB-S  000046 77 SUB-6                       +0002.              \n      ------------------------------------------------------------------------- \n       001231       * -----------------------------------------------*          \n U0001 001232        ORDER-CALC.                                                \n  0001 001233            MOVE CUSTOMER-VALUES TO CUSTOMER-ORDER.                \n  0001 001234            MOVE ZEROES TO ORDER-SUB-TOTAL, SUB-6, LOOP-OUT.       \n  0001 001235            PERFORM TOTAL-ORDER THRU TOTAL-ORDER-EX                \n       001236                UNTIL SUB-6 EQUAL 5.                               \n U---> 001237        ORDER-CALC-EX.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "64e389393766-2", "text": "U---> 001237        ORDER-CALC-EX.                                             \n  ---> 001238            GO TO OPTIONS.                                         \n  1926 001239        TOTAL-ORDER.                                               \n  1926 001240            ADD 1 TO SUB-6.                                        \n  1926 001241            ADD 1 TO LOOP-OUT.                                     \n 586", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "70a349c2d82a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  1925 001242            MULTIPLY UNIT-PRICE(SUB-6) BY NO-OF-WIDGETS(SUB-6)     \n       001243                GIVING ITEM-TOTAL.                                 \n  1925 001244            ADD ITEM-TOTAL TO ORDER-SUB-TOTAL.                     \n  1925 001245            MOVE 1 TO SUB-6.                                       \n  1925 001246        TOTAL-ORDER-EX.                                            \n2.Type the following command to execute CAMRCOB2 one verb every 2 seconds: slow 2 and press Enter.\nCAMRCOB2 continues a slow execution. As the code executes, you can see the code that is looping, and you can see\nthe corresponding value of SUB-6 in the keep window.\nThe following sample screen of a SLOW 2 Execution shows a Loop and SUB-6 problem: \nCAMRCOB2 ---------- CA InterTest Batch STEP BEFORE Intercept ----------------- \n COMMAND ===>                                                  SCROLL ===> CUR \n TRACE=> 001244 001242 001241 001240 001239 001253 001246 001245 001244 001242 \n       ------------------------------------------------------------------------\n       1F08D1C8 NB-S  000044 77 SUB-6                        +0002.            \n       ------------------------------------------------------------------------\n       001231       * -----------------------------------------------*          \n U0001 001232        ORDER-CALC.                                                \n  0001 001233            MOVE CUSTOMER-VALUES TO CUSTOMER-ORDER.                \n  0001 001234            MOVE ZEROES TO ORDER-SUB-TOTAL, SUB-6, LOOP-OUT.       \n  0001 001235            PERFORM TOTAL-ORDER THRU TOTAL-ORDER-EX", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "70a349c2d82a-1", "text": "001236                UNTIL SUB-6 EQUAL 5.                               \n U---> 001237        ORDER-CALC-EX.                                             \n  ---> 001238            GO TO OPTIONS.                                         \n  5002 001239        TOTAL-ORDER.                                               \n  5002 001240            ADD 1 TO SUB-6.                                        \n  5002 001241            ADD 1 TO LOOP-OUT.                                     \n  5002 001242            MULTIPLY UNIT-PRICE(SUB-6) BY NO-OF-WIDGETS(SUB-6)     \n       001243                GIVING ITEM-TOTAL.                                 \n  5001 001244            ADD ITEM-TOTAL TO ORDER-SUB-TOTAL.                     \n  5001 001245            MOVE 1 TO SUB-6.                                       \n  5001 001246        TOTAL-ORDER-EX.                                            \n       001247       *------------------------------------------------*          \n       001248       * The code above will loop. The loop can be      *          \nNotice that SUB-6 changes from 1 to 2, but back to 1 again. SUB-6 is being reset to 1, and causing the program to\nloop. The value of SUB-6 is preventing the exit of the TOTAL-ORDER routine.\n3.Halt execution again by pressing the ATTENTION or PA1 key. After the Attention Routine message displays, press\nEnter.\nThe application brings you to another Attention Intercept panel. The current statement is highlighted.\n4.To dynamically correct the loop-condition, you could use the SKIP command to bypass the offending statement. The s\nline command is another form of the SKIP command.\n5.Tab down to the statement: MOVE 1 TO SUB-6, and type S to the left of the line. The following sample screen shows\nusing Skip to bypass the cause of the loop:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "70a349c2d82a-2", "text": "using Skip to bypass the cause of the loop:\nCAMRCOB2 ---------- CA InterTest Batch ATTENTION Intercept -------------------  COMMAND ===>              \n                                    SCROLL ===> CUR \n TRACE=> 001244 001242 001241 001240 001239 001253 001246 001245 001244 001242 \n       ------------------------------------------------------------------------\n       1F08D1C8 NB-S  000044 77 SUB-6                        +0002.            \n       ------------------------------------------------------------------------\n       001231       * -----------------------------------------------*          \n U0001 001232        ORDER-CALC.                                                \n 587", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "824358a0a3f7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  0001 001233            MOVE CUSTOMER-VALUES TO CUSTOMER-ORDER.                \n  0001 001234            MOVE ZEROES TO ORDER-SUB-TOTAL, SUB-6, LOOP-OUT.       \n  0001 001235            PERFORM TOTAL-ORDER THRU TOTAL-ORDER-EX                \n       001236                UNTIL SUB-6 EQUAL 5.                               \n U---> 001237        ORDER-CALC-EX.                                             \n  ---> 001238            GO TO OPTIONS.                                         \n  5002 001239        TOTAL-ORDER.                                               \n  5002 001240            ADD 1 TO SUB-6.                                        \n  5002 001241            ADD 1 TO LOOP-OUT.                                     \n  5002 001242            MULTIPLY UNIT-PRICE(SUB-6) BY NO-OF-WIDGETS(SUB-6)     \n       001243                GIVING ITEM-TOTAL.                                 \n  5001 001244            ADD ITEM-TOTAL TO ORDER-SUB-TOTAL.                     \n s5001 001245            MOVE 1 TO SUB-6.                                       \n  5001 001246        TOTAL-ORDER-EX.                                            \n       001247       *------------------------------------------------*          \n       001248       * The code above will loop. The loop can be      *          \nThe application skips the execution of the MOVE statement, and executes the code as if the MOVE statement was\nremoved.\n6.To continue execution from that point, tab up to the first statement in the TOTAL-ORDER routine, ADD 1 to SUB-6, and\ntype G to the left of the line. Your entry should match the following panel:\nThe following sample screen shows a continuing execution from the ADD Statement:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "824358a0a3f7-1", "text": "The following sample screen shows a continuing execution from the ADD Statement:\nCAMRCOB2 ---------- CA InterTest Batch ATTENTION Intercept -------------------  COMMAND ===>              \n                                    SCROLL ===> CUR \n TRACE=> 001244 001242 001241 001240 001239 001253 001246 001245 001244 001242 \n       ------------------------------------------------------------------------\n       1F08D1C8 NB-S  000044 77 SUB-6                        +0002.            \n       ------------------------------------------------------------------------\n       001231       * -----------------------------------------------*          \n U0001 001232        ORDER-CALC.                                                \n  0001 001233            MOVE CUSTOMER-VALUES TO CUSTOMER-ORDER.                \n  0001 001234            MOVE ZEROES TO ORDER-SUB-TOTAL, SUB-6, LOOP-OUT.       \n  0001 001235            PERFORM TOTAL-ORDER THRU TOTAL-ORDER-EX                \n       001236                UNTIL SUB-6 EQUAL 5.                               \n U---> 001237        ORDER-CALC-EX.                                             \n  ---> 001238            GO TO OPTIONS.                                         \n  5002 001239        TOTAL-ORDER.                                               \n g5002 001240            ADD 1 TO SUB-6.                                        \n  5002 001241            ADD 1 TO LOOP-OUT.                                     \n  5002 001242            MULTIPLY UNIT-PRICE(SUB-6) BY NO-OF-WIDGETS(SUB-6)     \n       001243                GIVING ITEM-TOTAL.                                 \n  5001 001244            ADD ITEM-TOTAL TO ORDER-SUB-TOTAL.                     \n S5001 001245            MOVE 1 TO SUB-6.                                       \n  5001 001246        TOTAL-ORDER-EX.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "824358a0a3f7-2", "text": "5001 001246        TOTAL-ORDER-EX.                                            \n       001247       *------------------------------------------------*          \n       001248       * The code above will loop. The loop can be      *          \n7.Press Enter. CAMRCOB2 resumes execution from the line where you typed G, and continues execution until it\nreaches the next unconditional breakpoint. This activity is shown in the following panel. The following screen shows an\nunconditional breakpoint at ORDER-CALC-EX:\nCAMRCOB2 ---------- CA InterTest Batch UNCOND BEFORE Intercept --------------- \n COMMAND ===>                                                  SCROLL ===> CUR \n 588", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a2bae86b7e24-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n TRACE=> 001237 001253 001246 001244 001242 001241 001240 001239 001253 001246 \n       ------------------------------------------------------------------------\n       1F08D1C8 NB-S  000044 77 SUB-6                        +0005.            \n       ------------------------------------------------------------------------\n       001231       * -----------------------------------------------*          \n U0001 001232        ORDER-CALC.                                                \n  0001 001233            MOVE CUSTOMER-VALUES TO CUSTOMER-ORDER.                \n  0001 001234            MOVE ZEROES TO ORDER-SUB-TOTAL, SUB-6, LOOP-OUT.       \n  0001 001235            PERFORM TOTAL-ORDER THRU TOTAL-ORDER-EX                \n       001236                UNTIL SUB-6 EQUAL 5.                               \n U---> 001237        ORDER-CALC-EX.                                             \n  ---> 001238            GO TO OPTIONS.                                         \n  5004 001239        TOTAL-ORDER.                                               \n  5005 001240            ADD 1 TO SUB-6.                                        \n  5005 001241            ADD 1 TO LOOP-OUT.                                     \n  5005 001242            MULTIPLY UNIT-PRICE(SUB-6) BY NO-OF-WIDGETS(SUB-6)     \n       001243                GIVING ITEM-TOTAL.                                 \n  5005 001244            ADD ITEM-TOTAL TO ORDER-SUB-TOTAL.                     \n S5001 001245            MOVE 1 TO SUB-6.                                       \n  5004 001246        TOTAL-ORDER-EX.                                            \n       001247       *------------------------------------------------*          \n       001248       * The code above will loop. The loop can be      *", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a2bae86b7e24-1", "text": "001248       * The code above will loop. The loop can be      *         \nCAMRCOB2 finally executed out of the TOTAL-ORDER routine, and continued until it reached unconditional breakpoint\nset at ORDER-CALC-EX (one of the unconditional breakpoints included in the data set member demoincl).\nYou can see from the keep window that the value of SUB-6 is 5. This value is correct to permit the exit of the ORDER-\nCALC routine. Thus, the use of the skip command allowed us to dynamically fix the program code that caused the loop,\nand continue execution.\nRemove the Keep Window and Skip Command\nBefore going back to the options menu, remove the keep window and skip command.\nFollow these steps:\n1.Type the REMOVE ALL command.\n2.Tab down and overtype the S to the left of the MOVE statement with an X and press Enter.\nThe keep window is removed, and the skip line command is removed.\n3.Continue execution by  typing GO and pressing Enter.CAMRCOB2 resumes execution and displays the Demo Session\nOptions Menu.\nThis concludes Option 4: Interrupt a Program Loop. Select another option and go to the appropriate section, or exit the\ndemo using PF3.\nOption 5 Trace Program Execution\nThis option illustrates the use of the PREVIOUS and ADVANCE commands to help you trace program execution.\nNOTE\nBefore you proceed, completed the steps that are outlined in Advanced Demo Preliminaries, and have the Demo\nSession Options Menu displayed on your screen.\nFollow these steps:\n1.Type Option 5 and press Enter.\n 589", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7d8499a59d8c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAMRCOB2 displays the screen that describes what occurs in this part of the demo session.\n2.Press Enter. The application halts CAMRCOB2 at an unconditional breakpoint that you included at the beginning of the\ndemo.\nThe following sample screen shows CAMRCOB2 at an unconditional breakpoint:\nCAMRCOB2 ---------- CA InterTest Batch UNCOND BEFORE Intercept --------------- \n COMMAND ===>                                                  SCROLL ===> CUR \n TRACE=> 001055 001158 001157 001156 001155 001153 001147 001146 001139 001137 \n       001054       *                                                           \n U---> 001055        PAY-CALC.                                                  \n  ---> 001056            PERFORM POPULATE-GRAPH THRU POPULATE-GRAPH-EX          \n       001057                VARYING SUB-4 FROM 1 BY 1                          \n       001058                    UNTIL SUB-4 GREATER THAN NO-OF-HOURS.          \n  ---> 001059        PAY-CALC-EX.                                               \n  ---> 001060            MOVE SPACES      TO CHEQUE-LINE.                       \n  ---> 001061            MOVE TOTAL-GROSS TO CHEQUE-AMOUNT.                     \n  ---> 001062        PAY-RETURN.                                                \n  ---> 001063            GO TO OPTIONS.                                         \n       001064       *                                                           \n  ---> 001065        POPULATE-GRAPH.                                            \n  ---> 001066            MOVE MONTH-ITEM(SUB-4)     TO X-AXIS-YTD.              \n  ---> 001067            MOVE TOKEN-ITEM            TO X-AXIS-R(SUB-4).         \n  ---> 001068            ADD  MONTHLY-AMOUNT(SUB-4) TO YTD.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7d8499a59d8c-1", "text": "---> 001069            MOVE YTD                   TO TOTAL-GROSS.             \n  ---> 001070        POPULATE-GRAPH-EX.                                         \n  ---> 001071            EXIT.                                                  \n  ---> 001072        DEMONSTRATE-CONDITIONAL-BKPT.                              \n  ---> 001073            CALL 'ISPLINK' USING DSPLY,                           \nSuppose you want to trace the execution path of the program prior to this point. You can have the application scroll back\nand display a previously executed statement using the PREV command. The PREV command lets you view previously\nexecuted statements, but does not cause any statements to execute. After you scroll back using the PREV command, you\ncan scroll forward and retrace execution using the ADVANCE command. You may specify a number from 1 to 999 with the\nPREV and ADVANCE commands to scroll more than one statement at a time.\nThe PREV and ADVANCE commands do not change the statement where CAMRCOB2 resumes execution. The PREV\nand ADVANCE only scroll the statements in the trace.\nType PREV 9 in the Command field and press Enter.\nThe application displays the ninth previous statement executed.\nThe following screen shows the ninth previous statement:\nCAMRCOB2 ---------- CA InterTest Batch UNCOND BEFORE Intercept --------------- \n COMMAND ===>                                                  SCROLL ===> CUR \n TRACE=> 001055 001158 001157 001156 001155 001153 001147 001146 001139 001137 \n       001136                                                                   \n  0001 001137        DEMONSTRATE-PREV-COMMAND.                                  \n       001138       *                                                           \n  0001 001139            CALL 'ISPLINK' USING DSPLY,                            \n       001140                                 COBDPN75.                         \n       001141       * -----------------------------------------------*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7d8499a59d8c-2", "text": "001141       * -----------------------------------------------*          \n       001142       * This section of the Demo shows you             *          \n 590", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7206198d8a22-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n       001143       * the benefits of using the Prev                 *          \n       001144       * and Advance commands.. ..                      *          \n       001145       * -----------------------------------------------*          \n  0001 001146            MOVE  4        TO    COBDPN71-LENGTHS.                 \n  0001 001147            CALL 'ISPLINK' USING VCOPY,                            \n       001148                                 VCOPY-COBDPN71,                   \n       001149                                 VCOPY-COBDPN71-LENGTHS,           \n       001150                                 VCOPY-COBDPN71-VALUES,            \n       001151                                 VCOPY-MOVE.                       \n       001152       *                                                           \n  0001 001153            IF VCOPY-COBDPN71-EIBAID = 'PF03' OR 'PF15'            \n  ---> 001154               GO TO OPTIONS.                                      \n  0001 001155            MOVE SPACES  TO X-AXIS.                               \nNow you can retrace the execution of the nine statements using the ADVANCE command. The short form of the\nADVANCE command is A or AD. (You must enter the A on the command line.)\nType the A command and press Enter.\nThe application highlights the next statement executed.\nRepeat the Advance step a few more times.\nThe following screen shows advancing through the program trace:\nCAMRCOB2 ---------- CA InterTest Batch UNCOND BEFORE Intercept --------------- \n COMMAND ===>                                                  SCROLL ===> CUR \n TRACE=> 001055 001158 001157 001156 001155 001153 001147 001146 001139 001137 \n       001136                                                                   \n  0001 001137        DEMONSTRATE-PREV-COMMAND.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7206198d8a22-1", "text": "0001 001137        DEMONSTRATE-PREV-COMMAND.                                  \n       001138       *                                                           \n  0001 001139            CALL 'ISPLINK' USING DSPLY,                            \n       001140                                 COBDPN75.                         \n       001141       * -----------------------------------------------*          \n       001142       * This section of the Demo shows you             *          \n       001143       * the benefits of using the Prev                 *          \n       001144       * and Advance commands.. ..                      *          \n       001145       * -----------------------------------------------*          \n  0001 001146            MOVE  4        TO    COBDPN71-LENGTHS.                 \n  0001 001147            CALL 'ISPLINK' USING VCOPY,                            \n       001148                                 VCOPY-COBDPN71,                   \n       001149                                 VCOPY-COBDPN71-LENGTHS,           \n       001150                                 VCOPY-COBDPN71-VALUES,            \n       001151                                 VCOPY-MOVE.                       \n       001152       *                                                           \n  0001 001153            IF VCOPY-COBDPN71-EIBAID = 'PF03' OR 'PF15'            \n  ---> 001154               GO TO OPTIONS.                                      \n  0001 001155            MOVE SPACES  TO X-AXIS.                                \nYou can follow the execution order of the program by following the highlighted lines as you advance through the program\ntrace. In effect, using PREV and ADVANCE gives you a simulated instant replay of program execution.\nReturn to the Current Statement\nNow you can return to the current statement, that is, the statement where execution was halted prior to the unconditional\nbreakpoint.\n 591", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "89d9f1ac1799-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFollow these steps:\n1.Type the CS command and Press Enter.\nThe application displays the original Breakpoint Intercept panel that is shown in the beginning of this option.\n2.Type the GO command and press Enter.\nCAMRCOB2 resumes execution and displays the Advanced Options Demo Screen. You can continue with any option\nor exit.\nThis concludes Option 5: Trace Program Execution. Select another option and continue with the appropriate section, or\npress PF3 to end the demo.\nOption 6 Work with Indexed Table Items\nThis section of the demo session shows you a fast and easy way to inspect and modify the contents of indexed data\nitems. This section also demonstrates how to use the STEP command to single-step execution.\nNOTE\nBefore you proceed, completed the steps that are outlined in Advanced Demo Preliminaries, and have the Demo\nSession Options Menu that is displayed on your screen.\nFollow these steps:\n1.Select Option 6 and press Enter.\nCAMRCOB2 displays a screen that describes what occurs in this part of the demo session.\n2.Press Enter.CAMRCOB2 resumes execution.\nThe next screen that you see is an Abend Intercept panel. The application has automatically halted CAMRCOB2 because\nit detected a data exception in the highlighted ADD instruction.\nThe following screen shows the CAMRCOB2 at an S0C7 Abend Intercept:\nCAMRCOB2 ---------- CA InterTest Batch ABEND S0C7 Intercept ------------------ \n COMMAND ===>                                                  SCROLL ===> CUR \n TRACE=> 001184 001183 001182 001181 001196 001195 001193 001192 001196 001195 \n  0001 001183            SET C1 TO 5.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "89d9f1ac1799-1", "text": "0001 001183            SET C1 TO 5.                                           \n  0001 001184            ADD +1 TO DISTRICT ( A1, B1, C1 ).                     \n  ---> 001185            MOVE SPACES TO TASK-TEXT OF TASK-STRUCTURE.            \n       001186       * -----------------------------------------------*          \n       001187       * This section of the Demo shows you how to      *          \n       001188       * inspect and change the value of subscripted    *          \n       001189       * table items.. ..                               *          \n       001190       * -----------------------------------------------*          \n  ---> 001191            GO TO OPTIONS.                                         \n       PP 5655-G53 IBM Enterprise COBOL for z/OS and OS/390 3.1.0     CAMRCOB2  \n       LineID ----+-*A-1-B--+----2----+----3----+----4----+----5----+----6----+\n  0018 001192        INITIALIZE-TABLE.                                          \n  0018 001193            MOVE SUB-1 TO STATE-NUMBER (SUB-1),                    \n       001194                          COUNTY-NUM1 (SUB-1, SUB-2).              \n  0018 001195            MOVE ','   TO COUNTY-COMM (SUB-1, SUB-2).              \n  0018 001196            MOVE SUB-2 TO COUNTY-NUM2 (SUB-1, SUB-2).              \n  ---> 001197        SET-VAR-REC.                                               \n  ---> 001198            MOVE +100 TO VAR-REC-LEN.                              \n  ---> 001199            MOVE ZERO TO VAR-SS.                                   \n  ---> 001200        PROCESS-VAR.                                              \n 592", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4f572c665cc8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIf you recall, this type of error was detected and corrected in the basic demo session. To continue execution, find the data\nitem causing the S0C7 ABEND and dynamically modify it.\nLooking at the highlighted breakpoint statement, you might suspect the variable is at fault; it probably was not initialized\ncorrectly. The variable in this case is an indexed table entry.\nDisplay an Indexed Table Entry\nTo quickly inspect the value of the DISTRICT ( A1, B1, C1 ) field directly from this screen, type K to the left of the\nhighlighted statement.\nTab to the highlighted ADD instruction, type K (for keep) and press Enter.\nThe application displays the current value of DISTRICT. Because the k line command requests a display of each item on\nthat line, the value of each subscripted index item is also displayed.\nThe following panel shows displaying a keep window for the Table Entry:\nCAMRCOB2 ---------- CA InterTest Batch ABEND S0C7 Intercept ------------------ \n COMMAND ===>                                                  SCROLL ===> CUR \n TRACE=> 001184 001183 001182 001181 001196 001195 001193 001192 001196 001195 \n       ------------------------------------------------------------------------\n       1F08E5BE NP-S  000856 07 DISTRICT                     ?000.             \n                                   A1  (+1)                                    \n                                   B1  (+3)                                    \n                                   C1  (+5)                                    \n       ------------------------------------------------------------------------\n  0001 001183            SET C1 TO 5.                                           \n  0001 001184            ADD +1 TO DISTRICT ( A1, B1, C1 ).                     \n  ---> 001185            MOVE SPACES TO TASK-TEXT OF TASK-STRUCTURE.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4f572c665cc8-1", "text": "---> 001185            MOVE SPACES TO TASK-TEXT OF TASK-STRUCTURE.            \n       001186       * -----------------------------------------------*          \n       001187       * This section of the Demo shows you how to      *          \n       001188       * inspect and change the value of subscripted    *          \n       001189       * table items.. ..                               *          \n       001190       * -----------------------------------------------*          \n  ---> 001191            GO TO OPTIONS.                                         \n       PP 5655-G53 IBM Enterprise COBOL for z/OS and OS/390 3.1.0     CAMRCOB2  \n       LineID ----+-*A-1-B--+----2----+----3----+----4----+----5----+----6----+\n  0018 001192        INITIALIZE-TABLE.                                          \n  0018 001193            MOVE SUB-1 TO STATE-NUMBER (SUB-1),                   \nThe question mark that precedes the value of DISTRICT in the keep window tells us this field does not contain a valid\nvalue. This error triggered the automatic breakpoint.\nThe keep window also tells us which table entry is at fault. The values of each index item in this window indicate that the\ninvalid data occurs at element (1, 3, 5).\nDynamically Correct an Uninitialized Table Item\nTo dynamically correct this error, modify main storage so the field contains valid data. You can use the SET command to\nset the value to zero. The application sets the variable using the proper format.\nType the following command: set district (a1,b1,c1) = zero\nPress Enter.\nThe following panel shows correcting the uninitialized Table Item:\n 593", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d2dbaee57d84-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAMRCOB2 ---------- CA InterTest Batch ABEND S0C7 Intercept ------------------ \n COMMAND ===> set district (a1,b1,c1) = zero                   SCROLL ===> CUR \n TRACE=> 001184 001183 001182 001181 001196 001195 001193 001192 001196 001195 \n       ------------------------------------------------------------------------\n       1F08E5BE NP-S  000856 07 DISTRICT                     ?000.             \n                                   A1  (+1)                                    \n                                   B1  (+3)                                    \n                                   C1  (+5)                                    \n       ------------------------------------------------------------------------\n  0001 001183            SET C1 TO 5.                                           \n  0001 001184            ADD +1 TO DISTRICT ( A1, B1, C1 ).                     \n  ---> 001185            MOVE SPACES TO TASK-TEXT OF TASK-STRUCTURE.            \n       001186       * -----------------------------------------------*          \n       001187       * This section of the Demo shows you how to      *          \n       001188       * inspect and change the value of subscripted    *          \n       001189       * table items.. ..                               *          \n       001190       * -----------------------------------------------*          \n  ---> 001191            GO TO OPTIONS.                                         \n       PP 5655-G53 IBM Enterprise COBOL for z/OS and OS/390 3.1.0     CAMRCOB2  \n       LineID ----+-*A-1-B--+----2----+----3----+----4----+----5----+----6----+\n  0018 001192        INITIALIZE-TABLE.                                          \n  0018 001193            MOVE SUB-1 TO STATE-NUMBER (SUB-1),", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d2dbaee57d84-1", "text": "The application dynamically modifies the value in main storage for DISTRICT ( A1, B1, C1 ), and displays the new value in\nthe keep window. The message on the top right of the panel reads: SET COMPLETE .\nSingle-Step Execution\nUse the step command to execute just one line of code. The step command lets you determine how many lines are\nexecuted when you use the go command. For example, to execute one line at a time, or single-step, use the command:\nstep 1.\nType the STEP1 command and press Enter.\nThe application sets the step count to one and displays the following message: STEP COUNT SET.\nThe following panel shows setting the step count:\nCAMRCOB2 ---------- CA InterTest Batch ABEND S0C7 Intercept ---- STEP COUNT SET\n COMMAND ===>                                                  SCROLL ===> CUR \n TRACE=> 001184 001183 001182 001181 001196 001195 001193 001192 001196 001195 \n       ------------------------------------------------------------------------\n       1F08E5BE NP-S  000856 07 DISTRICT                     +000.             \n                                   A1  (+1)                                    \n                                   B1  (+3)                                    \n                                   C1  (+5)                                    \n       ------------------------------------------------------------------------\n  0001 001183            SET C1 TO 5.                                           \n  0001 001184            ADD +1 TO DISTRICT ( A1, B1, C1 ).                     \n  ---> 001185            MOVE SPACES TO TASK-TEXT OF TASK-STRUCTURE.            \n       001186       * -----------------------------------------------*          \n       001187       * This section of the Demo shows you how to      *          \n       001188       * inspect and change the value of subscripted    *          \n       001189       * table items.. ..                               *", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d2dbaee57d84-2", "text": "001189       * table items.. ..                               *          \n       001190       * -----------------------------------------------*          \n 594", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ef59ba973545-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  ---> 001191            GO TO OPTIONS.                                         \n       PP 5655-G53 IBM Enterprise COBOL for z/OS and OS/390 3.1.0     CAMRCOB2  \n       LineID ----+-*A-1-B--+----2----+----3----+----4----+----5----+----6----+\n  0018 001192        INITIALIZE-TABLE.                                          \n  0018 001193            MOVE SUB-1 TO STATE-NUMBER (SUB-1),                   \nExecute CAMRCOB2 by entering the command: GO and pressing Enter. The ADD statement is executed, and then the\napplication halts execution and displays a Step Count Intercept panel. The line below the ADD statement is now the\ncurrent line, and is highlighted.\nRemove the Step Count and Keep Window\nWhen you want to end single-stepping, reset the step count to zero. This action turns off single stepping. Remove the step\ncount and keep window before continuing execution.\nType the following command: step 0; remove all\nPress Enter.\nThe application resets the step count and removes the keep window.\nTo display the status of the step count, enter the step command without any count number.\nFollow these steps:\n1.Type the STEP command and press Enter.\nThe application displays the value of the step count in the top-right corner; in this case, the message is: NO STEP\nCOUNT SET.\n2.Resume execution of CAMRCOB2 by entering GO.CAMRCOB2 resumes execution, and you return to the Options\nMenu.\nThis concludes Option 6: Work with Indexed Table Items. Select another option and continue with the appropriate section,\nor press PF3 to end the demo.\nOption 7 Histogram Report", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ef59ba973545-1", "text": "or press PF3 to end the demo.\nOption 7 Histogram Report\nThis option illustrates how to create and view the Histogram Report of Statement Execution. The option is useful in\nidentifying dead code.\nNOTE\nBefore you proceed, completed the steps that are outlined in Advanced Demo Preliminary, and have the Demo\nSession Options Menu displayed on your screen.\nFollow these steps:\n1.Type Option 7 and press Enter.\nCAMRCOB2 displays the screen that describes what occurs in this part of the demo session.\n2.Press Enter. The application halts CAMRCOB2 at an unconditional breakpoint set at the program exit. The PGM Exit\nIntercept panel displays in the following panel.\nThe following screen shows the Program Exit Breakthrough Intercept panel:\nCAMRCOB2 ---------- CA InterTest Batch PGM EXIT Intercept -------------------- \n COMMAND ===>                                                  SCROLL ===> CSR \n TRACE=> 000975 000974 000973 001277 001310 001309 001308 001318 001317 001316 \n  0001 000974            CLOSE REPORT-OUT.                                      \n  ---> 000975            GOBACK.                                                \n       000976                                                                   \n       000977       * -----------------------------------------------*          \n 595", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1db704c0dc45-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n       000978       * The \" UNCOND ALL EXIT \" ( or \" AT ALL EXIT \" ) *          \n       000979       * command will cause an Unconditional Breakpoint *          \n       000980       * at a program's exit point.. ..                 *          \n       000981       * -----------------------------------------------*          \n       000982                                                                   \n  0001 000983        OPTIONS-MENU.                                              \n       000984       * -----------------------------------------------*          \n       000985       * Initialise the lengths in case of recursion .. *          \n       000986       * -----------------------------------------------*          \n  0001 000987            CALL 'ISPLINK' USING DSPLY,                            \n       000988                                 COBDPN70.                         \n       000989                                                                   \n  0001 000990            MOVE 4         TO OPTION-OPTAID.                       \n  0001 000991            CALL 'ISPLINK' USING VCOPY,                            \n       000992                                 VCOPY-OPTION-LIST,                \n       000993                                 VCOPY-OPTION-LENGTHS,             \nThis type of unconditional breakpoint is set with the command: UNCOND ALL EXIT or AT ALL EXIT. Prior to exiting the\nprogram, you can request a Histogram Report using the HIST command.\nType the HIST command and press Enter.\nThe application returns the following message:\n'HISTOGRAM SUCCESSFULLY WRITTEN'\nView the Histogram Report\nThe report is written to the data set associated with the ddname INT1REPT that you can view by splitting the screen.\nFollow these steps:\n1.ISPF users\nTab a few lines down your screen and press the SPLIT PF key that is defined in your ISPF profile (normally PF2).", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1db704c0dc45-1", "text": "The ISPF Main Menu displays in the split-screen area.\nRoscoe  users\nEnter the Roscoe  SPLIT sequence.\nA second Roscoe  panel displays.\n2.ISPF users\nSelect the ISPF Browse Facility and request a display of the data set associated with the ddname INT1REPT. You\nallocated this data set in the Advanced Demo Preliminaries. The suggested data set name was: userid.INT1REPT\nRoscoe  users\nUse Roscoe  Attach DSN command to display the data set member associated with the ddname INT1REPT. The\nsuggested data set name was: userid.INT1REPT.\nThe first page of the histogram report displays. A sample report is shown in the following panel.\nNOTE\nIn the following example, the data set name is: intbatch.histrept.\nThe following screen shows Browsing the Histogram Dataset Member:\nCAMRCOB2 ---------- CA InterTest Batch PGM EXIT- HISTOGRAM SUCCESSFULLY WRITTEN\n COMMAND ===>                                                  SCROLL ===> CUR \n TRACE=> 000975 000974 000973 001277 001310 001309 001308 001318 001317 001316 \n  0001 000974            CLOSE REPORT-OUT.                                      \n .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  \n 596", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1cbf9d13cc84-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n BROWSE -- USER99 _TSU04928 ------------------------- Line 00000000 Col 001 080 \n Command ===>                                                  Scroll ===> PAGE\n********************************* Top of Data **********************************\n1CA InterTest/Batch       Execution Histogram For Program-ID: CAMRCOB2     Date\n0                                                                               \n 000876 0001 |*                                                                 \n 000877 0001 |*                                                                 \n 000887 0001 |*                                                                 \n 000888 0001 |*                                                                 \n 000890 0001 |*                                                                 \n 000891 0001 |*                                                                 \n 000892 0001 |*                                                                 \n 000896 0002 |**                                                                \n 000897 0002 |**                                                                \n 000898 ---- |                                                                  \n 000900 0002 |**                                                                \n 000901 0002 |**                                                                \n 000902 0001 |*                                                                 \nPage down to the end of the report using the maximum command with PF8.\nType the M command and press PF8.\nThe last page of the Histogram Report displays, as shown in the following panel.\nThe following screen shows the last page of the Histogram Report:\nCAMRCOB2 ---------- CA InterTest Batch PGM EXIT- HISTOGRAM SUCCESSFULLY WRITTEN\n COMMAND ===>                                                  SCROLL ===> CUR \n TRACE=> 000975 000974 000973 001277 001310 001309 001308 001318 001317 001316 \n  0001 000974            CLOSE REPORT-OUT.                                      \n .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1cbf9d13cc84-1", "text": "BROWSE -- USER99 _TSU04928 ------------------------- Line 00000246 Col 001 080 \n Command ===>                                                  Scroll ===> PAGE\n 001310 0017 |*****************                                                 \n 001311 ---- |                                                                  \n 001312 ---- |                                                                  \n 001313 ---- |                                                                  \n 001314 0034 |**********************************                                \n 001315 0034 |**********************************                                \n 001316 0034 |**********************************                                \n 001317 0034 |**********************************                                \n 001318 0034 |**********************************                                \n              ----+----|----+----|----+----|----+----|----+----|----+----|----+\n0            *NOTE* ASTERISKS REPRESENT A SCALE OF 00000001 EXECUTION(S) PER AS\n1CA InterTest/Batch       Execution Histogram For Program-ID: CAMRCOB2     Date\n-Session Number: 1,175For Userid USER99                                         \n-Number of executable statements: 236                                           \n0Number of statements executed during this test: 116                            \n0Percentage of statements executed during this test: 49                        \nIn the previous panel, you can see that some lines were never executed. Check to see if these lines in the program are\ndead code and should be removed.\n 597", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "396b5e28ae63-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nIn our example, the unexecuted code starts at line 1311. Note the corresponding line number in your program\nthat is unexecuted.\nISPF users\nRemove your split-screen using the command: X\nRoscoe  users\nUse the Roscoe  END key to end the second session.\nYou return to a full-screen display of the Program Exit Intercept shown in the beginning of this option.\nUse the Find Statement (FS) command to display the code that was never executed.\nType the FS1311 command and press Enter.\nThe application displays the requested line of code.\nThe following screen displays the unexecuted code:\nCAMRCOB2 ---------- CA InterTest Batch PGM EXIT Intercept -------------------- \n COMMAND ===>                                                  SCROLL ===> CUR \n TRACE=> 000975 000974 000973 001277 001310 001309 001308 001318 001317 001316 \n  ---> 001311        990-INITIALISE.\n  ---> 001312            MOVE SPACES TO DM-TEXT.                                \n  ---> 001313            MOVE ZEROES TO DM-RC.                                  \n  0034 001314        990-INCREMENT.                                             \n       PP 5655-G53 IBM Enterprise COBOL for z/OS and OS/390 3.1.0     CAMRCOB2  \n       LineID ----+-*A-1-B--+----2----+----3----+----4----+----5----+----6----+\n  0034 001315            IF  TABLE-SUB LESS THAN 50                             \n  0034 001316                ADD 1 TO TABLE-SUB.                                \n  0034 001317        990-INCREMENT-EX.                                          \n  0034 001318            EXIT.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "396b5e28ae63-1", "text": "0034 001318            EXIT.                                                  \n       PP 5655-G53 IBM Enterprise COBOL for z/OS and OS/390 3.1.0     CAMRCOB2  \n       An \"M\" preceding a data-name reference indicates that the data-name is mo\n                                                                                \n        DEFINED   CROSS-REFERENCE OF DATA NAMES   REFERENCES                    \n                                                                                \n       000021      ASA-CNTL                                                     \n       000849      A1                              M1181 1184                   \n       000646      BALANCE-LINE                    M1299                        \n       000640      BALANCE-OUT                                                  \n       000638      BALANCE-REPORT                  M1298                        \nBy reviewing the code, you determine whether it is required. In this case, it is not required for the program and should be\nremoved.\nTo remove the code in your programs, you can split the screen again and make the code changes. You can also wait until\nyou complete the review of the histogram report.\nNow return to the current statement in the CAMRCOB2 program.\nFollow these steps:\n1.Type the CS command and press Enter.\nThe application displays the Program Exit Intercept panel.\n2.To continue the advanced demo, enter the command go options and press Enter. To end the demo, enter the\ncommand GO.\n 598", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f2c1d09011ec-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIf you are continuing the demo, CAMRCOB2 program execution continues with the display of the Advanced Options\nMenu. Choose another option from the menu.\nIf you are exiting the demo, CAMRCOB2 resumes execution at the normal program exit and terminates. You return to\nthe Execution Control panel of the Foreground Option. Your previous entries are displayed, letting you begin testing\nagain, or exit. Use PF3 to exit.\nNOTE\nBefore you proceed, completed the steps that are outlined in Advanced Demo Preliminaries, and have the Demo\nSession Options Menu that is displayed on your screen.\nAdvanced Demo Session for Assembler\nThis article illustrates an Assembler advanced demo session using CAMRASM.\nBefore you proceed, completed the steps outlined in Advanced Demo Preliminaries, and have the Initial Intercept for\nCAMRASM displayed on your screen.\nNOTE\nCAMRASM is an ISPF application.\nInclude Unconditional Breakpoints\nNow you are going to set unconditional breakpoints at a number of procedure names in the demo program. In the basic\ndemo you set an unconditional breakpoint using the U or ) line command, which are both equivalent to the UNCOND\ncommand. However, a quicker way to include unconditional breakpoints for a test session is to place the breakpoint\ncommands in a data set member, and simply include that member when the Initial Intercept panel displays.\nThe ASMINCL data set member of CAI.CAVHSAMP contains the application commands that set the breakpoints required\nfor using the Advanced Options Demo for Assembler. Include this data set member as follows:\nType the following command at the *Initial* Intercept panel:\ninclude asmincl\nPress Enter.\nThe application processes the commands in the asmincl data set, and returns the following message in the upper-right\ncorner of the screen: BREAKPOINT SET.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f2c1d09011ec-1", "text": "corner of the screen: BREAKPOINT SET.\nCAMRASM  ---------- CA InterTest Batch *INITIAL* Intercept ----- BREAKPOINT SET\nCOMMAND ===>                                                  SCROLL ===> CUR \nTRACE=> 000005                                                                 \n                       R:D  00000           4          USING LDATA,R13         \n *--> 000000 47F0 F074            00074     5          B     START-CAMRASM(,R15\n                                            6 *-------------------------------*\n                                            7 * Welcome to the CA InterTest   *\n                                            8 * Batch Assembler demonstration *\n                                            9 * program. You are now at the   *\n                                           10 * Initial Breakpoint panel,     *\n                                           11 * which is displayed upon entry *\n                                           12 * to the first program to be    *\n                                           13 * tested. At this point, other  *\n                                           14 * breakpoints can be set and    *\n                                           15 * control commands can be       *\n                                           16 * issued before the program is  *\n                                           17 * executed.                     *\n 599", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "61a06db54cb8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                           18 *-------------------------------*\n *--> 000004 C3C1D4D9C1E2D440              19          DC    CL8'CAMRASM'      \n *-->                                      20          DC    CL9'&SYSDATE'     \n      00000C F0F561F1F661F0F3                +         DC    CL9'05/16/03'     \n *-->                                      21          DC    CL6'&SYSTIME'     \n      000015 F1F74BF5F340                    +         DC    CL6'17.53'        \n *--> 00001B C1C4E5C1D5E3C1C7              22          DC    C'CA INT\nAccess the Demo Session Options Menu\nAfter setting the required breakpoints, access the Demo Session Options Menu by executing the demo program and\nchoosing the Advanced Options Menu from the Welcome panel.\nFollow these steps:\n1.From the Initial Intercept panel, type GO and press Enter to execute the program.The demo program begins execution\nand displays the Welcome panel.\n2.Press PF2 to access the Options Menu for the Advanced Demo Session.The Advanced Options Preliminary Screen is\ndisplayed, reminding you not to access the Options Menu without including the data set member ASMINCL.\n3.Press Enter to continue.The Demo Session Options Menu displays.\nEach of the Options on the menu is independent and can be performed in any order. To use an Option, follow the\nappropriate section. Upon completing an Option, you return to the Menu.\nBefore you start, you should know that:\n\u2022To interrupt a loop-press the ATTN or PA1 key. Try the ATTN key first. If that does not interrupt the loop, your testing", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "61a06db54cb8-1", "text": "environment requires you to use the PA1 key. If using PA1, you may need to press RESET first.\nExit the Advanced Options Demo\nYou can exit the demo from the Options Menu at any time.\nFollow these steps:\n1.Press PF3.The End Demo Session screen displays.\n2.Press Enter.The InterTest Batch Program Breakpoint Intercept panel displays for an unconditional breakpoint at label\nGOBACK. (This breakpoint was set by a command in the ASMINCL include file.)\n3.Type GO and press Enter to execute the program.The demo program ends, and the InterTest Batch Entry panel\ndisplays.\nReturn to the Advanced Options Demo Session\nIf you exit the InterTest Batch Demo, you can return at any time to perform another advanced option. Just repeat the\npreliminary steps in Access the Demo Session Options Menu. Remember to enter the following command at the Initial\nBreakpoint screen:\n include asmincl \nOption 1 Time-Controlled Execution\nThis option illustrates how you can slow the execution of your program. The InterTest Batch SLOW command executes\none statement in your program every few seconds. The exact time interval is specified when you issue the SLOW\ncommand. Using the SLOW command together with a keep window is an especially effective testing technique; it allows\nyou to halt the program whenever you see a problem, without having to determine the breakpoint in advance.\n 600", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fb47df528fb6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nBefore proceeding, be sure you have completed the steps outlined in Advanced Demo Preliminaries, and you\nhave the InterTest Batch Demo Session Options Menu displayed on your screen.\nThis option requires you to interrupt the program by pressing the ATTENTION key or the PA1 key. Before proceeding,\nlocate each of these keys on your keyboard. If you need help in finding them, ask a technical support person before you\nbegin.\nFollow these steps:\n1.Type Option 1 and press Enter.\nCAMRASM displays the screen that describes what occurs in this part of the demo session.\n2.Press  Enter.InterTest Batch halts CAMRASM at an unconditional breakpoint set at label PAY_CALC. The statement is\nhighlighted.\nOpen a keep window that displays the values of YTD and X_AXIS_YTD by entering the commands specified below.\nNotice how you can use the short form of the keep command K and use the TSO command delimiter (normally a semi-\ncolon) to string multiple commands on a single command line.\nType the following command: k ytd; k x_axis_ytd\nInterTest Batch displays a keep window showing the current values of YTD and X_AXIS_YTD.\nA sample screen showing the keep window for YTD and X_AXIS_YTD follows:\nCAMRASM  ---------- CA InterTest Batch UNCOND BEFORE Intercept --------------- COMMAND ===>                   \n                               SCROLL ===> CUR \nTRACE=> 000440 000438 000437 000436 000435 000434 000432 000431 000430 000429 0\n      -------------------------------------------------------------------------\n      0014CE9C AN    001325 02 YTD                          000000000         \n      0014CE7F AN    001319 02 X_AXIS_YTD                                     \n      -------------------------------------------------------------------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fb47df528fb6-1", "text": "-------------------------------------------------------------------------\n 0001 000414 D208 D66B C9BE 0066B 009BE   438          MVC   TOTALGROSS,ZEROS  \nU---> 00041A                              440 PAY_CALC DS    0H                \n ---> 00041A 1F00                         441          SLR   R0,R0             \n ---> 00041C 4000 D102            00102   442          STH   R0,SUB_4          \n ---> 000420                              444 PAY_CALC_LOOP DS 0H              \n ---> 000420 45E0 C440            00440   445          BAL   R14,POPULATE_GRAPH\n ---> 000424 4810 D102            00102   447          LH    R1,SUB_4          \n ---> 000428 4110 1001            00001   448          LA    R1,1(,R1)         \n ---> 00042C 4010 D102            00102   449          STH   R1,SUB_4          \n ---> 000430 4910 C9CE            009CE   451          CH    R1,NO_OF_HOURS    \n ---> 000434 4740 C420            00420   452          BL    PAY_CALC_LOOP     \n ---> 000438 45E0 C7EC            007EC   454          BAL   R14,UPDATE_CHEQUE \n ---> 00043C 47F0 C316            00316   456          B     OPTIONS           \n ---> 000440                              458 POPULATE_GRAPH DS 0H             \n ---> 000440 4820 D102            00102   459          LH    R2,SUB_4", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fb47df528fb6-2", "text": "---> 000444 4C20 CDF4            00DF4   460          MH    R2,=Y(L'MONTH_ITEM \nIssue the SLOW command to execute one statement every two seconds. As the program resumes execution, you\nare able to see the changing values of YTD and X_AXIS_YTD. In this demo, you are going to halt execution when the\nX_AXIS_YTD value is MAR by pressing the ATTENTION key.\nFollow these steps:\n1.Type the SLOW 2 command and press Enter.\nInterTest Batch initiates a time-controlled execution of CAMRASM, at a rate of one statement every two seconds.\n 601", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3182a64336ac-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n2.When the value of X_AXIS_YTD in the keep window is MAR, press the ATTN or PA1 key. Try the ATTN key first.The\napplication displays the Attention Intercept panel, as shown in the following panel.\nA sample Attention Intercept panel follows:\nCAMRASM  ---------- CA InterTest Batch ATTENTION Intercept -------------------  \nCOMMAND ===>                                                  SCROLL ===> CSR \nTRACE=> 000474 000473 000470 000468 000467 000466 000463 000461 000460 000459 0\n      -------------------------------------------------------------------------\n      0013EE9C AN    001323 02 YTD                          017539242         \n      0013EE7F AN    001317 02 X_AXIS_YTD                   Mar               \n      -------------------------------------------------------------------------\n                       R:2  00000         462          USING MONTH,R2          \n 0004 00044C D202 D657 2000 00657 00000   463          MVC   X_AXIS_YTD,MONTH_I\n                                          464          DROP  R2                \n 0003 000452 4820 D102            00102   466          LH    R2,SUB_4          \n               OPTIONS MENU PROCESSING                                         \n        Active Usings: CAMRASM(X'1000'),R12  LDATA(X'1000'),R13                \n        Loc  Object Code    Addr1 Addr2  Stmt   Source Statement               \n 0003 000456 4C20 CDF6            00DF6   467          MH    R2,=Y(L'X_AXIS_ITE\n 0003 00045A 4122 D65B            0065B   468          LA    R2,X_AXIS_LINE(R2)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3182a64336ac-1", "text": "R:2  00000         469          USING XAXIS,R2          \n 0003 00045E D201 2000 CA84 00000 00A84   470          MVC   X_AXIS_ITEM,TOKEN_\n                                          471          DROP  R2                \n 0003 000464 4820 D102            00102   473          LH    R2,SUB_4          \n 0003 000468 4C20 CDF8            00DF8   474          MH    R2,=Y(L'MONTHLY_AM\n 0003 00046C 4122 CAAC            00AAC   475          LA    R2,MONTHLY_THIS(R2\n                       R:2  00000         476          USING MGROSS,R2 \nReview what you just did.\n\u2022You opened a keep window for two variables whose values you wished to view and compare.\n\u2022You used the command slow 2 to have the application slowly execute the program. However, during the program\nexecution, you could monitor the values of the variables in the keep window.\n\u2022You used the ATTENTION or PA1 key to stop program execution, and the Attention Intercept panel displayed.\nThis combination of using keep windows, the slow command, and an Attention Intercept allows you to carefully control\nand monitor your program execution, while tracking the values of specific variables.\nNOTE\nAttention Intercept panel is only displayed when you press the ATTN or PA1 key and then the application\nexecutes a statement in a program that is currently being monitored.\nRemove the Keep Window\nBefore returning to the Options Menu of the advanced demo, remove the keep window as follows:\nType the REMOVE ALL command and press Enter.\nThe application removes the keep window for YTD and X_AXIS_YTD on the Attention Intercept panel.\nContinue Execution", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3182a64336ac-2", "text": "Continue Execution\nType GO and press Enter to continue execution.CAMRASM resumes execution, and displays the Options Menu.\nThis concludes Option 1: Time Controlled Execution. Select another option and go to the appropriate section, or exit the\ndemo using PF3.\n 602", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7b7d6b726fb3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nOption 2 Set Conditional Breakpoints\nThis option shows you how to set and use conditional breakpoints.\nNOTE\nBefore proceeding, be sure you have completed the steps outlined in Advanced Demo Preliminaries and you\nhave the Demo Session Options Menu displayed on your screen.\nFollow these steps:\n1.Type Option 2 and press Enter.\nCAMRASM displays the screen that describes what occurs in this part of the demo session.\n2.Press  Enter.The application halts CAMRASM at an unconditional breakpoint. The statement at the breakpoint is\nhighlighted.\nAccess the screen used to set conditional breakpoints. From this screen, you can set both the conditions and any\ncommands you want executed when the specified condition is met.\nFollow these steps:\n1.Type the COND command in the Command field and press Enter.\nThe application displays the When panel. WHEN is a synonym for COND.\n2.Make the following entries on the When panel and press Enter.\n----------------------- CA InterTest Batch WHEN PANEL -------------------------\nOPTION ===>S\n   S - SET A WHEN CONDITION                                                 \n   R - RESET A WHEN CONDITION                                               \n   L - OR BLANK, LIST THE WHEN CONDITIONS                                   \n                                                                            \nSPECIFY DATA AREA NAME(S) AND COMPARISON CONDITION:      \n   WHEN-NAME    ===> ytdcond                                                \n   DATA-AREA-1  ===> subtotal                                               \n   OPERATOR     ===> ge        (EQ, NE, LT, GT, LE, GE, =, <>, <, >, <=, >=)\n   DATA-AREA-2  ===> 000060000                                              \n   AFTER        ===> N         (Y/N)                                        \n                                                                            \nCOMMANDS TO BE EXECUTED AT WHEN CONDITION:                                  \n===>  k subtotal; set totalgross = 000200000; k totalgross", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7b7d6b726fb3-1", "text": "===>  k subtotal; set totalgross = 000200000; k totalgross \nThe application displays the following message in the top right corner of the When panel: WHEN CONDITION SET.\n3.Press PF3 to exit the When panel.The application brings you to the Intercept panel.\n4.Continue execution by typing GO and pressing Enter.CAMRASM resumes execution until the condition you set for\nthe YTDCOND breakpoint is met; when the value of SUBTOTAL is greater than or equal to 60000, the application\nhalts execution, and executes the commands you entered for the conditional breakpoint; it displays a keep window\nfor SUBTOTAL, sets TOTALGROSS to 200000, and then displays TOTALGROSS in the keep window. Your screen\nshould look like the Intercept panel in the following screen.\nA sample Intercept panel showing condition YTDCOND has been met follows:\nCAMRASM  ---------- CA InterTest Batch WHEN YTDCOND BEFORE Intercept ---------\n COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000545 000544 000543 000542 000541 000539 000538 000537 000536 000523\n       ------------------------------------------------------------------------\n       001428CE AN    001329 02 SUBTOTAL                     00009716H\n       001428B3 AN    001324 02 TOTALGROSS                   000200000\n 603", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fc75b96fedac-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n       ------------------------------------------------------------------------\n GR 0-7 00000000 00000002 1F1A0C90 1F1A0FA6 00142A1E FFEBD5E2 00000000 00000000\n    8-F 00000000 00000000 00000000 00000000 9F1A01C8 00142248 9F1A06A2 00000000\n       ------------------------------------------------------------------------\n  0003 00050E F384 D686 D058 00686 00058   543          UNPK  SUBTOTAL,LDWORK(5)\n  0003 000514 96F0 D68E      0068E         544          OI    SUBTOTAL+8,X'F0'\n  0002 000518 D208 D67D D686 0067D 00686   545          MVC   BILL_YTD,SUBTOTAL\n                                           546          DROP  R2\n  0002 00051E 07FE                         548          BR    R14\n  ---> 000520                              550 DEMONSTRATE_SPLIT_SCREEN DS 0H\n                                           551 *-------------------------------\n                                           552 * This section of the demo     \n                                           553 * shows you how to SPLIT the   \n                                           554 * screen ..                    \n                                           555 *-------------------------------\n  ---> 000520 58F0 D050            00050   556          L     R15,LDLINK@\n                                           557          CALL (15),(DSPLY,COBDPN\nNow remove the conditional breakpoint before continuing.\nFollow these steps:\n1.Return to the When panel by entering the WHEN command and pressing  Enter.\nThe When panel displays.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fc75b96fedac-1", "text": "The When panel displays.\n2.Type the following on the When panel and press Enter:\nOPTION: ===> r\nWHEN NAME ===> ytdcond\nThe application displays the following message in the top right corner of the When panel: WHEN DELETED.\n3.Press PF3 to exit the When panel.The application brings you to the previous Intercept panel.\nRemove the Keep Window and Continue Execution\nRemove the keep window before continuing execution.\nType the REMOVE ALL command and press Enter.\nThe keep window is removed.\nReturn to the Options Menu by continuing execution.\nType GO and press Enter.CAMRASM resumes execution and displays the Options Menu.\nThis concludes Option 2: Conditional Breakpoints. Select another option and go to the appropriate section, or exit the\ndemo using PF3.\nOption 3 Update Source Code\nThis option illustrates how you can use the ISPF or split-screen capability from any screen. One way to use this feature is\nto update your source code as soon as you find errors during your test session.\nNOTE\nBefore proceeding, be sure you have completed the steps outlined in Advanced Demo Preliminaries and you\nhave the Demo Session Options Menu displayed on your screen.\nFollow these steps:\n1.Type Option 3 and press Enter.\nCAMRASM displays the screen that describes what occurs in this part of the demo session.\n 604", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "962fa77839ff-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n2.Press Enter.The application halts CAMRASM at an unconditional breakpoint at the label SPLIT_SCREEN.\n3.Tab about halfway down your screen and press the SPLIT PF key defined in your ISPF profile (normally PF2).The\nISPF Primary Option Menu displays in the bottom half of your screen.\nUpdate Your Source Code\nIf you had found an error in your program code, you can use the ISPF menu to access and edit your source code before\ncontinuing with your test session.\nFor example, in the basic demo, the application stopped execution of the program because it detected an S0C7 ABEND.\nYou were able to continue execution by dynamically changing the value of Tasknum to zero. This was a one-time patch.\nTo correct the problem, you need to update your source code so that Tasknum is properly initialized. You can do this from\nany Intercept panel by splitting your screen to edit your source code.\nContinue Execution\nFollow these steps:\n1.Remove your ISPF split-screen using the command: =XYou return to a full-screen display of the unconditional\nbreakpoint shown in the previous panel.\n2.Type GO and press Enter to continue execution.You return to the Demo Options Menu.\nThis concludes Option 3: Update Source Code. Select another option and go to the appropriate section, or exit the demo\nusing PF3.\nOption 4 Interrupt a Looping Program\nThis option illustrates how to interrupt and verify that you have a looping program. It also illustrates the use of the skip\ncommand.\nNOTE\nBefore proceeding, be sure you have completed the steps outlined in Advanced Demo Preliminaries and you\nhave the Demo Session Options Menu displayed on your screen.\nThis option requires you to interrupt the program by pressing the ATTENTION key or the PA1 key. Before proceeding,", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "962fa77839ff-1", "text": "locate each of these keys on your keyboard. If you need help, ask a technical support person before you begin.\nFollow these steps:\n1.Type Option 4 and press Enter.\nCAMRASM displays the screen that describes what occurs in this part of the demo session.\n2.Press Enter.The application halts CAMRASM at an unconditional breakpoint set at ORDER_CALC.\nNOTE\nIf the Frequency Counter arrows and numbers are not displayed along the left side of your screen, turn the\nfrequency display on by entering the command: freq.\n3.Continue execution by typing GO and pressing enter.CAMRASM resumes execution. Notice the system light remains\non. There are additional breakpoints and screen panels in the demo program code, yet all you see is the system light.\nThis is symptomatic of a looping program. Halt the program to see what is going on.\n4.Press the ATTN or PA1 key. Try the ATTN key first. If that does not work, your testing environment requires you to use\nthe PA1 key. Press RESET before pressing the PA1 key to unlock the terminal keyboard.The Attention Intercept panel\ndisplays.\nContinue with the Continuing from the Attention Routine section.\n 605", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "53f4e6d5fc7a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nIf you do not successfully stop execution with the ATTN or PA1 key before 1024 executions of the demo\nprogram loop, you reach a safety net conditional breakpoint. If you reach this breakpoint, instructions for\ncontinuing are given in the next section.\nContinue from the \u201cSafety Net\u201d Conditional Breakpoint\nFollow this section only if you see the breakpoint in the following panel. If you do not, continue with the Continuing from\nthe Attention Routine section that follows.\nTo continue with the looping program demo, you must press the ATTN or PA1 key before 1024 executions of the loop this\ntime. To continue the program loop, use the following steps:\n1.Find label ORDER_CALC: fp order_calc\n2.Press Enter to go to the label.\n3.Type G to the left of the line:\nXC ORDER_SUB_TOTAL,ORDER_SUB_TOTAL\n4.Press Enter to continue the loop execution.\n5.Press the ATTN key or the RESET, then PA1 keys. Try the ATTN key first. If that does not work, your testing\nenvironment requires you to use the PA1 key.\nNOTE\nEven if PA1 stopped the slow execution in option 1, you may need to press ATTN to stop a loop.\nYou should see the Attention Intercept panel.\nTo return to the Options Menu:\n1.Enter the command: go options\n2.Press Enter.\nYou return to the Options Menu. You can try the same option again, even if you did not complete it the first time, or\nselect another option from the menu.\nContinue from the Attention Routine\nThe application now displays the Attention Intercept panel.\nCAMRASM keeps executing the TOTAL_ORDER routine. The current statement is highlighted.\nLook at the frequency counters to the left of the program statements. They show repeated execution of the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "53f4e6d5fc7a-1", "text": "Look at the frequency counters to the left of the program statements. They show repeated execution of the\nTOTAL_ORDER statements, indicating a loop. To investigate the logic in TOTAL_ORDER, you can set a keep window\nfor SUB_6 and then execute slowly using the SLOW command. This time you use the abbreviated form of the keep\ncommand: K.\nFollow these steps:\n1.Type the following command to set the keep window: k sub_6. Press Enter.\nThe application displays a keep window for the variable SUB_6.\nA sample screen showing the Keep Window to View SUB_6 follows:\nCAMRASM  ---------- CA InterTest Batch STEP BEFORE Intercept ----------------- \nOMMAND ===>                                                  SCROLL ===> CUR\nTRACE=> 000652 000651 000649 000648 000647 000646 000638 000637 000641 000640 0\n      -------------------------------------------------------------------------\n      0013F92E HX    001237 02 SUB_6                        0001             \n      -------------------------------------------------------------------------\n                       R:2  00000         650          USING ORDER,R2         \n 1131 0005CE F873 D058 2002 00058 00002   651          ZAP   LDWORK,UNIT_PRICE\n 606", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e1b731f4b607-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 1130 0005D4 FC73 D058 2006 00058 00006   652          MP    LDWORK,NO_OF_WIDGE\n 1130 0005DA D204 D0F3 D05B 000F3 0005B   653          MVC   ITEM_TOTAL,LDWORK+\n                                          654          DROP  R2               \n 1130 0005E0 4810 D106            00106   656          LH    R1,SUB_6         \n 1130 0005E4 4110 1001            00001   657          LA    R1,1(,R1)        \n 1130 0005E8 4010 D106            00106   658          STH   R1,SUB_6         \n 1130 0005EC 4810 D10C            0010C   660          LH    R1,LOOP_OUT      \n 1130 0005F0 4110 1001            00001   661          LA    R1,1(,R1)        \n 1130 0005F4 4010 D10C            0010C   662          STH   R1,LOOP_OUT      \n 1129 0005F8 D201 D106 C9CC 00106 009CC   664          MVC   SUB_6,ONE        \n 1129 0005FE 07FE                         666          BR    R14              \n                                                                              \n ---> 000600                              668 DEMONSTRATE_PREV_COMMAND DS 0H  \n                                          669 *-------------------------------*\n                                          670 * This section of the demo      *", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e1b731f4b607-1", "text": "669 *-------------------------------*\n                                          670 * This section of the demo      *\n2.Type the SLOW 2 command to execute one CAMRASM statement every two seconds and press Enter.\nCAMRASM continues a slow execution. As the code executes, you can see the code looping, and you can see the\ncorresponding value of SUB_6 in the keep window.\nNotice in the sample screen that SUB_6 changes from 1 to 2, but back to 1 again. SUB_6 is being reset to 1, and\ncausing the program to loop. The value of SUB_6 is causing the TOTAL_ORDER routine to continue to be executed.\n3.Halt execution again by pressing the ATTENTION or PA1 key. After the Attention Routine message displays, press\nEnter.\nThe application brings you to another Attention Intercept panel. The current statement is highlighted.\n4.To dynamically correct the loop-condition, you could use the SKIP command to bypass the offending statement. The s\nline command is another form of the SKIP command.\n5.Tab down to the statement: 'MVC SUB_6,ONE' and type S to the left of the line.The application skips the statement\nthat sets SUB_6 to 1, and executes the code as if the statement was removed.\n6.Back up to the first statement in the TOTAL_ORDER procedure, 'LH R2,SUB_6', and type G to the left of the line, to\ncontinue execution from that point.Press Enter.CAMRASM resumes execution from the line where you entered the g,\nand continues execution until it reaches the next unconditional breakpoint, as shown in the following panel.\nThe following sample screen shows an unconditional breakpoint at ORDER_CALC_EX:\nCAMRASM  ---------- CA InterTest Batch ATTENTION Intercept -------------------\nCOMMAND ===>                                                  SCROLL ===> CUR", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e1b731f4b607-2", "text": "COMMAND ===>                                                  SCROLL ===> CUR\nTRACE=> 000652 000651 000649 000648 000647 000646 000638 000637 000641 000640 0\n      -------------------------------------------------------------------------\n      0013F92E HX    001237 02 SUB_6                        0001             \n      -------------------------------------------------------------------------\n 1129 0005BA 4740 C5B0            005B0   641          BL    ORDER_CALC_LOOP  \nU---> 0005BE                              643 ORDER_CALC_EX DS 0H             \n ---> 0005BE 47F0 C316            00316   644          B OPTIONS              \n 1131 0005C2                              646 TOTAL_ORDER DS 0H               \n 1131 0005C2 4820 D106            00106   647          LH    R2,SUB_6         \n 1131 0005C6 4C20 CE00            00E00   648          MH    R2,=Y(ORDER_LEN) \n 1131 0005CA 4122 D6E4            006E4   649          LA    R2,CUSTOMER_ORDERS\n                       R:2  00000         650          USING ORDER,R2         \n 1131 0005CE F873 D058 2002 00058 00002   651          ZAP   LDWORK,UNIT_PRICE\n 1130 0005D4 FC73 D058 2006 00058 00006   652          MP    LDWORK,NO_OF_WIDGE\n 1130 0005DA D204 D0F3 D05B 000F3 0005B   653          MVC   ITEM_TOTAL,LDWORK+\n                                          654          DROP  R2", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e1b731f4b607-3", "text": "654          DROP  R2               \n 1130 0005E0 4810 D106            00106   656          LH    R1,SUB_6         \n 607", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "272d1ce1403a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 1130 0005E4 4110 1001            00001   657          LA    R1,1(,R1)        \n 1130 0005E8 4010 D106            00106   658          STH   R1,SUB_6         \n 1130 0005EC 4810 D10C            0010C   660          LH    R1,LOOP_OUT      \n 1130 0005F0 4110 1001            00001   661          LA    R1,1(,R1)        \nCAMRASM finally exited out of the loop that executed the TOTAL_ORDER routine and then continued until it reached the\nunconditional breakpoint set at ORDER_CALC_EX (one of the unconditional breakpoints included in the data set member\nasmincl).\nYou can see from the keep window that the value of SUB_6 is 5. This is the proper value to permit the exit of the\nORDER_CALC routine. Thus, the use of the skip command allowed us to dynamically fix the program code that caused\nthe loop, and continue execution.\nRemove the Keep Window and Skip Command\nBefore going back to the options menu, remove the keep window and skip command.\nFollow these steps:\n1.Type the REMOVE ALL command. Tab down to the 'MVC SUB_6,ONE' statement in the TOTAL_ORDER routine and\ntype over the S to the left of the statement with X. Press  Enter.\nThe keep window is removed, and the skip line command is removed.\n2.Continue execution by  typing GO and pressing Enter.CAMRASM resumes execution and displays the Demo Session\nOptions Menu.\nThis concludes Option 4: Interrupt a Program Loop. Select another option and go to the appropriate section, or exit the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "272d1ce1403a-1", "text": "demo using PF3.\nOption 5 Trace Program Execution\nThis option illustrates the use of the PREVIOUS and ADVANCE commands to help you trace program execution.\nNOTE\nBefore proceeding, be sure you have completed the steps outlined in Advanced Demo Preliminaries and you\nhave the Demo Session Options Menu displayed on your screen.\nFollow these steps:\n1.Type Option 5 and press Enter.\nCAMRASM displays the screen that describes what occurs in this part of the demo session.\n2.Press Enter.The application halts CAMRASM at an unconditional breakpoint that you included at the beginning of the\ndemo.\nSuppose you want to trace the execution path of the program prior to this point. You can have the application scroll back\nand display a previously executed statement using the PREV command. The PREV  command lets you view previously\nexecuted statements, but does not cause any statements to execute. After you scroll back using the PREV command, you\ncan scroll forward and retrace execution using the ADVANCE command. You may specify a number from 1 to 999 with the\nPREV and ADVANCE commands to scroll more than one statement at a time.\nThe PREV and ADVANCE commands do not change the statement where CAMRASM resumes execution; the PREV and\nADVANCE only scroll the statements in the trace.\nFollow these steps:\n1.Type the PREV 9 command in the Command field and press Enter.\nThe application displays the ninth previous statement executed. Now you can retrace the execution of the nine\nstatements using the ADVANCE command. The short form of the ADVANCE command is A or AD. (You must enter\nthe A on the command line.)\n2.Type the A command and press Enter.\n 608", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d00bc7ad3af1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe application highlights the next statement executed.\n3.Repeat the Advance step a few more times.You can follow the execution order of the program by following the\nhighlighted lines as you advance through the program trace. In effect, using PREV and ADVANCE gives you a\nsimulated instant replay of program execution.\nReturn to the Current Statement\nNow you can return to the current statement, that is, the statement where execution was halted prior to the unconditional\nbreakpoint.\nFollow these steps:\n1.Type the CS command and press Enter.\nThe application displays the original Breakpoint Intercept panel shown in the beginning of this option.\n2.Type the GO command and press Enter.\nCAMRASM resumes execution and displays the Advanced Options Demo Screen. You can continue with any option or\nexit.\nThis concludes Option 5: Trace Program Execution. Select another option and continue with the appropriate section, or\npress PF3 to end the demo.\nOption 7 Histogram Report\nThis option illustrates how to create and view the histogram report of statement execution, which is useful in identifying\ndead code.\nNOTE\nBefore proceeding, be sure you have completed the steps outlined in Advanced Demo Preliminaries and you\nhave the Demo Session Options Menu displayed on your screen.\nFollow these steps:\n1.Type Option 7 and press Enter.\nCAMRASM displays the screen that describes what occurs in this part of the demo session.\n2.Press Enter.The application halts CAMRASM at an unconditional breakpoint set at the program exit. Prior to exiting the\nprogram, you can request a histogram report using the HIST command.\n3.Type the HIST command and press Enter.\nThe application returns the following message: 'HISTOGRAM SUCCESSFULLY WRITTEN'\nView the Histogram Report", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d00bc7ad3af1-1", "text": "View the Histogram Report\nThe report is written to the data set associated with the ddname INT1REPT that can be viewed by splitting the screen.\nFollow these steps:\n1.Tab a few lines down your screen and press the SPLIT PF key defined in your ISPF profile (normally PF2).The ISPF\nMain Menu displays in the split-screen area.\n2.Select the ISPF Browse Facility and request a display of the data set associated with the ddname INT1REPT. You\nallocated this data set in Advanced Demo Preliminaries . The suggested data set name was: userid.INT1REPT.The first\npage of the histogram report displays.\n3.Page down to the end of the report using the maximum command with PF8.\n4.Type the M command. Press PF8.\nThe last page of the histogram report displays.\n5.Remove your split-screen using the command: X.You return to a full-screen display of the Program Exit Intercept.\nUse the Find Statement (FS) command to display the code that was never executed.\nType the FS 902 command and press Enter.\nThe application displays the requested line of code.\n 609", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "19cf6652cb28-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nDepending on your assemble options, line 902 may not be the label WRITE_ERROR. If this is the case, use the\nstatement number you found by scrolling up from the end of the histogram report.\nBy reviewing the code, you can determine whether or not it is required. In this case, it is an error routine and should be\nretained.\nIf unexecuted code needs to be removed from your own programs, you can split the screen again and make the code\nchanges, or wait until you complete the review of the histogram report.\nNow return to the current statement in the CAMRASM program.\nFollow these steps:\n1.Type the CS command and press Enter.\nThe application displays the Program Exit Intercept panel.\n2.To continue the advanced demo, enter the command go options and press Enter. To end the demo, enter the\ncommand GO.\nIf you are continuing the demo, CAMRASM program execution continues with the display of the Advanced Options\nMenu. Choose another option from the menu. If you are exiting the demo, CAMRASM resumes execution at the\nnormal program exit, and terminates. You return to the Execution Control panel of the Foreground Option. Your\nprevious entries are displayed, allowing you to begin testing again, or exit. Use PF3 to exit.\nAdvanced Demo Session for PL/I\nThis article illustrates a PL/I advanced demo session using CAMRPLI.\nBefore you proceed, completed the steps outlined in Advanced Demo Preliminarie, and have the Initial Intercept for\nCAMRPLI displayed on your screen.\nNOTE\nCAMRPLI is an ISPF application.\nInclude Unconditional Breakpoints\nNow you are going to set unconditional breakpoints at a number of procedure names in the demo program. In the basic", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "19cf6652cb28-1", "text": "demo you set an unconditional breakpoint using the U or ) line command, which are both equivalent to the UNCOND\ncommand. However, a quicker way to include unconditional breakpoints for a test session is to place the breakpoint\ncommands in a data set member, and simply include that member when the Initial Intercept panel displays.\nThe PLIINCL data set member of CAI.CAVHSAMP contains the commands that set the breakpoints required for using the\nAdvanced Options Demo for PL/I. Include this data set member as follows:\nEnter the following command at the *Initial* Intercept panel: include pliincl\nPress Enter.\nThe application processes the commands in the pliincl data set, and returns the following message in the upper-right\ncorner of the screen: BREAKPOINT SET.\n  CAMRPLI  ---------- CA InterTest Batch *INITIAL* Intercept ----- BREAKPOINT SET\n  COMMAND ===>                                                  SCROLL ===> CUR\n  TRACE=> 000001                                                                \n        *************************** Top of Data ********************************\n                            SOURCE LISTING                                      \n            STMT LEV NT                                                         \n   *-->                                                                         \n               1      0  CAMRPLI: PROC OPTIONS (MAIN);                          \n 610", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fb6e6626a793-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  \n  \n /*------------------------------------------------*/\n                            /* Welcome to the CA InterTest Batch    */\n                            /* PL/I demonstration program. You are now at the\n */\n                            /* Initial Breakpoint panel which is displayed   \n */\n                            /* upon entry to the first program to be tested. \n */\n                            /* At this point, other breakpoints can be set   \n */\n                            /* and control commands can be issued before the \n */\n                            /* program is executed.                          \n */\n  \n /*------------------------------------------------*/\n               2   1  0     DCL  REPORT                    FILE RECORD\n SEQUENTIA\n                                                           ENV (F,\n RECSIZE(80));\n               3   1  0     DCL  1 LINE_OUT,                                    \n                                    3 ASA_CNTL             CHAR(1),            \n \nAccess the Demo Session Options Menu\nAfter setting the required breakpoints, you can access the Demo Session Options Menu by executing the demo program\nand choosing the Advanced Options Menu from the Welcome panel.\nFollow these steps:\n1.In the Initial Intercept panel, type GO and press Enter to execute the program.The demo program begins execution\nand displays the Welcome panel.\n2.Press PF2 to access the Options Menu for the Advanced Demo Session.The Advanced Options Preliminary Screen is\ndisplayed, reminding you not to access the Options Menu without including the data set member PLIINCL.\n3.Press Enter to continue.The Demo Session Options Menu is displayed.\nA sample Demo Session Options Menu follows:\nEach of the options on the menu is independent and can be performed in any order. To use an option, follow the\nappropriate section. Upon completing an option, you return to the Menu.\nBefore you start, you should know that:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fb6e6626a793-1", "text": "Before you start, you should know that:\nTo interrupt a loop-press the ATTN or PA1 key. Try the ATTN key first. If that does not interrupt the loop, your testing\nenvironment requires you to use the PA1 key. If using PA1, you may need to press RESET first.\nExit the Advanced Options Demo\nYou can exit the demo from the Options Menu at any time.\nFollow these steps:\n1.Press PF3.The End Demo Session screen is displayed.\n 611", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fe7b571af93c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n2.Press Enter.The Program Breakpoint Intercept panel displays for an unconditional breakpoint at label\nRETURN_TO_OPSYS. (This breakpoint was set by a command in the PLIINCL include file.)\n3.Type GO and press Enter to execute the program.The demo program ends, and the Entry panel is displayed.\nReturn to the Advanced Options Demo Session\nIf you exit the demo, you can return at any time to perform another advanced option. Just repeat the steps in Access the\nDemo Session Options Menu. Remember to enter the following command at the Initial Breakpoint screen:\n include pliincl\n \nOption 1 Time-Controlled Execution\nThis option illustrates how you can slow the execution of your program. The SLOW command executes one statement\nin your program every few seconds. The exact time interval is specified when you issue the SLOW command. Using the\nSLOW command together with a keep window is an especially effective testing technique; it lets you halt the program\nwhenever you see a problem, without having to determine the breakpoint in advance.\nNOTE\nBefore proceeding, be sure you have completed the steps outlined in Advanced Demo Preliminaries and you\nhave the Demo Session Options Menu displayed on your screen.\nThis option requires you to interrupt the program by pressing the ATTENTION key or the PA1 key. Before proceeding,\nlocate each of these keys on your keyboard. If you need help in finding them, ask a technical support person before you\nbegin.\nFollow these steps:\n1.Select option 1 and Press  Enter.\nCAMRPLI displays the screen that describes what occurs in this part of the demo session.\n2.Press  Enter.The application halts CAMRPLI at an unconditional breakpoint set at procedure PAY_CALC. The\nprocedure statement is highlighted.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fe7b571af93c-1", "text": "procedure statement is highlighted.\n3.Open a keep window that displays the values of YTD and X_AXIS_YTD by entering the commands specified below.\nNotice how you can use the short form of the keep command K and use the TSO command delimiter (normally a semi-\ncolon) to string multiple commands on a single command line. Type the following command: k ytd; k x_axis_ytd\nThe application displays a keep window showing the current values of YTD and X_AXIS_YTD. A sample screen\nshowing the keep window for YTD and X_AXIS_YTD follows:\n CAMRPLI  ---------- CA InterTest Batch UNCOND BEFORE Intercept ---------------\n COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000168 000094 000093 000092 000091 000088 000087 000086 000085 000084\n 0\n  \n -------------------------------------------------------------------------\n       1F1A84EF NP-S  000090 02 YTD                          +0000000.00      \n       1F1A84F7 AN    000089 03 X_AXIS_YTD                                    \n  \n -------------------------------------------------------------------------\n  \n U--->      168   1  0     PAY_CALC: PROC ( I );                               \n  \n            169   2  0        DCL I                        PIC '999';          \n            170   2  0        DCL J                        FIXED BIN(15);      \n  \n  \n  --->      171   2  0        DO J = 1 TO I BY 1;                              \n 612", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3d99063f14f6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  --->      172   2  1           CALL POPULATE_GRAPH ( J );                    \n  --->      173   2  1           END;                                          \n  \n                           /* CHEQUE_LINE                 = ' ';             */\n  --->      174   2  0        CHEQUE_AMOUNT               = TOTALGROSS;        \n  --->      175   2  0        RETURN;                                          \n  \n  --->      176   2  0     END PAY_CALC;                                       \n \nIssue the SLOW command to execute one statement every two seconds. As the program resumes execution, you\nare able to see the changing values of YTD and X_AXIS_YTD. In this demo, you are going to halt execution when the\nX_AXIS_YTD value is MAR by pressing the ATTENTION key.\nFollow these steps:\n1.Type the SLOW 2 command and press Enter.\nThe application initiates a time-controlled execution of CAMRPLI, at a rate of one statement every two seconds.\n2.When the value of X_AXIS_YTD in the keep window is MAR, press the ATTN or PA1 key. Try the ATTN key first.The\nAttention Intercept panel displays, as shown in the following panel. A sample Attention Intercept panel follows:\n  CAMRPLI  ---------- CA InterTest Batch ATTENTION Intercept -------------------\n COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000185 000184 000183 000182 000177 000172 000173 000186 000185 000184\n 0\n  \n -------------------------------------------------------------------------\n       1F1A84EF NP-S  000090 02 YTD                          +0256273.52      \n       1F1A84F7 AN    000089 03 X_AXIS_YTD                   MAR", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3d99063f14f6-1", "text": "-------------------------------------------------------------------------\n  \n  0003      182   2  0        X_AXIS_YTD                  = MONTH_ITEM ( I );  \n  0003      183   2  0        X_AXIS_R ( I )              = TOKEN_ITEM;        \n  0003      184   2  0        YTD                        = YTD + MONTHLY_AMOUNT\n  0002      185   2  0        TOTALGROSS                  = YTD;               \n  0002      186   2  0        RETURN;                                          \n  \n  --->      187   2  0     END POPULATE_GRAPH;                                 \n  \n  --->      188   1  0     BILL_CALC: PROC;                                    \n  \n            189   2  0        DCL   I                       FIXED BIN(15);     \n            190   2  0        DCL 1 BILLS_BILLS_BILLS,                         \n                                    3 BILLS_MONTHLY,                           \n                                      5 BILLING_AMOUNT (12) FIXED DEC(7,2) \n INIT\n  \n \nReview what you just did.\n 613", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "32eadc372221-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022You opened a keep window for two variables whose values you wished to view and compare.\n\u2022You used the command slow 2 to have the application slowly execute the program. However, during the program\nexecution, you could monitor the values of the variables in the keep window.\n\u2022You used the ATTENTION or PA1 key to stop program execution, and the Attention Intercept panel displays.\nThis combination of using keep windows, the slow command, and an Attention Intercept lets you carefully control and\nmonitor your program execution, while tracking the values of specific variables.\nNOTE\nThe Attention Intercept panel is only displayed when the user presses the ATTN or PA1 key and then the\napplication executes a statement in a program that is currently being monitored.\nRemove the Keep Window\nBefore returning to the Options Menu of the advanced demo, remove the keep window.\nType the REMOVE ALL command and press Enter.\nThe application removes the keep window for YTD and X_AXIS_YTD on the Attention Intercept panel.\nContinue Execution\nType GO and press Enter to continue execution.CAMRPLI resumes execution, and displays the Options Menu.\nThis concludes Option 1: Time Controlled Execution. Select another option and go to the appropriate section, or exit the\ndemo using PF3.\nOption 2 Set Conditional Breakpoints\nThis option shows you how to set and use conditional breakpoints.\nNOTE\nBefore proceeding, be sure you have completed the steps outlined in Advanced Demo Preliminaries and you\nhave the Demo Session Options Menu displayed on your screen.\nFollow these steps:\n1.Select option 2 and press  Enter.\nCAMRPLI displays the screen that describes what occurs in this part of the demo session.\n2.Press  Enter.The application halts CAMRPLI at an unconditional breakpoint. The statement at the breakpoint is\nhighlighted.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "32eadc372221-1", "text": "highlighted.\n3.Access the screen used to set conditional breakpoints. From this screen, you can set both the conditions and any\ncommands you want executed when the specified condition is met.\n4.Type the COND command in the Command field and press Enter.\nThe When panel displays. WHEN is a synonym for COND.\n5.Make the following entries on the When panel and press Enter:\n ----------------------- CA InterTest Batch WHEN PANEL -------------------------\n OPTION ===>S\n  \n    S - SET A WHEN CONDITION                                                   \n  R - RESET A WHEN CONDITION                                               \n    L - OR BLANK, LIST THE WHEN CONDITIONS                                   \n  \n SPECIFY DATA AREA NAME(S) AND COMPARISON CONDITION:      \n    WHEN-NAME    ===> ytdcond                                                \n    DATA-AREA-1  ===> subtotal                                               \n    OPERATOR     ===> ge        (EQ, NE, LT, GT, LE, GE, =, <>, <, >, <=, >=)\n 614", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5dd880ea8be2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    DATA-AREA-2  ===> 600.00                                              \n    AFTER        ===> N         (Y/N)                                        \n  \n COMMANDS TO BE EXECUTED AT WHEN CONDITION:                                  \n ===>  k subtotal; set totalgross = 2000; k totalgross \n \nThe application displays the following message in the top right corner of the When panel: WHEN CONDITION SET.\n6.Press PF3 to exit the When panel.The application brings you to the previous Breakpoint Intercept panel.\n7.Continue execution by typing GO and pressing Enter.CAMRPLI resumes execution until the condition you set for the\nYTDCOND breakpoint is met; when the value of SUBTOTAL is greater than or equal to 600, InterTest Batch halts\nexecution, and executes the commands you entered for the conditional breakpoint; it displays a keep window for\nSUBTOTAL, sets TOTALGROSS to 2000, and then displays TOTALGROSS in the keep window. Your screen should\nlook like the Intercept panel in the following screen.\nA sample intercept panel showing condition YTDCOND has been met follows:\n  CAMRPLI  ---------- CA InterTest Batch WHEN YTDCOND BEFORE Intercept ---------\n COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000193 000192 000194 000193 000192 000194 000193 000192 000191 000188\n 0\n  \n -------------------------------------------------------------------------\n       1F1A84E6 NP-S  000101 02 SUBTOTAL                     +00971.68        \n       1F1A84EA NP-S  000090 02 TOTALGROSS                   +0002000.00      \n  \n -------------------------------------------------------------------------\n  0003      192   2  1          SUBTOTAL                 = SUBTOTAL + BILLING_A", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5dd880ea8be2-1", "text": "0002      193   2  1          BILL_YTD                  = SUBTOTAL;          \n  0002      194   2  1        END;                                             \n  --->      195   2  0        RETURN;                                          \n  \n  --->      196   2  0     END BILL_CALC;                                      \n  \n  --->      197   1  0     INITIALIZE_TABLE: PROC;                             \n  \n            198   2  0        DCL (I, J)                   FIXED BIN(15);      \n  \n  --->      199   2  0        DO I = 1 TO 2;                                   \n  --->      200   2  1          DO J = 1 TO 9;                                 \n  --->      201   2  2            STATE_NUMBER ( I )      = I;                 \n       5688-235 IBM PL/I for MVS & VM          CAMRPLI: PROC OPTIONS (MAIN);   \n           STMT LEV NT                                                         \n  --->      202   2  2            COUNTY_NUM1 ( I, J )    = I;                 \n \nNow remove the conditional breakpoint before continuing.\nFollow these steps:\n1.Return to the When panel by entering the WHEN command and pressing  Enter.\nThe When panel is displayed.\n2.Type the following on the When panel and press Enter:\n ----------------------- CA InterTest Batch WHEN PANEL -------------------------\n OPTION ===>R\n 615", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c4ecca93719c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  \n    S - SET A WHEN CONDITION                                                 \n    R - RESET A WHEN CONDITION                                               \n    L - OR BLANK, LIST THE WHEN CONDITIONS                                   \n  \n SPECIFY DATA AREA NAME(S) AND COMPARISON CONDITION:      \n    WHEN-NAME    ===> ytdcond                                                \n    DATA-AREA-1  ===>                                                \n    OPERATOR     ===>           (EQ, NE, LT, GT, LE, GE, =, <>, <, >, <=, >=)\n    DATA-AREA-2  ===>                                               \n    AFTER        ===> N         (Y/N)                                        \n  \n COMMANDS TO BE EXECUTED AT WHEN CONDITION:                                  \n ===>   \n \nThe application displays the following message in the top right corner of the When panel: WHEN DELETED.\n3.Press PF3 to exit the When panel.The application brings you to the previous Intercept panel.\nRemove the Keep Window and Continue Execution\nRemove the keep window before continuing execution.\nType the REMOVE ALL command and press Enter.\nThe keep window is removed.\nReturn to the Options Menu by continuing execution.\nType GO and press Enter.CAMRPLI resumes execution and displays the Options Menu.\nThis concludes Option 2: Conditional Breakpoints. Select another option and go to the appropriate section, or exit the\ndemo using PF3.\nOption 3 Update Source Code\nThis option illustrates how you can use the ISPF split-screen capability from any screen. One way to use this feature is to\nupdate your source code as soon as you find errors during your test session.\nNOTE\nBefore proceeding, be sure you have completed the steps outlined in Advanced Demo Preliminaries and you\nhave the Demo Session Options Menu displayed on your screen.\nFollow these steps:\n1.Select option 3 and press Enter.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c4ecca93719c-1", "text": "Follow these steps:\n1.Select option 3 and press Enter.\nCAMRPLI displays the screen that describes what occurs in this part of the demo session.\n2.Press Enter.The application halts CAMRPLI at an unconditional breakpoint at the label SPLIT_SCREEN.\n3.Tab about halfway down your screen and press the SPLIT PF key defined in your ISPF profile (normally PF2).The\nISPF Primary Option Menu displays in the bottom half of your screen. A sample showing using a split-screen from an\nIntercept panel follows:\n CAMRPLI  ---------- CA InterTest Batch UNCOND BEFORE Intercept ---------------\n COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000109 000108 000107 000106 000105 000078 000077 000076 000075 000074\n 0\n  \n U--->      109   1  0     SPLIT_SCREEN:                                       \n  \n 616", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a59611d1aee1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                              GO TO OPTIONS;                                   \n  \n                           /*------------------------------------------------*/\n                           /* FROM THIS UNCONDITIONAL BREAKPOINT YOU CAN     */\n                           /* PRESS THE PF KEY ASSIGNED TO THE SPLIT COMMAND */\n                           /* WHICH TAKES YOU TO THE ISPF MAIN MENU.         */\n                           /*------------------------------------------------*/\n .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . \n .\n                                    CA                         \n                            Islandia Data Center                               \n                                                                        USER01\n OPTION ===>                                   CCCCCCCCCCCCCCCCCCCCCCCC CATSO  \n                                             CCCCCCCCCCCCCCCCCCCCCCCC  \n 06/05/02\n                                            CCCC                        14:09  \n    C  CA Products                         CCCC                         XAD1   \n    D  SVC Dump Index                      CCCC                 AAAAAAA        \n    G  Color Graphics Terminal Products    CCCC               AAAAAAAAA        \n    P  Program Development Facility        CCCC             AAAA   AAAA        \n \nUpdate Your Source Code\nIf you had found an error in your program code, you can use ISPF to access and edit your source code before continuing\nwith your test session.\nFor example, in the basic demo, the application stopped execution of the program because it detected an S0C7 ABEND.\nYou were able to continue execution by dynamically changing the value of Tasknum to zero. This was a one-time patch.\nTo correct the problem, you need to update your source code so that Tasknum is properly initialized. You can do this from\nany Intercept panel by splitting your screen to edit your source code.\nContinue Execution\nFollow these steps:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a59611d1aee1-1", "text": "Continue Execution\nFollow these steps:\n1.Remove your ISPF split-screen using the command: =XYou return to a full-screen display of the unconditional\nbreakpoint shown in the previous panel.\n2.Type GO and press Enter to continue execution.You return to the Demo Options Menu.\nThis concludes Option 3: Update Source Code. Select another option and go to the appropriate section, or exit the demo\nusing PF3.\nOption 4 Interrupt a Looping Program\nThis option illustrates how to interrupt and verify that you have a looping program. It also illustrates the use of the skip\ncommand.\nNOTE\nBefore proceeding, be sure you have completed the steps outlined in Advanced Demo Preliminaries and you\nhave the Demo Session Options Menu displayed on your screen.\nThis option requires you to interrupt the program by pressing the ATTENTION key or the PA1 key. Before proceeding,\nlocate each of these keys on your keyboard. If you need help, ask a technical support person before you begin.\n 617", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2de04e626305-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFollow these steps:\n1.Select option 4 and press Enter.\nCAMRPLI displays the screen that describes what occurs in this part of the demo session.\n2.Press Enter.The application halts CAMRPLI at an unconditional breakpoint set at ORDER_CALC. A sample screen\nshowing CAMRPLI stopped at ORDER_CALC follows:\n  CAMRPLI  ---------- CA InterTest Batch UNCOND BEFORE Intercept ---------------\n COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000134 000133 000132 000131 000130 000079 000078 000077 000076 000075\n 0\n  \n U--->      134   1  0     ORDER_CALC:                                         \n  \n                           /*------------------------------------------------*/\n                           /* THIS SECTION OF THE DEMO SHOWS YOU HOW TO      */\n                           /* INTERRUPT A LOOPING PROGRAM AND CHANGE THE     */\n                           /* EXECUTION LOGIC WITHOUT RE-COMPILATION.        */\n                           /*------------------------------------------------*/\n  \n                              LOOP_OUT                    = 0;                 \n  \n  --->      135   1  0        CALL TOTAL_ORDER ( );                            \n  \n  --->      136   1  0        GO TO OPTIONS;                                   \n  \n  --->      137   1  0     DEMONSTRATE_HIST_COMMAND:                           \n  \n                           /*------------------------------------------------*/\n                           /* THIS SECTION OF THE DEMO SHOWS YOU HOW TO      */\n                           /* ISSUE THE HISTOGRAM COMMAND.                   */\n                           /*------------------------------------------------*/\n \nNOTE\nIf the Frequency Counter arrows and numbers are not displayed along the left side of your screen, turn the\nfrequency display on by entering the command: freq.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2de04e626305-1", "text": "frequency display on by entering the command: freq.\n3.Continue execution by typing GO and pressing Enter.CAMRPLI resumes execution. Notice the system light remains\non. There are additional breakpoints and screen panels in the demo program code, yet all you see is the system light.\nThis is symptomatic of a looping program. Halt the program to see what is going on.\n4.Press the ATTN or PA1 key. Try the ATTN key first. If that does not work, your testing environment requires you to use\nthe PA1 key. Press RESET before pressing the PA1 key to unlock the terminal keyboard.The Attention Intercept panel\ndisplays.\nContinue with the instructions in Continuing from the Attention Routine.\nNOTE\nIf you do not successfully stop execution with the ATTN or PA1 key before 20,000 executions of the demo\nprogram loop, you reach a safety net conditional breakpoint. If you reach this breakpoint, instructions for\ncontinuing follow.\nContinue from the \u201cSafety Net\u201d Conditional Breakpoint\nFollow this section only if you see the breakpoint in the following panel. If you do not, continue with the instructions in\nthe Continuing from the Attention Routine section that follows.\n 618", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5c31d47aea6d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nA sample screen showing a Safety Net Conditional Breakpoint of a Demo Loop follows:\n CAMRPLI  ---------- CA InterTest Batch WHEN LOOPCOND BEFORE Intercept --------\n COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000219 000218 000217 000216 000221 000220 000219 000218 000217 000216 0\n       -------------------------------------------------------------------------\n       227A93FA NP-S  000210    ITEM_TOTAL                   +0000969.00      \n       227A941A NP-S  000213 04 UNIT_PRICE                   +00080.75        \n                                   I  (+2)                                    \n       227A941E NP-S  000213 04 NO_OF_WIDGETS                +0000012.        \n                                   I  (+2)                                    \n       -------------------------------------------------------------------------\n  020K      217   2  1          I                         = I + 1;             \n  020K      218   2  1          LOOP_OUT                  = LOOP_OUT + 1;      \n  020K      219   2  1          ITEM_TOTAL                = UNIT_PRICE ( I ) * \n                                                       NO_OF_WIDGETS ( I );    \n       5688-235 IBM PL/I for MVS & VM          CAMRPLI: PROC OPTIONS (MAIN);   \n           STMT LEV NT                                                         \n  020K      220   2  1          I                         = 1;                 \n  020K      221   2  1          ORDER_SUB_TOTAL           = ORDER_SUB_TOTAL + IT\n            222   2  1        END;                                             \n  \n U--->      223   2  0     TOTAL_ORDER_EX:                                     \n  \n                              RETURN;", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5c31d47aea6d-1", "text": "RETURN;                                          \n \nTo continue with the looping program demo, you must press the ATTN or PA1 key before 20,000 executions of the loop\nthis time. To continue the program loop, use the following steps:\n1.Type GO and press Enter to continue the loop execution.\n2.Press the ATTN key or the RESET, then PA1 keys. Try the ATTN key first. If that does not work, your testing\nenvironment requires you to use the PA1 key.\nNOTE\nEven if PA1 stopped the slow execution in option 1, you may need to press ATTN to stop a loop.\nYou should see the Attention Intercept panel.\nTo return to the Options Menu:\n1.Enter the command: go options_menu\nNOTE\nThis compiler is an optimizing compiler. Therefore, an abend is possible using the GO <label> command. If\nthis happens, you can return to the Options Menu by restarting the demo application.\n2.Press Enter.\nYou return to the Options Menu. You can try the same option again, even if you did not complete it the first time, or\nselect another option from the menu.\nContinue from the Attention Routine\nThe application now displays the Attention Intercept panel. A sample showing an Attention Intercept in procedure\nTOTAL_ORDER follows:\n CAMRPLI  ---------- CA InterTest Batch ATTENTION Intercept -------------------\n COMMAND ===>                                                  SCROLL ===> CUR\n 619", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "39715843ddfe-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n TRACE=> 000221 000220 000219 000218 000217 000216 000221 000220 000219 000218 0\n  013K      220   2  1          I                         = 1;                 \n  013K      221   2  1          ORDER_SUB_TOTAL           = ORDER_SUB_TOTAL + IT\n            222   2  1        END;                                             \n  \n U--->      223   2  0     TOTAL_ORDER_EX:                                     \n  \n                              RETURN;                                          \n  \n  --->      224   2  0     END TOTAL_ORDER;                                    \n  \n  --->      225   1  0     PROPAGATE: PROC;                                    \n  \n            226   2  0        DCL I                        FIXED BIN(15)   INIT(\n            227   2  0        DCL TABLE_SUB                FIXED BIN(15)   INIT(\n            228   2  0        DCL 1 TABLE_OF_SORTS,                            \n                                    3 TABLE_ELEMENT (60)   CHAR(1);            \n  \n  --->      229   2  0        DO I = 1 TO 17;                                  \n  --->      230   2  1          TABLE_SUB                 = INCREMENT ( TABLE_SU\n  --->      231   2  1          TABLE_ELEMENT ( TABLE_SUB ) = '+';             \n  --->      232   2  1          TABLE_SUB                 = INCREMENT ( TABLE_SU\n \nCAMRPLI keeps executing the TOTAL_ORDER procedure, as you can see from your Attention Intercept screen display.\nThe current statement is highlighted.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "39715843ddfe-1", "text": "The current statement is highlighted.\nLook at the frequency counters to the left of the program statements. They show repeated execution of the\nTOTAL_ORDER statements, indicating a loop. To investigate the logic in TOTAL_ORDER, you can set a keep window for\nI and then execute slowly using the SLOW command. This time you use the abbreviated form of the keep command: K.\nFollow these steps:\n1.Type the K I command to set the keep window and press Enter.\nThe application displays a keep window for the variable I. A sample screen showing the keep window to View I follows:\n CAMRPLI  ---------- CA InterTest Batch ATTENTION Intercept -------------------\n COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000221 000220 000219 000218 000217 000216 000221 000220 000219 000218 0\n       -------------------------------------------------------------------------\n       1F1A93F2 NB-S  000209    I                            +1.              \n       -------------------------------------------------------------------------\n  013K      220   2  1          I                         = 1;                 \n  013K      221   2  1          ORDER_SUB_TOTAL           = ORDER_SUB_TOTAL + IT\n            222   2  1        END;                                             \n  \n U--->      223   2  0     TOTAL_ORDER_EX:                                     \n  \n                              RETURN;                                          \n  \n  --->      224   2  0     END TOTAL_ORDER;                                    \n  \n  --->      225   1  0     PROPAGATE: PROC;                                    \n  \n            226   2  0        DCL I                        FIXED BIN(15)   INIT(\n            227   2  0        DCL TABLE_SUB                FIXED BIN(15)   INIT(\n 620", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "275f6f219d68-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n            228   2  0        DCL 1 TABLE_OF_SORTS,                            \n                                    3 TABLE_ELEMENT (60)   CHAR(1);            \n  \n  --->      229   2  0        DO I = 1 TO 17;                                  \n \n2.To execute one CAMRPLI statement every two seconds, type the SLOW 2 command and press Enter.\nCAMRPLI continues a slow execution. As the code executes, you can see the code looping, and you can see the\ncorresponding value of I in the keep window. The following sample screen of a SLOW 2 Execution shows a Loop and I\nproblem:\n CAMRPLI  ---------- CA InterTest Batch STEP BEFORE Intercept -----------------\n COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000220 000219 000218 000217 000216 000221 000220 000219 000218 000217 0\n       -------------------------------------------------------------------------\n       1F1A93F2 NB-S  000209    I                            +2.              \n       -------------------------------------------------------------------------\n  \n  013K      216   2  0        DO UNTIL (I = ORDER_ITEMS);                      \n  013K      217   2  1          I                         = I + 1;             \n  013K      218   2  1          LOOP_OUT                  = LOOP_OUT + 1;      \n  013K      219   2  1          ITEM_TOTAL                = UNIT_PRICE ( I ) * \n                                                       NO_OF_WIDGETS ( I );    \n       5688-235 IBM PL/I for MVS & VM          CAMRPLI: PROC OPTIONS (MAIN);   \n           STMT LEV NT", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "275f6f219d68-1", "text": "STMT LEV NT                                                         \n  013K      220   2  1          I                         = 1;                 \n  013K      221   2  1          ORDER_SUB_TOTAL           = ORDER_SUB_TOTAL + IT\n            222   2  1        END;                                             \n  \n U--->      223   2  0     TOTAL_ORDER_EX:                                     \n  \n                              RETURN;                                          \n  \n  --->      224   2  0     END TOTAL_ORDER;                                    \n \nNotice that I changes from 1 to 2, but back to 1 again. I is being reset to 1, and causing the program to loop. The value\nof I is causing the TOTAL_ORDER procedure to continue to be executed.\n3.Stop the execution by pressing the ATTENTION or PA1 key. After the Attention Routine message is displayed, press\nEnter.\nThe application brings you to another Attention Intercept panel. The current statement is highlighted.\n4.To dynamically correct the loop-condition, you could use the SKIP command to bypass the offending statement. The s\nline command is another form of the SKIP command.\n5.Tab down to the statement: I = 1, and type S to the left of the line. The following sample screen shows using skip to\nbypass the cause of the loop:\n CAMRPLI  ---------- CA InterTest Batch ATTENTION Intercept -------------------\n COMMAND ===>                                                  SCROLL ===> CSR\n TRACE=> 000219 000218 000217 000216 000221 000220 000219 000218 000217 000216 0\n       -------------------------------------------------------------------------\n       1F1A93F2 NB-S  000209    I                            +2.              \n       -------------------------------------------------------------------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "275f6f219d68-2", "text": "-------------------------------------------------------------------------\n  \n  013K      216   2  0        DO UNTIL (I = ORDER_ITEMS);                      \n  013K      217   2  1          I                         = I + 1;             \n  013K      218   2  1          LOOP_OUT                  = LOOP_OUT + 1;      \n 621", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "889305095702-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  013K      219   2  1          ITEM_TOTAL                = UNIT_PRICE ( I ) * \n                                                       NO_OF_WIDGETS ( I );    \n       5688-235 IBM PL/I for MVS & VM          CAMRPLI: PROC OPTIONS (MAIN);   \n           STMT LEV NT                                                         \n S013K      220   2  1          I                         = 1;                 \n  013K      221   2  1          ORDER_SUB_TOTAL           = ORDER_SUB_TOTAL + IT\n            222   2  1        END;                                             \n  \n U--->      223   2  0     TOTAL_ORDER_EX:                                     \n  \n                              RETURN;                                          \n  \n  --->      224   2  0     END TOTAL_ORDER;                                    \n  \n \nThe application skips the statement that sets I to 1, and executes the code as if the statement was removed.\n6.Tab up to the second statement in the DO loop, I = I + 1, and type G to the left of the line, to continue execution from\nthat point\nYour entry should match the following panel. The following sample screen shows a continuing execution from the add\nstatement:\n CAMRPLI  ---------- CA InterTest Batch NEXT BEFORE Intercept --- BREAKPOINT SET\n COMMAND ===>                                                  SCROLL ===> CSR\n TRACE=> 000219 000218 000217 000216 000221 000220 000219 000218 000217 000216 0\n       -------------------------------------------------------------------------\n       1F1A93F2 NB-S  000209    I                            +2.              \n       -------------------------------------------------------------------------\n  \n  013K      216   2  0        DO UNTIL (I = ORDER_ITEMS);", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "889305095702-1", "text": "g013K      217   2  1          I                         = I + 1;             \n  013K      218   2  1          LOOP_OUT                  = LOOP_OUT + 1;      \n  013K      219   2  1          ITEM_TOTAL                = UNIT_PRICE ( I ) * \n                                                       NO_OF_WIDGETS ( I );    \n       5688-235 IBM PL/I for MVS & VM          CAMRPLI: PROC OPTIONS (MAIN);   \n           STMT LEV NT                                                         \n S013K      220   2  1          I                         = 1;                 \n  013K      221   2  1          ORDER_SUB_TOTAL           = ORDER_SUB_TOTAL + IT\n            222   2  1        END;                                             \n  \n U--->      223   2  0     TOTAL_ORDER_EX:                                     \n  \n                              RETURN;                                          \n  \n  --->      224   2  0     END TOTAL_ORDER;                                   \n \n7.Press Enter.CAMRPLI resumes execution from the line where you entered the g, and continues execution until it\nreaches the next unconditional breakpoint, as shown in the following panel.  The following sample screen shows an\nunconditional breakpoint at TOTAL_ORDER_EX:\n CAMRPLI  ---------- CA InterTest Batch UNCOND BEFORE Intercept ---------------\n COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000223 000221 000219 000218 000217 000216 000221 000219 000218 000217 0\n       -------------------------------------------------------------------------\n       1F1A93F2 NB-S  000209    I                            +5.              \n 622", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6813cfb2d826-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n       -------------------------------------------------------------------------\n  \n  013K      216   2  0        DO UNTIL (I = ORDER_ITEMS);                      \n  013K      217   2  1          I                         = I + 1;             \n  013K      218   2  1          LOOP_OUT                  = LOOP_OUT + 1;      \n  013K      219   2  1          ITEM_TOTAL                = UNIT_PRICE ( I ) * \n                                                       NO_OF_WIDGETS ( I );    \n       5688-235 IBM PL/I for MVS & VM          CAMRPLI: PROC OPTIONS (MAIN);   \n           STMT LEV NT                                                         \n S013K      220   2  1          I                         = 1;                 \n  013K      221   2  1          ORDER_SUB_TOTAL           = ORDER_SUB_TOTAL + IT\n            222   2  1        END;                                             \n  \n U--->      223   2  0     TOTAL_ORDER_EX:                                     \n  \n                              RETURN;                                          \n  \n  --->      224   2  0     END TOTAL_ORDER;                                    \n \nCAMRPLI finally exited out of the DO loop and continued until it reached the unconditional breakpoint set at\nTOTAL_ORDER_EX (one of the unconditional breakpoints included in the data set member PLIINCL).\nYou can see from the keep window that the value of I is 5. This is the proper value to permit the exit of the DO loop.\nThus, the use of the skip command allowed us to dynamically fix the program code that caused the loop, and continue\nexecution.\nRemove the Keep Window and Skip Command\nBefore going back to the options menu, remove the keep window and skip command.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6813cfb2d826-1", "text": "Before going back to the options menu, remove the keep window and skip command.\nFollow these steps:\n1.Type the REMOVE ALL command.\n2.Tab down to the I = 1 statement and type over the S to the left of the statement with X and press Enter.\nThe keep window is removed, and the skip line command is removed.\n3.Continue execution by  typing GO and pressing Enter.CAMRPLI resumes execution and displays the Demo Session\nOptions Menu.\nThis concludes Option 4: Interrupt a Program Loop. Select another option and go to the appropriate section, or exit the\ndemo using PF3.\nOption 5 Trace Program Execution\nThis option illustrates the use of the PREVIOUS and ADVANCE commands to help you trace program execution.\nNOTE\nBefore proceeding, be sure you have completed the steps outlined in Advanced Demo Preliminaries and you\nhave the Demo Session Options Menu displayed on your screen.\nFollow these steps:\n1.Select option 5 and press Enter.\nCAMRPLI displays the screen that describes what occurs in this part of the demo session.  The following sample\nscreen shows Option 5: Trace Program Execution:\n      **********************************************************************   \n      *****                                                            *****   \n 623", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "444dd57af6bc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n      *****              CA InterTest Batch Demo Session               *****   \n      *****                  Tracing program execution                 *****   \n      *****                                                            *****   \n      **********************************************************************   \n  \n        CA InterTest Batch gives you the ability to trace the execution of     \n        your program up to the point where a breakpoint occurs.                \n        Here is what will happen:                                              \n  \n        1. CA InterTest Batch halts the DEMO program at an unconditional       \n           breakpoint.                                                         \n        2. You use a combination of the Prev and Advance commands to           \n           scroll through the program statements in execution order.           \n        3. You issue the CS command to re-display the Current Statement        \n           to be executed.                                                     \n  \n  \n           Press ENTER to continue or PF3 to return to the Options Menu.       \n  \n \n2.Press Enter.The application halts CAMRPLI at an unconditional breakpoint that you included at the beginning of the\ndemo. The following sample screen shows CAMRPLI at an unconditional breakpoint:\n CAMRPLI  ---------- CA InterTest Batch UNCOND BEFORE Intercept ---------------\n COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000168 000118 000117 000116 000115 000114 000113 000112 000111 000110\n 0\n  \n U0001      168   1  0     PAY_CALC: PROC ( I );                               \n  \n            169   2  0        DCL I                        PIC '999';          \n            170   2  0        DCL J                        FIXED BIN(15);      \n  \n  \n  0001      171   2  0        DO J = 1 TO I BY 1;", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "444dd57af6bc-1", "text": "0005      172   2  1           CALL POPULATE_GRAPH ( J );                    \n  0005      173   2  1           END;                                          \n  \n                           /* CHEQUE_LINE                 = ' ';             */\n  0001      174   2  0        CHEQUE_AMOUNT               = TOTALGROSS;        \n  0001      175   2  0        RETURN;                                          \n  \n  --->      176   2  0     END PAY_CALC;                                       \n  \n  0005      177   1  0     POPULATE_GRAPH: PROC ( I );                         \n  \n            178   2  0        DCL   I                      FIXED BIN(15);      \n            179   2  0        DCL 1 MONTH_THING            STATIC,             \n \nSuppose you want to trace the execution path of the program prior to this point. You can have the application scroll back\nand display a previously executed statement using the PREV command. The PREV  command lets you view previously\nexecuted statements, but does not cause any statements to execute. After you scroll back using the PREV command, you\n 624", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ad80f200badc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\ncan scroll forward and retrace execution using the ADVANCE command. You may specify a number from 1 to 999 with the\nPREV and ADVANCE commands to scroll more than one statement at a time.\nThe PREV and ADVANCE commands do not change the statement where CAMRPLI resumes execution; the PREV and\nADVANCE only scroll the statements in the trace.\nFollow these steps:\n1.Type the PREV 9 command in the Command field and press Enter.\nThe application displays the ninth previous statement executed. The following screen shows the ninth previous\nstatement:\n CAMRPLI  ---------- CA InterTest Batch UNCOND BEFORE Intercept ---------------\n COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000168 000118 000117 000116 000115 000114 000113 000112 000111 000110\n 0\n  \n  0001      110   1  0     DEMONSTRATE_PREV_COMMAND:                           \n  \n                              CALL ISPLINK ( DSPLY,                            \n                                             COBDPN75 );                       \n  \n                           /*------------------------------------------------*/\n                           /* THIS SECTION OF THE DEMO SHOWS YOU             */\n                           /* THE BENEFITS OF USING THE PREV                 */\n                           /* AND ADVANCE COMMANDS.                          */\n                           /*------------------------------------------------*/\n  \n  0001      111   1  0        COBDPN71_LENGTHS            = 4;                 \n  \n  0001      112   1  0        CALL ISPLINK ( VCOPY,                            \n                                             VCOPY_COBDPN71,                   \n                                             VCOPY_COBDPN71_LENGTHS,           \n                                             VCOPY_COBDPN71_VALUES,            \n                                             VCOPY_MOVE );", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ad80f200badc-1", "text": "VCOPY_COBDPN71_VALUES,            \n                                             VCOPY_MOVE );                     \n  \n  0001      113   1  0        IF VCOPY_COBDPN71_EIBAID    = 'PF03' THEN        \n \nNow you can retrace the execution of the nine statements using the ADVANCE command. The short form of the\nADVANCE command is A or AD. (You must enter the A on the command line.)\n2.Type the A command and press Enter.\nThe application highlights the next statement executed.\n3.Repeat the Advance step a few more times. The following screen shows advancing through the program trace:\n CAMRPLI  ---------- CA InterTest Batch UNCOND BEFORE Intercept ---------------\n COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000168 000118 000117 000116 000115 000114 000113 000112 000111 000110\n 0\n  \n  0001      110   1  0     DEMONSTRATE_PREV_COMMAND:                           \n  \n                              CALL ISPLINK ( DSPLY,                            \n                                             COBDPN75 );                       \n  \n                           /*------------------------------------------------*/\n                           /* THIS SECTION OF THE DEMO SHOWS YOU             */\n 625", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ffe7dd4502b1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                           /* THE BENEFITS OF USING THE PREV                 */\n                           /* AND ADVANCE COMMANDS.                          */\n                           /*------------------------------------------------*/\n  \n  0001      111   1  0        COBDPN71_LENGTHS            = 4;                 \n  \n  0001      112   1  0        CALL ISPLINK ( VCOPY,                            \n                                             VCOPY_COBDPN71,                   \n                                             VCOPY_COBDPN71_LENGTHS,           \n                                             VCOPY_COBDPN71_VALUES,            \n                                             VCOPY_MOVE );                     \n  \n  0001      113   1  0        IF VCOPY_COBDPN71_EIBAID    = 'PF03' THEN        \n \nYou can follow the execution order of the program by following the highlighted lines as you advance through the\nprogram trace. In effect, using PREV and ADVANCE gives you a simulated instant replay of program execution.\nOption 5 Trace Program Execution\nThis option illustrates the use of the PREVIOUS and ADVANCE commands to help you trace program execution.\nNOTE\nBefore proceeding, be sure you have completed the steps outlined in Advanced Demo Preliminaries and you\nhave the Demo Session Options Menu displayed on your screen.\nFollow these steps:\n1.Select option 5 and press Enter.\nCAMRPLI displays the screen that describes what occurs in this part of the demo session.\n2.Press Enter.The application halts CAMRPLI at an unconditional breakpoint that you included at the beginning of the\ndemo. The following sample screen shows CAMRPLI at an unconditional breakpoint:\n CAMRPLI  ---------- CA InterTest Batch UNCOND BEFORE Intercept ---------------\n COMMAND ===>                                                  SCROLL ===> CUR", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ffe7dd4502b1-1", "text": "COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000168 000118 000117 000116 000115 000114 000113 000112 000111 000110\n 0\n  \n U0001      168   1  0     PAY_CALC: PROC ( I );                               \n  \n            169   2  0        DCL I                        PIC '999';          \n            170   2  0        DCL J                        FIXED BIN(15);      \n  \n  \n  0001      171   2  0        DO J = 1 TO I BY 1;                              \n  0005      172   2  1           CALL POPULATE_GRAPH ( J );                    \n  0005      173   2  1           END;                                          \n  \n                           /* CHEQUE_LINE                 = ' ';             */\n  0001      174   2  0        CHEQUE_AMOUNT               = TOTALGROSS;        \n  0001      175   2  0        RETURN;                                          \n  \n  --->      176   2  0     END PAY_CALC;                                       \n  \n  0005      177   1  0     POPULATE_GRAPH: PROC ( I );                         \n  \n 626", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "00263b3fd91c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n            178   2  0        DCL   I                      FIXED BIN(15);      \n            179   2  0        DCL 1 MONTH_THING            STATIC,             \n \nSuppose you want to trace the execution path of the program prior to this point. You can have the application scroll back\nand display a previously executed statement using the PREV command. The PREV  command lets you view previously\nexecuted statements, but does not cause any statements to execute. After you scroll back using the PREV command, you\ncan scroll forward and retrace execution using the ADVANCE command. You may specify a number from 1 to 999 with the\nPREV and ADVANCE commands to scroll more than one statement at a time.\nThe PREV and ADVANCE commands do not change the statement where CAMRPLI resumes execution; the PREV and\nADVANCE only scroll the statements in the trace.\nFollow these steps:\n1.Type the PREV 9 command in the Command field and press Enter.\nThe application displays the ninth previous statement executed. The following screen shows the ninth previous\nstatement:\n CAMRPLI  ---------- CA InterTest Batch UNCOND BEFORE Intercept ---------------\n COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000168 000118 000117 000116 000115 000114 000113 000112 000111 000110\n 0\n  \n  0001      110   1  0     DEMONSTRATE_PREV_COMMAND:                           \n  \n                              CALL ISPLINK ( DSPLY,                            \n                                             COBDPN75 );                       \n  \n                           /*------------------------------------------------*/\n                           /* THIS SECTION OF THE DEMO SHOWS YOU             */\n                           /* THE BENEFITS OF USING THE PREV                 */", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "00263b3fd91c-1", "text": "/* THE BENEFITS OF USING THE PREV                 */\n                           /* AND ADVANCE COMMANDS.                          */\n                           /*------------------------------------------------*/\n  \n  0001      111   1  0        COBDPN71_LENGTHS            = 4;                 \n  \n  0001      112   1  0        CALL ISPLINK ( VCOPY,                            \n                                             VCOPY_COBDPN71,                   \n                                             VCOPY_COBDPN71_LENGTHS,           \n                                             VCOPY_COBDPN71_VALUES,            \n                                             VCOPY_MOVE );                     \n  \n  0001      113   1  0        IF VCOPY_COBDPN71_EIBAID    = 'PF03' THEN        \n \nNow you can retrace the execution of the nine statements using the ADVANCE command. The short form of the\nADVANCE command is A or AD. (You must enter the A on the command line.)\n2.Type the A command and press Enter.\nThe application highlights the next statement executed.\n3.Repeat the Advance step a few more times.The following screen shows advancing through the program trace:\n CAMRPLI  ---------- CA InterTest Batch UNCOND BEFORE Intercept ---------------\n COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000168 000118 000117 000116 000115 000114 000113 000112 000111 000110\n 0\n  \n 627", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "213dac77557e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  0001      110   1  0     DEMONSTRATE_PREV_COMMAND:                           \n  \n                              CALL ISPLINK ( DSPLY,                            \n                                             COBDPN75 );                       \n  \n                           /*------------------------------------------------*/\n                           /* THIS SECTION OF THE DEMO SHOWS YOU             */\n                           /* THE BENEFITS OF USING THE PREV                 */\n                           /* AND ADVANCE COMMANDS.                          */\n                           /*------------------------------------------------*/\n  \n  0001      111   1  0        COBDPN71_LENGTHS            = 4;                 \n  \n  0001      112   1  0        CALL ISPLINK ( VCOPY,                            \n                                             VCOPY_COBDPN71,                   \n                                             VCOPY_COBDPN71_LENGTHS,           \n                                             VCOPY_COBDPN71_VALUES,            \n                                             VCOPY_MOVE );                     \n  \n  0001      113   1  0        IF VCOPY_COBDPN71_EIBAID    = 'PF03' THEN        \n \nYou can follow the execution order of the program by following the highlighted lines as you advance through the\nprogram trace. In effect, using PREV and ADVANCE gives you a simulated instant replay of program execution.\nReturn to the Current Statement\nNow you can return to the current statement, that is, the statement where execution was halted prior to the unconditional\nbreakpoint.\nFollow these steps:\n1.Type the CS command and press Enter.\nThe application displays the original Breakpoint Intercept panel shown in the beginning of this option.\n2.Type the GO command and press Enter.\nCAMRPLI resumes execution and displays the Advanced Options Demo screen. You can continue with any option or\nexit.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "213dac77557e-1", "text": "exit.\nThis concludes Option 5: Trace Program Execution. Select another option and continue with the appropriate section, or\npress PF3 to end the demo.\nOption 6 Work with Indexed Table Items\nThis section of the demo session shows you a fast and easy way to inspect and modify the contents of indexed data\nitems. It also demonstrates how to use the STEP command to single-step execution.\nNOTE\nBefore proceeding, be sure you have completed the steps outlined in Advanced Demo Preliminaries and you\nhave the Demo Session Options Menu displayed on your screen.\nFollow these steps:\n1.Select Option 6 and press Enter.\nCAMRPLI displays a screen that describes what occurs in this part of the demo session.\n2.Press Enter.CAMRPLI resumes execution.\n 628", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1343008cb106-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe next screen you see is an Abend Intercept panel. The application has automatically halted CAMRPLI because it\ndetected a data exception in the highlighted statement.\nThe following screen shows CAMRPLI at an S0C7 Abend Intercept:\n CAMRPLI  ---------- CA InterTest Batch ABEND S0C7 Intercept ------------------\n COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000128 000127 000126 000125 000206 000205 000204 000203 000202 000201\n 0\n  \n  0001      128   1  0        DISTRICT ( A1, B1, C1 )     =                    \n                                 DISTRICT ( A1, B1, C1 ) + 1;                  \n           -----------------------------------------------------------------   \n           |        THE FOLLOWING AUTOMATIC BREAKPOINT OCCURRED:           |   \n  --->     |   INTERCEPT IN PROGRAM CAMRPLI  AT #000128 REASON: ABEND S0C7 |   \n           |        PRESS ENTER TO REMOVE THIS MESSAGE.                    |   \n           -----------------------------------------------------------------   \n                           /* THIS SECTION OF THE DEMO SHOWS YOU HOW TO      */\n                           /* INSPECT AND CHANGE THE VALUE OF SUBSCRIPTED    */\n                           /* TABLE ITEMS.                                   */\n                           /*------------------------------------------------*/\n  \n  0001      130   1  0     DEMONSTRATE_LOOP_DETECTION:                         \n  \n                           /*------------------------------------------------*/\n                           /* THIS SECTION OF THE DEMO SHOWS YOU HOW TO      */\n                           /* INTERRUPT A LOOPING PROGRAM AND CHANGE THE     */\n                           /* EXECUTION LOGIC  _ WITHOUT RE_COMPILATION.     */\n                           /*------------------------------------------------*/", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1343008cb106-1", "text": "/*------------------------------------------------*/\n \nIf you recall, this is the same type of error detected and corrected in the basic demo session. To continue execution, you\nneed to find the data item causing the S0C7 ABEND and dynamically modify it.\nLooking at the highlighted breakpoint statement, you might suspect the variable is at fault; it probably was not initialized\ncorrectly. The variable in this case is an indexed table entry.\nPress Enter to remove the ABEND message box.The ABEND message box is removed.\nDisplay an Indexed Table Entry\nYou can quickly inspect the value of the DISTRICT ( A1, B1, C1 ) field directly from this screen by typing K to the left of the\nhighlighted statement.\nTab to the highlighted statement and type K (for keep).\nPress Enter.\nThe application displays the current value of DISTRICT. It also displays the value of each subscript item, because the k\nline command requests a display of each item on that line.\nThe following panel displays a Keep Window for the Table Entry:\n CAMRPLI  ---------- CA InterTest Batch ABEND S0C7 Intercept ------------------\n COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000128 000127 000126 000125 000206 000205 000204 000203 000202 000201\n 0\n  \n -------------------------------------------------------------------------\n 629", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0687989e8115-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n       1F1A8531 NP-S  000037 04 DISTRICT                     ?000.            \n                                   A1  (+1)                                   \n                                   B1  (+3)                                   \n                                   C1  (+5)                                   \n  \n -------------------------------------------------------------------------\n  \n  0001      128   1  0        DISTRICT ( A1, B1, C1 )     =                    \n                                 DISTRICT ( A1, B1, C1 ) + 1;                  \n  \n                           /* TASK_STRUCTURE.TASK_TEXT    = ' ';             */\n  --->      129   1  0        GO TO OPTIONS;                                   \n  \n                           /*------------------------------------------------*/\n                           /* THIS SECTION OF THE DEMO SHOWS YOU HOW TO      */\n                           /* INSPECT AND CHANGE THE VALUE OF SUBSCRIPTED    */\n                           /* TABLE ITEMS.                                   */\n                           /*------------------------------------------------*/\n  \n  0001      130   1  0     DEMONSTRATE_LOOP_DETECTION:    \n  \n \nThe question mark that precedes the value of DISTRICT in the keep window tells us this field does not contain a valid\nvalue. This is the error that triggered the automatic breakpoint.\nThe keep window also tells us which table entry is at fault. The values of each subscript item in this window indicate the\ninvalid data occurs at\nelement (1, 3, 5).\nDynamically Correct an Uninitialized Table Item\nTo dynamically correct this error you need to modify main storage so the field contains valid data. You can use the SET\ncommand to set the value to zero. The application sets the variable using the proper format.\nType the following command: set district (a1,b1,c1) = zero\nPress Enter.\nThe following panel corrects the uninitialized Table Item:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0687989e8115-1", "text": "Press Enter.\nThe following panel corrects the uninitialized Table Item:\n CAMRPLI  ---------- CA InterTest Batch ABEND S0C7 Intercept ------------------\n COMMAND ===> set district (a1,b1,c1) = zero                   SCROLL ===> CUR\n TRACE=> 000128 000127 000126 000125 000206 000205 000204 000203 000202 000201\n 0\n  \n -------------------------------------------------------------------------\n       1F1A8531 NP-S  000037 04 DISTRICT                     ?000.            \n                                   A1  (+1)                                   \n                                   B1  (+3)                                   \n                                   C1  (+5)                                   \n  \n -------------------------------------------------------------------------\n  \n  0001      128   1  0        DISTRICT ( A1, B1, C1 )     =                    \n                                 DISTRICT ( A1, B1, C1 ) + 1;                  \n 630", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "081b87834a58-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  \n                           /* TASK_STRUCTURE.TASK_TEXT    = ' ';             */\n  --->      129   1  0        GO TO OPTIONS;                                   \n  \n                           /*------------------------------------------------*/\n                           /* THIS SECTION OF THE DEMO SHOWS YOU HOW TO      */\n                           /* INSPECT AND CHANGE THE VALUE OF SUBSCRIPTED    */\n                           /* TABLE ITEMS.                                   */\n                           /*------------------------------------------------*/\n  \n  0001      130   1  0     DEMONSTRATE_LOOP_DETECTION:    \n \nThe application dynamically modifies the value in main storage for DISTRICT ( A1, B1, C1 ), and displays the new value in\nthe keep window. The message on the top right of the panel reads: SET COMPLETE.\nSingle-Step Execution\nUse the step command to execute just one line of code. The step command lets you determine how many lines are\nexecuted when you use the go command. For example, to execute 1 line at a time, or single-step, use the command: step\n1.\nFollow these steps:\n1.Type the STEP 1 command and press Enter.\nThe application sets the step count to 1 and displays the following message: STEP COUNT SET. The following panel\nshows setting the step count:\n CAMRPLI  ---------- CA InterTest Batch ABEND S0C7 Intercept ---- STEP COUNT SET\n COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000128 000127 000126 000125 000206 000205 000204 000203 000202 000201\n 0\n  \n -------------------------------------------------------------------------\n       1F1A8531 NP-S  000037 04 DISTRICT                     +000.            \n                                   A1  (+1)                                   \n                                   B1  (+3)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "081b87834a58-1", "text": "A1  (+1)                                   \n                                   B1  (+3)                                   \n                                   C1  (+5)                                   \n  \n -------------------------------------------------------------------------\n  \n  0001      128   1  0        DISTRICT ( A1, B1, C1 )     =                    \n                                 DISTRICT ( A1, B1, C1 ) + 1;                  \n  \n                           /* TASK_STRUCTURE.TASK_TEXT    = ' ';             */\n  --->      129   1  0        GO TO OPTIONS;                                   \n  \n                           /*------------------------------------------------*/\n                           /* THIS SECTION OF THE DEMO SHOWS YOU HOW TO      */\n                           /* INSPECT AND CHANGE THE VALUE OF SUBSCRIPTED    */\n                           /* TABLE ITEMS.                                   */\n                           /*------------------------------------------------*/\n  \n  0001      130   1  0     DEMONSTRATE_LOOP_DETECTION:                         \n \n 631", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "db35cbd7349c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n2.Execute CAMRPLI by entering the command: GO and pressing Enter.The statement that increments the DISTRICT\ntable item is executed, and then the application halts execution and displays a Step Count Intercept panel. Statement\n129 is now the current line, and is highlighted.\nRemove the Step Count and Keep Window\nWhen you want to end single-stepping, reset the step count to zero. This turns single stepping off. Remove the step count\nand keep window before continuing execution.\nFollow these steps:\n1.Type the following command and press Enter: STEP 0; REMOVE ALL.\nThe application resets the step count and removes the keep window.\n2.To display the current status of the step count, enter the step command without any count number. Type the STEP\ncommand and press Enter.\nThe application displays the value of the step count in the top-right corner; in this case, the message is: NO STEP\nCOUNT SET.\n3.Resume execution of CAMRPLI by entering GO.CAMRPLI resumes execution, and you return to the Options Menu.\nThis concludes Option 6: Work with Indexed Table Items. Select another option and continue with the appropriate section,\nor press PF3 to end the demo.\nOption 7 Histogram Report\nThis option illustrates how to create and view the histogram report of statement execution, which is useful in identifying\ndead code.\nNOTE\nBefore proceeding, be sure you have completed the steps outlined in Advanced Demo Preliminaries and you\nhave the Demo Session Options Menu displayed on your screen.\nFollow these steps:\n1.Select option 7 and press Enter.\nCAMRPLI displays the screen that describes what occurs in this part of the demo session.\n2.Press Enter.The application halts CAMRPLI at an unconditional breakpoint set at the program exit. The following", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "db35cbd7349c-1", "text": "screen shows the breakpoint intercept at label RETURN_TO_OPSYS:\n CAMRPLI  ---------- CA InterTest Batch UNCOND BEFORE Intercept ---------------\n COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000058 000142 000235 000234 000233 000239 000237 000232 000231 000239\n 0\n  \n U--->       58   1  0     RETURN_TO_OPSYS:                                    \n  \n                              RELEASE ISPLINK;                                 \n  --->       59   1  0        CLOSE FILE ( REPORT );                           \n  --->       60   1  0        RETCODE = DM_RC;                                 \n  --->       61   1  0        CALL PLIRETC ( RETCODE );                        \n  --->       62   1  0        RETURN;                                          \n  \n  0001       63   1  0     OPTIONS_MENU:                                       \n  \n                           /*------------------------------------------------*/\n                           /* INITIALIZE THE LENGTHS IN CASE OF RECURSION.   */\n                           /*------------------------------------------------*/\n  \n  \n 632", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5e4ccc7f774c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n       5688-235 IBM PL/I for MVS & VM          CAMRPLI: PROC OPTIONS (MAIN);   \n           STMT LEV NT                                                         \n                              CALL ISPLINK ( DSPLY,                            \n                                             PLIDPN70 );                       \n  \n  0001       64   1  0        OPTION_I                    = 1;  \n \nPrior to exiting the program, you can request a histogram report using the HIST command.\n3.Type the HIST command and press Enter.\nThe application returns the following message: 'HISTOGRAM SUCCESSFULLY WRITTEN'\nView the Histogram Report\nThe report is written to the data set associated with the ddname INT1REPT that can be viewed by splitting the screen.\nFollow these steps:\n1.Tab a few lines down your screen and press the SPLIT PF key defined in your ISPF profile (normally PF2).The ISPF\nMain Menu is displayed in the split-screen area.\n2.Select the ISPF Browse Facility and request a display of the data set associated with the ddname INT1REPT. You\nallocated this data set in Advanced Demo Preliminaries. The suggested data set name was: userid.INT1REPT\nNOTE\nIn the following example, the report is viewed in SDSF.\nThe first page of the histogram report displays. A sample report is shown in the following panel. The following screen\nshows Browsing the Histogram DD in SDSF:\n CAMRPLI  ---------- CA InterTest Batch UNCOND BEFORE Intercept ---------------\n  COMMAND ===>                                                  SCROLL ===> CSR\n  TRACE=> 000058 000142 000235 000234 000233 000239 000237 000232 000231 000239", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5e4ccc7f774c-1", "text": "U--->       58   1  0     RETURN_TO_OPSYS:                                    \n  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . \n  SYSVIEW 11.5 CA11 ----------------- Output ----------------- 05/02/14\n 18:01:17\n  Command ====>                                                 Scroll *===>\n CSR\n  -------------------------------------------------- Lvl 4 Row 1-35 Col\n 1-80/115\n  USER001  TSU   27743  DDname - INT1REPT  Stepname - CATSO     Procstep -\n CATSO\n  \n ------------------------------------------------------------------------------\n  \n ...+....10...+....20...+....30...+....40...+....50...+....60...+....70...+....\n CA InterTest/Batch       Execution Histogram For Program-ID: CAMRPLI     \n Date:\n  \n 000001 0001 |*                                                                 \n 000042 0001 |*                                                                 \n 000043 0001 |*                                                                 \n 000044 0001 |*                                                                 \n 000045 0001 |*                                                                 \n 000046 0001 |*                                                                 \n 633", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4934460053b0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 000047 0001 |*                                                                 \n 000048 0001 |*                                                                 \n 000049 0001 |*                                                                 \n 000050 ---- |                                                                  \n 000051 ---- |                                                                  \n \n3.Page down to the end of the report using the maximum command with PF8\n4.Type the M command and press PF8.\nThe last page of the histogram report displays, as shown in the following panel. The following screen shows the last\npage of the histogram report:\n CAMRPLI  ---------- CA InterTest Batch UNCOND BEFORE Intercept ---------------\n  COMMAND ===>                                                  SCROLL ===> CSR\n  TRACE=> 000058 000142 000235 000234 000233 000239 000237 000232 000231 000239\n  \n  U--->       58   1  0     RETURN_TO_OPSYS:                                    \n  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . \n  SYSVIEW 11.5 CA11 ----------------- Output ----------------- 05/02/14 18:06:44\n  Command ====>                                                 Scroll *===>CSR\n  GSVX006I End of data ---------------------- Lvl 4 Row 165-195/195 Col1-80/115\n  RYARO02  TSU   27743  DDname - INT1REPT  Stepname - CATSO     Procstep -CATSO\n  \n ------------------------------------------------------------------------------\n  \n ...+....10...+....20...+....30...+....40...+....50...+....60...+....70...+....", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4934460053b0-1", "text": "000234 0017 |*                                                                 \n 000235 0001 |*                                                                 \n 000236 ---- |                                                                  \n 000237 0034 |*                                                                 \n 000239 0034 |*                                                                 \n 000240 ---- |                                                                  \n 000241 ---- |                                                                  \n 000242 ---- |                                                                  \n             ----+----|----+----|----+----|----+----|----+----|----+----|----+-\n             *NOTE* ASTERISKS REPRESENT A SCALE OF 00000130 EXECUTION(S) PERAST\n CA InterTest/Batch       Execution Histogram For Program-ID: CAMRPLI     Date:\n Session Number: 54   For Userid RYARO02                                        \n Number of executable statements: 174                                           \n Number of statements executed during this test: 147                            \n Percentage of statements executed during this test: 84                         \n \nIn the previous panel, you can see that a number of lines were never executed. Check to see if these lines in the\nprogram are dead code and should be removed.\nNOTE\nIn our example, there is unexecuted code starting at line 240. Note the corresponding line number in your\nprogram that is unexecuted.\n5.Remove your split-screen using the command: XYou return to a full-screen display of the Program Exit Intercept\nshown in the beginning of this option.\n6.Use the Find Statement (FS) command to display the code that was never executed. Type the following command and\npress Enter: FS 240\nThe application displays the requested line of code.\nThe following screen displays the unexecuted code:\n 634", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "41cece0e57de-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n CAMRPLI  ---------- CA InterTest Batch UNCOND BEFORE Intercept ---------------\n COMMAND ===>                                                  SCROLL ===> CUR\n TRACE=> 000058 000142 000235 000234 000233 000239 000237 000232 000231 000239 0\n                                 RETURN ( I + 1 );                             \n  --->      240   2  0        ELSE                                             \n                                 RETURN ( I );                                 \n  \n  --->      241   2  0     END INCREMENT;                                      \n  \n  --->      242   1  0  END CAMRPLI;                                           \n  \n       5688-235 IBM PL/I for MVS & VM          CAMRPLI: PROC OPTIONS (MAIN);   \n                                                              ATTRIBUTE AND CROS\n       DCL NO.    IDENTIFIER                      ATTRIBUTES AND REFERENCES    \n  \n       3          ASA_CNTL                        /* IN LINE_OUT */ AUTOMATIC UN\n       5          A1                              AUTOMATIC ALIGNED BINARY FIXED\n                                                  125,128,128                  \n       18         BALANCE_LINE                    /* IN BALANCE_OUT */ AUTOMATIC\n       18         BALANCE_OUT                     AUTOMATIC /* STRUCTURE */    \n       17         BALANCE_REPORT                  AUTOMATIC /* STRUCTURE */    \n       188        BILL_CALC                       ENTRY RETURNS(DECIMAL /* SINGL\n                                                  102                          \n       101        BILL_YTD                        /* IN BILLING_VALUES */ AUTOMA\n \nBy reviewing the code, you can determine whether or not it is required. In this case, it is required for the program and\nshould be retained.\nIf unexecuted code needs to be removed from your own programs, you can split the screen again and make the code\nchanges, or wait until you complete the review of the histogram report.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "41cece0e57de-1", "text": "changes, or wait until you complete the review of the histogram report.\nNow return to the current statement in the CAMRPLI program.\nFollow these steps:\n1.Type the CS command and press Enter.\nThe application displays the Program Exit Intercept panel.\n2.To continue the advanced demo, enter the command go options and press Enter. To end the demo, enter the GO\ncommand.\nIf you are continuing the demo, CAMRPLI program execution continues with the display of the Advanced Options\nMenu. Choose another option from the menu.\nIf you are exiting the demo, CAMRPLI resumes execution at the normal program exit, and terminates. You return to\nthe Execution Control panel of the Foreground Option. Your previous entries are displayed, allowing you to begin\ntesting again, or exit. Use PF3 to exit.\nQuick References\nThis section contains the quick reference for InterTest for CICS and InterTest Batch.\nClick the file to view it, or use the right-click menu to save or to print the file.\nInterTest Batch Quick Reference\nInterTest for CICS Quick Reference for Assembler, COBOL, and PL/I Users\n 635", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "098aa02ab589-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterTest for CICS Quick Reference for All Users\n 636", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b4ff9b57879b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUsing\nUse InterTest and SymDump for debugging capabilities and fault management\nInterTest\nUse the InterTest debugging capabilities to quickly and easily identify and correct errors in:\n\u2022Batch and IBM \u00ae CICS \u00ae COBOL\n\u2022Assembler and PL/I programs\n\u2022IBM IMS/DC applications\n\u2022IBM DB2 stored procedures\nSymDump\nUse the SymDump fault management tool for IBM z/OS systems to provide critical, comprehensive ABnormal ENDing\n(ABEND) information for test and production environments.\nUsing Batch Tools\nUse the InterTest Batch tool for comprehensive, interactive testing and debugging.\nInterTest Batch is a comprehensive interactive tool for testing and debugging batch, DB2 stored procedures, and IMS/\nDC applications through a TSO/ISPF or Roscoe  Interactive Environment ( Roscoe ) interface. Instead of using dumps\nand reports, programmers use interactive, online facilities with the actual source listing for debugging to resolve multiple\nerrors in a single test session. The application intercepts all application abend conditions, and identifies the source code\nstatement that caused each error. Interactive debugging functions include the ability to:\n\u2022Set breakpoints\n\u2022Trace program execution\n\u2022Place data items in a keep window on the source listing screen\n\u2022Examine and modify the values of data items\n\u2022Find a data string in working storage\nA user-friendly, menu-driven allocation and JCL conversion facility simplifies the task of allocating program files for\nforeground execution, or preparing JCL for batch execution.\nSymDump  Batch provides abend diagnostic information for batch abends in test and production environments. Its\nformatted reports make it easy for programmers to resolve abends without having to decipher system dumps. SymDump\nBatch supports all languages, with special symbolic support for COBOL, PL/I, and Assembler. Batch also includes detailed", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b4ff9b57879b-1", "text": "database information for abending IMS, DB2, and IDMS/DB  applications. SymDump  Batch is automatically available to\nevery user once installed.\nCommand Syntax\nThe following notation conventions are used throughout the documentation to illustrate application commands:\n\u2022Uppercase letters and special characters are displayed as usual.\n\u2022Lowercase italic letters indicate the generic description of the value of a variable parameter.\n\u2022Brackets (< >) enclose optional values.\n\u2022Vertical bars (|) separate alternatives.\n\u2022Ellipses (...) specify that a parameter can be repeated.\n\u2022Default values are underlined.\n 637", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8cbb57d6bf86-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBatch Debugging\nThis section describes how to use InterTest Batch to test a program using application batch commands and panels.\nThe application is supported with HELP panels and an online tutorial which describe the application options and\ncommands. You can use this product to test the following programs:\n\u2022Assembler programs that are assembled with Assembler F, Assembler H, or the High Level Assembler\n\u2022COBOL programs that are compiled with any COBOL compiler that is supported by IBM\n\u2022PL/I programs that are compiled with any PL/I compiler that is supported by IBM\nThe application gives programmers complete access to the program as it is executing. You can stop the program and the\nIntercept panel that is displayed at user-specified intercept points. From the Intercept panel, you can browse the program\nlisting in full-screen mode, using program function keys (PFKs) to scroll backward or forward through the program. You\ncan examine and repair problem areas without ending the test session, or issue commands to set new intercept points\nand resume testing. Each application panel is supported with a HELP panel. An online tutorial describes the product\nsystem.\nDuring a test session, you can perform the following actions:\n\u2022Stop the test at any executable statement in the program.\n\u2022View the program listing while the test session is stopped.\n\u2022Trace the program execution and browse the trace table entries.\n\u2022Display and alter data-item values.\n\u2022Step through the program in increments of any number of statements.\n\u2022Identify the number of times each statement in the program is executed.\n\u2022Step through the program execution in reverse order.\n\u2022Access the other options such as Core.\nThe application runs under IBM ISPF and Roscoe  Interactive Environment ( Roscoe ) under ETSO. Programmers familiar\nwith these environments need little or no training to use this product.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8cbb57d6bf86-1", "text": "with these environments need little or no training to use this product.\nDuring a test session using the ISPF dialog manager, programmers can use the following features to test efficiently:\n\u2022Split the screen to access other ISPF options, such as EDIT.\n\u2022Print to the ISPF listing data set.\n\u2022Enter ISPF or TSO commands from any panel.\nDuring a test session using Roscoe , programmers can perform the following features:\n\u2022Split the screen to perform other InterTest Batch or Roscoe  functions.\n\u2022Suspend the application session to perform other Roscoe  functions.\n\u2022Print to an application data set, which can be allocated to the AWS or any MVS data set.\n\u2022Use the Roscoe  print facility.\nDebug Optimized Applications\nYou can use InterTest Batch to debug programs that were optimized by the COBOL compiler OPTIMIZE option or by\nOptimizer/II  or Optimizer/II . However, debugging these programs can result in unexpected behavior.\nDuring optimization, a compiler often relocates individual instructions, statements, or even entire paragraphs. If\ninstructions are moved to another statement, or if statements in a paragraph are moved to another paragraph, the\nresulting object program and listing might not accurately represent:\n\u2022The relationship between the source statements and their generated object code\n\u2022Or the relationship between a paragraph label and the statements contained within the paragraph.\n 638", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "883472068f2a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAs a result, the breakpoint intercept might not occur, or the wrong sequence of statements appears to be executed while\nsingle-stepping. Also, the debugger might appear to highlight the wrong statement at a breakpoint intercept.\nThese unexpected displays do not indicate that a program is being executed incorrectly. These displays indicate that the\ndebugger cannot accurately identify exactly which object code corresponds to which source statement, or which statement\nis contained within which paragraph.\nThe application uses the information in the compiler-generated procedure map or offset report to establish the program\noffset for each statement and label in the program. During execution, the debugger recognizes the start of the new\nstatement or label by matching the program offset of the currently executing instruction with the PROTSYM information\nobtained from the compiler listing. Inaccuracies can include the following instances:\n\u2022Incorrect execution when using the SKIP, GO stmt# or CS stmt# commands\n\u2022Failure to stop at a breakpoint at a paragraph label or statement\n\u2022Unexpected or out of sequence highlighting of statements when single-stepping\nApplication abends can result from the use of the SKIP, GO stmt#, or CS stmt# commands because the optimized object\ncode might have register requirements that do not support changes to the flow of control. Avoid these commands when\ndebugging an optimized program.\nFor the best debugging results, avoid using optimization in your testing environment when possible.\nNOTE\nFor more information about debugging optimized COBOL and the OPTIMIZE option, see COBOL OPTIMIZE\nCompiler Option .\nCOBOL Statement Numbers\nSome commands require a statement number in the command syntax. For COBOL programs, these statement numbers\nare generated by the COBOL compiler. The compiler-generated statement numbers are the ones farthest to the left in the\ncompilation listings and in application displays. Use these numbers in all commands that require a statement number.\nAssembler Offsets", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "883472068f2a-1", "text": "Assembler Offsets\nUse the statement number in an Assembler program to set breakpoints, as in COBOL programs, or by using the offset.\nWhen using an offset, you must prefix the offset with the + sign.\nFor example, enter AT +78 in the Command area of the Intercept panel to set a breakpoint at offset 78. You can also enter\nS in the Option field and +78 in the Statement field on the Breakpoint panel.\nPanels and Functions\nThis article describes how panels are displayed, the available options, and product documentation syntax.\nPanel Display Formats\nThe application uses full screen displays to prompt you for option selection and data entry, and to display source data,\nlistings, and other information.\nThe first two lines are the header lines; they have a common format for all displays.\nLine one of the application panel contains the panel title and short message area. The title line identifies the reason for\nthe panel being displayed, and, where appropriate, data set information. The short message area displays the following\ninformation:\n 639", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e0aa1a98bae2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Current line number (in BROWSE)\n\u2022Notice of successful completion of a processing function\n\u2022Notice of an error condition (accompanied by an audible alarm, if one is installed on the terminal)\n\u2022A frequency count in response to an Info line command\nLine two, the prompt or input area, is used to enter an option, selection, or command.\nThe remainder of the screen contains a list of options, input fields and prompts, or scrollable data. You can scroll in\nany application panel containing a SCROLL field in line two. The application recognizes PAGE (P), HALF (H), MAX\n(M), or four numeric digits. The default is PAGE. Enter a numeric value in the SCROLL field to control the number\nof lines scrolled when you press the SCROLL key.\nA scroll field value of cursor (CSR) is supported under InterTest Batch ISPF and Roscoe .\nThe application does not display ISPF long messages.\nProgram Access Keys\nFor ISPF users, the application uses the PF keys as set from the ISPF option. For Roscoe  users, the application uses the\nPF keys as set from the InterTest Batch Primary Option Menu.\nProgram Access Keys\nThe program access keys are defined as follows:\nATTENTION (PA1)\nInterrupts the program that is currently executing and displays the ATTENTION INTERCEPT panel at the next\nexecutable statement in a monitored program. If the program is in a loop, you might need to press RESET before\npressing PA1.\nNOTE\nThe ATTENTION key can be either the PA1 key or the ATTN key, depending on the terminal type and\nhow it is attached to the system.\nRESHOW (PA2)\nRedisplays the contents of the screen. Use this key if, for example, the CLEAR key was pressed accidentally.\nPrimary Option Menu", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e0aa1a98bae2-1", "text": "Primary Option Menu\nThe following list shows the features available from the Primary Option Menu. Availability of individual options depends on\nwhether you are using ISPF or Roscoe .\nOption 1\nForeground\nUse this option to set up and control a test execution of a program.\nOption 2\nCore\nUse this option to display virtual memory in hexadecimal and character format. Use SCROLL keys and\ncommands to locate and find data in virtual storage.\nOption 3\nAllocation\nISPF users can select this option to allocate ddnames and allow conversion of JCL into a CLIST or ALIB.\nOption 4\nMap\nThis option provides several address space-related displays that are most often used to debug complex system-\nrelated problems.\n 640", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e73b61676b7b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nOption 5\nBatch\nUse this option to set up and test a program to be executed in Batch.\nOption K\nKeys\nUse this option to set up and control a test execution of a program.\nOption K\nKeys\nRoscoe  users can set their PF keys for InterTest Batch. Type over the default assignments on the PF Key\nDefinition panel and press Enter to change the PF keys. The default key assignments are as follows:\nPF1\nHelp\nPF2\nSplit\nPF3\nEnd\nPF4\nReturn\nPF5\nFind\nPF6\nGo\nPF7\nUp\nPF8\nDown\nPF9\nSwap\nPF10\nLeft\nPF11\nRight\nPF12\nPrint\nValid PF key commands are HELP, SPLIT, END, RETURN, FIND, GO, UP, DOWN, SWAP, LEFT, RIGHT, and\nPRINT.\nOption U\nUtilities\nUse this option to display and update the contents of your PROTSYM file. You can also define which programs to\nexclude from auto-monitoring.\nOption X\nExit\nUse this option to terminate the application. The ISPF End key (typically PF3) or Roscoe  End Key (typically PF4)\nalso terminate the application from the Main Menu.\n 641", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b1292e68a827-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nISPF-HelpHelp\nDisplay the Tutorial Table of Contents from the Primary Option Menu. The tutorial summarizes the features and\ncommands. You can page through the tutorial or select a subject from the Tutorial Table of Contents.\nThe Primary Option Menu for Roscoe  users is displayed when you select the InterTest Batch Option on the Roscoe  menu,\nor when you enter the following commands, where xxx is the prefix of the library where the application is installed. Omit\nthis prefix if the application is installed in a common execution library.\n [xxx.]IBALLOC\n [xxx.]IBRUN\n \nDebugging Panels\nForeground, Option 1 on the Primary Option Menu, includes the following panels:\n\u2022Panels to identify the programs to be tested, and their associated symbolic files\n\u2022A panel to view the program listing and control the test execution\n\u2022Panels to display and alter program storage\n\u2022Panels to display trace, file, and other related information\nIn addition, novice users can gain online experience with the application by performing the basic demonstration sessions\ncontained in the sections.\nOverview of Test Panels\nThe testing process begins by selecting Option 1, Foreground, on the main menu. The first two panels are called the\nExecution Control panel and the Monitor Control panel. Once you enter data on the Execution Control and Monitor Control\npanels, execution of the test program begins.\nThe following list describes a list of test-related panels:\nBreakpoint Control\nThat panel allows you to set breakpoints (places where the application should interrupt) by statement number or\nparagraph name.\nBreakpoint Display\nThis panel lists the breakpoints set by statement numbers or paragraph names.\nWhen Control\nThis panel allows you to set breakpoints based on variable contents or when a variable changes.\nWhen Condition Display", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b1292e68a827-1", "text": "When Condition Display\nThis panel displays the when conditions set by the line mode COND command, or by the When Control panel.\nEquate\nThis panel allows data items to be equated to symbolic names. You can then refer to the variable using the data\nitem or the symbolic name.\nEquate Display\nThis panel displays the equate set by the line mode EQUATE command or by the Equate panel\nData Display\nThis panel shows a formatted display of program data.\nLinkage Display\nThis panel shows a formatted display of the LINKAGE SECTION in COBOL format. This display is only available\nfor COBOL programs.\n 642", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e14a73758af2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nRecords Display\nThis panel shows a formatted display of the records that are defined under the FILE SECTION in COBOL format.\nThis display is only available for COBOL programs.\nFile Status Panel\nThis panel shows the allocation for each FILE DESCRIPTION by ddname and dsname, and the DCB information\nwhether the file is open or closed. If the file is open, it indicates for INPUT, OUTPUT or INOUT. This display is only\navailable for COBOL programs.\nProgram Trace Display\nThis panel displays program statements in the order of their execution.\nDebug Session Display\nThis panel displays a list of saved debug sessions that are stored in the INT1CLIB file. These sessions can be\ndisplayed, maintained, and loaded into an active debugging session. Use the MLOG command to launch this\nscreen.\nTo access the other options during the test session, use the split-screen feature and select another option from the\nPrimary Option Menu.\nExecution Control Panel\nUse the Execution Control panel to specify the main program, execution parameters, and allocations required to run the\napplication.\nAllocations Fields\nUse the ALIB Dsname and Member fields to specify which existing ALIB member to use to perform the necessary\nallocations, specify the parameters to be passed to the main program, or to identify the main program.\nIf the ALIB contains multiple job steps, indicate which job step to use in the EXEC Job Step and Proc Step fields.\nSpecifying an ALIB is not required.\nExecution Overrides\nUse the Execution Overrides fields to override any fields that were obtained through the ALIB, if any were specified. The\nfields are as follows:\nPGM\nIndicates and overrides the main program to execute in this debug session.\nPARM\nSpecifies and overrides the execution parameter to pass to the main program.\nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e14a73758af2-1", "text": "PARM\nSpecifies and overrides the execution parameter to pass to the main program.\nNOTE\nPARM is mutually exclusive with the Number of Linkage Parameters field.\nNumber of Linkage Parameters\nSpecifies the number of linkage parameters expected by the main program when there is more than one. (For\na COBOL program, this number is equivalent to the number of Linkage Section data items defined on the\nPROCEDURE DIVISION USING statement.) You can initialize and update the parameter values using the SET\nand LINKAGE commands. It also allows you to debug a subprogram as a main program.\nTask Libraries\nSpecifies and overrides the STEPLIB (or JOBLIB if one was specified in the ALIB) required to execute the\napplication. Type the fully qualified data set name in quotes or indicate an allocated ddname in parentheses.\n 643", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5ae49264eaf6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nFor customers with multiple Endevor  C1DEFLTS:\nIf you want to use the dynamic symbolic support feature and you have chosen to run the debugging session as\nif you have a single C1DEFLTS (for example, if you have not defined your Endevor  site IDs in IN25SITE table),\ndefine the fully qualified data set name that contains the C1DEFLTS with your site ID in the Task Libraries fields.\nInitial Commands\nSpecifies a member in your INT1CLIB DD that includes commands to execute at the initial intercept.\nMonitor Control Panel\nUse the Monitor Control panel to specify which programs the application monitors during a debugging session.\nYou can define up to 30 programs, but the use of wildcards allows you to define an unlimited number of programs. The\ndata that you enter on this panel remains from session to session until you delete or change the information.\nMonitored Programs\nUse the Monitored Programs section to define the programs that you want to debug. The program name must match the\nname of the PROTSYM member that contains the symbolic information for the program being debugged. You can define\nthe complete name of up to 30 programs. You can specify more than 30 programs using when you use wildcards in the\nprogram name.\nIf you entered a Y in the Monitor PL/I field on the Monitor Control panel, the PL/I Protsym/Load Module Map panel\nappears when you press Enter. Specify the name of the load module in which these programs reside in the Modname field\nto the right of the entry.\nSymbolic Files\nUse the symbolic (PROTSYM) files section to define the files that contain the symbolic information for the programs\nthat you want to debug. A PROTSYM entry must exist for each program that you want to debug. Specify at least one", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5ae49264eaf6-1", "text": "PROTSYM file in this section.\nDynamic Symbolic Support\nDynamic symbolic support dynamically retrieves the compiler or assembler listing of the monitored program from a listing\ndata set managed by Endevor  and loads the listing into the designated PROTSYM file. For this feature to work, the load\nmodule library where the load module is loaded and the listing data set containing the module listing must be under\nEndevor  control.  The load library is specified under Task Libraries on the Execution Control panel.\nThe dynamic symbolic support feature always loads the correct symbolic information whenever a matching symbolic\nversion is not found. To activate the dynamic symbolic support feature, enter Y to the right of the PROTSYM file,\nunderneath the heading Endevor Auto Populate to designate the PROTSYM file as the file to receive the listing. To\ndeactivate the feature, change the  Y to N.\nSymbolic files associated with programs that do not contain a time stamp in the executable, such as non-LE-enabled\nAssembler programs, are reloaded every time that they are monitored. If you want to suppress this behavior, specify N in\nthe Always Auto-Populate Non-LE-Enabled Assembler field.\nNOTE\nThe dynamic symbolic support feature cannot differentiate between multiple listing outputs created by a\nsingle Endevor  processor for the same element. Dynamic symbolic support using listing outputs from multiple\ncompiles or assemblies from a single Endevor  GENERATE or MOVE action for the same element can produce\nunpredictable results.\n 644", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9487edefbdbd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDynamic Symbolic Support Return Codes\nDynamic symbolic support provides an integrated service using API calls that deploy various proven components\nincluding The following:\n\u2022Endevor\n\u2022PROTSYM post processors\n\u2022z/OS dynamic allocation\n\u2022CSVQUERY\n\u2022Binder services\nThe following table provides a list of possible return codes (RC) and reason codes (RSC) the API and various components\ncan return.\nNOTE\nOther numeric return codes and reason codes are also returned by Endevor  and z/OS binder services API\n(IEWBIND).\nFunction RC RSC Meaning\nAPI 0 0 Operations completed\nsuccessfully.\nAPI 2 0 GETMAIN failed.\nAPI 8 0 Endevor  server not activated.\nAPI 12 0 Invalid or missing parameter in\nNDVRCOMM.\nAPI 16 0 Bad return code from Endevor .\nSee Endevor  documentation.\nAPI 20 0 Data set open failed.\nAPI 28 0 Allocation error. See IBAPILOG\nfile.\nAPI 32 0 IN25DALC load failed.\nAPI 36 0 ENA$NDVR load failed.\nAPI 40 0 Endevor  footprint not found for\nrequested element.\nAPI 44 0 Requested CSECT not found.\nAPI 30 0 IN25CDRV load failed.\nBINDER 44 0 Requested CSECT not found by\nbinder.\nCSVQ 48 0 CSECT from IDRU does not\nmatch CSECT in NDVR_NAM2.\nEndevor 12 0 Incorrect C1DEFLTS used.\nEndevor 32 15 Endevor  encountered critical\nerror and cannot continue.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9487edefbdbd-1", "text": "Endevor 32 15 Endevor  encountered critical\nerror and cannot continue.\nNDSB 4 0 Compressed footprint in IDRU\ninvalid.\nNIDR 2 0 GETMAIN failed.\nNIDR 32 0 IN25NDSB load failed.\nNSRV 8 NSRV Listing server ABORTed or\nfailed.\n 645", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d20a63a8f1c3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n0000 12 0000 Incorrect C1DEFLTS used.\nIntercept Panel\nThe Intercept panel is the point where execution of the test program is controlled.\nThe Intercept panel has the following attributes:\n\u2022The monitor name of the program that is intercepted is displayed in the upper left corner of the panel.\n\u2022The reason the program has been intercepted is displayed in the title line of the panel (*INITIAL* INTERCEPT).\n\u2022The trace line shows the last 10 statement numbers executed.\n\u2022The program listing that is displayed is scrolled to the current statement and that statement is highlighted.\nNOTE\nEach time a test begins, the application displays an Initial Intercept panel that stops before the first monitored\nexecutable statement is executed. At this point, use breakpoints and control commands before the program is\nexecuted.\nYou can specify the number of times each statement has been executed as shown in the following panel. This function is\ncalled the frequency counter . For more information about the frequency counts, see Control Commands.\nInvoke all other test panels from the Intercept panel. You must return to the Intercept panel before accessing another test\npanel. For example, to format a data item, enter the DIsplay command in the Command field. To return to the Intercept\npanel, press the END key. To resume execution, enter GO in the Command field, use the G line command, or press the\nappropriate PF key. The test continues until the next intercept condition is encountered, an ABEND occurs, or the test\ncomes to the normal end of job.\nTypes of Intercepts\nThe type of intercept that is displayed is shown at the top center of the panel on the title line. The following list describes\nthe possible intercepts.\n*INITIAL* INTERCEPT\nThis intercept is displayed upon entry into the first program that you have asked to monitor. To have the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d20a63a8f1c3-1", "text": "This intercept is displayed upon entry into the first program that you have asked to monitor. To have the\napplication stop upon entry to all programs, enter AT ALL ENTRY on the command line at this intercept.\nUNCOND BEFORE and UNCOND AFTER INTERCEPT\nThis intercept is displayed when the program reaches an executable statement where the application was\ninstructed by the programmer to stop execution.\nABEND INTERCEPT\nThis intercept is displayed when a monitored program ABENDs or an unhandled condition has been raised\nunder LE/370. The ABEND code is shown in the title line. Use application commands to resolve ABENDs. For\nexample, if invalid data is in a data item, use the set command to change the value. Continue the test using the\nGO command.\nATTENTION INTERCEPT\nThis intercept is displayed when a potential breakpoint is reached after the ATTENTION or PA1 key is pressed.\nFor more information on use of the ATTENTION or PA1 key, see the Stopping a Looping Program in Testing\nProcedures. Enter the GO command in the Command field or press the appropriate PF key.\nSTEP BEFORE\nand STEP AFTER INTERCEPT\nThis intercept is displayed when the count parameter in the STEP command is matched. Enter the STEP\ncommand in the Command field of the Intercept panel. For more information about this command format, see\nSTEP Control Command in Debugging Commands.\n 646", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f0268cc27f6b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe STEP command specifies the number of statements to be executed each time the GO command is issued.\nThe STEP COUNT Intercept panel is displayed after each execution.\nNEXT BEFORE\nand NEXT AFTER INTERCEPT\nThis intercept is displayed when the next count (set by the NEXT command) is exceeded. Enter the NEXT\ncommand in the Command field of the Intercept panel. For more information about this command format, see\nthe NEXT Control Command in Debugging Commands. The NEXT command causes the execution of the next\nn statements in the program. The NEXT command operand specifies the number of statements to be executed\nbefore the Next Count Intercept panel is displayed again.\nWHEN\nwhen-name BEFORE ; WHEN when-name  AFTER INTERCEPT\nThis intercept is displayed at a conditional breakpoint. A conditional breakpoint is detected when the conditional\nstatement that is specified in the COND command is true. Enter the COND command in the Command field of\nthe Intercept panel to set conditional breakpoints or to access the When panel. For more information about the\ncommand formats, see Control Commands. Set conditional breakpoints with the line commands C, W, and V.\nLABEL INTERCEPT\nThis intercept is displayed with executing a label when the AT ALL LABEL or AT LABEL breakpoint are set.\nDBCALL INTERCEPT\nThis intercept is displayed when a call is made to a database (Such as DB2 or IMS) when the AT ALL DBCALL or\nAT DBCALL breakpoint are set.\nPGM ENTRY INTERCEPT\nThis intercept is displayed upon entry to a program that you are monitoring when the AT ALL ENTRY or AT\nENTRY breakpoint are set.\nPGM EXIT INTERCEPT\nThis intercept is displayed before exiting a COBOL program that is being monitored when the AT ALL EXIT or AT\nEXIT breakpoint are set.\nBreakpoint Panels\nThis article describes the breakpoint panels that are accessed from Option 1 on the main menu.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f0268cc27f6b-1", "text": "This article describes the breakpoint panels that are accessed from Option 1 on the main menu.\nWhen you use a conditional or unconditional breakpoint command, but do not specify operands, the application displays a\nseries of panels to collect the information that is required to define the breakpoint.\nNOTE\nYou can also set breakpoints by entering a single-character line command on the line where you want the\nbreakpoint. You can set an unlimited number of breakpoints.\nBreakpoint Panel\nUse the Breakpoint panel to set, reset (delete), or list unconditional breakpoints. Access the Breakpoint panel by entering\nthe command UNCOND (or AT) or OFF, without operands, in the Command field of the Intercept panel.\nUse the OPTION field to enter S (set), R (reset), or L (list):\nS\nYou must enter the statement number. The program stops whenever the statement number is encountered,\nunless you enter a count in the COUNT field.\nYou can use the COUNT field to specify the number of times a statement is executed before the program is\nstopped. The program stops at the designated statement before the final increment of the COUNT field. The\ncommands that you specified to be executed at breakpoint are executed when the COUNT limit is satisfied.\n 647", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ab4af2e6bf92-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse the AFTER field to indicate whether to stop the execution before this statement is executed (N), or after the\nstatement is executed (Y).\nR\nDeletes a breakpoint. You must enter the statement number. To delete a breakpoint for another program, enter the\nprogram name.\nL\nDisplays the Breakpoint Status panel. This panel lists all unconditional breakpoints that are currently set in the\nprogram.\nYou can specify application commands to execute at a breakpoint by entering the commands (separated by semicolons)\nin the COMMANDS TO BE EXECUTED AT BREAKPOINT field. The commands execute until the program resumes\nthrough the GO command, or until there is a request for a panel through a command such as DI or AT. The remaining\ncommands are ignored. The list of commands can be up to 73 characters long and should be entered as shown in the\nfollowing example:\n COMMANDS TO BE EXECUTED AT BREAKPOINT:\n ===>SET BINARY-1 = 01;LDI BINARY-1;NEXT 5\n \nIn this example, the following commands are executed when the breakpoint occurs:\n\u2022The value of data item BINARY-1 is set to 1.\n\u2022Data item BINARY-1 is displayed on the Intercept panel in a keep window .\n\u2022Five statements are executed.\nBreakpoint Status Panel\nThe Breakpoint Status panel lists breakpoints that are set in the Breakpoint panel, and by the UNCOND or AT commands\nfor the current program.\nThe panel displays the following information:\nPROGRAM\nThe monitored program name.\nSTMT#\nThe statement number of the breakpoint.\nCOUNT\nThe number of times a breakpoint is executed before the program stops and the command in the COMMANDS\nTO BE EXECUTED field is executed\nEXEC\nShows the number of times the breakpoint has been executed.\nB/A/T", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ab4af2e6bf92-1", "text": "EXEC\nShows the number of times the breakpoint has been executed.\nB/A/T\nIndicates whether execution stops before the statement (B), after the statement (A), or at a temporary breakpoint\n(T).\nNote:  If there is a temporary breakpoint, the execution stops before the statement.\nCOMMANDS TO BE EXECUTED\nApplication commands that are specified in the Breakpoint panel or by the AT command.\nSOURCE LINE\nShows the source line where the breakpoint was set.\nNOTE\nUse an O or X line command to remove these breakpoints from this screen.\n 648", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4012ea68b162-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nYou can use all SCROLL keys and SCROLL variables in this display.\nWhen (or COND) Panel\nUse the When panel to set, reset (delete), or list conditional breakpoints. Access this panel by entering either COND (or\nWHEN) or OFFWN, without operands, in the Command field of the Intercept panel.\nYou give each When condition a when-name that is up to eight characters long. If the when-name specified is a statement\nnumber in the program, the when condition is checked only before executing this statement. This line-specific when\ncondition is known as a local conditional and requires less computing overhead since the condition is not tested before\nevery statement.\nA When-condition breakpoint is defined by one of two conditions:\n\u2022If only the when-name and the data-area-1 operands are specified, a W when-name Intercept panel is displayed each\ntime the value of the specified data item in data-area-1 changes. This type of conditional breakpoint is called a variable\nchange breakpoint.\n\u2022If the operands when-name, data-area-1, operator, and data-area-2 are specified, the data item that is specified in\ndata-area-1 is compared to the data item that is specified in data-area-2 based on the operator. When the condition is\ntrue, a W when-name Intercept panel is displayed. (Data-area-2 can be a data item, a constant, LOW-VALUES, HIGH-\nVALUES, SPACES, or ZEROES.)\nUse the OPTION field to enter S (set), R (reset), or L (list):\nS\nThe when-name and data-area-1 operands are required; the operator and data-area-2 operands are optional.\nR\nOnly the when-name operand is required.\nL\nDisplays the When Conditions Display panel. This panel lists all conditional breakpoints in the program.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4012ea68b162-1", "text": "L\nDisplays the When Conditions Display panel. This panel lists all conditional breakpoints in the program.\nField Descriptions\nWHEN NAME\nA 1-8 character name that is assigned to the test or program statement number.\nDATA-AREA-1\nThe data-name to be tested.\nOPERATOR\nCondition which DATA-AREA-1 and DATA-AREA-2 must meet for the breakpoint to occur. Valid values are:\n\u2022GT or > Greater Than\n\u2022LT or < Less Than\n\u2022EQ or = Equal\n\u2022NE or ? = Not Equal\n\u2022GE or >= Greater Than or Equal\n\u2022LE or <= Less Than or Equal\nNOTE\n=> and =< are not permitted.\nDATA-AREA-2\n(Optional) Data-name or content which is compared with Data-AREA-1.\nBEFORE/AFTER\nField to indicate whether to stop before or after the statement when the condition is recognized.\n 649", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c7c7932af773-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nExecute commands at a conditional breakpoint by entering the commands (separated by semicolons) in the COMMANDS\nTO BE EXECUTED AT WHEN CONDITION field. At the breakpoint, commands execute sequentially until the program\nresumes execution through the GO command, or until there is a request for a panel through a command such as the DI or\nUNCOND command. The remaining commands are ignored. The list of commands can be up to 73 characters long and\nshould be entered as shown in the following example:\n COMMANDS TO BE EXECUTED AT WHEN CONDITION:\n ===>SET BINARY-1 = 01;LDI BINARY-1;NEXT 5\n \nWhen Conditions Display Panel\nThe When Conditions Display panel lists conditional breakpoints set in the When panel, by the V, C and W line\ncommands, and by the COND (or WHEN) command for the current program with operands in the Command field of an\nIntercept panel.\nA sample When Conditions Display panel follows:\n ------------------- CA InterTest Batch BREAKPOINTS PANEL ----------------------\n COMMAND ===>                                                  SCROLL ===> CUR \n  \n      *************************** Top of Data *********************************\n      CONDITIONAL BREAKPOINTS FOLLOW:                                          \n      PROGRAM   WHN NAME  DATA NAME 1                     OP    DATA NAME 2    \n      --------  --------  ------------------------------  ----  ---------------\n .    CAMRCOBB  LOOPCOND  LOOP-OUT                        GT    +5000.         \n      ..SUBCOMMANDS FOR ABOVE WHEN ==> SET LOOP-OUT=0                          \n  \n     ************************** Bottom of Data ******************************* \n \nNOTE\nUse an O or X line command to remove the breakpoint from this screen.\nYou can use all SCROLL keys and SCROLL variables in this display.\nEquate Panel", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c7c7932af773-1", "text": "You can use all SCROLL keys and SCROLL variables in this display.\nEquate Panel\nUse the Equate panel to set, drop (delete), or list equated variable names. You can equate a data item with a symbolic\nname and then refer to by either the symbolic name or the data name. An unlimited number of equates can be set. To\naccess the Equate panel, enter the command EQU or DROP, without operands, in the Command field of the Intercept\npanel.\nUse the OPTION field to enter S (set), D (drop), or L (list):\nS\nYou must enter an equate name and the data-name-1 fields. Only enter the data-name-2 and data-name-3 fields\nwhen equating qualified data-items. Data-name-1 can be a subscripted or indexed data item.\nD\nDrops an equate. You must enter the equate name.\nL\nDisplays the Equate Display panel. This panel lists all equates that were set using the EQUATE command\nNOTE\nFor more information on the use and function of this command, see the EQUATE Control Command in\nDebugging Commands.\n 650", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5131d52c2716-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nEquate Display Panel\nThe Equate Display panel lists the equate name and actual name for all equates currently set.\nYou can use all SCROLL keys and SCROLL variables in this display.\nData Display Panels\nYou view or alter data values in a monitored program using data display panels. Enter one of the following commands in\nthe Command field of the Intercept panel to access each type of display.\nDISPLAY\nDisplay a data item defined to the monitored program or the WORKING STORAGE SECTION of a COBOL\nprogram.\nLINKAGE\nDisplay the LINKAGE SECTION of a COBOL program. This command is not valid for assembler or PL/I.\nRECORDS\nDisplay the FILE SECTION file descriptions of a COBOL program. This command is not valid for assembler or PL/\nI.\nNOTE\nWhen the DATAMON command is in effect and the trace navigation commands (PREV, ADV, POINT) have been\nused since the last breakpoint, this panel does not allow altering of data values.  In addition, the data values that\nare displayed correspond to the data values before the current trace entry was executed.\nDisplay Panel\nThe Display panel shows the following information:\nADDRESS\nThis column shows the starting virtual storage address for the data item. Use this address to address the data in\nCore, Option 2 on the PRIMARY OPTION MENU.\nTYPE\nThis is defined as follows:\n 651", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1d34d30e7b70-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Alphabetic\n\u2022AN Alphanumeric\n\u2022AN-V Varying alphanumeric\n\u2022ANE Alphanumeric edited\n\u2022BF Binary floating point\n\u2022BIT Bit\n\u2022BIT-V Varying bit\n\u2022Display (Sterling nonreport)\n\u2022DE Display edited (Sterling report)\n\u2022DBC Graphic or DBCS\n\u2022DBC-V Varying graphic\n\u2022Floating point (COMP-1/COMP-2)\n\u2022FD Floating point display (external floating point)\n\u2022HX Hexadecimal\n\u2022N National (UTF-16)\n\u2022NB Numeric binary unsigned (COMP)\n\u2022NB-S Numeric binary signed\n\u2022ND Numeric decimal unsigned (external decimal)\n\u2022ND-OL Numeric display, overpunch sign leading\n\u2022ND-OT Numeric display, overpunch sign trailing\n\u2022ND-SL Numeric display, separate sign leading\n\u2022ND-ST Numeric display, separate sign trailing\n\u2022NE Numeric edited\n\u2022NP Numeric packed decimal unsigned (COMP-3)\n\u2022NP-S Numeric packed decimal signed\n\u2022PTR Pointer data item (usage pointer)\n\u2022UI Index data item (usage index)\n\u2022Subscripted\nLINE #\nThis column shows the program line numbers where the data names are defined.\nLV\nThis column shows the level number generated by the compiler. Level numbers appear in the DMAP output of the\nCOBOL compiler or the AGGREGATE output of the PL/I compiler.\nNAME/VALUE\nThis column displays the data-item names.\nThe value of the data item is displayed as it is defined in the monitored program. If the data in the VALUE field is more\nthan 20 characters long, it is shown on multiple lines.\nNOTE\nCOBOL programs can be compiled with the ARITH(EXTEND) parameter, which will allow a numeric field to be", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1d34d30e7b70-1", "text": "greater than 18 bytes. These fields will be displayed with the message 'TOO BIG TO DISPLAY' in the value. To\nview or change the actual value of the field, use the CORE command.\nAlter data by typing over the value field. The application truncates data if you attempt to modify a data item with a value\nlarger than the size of the data item. Movement of new values to the data area is done according to how the item is\ndefined. For example, if the variable is alphanumeric and is 2 bytes long, if you enter 12B, the value truncates to 12.\nYou can use all SCROLL keys and SCROLL variables.\n 652", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5444bd75a9cb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFor assembler programs, when an access register or 64-bit address is requested for display, an additional line shows the\naccess register or \u201chigh half\u201d value, as shown in the following panels:\n  -------------- CA InterTest Batch ASSEMBLER DATA DISPLAY ---------------------\n COMMAND ===>                                                  SCROLL ===> CUR \n ADDRESS  TYPE  LINE # LV  NAME  / VALUE                 0----.----1----.----2--\n **************************** Top of Data ************** ********************   \n High-Half ==> 00000001                                                         \n 00000000 HX    000000 02 R1                             0000000000000000       \n 00000008 HX    000000     +0008                         0000000000000000       \n 00000010 HX    000000     +0016                         00000003000B3958 \n \u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026\n *************************** Bottom of Data ************ ********************  \n -------------- CA InterTest Batch ASSEMBLER DATA DISPLAY ---------------------\n COMMAND ===>                                                  SCROLL ===> CUR \n ADDRESS  TYPE  LINE # LV  NAME  / VALUE                 0----.----1----.----2--\n **************************** Top of Data ************** ********************   \n ALET     ===> 00010004                                                         \n 00000000 HX    000000 02 R3?                            0000000000000000       \n 00000008 HX    000000     +0008                         0000000000000000       \n 00000010 HX    000000     +0016                         0000000000000000\n \u2026\u2026\u2026\u2026\u2026\u2026\u2026\u2026       \n *************************** Bottom of Data ************ ********************    \n \nFor more information on Assembler indirect addressing, see Control Commands.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5444bd75a9cb-1", "text": "For more information on Assembler indirect addressing, see Control Commands.\nInvoke the panel by entering the Display command, with or without operands, from an Intercept panel. For assembler and\nPL/I programs, operands are required.\nLinkage Panel\nTo invoke the Linkage panel, enter the LInkage command with or without operands from an Intercept panel. This\ncommand is only valid for COBOL programs.\nDisplay the Linkage panel after the first PROCEDURE DIVISION statement has been executed, otherwise the linkage\naddresses will not be resolved. This occurs only when the Intercept panel is displayed for the first time and the LINKAGE\ncommand is entered. You can avoid this by using the NEXT command the first time the Intercept panel is displayed to\nexecute the first statement in the PROCEDURE DIVISION and resolve the linkage addresses.\nRecords Panel\nTo display the Records panel, enter the REcords command with or without operands from an Intercept panel. This\ncommand is only valid for COBOL programs. You can only use the RECORDS command, which displays the File Section\nDisplay panel, to modify data if the file is open.\nFile Status Panel\nThe File Status panel displays the characteristics of all assigned files, and shows whether they are open or closed. Enter\nthe FILES (FI) command from an Intercept panel to open this screen. The File Status panel is only available for COBOL\nprograms.\nThe following screen is an example of the File Status panel:\n --------------------- CA InterTest Batch FILE STATUS PANEL --------------------\n 653", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8aa30822f04a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n COMMAND ===>                                                   SCROLL ===> PAGE\n FD-NAME------------------------DDNAME---DSNAME-------------------------------------\n INPUT-FILE                     SYSUT1  INTC.SOME.DATAS                         \n OPEN  INPUT   DSORG=PS RECFM=FB        BLKSIZE=06000 LRECL=0080                \n DCB=00123456  DEB=006C941C                                                     \n .   .   .   .   .   .   .   .   .     .   .   .   .   .   .   .   .   .   .  . \n SYMBOL-FILE                  SYMBOL     *** WARNING *** DD CARD NOT ALLOCATED   \n  CLOSED        DSORG=PS RECFM=.....     BLKSIZE=00800 LRECL=0080\n   DCB=0018D42C                                                                 \n .   .   .   .   .   .   .   .     .   .   .   .   .   .   .   .  .   .  .  .\n OUTPUT-FILE                  SYSUT2     INTC.NOTA.PDS                          \n  OPEN  OUTPUT  DSORG=PS RECFM=FB        BLKSIZE=06000 LRECL=0080\n   DCB=0018DD40 DEB=006C941C  DECB=0018BD80                                     \n .   .   .   .   .   .   .   .   .     .   .   .   .   .   .   .   . .          \n \nIf you receive a warning that says the DD CARD is not allocated take one of the following actions:\n\u2022Split the screen and enter TSO using the ALLOCATE command to allocate the required file.\n\u2022Enter the TSO ALLOCATE command on the command line of the current ISPF screen.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8aa30822f04a-1", "text": "\u2022Enter the TSO ALLOCATE command on the command line of the current ISPF screen.\n\u2022Invoke another session and select Option 3 to allocate the file.\n\u2022Suspend the session and perform the allocation under Roscoe , for Roscoe  users. Then resume the ETSO session to\nresume your InterTest Batch session.\nNOTE\nBatch Link users must use the DDALLOC command to allocate the DD. For more information on this command,\nsee Control Commands.\nThe data event block (DEB) is only displayed for open BSAM files.\nFor OS/VS COBOL users, IMS databases do not appear on the status display.\nProgram Trace Display Panel\nThe Program Trace Display panel displays program statements in the order of their execution. To initiate a trace, enter the\nTRACE or TRACE SOURCE command in the Command field of the Intercept panel. For more details on the command\nformat for TRACE Control Command, see Debugging Commands.\nA sample Program Trace Display panel with TRACE follows:\n------------------ CA InterTest Batch PROGRAM TRACE DISPLAY -------------------\nCOMMAND INPUT ===>                                              SCROLL===> PAGE\nStmtNo   Program    Label Name/Source Line                           \n043700   CAMRCOBB                                                            \n043500   CAMRCOBB                                                            \n043400   CAMRCOBB   FORCING-THE-ABEND                                        \n043300   CAMRCOBB                                                            \n043100   CAMRCOBB                                                            \n042200   CAMRCOBB                                                            \n042034   CAMRCOBB                                                            \n042033   CAMRCOBB                                                            \n042031   CAMRCOBB                                                            \n051500   CAMRCOBB   0100-SOME-MEANINGFUL-LABEL                               \n051400   CAMRCOBB                                                            \n050600   CAMRCOBB                                                            \n 654", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a1c063c12186-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n050400   CAMRCOBB                                                            \n050200   CAMRCOBB                                                            \n049800   CAMRCOBB   0200-THESE-ARE-PARAGRAPH-NAMES                           \n049700   CAMRCOBB                                                            \n049400   CAMRCOBB                                                            \n048600   CAMRCOBB                                                            \n042030   CAMRCOBB                                                            \n042029   CAMRCOBB                                                            \n042028   CAMRCOBB \nA sample Program Trace Display panel with TRACE SOURCE follows:\n------------- CA InterTest Batch PROGRAM TRACE DISPLAY ------------------------\nCOMMAND ===>                                                 Scroll ===> PAGE  \nStmtNo  Program   Label Name/Source Line                                   \n**************************************** TOP OF DATA **************************\n001042  CAMRCOBB              MOVE  R1498-TIMEO TO R1498-TIME.                 \n001041  CAMRCOBB          SPLIT-SCREEN.                                        \n001038  CAMRCOBB              IF   S-AID = 'PF3 ' OR 'PF15'                    \n001037  CAMRCOBB              CALL 'ROETSAPI' USING  GETV  S-AID-DEF  S-AID.   \n001035  CAMRCOBB              IF RETURN-CODE NOT EQUAL ZERO                    \n001034  CAMRCOBB              CALL 'ROETSAPI' USING  PANL  PANL-PARM.          \n001033  CAMRCOBB              MOVE '73' to  PANL-ID.                           \n001028  CAMRCOBB          DEMONSTRATE-SPLIT-SCREEN.                            \n000950  CAMRCOBB                  GO TO DEMONSTRATE-SPLIT-SCREEN.              \n000949  CAMRCOBB              IF  P-OPT = '3'                                  \n000947  CAMRCOBB              IF  P-OPT = '2'", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a1c063c12186-1", "text": "000947  CAMRCOBB              IF  P-OPT = '2'                                  \n000945  CAMRCOBB              IF  P-OPT = '1'                                  \n000942  CAMRCOBB              IF  S-AID = 'PF3 ' OR 'PF15'                     \n000939  CAMRCOBB              IF RETURN-CODE NOT EQUAL ZERO                    \n000937  CAMRCOBB              CALL 'ROETSAPI' USING  GETV S-AID-DEF   S-AID    \n000934  CAMRCOBB              IF RETURN-CODE NOT EQUAL ZERO                    \n000933  CAMRCOBB              CALL 'ROETSAPI' USING  PANL  PANL-PARM.          \n000932  CAMRCOBB              MOVE '07' to  PANL-ID.                           \n000930  CAMRCOBB              MOVE ZEROES    TO LOOP-OUT.                      \n000929  CAMRCOBB          OPTIONS.                                             \nThe Command field accepts only display commands. For valid commands, see Display Commands. You can use all\nSCROLL keys and SCROLL variables in this panel.\nCore Option\nUse the Core option, option 2 on the Primary Option Menu, to display the memory for your TSO user region during a test.\nYou can also use the CORE command from any Intercept panel.\nThe screen displays memory in hexadecimal and character formats. You can change memory that is not modify-protected\nby overwriting the data on the display. Fetch protected memory cannot be displayed or modified.\nLocate data in memory by using the following methods:\n\u2022The FIND commands search for a specified character or hexadecimal string.\n\u2022The DISPLAY command locates a specified address.\n\u2022Specify a hexadecimal and use the scroll keys to shift the contents of the display by the specified amount.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a1c063c12186-2", "text": "\u2022Type an address over the primary address field, or an offset from the primary address can be typed over the primary\noffset field. The primary offset fields are and the display scrolled to that part of memory.\n 655", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9b6c0bce849a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nYou can also use the following PF keys:\nPF10\nRestore the address that was previously displayed.\nPF11\nThe address indicated by the cursor position appears in the primary address field and the display is scrollable to\nthat part of memory.\nNOTE\nIf you enter the CORE command from an Intercept screen, the display includes an updateable EXPR field, which\nshows a register expression or the address currently displayed. Commands that modify the displayed address\nalso modify this field.\nDISPLAY \nThe DISPLAY command sets the primary address field to the specified address. The primary address field is updated to\nthe indicated address in virtual storage. The primary offset field is set to zero.\nSyntax\nDISPLAY address\n\u2022address\nSpecify the address in virtual storage. The address is case-sensitive and can be a one to eight digit hexadecimal\nnumber.\nFIND Command\nThe FIND command, or F, searches memory until the string operand is matched.\nSyntax\nFIND string <NEXT|FIRST|LAST|PREV>\n\u2022string  Specify the search argument on the data area. The string can be alphabetic, numeric, and special characters.\nUse single or double quotation marks around the string if it contains embedded blanks or quotes.\n\u2022NEXT\nSearch for the next occurrence of the string, starting at the beginning of the first address displayed.\n\u2022FIRST\nScroll to location zero followed by a FIND NEXT operation.\n\u2022LAST\nStart the scan at address 16,777,215 (X'FFFFFF') and move backwards to find the last occurrence of string.\n\u2022PREV\nStart the scan at the current address and move backward to find the previous occurrence of the string.\nFX (Find Hex Data)\nThe FX command searches memory until the hexadecimal string is matched.\nSyntax\nFX string   < NEXT|FIRST|LAST|PREV>\nstring", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9b6c0bce849a-1", "text": "Syntax\nFX string   < NEXT|FIRST|LAST|PREV>\nstring\nSpecify a search argument of one to eight hexadecimal characters.\n 656", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a6814cf92413-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNEXT\nSearch for the next occurrence of string starting at the beginning of the first address displayed.\nFIRST\nScroll to location zero, and then process the FIND NEXT operation.\nLAST\nStart the scan at address X'FFFFFF' (16,777,215) and move backwards to find the last occurrence of string.\nPREV\nStart the scan at the current address and move backwards to find the previous occurrence of string\nPOP\nThe POP command restores the address most recently pushed onto the stack. The address becomes the primary address\non the display, and the primary offset field is set to zero. If the stack is empty, an EMPTY STACK message appears.\nSyntax\nPOP\nPUSH\nThe PUSH command places on the stack the current primary address.\nSyntax\nPUSH\nMap Option\nThe Region Map Display panel shows the task control blocks (TCBs) for the program that you initiate the command from.\nLaunch this panel by using the MAP command from any debugging session. You can also  use Option 4 from the primary\noption menu.\nThe Region Map Display panel shows the following information about the TCB list:\nTCB\nThe address of the current TCB\nID\nThe number associated with the current TCB\nNOTE\nUse the ID command to overwrite this field.\nTIOT\nThe task input/output table\nASCB\nThe location of the address space control block\nASID\nThe address space identifier\nThe table shows the following information for each TCB listed:\nTCB\nThe name of each TCB that resides under the parent\n 657", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3dc0ebaf48fd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nID\nThe ID number for each TCB listed\nLevel\nThe hierarchical representation of the TCB\nProgram\nThe program the TCB is assigned to\nStatus\nThe state of the TCB\nNDISP\nThe format\nUse the following commands to control what TCB information the Region Map Display panel shows.\nID task number\nSet the TCB number for your program.\nCDE\nThe programs in storage for the current TCB ID number.\nSAVE\nThe save area map for the current TCB ID number.\nALLOC\nThe current allocations by ddname. The option ALLOC is similar to the TSO LISTALC command, but ALLOC\ndisplays the ddname. You can also scroll the display.\nFILE\nThe Information on open files related to the current TCB ID number.\nNOTE\nIMS database files do not display using the FILE command. Use the ALLOC command to see\ninformation for IMS databases.\nTCB\nThe status of the user's TCBs (not task related).\nRB\nThe active request blocks (RB) for the current TCB ID number.\nALLTCB\nAll TCBs for your TSO session\nUse the scroll keys to view and select the TCB number of the program you are testing from the list of ID numbers on the\nControl Block Display panel.\nDebugging Commands\nThis section describes the commands valid for use during a debugging session. There are four types of commands:\n\u2022Display\n\u2022Line\n\u2022Control\n\u2022Report\nUse display  commands to locate selected data in the program and position it on the screen. These are commands such\nas FIND and SCROLL; they can be used in any panel containing a command input field.\n 658", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f2015819f7f4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nControl and line commands direct the test session and you enter them only in the Intercept panel. Line commands are\nshorter versions of some control commands.\nReport  commands generate reports to be printed and analyzed offline. Only enter report commands in the Intercept panel.\nDisplay Commands\nThis article describes the display commands that you can use to locate and position data on the screen. Enter them on the\ncommand line of any panel containing a command input field.\nCOLUMN Command\nThe COLUMN command places a line that shows the column numbers on the first line of the display area of the Intercept\nor Display panel.\nSyntax\nUse the following syntax for COLUMN:\nCOLUMN < ON|OFF>\nVariables\nUse the following variables with the COLUMN command:\nON\nEnables the column numbers display.\nOFF\nDisables the column numbers display.\nCOLUMN OFF is functionally equivalent to the RESET command, which removes the column numbers from the panel\ndisplay.\nFIND Command\nThe FIND command searches the file until the string operand is matched.\nSyntax\nUse the following syntax for FIND:\nFIND string <col1 <col2>> <NEXT|FIRST|LAST|PREV>\nYou can enter FIND in its abbreviated form: F.\nVariables\nUse the following variables with the FIND command:\n\u2022string\nThe search argument on the data area. String can be alphabetic, numeric, and special characters. If string contains\nembedded blanks or quotes, it must be enclosed in single or double quotation marks.\n\u2022col1\nSpecifies the column in which to begin the search for string. If col1 is specified and col2 is omitted, the string must start\nin the specified column.\n\u2022col2\n 659", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f27ea53dec64-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSpecifies the last column of a range of columns to search for string. If col2 is greater than the record length, the record\nlength is used.\n\u2022NEXT\nCauses a search for the next occurrence of string starting at the beginning of the first line displayed after the cursor\nlocation. The default is NEXT.\n\u2022FIRST\nCauses a scroll to the top of the data followed by a FIND NEXT operation.\n\u2022LAST\nStarts the scan at the bottom of the data and moves backward to find the last occurrence of string.\n\u2022PREV\nStarts the scan at the current cursor location and moves backward to find the previous occurrence of string.\nExample:\nTo find the next occurrence of TEST  in a program, enter:\nF \"'TEST'\"\nFP Command (Find Paragraph)\nThe Find Paragraph command scrolls the display to the definition of the specified paragraph, procedure, or label name.\nSyntax\nUse the following syntax for FP:\nFP paragraph-name|procedure-name|label-name\nYou must enter this command in its abbreviated form: FP.\nVariables\nUse the following variables with the FP command:\nparagraph-name\nDesignates a paragraph name defined in the Procedure Division of the currently qualified COBOL program\nprocedure-name\nDesignates a procedure name defined in the currently qualified PL/I program.\nlabel-name\nDesignates a label name defined in the currently qualified assembler or PL/I program.  \nFS Command (Find Statement)\nThe Find Statement command scrolls a display to a specified statement number.\nSyntax\nUse the following syntax for FS:\nFS statement-number\nYou must enter this command in its abbreviated form: FS.\nVariable\n 660", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "12c49132cd7e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nstatement-number\nSpecifies a statement number in the currently qualified program.\nCursor Sensitive Find\nIf a data name is displayed and you wish to locate its definition, place the cursor over the data name and press  Enter. The\napplication repositions the display at the definition of the data name.\nIf a paragraph, procedure, or label name is displayed and you wish to locate the line on which it starts, place the cursor\nover the name and press Enter. the application repositions the display at the paragraph, procedure, or label.\nKDOWN Command (Scroll Keep Window Down)\nUse the KDOWN command to scroll the keep window in the downward direction. The keep window appears on the\nIntercept panel immediately above the first line of the program listing.\nSyntax\nUse the following syntax for KDOWN:\nKDOWN scroll-amt\nVariables\nUse the following variables with the KDOWN command:\n\u2022scroll-amt\nIdentifies the number of lines to scroll, specified as one of the following:\n\u2022PAGE\nScroll up one full page.\n\u2022HALF\nScroll up one half page.\n\u2022MAX\nScroll up to the top of the window.\n\u2022nnn\nScroll the number of lines specified.\nUsage Notes\nThe keep window is not scrollable if the number of entries in the window is less than the maximum depth defined by the\nKSIZE command. If the window is not scrollable, the KDOWN command is not functional.\nIf no argument is specified, the default scroll amount is used. The default scroll amount is defined in the upper right corner\nof the Intercept panel.\nKSIZE (or KS) Command (Keep Window Size)\nUse the KSIZE command to determine the size of your keep window. The keep window appears on the Intercept panel\nimmediately above the first line of the program listing.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "12c49132cd7e-1", "text": "immediately above the first line of the program listing.\nThe KSIZE command lets you control the maximum depth of the keep window and whether the window should be fixed or\nvariable in size.\nSyntax\nUse the following syntax for KSIZE:\nKSIZE depth F|V\n 661", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fe5940873cd1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nEnter this command in its abbreviated form: KS.\nVariables\nUse the following variables with the KSIZE command:\ndepth\nThe maximum number of lines of data to be displayed in the window at one time.\nF\nSpecify F for a fixed window size.\nV\nSpecify V for a variable sized window.\nUsage Notes\nYou can set the keep window size to any depth from 1 to 15 lines of data. The default depth is 6 lines.\nIf KSIZE is defined as fixed, the keep window always occupies the maximum depth, even if the window contains less\ndata items that the maximum. If the window is defined as variable, it will never occupy more lines on the screen than are\nnecessary to display all of the data items, and never more than the maximum depth.\nDefine your keep window as fixed to prevent bouncing of your source listing while stepping through the program.\nKUP Command (Scroll Keep Window Up)\nUse the KUP command to scroll the keep window in the upward direction. The keep window appears on the Intercept\npanel immediately above the first line of the program listing.\nSyntax\nUse the following syntax for KUP:\nKUP scroll-amt\nVariables\nUse the following variables with the KUP command:\n\u2022scroll-amt\nIdentifies the number of lines to scroll, specified as one of the following:\n\u2022PAGE\nScroll up one full page.\n\u2022HALF\nScroll up one half page.\n\u2022MAX\nScroll up to the top of the window.\n\u2022nnn\nScroll the number of lines specified.\nUsage Notes\nThe keep window is not scrollable if the number of entries in the window is less than the maximum depth defined by the\nKSIZE command. If the window is not scrollable, the KUP command is not functional.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fe5940873cd1-1", "text": "KSIZE command. If the window is not scrollable, the KUP command is not functional.\nIf no argument is specified, the default scroll amount is used. The default scroll amount is defined in the upper right corner\nof the Intercept panel.\n 662", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8f8f697103aa-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nLOCATE Command\nUse the LOCATE command to scroll to a specified line or a user-defined symbolic label in the program.\nSyntax\nUse the following syntax for LOCATE:\nLOCATE nnnnnn|.label\nYou can enter this command in its abbreviated form: L.\nVariables\nUse the following variables with the LOCATE command:\n\u2022nnnnnn\nSpecifies a relative line number. The display scrolls so that the line number is the first line of the display. A line number\nof zero causes a scroll to the top of the data; 999999 causes a scroll to the bottom of the data.\n\u2022.label\nCauses the display to scroll so that the line number equated to the symbolic label is the first line in the display.\nA symbolic label equates to a line number. To establish a symbolic label, scroll the display until the line number to be\nequated is on the first line of the display. Enter the label in the COMMAND input field in the format:\nxxxxxxx\nThe period is required and is followed by up to seven alphanumeric characters. The application does not retain symbolic\nlabels when the test session ends.\n.label Command\nThis command assigns a symbolic label to the current line number in the program.\nSyntax\nUse the following syntax for .label:\n.xxxxxx\nVariables\nUse the following variables with the .label command:\nxxxxxxx\nThe period is required and may be followed by up to 7 alphanumeric characters.\nThe application does not retain symbolic labels when the test session ends.\nLine Commands\nLine commands are typed in the far left field of a line to perform various actions.\nYou can type multiple commands on different lines before pressing Enter, which processes all commands. Scrolling, or\nother commands that change the display, also cause the specified line commands to be processed.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8f8f697103aa-1", "text": "other commands that change the display, also cause the specified line commands to be processed.\nThis article describes the following commands:\n 663", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "39150e1219d0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe following table is an overview of the Line commands, the corresponding Control Commands, and their function. The\nfollowing pages provide a more complete description of each command.\nNote that some commands have synonyms, such as A and U, which are fully interchangeable. Use whichever one you\nfind easiest to remember.\nLineCommands ControlCommands Description\nA\nUAT\nUNCONDAn unconditional \"before\" breakpoint\nis set at the specified line. This type of\nbreakpoint stops before  the specified\nprogram statement. You can enter an\n\"after\" breakpoint by entering the ) line\ncommand.\nA U remains in the first column to show\nwhere breakpoints are set.\nFor assembler, if an A is placed next to a\nline in the keep window, the access register\nfor that item is displayed.\nC\nWCOND\nWHENA conditional breakpoint is set at the\nspecified line. Issuing this command causes\nthe application to display the When screen,\nwhere the condition may be specified.\nThe application automatically completes\nthe line number portion of the When screen\nbased on your breakpoint line.\nD DISPLAY The DISPLAY panel is shown for all of\nthe data items on the line where the D\ncommand is specified.\nFor assembler, the operands for the current\ninstruction in register notation are shown in\nthe DISPLAY panel.\nCursor-sensitive DISPLAY - If D is entered\nand the cursor is placed on a COBOL or\nPL/I data item in that line, pressing Enter\ndisplays the DISPLAY panel for only that\nitem and data items to the right of the item\non the same line.\nG GO The program begins executing (Go to) the\nline where the G is typed.\nGT GOTO The program executes to the specified line.\n 664", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e887b619965a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nH KEEPX\nLDIX\nLDXThe data items on the line where the H is\nplaced are listed at the top of the Intercept\npanel in a keep window and shown in Hex\nformat.\nFor assembler, the operands for the current\ninstruction in register notation are added to\nthe keep window.\nCursor-sensitive KEEPX - if H is entered\nand the cursor is placed on a COBOL or\nPL/I data item in that line, pressing Enter\nlists in the keep window only that data item\nand data items to the right of that item on\nthe same line.\nFor assembler programs, if an H is placed\non a line within the keep window, the high\nhalf of the 64bit register is displayed.\nI INFO In instances where a frequency count\nexceeds 9999, Info displays the actual\ncount at the top right of the screen.\nFor assembler programs, if an I is placed\non a line within the keep window, the\naccess register is displayed.\nK KEEP\nLDIThe data items on the line where the K or L\nis placed are listed in a keep window on the\ntop of the Intercept panel.\nFor assembler, the operands for the current\ninstruction in register notation are added to\nthe keep window.\nCursor-sensitive KEEP - If you enter K and\nthe cursor is placed on a COBOL or PL/I\ndata item in that line, pressing Enter lists\nin the keep window only that data item and\ndata items to the right of that item on the\nsame line.\nO , blank,\nXOFF\nOFFUThe breakpoint currently set on the line is\nreset (turned off).\nP PRINT The DISPLAY for all the COBOL or PL/\nI data items on the line are written to the\nsession log for later printing.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e887b619965a-1", "text": "I data items on the line are written to the\nsession log for later printing.\nFor assembler, the operands for the current\ninstruction in register notation are written to\nthe session log for later printing.\nR REMOVE\nLDIAn RDI, reset data item, is done for each of\nthe data items on the line to remove entries\nin the keep window. You may also use it\nnext to individual keep window entries.\nS SKIP Skip this statement. The S remains in the\nfirst column to show you which statements\nare skipped.\n 665", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7219f630ce85-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nV COND\nWHENA variable change breakpoint is set at the\nspecified line. The breakpoint is triggered\nbefore the line is executed when the\napplication determines that the value of a\nvariable in the line changes.\nCursor-sensitive variable change\nbreakpoint - If you enter V and the cursor\nis placed on a COBOL or PL/I data item,\npressing Enter designates that item as the\nvariable change item.\nX OFF\nRDIRemove breakpoint or remove data item\nfrom keep window.\n) AT\nUNCONDAn unconditional \"after\" breakpoint is\nset at the specified line. This type of\nbreakpoint stops after the specified\nprogram statement. You can enter a\n\"before\" breakpoint by entering the U or A\nline command.\nA ) remains in the first column to show\nwhere breakpoints are set.\n+ nnn Increment a subscript by nnn on a\ndisplayed data item.\n- nnn Decrement a subscript by nnn on a\ndisplayed data item.\n<[nnnn] Used on a keep window entry scrolls the\ndata left nnnn  bytes.\n>[nnnn] Used on a keep window entry scrolls the\ndata right nnnn  bytes.\nA or U Command (Set Unconditional \"Before\" Breakpoints)\nThe A or U line command performs the same function as the AT or UNCOND command. An unconditional \"before\"\nbreakpoint is set on the line where the A or U is typed. The program stops at the statement prior to executing it. A U\ndisplays on the line to show you where breakpoints have been set. The U or A line command is only valid on executable\nlines of the program listing. Executable lines contain a frequency counter number or arrow. There is no limit other than the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7219f630ce85-1", "text": "size of the screen. If you press Enter or the scroll keys, it sets the breakpoints.\nYou can type other commands over the U. Reset breakpoints using the OFF, O, X, or blank line commands.\nThe following panel shows \"before\" breakpoints being set on lines 13100, 13400, and 13736 of the program:\n CAMRCOB2 ---------- CA InterTest Batch NEXT BEFORE Intercept -----------------\n COMMAND ===>                                                  SCROLL===> PAGE    \n TRACE= 012400 012300                                                            \n          7        CAMRCOB2        15.49.31        JUN 30,2014                    \n  0001        012300 PROCEDURE DIVISION USING PARMS TEST-THREE TEST-FOUR PASS-    \n  --->        012400 DEMO-BEGIN.                                                \n  --->        012500     GO TO DEMO-INIT.                                        \n  --->        012600 DEMO-INIT.                                                  \n  --->        012700     OPEN OUTPUT OUTPUT01.                                   \n  --->        012800     MOVE HD1 TO LINE-OUT.                                   \n  --->        012900     PERFORM WRITE-LINE.                                     \n \n u--->        013100 FORCING-THE-ABEND.                                          \n 666", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d27d212f9be4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  --->        013200     MOVE MASK1  TO BIN1.                                    \n  --->        013300     MOVE ZERO   TO MASK1.                                   \n u--->        013400     MOVE MASK1  TO BIN1                                      \n              013410                    BIN2                                      \n              013500                    BIN3                                      \n              013600                    BIN4.                                    \n  --->        013700 TABLE-MOVE.                                                 \n u--->        013736       MOVE TABLE-FILL TO WA-TABLE-1.          \n  --->        013737 NUM-EDITED-TEST.                                            \n  --->        013738       MOVE IN-FUNC TO OUT-FUNC.                             \n  --->        013739       MOVE IN-FUNC TO OUT-FUNC2.                            \nPress Enter to set the breakpoints.\nThe listing appears as shown in the following panel. The lines that have \"before\" breakpoints set display a U in the first\ncolumn to show you where the breakpoints are.\nCAMRCOB2 ---------- CA InterTest Batch NEXT BEFORE Intercept ----------------- COMMAND ===>                   \n                               SCROLL===> PAGE    \n TRACE=> 012400 012300                                                            \n          7        CAMRCOB2        15.49.31        JUN 30,2014                    \n  0001        012300 PROCEDURE DIVISION USING PARMS TEST-THREE TEST-FOUR PASS-    \n  --->        012400 DEMO-BEGIN.                                                \n  --->        012500     GO TO DEMO-INIT.                                        \n  --->        012600 DEMO-INIT.                                                  \n  --->        012700     OPEN OUTPUT OUTPUT01.                                   \n  --->        012800     MOVE HD1 TO LINE-OUT.                                   \n  --->        012900     PERFORM WRITE-LINE.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d27d212f9be4-1", "text": "--->        012900     PERFORM WRITE-LINE.                                     \n \n U--->        013100 FORCING-THE-ABEND.                                          \n  --->        013200     MOVE MASK1  TO BIN1. \n \n  --->        013300     MOVE ZERO   TO MASK1.                                   \n U--->        013400     MOVE MASK1  TO BIN1                                      \n              013410                    BIN2                                      \n              013500                    BIN3                                      \n              013600                    BIN4.                                    \n  --->        013700 TABLE-MOVE.                                                 \n U--->        013736       MOVE TABLE-FILL TO WA-TABLE-1.                        \n  --->        013737 NUM-EDITED-TEST. \n  --->        013738       MOVE IN-FUNC TO OUT-FUNC.\n  --->        013739       MOVE IN-FUNC TO OUT-FUNC2.                            \nYou can also use the LISTAT command to show the Breakpoints panel as follows:\n-------------------- CA InterTest Batch BREAKPOINTS PANEL ---------------------\nCOMMAND ===>                                                  SCROLL ===> CUR \n \n     *************************** Top of Data *********************************\n     UNCONDITIONAL BREAKPOINTS FOLLOW:                                        \n     PROGRAM   STMT#   COUNT  EXEC  B/A  COMMANDS TO BE EXECUTED              \n     --------  ------  -----  ----  ---  -------------------------------------\n.    CAMRCOB2  000589  0000   0000   B                                        \n     SOURCE LINE: SPLIT-SCREEN.                                               \n \n 667", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2a8fe44bf11b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n.    CAMRCOB2  000541  0000   0000   B                                        \n     SOURCE LINE: PAY-CALC.                                                   \n \n.    CAMRCOB2  000659  0000   0000   B                                        \n     SOURCE LINE: ORDER-CALC.                                                 \n ************************************* BOTTOM OF DATA *************************   \n \nC or W Command (Set Conditional Breakpoint)\nUse the C or W command to set a conditional breakpoint for a specified line. When you enter a C or W on a line and press\nEnter, the When screen displays. The WHEN-NAME field is populated with the line that you have specified. Use the When\nscreen to specify the condition for the breakpoint. The condition is only checked before executing that statement. The\napplication automatically completes the line number portion of the When screen based on your breakpoint line.\nThe C or W line command is only valid on executable lines in the program listing. Executable lines contain a frequency\ncounter number or arrow.\nNOTE\nFor further explanation of the When panel, see Debugging Panels.\nExample:\nIn the following example, you have entered the C command at line 1149 to set a conditional breakpoint.\nCAMRCOB2 ---------- CA InterTest Batch NEXT BEFORE Intercept ------------------\nCommand ===>                                                    Scroll===> CUR \nTRACE=> 001151 001150 001149 001148 001162 001155 001154 001153 001151 001150 0\nU0001   001141                ORDER-CALC.                                     \n 0001   001142                    MOVE CUSTOMER-VALUES TO CUSTOMER-ORDER.     \n 0001   001143                    MOVE ZEROES TO ORDER-SUB-TOTAL, SUB-6, LOOP-O", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2a8fe44bf11b-1", "text": "0001   001144                    PERFORM TOTAL-ORDER THRU TOTAL-ORDER-EX      \n        001145                        UNTIL SUB-6 EQUAL 5.                    \nU--->   001146                ORDER-CALC-EX.                                  \n --->   001147                    GO TO OPTIONS.                              \n 0101   001148                TOTAL-ORDER.                                    \nc0101   001149                    ADD 1 TO SUB-6.                             \n 0101   001150                    ADD 1 TO LOOP-OUT.                          \n 0100   001151                    MULTIPLY UNIT-PRICE(SUB-6) BY NO-OF-WIDGETS(S\n        001152                        GIVING ITEM-TOTAL.                      \n 0100   001153                    ADD ITEM-TOTAL TO ORDER-SUB-TOTAL.          \n 0100   001154                    MOVE 1 TO SUB-6.                            \n 0100   001155                TOTAL-ORDER-EX.                                 \n        001156               *------------------------------------------------*\n        001157               * The code above will loop. The loop can be      *\n        001158               * interrupted by pressing an attention key.. .. *\n        001159               * The frequency counter should provide a clue    *\nWhen you press Enter in this example, the When panel displays, and the WHEN-NAME field is populated with the number\n1149.\nD Command (Display Working Storage)\nFor COBOL and PL/I programs the D line command causes the Display panel to be shown for all the data items on the\nline where the command is typed. For assembler programs, the D line command displays the operands for the current\ninstruction in register notation. The D line command is valid on any line in the program listing.\n 668", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a236690eb24e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nYou may type multiple D line commands on different lines, but to display the Display panel from each line in succession,\npress the END (PF3 or PF15) key. If D is specified on four lines, the Display panel appears for the data items on the first\nline. When END is pressed, the Display panel appears for the data items on the second line. This continues until the last\nD command is processed. Then the Intercept panel is displayed.\nCursor-sensitive Display: If you enter D and the cursor is placed on a COBOL and PL/I data item in the line, pressing\nEnter displays the Display panel for only that item and data items to the  right of the item on the same line.\nFor more information on the Display Panel, see Data Display Panels.\nG Command (Go from Line)\nThe G line command causes the program to begin executing from the line on which you typed the G. Specify only one G\nline command at any time. If you type, execution begins from the highest line number. For example, if you type G on line\n12900 and on line 13100, execution resumes at line 13100.\nIf you type G on line 13100 of the listing, as shown in the following panel, the program begins executing on line 13100\ninstead of normally beginning on line 12800. Lines 12800 and 12900 are not executed.\nCAMRCOB2 ---------- CA InterTest Batch NEXT BEFORE Intercept -----------------\n COMMAND ===>                                                  SCROLL===> PAGE \n TRACE=> 012800 012700 012600 012400 012300  \n          7        CAMRCOB2        15.49.31        JUN 30,2014", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a236690eb24e-1", "text": "0001        012300 PROCEDURE DIVISION USING PARMS TEST-THREE TEST-FOUR PASS- \n  0001        012400 DEMO-BEGIN.                                               \n  --->        012500     GO TO DEMO-INIT.                                      \n  0001        012600 DEMO-INIT.                                                \n  0001        012700     OPEN OUTPUT OUTPUT01.                                 \n U--->        012800     MOVE HD1 TO LINE-OUT.                                 \n  --->        012900     PERFORM WRITE-LINE.                                   \n \n g--->        013100 FORCING-THE-ABEND.                                        \n  --->        013200     MOVE MASK1  TO BIN1.                                  \n  --->        013300     MOVE ZERO   TO MASK1.                                 \n U--->        013400     MOVE MASK1  TO BIN1                                   \n              013410                    BIN2                                   \n              013500                    BIN3                                   \n              013600                    BIN4.                                  \n  --->        013700 TABLE-MOVE.                                               \n U--->        013736       MOVE TABLE-FILL TO WA-TABLE-1.                      \n  --->        013737 NUM-EDITED-TEST.                                          \n \nGT Command (Go to line)\nThe GT line command resumes program execution to the line on which you entered the GT command. The command\nputs a temporary breakpoint on the specified line and resumes execution. When the temporary breakpoint is reached, the\nbreakpoint is removed.\nIf the temporary breakpoint is still active at the time of intercept, the specified line is denoted as \u201cT\u201d. The temporary\nbreakpoints are also displayed on the breakpoint panel.\nThe GT command overrides the existing conditional breakpoint on the specified line. The command honors all breakpoints\nduring execution.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a236690eb24e-2", "text": "during execution.\nIf multiple GT commands are entered, the execution is resumed until the first GT line is reached and other GT commands\nare treated as temporary breakpoints.\n 669", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "15a25c6b66c6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo reset a temporary breakpoint that was created by a GT command, use the OFF, O, X, or blank line commands.\nCAMRCOB  ---------- CA-InterTest Batch TEMP BP Intercept --------------------- \nCOMMAND ===>                                                  SCROLL ===> CUR \n0001 000886            MOVE  R1498-TIMEI TO R1498-TIME.                       \n ---> 000887            PERFORM TIME-EDIT THRU TIME-EDIT-EX.                   \n      000888       *                                                           \n ---> 000889            MOVE  R1498-TIMEO TO R1498-TIME.                       \n ---> 000890            PERFORM TIME-EDIT THRU TIME-EDIT-EX.                   \n ---> 000891            GO TO DISPLAY-1ST-PANEL.                               \n      000892       * -----------------------------------------------*          \n      000893       *    THIS ROUTINE EDITS INPUT TIME FOR VALIDITY  *          \n      000894       * -----------------------------------------------*          \nGT--> 000895        TIME-EDIT.                                                 \n ---> 000896            IF    R1498-TIME IS NOT NUMERIC                        \n ---> 000897                  MOVE 'B' TO R1498-STATUS                         \n      000898            ELSE                                                   \n ---> 000899                  IF  R1499-HH < 25                                \n ---> 000900                      IF R1499-MM < 60                             \n ---> 000901                          IF R1498-TIME NOT > 2359                 \n ---> 000902                               MOVE 'G' TO R1498-STATUS            \n      000903                          ELSE                                     \n ---> 000904                               MOVE 'T' TO R1498-STATUS            \n      000905                      ELSE                                         \n ---> 000906                               MOVE 'M' TO R1498-STATUS            \n      000907                  ELSE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "15a25c6b66c6-1", "text": "000907                  ELSE                                             \n ---> 000908                      MOVE 'H' TO R1498-STATUS.                    \n ---> 000909        TIME-EDIT-EX.                                              \n ---> 000910            EXIT.\nH Command (Display Hex Data)\nFor COBOL or PL/I programs, the H line command causes a data item to be displayed in hexadecimal format for any\ndata items contained on the line where you type the H. See the LDX command in the Control Commands section that\nfollows for further explanation of the display. For assembler programs, the H line command displays the operands for\nthe current instruction in register notation. For assembler programs, there is no functional difference between the H\nline command and the K line command. The number of H's that you specify is limited only by the number of data items\ndisplayed, because of the screen size.\nCursor-sensitive hex display: If you enter H and the cursor is placed on a COBOL or PL/I data item in that line, pressing\nEnter displays in hexadecimal format only that data item and data items to the right of that item on the same line.\nYou may reset the hex displays using the RDI command or the R line command.\nNOTE\nYou cannot modify the zones and numerics portion of the data display. You also cannot modify group items.\nIn the following panel, the program has stopped executing because of an S0C7 abend as shown at the top of the Intercept\npanel. You have typed an H on line 13200 where the ABEND occurred to view the data items from that line. If you press\nEnter, it causes the line command to process.\nCAMRCOB2 ---------- CA InterTest Batch ABEND S0C7 Intercept ------------------\nCOMMAND ===>                                                  SCROLL===> PAGE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "15a25c6b66c6-2", "text": "COMMAND ===>                                                  SCROLL===> PAGE  \n TRACE=> 013200 013100 020100 020000 012900 012800 012700 012600 012500 012400 \n          7        CAMRCOB2        15.49.31        JUN 30,2014      \n  0001         012300 PROCEDURE DIVISION USING PARMS TEST-THREE TEST-FOUR PASS-\n 670", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "51fb9b96c9db-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  0001         012400 DEMO-BEGIN.                                 \n  0001         012500     GO TO DEMO-INIT.                        \n  0001         012600 DEMO-INIT.                                  \n  0001         012700     OPEN OUTPUT OUTPUT01.                            \n  0001         012800     MOVE HD1 TO LINE-OUT.                            \n  0001         012900     PERFORM WRITE-LINE.                              \n \n U0001         013100 FORCING-THE-ABEND.                                   \n h0001         013200     MOVE MASK1  TO BIN1.                             \n  --->         013300     MOVE ZERO   TO MASK1.                            \n U--->         013400     MOVE MASK1  TO BIN1                               \n               013410                    BIN2                               \n               013500                    BIN3                               \n               013600                    BIN4.                             \n  --->         013700 TABLE-MOVE.                                          \n U--->         013736       MOVE TABLE-FILL TO WA-TABLE-1.                 \n  --->         013737 NUM-EDITED-TEST.                                     \nThe following panel shows the hex data displays for the data items, MASK1 and BIN1, on line 13200. From the displayed\ndata items, you should be able to determine the cause of the ABEND. A character field, MASK1, filled with blanks (X'40')\nis being moved to a numeric binary field. You could then use the SET command to change MASK1 to an acceptable\nnumeric value.\n CAMRCOB2 ---------- CA InterTest Batch ABEND S0C7 Intercept ------------------\n COMMAND ===>                                                  SCROLL===> PAGE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "51fb9b96c9db-1", "text": "COMMAND ===>                                                  SCROLL===> PAGE    \n TRACE=> 013200 013100 020100 020000 012900 012800 012700 012600 012500 012400 \n       ------------------------------------------------------------------------   \n       00243DA0 AN    004000 03 MASK1                                             \n                DATA OCCUPIES 0002 BYTES OF STORAGE     ZONES 44                  \n                                                     NUMERICS 00                  \n \n       00243DB2 NB-S  004600 03 BIN1                          +00000000.         \n                DATA OCCUPIES 0004 BYTES OF STORAGE     ZONES 0000                \n                                                     NUMERICS 0000             \n       ------------------------------------------------------------------------   \n          7        CAMRCOB2        15.49.31        JUN 30,2014                    \n  0001         012300 PROCEDURE DIVISION USING PARMS TEST-THREE TEST-FOUR PASS-   \n  0001         012400 DEMO-BEGIN.                                                \n  0001         012500     GO TO DEMO-INIT.                                       \n  0001         012600 DEMO-INIT.                                                 \n  0001         012700     OPEN OUTPUT OUTPUT01.                                  \n  0001         012800     MOVE HD1 TO LINE-OUT.                                  \n  0001         012900     PERFORM WRITE-LINE.                                    \n \n U0001         013100 FORCING-THE-ABEND.                                         \n \n  0001         013200     MOVE MASK1  TO BIN1.                                   \n  --->         013300     MOVE ZERO   TO MASK1. \n U--->         013400     MOVE MASK1  TO BIN1", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "51fb9b96c9db-2", "text": "U--->         013400     MOVE MASK1  TO BIN1                                     \nFor assembler programs, if you use the H line command within the keep window, the high half of the 64bit register is\ndisplayed in a short message at the top of the screen. The following panel shows the short message displayed when the\nH command is used in the keep window:\n 671", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2500476bcef9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMEMTEST  ---------- CA InterTest Batch *INITIAL* Inte- High Half = 00000001    \nCOMMAND ===>                                                  SCROLL ===> CSR  \nTRACE=> 000060 000059 000058 000056 000055 000050 000049 000048 000047 000046 0\n      ------------------------------------------------------------------------- \n      00000000 HX    000000 02 R1                           000000000000000000 \n      ------------------------------------------------------------------------- \n 0001 000096 900F 1000            00000    59          STM   R0,R15,0(R1)     \n ---> 00009A EB0F 1040 0026       00040    60          STMH  R0,R15,64(R1)    \n ---> 0000A0 9B0F 1080            00080    61          STAM  R0,R15,128(R1)   \nI Command (Display Full Frequency Count Information)\nIn instances where a frequency count for a line exceeds 9999, the I line command displays the actual count at the top\nright of the screen. After typing I to the left of the line, press Enter to display the frequency count.\nThe following panel shows the actual frequency count for a line number that has exceeded 9999 executions:\nCARMCOB2 ---------- CA InterTest Batch WHEN LOOPCOND BEFORE Inte Executed 10000\nCommand ===>                                                    Scroll===> CUR \nTRACE=> 001151 001150 001149 001148 001162 001155 001154 001153 001151 001150 0\n U0001   001141               ORDER-CALC.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2500476bcef9-1", "text": "U0001   001141               ORDER-CALC.                                     \n  0001   001142                   MOVE CUSTOMER-VALUES TO CUSTOMER-ORDER.     \n  0001   001143                   MOVE ZEROES TO ORDER-SUB-TOTAL, SUB-6, LOOP-O\n  0001   001144                   PERFORM TOTAL-ORDER THRU TOTAL-ORDER-EX      \n         001145                       UNTIL SUB-6 EQUAL 5.                    \n U--->   001146               ORDER-CALC-EX.                                  \n  --->   001147                   GO TO OPTIONS.                              \n  0101   001148               TOTAL-ORDER.                                    \n I010K   001149                   ADD 1 TO SUB-6.                             \n  0101   001150                   ADD 1 TO LOOP-OUT.                          \n  0100   001151                   MULTIPLY UNIT-PRICE(SUB-6) BY NO-OF-WIDGETS(S\n         001152                       GIVING ITEM-TOTAL.                      \n  0100   001153                   ADD ITEM-TOTAL TO ORDER-SUB-TOTAL.          \n  0100   001154                   MOVE 1 TO SUB-6.                            \n       PP 5668-958 IBM VS COBOL II Release 3.2 09/05/90                COB2DEMR\nFor assembler, if you use the I line command within the keep window the access register of the item is displayed in a short\nmessage at the top of the screen. The following panel shows the short message displayed when you use the A command\nin the keep window.\nTESTAR   ---------- CA InterTest Batch ABEND S0C7 Int- ALET ===>  00010004    \nCOMMAND ===>                                                  SCROLL ===> CSR", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2500476bcef9-2", "text": "COMMAND ===>                                                  SCROLL ===> CSR  \nTRACE=> 000060 000059 000058 000056 000055 000050 000049 000048 000047 000046 0\n      ------------------------------------------------------------------------- \n      00000000 HX    000000 02 R1                           000000000000000000.\n      ------------------------------------------------------------------------- \n 0001 000096 900F 1000            00000    59          STM   R0,R15,0(R1)     \n ---> 00009A EB0F 1040 0026       00040    60          STMH  R0,R15,64(R1)    \n ---> 0000A0 9B0F 1080            00080    61          STAM  R0,R15,128(R1)   \nL or K Command (Display Data Item in a Keep Window)\nFor COBOL or PL/I programs, the L line command causes a data item to be displayed on the Intercept panel for any data\nitems contained on the line where the L is typed. For assembler programs, the L line command displays the operands\nfor the current instruction in register notation. This is commonly known as a keep window. For more information on LDI\n 672", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5418220ea78f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\ncommands, see the LDI (or KEEP) command in the Control Commands section that follows. The number of L's you can\nspecify is limited only by the number of data items displayed because of the screen size.\nCursor-sensitive keep: If you enter L or K and the cursor is placed on a COBOL or PL/I data item in that line, pressing\nEnter lists in the keep window only that data item and data items to the right of that item on the same line.\nThe LDI (or keep window) displays may be reset using the remove all  command or the R line command.\nNOTE\nElementary items are modifiable from within the keep window.\nIn the following panel the program has stopped at a breakpoint. To display all the data items in the MOVE statement, you\nmust type a K on each of the lines on which the statement occurs. In this case, you must type K on lines 13400, 13410,\n13500, and 13600. Pressing Enter causes the command to process.\n CAMRCOB2 ---------- CA InterTest Batch NEXT BEFORE Intercept -----------------\n COMMAND ===>                                                  SCROLL===> PAGE    \n TRACE=> 013400 013300 013200 013100 020100 020000 012900 012800 012700 012600    \n          7        CAMRCOB2        15.49.31        JUN 30,2014                    \n  0001        012300 PROCEDURE DIVISION USING PARMS TEST-THREE TEST-FOUR PASS-    \n  0001        012400 DEMO-BEGIN.                                                 \n  0001        012500     GO TO DEMO-INIT.                                        \n  0001        012600 DEMO-INIT.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5418220ea78f-1", "text": "0001        012600 DEMO-INIT.                                                  \n  0001        012700     OPEN OUTPUT OUTPUT01.                                   \n  0001        012800     MOVE HD1 TO LINE-OUT.                                   \n  0001        012900     PERFORM WRITE-LINE.                                     \n \n U0001        013100 FORCING-THE-ABEND.                                          \n  0001        013200     MOVE MASK1  TO BIN1.                                    \n  0001        013300     MOVE ZERO   TO MASK1.                                   \n k--->        013400     MOVE MASK1  TO BIN1                                      \n k            013410                    BIN2                                      \n k            013500                    BIN3                                      \n k            013600                    BIN4.                                    \n  --->        013700 TABLE-MOVE.                                                 \n U--->        013736       MOVE TABLE-FILL TO WA-TABLE-1.                        \n  --->        013737 NUM-EDITED-TEST.                                            \nThe following panel shows the keep window displays for data items MASK1, BIN1, BIN2, BIN3, and BIN4:\n CAMRCOB2 ---------- CA InterTest Batch NEXT BEFORE Intercept -----------------\n COMMAND ===>                                                  SCROLL===> PAGE \n TRACE=> 013400 013300 013200 013100 020100 020000 012900 012800 012700 012600 \n       ------------------------------------------------------------------------\n       00204DA0 AN    004000 03 MASK1                         00               \n       00204DB2 NB-S  004600 03 BIN1                          +00000001.      \n       00204DB6 NB-S  004700 03 BIN2                          +00000016.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5418220ea78f-2", "text": "00204DBA NB-S  004800 03 BIN3                          +00000032.      \n       00204DBE NB-S  004900 03 BIN4                          +00000077.      \n       ------------------------------------------------------------------------\n          7        CAMRCOB2        15.49.31        JUN 30,2014                 \n  0001         012300 PROCEDURE DIVISION USING PARMS TEST-THREE TEST-FOUR PASS-\n  0001         012400 DEMO-BEGIN.                                             \n  0001         012500     GO TO DEMO-INIT.                                    \n  0001         012600 DEMO-INIT.                                              \n  0001         012700     OPEN OUTPUT OUTPUT01.                               \n 673", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dab9f370e394-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  0001         012800     MOVE HD1 TO LINE-OUT.                               \n  0001         012900     PERFORM WRITE-LINE.\n U0001         013100 FORCING-THE-ABEND.                                      \n  0001         013200     MOVE MASK1  TO BIN1.                                \n  0001         013300     MOVE ZERO   TO MASK1.                               \n U--->         013400     MOVE MASK1  TO BIN1                                  \n               013410                    BIN2                                  \nO or X Command (Turn Off Breakpoints)\nThe O or X line command removes a breakpoint that is set for the line on which it is typed. A blank in the first field on\na line also resets the breakpoint. The O line command should only be used on lines that contain a U, ), or S in the first\ncolumn (where a breakpoint is set). An O on any other line has no effect. The number of O commands that may be\nprocessed is limited only by the display screen size.\nC, W, and V line commands are not displayed and therefore cannot be removed with an O or X.\nNOTE\nX is a synonym of the R line command when it is used in the keep window. When it is used on a source line, X is\na synonym of the O line command.\nIn the following panel, you have entered an O line command on lines 13400 and 13736 by typing over the U's in the first\ncolumn:\n CAMRCOB2 ---------- CA InterTest Batch NEXT BEFORE Intercept -----------------  \n COMMAND ===>                                                  SCROLL===> PAGE    \n TRACE=> 013400 013300 013200 013100 020100 020000 012900 012800 012700 012600", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dab9f370e394-1", "text": "7        CAMRCOB2        15.49.31        JUN 30,2014                    \n  0001        012300 PROCEDURE DIVISION USING PARMS TEST-THREE TEST-FOUR PASS-    \n  0001        012400 DEMO-BEGIN.                                                 \n  0001        012500     GO TO DEMO-INIT.                                         \n  0001        012600 DEMO-INIT.                                                   \n  0001        012700     OPEN OUTPUT OUTPUT01.                                    \n  0001        012800     MOVE HD1 TO LINE-OUT.                                    \n  0001        012900     PERFORM WRITE-LINE.                                      \n \n U0001        013100 FORCING-THE-ABEND.                                           \n  0001        013200     MOVE MASK1  TO BIN1.                                     \n  0001        013300     MOVE ZERO   TO MASK1.                                    \n o--->        013400     MOVE MASK1  TO BIN1                                      \n              013410                    BIN2                                      \n              013500                    BIN3                                      \n              013600                    BIN4.                                     \n  --->        013700 TABLE-MOVE.                                                  \n o--->        013736       MOVE TABLE-FILL TO WA-TABLE-1.                         \n  --->        013737 NUM-EDITED-TEST.                                             \nAfter you press Enter, the U's are no longer on the lines. This indicates that the breakpoints have been reset as shown in\nthe following panel:\n CAMRCOB2 ---------- CA InterTest Batch NEXT BEFORE Intercept ----------------- \n COMMAND ===>                                                  SCROLL===> PAGE    \n TRACE=> 013400 013300 013200 013100 020100 020000 012900 012800 012700 012600", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dab9f370e394-2", "text": "7        CAMRCOB2        15.49.31        JUN 30,2014                    \n  0001        012300 PROCEDURE DIVISION USING PARMS TEST-THREE TEST-FOUR PASS-    \n  0001        012400 DEMO-BEGIN.                                                  \n 674", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b76a9d8715b6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  0001        012500     GO TO DEMO-INIT.                                         \n  0001        012600 DEMO-INIT.                                                   \n  0001        012700     OPEN OUTPUT OUTPUT01.                                    \n  0001        012800     MOVE HD1 TO LINE-OUT.                                    \n  0001        012900     PERFORM WRITE-LINE.                                      \n \n U0001        013100 FORCING-THE-ABEND.                                           \n  0001        013200     MOVE MASK1  TO BIN1.                                     \n  0001        013300     MOVE ZERO   TO MASK1.\n  --->        013400     MOVE MASK1  TO BIN1                                      \n              013410                    BIN2                                      \n              013500                    BIN3                                      \n              013600                    BIN4.                                     \n  --->        013700 TABLE-MOVE.                                                  \n  --->        013736       MOVE TABLE-FILL TO WA-TABLE-1.                         \n  --->        013737 NUM-EDITED-TEST.                                             \nYou can confirm that you reset the breakpoints by using the LISTAT command to produce the Breakpoint Status panel.\nP Command (Print Display)\nFor COBOL or PL/I programs, the P line command writes the display in the session log for all the data items on the\nline where you typed the command. For assembler programs, the P line command prints the operands for the current\ninstruction in register notation. The data is written as it would be displayed using the D line command. For a description of\nthe Display Panel, see Data Display Panels in Debugging Panels.\nYou can type the P line command on any line in the program listing. You can enter multiple P commands on different lines.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b76a9d8715b6-1", "text": "For further description and a sample of the session log, see Session Log Facility (Review Debugging Session) at the end\nof this section.\nR Command (Reset Data Item Display)\nThe R line command resets a data item display from an LDI command, an L line command, an LDX command, or an H\nline command. Place the R line command on a line on the program listing to reset all the data items on that line for which\nList Data Item displays are present, or place it directly on a listed data item display to reset that display.\nNOTE\nX is a synonym of the R line command when it is used in the keep window. When it is used on a source line, X is\na synonym of the O line command.\nIn the following panel, an LDI has been done for MASK1 and BIN1, and an LDX has been done for BIN2. By placing an R\non the data item display for BIN1 and line 13410 containing BIN2, these data items are reset after  you press Enter.\n CAMRCOB2 ---------- CA InterTest Batch NEXT BEFORE Intercept ----------------- \n COMMAND ===>                                                  SCROLL===> PAGE    \n TRACE=> 013400 013300 013200 013100 020100 020000 012900 012800 012700 012600    \n       ------------------------------------------------------------------------\n       00204DA0 AN    004000 03 MASK1                         00                  \n r     00204DB2 NB-S  004600 03 BIN1                          +00000001.          \n       00204DB6 NB-S  004700 03 BIN2                          +00000016.          \n                DATA OCCUPIES 0004 BYTES OF STORAGE     ZONES 0001                \n                                                     NUMERICS 0000             \n       ------------------------------------------------------------------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b76a9d8715b6-2", "text": "NUMERICS 0000             \n       ------------------------------------------------------------------------   \n          7        CAMRCOB2        15.49.31        JUN 30,2014                    \n  0001        012300 PROCEDURE DIVISION USING PARMS TEST-THREE TEST-FOUR PASS-    \n 675", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "734c330ba4c6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  0001        012400 DEMO-BEGIN.                                                  \n  0001        012500     GO TO DEMO-INIT.                                         \n  0001        012600 DEMO-INIT.                                                   \n  0001        012700     OPEN OUTPUT OUTPUT01.                                    \n  0001        012800     MOVE HD1 TO LINE-OUT.                                    \n  0001        012900     PERFORM WRITE-LINE.                                      \n \n U0001        013100 FORCING-THE-ABEND.                                           \n  0001        013200     MOVE MASK1  TO BIN1.                                     \n  0001        013300     MOVE ZERO   TO MASK1.                                    \n \n  --->        013400     MOVE MASK1  TO BIN1                                      \n r            013410                    BIN2                                      \nThe following panel shows the results of the R line commands. The BIN1 and BIN2 displays have been reset, leaving only\nthe display for MASK1:\n CAMRCOB2 ---------- CA InterTest Batch NEXT BEFORE Intercept -----------------\n COMMAND ===>                                                  SCROLL===> PAGE \n TRACE=> 013400 013300 013200 013100 020100 020000 012900 012800 012700 012600 \n       ------------------------------------------------------------------------\n       00204DA0 AN    004000 03 MASK1                         00               \n       ------------------------------------------------------------------------\n          7        CAMRCOB2        15.49.31        JUN 30,2014                 \n  0001        012300 PROCEDURE DIVISION USING PARMS TEST-THREE TEST-FOUR PASS- \n  0001        012400 DEMO-BEGIN.                                               \n  0001        012500     GO TO DEMO-INIT.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "734c330ba4c6-1", "text": "0001        012500     GO TO DEMO-INIT.                                      \n  0001        012600 DEMO-INIT.                                                \n  0001        012700     OPEN OUTPUT OUTPUT01.                                 \n  0001        012800     MOVE HD1 TO LINE-OUT.                                 \n  0001        012900     PERFORM WRITE-LINE.                                   \n \n U0001        013100 FORCING-THE-ABEND.                                        \n  0001        013200     MOVE MASK1  TO BIN1.                                  \n  0001        013300     MOVE ZERO   TO MASK1.                                 \n \n  --->        013400     MOVE MASK1  TO BIN1                                   \n              013410                    BIN2                                   \n              013500                    BIN3                                   \n              013600                    BIN4.                                  \n  --->        013700 TABLE-MOVE.                                               \n  --->        013736       MOVE TABLE-FILL TO WA-TABLE-1.                      \nS Command (Skip this Statement)\nThe S (Skip) line command when placed directly next to a statement causes the statement to be skipped when the\nprogram is executing. The S remains on the line to show you which statements are not executed. Skip is considered an\nunconditional breakpoint.\nYou may type other commands over the S. To cancel a Skip line command use a blank, X, or O line command. If you use\nOFF ALL to remove all breakpoints, all skip conditions are also removed.\nWARNING\nWhen a program has been optimized, or when the statement being skipped is any of the following, the S (Skip)\nline command may have undesired results:\n 676", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a84e0dbdc8cf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe last statement in the program\n\u2022The last statement in a performed paragraph\n\u2022Immediately followed by an ELSE statement\nFor more details, see the SKIP Command (Skip a Statement).\nThe following panel shows a skip breakpoint being set at statement 21010. The S causes the call to the program A1 to be\nskipped as the program is executed:\nCAMRCOB2 ---------- CA InterTest Batch *INITIAL* Intercept -------------------\nCOMMAND ===>                                                   SCROLL===> HALF \nTRACE=> 020400                                                                   \n         8                        17.28.55        MAR 10,2014                    \n *-->        020400 PROCEDURE DIVISION USING PARMS TEST-THREE TEST-FOUR PASS-    \n *-->        020500 DEMO-BEGIN.                                                  \n *-->        020600     GO TO DEMO-INIT.                                         \n *-->        020700 DEMO-INIT.                                                   \n *-->        020800     OPEN OUTPUT OUTPUT01.                                    \n *-->        020900     MOVE HD1 TO LINE-OUT.                                    \n *-->        021000     PERFORM WRITE-LINE.                                      \nS*-->        021010     CALL 'A1'.                                               \n *-->        021020     CALL 'A2'.                                               \n \nU*-->        021200 FORCING-THE-ABEND.                                          \n *-->        021300     MOVE MASK1  TO BIN1.                                     \n *-->        021310     DISPLAY MASK1 BIN1 BIN2 BIN3 BIN4.                       \n *-->        021400     MOVE ZERO   TO MASK1.                                    \n *-->        021500     MOVE MASK1  TO BIN1                                      \n             021600                    BIN2                                      \n             021700                    BIN3                                      \n             021800                    BIN4.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a84e0dbdc8cf-1", "text": "021700                    BIN3                                      \n             021800                    BIN4.                                     \n *-->        021900     IF BIN1 = BIN2                                           \n             022000       NEXT SENTENCE.                                         \nThe following panel shows what the program looks like after you have used the GO command to resume program\nexecution. The program is intercepted by the breakpoint on line 21200. Note that there is no frequency counter on\nstatement 21010. This statement was not executed.\nCAMRCOB2 ---------- CA InterTest Batch UNCOND BEFORE Intercept --------------- \nCOMMAND ===>                                                   SCROLL===> HALF   \nTRACE=> 021200 021020 021000 020900 020800 020700 020600 020500 020400           \n         8                        17.28.55        MAR 10,2014                    \n 0001         020400 PROCEDURE DIVISION USING PARMS TEST-THREE TEST-FOUR PASS-   \n 0001         020500 DEMO-BEGIN.                                                 \n 0001         020600     GO TO DEMO-INIT.                                        \n 0001         020700 DEMO-INIT.                                                  \n 0001         020800     OPEN OUTPUT OUTPUT01.                                   \n 0001         020900     MOVE HD1 TO LINE-OUT.                                   \n 0001         021000     PERFORM WRITE-LINE.                                     \nS--->         021010     CALL 'A1'.                                              \n 0001         021020     CALL 'A2'.                                              \n \nU--->         021200    FORCING-THE-ABEND.                                       \n --->         021300     MOVE MASK1  TO BIN1.                                    \n 677", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8acfffa47b39-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n --->         021310     DISPLAY MASK1 BIN1 BIN2 BIN3 BIN4.                      \n --->         021400     MOVE ZERO   TO MASK1.                                   \n --->         021500     MOVE MASK1  TO BIN1                                     \n              021600                    BIN2                                     \n              021700                    BIN3                                     \n              021800                    BIN4.                                    \n --->         021900     IF BIN1 = BIN2                                          \n              022000       NEXT SENTENCE.                                        \nV Command (Set Variable Change Breakpoint)\nThe V line command sets a variable change breakpoint at the specified line. A when-name is automatically generated.\nThe name is VR nnnnnn  where n=line number of the breakpoint. This means you can have only one conditional set by\nthe V line command per line. The breakpoint is triggered before the line is executed when the application determines that\nthe value of a variable in the line changes. The condition is not checked before each verb. This command is only valid for\nCOBOL or PL/I programs.\nCursor-sensitive variable change breakpoint: If you enter V and the cursor is placed on a COBOL or PL/I data item,\npressing Enter designates that item as the variable change item.\nThe following panel shows variable change breakpoints being set on lines 1149 and 1154 of the program. You must press\nEnter after entering the breakpoints in order to set them:\nCAMRCOB2 ---------- CA InterTest Batch NEXT BEFORE Intercept -----------------\nCommand ===>                                                    Scroll===> CUR \nTRACE=> 001151 001150 001149 001148 001162 001155 001154 001153 001151 001150 0\n U0001   001141                ORDER-CALC.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8acfffa47b39-1", "text": "U0001   001141                ORDER-CALC.                                    \n  0001   001142                   MOVE CUSTOMER-VALUES TO CUSTOMER-ORDER.     \n  0001   001143                   MOVE ZEROES TO ORDER-SUB-TOTAL, SUB-6, LOOP-O\n  0001   001144                   PERFORM TOTAL-ORDER THRU TOTAL-ORDER-EX     \n         001145                        UNTIL SUB-6 EQUAL 5.                    \n U--->   001146                ORDER-CALC-EX.                                 \n  --->   001147                   GO TO OPTIONS.                             \n  0101   001148                TOTAL-ORDER.                                   \n v0101   001149                   ADD 1 TO SUB-6.                            \n  0101   001150                   ADD 1 TO LOOP-OUT.                         \n  0100   001151                   MULTIPLY UNIT-PRICE(SUB-6) BY NO-OF-WIDGETS(S\n         001152                        GIVING ITEM-TOTAL.                     \n  0100   001153                   ADD ITEM-TOTAL TO ORDER-SUB-TOTAL.         \n v0100   001154                   MOVE 1 TO SUB-6.                           \n        PP 5668-958 IBM VS COBOL II Release 3.2 09/05/90               CAMRCOB2\n        LineID  PL SL  ----+-*A-1-B--+----2----+----3----+----4----+----5----+-\n) Command (Set Unconditional \"After\" Breakpoints)\nThe ) line command performs the same function as the AT or UNCOND command. An unconditional \"after\" breakpoint\nis set on the line where the A or U is typed. The program stops after executing the statement. A ) displays on the line to", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8acfffa47b39-2", "text": "show you where breakpoints have been set. The ) line command is only valid on executable lines of the program listing.\nExecutable lines contain a frequency counter number or arrow. There is no limit other than the size of the screen. If you\npress Enter or the scroll keys, it sets the breakpoints.\nYou can type other commands over the ). Reset breakpoints using the OFF, O, X, or blank line commands.\nThe following panel shows an \"after\" breakpoint being set on line 13736 of the program:\n CAMRCOB2 ---------- CA InterTest Batch NEXT BEFORE Intercept -----------------\n 678", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "552b2bda1fd6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n COMMAND ===>                                                  SCROLL===> PAGE    \n TRACE= 012400 012300                                                            \n          7        CAMRCOB2        15.49.31        JUN 30,2014                    \n  0001        012300 PROCEDURE DIVISION USING PARMS TEST-THREE TEST-FOUR PASS-    \n  --->        012400 DEMO-BEGIN.                                                \n  --->        012500     GO TO DEMO-INIT.                                        \n  --->        012600 DEMO-INIT.                                                  \n  --->        012700     OPEN OUTPUT OUTPUT01.                                   \n  --->        012800     MOVE HD1 TO LINE-OUT.                                   \n  --->        012900     PERFORM WRITE-LINE.                                     \n \n u--->        013100 FORCING-THE-ABEND.                                          \n  --->        013200     MOVE MASK1  TO BIN1.                                    \n  --->        013300     MOVE ZERO   TO MASK1.                                   \n u--->        013400     MOVE MASK1  TO BIN1                                      \n              013410                    BIN2                                      \n              013500                    BIN3                                      \n              013600                    BIN4.                                    \n  --->        013700 TABLE-MOVE.                                                 \n )--->        013736       MOVE TABLE-FILL TO WA-TABLE-1.          \n  --->        013737 NUM-EDITED-TEST.                                            \n  --->        013738       MOVE IN-FUNC TO OUT-FUNC.                             \n  --->        013739       MOVE IN-FUNC TO OUT-FUNC2.                            \nPress Enter to set the breakpoints.\nThe listing appears as shown in the following panel. The line that has an \"after\" breakpoint set displays a ) in the first\ncolumn to show you where it is.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "552b2bda1fd6-1", "text": "column to show you where it is.\nCAMRCOB2 ---------- CA InterTest Batch NEXT BEFORE Intercept -----------------\nCOMMAND ===>                                                  SCROLL===> PAGE    \n TRACE=> 012400 012300                                                            \n          7        CAMRCOB2        15.49.31        JUN 30,2014                    \n  0001        012300 PROCEDURE DIVISION USING PARMS TEST-THREE TEST-FOUR PASS-    \n  --->        012400 DEMO-BEGIN.                                                \n  --->        012500     GO TO DEMO-INIT.                                        \n  --->        012600 DEMO-INIT.                                                  \n  --->        012700     OPEN OUTPUT OUTPUT01.                                   \n  --->        012800     MOVE HD1 TO LINE-OUT.                                   \n  --->        012900     PERFORM WRITE-LINE.                                     \n \n U--->        013100 FORCING-THE-ABEND.                                          \n  --->        013200     MOVE MASK1  TO BIN1. \n \n  --->        013300     MOVE ZERO   TO MASK1.                                   \n U--->        013400     MOVE MASK1  TO BIN1                                      \n              013410                    BIN2                                      \n              013500                    BIN3                                      \n              013600                    BIN4.                                    \n  --->        013700 TABLE-MOVE.                                                 \n )--->        013736       MOVE TABLE-FILL TO WA-TABLE-1.                        \n  --->        013737 NUM-EDITED-TEST. \n  --->        013738       MOVE IN-FUNC TO OUT-FUNC.\n  --->        013739       MOVE IN-FUNC TO OUT-FUNC2.                            \n 679", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c12d2332a156-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nYou can also use the LISTAT command to show the Breakpoints panel as follows:\n-------------------- CA InterTest Batch BREAKPOINTS PANEL ---------------------\nCOMMAND ===>                                                  SCROLL ===> CUR \n \n     *************************** Top of Data *********************************\n     UNCONDITIONAL BREAKPOINTS FOLLOW:                                        \n     PROGRAM   STMT#   COUNT  EXEC  B/A  COMMANDS TO BE EXECUTED              \n     --------  ------  -----  ----  ---  -------------------------------------\n.    CAMRCOB2  000589  0000   0000   B                                        \n     SOURCE LINE: SPLIT-SCREEN.                                               \n \n.    CAMRCOB2  000541  0000   0000   B                                        \n     SOURCE LINE: PAY-CALC.                                                   \n \n.    CAMRCOB2  000659  0000   0000   A                                        \n     SOURCE LINE: ORDER-CALC.                                                 \n ************************************* BOTTOM OF DATA *************************                               \n                                                      \n+ (plus) Command (Increment a Subscript)\nUse the plus (+) line command to increment the value of a subscript on a displayed data item. Display the data item using\nthe LDI or LDX control commands or the L or H line commands. The format of the command is + nnn where nnn is any\nnumber from 1 to 999. The subscript is incremented by the amount specified by nnn. The default is 1, and this is the value\nthat is used if  nnn is not specified. More than one subscript may be incremented or decremented at the same time. This\ncommand is only valid for COBOL or PL/I programs.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c12d2332a156-1", "text": "command is only valid for COBOL or PL/I programs.\nThe following panel shows a data display for WA-T1-3A(BIN1,4,1) of WA-TABLE-1 of WA-LEVEL1. Currently, WA-\nT1-3A(2,4,1) is displayed. Note the address and the value. The first subscript (BIN1) and the third subscript are\nincremented by the value of 2.\nCAMRCOB2 ---------- CA InterTest Batch UNCOND BEFORE Intercept --------------- \nCOMMAND ===>                                                   SCROLL===> HALF   \nTRACE=> 022300 022200 022100 021900 021500 021400 021310 021300 021200 021020    \n        -----------------------------------------------------------------------\n        00262E08 ND    016800 06 WA-T1-3A                    01.                 \n +2                              BIN1  (2)                                       \n                                 (4)                                            \n +2                              (1)                                            \n                               OF WA-TABLE-1                                     \n                               OF WA-LEVEL1                                     \n        ----------------------------------------------------------------------- \n \n 0001         021200 FORCING-THE-ABEND.                                          \n 0001         021300     MOVE MASK1  TO BIN1.                                    \n 0001         021310     DISPLAY MASK1 BIN1 BIN2 BIN3 BIN4.                      \n 0001         021400     MOVE ZERO   TO MASK1.                                   \n 0001         021500     MOVE MASK1  TO BIN1                                     \n              021600                    BIN2                                     \n              021700                    BIN3                                     \n              021800                    BIN4.                                    \n 0001         021900     IF BIN1 = BIN2                                          \n              022000       NEXT SENTENCE.                                        \n 680", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "459e3eb8e2f3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 0001         022100 TABLE-MOVE.                                                 \n 0001         022200       MOVE TABLE-FILL TO WA-TABLE-1 OF WA-LEVEL1.           \nU--->         022300 NUM-EDITED-TEST.                                            \n --->         022310       MOVE 'XP' TO ED-ALPHA.                                \nPressing Enter causes the line commands to be executed. The value of BIN1 and the value of the third subscript have\nbeen incremented by 2, so that WA-T1-3A(4,4,3) is now the table item displayed. Note that by incrementing the subscript\nvariable BIN1, the value of BIN1 has been changed to 4 as shown in the following panel:\nCAMRCOB2 ---------- CA InterTest Batch UNCOND BEFORE Intercept ---------------\nCOMMAND ===>                                                   SCROLL===> HALF \nTRACE=> 022300 022200 022100 021900 021500 021400 021310 021300 021200 021020  \n      ------------------------------------------------------------------------\n      00262E6C ND    016800 06 WA-T1-3A                    03.                 \n                                  BIN1  (4)                                    \n                                 (4)                                           \n                                 (3)                                           \n                               OF WA-TABLE-1                                   \n                               OF WA-LEVEL1                                   \n      ------------------------------------------------------------------------ \n \n 0001         021200 FORCING-THE-ABEND.                                        \n 0001         021300     MOVE MASK1  TO BIN1.                                  \n 0001         021310     DISPLAY MASK1 BIN1 BIN2 BIN3 BIN4.                    \n 0001         021400     MOVE ZERO   TO MASK1.                                 \n 0001         021500     MOVE MASK1  TO BIN1", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "459e3eb8e2f3-1", "text": "0001         021500     MOVE MASK1  TO BIN1                                   \n              021600                    BIN2                                   \n              021700                    BIN3                                   \n              021800                    BIN4.                                  \n 0001         021900     IF BIN1 = BIN2                                        \n              022000       NEXT SENTENCE.                                      \n 0001         022100 TABLE-MOVE.                                               \n 0001         022200       MOVE TABLE-FILL TO WA-TABLE-1 OF WA-LEVEL1.         \nU--->         022300 NUM-EDITED-TEST.                                          \n --->         022310       MOVE 'XP' TO ED-ALPHA.                              \n- (minus) Command (Decrement a Subscript)\nUse the minus (-) command to decrement the value of a subscript on a displayed data item. Display the data item using\nthe LDI or LDX control commands or the L or H line commands. The format of the command is - nnn where nnn is any\nnumber from 1 to 999. The subscript is decremented by the amount specified by nnn. The default is 1, and this is the\nvalue that is used if  nnn is not specified. You may increment or decrement more than one subscript at the same time. This\ncommand is only valid for COBOL or PL/I programs.\nThe following panel shows a data display for WA-T1-3A(BIN1,4,3) of WA-TABLE-1 of WA-LEVEL1. Currently, WA-\nT1-3A(4,4,3) is displayed. Note the address and the value. The first subscript (BIN1) is decremented by 3, and the second\nand third subscripts are decremented by 1:\nCAMRCOB2 ---------- CA InterTest Batch UNCOND BEFORE Intercept ---------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "459e3eb8e2f3-2", "text": "CAMRCOB2 ---------- CA InterTest Batch UNCOND BEFORE Intercept --------------- \nCOMMAND ===>                                                   SCROLL===> HALF \nTRACE=> 022300 022200 022100 021900 021500 021400 021310 021300 021200 021020  \n      ------------------------------------------------------------------------\n      00262E6C ND    016800 06 WA-T1-3A                    03.                 \n -3                               BIN1  (4)                                    \n -1                               (4)                                          \n 681", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "da9e9c2c8561-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n -1                               (3)                                          \n                               OF WA-TABLE-1                                   \n                               OF WA-LEVEL1                                   \n      ------------------------------------------------------------------------ \n \n 0001         021200 FORCING-THE-ABEND.                                        \n 0001         021300     MOVE MASK1  TO BIN1.                                  \n 0001         021310     DISPLAY MASK1 BIN1 BIN2 BIN3 BIN4.                    \n 0001         021400     MOVE ZERO   TO MASK1.                                 \n 0001         021500     MOVE MASK1  TO BIN1                                   \n              021600                    BIN2                                   \n              021700                    BIN3                                   \n              021800                    BIN4.                                  \n 0001         021900     IF BIN1 = BIN2                                        \n              022000       NEXT SENTENCE.                                      \n 0001         022100 TABLE-MOVE.                                               \n 0001         022200       MOVE TABLE-FILL TO WA-TABLE-1 OF WA-LEVEL1.         \nU--->         022300 NUM-EDITED-TEST.                                          \n --->         022310       MOVE 'XP' TO ED-ALPHA.                             \nPressing Enter causes the line commands to be executed. The value of BIN1 has been decremented by 3, and the\nsecond and third subscripts have been decremented by 1, so that WA-T1-3A(1,3,2) is now the table item displayed.\nNote that by decrementing the subscript variable BIN1, the value of BIN1 has been changed to 1 as shown in the following\npanel:\nCAMRCOB2 ---------- CA InterTest Batch UNCOND BEFORE Intercept ---------------\nCOMMAND ===>                                                   SCROLL===> HALF", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "da9e9c2c8561-1", "text": "COMMAND ===>                                                   SCROLL===> HALF\nTRACE=> 022300 022200 022100 021900 021500 021400 021310 021300 021200 021020\n        -----------------------------------------------------------------------\n        00262DCF ND    016800 06 WA-T1-3A                    02.             \n                                  BIN1  (1)                                  \n                                  (3)                                        \n                                  (2)                                        \n                               OF WA-TABLE-1                                 \n                               OF WA-LEVEL1                                  \n        -----------------------------------------------------------------------\n \n 0001         021200 FORCING-THE-ABEND.                                      \n 0001         021300     MOVE MASK1  TO BIN1.                                \n 0001         021310     DISPLAY MASK1 BIN1 BIN2 BIN3 BIN4.                  \n 0001         021400     MOVE ZERO   TO MASK1.                                  \n 0001         021500     MOVE MASK1  TO BIN1                                    \n              021600                    BIN2                                    \n              021700                    BIN3                                    \n              021800                    BIN4.                                   \n 0001         021900     IF BIN1 = BIN2                                         \n              022000       NEXT SENTENCE.                                       \n 0001         022100 TABLE-MOVE.                                                \n 0001         022200       MOVE TABLE-FILL TO WA-TABLE-1 OF WA-LEVEL1.          \nU0001         022300 NUM-EDITED-TEST.                                           \n 682", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5972521b97f4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n< nnnn (Scroll Left) Command\nThe scroll left (<) command is used to scroll data in the keep window left. The format of the command is <[ nnnn ] where\nnnnn  is any number from 1 to 9999. If the data length is greater than the display area, the data is scrolled the number of\nbytes indicated by nnnn . Data cannot be scrolled beyond the length of the data item. If the nnnn  value is greater than the\nlength of the data item, the display is positioned at the last n number of bytes that fit in the display area.\nThe following panel shows a data item scrolled left 5 bytes:\nCAMRCOB2 ---------- CA InterTest Batch *INITIAL* Intercept -------------------\nCOMMAND ===>                                                  SCROLL ===> CSR\nTRACE=>                                                                       \n      -------------------------------------------------------------------------\n      1F0A9630       000838 01 TRL-TABLE                                     \n      1F0A9635 AN    000839 03 FILLER               (+0005) EFGHIJKLMNOPQRSTUV\n      1F0A964B AN    000841 03 FILLER                       1234567890       \n      1F0A9655 AN    000843 03 FILLER                       -+=.,;:#*/()@&%$\u00a2?\n      -------------------------------------------------------------------------\n      000875        PROCEDURE DIVISION USING PARAMETER-AREA.                  \n *--> 000876        START-PROGRAM.                                            \n *--> 000877            OPEN OUTPUT REPORT-OUT.                               \n      000878       * -----------------------------------------------*         \n      000879       * Welcome to the CA InterTest Batch COBOL II     *         \n      000880       * Demonstration Program. You are now at the      *", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5972521b97f4-1", "text": "000880       * Demonstration Program. You are now at the      *         \n      000881       * Initial Breakpoint panel which is displayed    *         \n      000882       * upon entry to the first program to be tested.  *         \n      000883       * At this point, other breakpoints can be set    *         \n      000884       * and control commands can be issued before  the *         \n      000885       * program is executed.                           *         \n      000886       * -----------------------------------------------*         \n *--> 000887            MOVE  R1498-TIMEI TO R1498-TIME.                      \n *--> 000888            PERFORM TIME-EDIT THRU TIME-EDIT-EX.                  \n      000889       *                                                          \n *--> 000890            MOVE  R1498-TIMEO TO R1498-TIME.                      \n *--> 000891            PERFORM TIME-EDIT THRU TIME-EDIT-EX.                  \n *--> 000892            GO TO DISPLAY-1ST-PANEL.                              \nNote: Scrolling starts from relative zero. In the previous example the displayed character \u201cE\u201d is at real\n position 6 (+0005 relative to 0).\n> nnnn (Scroll Right) Command\nThe scroll right (>) command is used to scroll data in the keep window right. The format of the command is >[ nnnn ] where\nnnnn  is any number from 1 to 9999. If the data length is greater than the display area, the data is scrolled the number of\nbytes indicated by nnnn . Data cannot be scrolled beyond the length of the data item. If the nnnn  value is greater than the\nlength of the data item, the display is positioned at the first n number of bytes that fit in the display area.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5972521b97f4-2", "text": "The following panel shows a data item scrolled right 3 bytes:\nCAMRCOB2 ---------- CA InterTest Batch *INITIAL* Intercept -------------------\nCOMMAND ===>                                                  SCROLL ===> CSR\nTRACE=>                                                                       \n      -------------------------------------------------------------------------\n      1F0A9630       000838 01 TRL-TABLE                                     \n      1F0A9632 AN    000839 03 FILLER               (+0002) BCDEFGHIJKLMNOPQRS\n      1F0A964B AN    000841 03 FILLER                       1234567890       \n 683", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f834915cd30f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n      1F0A9655 AN    000843 03 FILLER                       -+=.,;:#*/()@&%$\u00a2?\n      -------------------------------------------------------------------------\n      000875        PROCEDURE DIVISION USING PARAMETER-AREA.                  \n *--> 000876        START-PROGRAM.                                            \n *--> 000877            OPEN OUTPUT REPORT-OUT.                               \n      000878       * -----------------------------------------------*         \n      000879       * Welcome to the CA InterTest Batch COBOL II     *         \n      000880       * Demonstration Program. You are now at the      *         \n      000881       * Initial Breakpoint panel which is displayed    *         \n      000882       * upon entry to the first program to be tested.  *         \n      000883       * At this point, other breakpoints can be set    *         \n      000884       * and control commands can be issued before  the *         \n      000885       * program is executed.                           *         \n      000886       * -----------------------------------------------*         \n *--> 000887            MOVE  R1498-TIMEI TO R1498-TIME.                      \n *--> 000888            PERFORM TIME-EDIT THRU TIME-EDIT-EX.                  \n      000889       *                                                          \n *--> 000890            MOVE  R1498-TIMEO TO R1498-TIME.                      \n *--> 000891            PERFORM TIME-EDIT THRU TIME-EDIT-EX.                  \n *--> 000892            GO TO DISPLAY-1ST-PANEL.                              \nNOTE\nScrolling starts from relative zero. In the previous example the displayed character \u201cB\u201d is at real position 3\n(+0002 relative to 0)\nControl Commands", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f834915cd30f-1", "text": "(+0002 relative to 0)\nControl Commands\nUse Control commands to control the test session.\nTo use Control commands to control the test session, enter the Control commands on the command line of the Intercept\npanel. To enter multiple control commands on the command line, separate the commands with semicolons (;).\nAssembler Indirect Addressing Note : Some control commands can accept an expression in  register notation when\ndebugging an assembler program. The format of an expression is as follows:\n <base <suffix>> <<offset<suffix>>...>\n \nOperands Description\nbase hexadecimal address, or\nregister number (that is, R1 for general register 1), or\na data name\nsuffix % for indirect addressing in 24 bit mode\n? for indirect addressing in 31 bit mode\n! for indirect addressing in 64 bit mode\noffset plus (+) or minus (-) a hexadecimal value up to 4 characters long\nNOTE\nWhen starting an expression with a hexadecimal address, it must start with a plus (+) sign.\n 684", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "76e9b98cd32e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe following table shows a list of control commands available when using your product:\nCommand Definition\nADVANCE Follows the trace pointers forward.\nAT Sets an unconditional breakpoint (same as UNCOND).\nCORE Displays memory for the debugging region.\nCOUNTS Enables frequency counting, reset counters, display counters.\nCS Highlights the current statement.\nDATAMON Enables the data monitoring feature.\nDDALLOC Allocates a DD.\nDDFREE Frees a DD.\nDDQ Queries a DD.\nDISPLAY Formats a data item or the COBOL Working Storage section.\nDROP Drops the symbolic name.\nDROPUSE Removes a using that was set with the USING command.\nDUMP Terminates testing with a dump.\nEQUATE Specifies symbolic name.\nEXSUM Provides the execution summary display.\nFILES Displays COBOL FD status.\nFM Starts File Master Plus .\nFREQ Controls verb execution counts.\nGO Resumes execution of the application.\nGOTO Resumes execution until the specified line.\nINCLUDE Executes a set of application commands.\nLDA (or AUTOKEEP) Displays all data items referenced by the current statement.\nLDI (or KEEP) Lists data item.\nLDX (or KEEPX) Lists data item in hexadecimal.\nLEQ Lists equated symbolic names.\nLINKAGE Formats the COBOL LINKAGE section.\nLISTAT Lists breakpoints.\nLISTBP Displays the BREAKPOINT panel.\nLISTLBL Lists labels added with the .label command.\nLISTUSE Displays the USING STATUS panel.\nLISTWHEN Lists WHEN conditions.\nMAP Invokes the Region Map Display panel.\nMLOG Records a debugging session.\nNEXT Executes the next n verbs.\nNOFREQ Removes frequency counters.\nOFF (or OFFU) Removes unconditional breakpoints.\nOFFWN (or OFFC) Removes conditional breakpoints.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "76e9b98cd32e-1", "text": "OFFWN (or OFFC) Removes conditional breakpoints.\nPOINT Directs PREVIOUS and ADVANCE pointer.\nPREV Follows trace pointers in reverse.\n 685", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e4fed76b9e3d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPS Prints stream to session log.\nQUALIFY Sets current program id.\nQUIT Terminates the test session.\nRDI Resets data item (or REMOVE).\nRECORDS Formats data in the COBOL FILE section.\nREFRESH Displays updated split screen values.\nREGS Displays registers for assembler programs.\nRESET Removes column numbers from display.\nRESTART Restarts a batch link debugging step.\nRUN Removes breakpoints and execute.\nSDWA Displays the system diagnostic work area.\nSET Changes value of a data item.\nSKIP Skips a statement.\nSLOW Observes execution a verb at a time.\nSNAP Produces an Optimizer/II , Optimizer/II , or SymDump  Batch SNAP\nreport.\nSPEED Accelerates program testing.\nSTEP Sets count for GO command.\nSUSPEND Detaches a terminal from a batch link debugging session without\nterminating the session.\nTRACE Controls/displays program trace entries.\nTRACE SOURCE Controls/displays program trace entries and their corresponding\nsource code.\nTRP Displays traced paragraph entries.\nUNCOND Sets an unconditional breakpoint (same as AT).\nUSING Sets an assembler base register for a DSECT that currently has\nno active USING.\nWHEN (or COND) Sets conditional breakpoints (or COND).\n* Adds a comment to the session log.\n/clist Executes CLIST CAMRCMD, called with parameter clist.\nADVANCE Command (Follow Trace Pointers Forward)\nReferencing the trace table, the ADVANCE command highlights and displays the next statement that was executed. This\nfeature lets the programmer visually follow in a forward sequence the statements that have been executed. This command\nis used along with the PREVIOUS command.\nSyntax\nUse the following syntax for ADVANCE:\n   ADVANCE <nnn|P nn>", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e4fed76b9e3d-1", "text": "ADVANCE <nnn|P nn>\n \nYou may enter this command in its abbreviated form: A.\nVariables\n 686", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f8e3b2c31007-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse the following variables with the ADVANCE command:\nnnn Specifies the number of executed statements for the session to\nmove forward. The default is one.\nP Specifies that the next executed paragraph, procedure, or label is\ndisplayed.\nnn Specifies the number of paragraphs, procedures, or labels for the\nsession to move forward. The default is one.\nUsage Notes\nThe trace facility must be turned on for the ADVANCE command to function. The trace facility is turned on by default when\nyou first invoke the application. For further information on turning the trace facility on and off, see the TRACE command\nlater in this section.\nThe ADVANCE command visually displays the forward execution of the program using the trace table entries. It does not\nactually execute the program.\nThe ADVANCE command does not affect the point at which a program resumes execution. Execution is resumed by\nissuing a GO command.\nIf you have not used the PREV command, the ADVANCE P command scrolls the program to the current statement,\nhighlights it, and displays END OF TRACE TABLE in the upper right-hand corner. Use this to return the program to the\ncurrent statement after scrolling through the listing. The control command CS also displays and highlights the current\nstatement.\nIf data monitoring was in effect when the statement highlighted from the ADVANCE command was executed, the values\ndisplayed for your data items are from the time before that statement was executed.\nAT (or UNCOND) Command (Set an Unconditional Breakpoint)\nUse the AT command to set breakpoints from the Intercept panel or to display the Breakpoint panel. The UNCOND\ncommand is a synonym of AT.\nIf you enter the AT or UNCOND command with operands in the Command field of an Intercept panel, the breakpoint is\nset.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f8e3b2c31007-1", "text": "set.\nIf you enter AT or UNCOND without operands, the Breakpoint panel is displayed.\n AT <<statement-number|paragraph-name|procedure-name|label-name> <AFTER|BEFORE> <(subcommand-list)>>\n <<ALL|program-name> <ENTRY|EXIT|LABEL|DBCALL>  <(subcommand-list)>>\n \nVariables\nSee the following variables with the AT or UNCOND commands:\nstatement-number Specifies a statement-number in the program where a breakpoint\nis set.\nparagraph-name Specifies a paragraph-name in the COBOL program where a\nbreakpoint is set.\nprocedure-name Specifies a procedure-name in the PL/I program where a\nbreakpoint is set.\nlabel-name Specifies label-name in the assembler or PL/I program where a\nbreakpoint is set.\n 687", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ae546f470882-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nENTRY For COBOL programs, specifies that a breakpoint occurs each\ntime the currently qualified program begins execution. For PL/I\nand assembler programs, specifies that a breakpoint occurs the\nfirst time the currently qualified program is entered.\nEXIT Specifies that a breakpoint occurs each time the currently qualified\nCOBOL program finishes execution.\nLABEL Specifies that a breakpoint occurs each time the currently qualified\nprogram executes a paragraph, procedure, or label.\nDBCALL Specifies that a breakpoint occurs each time the currently qualified\nprogram makes a call to a database, such as DB2 or IMS\nALL ENTRY Specifies that a breakpoint occurs each time a monitored COBOL\nprogram in the run unit begins execution and the first time a\nmonitored assembler or PL/I program in the run unit begins\nexecution.\nALL EXIT Specifies that a breakpoint occurs each time any monitored\nCOBOL program in the run unit finishes execution.\nALL LABEL Specifies that a breakpoint occurs each time a monitored program\nexecutes a label.\nALL DBCALL Specifies that a breakpoint occurs each time a monitored program\nmakes a call to a database, such as DB2 or IMS.\nAFTER Specifies that the breakpoint should be triggered after the\nstatement is executed.\nBEFORE Specifies that the breakpoint should be triggered before the\nstatement is executed. This is the default.\nsubcommand-list A list of application commands, separated by semicolons, to be\nexecuted when the breakpoint is encountered during the test.\nWhen testing under the ISPF dialog manager, you may enter only\none subcommand unless the ISPF command delimiter character is\nchanged to something other than the semicolon. This can be done\nunder option 0.1 of the ISPF main menu.\nUsage Notes\nSet a breakpoint by the paragraph name or by the line number of the paragraph. Sample statements to set breakpoints by", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ae546f470882-1", "text": "paragraph name are shown next:\n  041400 0000-INITIALIZATION SECTION.\n  041500\n  041600 MOVE +20 TO VARIABLE-LENGTH-1.\n  041700 MOVE +25 TO VARIABLE-LENGTH-2.\n  041800 MOVE +30 TO VARIABLE-LENGTH-3.\n \nSet a breakpoint on the first statement of the example by either of the following AT commands:\n AT 41400 or AT 0000-INITIALIZATION\n \nSet a breakpoint with a list of application commands to be executed at the breakpoint. The commands are executed one\nat a time until the program resumes execution or until a transfer of panels occurs, at which point the remaining commands\nare ignored. Commands should be in parentheses, separated by semicolons, as follows:\n AT 41700 (SET VARIABLE-LENGTH-2 = 50;GO 41800)\n \n 688", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "045113fa3518-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIn this example, the program stops before executing statement 41700, and VARIABLE-LENGTH-2 is set to 50. The GO\n41800 causes the program to resume execution at statement 41800 so the contents of VARIABLE-LENGTH-2 are not\nchanged to +25. You can use commands like these to temporarily modify the execution flow of the program.\nISPF Note\nWhen running under ISPF, specify only one command in the subcommand list because of restricted use of the semicolon,\nunless the ISPF command delimiter character has been changed. You can do this in option 0.1 of the ISPF main menu.\nCORE Command (Display Memory)\nThe CORE command invokes the Display-Alter Memory panel. This panel lets you modify data based on its address. For\nmore information, see Core Option and Map Option.\nSyntax\nUse the following syntax for CORE:\n CORE <data-item|paragraph-name|address|expression>\n \nUsage Notes\nIf you are navigating the trace table and data monitoring was in effect for the currently highlighted statement, you will see\na warning panel.  The CORE command shows only the current values of data items and not previous values.  Previous\nvalues of data items cannot be modified.\nCOUNTS Command (Control Frequency Counting)\nUse the COUNTS command to enable or disable frequency counting, reset frequency counters, and control the display of\nthe frequency counters.\nWhen enabled, frequency counting causes the debugger to count the number of times each statement is executed. When\nthe display is active, the frequency counters appear on the Intercept panel in the left margin.\nSyntax\nUse the following syntax for COUNTS:\n COUNTS <ON|OFF> <SHOW|NOSHOW> <RESET|RESET ALL|RESET progid>\n \nVariables\nUse the following variables with the COUNTS command:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "045113fa3518-1", "text": "Variables\nUse the following variables with the COUNTS command:\nON Enables frequency counting\nOFF Disables frequency counting\nSHOW Causes the frequency counters to be displayed on the Intercept\npanel\nNOSHOW Suppresses the display of the frequency counters on the Intercept\npanel\nRESET Clears to zero all of the counters for the current program\nRESET ALL Clears to zero all of the counters for all of the programs\nRESET progid Clears to zero all of the counters for the specified program\nUsage Notes\n 689", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4a68a5d1de73-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWhen specifying COUNTS ON or OFF, you may also specify SHOW or NOSHOW as a second argument.\nIf frequency counting is enabled but the display is disabled, counting continues even though no counts are displayed.\nCS Command (Current Statement)\nThe Current Statement (CS) command displays and highlights the current statement. This is especially useful after\nscrolling through the listing and any time the next statement to be executed is no longer displayed. You can also change\nthe current statement by a passing statement number.\nSyntax\nUse the following syntax for CS:\n CS <statement-number|paragraph-name|procedure-name|label-name>\n \nUsage Notes\nWhen using CS to modify the flow of execution of a COBOL program, be careful to avoid entering a paragraph and\nbypassing the PERFORM statement. When the exit to the paragraph is reached, a USER 519 abend may be issued\nbecause the references to the calling statement are not defined.\nWhen using CS to modify the flow of execution of a PL/I program, be careful to avoid entering a block (that is, procedure,\nBEGIN block, or ON-unit) other than at the start of the block, or exiting a block other than at the END statement for the\nblock, as it causes unpredictable results.\nDATAMON (Enable Data Monitoring)\nThe DATAMON command enables data monitoring for the specified COBOL program. When this feature is used in\nconjunction with the trace navigation commands (PREV, ADV, POINT), you see past data values when displaying data.\nSyntax\nUse the following syntax for DATAMON:\n DATAMON ON|OFF <pgmid>\n \nYou can use this command in its abbreviated form: DM.\nUsage Notes", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4a68a5d1de73-1", "text": "You can use this command in its abbreviated form: DM.\nUsage Notes\nEnabling DATAMON lets you view past data values when navigating the trace table. If DATAMON was in effect for the\nstatement highlighted by the trace navigation command (PREV, ADV, POINT), the data values displayed in the KEEP\nand DISPLAY commands will be past data values captured from a point in time before  a COBOL statement referencing\nthem is executed. These values are protected as you may not be able to update data while viewing past data values. For\nthis reason, the SET command is disabled in this situation. When using the CORE command, a warning panel is shown\nindicating that the current data is shown for viewing and updating, not the past data values. Also, use of the + and - line\ncommands are disabled when incrementing or decrementing a subscript symbolically.\nThe DATAMON command can be CPU intensive and it requires a significant amount of storage. The DATAMON command\nis only valid for COBOL programs.\nDDALLOC Command (Allocate a DD)\nThe DDALLOC command displays the DDALLOC panel. From this panel, you allocate a DD to DUMMY, a SYSOUT class,\nor a data set. Note that this feature works in both batch link and foreground testing. Foreground users can also split their\nscreen and use Option 3, ALLOCATIONS, to perform their allocations.\nSyntax\n 690", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "76dc6b8c2322-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse the following syntax for DDALLOC:\n DDALLOC <ddname>\n \nYou can enter this command in its abbreviated form: DDA.\nDDFREE Command (Free a DD)\nThe DDFREE command lets you free a specified DD.\nSyntax\nUse the following syntax for DDFREE:\n DDFREE ddname\n \nYou can enter this command in its abbreviated form: DDF.\nDDQ Command (Query a DD)\nThe DDQ command invokes the DDName Query panel. The panel displays information about the allocated DD's.\nSyntax\nUse the following syntax for DDQ:\n DDQ <ddname>\n \nDISPLAY Command (Format Data or the COBOL Working Storage Section)\nThe DISPLAY command invokes the Display panel. You can modify the data values on this display.\nSyntax\nUse the following syntax for DISPLAY:\n DISPLAY <data-item|expression <data-item> ...> <PRINT>\n \nYou can enter this command in its abbreviated form: D.\nNOTE\nData for variables are case-sensitive.\nVariables\nUse the following variables with the DISPLAY command:\ndata item Causes a display of the data item, any subordinate level data\nitems, and their data values. You may enter more than one data\nitem.\nexpression For assembler programs, enter an expression in register notation.\nPRINT Causes the data displayed by the command to be written to the\nsession log.\nUsage Notes\nConsider the following COBOL WORKING-STORAGE definition:\n 691", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "20b7caf1d2d5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  WORKING-STORAGE SECTION.\n  01 WORKING-STORAGE-AREA.\n            05 CONVERSION-AREA.\n            10 CONV-DATE      PIC 9(7) VALUE ZERO.\n            10 CONV-TIME      PIC 9(6)V999 VALUE ZERO.\n            05 SELECTION CRITERIA.\n            10 SELECT-START   PIC S9(15)V999 COMP.\n            10 SELECT-END     PIC S9(15)V999 COMP.\n \nIf you enter the DISPLAY command without operands, it formats and displays all of the previous data items and their data\nvalues.\nThe command D CONVERSION-AREA would format and display CONVERSION-AREA, CONV-DATE, and CONV-TIME.\nThe command D SELECT-START would format and display only the data item SELECT-START.\nNOTE\nIf data monitoring was in effect, data item values displayed are those captured at a point in time before th e\nCOBOL statement, positioned by Prev or Adv command is executed.\nIf a data item is modified on the other side of a split screen, you can update the Display panel to reflect any changes made\nby typing REFRESH  on the command line.\nNOTE\nThe data-item parameter may be a qualified data item, as in the following examples:\nCOBOL: Use the command D EMPLOYEE-NO IN MASTER-RECORD\nto refer to the EMPLOYEE-NO in MASTER-RECORD if\nEMPLOYEE-NO is not unique.\nPL/I: Use the command D MASTER.RECORD.EMPLOYEE_NO to refer\nto the EMPLOYEE_NO in MASTER_RECORD if EMPLOYEE_NO\nis not unique.\nUse the command D NEXT_ELEM_PTR->ELEMENT to refer to\nthe allocation of based variable ELEMENT that is pointed to by\nNEXT_ELEM_PTR.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "20b7caf1d2d5-1", "text": "the allocation of based variable ELEMENT that is pointed to by\nNEXT_ELEM_PTR.\nFor assembler or PL/I programs, you need a data-item or expression operand.\nIf you are navigating the trace table and data monitoring was in effect for the currently highlighted statement, the values\ndisplayed for your data items are from the time before that statement was executed.\nDROP Command (DROP Symbolic Name)\nUse the DROP command to remove the symbolic name for a data item that has been set by the EQUATE command. View\nthe symbolic names using the LEQ command or set by using the EQUATE command. DROP without operands causes the\nEquate panel to be displayed. For more information on the EQUATE command, see Breakpoint Panels.\nSyntax\nUse the following syntax for DROP:\n DROP <symbolic-name>\n \nYou can enter this command in its abbreviated form: DR.\nVariables\n 692", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "597bdc54095c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse the following variable with the DROP command:\nsymbolic-name User-defined symbolic name for a data item.\nDROPUSE Command (Remove a Using)\nThe DROPUSE command removes a using that was set with the USING command. This command is only valid when\ndebugging an assembler program.\nSyntax\nUse the following syntax for DROPUSE:\n DROPUSE dsect|csect\n \nVariables\nUse the following variables with the DROPUSE command:\ndsect Assembler DSECT that you wish to map\ncsect Assembler CSECT that you wish to map\nYou can enter this command in its abbreviated form: DROPU.\nDUMP Command (Terminate Testing with a Dump)\nUse the DUMP command to terminate the testing session with a dump. This command only works when the application\nbeing tested has previously abended.\nSyntax\nUse the following syntax for DUMP:\n DUMP\n \nUsage Notes\nTo use the DUMP command, you must pre-allocate an MVS dump data set (SYSMDUMP). Allocate the dump data set\nfrom Option 3 (ISPF) - ALLOCATION, of the Primary Option Menu; from ISPF option 6 using the TSO allocate command;\nor by pre-allocating a dump data set in the CLIST. The following example is a sample allocation as it appears in a CLIST:\n  CONTROL NOMSG\n  FREE DD(SYSMDUMP)\n  DEL yourdsn\n  CONTROL MSG\n  ALLOC DD(SYSMDUMP) DSN(yourdsn) NEW SPACE(105) CYL\n  UNIT(unitname) VOLUME(volser) CATALOG\n \nFollowing is a sample dump allocation for Roscoe  users:\n FREE  SYSMDUMP\n DELETEDSN SYSMDUMP", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "597bdc54095c-1", "text": "FREE  SYSMDUMP\n DELETEDSN SYSMDUMP\n ALLOC SYSMDUMP dsn=SYSDUMP\n SPACE=(cyl, (50,10))\n DISP=(NEW,catlg)\n VOL=\n 693", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b0f806cbd1be-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n UNIT=\n \nYou must print SYSMDUMPs using the AMDPRDMP utility.\nNOTE\nYou can also use the DDALLOC command to allocate the SYSMDUMP DD to an existing DSN or a SYSOUT\nclass.\nEQUATE Command (Specify Symbolic Name)\nUse the EQUATE command to equate a data item with a symbolic name. You may then refer to the data item by either\nthe data item or the symbolic name. View the symbolic names using the LEQ command or delete by using the DROP\ncommand. The EQUATE command supports qualified data items. Equate without operands causes the Equate panel to\ndisplay. For more information on the EQUATE command, see Breakpoint Panels.\nSyntax\nUse the following syntax for EQUATE:\n EQUATE <symbolic-name data-item>\n \nYou can enter this command in its abbreviated form: EQU.\nVariables\nUse the following variables with the EQUATE command:\nsymbolic-name A user-defined symbolic name for a data item\ndata-item An elementary data item or qualified data item\nData-item can be a qualified data item with 1 or 2 levels of qualification, as described in the following examples:\nCOBOL: The following command equates NAME-ONE OF EMP-NAME OF\nPAYROLL-REC to the symbolic name N1. You may now specify\nN1 as the data item for control commands such as LDI and SET.\nEQUATE N1 NAME-ONE OF EMP-NAME OF PAYROLL-REC\nThis variable may also be specified by equating the following:\nEQU NO NAME-ONE\nEQU EN EMP-NAME\nEQU PR PAYROLL-REC\nNO OF EN OF PR used as the data item in a control command", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b0f806cbd1be-1", "text": "NO OF EN OF PR used as the data item in a control command\nalso refers to NAME-ONE OF EMP-NAME OF PAYROLL-REC.\nPL/I: The following command equates\nPAYROLL_REC.EMP_NAME.NAME_ONE to the symbolic\nname N1. You may now specify N1 as the data item for control\ncommands such as LDI and SET.\nEQUATE N1 PAYROLL_REC.EMP_NAME.NAME-ONE\nYou may also specify this variable by equating the following:\nEQU NO NAME_ONE\nEQU EN EMP_NAME\nEQU PR PAYROLL_REC\nPR.EN.NO used as the data item in a control command also refers\nto PAYROLL_REC.EMP_NAME.NAME_ONE.\n 694", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bc8dc8fc2eb2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe data item may be a fixed or variably subscripted data item or indexed data item. The following commands equate a\nvariably subscripted data item to the symbolic name W1.\nCOBOL:\n EQ W1 WA-TI-3A(S1,S2,S3)\n \nPL/I:\n EQ W1 WA_TI_3A(S1,S2,S3)\n \nThe data item can also be a qualified subscripted or indexed data item, as in the following examples:\nCOBOL: This command equates the symbolic name W1 to the fourth value\nin the non-unique table WA-1A in the unique table WA-TABLE-1:\nEQU W1 WA-1A OF WA-TABLE-1(4)\nPL/I: This command equates the symbolic name W1 to the fourth value\nin the non-unique table WA_1A in the unique table WA_TABLE_1:\nEQU W1 WA_TABLE_1.WA-1A(4)\nEXSUM Command (Display Execution Summary)\nThe EXSUM command provides an execution summary display of the current program. The display shows the number of\nexecutable statements, the number of statements currently executed during the test, and the percentage of statements\ncurrently executed during the test.\nNOTE\nStatements executed when COUNTS OFF is in effect are not counted by the EXSUM command and will not get\nincluded in the summary.\nSyntax\nUse the following syntax for EXSUM:\n EXSUM\n \nYou can enter this command in its abbreviated form: EXS.\nThe following panel is a sample Execution Summary Display:\n ---------------- CA InterTest Batch Execution Summary Display -----------------\n  \n PROGRAM ID:  INSTST\n  \n Number of executable statements: 21\n  \n Number of statements currently executed during this test: 21", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bc8dc8fc2eb2-1", "text": "Number of statements currently executed during this test: 21\n  \n Percentage of statements currently executed during this test: 100\n \nNOTE\nIf COUNTS NOSHOW is in effect, no statements are counted and the Execution Summary Display will show N/A\nfor Not Applicable for all three counts.\n 695", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a194c37c785c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFILES Command (Display COBOL FD Status)\nThe FILES command displays the File Status panel. The File Status panel indicates whether the data sets in the FD\nsection are open or closed, and it gives the DSORG and DCB information for the files. For more information on File Status\nPanels, see Debugging Panels.\nSyntax\nUse the following syntax for FILES:\n FILES\n \nYou can enter this command in its abbreviated form: FI.\nUsage Notes\nIMS databases are not supported on this display. This command is not supported for assembler or PL/I programs.\nFM Command (Invoke File Master Plus )\nThe FM command invokes File Master Plus , if you have that product installed. For details on using that product, see the\nFile Master Plus  documentation.\nSyntax\nUse the following syntax for FM:\n FM\n \nNOTE\nThis command is valid for both batch link and foreground testing.\nFREQ Command (Controls FREQ Counter)\nThe frequency command controls the statement frequency counter, but the frequency command and the NOFREQ\ncommand control whether the counters are displayed.\nNOTE\nThe FREQ command is replaced by the COUNTS command, which is described earlier in this section.\nSyntax\nUse the following syntax for FREQ:\n FREQ <ON|OFF|RESET>\n \nYou can enter the FREQ command in its abbreviated form: FR.\nVariables\nUse the following variables with the FREQ command:\nON Enables frequency counting. This is the default. This command\ncauses the Intercept panel to shift to the right six characters and\ndisplays one of the following in the left margin:\nnnnn A four-digit integer indicating the number of times the statement\nhas executed. If the counter exceeds 9999, the number is\nrepresented as follows:\n 696", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cd5a14bfb680-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nnnnK = nnn x 1 thousand (for example, 010K= 10 thousand)\nnnnM=nnn x 1 million (for example, 010M= 10 million)\nnnnG=nnn x 1 billion (for example, 010G= 10 billion)\nIf your frequency count has exceeded 9999 and you wish to see\nan exact count, issue an I (Info) line command to the left of the\nline. The full count is displayed in the upper right-hand corner of\nthe Intercept panel.\n---> This line contains the beginning of a valid statement, but it has not\nyet been executed.\nSpaces The line number is not the beginning of a statement.\nOFF Disables frequency counting.\nRESET Zeroes the frequency counters for the currently qualified program.\nUsage Notes\nWhen you initially invoke the application, the frequency counter is turned on but is not displayed. To enable the display,\nenter the FREQ command without operands. Subsequently, if the FREQ OFF command is issued, the counters are no\nlonger maintained, but the residual counts remain on the screen. To remove the counters and arrows from the screen,\nenter the NOFREQ command.\nThe status of the frequency command is maintained over sessions.\nGO Command (Continue Test Session)\nThe GO command causes the test session to continue until the next intercept occurs.\nSyntax\nUse the following syntax for GO:\n GO <Statement-number|paragraph-name|procedure-name|label-name>\n \nVariables\nUse the following variables with the GO command:\nstatement-number Specifies a statement-number in the program where the program\nresumes execution.\nparagraph-name Specifies a paragraph-name in the program where execution\nresumes.\nprocedure-name Specifies a procedure-name in the PL/I program where execution\nresumes.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cd5a14bfb680-1", "text": "procedure-name Specifies a procedure-name in the PL/I program where execution\nresumes.\nlabel-name Specifies a label-name in the assembler or PL/I program where\nexecution resumes.\nSpecify a statement number, paragraph, procedure, or label name as the execution start point. GO with no operands\nresumes execution at the next logical statement unless the program was interrupted because of an ABEND. In this case,\nthe program resumes execution at the statement where the ABEND occurred.\nThe program executes until one of the following occurs:\n 697", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bc1dda08f22b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022A breakpoint is encountered.\n\u2022An ABEND occurs in the program.\n\u2022The step count (specified by the STEP command) is exhausted.\n\u2022The user interrupts the test by pressing the ATTENTION key.\n\u2022The program runs to normal completion.\nUsage Notes\nWhen using GO to modify the flow of execution of a COBOL program, be careful to avoid entering a paragraph and\nbypassing the PERFORM statement. When you reach the exit to the paragraph, you may receive a USER 519 ABEND\nbecause the references to the calling statement are not defined.\nWhen using GO to modify the flow of execution of a PL/I program, be careful to avoid entering a block (that is, procedure,\nBEGIN block, or ON-unit) other than at the start of the block, or exiting a block other than at the END statement for the\nblock, as it will cause unpredictable results.\nGOTO Command (Resumes execution until specified line)\nThe GOTO line command resumes execution until the specified line.\nSyntax\nUse the following syntax for GOTO:\nGOTO <Statement-number|paragraph-name|procedure-name|label-name>\nVariables\nUse the following variables with the GOTO command:\nstatement-number Specifies a statement-number in the program until the program\nresumes execution.\nparagraph-name Specifies a paragraph-name in the program until execution\nresumes.\nprocedure-name Specifies a procedure-name in the PL/I program until execution\nresumes.\nlabel-name Specifies a label-name in the assembler or PL/I program until\nexecution resumes.\nTo resume execution to the specified point, specify a statement number, paragraph, procedure, or label name. The\nGOTO command overrides the existing unconditional breakpoint on that line. The command honors all breakpoints during\nexecution.\nUsage Notes", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bc1dda08f22b-1", "text": "execution.\nUsage Notes\nThe GOTO command puts a temporary breakpoint on the specified line and resumes execution. Once the temporary\nbreakpoint is reached, the temporary breakpoint is removed. If the temporary breakpoint is still active at the time of\nintercept, the specified line is denoted as \"T\". The temporary breakpoints are also displayed on the breakpoint panel.\nINCLUDE Command (Execute Application Commands)\nThe INCLUDE command reads and executes a set of application commands from a partitioned data set.\nSyntax\nUse the following syntax for INCLUDE:\n INCLUDE member-name\n \n 698", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0d94ef770805-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nVariables\nUse the following variable with the INCLUDE command:\nmember-name Specifies a valid member name of a partitioned data set (PDS)\nallocated to ddname INT1CLIB.\nUsage Notes\nBefore you enter the INCLUDE command, perform an allocation to ddname INT1CLIB. Allocate the partitioned data set\nwith an LRECL=80 and a RECFM=FB. Create the members using a text editor.\nUse the INCLUDE command to execute a set of application commands for regression testing or retesting as code is\nmodified during testing. For example, use the following commands to test a tax computation routine:\n  SET EMPLOYEE-NAME = 'PIERCE, MICHAEL'\n  SET EMPLOYEE-NUMBER = 3938\n  SET EMPLOYEE-STATE = 'CA'\n  WHEN TOOHIGH EMPLOYEE-SALARY GT 50000.00\n  AT 0100-CALC-FICA\n \nNOTE\nThe INCLUDE command ignores all commands in the input stream following a command that causes the\nprogram to resume.\nFor example, GO or NEXT cause the program to resume execution; DISPLAY or LISTAT cause a transfer of panels. If the\ninput stream includes these commands, any command following them is ignored.\nLDA (or AUTOKEEP) Command (List Data Automatic)\nThe LDA or AUTOKEEP (list data automatic) command displays in the keep window all the data items referenced by the\ncurrent statement.\nThe keep window appears on the Intercept panel immediately above the first line of the program listing.\nSyntax\nUse the following syntax for LDA or AUTOKEEP:\n LDA <ON|OFF>\n \nYou may enter this command in its abbreviated form: AUTOK.\nVariables\nUse the following variables with LDA or AUTOKEEP:\nON Enables the automatic list data facility.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0d94ef770805-1", "text": "Use the following variables with LDA or AUTOKEEP:\nON Enables the automatic list data facility.\nOFF Disables the automatic list data facility.\nUsage Notes\nLDA does not inhibit your ability to use the LDI (KEEP) or LDIX (KEEP HEX) commands to add static entries to the keep\nwindow. While automatically added data items are added and removed at each breakpoint, a static data item continues to\nbe displayed in the keep window until removed manually.\nWhen AUTOKEEP is in effect for an assembler routine, the operands for the current instruction are added to the keep\nwindow in register notation.\n 699", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5b1dd9c46dcc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCOBOL programs can be compiled with the ARITH(EXTEND) parameter which will allow a numeric field to be greater\nthan 18 bytes. These fields will be displayed with the message 'TOO BIG TO DISPLAY' in the value. To view or change\nthe actual value of the field, use the CORE command.\nLDI (or KEEP) Command (List Data Item)\nThe list data item (LDI) command inserts a line that shows the data item and its value before the first line of the program\nlisting on the Intercept panel. The data item appears on all subsequent Intercept panels until it is reset by the RDI (reset\ndata item) command.\nSyntax\nUse the following syntax for LDI or KEEP:\n LDI data-item|expression\n \nNOTE\nData for variables are case-sensitive.\nYou can enter this command in its abbreviated form: K.\nVariables\nUse the following variables with LDA or AUTOKEEP:\ndata-item An elementary data item or group name from the test program.\nexpression For assembler programs, enter an expression in register notation.\nUsage Notes\nModify elementary items from within the keep window. Type over the value displayed on the screen with the new value.\nThe LDI command supports group level items. To view the members of a data group, specify the group name as the data-\nitem for the LDI command.\nUse the LDI command to view COBOL SPECIAL REGISTERS. For example, this command places the current value of\nreturn code on the Intercept panel:\n LDI RETURN-CODE\n \nThe data-item parameter can be a qualified data item, as in the following examples. Specify either 1 or 2 levels of\nqualification.\nCOBOL : Use this command to refer to the EMPLOYEE-NO in the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5b1dd9c46dcc-1", "text": "qualification.\nCOBOL : Use this command to refer to the EMPLOYEE-NO in the\nMASTER-RECORD if the EMPLOYEE-NO is not unique.\nLDI EMPLOYEE-NO IN MASTER-RECORD\nPL/I: Use this command to refer to the EMPLOYEE_NO in the\nMASTER_RECORD if the EMPLOYEE_NO is not unique.\nLDI MASTER_RECORD.EMPLOYEE_NO\nThe data-item parameter can be a fixed or variably subscripted data item or an indexed data item. For example, the\nfollowing commands show the use of fixed subscripts:\nCOBOL:\n LDI WA-TI-3A(1,2,3)\n \n 700", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cedda44d36d7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPL/I:\n LDI WA_TI_3A(1,2,3\n \nYou can specify also variable subscripts, as follows:\nCOBOL:\n LDI WA-TI-3A(SUB1,SUB2,SUB3)\n \nPL/I:\n LDI WA_TI_3A(SUB1,SUB2,SUB3)\n \nIn this case, the value displayed changes as the subscripted variables change. The values of the subscripts are also\ndisplayed. An * INVALID * message is placed next to any of the subscripts that are out of range.\nThe data-item can also be a qualified, fixed or variably subscripted data-item, or an indexed data item, as in the following\nexamples:\nCOBOL: This command displays the fourth element of the Table WA-1A in\nWA-TABLE-1:\nLDI WA-1A OF WA-TABLE-1 (4)\nPL/I: This command displays the fourth element of the Table WA_1A in\nWA_TABLE_1:\nLDI WA_TABLE_1.WA_1A (4)\nFor PL/I programs, the data-item parameter can be a locator qualified based variable. For example, use the following\ncommand to display the allocation of ELEMENT that is based off of NEXT_ELEM_PTR.\n LDI NEXT_ELEM_PTR->ELEMENT\n \nBoth the data-item and the locator qualifier can also be qualified and fixed or variably subscripted. Broadcom  supports up\nto 15 levels of locator qualification.\nCOBOL programs can be compiled with the ARITH(EXTEND) parameter which will allow a numeric field to be greater\nthan 18 bytes. These fields will be displayed with the message 'TOO BIG TO DISPLAY' in the value. To view or change", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cedda44d36d7-1", "text": "the actual value of the field, use the CORE command.\nSpecial Registers\nSpecial registers are compiler-generated storage areas whose primary use is to store information produced through one\nof COBOL's specific features.\nYou may display the value of the following special registers in the application:\n RETURN-CODE\n SORT-RETURN\n SORT-FILE-SIZE\n SORT-CORE-SIZE\n SORT-MODE-SIZE\n LABEL-RETURN\n \nFor more information regarding these special registers, refer to your IBM VS COBOL for OS/VS  Manual , IBM COBOL II\nApplication Programming Language Reference Manual, or COBOL/370 Language Reference Manual .\n 701", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5c5c05f8baa1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nLDX (or KEEPX) Command (List Data Item in Hex)\nThe list data item in hexadecimal (LDX) command inserts three lines showing the data item and its value before the first\ndisplay lines of the program listing on the Intercept panel. The second and third lines display the data representation in\nhex format showing zones and numerics, respectively. The data item appears on all following Intercept panels until it is\nreset by the RDI (reset data item) command.\nSyntax\nUse the following variables with LDX or KEEPX:\n LDX data-item\n \nYou can enter this command in its abbreviated form: KX..\nVariables\nUse the following variable with the LDX or KEEPX commands:\ndata-item An elementary data item or group item from the test program.\nUsage Notes\nModify elementary items from within the keep window. Type over the value displayed on the screen with the new value.\nNote that you cannot modify the zones and numerics portion of the data display.\nThe LDX command supports group level items. To view the members of a data group, enter the group name as the data-\nitem for the LDX command.\nUse the LDX command to view COBOL special registers. For example, use the following command:\n LDX RETURN-CODE\n \nThe data-item parameter can be a qualified data item, as in the following examples. Specify either 1 or 2 levels of\nqualification.\nCOBOL: Use this command to refer to the EMPLOYEE-NO in the\nMASTER-RECORD if the EMPLOYEE-NO is not unique:\nLDX EMPLOYEE-NO IN MASTER-RECORD\nPL/I: Use this command to refer to the EMPLOYEE_NO in the\nMASTER_RECORD if the EMPLOYEE_NO is not unique:\nLDX MASTER_REC.EMPLOYEE_NO", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5c5c05f8baa1-1", "text": "MASTER_RECORD if the EMPLOYEE_NO is not unique:\nLDX MASTER_REC.EMPLOYEE_NO\nThe data-item parameter can be a fixed or variably subscripted data item or an indexed data item. For example, the\nfollowing commands show the use of fixed subscripts:\nCOBOL:\n LDX WA-TI-3A(1,2,3)\n \nPL/I:\n LDX WA_TI_3A(1,2,3)\n \nYou can specify also variable subscripts, as follows:\nCOBOL:\n 702", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c338573128cd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n LDX WA-TI-3A(SUB1,SUB2,SUB3)\n \nPL/I:\n LDX WA_TI_3A(SUB1,SUB2,SUB3)\n \nIn this case, the value displayed changes as the subscript variables change. The values of the subscripts are also\ndisplayed. An * INVALID * message is placed next to any of the subscripts that are out of range.\nThe data-item can be a qualified fixed or variably subscripted data item or an indexed data item, as in the following\nexamples:\nCOBOL: This command displays the fourth element of the table WA-1A in\nWA-TABLE-1:\nLDX WA-1A OF WA-TABLE-1 (4)\nPL/I: This command displays the fourth element of the table WA_1A in\nWA_TABLE_1:\nLDX WA_TABLE_1.WA_1A (4)\nFor PL/I programs, the data-item parameter can be a locator qualified based variable. For example, use the following\ncommand to display the allocation of ELEMENT that is based off of NEXT_ELEM_PTR:\n LDX NEXT_ELEM_PTR->ELEMENT\n \nBoth the data-item and the locator qualifier can also be qualified and fixed or variably subscripted. Broadcom  supports up\nto 15 levels of locator qualification.\nSpecial Registers\nSee the previous section, LDI (or KEEP) Command (List Data Item), for a description of the supported special registers.\nLEQ Command (List Equated Names)\nThe LEQ command lists the equated symbolic names and data items set by the EQUATE command. Delete the symbolic\nnames by using the DROP command.\nSyntax\nUse the following syntax with LEQ:\n LEQ", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c338573128cd-1", "text": "Syntax\nUse the following syntax with LEQ:\n LEQ\n \nLINKAGE Command (Format the COBOL Linkage Section)\nThe LINKAGE command displays the Linkage Display panel. Modify the data values on this display.\nSyntax\nUse the following syntax with LINKAGE:\n LINKAGE   <data-item> <PRINT>\n \nYou can enter this command in its abbreviated form: LI.\nVariables\n 703", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3aeb3f00d837-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse the following variables with the LINKAGE command:\ndata-item Causes a display of the data item, any subordinate data items,\nand their data values.\nPRINT Causes the data displayed by the command to be written in the\nsession log.\nUsage Notes\nConsider the following LINKAGE SECTION definition:\n LINKAGE SECTION\n 01 PARM-VALUE\n     05 PARM-COUNT                PIC S9(4) COMP SYNC.\n     05 PARM-DATA \n         10 PARM-DATE             PIC X(5).\n         10 PARM-TIME.\n             15 PARM-HH           PIC XX\n             15 PARM-MM           PIC XX\n             15 PARM-SS           PIC XX\n \nIf you enter the LINKAGE command without operands, it formats and displays all of the preceding data items and their\ndata values.\nThe command LI PARM-DATA formats and displays PARM-DATA, PARM-DATE, PARM-TIME, PARM-HH, PARM-MM, and\nPARM-SS.\nThe command LI PARM-SS formats and displays PARM-SS.\nWARNING\nThe LINKAGE command should not be used until the COBOL program has executed the PROCEDURE\nDIVISION or ENTRY statement.\nThe LINKAGE command is not valid for assembler or PL/I programs.\nIf you are navigating the trace table and data monitoring was in effect for the currently highlighted statement, the values\ndisplayed for your data items are from the time before that statement was executed.\nLISTAT Command (List Breakpoints)\nThe LISTAT command displays the Breakpoint Status panel. This is a listing of the unconditional breakpoints set in the\ncurrently qualified program. You can delete breakpoints from this panel as well by placing an X in the command column of", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3aeb3f00d837-1", "text": "the line the breakpoint to be deleted is listed on, and pressing enter.\nSyntax\nUse the following syntax with LISTAT:\n LISTAT\n \nLISTBP Command (List All Breakpoints)\nThe LISTBP command displays the Breakpoints panel. This is a listing of all conditional (WHEN) and unconditional (AT)\nbreakpoints set in the application. You may also delete breakpoints from this panel by placing an X in the command\ncolumn of the line the breakpoint to be deleted is listed on, and pressing Enter.\nSyntax\n 704", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8cbcbfbebdb9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse the following syntax with LISTBP:\n LISTBP\n \nYou can enter this command in its abbreviated form: LBP.\nLISTLBL Command (List Labels)\nThe LISTLBL command lists the labels that were added with the .label command.\nSyntax\nUse the following syntax with LISTLBL:\n LISTLBL\n \nLISTUSE Command (List Usings)\nThe LISTUSE command displays the Using Status panel. This is a listing of all usings set by the USING command. This\ncommand is only valid when debugging an assembler program.\nSyntax\nUse the following syntax with LISTUSE:\n LISTUSE\n \nYou can enter this command in its abbreviated form: LISTU.\nLISTWHEN Command (List WHEN Conditions)\nThe LISTWHEN command displays the When Conditions Display panel. This is a listing of the conditional breakpoints\nset in the currently qualified program. It lists both global and local conditional breakpoints. You may delete breakpoints\nfrom this panel as well by placing an X in the command column of the line the breakpoint to be deleted is listed on, and\npressing Enter.\nSyntax\nUse the following syntax with LISTWHEN:\n LISTWHEN\n \nYou can enter this command in its abbreviated form: LISTW.\nMAP Command (Region MAP Display)\nThe MAP command invokes the Region Map Display Panel. This panel lets you display information about programs in\nstorage. For more information, see Core Option and Map Option.\nSyntax\nUse the following syntax with MAP:\n MAP\n \n 705", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3bb93ae3e7cd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMLOG Command (Record Debugging Session)\nLogs and monitors a debugging session so you can save it and reuse the session commands in a future debugging\nsession.\nSyntax\nUse the following syntax with MLOG:\n MLOG <START|STOP|CANCEL|DISPLAY|LOAD> <name> <description>\n \nVariables\nMLOG START name description\nMonitoring commands are recorded for later use in restoring the debug session. The monitoring commands are saved into\nINT1CLIB as a member with the name specified.\nName is optional and is 1-8 characters and must be a valid name for a PDS member. If name is not specified the default\nname is the name of the loaded program.\nDescription is optional and is 1-35 characters. This is a comment field where the user can provide a description of the\ndebug session.\nAfter the MLOG START command is invoked, 'RECORDING' will be displayed in the upper right hand corner for the\nscreen. This is an indicator that debugging commands are being recorded for use at a later time.\nMLOG STOP\nRecording of monitor commands is stopped for the user entering the command.\nAfter the MLOG STOP command is issued the RECORDING indicator will be turned off.\nMLOG CANCEL\nLogging of monitoring commands is turned off for the session and entries recorded since the prior MLOG START\ncommand are deleted.\nMLOG DISPLAY\nPresents a menu of active and saved debugging sessions in the INT1CLIB file. This is the default if MLOG is specified\nwith no subcommand.\nMLOG LOAD name\nPerforms a load of a saved debug session from the INT1CLIB library. This command behaves the same as the INCLUDE\ncommand.\nNEXT Command (Executing Verbs)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3bb93ae3e7cd-1", "text": "command.\nNEXT Command (Executing Verbs)\nThe NEXT command executes the next verb in the program. You will see the Next Intercept panel after entering NEXT.\nSyntax\nUse the following syntax with NEXT:\n NEXT <nnn|P|BEFORE|AFTER|?|OVER|RETURN>\n \nYou can enter this command in its abbreviated form: N.\nVariables\n 706", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4c80b960fc95-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse the following variables with the NEXT command:\nnnn Specifies the number of statements to execute. The default is one.\nP Specifies that all statements in the current paragraph that are not\nto be skipped will be executed, and execution stops at the next\nparagraph.\nBEFORE Specifies that when the NEXT command is used, execution stops\nbefore the statements are executed. Note this is the default.\nAFTER Specifies that when the NEXT command is used, execution stops\nafter the statements are executed.\nNotes:\nIf NEXT is set to AFTER, statements that cause execution to leave\nthe current program, such as GOBACK for COBOL, will have no\neffect on the NEXT command.\nIf data monitoring was in effect, all data item changes are captured\nat a point in time before  COBOL statements referencing them are\nexecuted even when NEXT AFTER is set.\n? Displays a short message, reporting on whether NEXT stops\nbefore or after the specified number of statements.\nOVER Specifies that when the NEXT command is used executes through\na verb, instruction, or statement and return to that line. This is to\navoid breakpoints.\nRETURN Specifies that when the NEXT command is used to continue\nexecution until the next CALL or PERFORM verb. Execution will\nstop when it hits a CALL or PERFORM execution.\nWhen stopped on a PERFORM or CALL, the NEXT OVER command causes the test session to continue until the lexical\nstatement following the PERFORM or CALL is encountered, where a breakpoint occurs.\nWhen stopped within a paragraph or subroutine, the NEXT RETURN  command causes the test session to continue until\nthe session encounters the lexical statement following the PERFORM or CALL that invoked the current paragraph or\nsubroutine, where a break point occurs.\nNOFREQ Command (Remove Frequency Counters)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4c80b960fc95-1", "text": "subroutine, where a break point occurs.\nNOFREQ Command (Remove Frequency Counters)\nUse the NOFREQ command to remove the frequency counters and arrows from the Intercept panel.\nSyntax\nUse the following syntax for NOFREQ:\n NOFREQ\n \nNOTE\nThis is used along with the FREQ command. This command and the FREQ command have been replaced by\nthe COUNTS command.\nOFF (or OFFU) Command (Remove Unconditional Breakpoints)\nUse the OFF command to delete unconditional breakpoints set by the AT or UNCOND command, the A or U line\ncommand, the ) line command, the SKIP command, the S line command, or the Breakpoint panel.\nIf you specify the OFF command with no operands, the Breakpoint panel is displayed.\n 707", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0d37ee9d51ce-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDelete a breakpoint by specifying OFF with the statement number where the breakpoint is set in the COMMAND field of\nthe Intercept panel.\nSyntax\nUse the following syntax for OFF and OFFU:\n  OFF <statement-number|paragraph-name|procedure-name|label-name|ENTRY|EXIT|LABEL|DBCALL|ALL ENTRY|ALL EXIT|\nALL LABEL|ALL DBCALL <(subcommand-list)>>\n \nYou can enter this command in its abbreviated form: O.\nVariables\nUse the following variables with the OFF or OFFU commands:\nStatement-number A program statement number where an existing breakpoint is\ndeleted.\nParagraph-name A COBOL paragraph name where an existing breakpoint is\ndeleted.\nProcedure-name A PL/I procedure name where an existing breakpoint is deleted.\nLabel-name An assembler or PL/I label name where an existing breakpoint is\ndeleted.\nALL Indicates all unconditional breakpoints be deleted.\nENTRY Deletes the breakpoint set by the ENTRY operand of the AT or\nUNCOND command in the currently qualified program.\nEXIT Deletes the breakpoint set by the EXIT operand of the AT or\nUNCOND command in the currently qualified program.\nLABEL Deletes the breakpoint set by the LABEL operand of the AT or\nUNCOND command in the currently qualified program.\nDBCALL Deletes the breakpoint set by the DBCALL operand of the AT or\nUNCOND command in the currently qualified program.\nALL ENTRY Deletes the breakpoints set by the ALL ENTRY operand of the AT\nor UNCOND command.\nALL EXIT Deletes the breakpoints set by the ALL EXIT operand of the AT or\nUNCOND command.\nALL LABEL Deletes the breakpoints set by the ALL LABEL operand of the AT\nor UNCOND command.\nALL DBCALL Deletes the breakpoints set by the ALL DBCALL operand of the\nAT or UNCOND command.\nUsage Notes", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0d37ee9d51ce-1", "text": "AT or UNCOND command.\nUsage Notes\nSet a breakpoint by paragraph, procedure, or label name, and delete by the statement number on which the paragraph is\ndeclared and vice versa. For example, consider the following code:\n  041400    0000-INITIALIZATION SECTION.\n  041500\n  041600      MOVE +20 TO VARIABLE-LENGTH-1.\n  041700      MOVE +25 TO VARIABLE-LENGTH-2.\n  041800      MOVE +30 TO VARIABLE-LENGTH-3.\n \nSet a breakpoint on the first statement of the example by either of the following UNCOND commands:\n 708", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "56aa857925fe-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n UNCOND 41400\n     or \n UNCOND 0000-INITIALIZATION\n \nThe breakpoint could be removed by either of the following OFF commands:\n OFF 41400\n     or \n OFF 0000-INITIALIZATION\n \nOFFWN (or OFFC) Command (Remove Conditional Breakpoints)\nUse the OFFWN command to delete conditional breakpoints set by the C, W or V line commands, by the WHEN\ncommand, or in the When panel.\nIf you specify the OFFWN command with no operands, the When panel displays.\nDelete a breakpoint by specifying OFFWN and when-name of the breakpoint to be deleted in the Command field of the\nIntercept panel.\nSyntax\nUse the following syntax for OFFWN and OFFC:\n OFFWN <when-name|ALL>\n \nVariables\nUse the following variables with the OFFWN or OFFC commands:\nwhen-name A user-defined unique label specified in the WHEN command and\nused by the OFFWN command. When-name may be from one to\neight characters in length. A when-name can also be a statement\nnumber. Variable change breakpoints set by the V line command\ngenerate their own when-names (see the description of the V line\ncommand earlier in this section).\nALL Indicates that all conditional breakpoints should be reset.\nPOINT Command (Direct PREV and ADVANCE Pointer)\nThe POINT command causes the PREV and ADVANCE commands to operate from the statement number, paragraph, or\nprocedure, or label name designated in the POINT command.\nSyntax\nUse the following syntax for POINT:\n POINT statement-number|paragraph-name|procedure-name|label-name\n \nEnter this command in its abbreviated form: PO.\nVariables\n 709", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cf4a684b56c5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse the following variables with the POINT command:\nstatement-number A program statement number from which PREV and ADVANCE\nare used.\nparagraph-name A COBOL paragraph name from which PREV and ADVANCE are\nused.\nprocedure-name A PL/I procedure name from which PREV and ADVANCE are\nused.\nlabel-name An assembler or PL/I label name from which PREV and\nADVANCE are used.\nUsage Notes\nYou must turn on the trace facility for the POINT command to function. For example, if the program abended on statement\n13100 and you wanted to review the statements that were executed earlier, the POINT command could be used to\nestablish a statement from which to use the PREV and ADVANCE commands. Suppose a part of the trace table\ncontained the following:\n 13100\n 13000\n   .\n   .\n   .\n 11000\n 10900\n 10800\n 10700\n 10300\n 10200\n 10100\n 09900\n \nIf you entered the statement PO 10300 in the command line, ADVANCE would display and highlight 10700, but PREV\nwould display and highlight 10200.\nIf data monitoring was in effect when the statement that is highlighted from the POINT command was executed, the\nvalues displayed for your data items are from the time before that statement was executed.\nPREV Command (Trace in Reverse)\nThe PREV command causes the display to scroll to the previously executed statement and highlights it. Use the PREV\ncommand to step backward through the execution of the program.\nSyntax\nUse the following syntax for PREV:\n PREV <nnn|P nn>\n \nYou can enter this command in its abbreviated form: P.\nVariables\n 710", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8968d3c69a8c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse the following variables with the PREV command:\nnnn Specifies the number of previously executed statements for the\napplication to scroll. The default is one.\nP Specifies that the previously executed paragraph, procedure, or\nlabel is displayed.\nnn Specifies the number of previously executed paragraphs,\nprocedures, or labels for the application to scroll. The default is\none.\nUsage Notes\nYou must turn on the trace facility for the PREV command to function. You turn on the trace facility by default when you\nfirst invoke the application. For further information on turning the trace facility on and off, see the TRACE command later\nin this section.\nThe PREV command visually displays the flow of execution of the program in reverse. It does not actually reverse the\nexecution or execute the program in reverse.\nThe PREV command does not affect the point at which the application resumes execution.\nIf data monitoring was in effect when the statement that is highlighted from the PREV command was executed, the values\ndisplayed for your data items are from the time before that statement was executed.\nPS Command (Print Stream)\nThe Print Stream (PS) command causes the currently displayed stream to be written to the session log for the current\nsession.\nSyntax\nUse the following syntax for PS:\n PS\n \nUsage Notes\nThe PS command writes the entire stream, not just the portion displayed on the screen. For example, if only the data that\nis currently shown on the screen display is needed, Roscoe  users should allocate an INT1PRNT DD data set and use the\nPRINT PF Key function. Native TSO users can use this command as well. ISPF users should use the ISPF PRINT facility.\nQUALIFY Command (Set Current Program Id)\nThe QUALIFY command identifies the program to which all subsequent commands apply. This qualification is", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8968d3c69a8c-1", "text": "The QUALIFY command identifies the program to which all subsequent commands apply. This qualification is\nautomatically reset by another QUALIFY command, or resulting from the flow of the execution. When testing more than\none program, the listing switches automatically to the qualified program.\nSyntax\nUse the following syntax for QUALIFY:\n QUALIFY program-id\n \nVariables\n 711", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d44aefe4ffa3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse the following variables with the QUALIFY command:\nprogram-id Specifies the PROTSYM member name of the program to which\nthe following commands apply.\nThe program-id of the currently intercepted program is automatically qualified at each program intercept. The qualified\nprogram-id of the program is displayed in the upper left corner of the display.\nUsage Notes\nThe QUALIFY command is useful when you are testing multiple programs. For example, you are testing programs A and\nB. The initial breakpoint occurs in A, but you want to set a breakpoint in B. The following command switches the listing file\nin the Intercept panel to program B:\n QUALIFY B\n \nUse display commands to find and scroll to the statement where you want to set the breakpoint. Issue the AT command,\nand the breakpoint is set in program B. Issue the following commands:\n QUALIFY A\n GO\n \nYour test resumes execution until the breakpoint in program B is encountered.\nQUIT Command (Terminate Session)\nThe QUIT command stops the test session. The Execution Control panel displays so you can do additional testing.\nPressing the END key twice in a row is the same as entering the QUIT command.\nSyntax\nUse the following syntax for QUIT:\n QUIT\n \nUsage Notes\nThe QUIT command is the same as END and CANCEL.\nThe first time you press the END key, the message USE \"END\" TO TERMINATE appears at the top of the screen. Press\nthe END key again.\nRDI or REMOVE Command (Reset Data Item)\nThe RDI command removes from the Intercept panel the lines placed there by the LDI (list data item) or the LDX (list data\nitem in hex) commands, or the L or H line commands, and moves the program listing up.\nSyntax\nUse the following syntax for RDI or REMOVE:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d44aefe4ffa3-1", "text": "Syntax\nUse the following syntax for RDI or REMOVE:\n RDI   data-item|ALL\n \nYou can enter this command in its abbreviated form: RE.\nVariables\n 712", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a2c8ec87eae6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse the following variables with the RDI or REMOVE command:\ndata-item Must be a data item in a LDI command.\nALL Specifies that all LDI items should be deleted from the Intercept\npanel.\nRECORDS Command (Show COBOL Record Formats)\nThe RECORDS command displays the COBOL File Section Display panel. The File Section Display panel shows the\nrecord formats under the file descriptions (FDs). You can modify data values on this display.\nSyntax\nUse the following syntax for RECORDS:\n RECORDS <data-item> <PRINT>\n \nYou can enter this command in its abbreviated form: REC.\nVariables\nUse the following variables with the RECORDS command:\ndata-item Causes a display of the data item, any subordinate level data\nitems, and their data values.\nPRINT Causes the data displayed by the command to be written in the\nsession log.\nUsage Notes\nConsider the following COBOL RECORD definition:\n  FILE SECTION.\n  FD INPUT-FILE.\n       BLOCK CONTAINS 0 RECORDS\n       RECORDING MODE IS F.\n  01 INPUT-RECORD.\n       05 INPUT-NUMBER              PIC X(4).\n       05 INPUT-NAME                PIC X(36).\n       05 INPUT-SSN.\n          10 INPUT-SSN-XXX          PIC X(3).\n          10 INPUT-SSN-YY           PIC X(2).\n          10 INPUT-SSN-ZZZZ         PIC X(4).\n \nIf you enter the RECORDS command without operands, it formats and displays all of the previous data items and their\nvalues.\nThe command REC INPUT-SSN formats and displays INPUT-SSN, INPUT-SSN-XXX, INPUT-SSN-YY and INPUT-SSN-", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a2c8ec87eae6-1", "text": "ZZZZ.\nThe command REC INPUT-SSN-ZZZZ formats and displays INPUT-SSN-ZZZZ.\nThe INPUT-FILE must be open to modify data with the RECORDS command.\nThe RECORDS command is not valid for assembler or PL/I.\n 713", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9ae835c79ada-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIf you are navigating the trace table and data monitoring was in effect for the currently highlighted statement, the values\ndisplayed for your data items will be from the time before that statement was executed.\nREFRESH Command\nUse the REFRESH subcommand when you have split the screen during test execution, and have used one screen to\nchange the value of a data item that is currently displayed on the other screen (screen 2).\nREFRESH, typed on screen 2, lets the application pick up and display the newly updated value.\nSyntax\nUse the following syntax for REFRESH:\n REFRESH\n \nREGS Command\nThe REGS command displays the current application's registers. This command is only valid for assembler programs.\nSyntax\nUse the following syntax for REGS:\n REGS <ON|OFF|DISPLAY|FLOAT|VECTOR>\n \nYou can enter this command in its abbreviated form: REG.\nVariables\nUse the following variables with the REGS command:\nON Displays the general registers in the Keep window.\nOFF Removes the general registers from the Keep window.\nDISPLAY Displays a panel where the general registers, their high halfs, and\nthe access registers are displayed.\nFLOAT Displays a panel where the floating point registers are displayed.\nVECTOR Displays a panel where vector registers are displayed.\nRESET Command\nRESET removes column numbers that are displayed on the Intercept or Display panel by the COLUMN command.\nSyntax\nUse the following syntax for RESET:\n RESET\n \nUsage Notes\nThe RESET command runs from any panel that has a command line that accepts the COLUMN command.\nRESTART Command\nThe RESTART command re-initiates a batch link job to the beginning of the current step being debugged.\n 714", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "875913e1dbcc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n RESTART\n \nUsage Notes\nThis command is only valid under batch link. Foreground users should use the QUIT command.\nRUN Command (Resume Execution)\nThe RUN command resumes execution of the program ignoring all breakpoints. The program continues to execute until\nnormal termination or until it abends. The Execution Control panel displays.\nThis command removes any capability for further program debugging. The application will not intercept abends.\nHowever, if an optional statement number is passed to the RUN command, when execution from the RUN command hits\nthat statement, the RUN command is converted into a GO command. This means that existing breakpoints are honored\nagain.\nNOTE\nUsing the RUN command during a batch link session also issues a SUSPEND command, releasing the terminal.\nSyntax\nUse the following syntax for RUN:\n RUN <statement-number>\n \nVariables\nUse the following variables with the RUN command:\nStatement-number A program statement number where the RUN command is\nconverted to a GO command.\nSDWA Command (System Diagnostic Work Area)\nThe SDWA command displays the System Diagnostic Work Area if a failure occurs. The panel displayed gives the\nfollowing information: the SDWA address, the ABEND code, the PSW, the program name, the EP address, the offset, and\nthe contents of the registers at the time of failure.\nSyntax\nUse the following syntax for SDWA:\n SDWA\n \nSET Command (Change Data Item Value)\nUse the SET command to change the value of a data item.\nSyntax\nUse the following syntax for SET\n SET data-item <=> value|LOW VALUES|HIGH VALUES|SPACES|ZERO|ZEROES|X'hex char string'\n \nNOTE\nData for variables are case-sensitive.\n 715", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5f81bc6a7303-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse the following variables with the SET command:\ndata-item A data item in the monitored program or a COBOL special\nregister. Data-item may be a fixed or variably subscripted data\nitem or an indexed data item. It may also be a qualified data item.\nvalue The new value of the data item.\nLOW-VALUES Indicates that the value of the data item is the figurative COBOL\nconstant of hexadecimal '00', which is the lowest value in the\ncomputer's collating sequence.\nHIGH-VALUES Indicates that the value of the data item is the figurative COBOL\nconstant of hexadecimal 'FF', which is the highest value in the\ncomputer's collating sequence.\nSPACES Indicates that the value of the data item is one or more blanks or\nspaces.\nZEROS | ZEROES Indicates that the value of the data item is one or more zeros.\nhex-char-string 1 to 20 valid hexadecimal characters. The data is replaced from\nleft to right.\nUsage Notes\nAlter data by overtyping on any of the data displays (from DISPLAY, LINKAGE, and RECORDS command). Change\nelementary data items using the SET command on the Intercept panel.\n SET EMPLOYEE-ID = '123-45-6789'\n \nThis entry sets the data item EMPLOYEE-ID to a value of 123-45-6789. Use this command with the command library\nfacility to initialize areas of data for testing. See the INCLUDE command described earlier in this section for further\ninformation on the command library facility.\nModify fixed or variably subscripted data items or index data items, that is, table entries, using the SET Command, as in\nthe following examples:\nCOBOL: SET WA-TI(4) = 6", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5f81bc6a7303-1", "text": "the following examples:\nCOBOL: SET WA-TI(4) = 6\nSets the fourth element in the table WA-T1 to 6.\nSET WA-TI2(SUB1,SUB2) = 'S1S2'\nSets an element in WA-T2 depending on the values of SUB1 and\nSUB2 to S1S2.\nSET WA-T1-1A OF WA-TABLE-1 (2)= 2\nSets the second element of the non-unique table WA-T1-1A in the\nunique table WA-TABLE-1 to 2.\nPL/I: SET WA_TI(4) = 6\nSets the fourth element in the table WA_T1 to 6.\nSET WA_TI2(SUB1,SUB2) = 'S1S2'\nSets an element in WA_T2 depending on the values of SUB1 and\nSUB2 to S1S2.\nSET WA_TABLE_1.WA_T1_1A(2) = 2\nSets the second element of the non-unique table WA_T1_1A in\nthe unique table WA_TABLE_1 to 2.\nSET WA_TBL_PTR->WA_T1_1A(2) = 2\nSets the second element of the based table WA_T1_1A in the\ntable allocation pointed to by WA_TBL_PTR.\n 716", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "643b6cff5dbf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIf you are navigating the trace table and data monitoring was in effect for the currently highlighted statement, the SET\ncommand is not enabled.  You must first issue the CS command to reset the tracing and then issue the SET command.\nCOBOL programs can be compiled with the ARITH(EXTEND) parameter which will allow a numeric field to be greater\nthan 18 bytes. The SET command is unavailable to modify fields longer than 18 bytes. The CORE command can be used\nto edit these fields.\nSKIP Command (Skip a Statement)\nThe SKIP command causes the statement number specified to be skipped when the program is executed.\nThe Intercept panel shows an S to the left of any statements that are to be skipped.\nSkip is considered an unconditional breakpoint and may be reset using the OFF control command or the O or X line\ncommand.\nSyntax\nUse the following syntax for SKIP:\n SKIP statement-number\n \nVariables\nUse the following variable with the SKIP command:\nstatement-number Specifies the statement-number in the program that is to be\nskipped when the program is executing.\nUsage Notes\nSkipping a statement causes the execution of that statement to be bypassed entirely, with execution resuming at the verb\nor label whose statement number is nearest to and greater than the statement being skipped. In some instances, this\nmay not result in the required execution path, with execution resuming at a statement that would otherwise not have been\nexecuted.\nThis can occur when the statement being skipped is any of the following statements:\n\u2022The last statement in the program\n\u2022The last statement in a PERFORMed paragraph\n\u2022Immediately followed by an ELSE statement\nWARNING\nIn those instances that may not result in the required execution path, you should avoid using a SKIP command,\nand instead use an unconditional breakpoint with an associated GO command.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "643b6cff5dbf-1", "text": "and instead use an unconditional breakpoint with an associated GO command.\nTo set an unconditional breakpoint, type AT on the command line and press Enter. When prompted, enter the statement\nnumber where the breakpoint should occur, which is the statement you wish to skip. Type GO nnnnn  in the Command\nfield, where nnnnn  is the number of the statement at which execution should resume.\nIn this example, a SKIP command on statement 917 would cause execution to resume at statement 919, which is not the\nrequired execution path:\n           000915             IF A NOT EQUAL ZERO\n           000916                  MOVE A TO OPTION-CHOSEN\n       S   000917                  PERFORM PROCESS-SELECTION\n           000918             ELSE\n           000919                  DISPLAY 'ERROR: INVALID SELECTION'\n           000920                  MOVE 12 TO RETURN-CODE.\n 717", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "35d444bf07c5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n           000921             PERFORM LOG-RESULT.             \n \nInstead, use the AT command to force execution to resume at statement 921:\n  -------------------- CA InterTest Batch BREAKPOINT PANEL ---------------------\n  OPTION ===> S\n  \n     S - SET A BREAKPOINT\n     R - RESET A BREAKPOINT\n     L - OR BLANK, LIST THE BREAKPOINTS\n  \n  SPECIFY PROGRAM NAME AND STATEMENT NUMBER:\n     PROGRAM NAME ===>\n     STATEMENT    ===> 917\n  \n     COUNT        ===>          AFTER ===> N  (Y/N)\n  \n  COMMANDS TO BE EXECUTED AT BREAKPOINT:\n  ===> GO 921\n \nYou should also be aware that the use of a SKIP command may result in incorrect results when the program has been\noptimized, either by the IBM optimize option or by Optimizer/II  or Optimizer/II . Skipping a statement in an optimized\nprogram may result in the loss of calculations or intermediate results, which may affect future statements.\nSLOW (or AUTOSTEP) Command (Slowly Resume Program Execution)\nThe SLOW command resumes execution of the program one verb at a time and displays the Intercept panel between the\nexecutions of each verb.\nSyntax\nUse the following syntax for SLOW or AUTOSTEP:\n SLOW     <nnn|FAST>  \n \nYou can enter this command in its abbreviated form: AUTO.\nVariables\nUse the following variables with the SLOW command:\nnnn Specifies the number of seconds to halt the display between verb\nexecutions. The default is two seconds.\nFAST Executes the program without halting between screen refreshes.\nUsage Notes\nAUTOSTEP (or AUTO) is a synonym for SLOW.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "35d444bf07c5-1", "text": "Usage Notes\nAUTOSTEP (or AUTO) is a synonym for SLOW.\nInterrupt this feature by pressing the Attention key. For information on the Attention key, see Stop a Looping Program in\nGuidelines for Novice Users.\nOccasionally when you press the Attention key, the program stops and the short message field SUBCOMMAND ABEND\nis displayed. If this occurs, issue the NEXT command to refresh the display.\n 718", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6ae9284c5ce5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSNAP Command (Produce a SNAP Report)\nThe SNAP command produces a SymDump  Batch, Optimizer/II , or Optimizer/II  SNAP report, if you have one of these\nproducts initialized. For details on the SNAP report, see the appropriate product's documentation.\nSyntax\nUse the following syntax for SNAP:\n SNAP\n \nNOTE\nMinimum release requirements are SymDump  Batch 2.0, Optimizer/II  3.0, or Optimizer/II  7.0.\nSPEED Command (Accelerate Program Testing)\nThe SPEED command deactivates the trace and frequency facilities.\nSyntax\nUse the following syntax for SPEED:\n SPEED <ON|OFF>\n \nVariables\nUse the following variables with the SPEED command:\nON Turns off trace and frequency counting. Issues the TRACE OFF\nand the FREQ OFF commands.\nOFF Enables tracing and statement frequency counting. Issues the\nTRACE ON and the FREQ ON commands.\nUsage Notes\nThis feature is very useful when testing a large program. It turns off trace and frequency counting and therefore improves\nperformance. For example, to test a COBOL program with 20,000 PROCEDURE DIVISION statements, set a breakpoint\nat statement 15000, and step through the program when you get to that point. The commands to perform this are as\nfollows:\n AT 15000\n SPEED\n \nWhen statement 15000 is reached, an Intercept panel is displayed. To step through the program from this point, enter the\nfollowing to turn on trace and frequency counting:\n SPEED OFF\n STEP 1\n \nSTEP Command (Set Count for GO Command)\nThe STEP command sets the execution mode to step operation. For each GO command, the specified number of verbs is", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6ae9284c5ce5-1", "text": "executed, and the STEP COUNT Intercept panel is displayed when that number of verbs has executed.\nSyntax\n 719", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bf2e4596015f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse the following syntax for STEP:\n STEP <nnnn|BEFORE|AFTER>\n \nYou can enter this command in its abbreviated form: ST.\nVariables\nUse the following variable with the STEP command:\nnnnn Specifies the number of verbs to be executed each time you\nenter a GO command. Setting the STEP count to 0 (zero) turns\noff step counting so that the next GO command executes until\na breakpoint is encountered, an abend occurs, or the program\nreaches normal termination. The maximum step count that you\ncan enter is 9999.\nBEFORE Specifies that execution should stop before the statement that\nsatisfies the STEP count. This is the default.\nAFTER Specifies that execution should stop after the statement that\nsatisfies the STEP count.\nNotes:\nIf STEP is set to AFTER, statements that cause execution to leave\nthe current program, such as GOBACK for COBOL, have no effect\non the STEP count.\nIf data monitoring was in effect, all data item changes are captured\nat a point in time before  COBOL statements referencing them are\nexecuted even when STEP AFTER is set.\nNOTE\nIf no variable is used with the STEP command, the current STEP count and status is displayed in the upper right\nhand corner.\nSUSPEND Command (Suspend a Batch Link Session)\nUse the SUSPEND command to detach a terminal from a batch link debugging session without terminating the session.\nSyntax\nUse the following syntax for SUSPEND:\n SUSPEND\n \nYou can enter this command in its abbreviated form: SUS.\nUsage Notes\nThe SUSPEND command is only valid for batch link debugging sessions and you can only use it from the Monitor Control\nor Intercept panels.\nA suspended batch link session becomes immediately available for selection from the Batch Link Selection panel.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bf2e4596015f-1", "text": "A suspended batch link session becomes immediately available for selection from the Batch Link Selection panel.\nReconnect a suspended session by the same user or by a different user. Regardless of which user selects the suspended\nsession, the session is resumed from exactly the same point at which the session was suspended, and continues to use\nthe same profile member that was defined in the INT1OPTS file.\n 720", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "63c8f5df0d5a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTRACE SOURCE Command (Trace with Source Code Displayed)\nThe TRACE SOURCE command functions similar to the TRACE command, but displays the code being traced as well as\nthe statement number.\nSyntax\nUse the following syntax for TRACE SOURCE:\n TRACE SOURCE n\n \nYou can enter this command in its abbreviated form: TR SO.\nVariables\nUse the following variables with the TRACE SOURCE command:\nn Specifies the maximum number of trace entries to be displayed.\nThe default is 500.\nTRACE Command (Controls Program Trace Entries)\nIf the TRACE command does not have an operand, it displays the Program Trace Display panel. This panel shows\nstatement numbers in the order they were executed.\nSyntax\nUse the following syntax for TRACE:\n TRACE <ON|OFF|n>\n \nYou can enter this command in its abbreviated form: TR.\nVariables\nUse the following variables with the TRACE command:\nON Turns on statement tracing. The number of entries retained is set\nby the TRACE(n) parameter in the initialization PARMLIB member.\nThe default is 500.\nOFF Turns off statement tracing.\nn Specifies the number of entries to be saved in the trace table\nand displayed by the TRACE command. The current trace table\nis cleared and reset. This overrides the value specified in the\nTRACE(n) initialization PARMLIB member.\nUsage Notes\nThe trace setting is remembered from session to session.\nIt is possible to view the statements that have been executed in reverse by using the PREVIOUS command, instead of\nhaving to view the trace display.\nIf data monitoring is in effect for any program in your application, changing the trace table resets the effects of the\nDATAMON command.\n 721", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "181814a0e996-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTRP Command (Trace Paragraphs)\nThe TRP command invokes the Program Trace Display panel. This panel shows statement numbers and paragraph,\nprocedure, or label names executed.\nSyntax\nUse the following syntax for TRP:\n TRP\n \nUsage Notes\nThe trace facility must be enabled for the TRP command to function.\nUSING Command (Assign a Register or Address to a DSECT or CSECT)\nThe USING command lets you assign a register or address for the debugger to use to map a DSECT or CSECT that has\nno current using in the program being debugged. This command is only valid when debugging an assembler program.\nSyntax\nUse the following syntax for USING:\n USING dsect|csect register|address\n \nVariables\nUse the following variables with the USING command:\ndsect Assembler DSECT that you wish to map\ncsect Assembler CSECT that you wish to map\nregister Register that maps the DSECT or CSECT\naddress Address that maps the DSECT or CSECT\nWHEN (or COND) Command (Set Conditional Breakpoints)\nThe WHEN command sets conditional breakpoints. There are two types of conditional breakpoints and the format of the\ncommand syntax is different for each:\nUse this Syntax format For this Type of Conditional Breakpoint\n1 Whenever the value of a specified data item changes\n2 When a relationship between two data items is true, for example,\n'SUBSCRIPT-1 GT 4'\nEnter operands in the When panel or in the COMMAND field of the Intercept panel in one of the following formats:\nFormat 1 This type stops the program's execution any time the value of the\nspecified data item changes. For example: WHEN whename1\nR1498_STATUS.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "181814a0e996-1", "text": "specified data item changes. For example: WHEN whename1\nR1498_STATUS.\nFormat 2 This type checks a relational expression for a TRUE condition\nbefore intercepting the program. For example:\nWHEN whename2 R1498_STATUS GT G\n 722", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eaacf14e4b82-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIf the when-name  specified is a statement number, the WHEN condition is only tested before executing that statement\nnumber. In this case, the application does not test for the condition before each statement. This local type of conditional\nbreakpoint reduces computing overhead.\nNOTE\n\u2022WHEN conditions that are set for subscripted or indexed items are checked only if the subscript or index is\nvalid.\n\u2022If you use the WHEN command without operands, the WHEN panel is displayed. Set, reset, or list conditional\nbreakpoints from this displayed WHEN panel.\nSyntax Format 1 When the value of a specified data Item changes\nSyntax\nUse the following syntax for WHEN or COND:\n  WHEN <when-name data-item-1> <BEFORE|AFTER> <(subcommand-list)>\n \nYou can enter this command in one of its abbreviated forms: WH, WN or C.\nVariables\nUse the following variables with the WHEN or COND commands:\nwhen-name A user-defined unique label or a statement number; if the when-\nname is a statement number, the when condition is only checked\nbefore the statement is executed. It is also displayed in the title\nline of the W when-name Intercept panel.\ndata-item-1 The data item is examined before each verb is executed unless\nthe when-name is a statement number in which case the data item\nis only examined before executing that statement (local conditional\nbreakpoint). Whenever the value of the data item changes, a W\nwhen-name Intercept panel is displayed. Data-item-1 may be a\nfixed or variably subscripted, indexed, or qualified data item.\nBEFORE Specifies that execution should stop before  the statement when\nthe condition is met. (That is, the application detected that the\nvalue of the specified data-item  has changed.) This is the default\nbehavior.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eaacf14e4b82-1", "text": "value of the specified data-item  has changed.) This is the default\nbehavior.\nAFTER Specifies that execution should stop after the statement when the\ncondition is met. (That is, the application detected that the value of\nthe specified data-item  has changed.)\nsubcommand-list A list of application commands, separated by semicolons, to be\nexecuted when the breakpoint is encountered during the test. The\nsubcommand-list is enclosed in parenthesis.\nSyntax\nUse the following syntax for WHEN or COND:\n  WHEN  <when-name <data-item-1 <operator <data-item-2|value> <BEFORE}AFTER>>\n         <(subcommand-list)>>>\n \nYou can enter this command in one of its abbreviated forms: WH, WN or C\nVariables\n 723", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d5d6b1da3953-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse the following variables with the WHEN or COND commands:\ndata-item-1 Based on the value of the operator, data-item-1 is compared\nto data-item-2. Whenever the expression is true, a W when-\nname Intercept panel is displayed. Data-item-1 may be a fixed or\nvariably subscripted, indexed, or qualified data item.\noperator A relational operator used to compare data-item-1 to data-item-2.\nValues can be any one of the following:\nEQ or = Equal to\nNE or ?= Not equal to\nLE or <= Less than or equal to\nGE or >= Greater than or equal to\nLT or < Less than\nGT or > Greater than\nNote: => and =< are not permitted.\ndata-item-2 Compared to data-item-1. When the comparison is true, a W\nwhen-name Intercept panel is displayed. A value can be used in\nplace of data-item-2. Data-item-2 may be fixed subscripted, an\nindexed data item, or a qualified data item.\nvalue Specifies a constant value, which you can use in place of data-\nitem-2. This value may be one of the following figurative COBOL\nconstants: LOW-VALUES, HIGH-VALUES, ZEROS, or SPACES.\nThis value may also be hex data in the format following:\nX'hex-char-string'\nwhere hex-char-string is 1 to 20 valid hexadecimal characters.\nBEFORE Specifies that execution should stop before  the statement when\nthe condition is met. (The specified condition  is TRUE.) This is the\ndefault behavior.\nAFTER Specifies that execution should stop after the statement when the\ncondition is met. (The specified condition  is TRUE.)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d5d6b1da3953-1", "text": "condition is met. (The specified condition  is TRUE.)\nsubcommand-list A list of application commands, separated by semicolons, to be\nexecuted when the breakpoint is encountered during the test. The\nsubcommand-list is enclosed in parenthesis.\nUsage Notes\nGlobal conditional breakpoints (the when-name is not specified using a statement number) are breakpoints whose\nconditions are checked before every executed statement and are very resource intensive and may require considerable\noverhead. When possible, use local conditional breakpoints (the when-name is specified using a statement number) which\nare only checked at the time a particular statement is executed. See the Line Commands section earlier in this article for\ninformation on setting local conditional breakpoints with the line commands C, W, and V.\nA before  breakpoint is a breakpoint that stops before  a statement is executed. A before  breakpoint will never stop before\na statement that makes  the condition true. It would only stop before the next statement which follows the statement that\nmakes the condition true. Thus, a  before  WHEN condition is evaluated before a statement is executed, and if true, the\nbreakpoint occurs immediately, before that statement is executed.\nAn after breakpoint is a breakpoint that stops after a statement that makes the condition true. Thus, an after WHEN\ncondition is evaluated after the statement is executed, and if true, the breakpoint occurs immediately, after the statement\nis executed.\n 724", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "037ea6b46153-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n* Command (Add Comments in Session Log)\nThe * command lets you specify a comment to be inserted in the session log. The text following the * is inserted in the\ncurrent session log exactly as typed.\nSyntax\nUse the following syntax for *:\n * text\n \nVariables\nUse the following variable with the /clist command:\nText Comment to be inserted in the session log\n/clist Command (Execute CAMRCMD)\nThis product provides a facility for executing a CLIST from within the application. By typing in a slash (/) followed by\na string, the CAMRCMD CLIST is called with a parameter, which is the string that follows the slash. Review CLIST\nCAMRCMD for further modification instructions.\nSyntax\nUse the following syntax for /clist:\n /clist\n \nVariables\nUse the following variable with the /clist command:\nClist  The parameter with which the CAMRCMD CLIST is called.\nReport Commands\nThe software provides report commands to create reports that you can print and analyze offline. The reports show path\ncoverage of program execution and a histogram report displaying the execution frequencies by statement number in\ngraphic format. Both reports have an execution summary showing the number of executable statements, the number of\nstatements executed, and the percentage of path coverage.\nNOTE\nThe frequency counter must be on (using the COUNTS command) during testing if any of these reports are to\nbe produced.\nThe reports use the ddname INT1REPT. The allocation of INT1REPT can be either to a SYSOUT class or to a disk data\nset. Sample allocations are as follows.\nAllocation of INT1REPT to a SYSOUT class:\nALLOC DD(INT1REPT) SYSOUT(A)\nAllocation of INT1REPT to a disk data set:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "037ea6b46153-1", "text": "Allocation of INT1REPT to a disk data set:\nALLOC DD(INT1REPT) DSN(INT.REPORT) NEW SPACE(2 1) CYL\n 725", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "365b17816e07-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIf the ddname is allocated to a disk data set, the issuance of each report command completely rewrites the data set. If you\nwould like to obtain both reports, perform the following steps:\n1.Allocate the ddname INT1REPT to a data set.\n2.Enter the HIST command.\n3.Reallocate the INT1REPT to another data set.\n4.Enter the XSUM command.\nHISTOGRAM Command (Graph Execution Frequencies)\nThe HISTOGRAM command writes an execution histogram to ddname INT1REPT. The histogram consists of one line\nper executable statement. The line contains the statement number, the execution frequency counter, and a graphic\nrepresentation of the number of times the statement has been executed.\nThe final page of the report identifies the number of statements in the program, an indication of the number of statements\nthat were executed, and the percentage of the statements that were executed during this test.\nSyntax\nUse the following syntax for HISTOGRAM:\nHIST <scale>\nYou can enter this command in its abbreviated form: HI.\nUse the scale parameter to specify the histogram scale to be used. For example, a scale value of 10 would cause one\nasterisk to be printed on the histogram for every 10 executions of a statement.\nIf you do not specify a scale, the application automatically selects a scale in a multiple of five that causes no overflow to\noccur.\nThe histogram produces correct output only if the test was produced with FREQ ON and TRACE ON. A sample histogram\nreport follows:\n1CA InterTest/Batch       Execution Histogram For Program-ID: CAMRCOB2     Date\n0                                                                              \n 000875 0001 |*                                                                 \n 000876 0001 |*                                                                 \n 000886 0001 |*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "365b17816e07-1", "text": "000876 0001 |*                                                                 \n 000886 0001 |*                                                                \n 000887 0001 |*                                                                 \n 000889 0001 |*                                                                 \n 000890 0001 |*                                                                 \n 000891 0001 |*                                                                 \n 000895 0002 |**                                                                \n 000896 0002 |**                                                                \n 000897 ---- |                                                                 \n 000899 0002 |**                                                                \n 000900 0002 |**                                                                \n 000901 0001 |*                                                                \n 000902 0001 |*                                                                 \n 000904 ---- |                                                                  \n 000906 0001 |*                                                                \n 000908 ---- |                                                                  \n 000909 0002 |**                                                                \n 000910 0002 |**                                                               \n 726", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a832579fef0b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 000914 0001 |*                                                                 \n 000915 0001 |*                                                                 \n 000917 0001 |*                                                                \n 000920 0001 |*                                                                 \n 000921 ---- |                                                                  \n 000923 ---- |                                                                  \n 000925 0001 |*                                                                 \n 000931 0001 |*                                                                 \n 000932 0001 |*                                                                 \n 000933 ---- |                                                                  \n 000934 ---- |                                                                  \n 000935 ---- |                                                                  \n 000938 ---- |                                                                 \n 000945 ---- |                                                                  \n 000946 ---- |                                                                  \n 000953 ---- |                                                                 \n 000954 ---- |                                                                  \n 000957 ---- |                                                                  \n 000958 ---- |                                                                 \nA sample histogram report summary follows:\n1CA InterTest/Batch       Execution Histogram For Program-ID: CAMRCOB2      Date\n-Session Number: 1,890 For Userid user99                                       \n-Number of executable statements: 236                                           \n0Number of statements executed during this test: 78                             \n0Percentage of statements executed during this test: 33                         \nXSUM Command (Execution Summary Report)\nThe XSUM command writes an Execution Summary report to ddname INT1REPT. The summary report consists of the\nprogram listing with the execution frequency counter to the left of each valid executable statement.\nThe final page of the report identifies the number of executable statements in the program, an indication of the number of\nstatements that were executed, and the percentage of the statements that were executed during this test.\nSyntax\nUse the following syntax for XSUM:\nSUM <UNEXEC>\nVariables\nUse the following variable with the XSUM command:\nUNEXEC\nSpecifies that the report should only contain statements that have not been executed.\nA sample XSUM report follows:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a832579fef0b-1", "text": "A sample XSUM report follows:\nPP 5740-CB1 RELEASE 2.3   JULY 24, 2014                IBM OS/VS COBOL\n \n 16.20.10  DATE FEB   3,2014\n \n 727", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0a82c8cebabe-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n         1                          16.20.10                FEB 3,2014\n \n               100010  IDENTIFICATION DIVISION.\n               100020  PROGRAM-ID.  SCRIPT.\n               100030  DATE-COMPILED.  FEB 3,2014.\n               100050    ENVIRONMENT DIVISION.\n               100060    DATA DIVISION.\n               100070    WORKING-STORAGE SECTION.\n               100080    01  BIN-REC.\n               100090     05  BIN1        PIC 9999 VALUE 0.\n               100100     05  BIN2        PIC 9999 VALUE 0.\n               100110     05  BIN3        PIC 9999 VALUE 0.\n               100120     05  BIN4        PIC 9999 VALUE 0.\n               100130     05  MOVE-DISP   PIC X(6).\n               100140*\n               100150    PROCEDURE DIVISION.\n               100160*\n0001           100170    INITIALIZATION SECTION.\n0001           100180        DISPLAY 'PROGRAM STARTING'.\n0001           100190    BIN SECTION.\n0010           100200    LOOP-MOVE.\n0010           100210        IF BIN1 > 8\n               100220          OR BIN2 > 346\n               100230          OR BIN3 > 77\n               100240          OR BIN1 NOT = BIN4\n               100250          OR MOVE-DISP = 'INTCOB'\n0001           100260             MOVE ZERO TO BIN1\n0001           100270             GO TO LOOP-MOVE-END.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0a82c8cebabe-1", "text": "0001           100270             GO TO LOOP-MOVE-END.\n0009           100280        ADD 1 TO BIN1.\n0009           100290        ADD 3 TO BIN2.\n0009           100300        ADD 9 TO BIN3.\n0009           100310        ADD 1 TO BIN4.\n0009           100320        MOVE BIN1 TO MOVE-DISP.\n0009           100330        GO TO LOOP-MOVE.\n0001           100340    LOOP-MOVE-END.\n0001           100350        DISPLAY MOVE-DISP.\n0001           100360        MOVE ZERO TO BIN3.\n0022           100370    NEXT-LOOP.\n0022           100380        IF BIN3 > 20\n0001           100390           GO TO NEXT-LOOP-END.\n0021           100400        ADD 1 TO BIN3.\n0021           100410        GO TO NEXT-LOOP.\n0001           100420    NEXT-LOOP-END.\n0001           100430        DISPLAY MOVE-DISP.\n0001           100440        MOVE ZERO TO BIN2.\n0001           100450    LAST-LOOP.\n0041           100460        IF BIN2 < 40\n0040           100470          ADD 1 TO BIN2\n0040           100480          GO TO LAST-LOOP.\n0001           100490    LAST-LOOP-END.\n0001           100500          DISPLAY BIN2.\n0001           100510          DISPLAY 'END OF PROGRAM'.\n0001           100520          STOP RUN.\n 728", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c30907fdc767-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nA sample XSUM report summary follows:\nCA InterTest Batch       EXECUTION SUMMARY REPORT FOR PROGRAM-ID: SCRIPT\n \nDATE: 02/03/14 TIME: 16:21:07 \n \nSESSION NUMBER: 0127 FOR USERID USER01\n \nNUMBER OF EXECUTABLE STATEMENTS: 000032 \n \nNUMBER OF STATEMENTS EXECUTED DURING THIS TEST: 000032 \n \nPERCENTAGE OF STATEMENTS EXECUTED DURING THIS TEST: 100\nA sample XSUM UNEXEC report follows:\n                     UNEXECUTED STATEMENTS AND PARAGRAPHS REPORT                \n --->  000457                  MOVE 'B' TO R1498-STATUS                         \n --->  000464                               MOVE 'T' TO R1498-STATUS            \n --->  000468                      MOVE 'H' TO R1498-STATUS.                    \n --->  000478               PERFORM 900-WRITE-ERROR THRU                        \n --->  000480               GO TO RETURN-TO-OPSYS.                              \n --->  000497            GOBACK.                                                \n --->  000513                GO TO DEMONSTRATE-SLOW-COMMAND.                    \n --->  000515                GO TO DEMONSTRATE-CONDITIONAL-BKPT.                \n --->  000517                GO TO DEMONSTRATE-SPLIT-SCREEN.                    \n --->  000519                GO TO DEMONSTRATE-LOOP-DETECTION.                  \n --->  000521                GO TO DEMONSTRATE-PREV-COMMAND.                    \n --->  000523                GO TO DEMONSTRATE-PROCESS-TABLE.                   \n --->  000525                GO TO DEMONSTRATE-HIST-COMMAND.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c30907fdc767-1", "text": "--->  000525                GO TO DEMONSTRATE-HIST-COMMAND.                    \n --->  000531        DEMONSTRATE-SLOW-COMMAND.                                  \n --->  000532            MOVE ZERO    TO OPTION-CHOSEN.                         \n --->  000537        SLOW-COND.                                                 \n --->  000538            MOVE SPACES  TO X-AXIS.                               \n --->  000539            MOVE ZEROES  TO YTD, TOTAL-GROSS.                     \n --->  000541        PAY-CALC.                                                 \n --->  000542            PERFORM POPULATE-GRAPH THRU POPULATE-GRAPH-EX         \n --->  000545        PAY-CALC-EX.                                              \n --->  000546            MOVE SPACES      TO CHEQUE-LINE.                      \n --->  000547            MOVE TOTAL-GROSS TO CHEQUE-AMOUNT.                    \n --->  000548        PAY-RETURN.                                               \n --->  000549            GO TO OPTIONS.                                        \n --->  000551        POPULATE-GRAPH.                                           \n --->  000552            MOVE MONTH-ITEM(SUB-4)     TO X-AXIS-YTD.             \n --->  000553            MOVE TOKEN-ITEM            TO X-AXIS-R(SUB-4).        \n --->  000554            ADD  MONTHLY-AMOUNT(SUB-4) TO YTD.                    \n --->  000555            MOVE YTD                   TO TOTAL-GROSS.            \n --->  000556        POPULATE-GRAPH-EX.                                        \n --->  000557            EXIT.                                                 \n --->  000558        DEMONSTRATE-CONDITIONAL-BKPT.                             \n --->  000559            MOVE ZERO    TO OPTION-CHOSEN.  \n --->  000561        CONDITIONAL-BREAKPOINT.                                  \n 729", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "039eeea6c90d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n --->  000562            MOVE ZEROES  TO BILL-YTD, SUB-TOTAL.                 \n --->  000568            PERFORM BILL-CALC THRU BILL-CALC-EX                  \n --->  000572            MOVE SPACES      TO CHEQUE-LINE.                     \n --->  000573            MOVE TOTAL-GROSS TO CHEQUE-AMOUNT.                   \n --->  000574            GO TO OPTIONS.                                       \n --->  000576        BILL-CALC.                                               \n --->  000577            ADD BILLING-AMOUNT(SUB-7) TO SUB-TOTAL.              \n --->  000578            MOVE SUB-TOTAL            TO BILL-YTD.               \n --->  000579        BILL-CALC-EX.                                            \n --->  000580            EXIT.                                                \n --->  000583        DEMONSTRATE-SPLIT-SCREEN.                                \n --->  000584            MOVE ZERO    TO OPTION-CHOSEN.                       \n --->  000589        SPLIT-SCREEN.                                            \n --->  000590            MOVE  R1498-TIMEO TO R1498-TIME.                     \n --->  000591            GO TO OPTIONS.                                       \n --->  000600        DEMONSTRATE-PREV-COMMAND.                                \n --->  000601            MOVE ZERO    TO OPTION-CHOSEN.     \nSession Log Facility (Review Debugging Session)\nThe application session log facility records and subsequently enables a user to review the activities of a debugging\nsession.\nThe session log contains the following:\n\u2022An entry identifying the user ID and session number\n\u2022Two lines for each program intercept. The first identifies the program and intercept reason code. The second is a copy\nof the TRACE line as it appeared on the Intercept panel.\n\u2022All input commands", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "039eeea6c90d-1", "text": "of the TRACE line as it appeared on the Intercept panel.\n\u2022All input commands\n\u2022Any comments entered by the user using the * command on the Intercept panel during the testing session\n\u2022Any WORKING STORAGE SECTION, LINKAGE SECTION, or RECORDS data displayed using the DI, LI, or RE\ncommand with the PRINT option or the P line command\nA sample session log with dynamic symbolic support deactivated follows:\n*INTERTEST BATCH SESSION #1168 FOR USER USER01  BEGINS AT 12:59:30 ON 09/09/14.\n*SYMBOLIC FOR CAMRASM LOADED FROM==> NDVRTS.USER01.PROTSYM\n*  INTERCEPT IN PROGRAM CAMRASM  AT #000005 REASON: *INITIAL*                   \n*                                                                               \nAT START                                                                        \nAT GOBACK                                                                       \nGO                                                                              \n                                                                                \n*  INTERCEPT IN PROGRAM CAMRASM  AT #000025 REASON: UNCOND BEFORE               \n*000025                                                                         \nGO                                                                              \n                                                                                \n*  INTERCEPT IN PROGRAM CAMRASM  AT #000147 REASON: ABEND S0C7                  \n*000147 000145 000144 000142 000141 000140 000139 000137 000136 000135 000134   \nSET TASKNUM = 0                                                                 \nGO                                                                              \n                                                                                \n*  INTERCEPT IN PROGRAM CAMRASM  AT #000265 REASON: UNCOND BEFORE               \n 730", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "61c0d3d4b2ec-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n*000265 000260 000259 000258 000257 000255 000254 000253 000252 000251 000250   \nXSUM                                                                            \nGO                                                                              \nA sample session log with dynamic symbolic support activated follows:\n*INTERTEST BATCH SESSION #1169 FOR USER USER01  BEGINS AT 13:10:30 ON 03/29/14.\n* SYMBOLIC FOR: CAMRASM AUTO POPULATED TO: NDVRTS.USER01.PROTSYM\n* SYMBOLIC FOR: CAMRASM LOADED FROM=> NDVRTS.USER01.PROTSYM     \n*  INTERCEPT IN PROGRAM CAMRASM  AT #000005 REASON: *INITIAL*     \n*                                                                 \nAT START                                                          \nAT GOBACK                                                         \nGO                                                                 \n                                                                   \n*  INTERCEPT IN PROGRAM CAMRASM  AT #000025 REASON: UNCOND BEFORE  \n*000025                                                            \nGO                                                                 \n                                                                   \n*  INTERCEPT IN PROGRAM CAMRASM  AT #000147 REASON: ABEND S0C7     \n*000147 000145 000144 000142 000141 000140 000139 000137 000136 000135 000134   \nSET TASKNUM = 0                                                    \nGO                                                                 \n                                                                   \n*  INTERCEPT IN PROGRAM CAMRASM  AT #000265 REASON: UNCOND BEFORE  \n*000265 000260 000259 000258 000257 000255 000254 000253 000252 000251 000250   \nXSUM                                                               \nGO                                                                 \nThe application session log facility records and subsequently enables a user to review the activities of a debugging\nsession as shown in the previous panel. The session log may be copied into a member of a partitioned data set and", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "61c0d3d4b2ec-1", "text": "subsequently edited and used as the subject of an INCLUDE command.\nPre-allocating the ddname INT1CLOG activates the session log. Allocate the log to a disk file or to a SYSOUT class. In\neither case, there is no need to specify any DCB information as the application sets it to:\nRECFM=FB,LRECL=80,BLKSIZE=6160\nBecause user ID keeps the session log, each user who wants to use the log facility must have a session log data set. The\ndata set must be a sequential file. A sample CLIST, INT1CLOG, exists in the CAI.CAVHCLS0 data set to create a sample\nsession log data set.\nTesting Procedures\nThis section describes how to do the following procedures:\n\u2022Prepare a program for testing.\n\u2022Identify to the application the program to be tested.\n\u2022Start and stop program testing at selected statements.\n\u2022Test IMS applications.\n\u2022Test DB2 applications.\n 731", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "10c49daf4814-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nGuidelines for Novice Users\nThis section provides an overview and checklist for novice users of the Foreground option. The following sections assist\nyou in preparing your programs for testing and using the application panels and commands to test your programs. For\ndetailed information on the application panels used with the Foreground Option, see Debugging Panels, and for detailed\ninformation concerning the commands used with the Foreground Option, see Debugging Commands.\nPreparation for Test Execution\nUse the following steps to compile a program to be tested under the control of the application and to begin foreground test\nexecution.\nIf you are testing an IMS program, first read this section, then read Test IMS Applications. Also, if you are testing a DB2\napplication, see Test IBM DB2 Applications. If you are testing an application that uses any database, batch link is the\nsuggested method for debugging.\n1.Compile the program that you wish to test using the procedure set up by your installer. This procedure has a post-\ncompile step that generates the symbolic information needed to debug your program. Alternatively, you can do the\nfollowing:\n\u2013Add the symbolic information using the Utilities panel if you have the listing available.\n\u2013Take advantage of the dynamic symbolic support feature, if you have Endevor  r7 SP2 or later installed.\n2.Log in to TSO and enter the TSO command PROFILE WTPMSG. This command causes all messages that normally\nappear in the batch job log (write-to-programmer messages) to be sent to the terminal.\nIf you place the PROFILE WTPMSG in the application CLIST, you will not need to reenter it each time you invoke the\napplication.\n3.Invoke the application (ask you technical support personnel for instructions, if needed).", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "10c49daf4814-1", "text": "application.\n3.Invoke the application (ask you technical support personnel for instructions, if needed).\nIf you are testing an IMS or DL/I program, also review the instructions given in the section Testing IMS Applications.\nIf you are testing under Roscoe , also review the instructions in the section Testing Under Roscoe .\n4.When the Primary Option Menu displays, select Option 1: Foreground.\n5.Fill in the relevant information on the Execution Control panel. Enter the name of the main program of the application\nthat you want to debug, the execution parameters, if there are any, and the STEPLIB to be used for this test. If your\nexecution JCL was converted to ALIB format, you can specify that ALIB data set and member here. Then all the\ninformation, described previously will be extracted from the ALIB file and the DDs that are required for execution will\nalso be allocated. If you do not have an ALIB for this application, you will need to allocate any required DDs through\nthe TSO ALLOC command or through Option 3: Allocate off of the Primary Option Menu.\nIf you are testing an IMS or DL/I program, also review the instructions given in the section Testing IMS Applications.\n6.Fill in the name of the program that you wish to debug in the Monitored Programs section of the Monitor Control panel.\nThe name of the program is the PROTSYM member name for the program to be tested. Also fill in the data set name\nof the Symbolic file, the PROTSYM that was used when the program was compiled and post-processed. When all the\ninformation has been filled in, press Enter.\nIf any of the programs specified on the Monitor Control panel are Visual Age PL/I for OS/390 programs and you\nentered a Y in the Monitor PL/I field, the PL/I PROTSYM/Load Module Map panel displays. Fill in the load module", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "10c49daf4814-2", "text": "names for any PL/I programs that you want to debug.\nIf you are using Endevor  to manage your load module and listing libraries, you can activate the dynamic symbolic\nsupport feature (DSS) by designating a PROTSYM file as the receiver for DSS post processor-created symbolic files.\nThis reduces your pre-testing setup time and ensures you will always debug with the correct symbolic file associated\nwith the load module being monitored.\nThe execution of the application begins.\n7.If no errors are encountered, the Initial Intercept panel displays. This is a display of the source statements beginning\nwith the first executable statement. The title line should read *INITIAL* Intercept.\n8.The program is ready to execute the application. Enter the GO command in the Command field and press Enter, or\npress the PF key set to GO.\nThe program executes until one of the following conditions is encountered:\n 732", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "da8120252751-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2013An abend occurs: The Intercept panel is displayed, highlighting the statement where the abend was detected.\n\u2013The program runs to normal completion. The Execution Control panel displays with the return code in the upper\nright corner indicating that the run has completed.\nExecute a Program Until an Error Occurs\nWhen an abend occurs, use application commands to correct the bad data and continue the test.\nFor example, consider the following COBOL statements:\n 041600    MOVE +20       TO VARIABLE-LENGTH-1.\n 041700    MOVE FIELD1    TO SALARY-TO-DATE.\n 041800    MOVE +30       TO VARIABLE-LENGTH-3.\n \nIf FIELD1 contains invalid numeric data such as spaces, an S0C7 occurs when an attempt is made to execute statement\n041700. When the S0C7 occurs, the Intercept panel displays: the abend reason code appears on the title line and\nstatement 041700 is highlighted.\nTo check the contents of FIELD1, use the DISPLAY command to format and display WORKING STORAGE. To change\nthe contents of FIELD1, move the cursor under the data displayed at the right of the data item, and key in the new value\nfor the data item.\nPress the END key to return to the Intercept panel. Then issue the GO command to resume the test session.\nStop a Looping Program\nPress the Attention key or PA1 key to stop a looping program. This causes the debugger to stop execution at the next\nexecuted statement. The Attention key works for terminals that are attached to the system through an SNA controller. The\nPA1 key works for terminals attached to the system using other means. To have the PA1 key work on most terminals, you\nmust first press the RESET key.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "da8120252751-1", "text": "must first press the RESET key.\nIf you cannot locate the Attention or RESET and PA1 keys, ask your technical support person for assistance.\nNOTE\nIf you are attempting to break from a looping program and the PA1 key does not work, press RESET and then\nthe PA1 key.\nTrace a Program in Reverse\nA program can be stepped backward from the point of an abend to determine the cause of the abend condition.\nUse the PREV command to trace the program's execution in reverse. The PREV command does not affect the contents of\nthe application's variables. It also does not change the location where the GO command will resume execution.\nTo view the statement that has been executed, enter P or PREV in the Command field of the Intercept panel and press\nEnter.\nStop a Program at a Particular Statement\nStop a program at selected statements by setting unconditional breakpoints at those statements. From the Intercept\npanel, locate the statement where the program will be stopped, then use the U line command or the UNCOND command\nto set a \"before\" unconditional breakpoint that stops before  the statement is executed. You can also use the ) line\ncommand or UNCOND command to set an \"after\" unconditional breakpoint that stops after the statement is executed. To\naccess the Intercept panel, review the Preparation for Test Execution section.\nFor example, consider the following COBOL statements:\n 041400  0000-INITIALIZATION SECTION.\n 733", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "62ca968e3c73-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 041500\n 041600       MOVE +20 TO VARIABLE-LENGTH-1.\n 041700       MOVE +25 TO VARIABLE-LENGTH-2.\n  \n 041800       MOVE +30 TO VARIABLE-LENGTH-3.\n \nThe program is stopped at the first line of this code so that you can examine the value of the VARIABLE-LENGTH\nvariables used in the next three lines.\nSet the breakpoint by typing a U or a ) in the left margin where the breakpoint will be set. In this example, type a U at\nstatement 41400 and press Enter. Type GO and press Enter.\nYou can also use the UNCOND command to set the breakpoint. It is especially useful if you want to automatically execute\ncommands at the breakpoint. Assume that VARIABLE-LENGTH-4 was a data-item that should have been initialized in this\nparagraph. The MOVE +45 TO VARIABLE-LENGTH-4 statement was omitted from the program source code. Add the\nstatement by setting a breakpoint and specifying the SET command on the UNCOND command.\nIn this example, set the breakpoint using either of the following UNCOND command formats:\n UNCOND 41400 (SET VARIABLE-LENGTH-4 = +45)\n     or\n UNCOND 0000-INITIALIZATION (SET VARIABLE-LENGTH-4 = +45)\n \nPress Enter  to set the breakpoint and then issue the GO command to execute the program. When the program begins\nexecution of statement 041400, the Intercept panel displays. The title line reads BREAKPOINT INTERCEPT and line\n041400 is highlighted. The Breakpoint Intercept panel displays before the statement is executed. The assignment of +45\nto VARIABLE-LENGTH-4 has been done automatically.\nStop at a Statement and Step by Verb", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "62ca968e3c73-1", "text": "to VARIABLE-LENGTH-4 has been done automatically.\nStop at a Statement and Step by Verb\nStep through a section of code by setting unconditional breakpoints at particular statements and then use the STEP and\nGO commands to execute each verb. For example, consider the following statements:\n 049400  DIVIDE CONV-YEAR BY 4\n 049500      GIVING CONV-LEAP-COUNT\n 049600      REMAINDER CONV-LEAP-REMAINDER.\n 049700  ADD +1 TO CONV-LEAP-COUNT.\n 049800  IF CONV-LEAP-REMAINDER IS EQUAL TO ZERO\n 049900      THEN\n 050000      SUBTRACT +1 FROM CONV-LEAP-COUNT.\n 050100\n 050200  IF CONV-DAY IS NOT EQUAL TO ZERO\n 050300      THEN\n 050400      SUBTRACT +1 FROM CONV-DAY.\n 050500\n 050600  COMPUTE CONV-TOD =\n 050700      (((((((CONV-YEAR * 365) + CONV-LEAP-COUNT + CONV-DAY)\n 050800      * 24) + CONV-TIME-HOUR) * 60) * CONV-TIME-MINUTE)\n 050900      * 60) + CONV-TIME-SST.\n 051000\n \n 734", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c2683286b087-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAssume that one of the IF clauses in the previous example is not functioning as expected. Step through this section of the\ncode by using the following command sequence:\nUNCOND 49400 Sets a breakpoint at statement 049400, the DIVIDE verb.\nGO or GO key Executes the program until statement 049400 is reached; then the\nIntercept panel displays. The title line reads UNCOND BEFORE\nINTERCEPT. Statement 049400 is highlighted.\nSTEP 1 Executes (or steps) one verb each time you enter the GO\ncommand.\nGO or GO key Executes one verb and redisplays the Intercept panel. This occurs\neach time you enter GO, until the step count is turned off. This\nprocess lets you monitor the flow of control through the program.\nAssume that statement 050600 has been reached and you want to execute the program until this loop is reentered without\nentering GO commands for each statement. To reset the program to normal execution, you must turn off the step count\nand enter the GO command once more:\nSTEP 0 Turns off the step count (sets it to zero).\nGO or GO key Executes the program normally until statement 049400 is reached\nagain. The Intercept panel displays, the title line reads UNCOND\nBEFORE INTERCEPT. Statement 049400 is highlighted.\nNOTE\nAs an alternative to using the STEP 1 command in conjunction with the GO command, you can use the NEXT\ncommand. This command executes up to the next verb.\nStop a Program When a Subscript Overflows\nMany S0C4 abends are caused by a subscript exceeding its expected range (overflowing). This causes unrelated data in\na program to be overlaid or garbled. The application can stop a program when a particular data item contains or exceeds", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c2683286b087-1", "text": "a value or another data item. This is done by setting a conditional breakpoint using the WHEN command.\nFor example, assume that subscript SUBS1 is exceeding its range (1 through 30). To stop the program at the statement\nwhere SUBS1 exceeds 30, enter the following command:\n WHEN SUBSCRIP SUBS1 GT 30\n \nThis command stops the program when SUBS1 is greater than 30. The character string SUBSCRIP in the command is\nthe name assigned to the WHEN condition. It is displayed in the title of the W when-name Intercept panel whenever this\ncondition is encountered; for example, the title of the Intercept panel reads:\n WHEN SUBSCRIP BEFORE INTERCEPT\n \nThe when-name identifies which WHEN condition was encountered. The when-name can also be a statement number.\nFor example, assume that SUBS1 is updated in statement 15200 and that SUBS1 exceeds its range.\nEnter the WHEN condition as follows:\n WHEN 15200 SUBS1 GT 30\n \nThis way the condition will only be checked when the specified statement number is being executed.\n 735", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ac147f29311d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTest IMS Applications\nIf you are licensed for the IMS Option, you can use the product to test and debug either batch or online IMS applications.\nTest the IMS programs with the product the same way as other programs, but remember that the IMS program is not\nthe first program that is executed when an IMS application is invoked; the IMS program is attached by the IMS Region\nController (DFSRRC00). This occurs whether the application is a DB/DC application (MPP or BMP) or a DB application\n(batch).\nYour product interfaces with the IBM BTS (Batch Terminal Simulator) program, which you use to simulate online\napplications.\nNOTE\n\u2022The Region Controller is a module, DFSRRC00. It is not the IMS control region. The IMS control region is an\nMVS address space that runs the program DFSRRC00. The application runs in an MVS address space, TSO\nthat can also run the program DFSRRC00. Neither TSO nor InterTest Batch runs in the IMS Control Region.\n\u2022The instructions in this section are for debugging an application under Foreground, Option 1 on the Primary\nOption Menu. The suggested method for testing IMS applications is using Option 5, Batch Link. For more\ninformation about batch link, see Batch Link Facility.\n\u2022A facility exists for debugging your online IMS application without the use of BTS. For more information about\ndebugging IMS DC applications, see Batch Link Facility.\nIMS Batch Program Testing\nThe JCL for executing a batch IMS program has an EXEC statement that specifies the module DFSRRC00. The\napplication program name is specified as a parameter to the DFSRRC00 module. To facilitate testing IMS batch\napplications with your product, create a CLIST to allocate IMS and InterTest Batch-related data sets. Ask your technical", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ac147f29311d-1", "text": "support person for assistance in creating the CLIST, if needed.\nThe CLIST allocations are as follows:\nIMS-related:\nDFSRESLB  IMS  IEFRDER  DFSVSAMP\nNOTE\nOn the ddname DFSRESLB, the IMS RESLIB data set is concatenated to itself. This is necessary to\nprevent a dynamic allocation to the ddname. If the IMS RESLIB data set is not concatenated to itself\nunder the ddname DFSRESLB, USER 0684 abends and other unpredictable user abends can occur.\nInterTest Batch-related:\nINT1PARM  INT1LOAD  INT1PNNL  INT1PROF  INT1MSGL INT1CLOG INT1CLIB INT1REPT\nNOTE\nFor additional information about InterTest Batch-related CLISTS, see Basic Foreground Demo Session.\nPreparation for Test Execution - Batch Programs\nReplace Step 5 in the section Preparation for Testing Execution with the following information:\n\u2022On the Execution Control panel, specify the name of the IMS RESLIB data set as the load library.\n\u2022The first program to be executed is always DFSRRC00.\n\u2022The execution parameters are the same as the parameters used in a batch execution.\nGenerally, the execution parameters are DLI,membername,psbname. If the application program module name and the\npsbname are the same, you do not need to specify the psbname parameter.\n 736", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "20b952a848c4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022The application requires a STEPLIB DD statement that identifies the load library containing the application program to\nbe executed.\n\u2022You must also ALLOCATE the data bases that are used by the IMS program that will be tested.\nThe application generates a dynamic STEPLIB DD statement from the data set names that are listed under the STEPLIB\nportion of the Execution Control panel. For more information about dynamic STEPLIB facility in Execution Control Panel,\nsee Debugging Panels.\nUse the Monitor Control panel to identify the programs that have their execution controlled by the application. Identify\nonly the programs that you want to debug with the application. Also, provide the PROTSYM files that contain the symbolic\ninformation for the programs that you would like to debug.\nExample:\nIn this example assume that you have two driver modules to debug and test: DLIPGM1 and DLIPGM2. DLIPGM1 calls\nfive subprograms: SUBPGM1, SUBPGM2, SUBPGM3, SUBPGMA, and SUBPGMB. DLIPGM2 calls SUBPGMA and\nSUBPGMB. SUBPGMA and SUBPGMB do not need to be debugged. In this run, they are executed, but not symbolically\ndebugged. Thus, their names do not need to be included on the Monitor Control panel.\n  ---------------- CA InterTest Batch MONITOR CONTROL Panel ---------------------\n  COMMAND ===>                                                              \n                                                      Monitor PL/I ==> N  \n  --------------------Monitored Programs -----------------------------\n  \n  \n  ==> DLIPGM1    ==> SUBPGM1     ==> SUBPGM2     ==> SUBPGM3 ==> DLIPGM2\n  ==>            ==>             ==>             ==>         ==>        \n  ==>            ==>             ==>             ==>         ==>        \n  ==>            ==>             ==>             ==>         ==>", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "20b952a848c4-1", "text": "==>            ==>             ==>             ==>         ==>        \n  ==>            ==>             ==>             ==>         ==>        \n  ==>            ==>             ==>             ==>         ==>        \n  \n  ----------Symbolic (PROTYSM) Files ----------------Endevor Auto Populate\n                                                        -----------------\n  ==> 'USER01.PROTSYM'                           ==> Y  |Always         | \n  ==>                                            ==>    |Auto-Populate  | \n  ==>                                            ==>    |Non-LE-Enabled |\n  ==>                                            ==>    |Assembler?     |\n  ==>                                            ==>    |==> Y (Y/N)    |\n  ==>                                            ==>    ----------------- \n  ==>                                            ==>               \n \nBatch Procedures for BMP Testing\nBMPs are batch IMS programs that run under the control of an online IMS control region. The job is executed in an IMS\nBMP region. The BMP accesses databases that are allocated to IMS. Thus, the CLIST you use to invoke the application\nwill not include allocation statements for the databases.\nIf you need assistance in creating the CLIST, ask your technical support person.\nNOTE\nIf you prematurely end your test session with an END, CANCEL, or QUIT command when testing BMPs, the\nBMP region does not know the testing session is ending. The BMP region can abend with an S13E.\nThe following screen shows you an example of an Execution Control panel for IMS BMP testing:\n 737", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0f99c231d5fd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  -------------- CA InterTest Batch EXECUTION CONTROL Panel ---------------------\n  COMMAND ===>                                                               \n  \n  ------------------------------ Allocations ------------------------------------\n  \n  ALIB Dsname   ===>                                                         \n       Member   ===>                                                         \n  \n  EXEC Job Step ===>             Proc Step ===>                              \n  \n  -------------------------- Execution Overrides --------------------------------\n  \n  PGM   ===> DFSRRC00            Initial Commands ===>                       \n  \n  PARM  ===> BMP,PAYROLL,,,,N0003,,2,,,0002,,,IMST                              \n   or Number of Linkage Parameters ===>                                       \n  \n  Task Libraries  ===> 'IMS.RESLIB'                                          \n     DSNAME       ===> 'USER01.LOAD'\n       or         ===>                                                      \n    (DDNAME)      ===>                                                      \n                  ===>                                                      \n \nFrom the Monitor Control panel, the process to test a BMP is the same as the process to test an IMS batch program.\nDefine Your Application\nAt least one BMP must be added to the IMS/VS Stage 1.\nAsk the appropriate technical staff member to add the following application definitions to your IMS/VS System:\n1.The APPLCTN MACRO must be defined with the DOPT option so that a new copy of the PSB is obtained each time\nthat the program executes.\n2.The PARMLIM must be zero. The option PGMTYPE=BATCH forces the PARMLIM to zero.\n3.Define a different BMP for each applications programmer who is testing in this manner. Each programmer should be\nassigned a unique BMP to avoid having one programmer overwriting the PSB of another.\nNote: You should only use this on an IMS/VS test system. The DOPT option can have a performance impact on a\nproduction IMS/VS system.\nTest Your Application", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0f99c231d5fd-1", "text": "production IMS/VS system.\nTest Your Application\nThe BMP defined is used to test the online application. Perform the following steps:\n1.Replace the PSB for the BMP in the dynamic PSBLIB with the application PSB using the BMP PSB name.\nFor example, the BMP PSB is ABCD1234 and the application PSB is MYAPPLTN. Thus, the PSB defining MYAPPLTN\nshould be linked into the dynamic PSB library with a name of ABCD1234.\nThe programmer can use the same BMP name for any IMS/VS online applications to be tested and debugged.\nNOTE\nThe dynamic PSBLIB data set must be concatenated after the ACBLIB data set. The PSB must reside in\na library with the same format as IMSVS.ACBLIB and be concatenated to the IMSACB DD statement. The\ndynamic PSB must not be a member of IMSVS.ACBLIB.\n2.Log on to the IMS/VS test system.\n3.Enter an IMS/VS SET command in the form:\n 738", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ed9623d4f86a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n /SET TRAN trancode\n \nwhere trancode  is the trancode of the BMP defined in the previous section. This command directs all input messages\nfrom this LTERM (logical terminal) to trancode . Normally MFS provides the trancode to IMS/VS. The trancode of the\napplication to be tested is different from the trancode  through which the application Batch gains control.\n4.Enter as many transactions as necessary. The transactions remain queued on the IMS/VS message queue until a test\nsession is initiated.\n5.Log off IMS/VS. You might have a VTAM product, which lets you do a VTAM switch without logging off IMS/VS.\n6.Log on to TSO.\n7.Begin a session with the following entries on the Execution Control panel:\na.The name of the first module to be executed is DFSRRC00\nb.The execution parameters for the first program are as follows:\nBMP,mbr,psb,in,,ostd,,stimer,,,cputime,,,imsid\nwhere:\n\u2022mbr-The name of the application program to be tested\n\u2022psb-Psbname of the BMP defined previously containing the PSB of the application program being tested\n\u2022in-The trancode of the BMP defined previously\n\u2022ostd-&opt&spie&test&dirca\n\u2022&opt - Action to be taken if the batch message region starts and no control program is active. Default is N\n(ask operator for decision).\n\u2022&spie - Turn on the SPIE option (0) or not (1)\n\u2022&test - Check (1) or not (0) the addresses in the user call list for validity\n\u2022&dirca - Required for dynamic PSBs", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ed9623d4f86a-1", "text": "\u2022&dirca - Required for dynamic PSBs\n\u2022stimer-Whether to set the timer (1) or not (0). Must be set to 1 if CPUTIME 0\n\u2022cputime-BMP task timing option. No timing (0) or maximum task time ( n) where n is from 1 to 1440 minutes\n\u2022imsid-The IMS/VS system identifier where you want the BMP to execute\n8.End the session, after testing and debugging with the application.\n9.Log off TSO.\n10.Log on to IMS/VS to the LTERM used in Step 3.\n11.Review the output messages that may have been sent to your LTERM from your application program.\n12.Enter the IMS/VS RESET command as follows:\n /RESET\n \nApplication Testing Scenario\nIf you have two programmers testing online IMS/VS applications, you could define the following MACROS:\n APPLCTN DOPT,PSB=INT01,PGMTYPE=BATCH\n TRANSACT CODE=(INT01A),PRTY=(0,0)\n APPLCTN DOPT,PSB=INT02,PGMTYPE=BATCH\n TRANSACT CODE=(INT02A),PRTY=(0,0)\n  \n (PRTY=(0,0) is the default when PGMTYPE=BATCH.)\n \nJones would like to test and debug program PAYROLL while Smith tests program MANUFACT. Jones would either do a\nPSBGEN or copy his PSB (PAYROLL) into the dynamic PSBLIB member INT01. Likewise, Smith would do the same thing\nfor his PSB (MANUFACT) but as member INT02.\nJones logs on to IMS/VS. He enters:\n 739", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a60b2cf5fda0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n /SET TRAN INT01A\n \nHe then enters his FORMAT and data to execute his transaction. He can enter as many transactions as he likes. When\nhe is done, he may either log off of IMS/VS or do a VTAM switch. He then logs on to TSO to start his test session. On the\nExecution Control panel under EXECUTION PARAMETERS he enters the following:\n PARM ==> BMP,PAYROLL,INT01,INT01A,,N00003,,2,,,0002,,,IMST\n \nWhen he has ended the application, he can log back on to IMS/VS and view any output messages that his application\ngenerated to his LTERM. Once he has viewed all of the IMS/VS output screens, he enters the following command before\nlogging off IMS/VS:\n /RESET.\n \nSmith logs on to IMS/VS. He enters the following command:\n /SET TRAN INT02A\n \nHe then enters his FORMAT and data to execute his transaction. He can enter as many transactions as he likes. When\nhe is done, he can either log off IMS/VS or do a VTAM switch. He then logs on to TSO to start his test session. On the\nExecution Control panel under EXECUTION PARAMETERS he enters the following:\n PARM==> BMP,MANUFACT,INT02,INT02,,N00003,,2,,,0002,,,IMST\n \nWhen he has ended the application, he can log back on to IMS/VS and view any output messages that his application\nsent to his LTERM. Once he has viewed all of the IMS/VS output screens, he enters the following command before\nlogging off IMS/VS:\n /RESET\n \nSince IMS/VS sees the program with a trancode other than the trancode of the program being tested, different users may", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a60b2cf5fda0-1", "text": "schedule the program into multiple IMS/VS regions.\nTest Message Switching Applications\nTesting an IMS/VS application whose input messages are placed on the message queue by another IMS/VS program\nrequires a modification to the procedure outlined in the section Testing Your Application. Remember that you use the /\nSET TRAN trancode command on your IMS/VS terminal to direct IMS to queue all transactions that are entered from your\nLTERM to the trancode specified in the SET command. Therefore, your application running as BMP transaction trancode\nis able to retrieve any messages on the queue destined for your application.\nNOTE\nThe suggested method for testing IMS applications is using Option 5, Batch Link.\nUnfortunately, any messages that are inserted to the message queue destined for another program are not tagged with\nthe BMP trancode. There is a way to work around this situation, as follows:\n1.Follow steps 1 through 7 in the section Testing Your Application.\n2.Set a breakpoint before the call to insert the message on the message queue. This is usually after the CHNG call.\n3.Display the contents of the parms passed to your program using the DI or LI command.\n4.Modify the trancode on the message to be inserted to be the BMP trancode and return to the Intercept panel.\n5.Continue the testing of the application.\n 740", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c3db5f2e2049-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n6.Return to the Execution Control panel, split the screen, and select Option 6 (TSO COMMAND PROCESSOR).\n7.Copy the PSB for the program that retrieves the inserted messages into the dynamic PSBLIB data set with the BMP\nPSB member name. End the split screen mode.\n8.Change the second execution parameter, mbr, to the name of the program retrieving the inserted messages, on the\nExecution Control panel.\n9.Begin testing the application. Follow steps 8 through 12 in the section Testing Your Application.\nTest Procedure Using BTS\nLike an IMS batch application, a DB/DC application executed using BTS is not the first program executed. The module\nBTSTSOST is the first module executed. It in turn attaches the IMS region controller, DFSRRC00, which attaches the\napplication program to be executed. To facilitate testing of IMS applications with both InterTest Batch and BTS, create\na CLIST to allocate IMS, BTS, and InterTest Batch-related data sets. If you need help in creating the CLIST, ask your\ntechnical support staff for assistance.\nThe CLIST allocations are given as follows:\nIMS-related:\n DFSRESLB  IMS  IEFRDER  DFSVSAMP\n \nBTS-related:\n BTSIN BTSOUT BTSPUNCH BTSSNAP QIOPCB QALTPCB QALTRAN TASKLIB\n \nInterTest Batch -related:\n INT1PARM  INT1LOAD  INT1PNNL  INT1PROF  INT1MSGL  INT1CLOG INT1CLIB INT1REPT\n \nNOTE\nFor additional information about InterTest Batch-related CLISTs, see Basic Foreground Demo Session.\nPreparation for Test Execution - BTS\nReplace Step 5  in the section Preparation for Test Execution with the following step:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c3db5f2e2049-1", "text": "Replace Step 5  in the section Preparation for Test Execution with the following step:\n\u2022On the Execution Control panel, specify the name of the load library containing the BTS load modules. The first\nprogram to be executed is BTSTSOST.\nThe execution parameters are the same parameters that are specified to BTS. Generally, the parameter that is\nspecified is DLI,,, . If you specify the program member name, the psbname, or both, as you would to test a batch IMS\nprogram, a USER 0642 abend can occur (parm exceeds maximum length). The programs and the PSBnames to be\ntested are identified on ./T cards in the BTSIN data set.\nNOTE\nThe dynamic STEPLIB function is performed by the BTS Tasklib option. Do not specify a TASKLIB ddname on\nthe Execution Control panel, or BTS will believe that TASKLIB ddname is not allocated and terminate. Allocate\nthe ddname TASKLIB in the CLIST to invoke the application. The load libraries containing the modules to be\ntested must be allocated to the ddname TASKLIB.\nUse the Monitor Control panel to identify the programs that have their execution controlled by the application. Identify\nonly the programs that you want to debug. Also, provide the PROTSYM files that contain the symbolic information for the\nprograms that you would like to debug.\n 741", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d1239ed1bbc7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBTS Interactions\nAfter you have entered the Execution Control panel and the Monitor Control panel, BTS begins execution by reading\nthe BTSIN data set. A BTS0007I message and images of the BTS input commands are displayed on the terminal.\nBTS requests a BTS command, a /FORMAT statement, or a /*. The /FOR modname causes BTS to display a formatted\nIMS screen for input. Once the data has been input, BTS attaches the application program. InterTest Batch gains control.\nWhen the application program calls CBLTDLI, BTS again has control until the IMS language interface module passes\ncontrol back to the calling program. As a result, the BTS displays are interleaved with the Intercept panels.\nIf the BTS session ends prematurely and there was no BTS error message displayed on the terminal, review the BTSOUT\ndata set. The BTSOUT data set often contains data that does not appear on the terminal.\nNOTE\nThe application intercepts all keyed PA1s during the BTS testing session.\nMessage Switching\nMessage switching is when an IMS application program inserts a message to the message queue that is either an output\nmessage to another IMS terminal or an input message to another transaction. If the message is an input message to\nanother transaction, then BTS schedules another program to process the input message. To set breakpoints in the IMS\nprogram that processes the message inserted into the message queue, perform the following steps:\n1.Program A inserts a message for program B. When the first executable statement in program A displays on the\nterminal, enter QUALIFY B  on the command line. The beginning of the listing for program B displays. Set any\nUNCOND or WHEN breakpoints that you want. Enter  QUALIFY A  on the command line to return to the program A\ndisplay.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d1239ed1bbc7-1", "text": "display.\n2.You can also accomplish this by specifying UNCOND ALL ENTRY on the command line of the Intercept panel upon\ninitial entry into the first IMS application program.\nBTS0067I MESSAGE\nIf this message should occur while testing in a BTS environment, ensure the BTSEXT parameter has been added to the\nPARMLIB member used to invoke the application.\nDisplay and Figure Verbs in a BTS Environment\nWhen using these verbs in a BTS message switching environment, ensure the BTSSYSO parameter has been added to\nthe PARMLIB member used to invoke the application. For more information, see Applications Using Message Switching\nand DISPLAY or Figure Verbs in InterTest Batch Options. Without this option, abends 0C4 and/or 0C1 can occur.\nTest COBOL Programs Which Run Under an ADF Shell\nUse this product to test COBOL programs that run under an ADF shell. The recommended procedure for doing this is the\nsame as for testing COBOL programs under BTS. A programmer specifies BTSTSOST on the Execution Control panel\nas shown in the previous section and the names of the COBOL programs to be tested on the Monitor Control panel. Both\nof these panels are shown in the previous section Preparation for Test Execution - BTS. Specify the four-character ID of\nthe ADF SIGN-ON screen on the /FOR statement. All of the functions of the application are available while testing the\nspecified COBOL programs.\nAlthough this application does not display or intercept code that is written in the ADF Audit Language, some users use the\napplication facilities to help debug their ADF code. One way is to insert a call to a dummy COBOL program at whatever\npoint in the ADF code they want to intercept execution. Once in the Breakpoint Intercept panel, you can use the Option 2:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d1239ed1bbc7-2", "text": "CORE to display ADF work areas and tables. This requires a good knowledge of ADF. The best source for this information\nis the IBM IMS ADF II Manuals.\n 742", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "feb4b0ea7d48-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTest IBM DB2 Applications\nTo test IBM DB2 applications using your product in foreground, you can modify the TSO CLIST CAMRCDB2, which\ninvokes the application. You find CAMRCDB2 in the CAVHCLS0 data set. A sample batch  execution of DB2 programs\nfollows to give you some background into the DB2 commands DSN and RUN and how they relate to DB2 foreground\nexecution.\nNOTE\nThe instructions in this section are for debugging an application under Foreground, Option 1 on the Primary\nOption Menu. The suggested method for testing DB2 applications is using Option 5, Batch Link. For more\ninformation on batch link and about debugging your DB2 Stored Procedure, see Batch Link Facility.\nNOTE\nIf you are using the Call Attach Facility of DB2, you may use the CAMRCLST CLIST to debug your application in\nforeground.\nTo run the DB2 program DSN8BC3 under InterTest Batch\n1.Modify the TSO CLIST CAMRCDB2 by replacing INTBATCH with the data set prefix defined at install time.\n2.Verify that the application's ISPF Panel library is concatenated to the IBM ISPF panel library, ddname ISPPLIB , and\nthe message library is concatenated to the IBM ISPF message library, ddname ISPMLIB.\nNOTE\nFor more information, see CAMRCDB2 in Customize CLISTs in InterTest Batch Options.\nTo test a DB2 program (PAYROLL in this example), perform the following steps:\n1.EXEC the modified application CLIST.\nThe DB2 panel displays.\n2.Complete the three fields on the InterTest Batch DB2 panel. Each field is defined in the following table:\nField Description\nDB2 Subsystem Name ===> The name of the DB2 Subsystem where the program being tested", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "feb4b0ea7d48-1", "text": "DB2 Subsystem Name ===> The name of the DB2 Subsystem where the program being tested\nruns.\nPlan Name ===> The DB2 Plan name for the program being tested.\nLibrary Name ===> The Load Library name where the program being tested resides.\n1.Press Enter after completing the panel fields. The Primary Option Menu displays.\n2.Select Option 1: Foreground. The Execution Control panel displays.\n3.Supply the main application program name and the required STEPLIB to execute the application. Press Enter to see\nthe Monitor Control panel.\n4.On the Monitor Control panel, type in the names of the programs that you want to debug and DSNs of the PROTSYM\nfiles containing the symbolic information for the programs you want to debug. Press Enter to receive the *INITIAL*\nIntercept panel.\n5.Run the test session in the usual way.\nNotice that once you invoke InterTest Batch, there is no difference in the way the application is used to test DB2\nprograms.\nNOTE\nThis procedure does not let you end the program and return to the Execution Control panel to retest the\nsame program. You must exit the application and rerun the CLIST (Step 1).\nUse the following approach when debugging in foreground with DB2 and InterTest Batch:\n1.Get InterTest Batch working for non-DB2 programs.\n2.Get the DB2 program running under native TSO.\n 743", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d2a44a73f613-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n3.Ensure that the DB2 program is correctly prepared as follows:\na.DB2 pre-processed\nb.Compiled and post processed into a PROTSYM file\nc.Linked\nd.A DB2 bind step or job is run for the recompiled program\ne.All other DB2 protocol is done\n4.Modify the application CLIST as explained previously.\nTest Data Generation\nThis product assists you in generating test data or files for testing. Consider the following COBOL program:\n000100 IDENTIFICATION DIVISION.\n000200\n000300 PROGRAM-ID.    DATAGEN.\n000400 AUTHOR.        J. DOE.\n000500 INSTALLATION.  DATACEN.\n000600 REMARKS.\n000700\n000800\n000900 ENVIRONMENT DIVISION.\n000901 INPUT-OUTPUT SECTION.\n000902 FILE-CONTROL.\n000910 COPY OUTFILE.\n001000\n001100 DATA DIVISION.\n001200\n001300 FILE SECTION.\n001400 COPY OUTREC.\n001500\n001600 PROCEDURE DIVISION.\n001700 BEGIN.\n001800     OPEN OUTPUT OUT-FILE.\n001900 0100-WRITE-IT.\n002000     WRITE OUT-RECORD.\n002010     GO TO 0100-WRITE-IT.\n002100 0100-END-IT.\n002200     CLOSE OUT-FILE.\n002300     GOBACK.GOBACK Key\nAssume that the COPY codes OUTFILE and OUTREC contain the SELECT and FD information respectively. Use the\nfollowing command to set a breakpoint at the write statement and display the record contents in COBOL format:\nUNCOND 0100-WRITE-IT (RECORDS)\nEach time statement 1900 is executed, the COBOL program stops and a formatted display of the record for OUT-FILE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d2a44a73f613-1", "text": "appears. To generate the data, type over the values that you want, press the END key to return to the Intercept panel, and\npress the GO key to write the record.\nAdding another File Definition, OPEN, and a READ before the WRITE could make this into a COBOL format record editor.\n 744", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d3f5847d5dea-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTest Under Roscoe\nIf you run this product under Roscoe , you should be aware of the following points:\n\u2022The suggested method for testing applications with Roscoe  is using Option 5, Batch Link.\n\u2022The application runs under the ETSO OR BTSO facility of Roscoe .\n\u2022A special JCL conversion facility to simplify file allocations is available for Roscoe  users and is described in JCL\nConversion for Roscoe .\n\u2022Your application PF key assignments can differ from your Roscoe  PF key assignments. Define PF keys by selecting\nthe KEYS option on the Primary Option Menu.\n\u2022The application lets you use the split-screen facility to establish a second session using the PF SPLIT key. You also\ncan use standard Roscoe  commands to initiate a second Roscoe  session.\n\u2022Use the Roscoe  SUSPEND function to suspend an InterTest Batch session and return to Roscoe . You can then\nperform other Roscoe  functions; however, you cannot call another ETSO OR BTSO application. Resume ETSO OR\nBTSO to return to your session.\n\u2022Use the PF PRINT key to print to an InterTest Batch data set, which can be allocated to the AWS or any MVS data set.\n\u2022Use the Roscoe  print facility to print to a Roscoe  data set.\nAllocations Facility for ISPF\nBefore you can begin a debugging session, you must allocate the data sets that your program will be using. The\nallocations facility for TSO/ISPF users provides a number of features that makes this set-up process easier.\nBriefly, the allocations facility lets you to do the following actions:\n\u2022Create and manage ALIB (Allocations Library) allocations members. ALIB is the internal allocations format for the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d3f5847d5dea-1", "text": "application. The ALIB is a PDS that consists of members created through the ALIB editor or JCL converter of this\napplication. You can create new allocations library members, or edit, browse, allocate and free data sets specified in\nexisting members. Once you save an ALIB, you can use its allocations in the future, saving you valuable debugging\nset-up time.\nNOTE\nThe ALIB dataset is optional and is used by the InterTest Batch foreground testing facility. For more\ninformation, see Allocate ALIBs (Optional) in InterTest Batch Options.\n\u2022Convert allocation lists from ALIB to CLIST format. Although ALIB is an efficient format that is sufficient for most\nsituations, conversion to CLIST is useful in complex allocation situations that are beyond the straightforward free-\nand-allocate capabilities of ALIB (conditional data set allocations, for example). Converting to CLIST may also be\nnecessary if your particular operating environment requires the CLIST format.\n\u2022Browse existing JCL members in PDS, Librarian , and Panvalet  libraries.\n\u2022Convert JCL to ALIB format. This feature is useful if you have existing JCL that you would like to use for your\nallocations. The system's conversion utility fully supports JCL allocation features, and converted JCL is displayed\nin Edit mode for further processing. You can also use the resulting ALIB on the Execution Control panel to allocate\nand free the required application DDs. You can convert JCL to CLIST format by first converting it to ALIB format, then\nconverting it from ALIB to CLIST (it is not necessary to save in ALIB format). Using this feature saves you the time\nneeded to key in and debug ALIB or CLIST statements from scratch.\nThe allocations facility panels conform to ISPF file name and command conventions (for example, the ISPF Locate\ncommand).\nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d3f5847d5dea-2", "text": "command).\nNOTE\nFor more information on how to use the JCL conversion facility, Roscoe  users should see JCL Conversion for\nRoscoe .\n 745", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a03da0894679-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe Allocations Main Menu\nAccess the Allocations Main Menu by selecting option 3 from the Primary Option Menu. The Allocations Main Menu the\nstarting point for accessing all of the allocations facility's features:\nThe fields on the Allocations Main Menu are as follows:\n1 ALIB Create new allocations members, edit and browse existing\nmembers, allocate/free data sets specified in members, and\nconvert ALIB members into CLIST format.\n2 JCL Browse existing JCL members in PDS, Librarian , or Panvalet\nlibraries. You can also select members for conversion from JCL\nto ALIB format. The converted JCL is displayed in Edit mode for\nfurther processing.\n3 CURRENT Display current session allocations and free, browse, or edit\nallocated data sets.\n4 OPTIONS Specify various JCL conversion options and ALIB member\nexport options, and identify procedure libraries (proclibs) used for\nexpanding JCL procedures found during JCL conversion.\nOption 1 ALIB (Allocations Library) Functions\nThe ALIB library option lets you create new allocations members, edit and browse existing members, allocate/free data\nsets specified in members, export (convert) ALIB members to CLIST format, and import (convert) JCL members to ALIB\nformat. Selecting this option displays the Allocations Library panel.\nSelect an ALIB Member from the Allocations Library Panel\nThe application displays the Allocations Library panel if you select option 1 (ALIB) from the Allocations Main Menu. Use\nthis panel to enter the name of the member you want to edit.\nFor ISPF library members: The Allocation Library panel has the following input fields:\nFor ISPF library members:\nProject, Group, Type Required. Enter the three-level qualifier for standard data set names in ISPF.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a03da0894679-1", "text": "Member Optional. If you do not know the member name, leave this field blank or enter a member\nname pattern. Valid ISPF wild card  member pattern characters are:\n% Substitutes for any one character. May be\nthe first character.\n* Substitutes for any number of characters.\nMay not be the first character.\nFor PDS members:\nData set name Optional. If your member is not in an ISPF library, enter the actual,\ncataloged name of the file. The name can be up to 44 characters\nlong, with segments up to eight characters long, separated by\nperiods. You can specify any MVS data set name and use wild\ncard substitutions, as described for the Member field.\nVolume serial Optional. This field identifies the VOLSER of the data set specified\nin the data set name field and is necessary only when a file is not\ncataloged.\n 746", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7bb3973d4fbc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo select an ALIB Member from the Allocations Library panel:\n1.Enter the ISPF library or PDS information for the member you want to edit.\n2.Press Enter.\nIf you entered a complete member name, the application displays the Allocations Edit panel. If you entered a partial\nmember name, the application displays the ALIB Member Selection List.\nSelect an ALIB Member from the ALIB Member Selection List\nIf you did not specify a complete member name on the Allocations Library panel, the application displays the ALIB\nMember Selection List panel. This panel lists all the allocations library members or those that match the pattern.\nCA InterTest Batch  ALIB: USER01.INTBATCH.ALIB --------------------------------\nCommand ===>                                                   Scroll ==> PAGE \nCmd Name       Message  VV.MM Created  Modified______  Size  Init  Mods ID \n    NEW                 01.02 14.060   14.077   12:47 00090 00090 00000 USER01\n    PGM1                01.08 92.351   14.077   12:33 00001 00001 00000 USER01\n    PGM2                01.01 14.077   14.077   14:09 00013 00013 00000 USER01 \n    PGM3                01.08 14.062   14.077   10:27 00002 00002 00000 USER01 \n    TEST1               01.01 14.077   14.077   14:10 00002 00002 00000 USER01", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7bb3973d4fbc-1", "text": "TEST2               01.02 14.078   14.078   10:11 00001 00021 00000 USER01 \nEnter the following line commands in the Cmd field before each member in the list:\nAL To allocate all the data sets in the ALIB member.\nB To browse the ALIB members. The Allocation List Browse panel\ndisplays. From this panel you may view the allocation list in an\nALIB. You can scroll through the members and use the ISPF\nLocate (L) command to locate specific members. The Allocation\nList Browse panel is identical in format to the Allocations Edit\npanel, but no edits may be made.\nC To display the Convert to CLIST panel, which lets you convert the\nselected ALIB member to CLIST format. For more information, see\nConvert ALIB to CLIST (Export ALIB).\nE/S To edit the ALIB member. Issuing this command displays the\nAllocations Edit panel. For more information, see Edit ALIB\nAllocations.\nF To free all the ddnames in the ALIB member.\nEdit ALIB Allocations\nDisplay the Allocations Edit panel in any one of the following ways:\n\u2022From the Allocations Library panel by specifying a particular member\n\u2022From the ALIB Member Selection List panel by entering the line commands E or S next to a member\n\u2022From the JCL Allocations Step Selection List panel by selecting converted JCL steps for allocation\nThe Allocations Edit panel lets you create, modify, and manipulate lists of data set allocations. A list may be saved into the\nALIB, exported (converted) into a CLIST library, allocated, or freed. JCL may be imported (converted) into ALIB format.\nA sample Allocations Edit Panel is shown next:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7bb3973d4fbc-2", "text": "A sample Allocations Edit Panel is shown next:\nCA InterTest Batch ALIB EDIT: PDS USER01.INTBATCH.ALIB(PGM1) -------------------\nCOMMAND ===>                                                    SCROLL==> PAGE\nLINE COMMANDS - I(NNN), D(NNN), R(NNN), AL(LOCATE), F(REE), S(PACE)            \n 747", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "564a63fdf1f7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPRIMARY COMMANDS - ALLOCATE, SAVE, CREATE, RESET, CANCEL, IMPORT, EXPORT,      \n REPLACE, FREE, OPTS, END.  FOR AN EXPLANATION, SEE THE USER GUIDE OR HIT HELP.\nCMD  DDNAME   DATA SET NAME                                DISP VOLSER   DCB AL\nMSG> Imported from USER01.JCL(PGM1)                                       \nMSG> USER01   //USER01R   JOB (42400000),'USER01',CLASS=A,M                      \nMSG> RUN     //RUN      EXEC PGM=MAINCOB,REGION=4M,PARM='            RUN       \nMSG> ..  MAINCOB                                                               \n.... @STEPLIB USER01.LOAD                                   SHR            N    \n.... SYSPRINT SYSOUT=X                                     NEW            N    \n.... SYSABOUT SYSOUT=X                                     NEW            N    \n.... SYSOUT   SYSOUT=X                                     NEW            N   A\n.... SYSUDUMP SYSOUT=X                                     NEW            N    \n.... CARDIN   USER01.CARDIN.FILE                            NEW            Y    \n.... CARDOUT  USER01.SYSOUT                                 SHR            N    \nCMD Enter all line commands in this area.\nDDName Data definition name. Enter a valid ddname in this field.\nData Set Name Data set name. Enter a valid data set name in this field. Data set\nnames must be fully qualified and without apostrophes. SYSOUT=\nand TERMINAL are valid entries.\nDisp The disposition of the data set. Enter the disposition of the data\nset in this field. Valid dispositions are:\nOLD\nSHR\nNEW\nDefault: SHR.\nVolser The old volume serial, if any, of the data set. You may enter\nanother volume serial on which the data set is to reside.\nDCB Yes DCB information is present", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "564a63fdf1f7-1", "text": "DCB Yes DCB information is present\nNo There is no DCB information for the data set\nAL A The ddname is allocated\nblank The ddname is not allocated\nPrimary Commands\nThe Allocations Edit Panel primary commands, which you enter on the COMMAND ===> line, are shown next.\nALLOCate Allocates all the allocations listed on the screen.\nSAVE Saves any changes made to the list of allocations in the current\nALIB member.\nCREate Writes the list of allocations to a new ALIB member. Issuing this\ncommand displays the Copy to Allocation Library panel.\nRESet Removes all non-relevant MSG lines created during JCL\nconversion or during allocation.\nCANcel Exits without saving any changes and redisplays the Member\nSelection List panel from which you entered the editor. All changes\nto the member that were not saved are discarded.\n 748", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "924c73ebb3bb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIMPort Invokes the JCL Converter to convert raw JCL into ALIB format.\nImport JCL from a PDS, Librarian , Panvalet , and current session\nallocations libraries. The application displays the JCL Import\nSpecifications panel. For more information, see Converting JCL to\nALIB (Import JCL).\nEXPort Converts the current ALIB member into CLIST format. For more\ninformation, see Convert ALIB to CLIST (Export ALIB).\nREPlace Replaces a member with the contents of the current member.\nIssuing this command displays the Copy to Allocation Library\npanel.\nEND Ends the current Edit session and displays the Member Selection\nList panel from which you entered the editor. The member is\nautomatically saved if it was modified.\nFREE Frees all ddnames in the current member.\nOPTS Lets you change conversion and allocation options. Invoking this\ncommand displays the JCL Conversion/Allocation Options panel.\nFor more information, see Option 4: JCL Conversion/Allocation\nOptions.\nLine Commands\nEnter line commands in the Cmd field next to the ddname:\nDataset Attributes Panel\nUse the Dataset Attributes panel to review and change the data set attributes including DCB information, space\ninformation, and extended (SMS) attributes. This panel displays when you select a ddname on the Allocations Edit panel.\nDataset Attributes Panel: Fields\nThe following table describes the Dataset Attributes Panel fields:\nLRECL The logical record length of the data set.\nBLKSIZE The block size of the data set.\nRECFM The record format of the data set. Valid formats are:\nF Fixed\nFB Fixed blocked\nFBA Fixed blocked with carriage control character\nV Variable\nVB Variable blocked\nU Undefined\nDefault:  the current record format of the data set.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "924c73ebb3bb-1", "text": "VB Variable blocked\nU Undefined\nDefault:  the current record format of the data set.\nDSORG The organization of the data set. Valid organizations are:\nPO Partitioned Organization (PDS)\nPS Sequential\nSPACE UNIT The space unit used by the data set for primary and secondary storage. Valid space units\nare:\nBLK Blocks\nTRK Tracks\nCYL Cylinders\nDefault:  the current space unit of the data set.\nPRIME SIZE The primary storage.\n 749", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c13ec0516e33-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSECONDARY The secondary storage.\nDIRECTORY BLOCKS The number of directory blocks.\nRELEASE Whether unused storage should be released. Valid values are:\nYes Release unused storage\nNo Do not release unused storage\nDefault:  No\nUNIT NAME The unit name.\nVOLUME SERIAL If you entered a VOLSER on the Allocations Edit panel, it is displayed here. If this field is\nblank or you want to change the VOLSER, enter the new VOLSER.\nOR ALLOCATE LIKE DDNAME OR\nDSNAMEUse this field to obtain DCB information from another data set or ddname. Enter a valid\nddname in parentheses (for example,INT1LOAD), or a fully qualified data set name.\nSTORCLAS The SMS storage class.\nDATACLAS The SMS data class.\nMGMTCLAS The SMS management class.\nDSNTYPE One of the following valid data set types:\nLIBRARY\nPDF\nPIPE\nHFS\nRECORG One of the following valid record organizations:\nKS Keyed sequential file\nES Entry-sequenced file\nRR Relative record file\nLS Linear space file\nAVGREC Allocate space by records using one of these valid specifications:\nU Unit is one record\nT Unit is one thousand records\nM Unit is one million records\nKEYOFF Identifies the offset within the record where the key resides, for keyed files only.\nKEYLEN Identifies the length of the key.\nTo change DCB information\n1.Enter the DCB information in the appropriate fields.\n2.Enter END  on the command line and press Enter, or press the End key.\nResult: The application saves the DCB information and redisplays the\nAllocations Edit panel.\nNOTE\nEnter CANCEL  to ignore the DCB information and to redisplay the Allocations Edit panel.\nCopy to Allocation Library Panel", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c13ec0516e33-1", "text": "Copy to Allocation Library Panel\nThe application displays the Copy to Allocation Library panel whenever the ALIB editor needs the name of the ALIB data\nset and member in order to write the allocations list. The application displays this panel if you issue a Replace or Create\ncommand from the Allocations Edit panel.\nTo specify the ALIB data set name\n 750", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ffcfcbf7a30e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nThe ALIB data set is optional. If your installation is not using an ALIB data set no entry is required on this panel.\nPress PF3 several times until you return to the InterTest Batch PRIMARY OPTION MENU. For more information,\nsee the section Allocate ALIBs (Optional) in InterTest Batch Options.\n1.If the data set to which you are writing is an ISPF library, complete the information for the ISPF Library fields (Project,\nGroup, Type, and Member). For more information on these fields, see Select an ALIB Member from the Allocations\nLibrary Panel.\n2.If the data set to which you are writing is not an ISPF library, complete the information for the Other partitioned data\nset fields (Data set name, Volume serial). For more information on these fields, see Select an ALIB Member from the\nAllocations Library Panel.\n3.Enter Yes in the Replace like-named member field if you want the editor to overwrite members by the same name in\nthe library (the default is No).\n4.Press Enter.\nResult: The application creates or replaces the ALIB data set and\nredisplays the Allocations Edit panel.\nConvert ALIB to CLIST (Export ALIB)\nAccess the Convert to CLIST Options panel in one of these ways:\n\u2022From the ALIB Member Selection List panel by entering the line command C (Convert to CLIST) next to the member to\nconvert.\n\u2022From the Allocations Edit panel by entering the primary command EXP (Export) on the command line.\nIf your allocation situation is too complex for the limitations of the ALIB format (for instance, if you need conditional\nallocations or need to use other TSO commands beyond simple free-and-allocate statements), you may find it useful to\ntranslate your ALIB statements to CLIST.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ffcfcbf7a30e-1", "text": "translate your ALIB statements to CLIST.\nThe ISPF library and Other partitioned data set fields, in which you specify your destination ( TO) data set, are the same as\nthose on the Allocations Library panel.\nThe other fields are as follows:\nReplace ? Determines if the target CLIST library is to be replaced.\nYes Replace the target CLIST library\nNo Do not overwrite the existing CLIST library.\nAfter you press Enter, the cursor is placed\nin the Data Set Name field and you can\nspecify a new name\nEdit CLIST ? Determines if the ISPF editor will be invoked to edit the converted member.\nYes The ISPF editor will be invoked to edit the\nconverted member\nNo The ISPF editor will not be invoked\nTo convert from ALIB to CLIST\n1.Specify the destination (TO) data set in either the ISPF library or the Other partitioned data set fields. Modify the\nmember name, if necessary.\n2.Enter Yes or No in the Replace? and Edit CLIST? fields.\n 751", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6aca7e1c7e41-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n3.Press Enter.\nResult: The application performs the conversion.\nIf you entered Yes in the Edit CLIST field,\nthe application invokes the ISPF editor to\nallow you to further modify the CLIST. If\nyou entered No in the Edit CLIST field, the\napplication redisplays the panel from which\nthe converter was invoked.\nConvert JCL to ALIB (Import JCL)\nThe application displays the JCL Import Specifications panel when you use the Import command on the Allocations\nEdit Panel. Use this panel to enter the name and type of the JCL library member from which you want to import JCL for\nconversion.\nThe ISPF library and Other data set fields are the same as those on the Allocations Library panel. The other fields are as\nfollows.\nOption The data set format of the data set you want to import for conversion.\nBlank The member is in a PDS.\nL The member is in a Librarian  library.\nP The member is in a Panvalet  library.\nS Import the currently allocated data set list\n(current session allocations). No other fields\non this panel need to be completed if you\nchoose this option.\nLibrarian\nindex typeWhen converting Librarian  members, determines the amount of directory information\ndisplayed.\nQ Quick. Displays the member name only and\ntakes less time than the S (Short) option.\nS Short. Displays more information on the\nselected member than the Q (Quick) option.\nTo convert from JCL to ALIB\n1.Enter the data set format of the JCL member you want to import for conversion.\n2.In either the ISPF library or the other partitioned data set fields, specify the source  (FROM ) data set that contains the\nJCL you want to import for conversion.\n3.Press Enter.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6aca7e1c7e41-1", "text": "JCL you want to import for conversion.\n3.Press Enter.\nResult: If you have requested the JCL Conversion/\nAllocations Options Panel, it will be\ndisplayed next. Otherwise, the JCL member\nselection panel is displayed.\nOption 2 The JCL Library/Allocations Functions\nOption 2 (JCL) on the Allocations Main Menu panel lets you select existing JCL members for conversion to ALIB format.\nPDS, Librarian , and Panvalet  libraries are supported. Use the resulting ALIB member on the Execution Control Panel to\nallocate and free DDs.\n 752", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5c125afaeb1c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSpecify the JCL to Convert\nThe application displays the JCL Library panel when you select the JCL option from the Allocations Main Menu. Use this\npanel to specify the name and type of the JCL member you want to convert.\nComplete the following input fields:\nOption The format of the data set you want to import for conversion.\nBlank The member is in a PDS.\nL The member is in a Librarian  library.\nP The member is in a Panvalet  library.\nFor ISPF Library members:\nProject, Group, Type Required. Enter the three-level qualifier for standard data set names in ISPF\nMember Optional. If you do not know the member name, leave this field blank or enter a member\nname pattern. Valid ISPF wild card  member pattern characters are:\n% Substitutes for any one character. May be\nthe first character.\n* Substitutes for any number of characters.\nMay not be the first character\nFor PDS members:\nData set name Optional. If your member is not in an ISPF library, enter the actual, cataloged name of\nthe file. The name can be up to 44 characters long, with segments up to eight characters\nlong, separated by periods. You can specify any MVS data set name. You can use wild\ncard substitutions, as described for the Member field.\nVolume serial Optional. This field identifies the VOLSER of the data set specified in the Data set name\nfield and is necessary only when a file is not cataloged.\nLibrarian\nindex typeUsed only when converting Librarian  files. Determines the amount of directory\ninformation the application displays.\nQ Quick. Displays the member name only and\ntakes less time than the S (Short) option.\nS Short. Displays more information on the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5c125afaeb1c-1", "text": "takes less time than the S (Short) option.\nS Short. Displays more information on the\nselected member than the Q (Quick) option.\nTo specify a JCL member for conversion:\n1.Enter the ISPF library or PDS information.\n2.If you are converting a Librarian  member, enter the Librarian  index type you desire.\n3.Press Enter.\n4.The application displays the JCL Member Selection List panel.\nUse the JCL Member Selection List\nAfter specifying a partial or complete member name on the JCL Library panel, the application displays the JCL Member\nSelection List panel.\nCA InterTest Batch JCL: PDS USER01.INTBATCH.JCL---------------------------------- \nCommand ===>                                                   Scroll ==> PAGE \n    Enter  B to Browse member, S to select member for JCL conversion \n 753", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "db975b64745b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCmd Name       Message  VV.MM Created  Modified______  Size  Init  Mods ID \n    ABSDUMP             01.00 14.325   14.325   15:47 00006 00006 00000 USER01 \n    ASMHAL              01.00 14.154   14.154   11:40 00015 00015 00000 USER01 \n    TESTX               01.02 14.008   14.211   15:47 00043 00022 00027 USER01 \n    TEST2               01.03 14.188   14.062   09:13 00005 00005 00000 USER01 \n    TEST3               01.00 14.188   14.188   10:34 00007 00007 00000 USER01 \nThis panel displays the JCL members that match the member name or wild card pattern specified in the Member field on\nthe JCL Library panel. If you made no entry in the Member field, the application displays all the members of the library.\nEnter the following line commands in the Cmd field before each member in the list:\nB To browse the JCL library member. the application displays the\nJCL Browse panel.\nS To select the JCL member for conversion to ALIB format. Once\nthe JCL conversion has ended, the application displays the JCL\nAllocations Step Selection List panel. Note that if you have not set\nthe option to suppress the Conversion/Allocation Options panel,\nit is displayed before converting the JCL and displaying the JCL\nAllocations Step Selections Panel. For more information, see\nOption 4: JCL Conversion/Allocation Options.\nThe JCL Browse Panel", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "db975b64745b-1", "text": "Option 4: JCL Conversion/Allocation Options.\nThe JCL Browse Panel\nThe application displays the JCL Browse panel when you use the Browse command on the JCL Member Selection List\npanel.\nUse the JCL Browse panel to check the contents of a member selected for conversion and to determine the STEP names.\nScroll through the member to find the STEPs you want to use. Entering an END command or pressing the End key\nredisplays the JCL Member Selection List panel.\nCA InterTest Batch Browse JCL: PDS USER01.INTBATCH.JCL --------------------------\nCommand ===>                                                   Scroll ==> PAGE \nCmd __________________________________ JCLs __________________________________ \n    //USER01C  JOB (12300000,76),'RUN',CLASS=A,MSGCLASS=Z,        \n    //    NOTIFY=USER01 \n    //PROCLIB  DD  DISP=SHR,DSN=USER01.PROCLIB \n    //QDD1     EXEC  COB,N=QDD \n    //COB.SYSIN DD   DISP=SHR,DSN=USER01.QDD.COBOL \n    //QEE2     EXEC  COB,N=UXX \n    //COB.SYSIN DD   DISP=SHR,DSN=SYS2.ROSCOE56.DAILY.BKUP(-5) \nSelect Converted JCL Steps for Allocation\nThe application always displays the JCL Allocation Step Selection List panel after JCL conversion, if there were multiple\nsteps in the JCL. The panel lists all JCL EXEC cards in the member:\nCA InterTest Batch JCL: PDS USER01.INTBATCH.JCL(TEST3) ------------------------- \nCommand ===>                                                   Scroll ==> PAGE \n    Enter S beside step to select, or press END key to select all \nCmd----------------------------------- Steps ------------------------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "db975b64745b-2", "text": "Cmd----------------------------------- Steps ------------------------------ \n    DELETE    //DELETE  EXEC PGM=IEFBR14 \n    C         //C       EXEC PGM=IKFCBL00,REGION=4M, \n    LKED      //LKED      EXEC PGM=IEWL, \n    PRINTIT   //PRINTIT   EXEC PGM=IEBGENER,REGION=1024K \n    DELETE    //DELETE  EXEC PGM=IEFBR14 \n 754", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "25854877dc48-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    C         //C       EXEC PGM=IKFCBL00,REGION=4M, \n    LKED      //LKED      EXEC PGM=IEWL, \n    PRINTIT   //PRINTIT   EXEC PGM=IEBGENER,REGION=1024K \nNOTE\nIf you have not set the option to suppress the Conversion/Allocation Options panel, it displays before converting\nthe JCL and displaying the JCL Allocations Step Selections Panel. For more information, see Option4: JCL\nConversion/Allocation Options.\nTo select converted JCL steps for allocation\n1.On the JCL Allocation Step Selection List panel, enter S next to the steps whose data set allocations you want to use\nor enter the END command (or press the END key) to use all the steps. The steps you select form your allocation list.\n2.Press Enter (unless you used an END key instead of entering the END command in step 1).\n3.The application displays the Allocations Edit panel so you may edit the newly created Allocation List, saved in an\nallocation library or converted to CLIST format.\nFor more information on working with allocation libraries, see Edit ALIB Allocations.\nThe Conversion Process\nWhen you select JCL for conversion to ALIB format, the JCL converter checks the JCL for syntax. If the JCL executes\nprocedures and PROCLIBs were specified on the Conversion/Allocation Options panel, the JCL converter expands\nthe procedures found in the PROCLIBs, substitutes parameters, and performs step overrides. If the JCL executes a\nprocedure that is not found in a PROCLIB, a WARNING panel is displayed and JCLCheck message CAY6027E is\nincluded in the ALIB member, indicating the name of the procedure that was not found.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "25854877dc48-1", "text": "included in the ALIB member, indicating the name of the procedure that was not found.\nCA InterTest Batch ALIB EDIT: PDS CAI.CAVHJCL(DEMOJCL)                    ----\nCOMMAND ===>                                                    SCROLL==> PAGE\nLINE COMMANDS - I(NNN), D(NNN), R(NNN), AL(LOCATE), F(REE), S(PACE)            \nPRIMARY COMMANDS - ALLOCATE, SAVE, CREATE, RESET, CANCEL, IMPORT, EXPORT,      \n REPLACE, FREE, OPTS, END.  FOR AN EXPLANATION, SEE THE USER GUIDE OR HIT HELP.\nCMD  DDNAME   DATA SET NAME                                DISP VOLSER   DCB AL\nMSG> Imported from CAI.CAVHJCL(DEMOJCL)                    \nMSG> DEMOJCL //DEMOJCL  JOB (124400000),'INTBAT10 DEMOJCL                      \nMSG> STEP1   //STEP1    EXEC PGM=CAMRCOBB,REGION=4M                  STEP1     \nMSG> ..  .CA                                                                   \n.... @STEPLIB USER01.LOAD                                   SHR            N    \n.... SYSPRINT SYSOUT=X                                     NEW            N    \n.... SYSOUT   SYSOUT=X                                     NEW            N    \n.... REPORT   SYSOUT=X                                     NEW            N    \n******************************** BOTTOM OF DATA *******************************\nTo save the created Alib member\n1.Place the cursor on the command line and type in 'SAVE' to save the ALIB version of the JCL.\nThe Copy to Allocation Library screen opens.\n2.Fill in the library and member name where your ALIB member is to be saved and press Enter.\nThe ALIB member is saved.\nSpecial Considerations\nThere are some special conversion considerations for certain types of DD statements. The application allocates DD", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "25854877dc48-2", "text": "There are some special conversion considerations for certain types of DD statements. The application allocates DD\nstatements to a particular TSO session by using SVC 99, which performs dynamic allocation. SVC 99 does not allow the\nfollowing four DD statements to be dynamically allocated:\n 755", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c2c08249c9eb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022STEPLIB\n\u2022JOBLIB\n\u2022STEPCAT\n\u2022JOBCAT\nThe application changes STEPLIB to @STEPLIB and JOBLIB to @JOBLIB.\nJCL Keywords Supported for Conversion\nThe JCL converter supports the following JCL keywords and positional operands. The degree of converter support is\nnoted.\nJCL Keywords Description\nDSN= Fully supported.\nDISP= All operands except conditional dispositions are supported. If a DD\nwith a conditional disposition is passed, the third sub parameter is\nignored.\nDCB= The DCB keywords supported are:\nRECFM=\nBLKSIZE=\nLRECL=\nDSORG=\nHOLD= Ignored.\nSYSOUT= Fully supported. Only the CLASS parameter is used.\nUNIT= Fully supported.\nVOL= Fully supported. Only the VOLSER parameter is used.\nSUBSYS= Fully supported. Check with the vendor to make sure that a DD\ncan be allocated for this subsystem with SVC 99.\nSPACE= Fully supported.\nSTORCLAS= Fully supported.\nDATACLAS= Fully supported.\nMGMTCLAS= Fully supported.\nDSNTYPE= Fully supported.\nRECORG= Fully supported.\nAVGREC= Fully supported.\nKEYOFF= Fully supported.\nKEYLEN= Fully supported.\nLIKE= Fully supported.\nREFDD= Fully supported.\nJCL Keywords Not Supported for Conversion\nThe JCL converter does not convert all JCL keywords because many parameters in batch JCL are not supported in TSO\nCLISTs. The converter ignores backward references and keywords that it does not convert.\nAMORG= FLASH=\nBURST= FREE=\nCHARS= LABEL=\n 756", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c1fe236b9001-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCHKPT= MODIFY=\nCNTL= MSVGP=\nCOPIES= OUTLIM=\nDDNAME= OUTPUT=\nDEST= PROTECT=YES\nDLM= QNAME=\nDSID= UCS=\nFCB=\nOption 3 Current Allocations\nThe application displays the Current Allocations panel when you select option 3 (CURRENT) from the Allocations Main\nMenu panel. The current allocations option displays current session allocations and lets you free, browse, or edit allocated\ndata sets.\nThe Current Allocations panel lists currently allocated data sets, which may have been previously allocated in TSO Logon\nProcedures (such as STEPLIB), by a CLIST, or by the Allocation Facility. A sample Current Allocations List panel follows:\n----------------- CA InterTest Batch Current Allocations List ------------------\nCommand ===>                                                   Scroll ==> PAGE \n   Line commands: F - Free, B - Browse, E -Edit. \nCm DDName   Disp   Dataset Name                                         Volser \n   ISP10155 SHR    USER01.INTBATCH.ISPMLIB                               OSI011 \n   ISPPROF  SHR    USER01.ISPF.ISPPROF                                   CAI801 \n   SYSPRINT        TERM \n   SYSTERM         TERM \n   SYSOUT          TERM \n   SYSUDUMP        JES \n   SYSIN           TERM \n   SYS00001 SHR    SYS1.BRODCAST                                        MVSLIB \n   ISPALIB  SHR    ISP.ISPALIB                                          MVXAD1 \n   ISRCFIL  SHR    ISR.ISPFLMF.CFIL                                     MVS003 \n   SYSHELP  SHR    SYS2.HELP                                            MVSLIB \n            SHR    SYS1.HELP                                            MVXAD1", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c1fe236b9001-1", "text": "SHR    SYS1.HELP                                            MVXAD1 \n            SHR    USER.HELP                                            CAI800 \n   ISPTABL  SHR    USER01.ISPF.ISPPROF                                  CAI801 \n   ICQTABL  SHR    ICQ.ICQTLIB                                          MVXAD1 \n   SYSPROC  SHR    SYS2.CLIST                                           MVSLIB \n            SHR    ICQ.ICQCCLIB                                         MVXAD1 \n            SHR    ICQ.ICQACLIB                                         MVXAD1 \n            SHR    ISR.ISRCLIB                                          MVXAD1 \n            SHR    SYS1.RMFCLS                                          MVXAD1 \nYou may scroll through the list and enter the following line commands next to any data set in the list:\nF/S Free the data set/ddname.\nB Browse the data set. This is an ISPF function and operates only if\nit is supported by your ISPF installation.\nE Edit the data set. This is an ISPF function, and operates only if it is\nsupported by your ISPF installation.\n 757", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "49462e9d44ad-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nOption 4 JCL Conversion/Allocation Options\nThe application displays the JCL Conversion/Allocation Options panel when you select option 4 (OPTIONS) from the\nAllocations Main Menu panel.\nUse the Options option to specify JCL conversion and ALIB member export options and Proclibs (procedure libraries)\nused for expanding JCL procedures found during JCL conversion.\nThe Current Allocations/Options fields are described next:\nProclib 1 -7 The procedure library names you want to use for expanding procedures found in\nJCL during conversion. When your JCL job stream executes procedures, assign the\nprocedures a Proclib to be used during the conversion process. Enter up to seven\nprocedure library names. If you require more than seven Proclibs, use a pre-allocated\nddname instead.\nPre-allocated DD If you require more than seven Proclibs, or if your Proclibs are pre-allocated by other\nmeans (for example, in the TSO logon procedures or custom CLISTs), enter the name of\na pre-allocated ddname here.\nEasyProclib For EasyProclib users, this field specifies whether the JCL conversion facility uses\nprivate JCL procedure libraries identified by the //PROCLIB ddname in the job stream.\nYes The JCL conversion facility uses private\nJCL procedures using the //PROCLIB\nddname in the job stream.\nNo The JCL conversion facility will  not use\nprivate JCL procedures using the //\nPROCLIB ddname in the job stream.\nDefault: No\nCLIST 'Control' Whatever you enter here appears in the CLIST control statement when you convert\nfrom ALIB to CLIST (for example, NOMSG and NOLIST). For more information on valid", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "49462e9d44ad-1", "text": "CLIST control statements, see the IBM publication TSO Command Language Reference\nManual .\nDCB info on\n(Attr, Alloc)Determines whether DCB information appears on the attribute statement or the allocate\nstatement in your CLIST when you convert from ALIB to CLIST. The choice is mainly\ndictated by user-preference.\nALLOC Put DCB information on the generated\nALLOC statement.\nATTR Generate DCB information on a separate\nATTRIB statement.\nDefault: Attr\nIf allocated (Reuse, Free) Controls the allocation process during CLIST conversion. If the data set is already\nallocated:\nR The application tries to reuse the allocation.\nThe REUSE statement is generated on the\nallocations card.\nF The application frees the data set before\nallocation. The FREE statement is\ngenerated on the allocations card.\nDefault: Free\nIf exists (Delete, Use  - for new data sets\nonly)Used for allocating a new, non-temporary data set. Generates a DELETE statement in\nthe CLIST to prevent a Duplicate Data Set Name  error.\n 758", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a5e9edae9d21-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDELETE Generates a DELETE statement in the\nCLIST. This deletes any existing data set\nallocated with the same name.\nUSE A Duplicate Data Set Name  error is\ngenerated if there is an existing data set\nallocated with the same name.\nDefault: USE\nSuppress (Yes or No) Indicates whether or not this panel should be suppressed when converting JCL. Once\nthis option is set to Yes, this panel only displays when choosing option 4 from the\nAllocations Main Menu.\nJCL Conversion for Roscoe\nThis section describes how to use the JCL Conversion facility for Roscoe .\nThe JCL Conversion facility lets you convert JCL to Roscoe  RPF format so that Roscoe  can execute it. Use this facility to\nconvert the JCL that performs the allocations required by programs you are testing in foreground with your product.\nAccess the JCL Conversion Facility\nTo enter the JCL Conversion facility, enter the following command on the command line:\n[xxx.]IBCONV\nwhere xxx is the prefix of the library in which the product is installed. Omit this prefix if the application is installed in a\ncommon execution library.\nThe application displays the JCL Converter panel.\nSpecify the JCL Member for Conversion\nThe JCL Converter panel lets you specify the JCL member for conversion:\n----------------------- CA InterTest Batch JCL Converter ----------------------\n Option ===> \n Select an Option and press ENTER \n             A - AWS.... \n             L - LIB.... \n             D - DSN.... USER01.LIB.CNTL(TEST*) \n             J - JOB...: \n \n             X    -  Exit \n \n \n JCL Conversion PROCLIBs: \n             Proclib1... USER01.PROCLIB \n             Proclib2... SYS2.PROCLIB", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a5e9edae9d21-1", "text": "Proclib2... SYS2.PROCLIB \n             Proclib3... \n             Proclib4... \n             Proclib5... \n             Proclib6... \n             Proclib7...\n 759", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "563119fab2f2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIdentify Where the JCL Member Is Stored\nJCL members are stored in one of the following areas:\nAWS Roscoe  active working storage\nLIB Roscoe  user library\nDSN Data set (PDS, sequential or Librarian )\nJOB The currently attached job. You cannot change this jobname.\nThe information specified in these fields reflects your profile. If you change this information, for example if you change\nthe DSN, application updates your profile, which is stored in your library in member ZZIBOPTS. Follow standard Roscoe\nconventions for specifying the AWS, Library or DSN.\nIdentify the PROCLIBs\nIn addition to specifying where the JCL member is stored, you must specify at least one PROCLIB. Each PROCLIB\nidentifies a library where JCL procedures are stored. Even if the JCL member does not use a procedure, one PROCLIB\nmust be specified on the JCL Conversion panel.\nDisplay the JCL Member\nFollow these steps:\n1.Enter a letter (A,L,D,J) in the Option field to indicate where the JCL member is stored.\n2.Complete the information for the option you selected:\n\u2013For A (AWS), enter the AWS name or leave this field blank.\n\u2013For L (library) or D (DSN), enter the library or DSN name or a partial name using the generic characters + or *, or\nleave this field blank.\n\u2013For J (job), the name of the currently attached job already appears on the JCL Conversion panel and cannot be\nchanged.\n3.Enter at least one PROCLIB name in the PROCLIB list.\n4.Press Enter.\nIf you entered a complete AWS, library or DSN name, Roscoe  displays the JCL member you selected. If you entered", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "563119fab2f2-1", "text": "a partial name or left the name blank, Roscoe  prompts you for additional information. See Selecting the JCL Member\nfrom a List, which follows, for instructions on specifying that information. If you selected J (job), Roscoe  displays file 2\n(the JCL file) of the currently attached job.\nSelect the JCL Member from a List\nIf you do not specify a complete AWS, library or DSN name on the JCL Converter panel, Roscoe  prompts you for\nadditional information.\nFor AWS, Roscoe  displays a list of members. Enter a to the left of the desired AWS and press Enter to attach and display\nthe member.\nFor a library :\n\u2022If you left the library field blank on the JCL Converter panel, Roscoe  displays the Library Facility panel. Specify the\nlibrary information and, optionally, the member name, and attach the library.\n\u2013If you specify the member name, Roscoe  displays the member.\n\u2013If you omit the member name, Roscoe  displays the member list.\n\u2022If you specified a partial library name on the JCL Converter panel, Roscoe  displays a list of members that meet the\ncriteria.\n 760", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3b0a1272c4b1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWhen Roscoe  displays the member list, enter a to the left of the library JCL member and press Enter to attach and display\na member.\nFor a DSN :\n\u2022If you left the DSN field blank on the JCL Converter panel, Roscoe  displays the Data Set Facility panel. Specify the\ndata set information and attach the data set to display a list of members.\n\u2022If you specified a partial data set name on the JCL Converter panel, Roscoe  displays a list of members that meet the\ncriteria.\nWhen Roscoe  displays the member list, enter a to the left of the data set JCL member and press Enter to attach and\ndisplay a member.\nConvert the JCL Member\nWhen the application displays the JCL member you specified on the JCL Converter panel or selected from a list, you can\nreview the member to make sure it is the one you want to convert.\nFollow these steps:\n1.Enter GO on the command line.\n2.Press Enter.\nThe application converts the JCL member to Roscoe  RPF format and displays the following message:\nRPF generated in AWS xxxx\nWhere xxxx is the current AWS.\nAfter the JCL member has been converted, enter a to attach and display the converted JCL member.\nReview and Edit the Converted JCL\nYou can review and, if desired, edit the converted JCL to delete unnecessary steps. Note the following:\n\u2022The converted JCL is divided into steps.\n\u2022:: denotes a comment that identifies a STEP in the original JCL and displays the EXEC card.\n\u2022: denotes a message generated during conversion. These messages can be ignored.\n\u2022Each step contains:\n\u2013FREE statements to deallocate previously allocated data sets.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3b0a1272c4b1-1", "text": "\u2022Each step contains:\n\u2013FREE statements to deallocate previously allocated data sets.\n\u2013DELETE statements, if necessary, to delete non-temporary data sets that need to be created and may already exist.\n\u2013ALLOC statements to allocate and, if necessary, create the data sets.\nUse standard Roscoe  editing commands to edit the converted JCL. When you finish editing the member, save it in your\nown Roscoe  library.\nExecute the Converted JCL\nAfter the JCL member has been saved in your Roscoe  library, you can execute the converted JCL member at any time\nto perform the allocations. Before executing a program that you want to test with the application, execute the appropriate\nRPF member to allocate the files required by the program.\n 761", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5fc2ea18363a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nConvert JCL to ALIB in Batch\nA utility exists, CAMRAUTL, which takes a given JCL member of a PDS and creates an ALIB member from it. Review JCL\nmember CAMRAUTL in CAVHPROC. There are three required DDs, shown in the following table:\nDDname Description\nJCL DD pointing to the JCL member to be used in creating the ALIB.\nALIB DD pointing to the ALIB PDS.\nSYSPROC DD pointing to the PROCLIB concatenation.\nJCL example:\n// JOB \n//********************************************************************\n//CRE8ALIB EXEC PGM=CAMRAUTL                                         \n//STEPLIB  DD  DISP=SHR,DSN=CAI.CAVHLOAD                     \n//SYSPROC  DD  DISP=SHR,DSN=USER.JCL                         \n//JCL      DD  DISP=SHR,DSN=USER.JCL(TESTJCL)                \n//ALIB     DD  DISP=SHR,DSN=USER.ALIB                        \n//           \nBatch Link Facility\nBatch link lets you debug applications from a terminal while they execute in batch.\nThe batch link facility offers the following advantages over standard foreground debugging:\n\u2022No foreground allocations\nExecuting an application in foreground requires that all data sets used by the application be first allocated in\nforeground. While the application provides a JCL conversion and allocations facility for this purpose, the allocation and\nde-allocation process can complicate the debugging process. Applications debugged using batch link are executing in\nbatch, so no foreground allocations are required.\n\u2022Execution of leading and trailing steps\nSometimes an application is executed as part of a multi-step job stream and one or more leading steps must be", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5fc2ea18363a-1", "text": "executed before the application can run. Batch link allows debugging of any job step executing in batch, and therefore\npermits the normal completion of leading steps prior to debugging. After debugging, any trailing steps can be\ncompleted prior to job termination.\n\u2022Use of temporary files\nBecause batch link permits the execution of leading steps, applications can use temporary files created by a prior step.\nThe job stream can then delete these files when they are no longer needed.\n\u2022Multi-step debugging\nBatch link supports the debugging of multiple steps within the same job stream. When debugging of any step\ncompletes, the job continues as usual with the execution of the following step until end of job. Each batch link user\ncontrols which steps will be debugged within a job stream before the job is submitted.\n\u2022Multi-user debugging\nAt any time during a batch link debugging session, you can suspend the session and disconnect the terminal from\nthe batch debugging session. This lets the debugging session be retrieved by another (or even the same) user\nat a later time. This facilitates the transfer of the debugging session from one user to another without terminating and\nrestarting the application.\n 762", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d7c699ca3945-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterTest Batch JCL Requirements\nBefore debugging a batch application using the batch link facility, modify the application JCL to enable the batch link\nenvironment. Do this manually as described here, or automatically using the batch link JCL conversion facility.\nChange the application JCL for each step to be debugged. These changes include the following steps:\n1.Modify the PGM= field on the // EXEC statement to execute CAMRBL01.\n2.Insert the application executable library at the end of the STEPLIB or JOBLIB concatenation if it does not exist in\nLINKLIST.\nNOTE\nIt is possible to use the dynamic symbolic support feature if you have multiple Endevor  C1DEFLTS and are\ndebugging as if you have a single C1DEFLTS.\nTo do so, insert a fully qualified data set name containing the C1DEFLTS with your site under the STEPLIB\nconcatenation ID.\n3.Insert additional DD statements for the application data sets used by the debugging engine, including INT1PARM,\nINT1PROF, INT1PNLL, and INT1MSGL.\nNOTE\nFor more information about these additional DD statements, see The Batch Link DD Statements in Batch\nLink JCL Edit Panel.\n4.Insert an INT1OPTS DD containing in-stream debugging options, such as the original program name from the PGM=\nfield on the // EXEC statement.\nNOTE\nFor more information about valid options, see Batch Link Options in Batch Link JCL Edit Panel. Different\nrequirements apply for DB2 applications.\nThe following code is a sample JCL stream for batch link:\n // JOB\n // EXEC PGM=CAMRBL01,PARM='application parms'\n //STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d7c699ca3945-1", "text": "//STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD\n //         DD DISP=SHR,DSN=USER.LOADLIB\n //         DD DISP=SHR,DSN=USER.C1DEFLTS\n //INT1PARM DD DISP=SHR,DSN=CAI.CAVHSAMP\n //INT1PROF DD DISP=SHR,DSN=CAI.PROFLIB\n //INT1PNLL DD DISP=SHR,DSN=CAI.CAVHPNL1\n //INT1MSGL DD UNIT=SYSDA,SPACE=(TRK,(1,1))\n //INT1OPTS DD *\n   EXEC=CAMRCOBB,PROFILE=USER01\n /*\n \nDebug a Batch Application\nWhen a job step that has been modified for batch link executes, the program CAMRBL01 starts the debugging engine in\nbatch. At this point the job step becomes available for debugging.\nBatch link debugging sessions can only be connected to a terminal using the Batch Link Option Menu, described later\nin this section. You choose a batch link job step for debugging from the selection list provided. Doing so connects the\nterminal to the batch job, creating a batch link debugging session.\nDebugging is exactly the same as it is for a standard foreground testing session, with the following exceptions:\n 763", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bc0d992858af-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022The application and the debugging engine both execute in batch, not in foreground. The terminal acts only as a\nwindow  for communicating with the batch link session.\n\u2022The batch link session begins with the Monitor Control panel, not an Execution Control panel.\n\u2022When the debugging session ends, the batch job continues normally with the next step, and the terminal returns to the\nBatch Link Option Menu.\nUse the Batch Link Menus\nYou can display the Batch Link menu by selecting option 5 from the Primary Option Menu:\nThe Batch Link Option menu consists of four options:\nJCL\nUse this option to convert and submit JCL for batch link. Conversion is only required once per JCL stream, unless\nyou alter your original JCL or decide to change which steps to debug. Alternatively, you can modify the JCL\nmanually.\nBatch Link\nUse this option to select a batch job for debugging. Batch link lists all jobs available for debugging. Select the job\nthat you want to debug to connect your terminal to the batch job, creating a batch link session.\nEdit JCL\nUse this option to edit and submit existing batch link JCL.\nNOTE\nThis option is only supported under ISPF.\nScheduling\nUse this option to use the DB2 SP and IMS/DC scheduling feature. This feature lets you specify which programs\nin which regions you want the application to monitor, and lets all other programs run unmonitored. This feature\nlets you use the same region for debugging and for running the normal IMS/DC and DB2SP workload.\nBatch Link JCL Conversion Panel\nOption 1 of the Batch Link Option Menu displays the Batch Link JCL Conversion panel. Use this panel to identify the\nlibrary name (and member if the library is partitioned) containing the JCL to be converted for batch link.\nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bc0d992858af-1", "text": "NOTE\nThe batch link JCL conversion utility creates a new JCL member in the output destination of your choice.\nThe Batch Link Conversion panel fields are described next:\nField Name Description\nProject The high-level qualifier for the library containing the JCL to be\nconverted.\nLibrary The middle-level qualifier for the library containing the JCL to be\nconverted.\nType The lowest-level qualifier for the library containing the JCL to be\nconverted.\nMember The name of the member to be converted when the library is\npartitioned. Leave this field blank for sequential files or to produce\na member list for a PDS.\n 764", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bbab071abdf8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nData Set Name If the JCL library name does not conform to\nPROJECT.LIBRARY.TYPE, enter the name of the library in this\nfield. Use quotes for fully qualified names. If quotes are omitted,\nyour ISPF prefix is appended as the high-level qualifier.\nVolume Serial If the JCL library is not catalogued, use this field to enter the\nVOLSER of the DASD volume on which the library resides.\nDataset Password For password-protected libraries only, enter the password in this\nfield.\nOnce you have given values to all of the necessary fields on the panel, press Enter to advance to the next panel.\nSelect a JCL Member\nIf you have not provided a member name and your JCL library is partitioned, you are prompted to select a member for\nconversion.\n ----------------- CA InterTest Batch MEMBER SELECTION -------------------------\n  COMMAND INPUT ===>                                           SCROLL ===> HALF\n       NAME\n       **************************** TOP OF DATA ********************************\n       ARMYCOMP\n       ARMYRUN\n       ARMY5STP\n       ASM1\n       COMPNGO\n       DB2COMP\n       DB2DEMO2\n       DB2DEMO3\n       DB2RUN\n     s DEMOJCL\n       IMSBUILD\n       *************************** BOTTOM OF DATA ******************************\n \nTo select a member, place an s in the prefix area next to the member name and press Enter.\nBatch Link Conversion Options Panel\nAfter you identify the JCL library, use the Batch Link Conversion Options panel to specify options for the conversion.\nThe Batch Link Conversion Options panel fields are described next:\nField Name Description\nProclib 1-7 The data set names of any procedure libraries required for\nconverting the JCL.\nPreallocated DD Identifies the ddname used to pre-allocate procedure libraries", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bbab071abdf8-1", "text": "Preallocated DD Identifies the ddname used to pre-allocate procedure libraries\nrequired for converting the JCL.\nOutput JCL Lib The name of the JCL library where the converted JCL should be\nwritten. If this field is left blank, a temporary output file is allocated.\nWhen specifying an output JCL library, use quotes for fully\nqualified data set names. If quotes are omitted, your ISPF prefix is\nappended as the high-level qualifier.\n 765", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d522662848cf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nOutput Member If a partitioned output JCL library is specified, enter the member\nname into which the converted JCL is to be written.\nUnit The unit field to be used if the converted JCL is being written to a\ntemporary file.\nIf using a temporary file for the converted JCL, VIO must not be\nused.\nProfile Library The name of the application profile library that should be used\nby the batch debugging engine, excluding the profile member\nname. Use quotes for fully qualified data set names. If quotes are\nomitted, your ISPF prefix is appended as the high-level qualifier.\nProfile Member The name of the member within the profile library that should be\nused by the batch debugging engine.\nOptions Enter additional batch link options in this field. These options are\ndiscussed in Batch Link JCL Edit Panel.\nAfter you assign values to all of the necessary fields on the panel, press Enter to advance to the next panel.\nSelect Job Steps\nIf your JCL contains multiple steps, you are prompted to select job steps.\n ----------------- CA InterTest Batch Step Selection List ----------------------\n  COMMAND INPUT ===>                                            SCROLL ===> PAGE\n       Select one or more of the following Steps:\n       **************************** TOP OF DATA ********************************\n  s    1     //STEP1    EXEC PGM=CAMRCOBB,REGION=4M\n       2     //STEP2    EXEC PGM=CAMRCOB,REGION=4M\n       *************************** BOTTOM OF DATA ******************************\n \nYou can select any or all job steps in the selection list. To select a job step, place an s in the prefix area next to the entry.\nTo select multiple job steps, place an s in the prefix area next to each entry.\nPress Enter to convert the JCL for batch link.\nConvert and Submit the JCL", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d522662848cf-1", "text": "Press Enter to convert the JCL for batch link.\nConvert and Submit the JCL\nOnce the JCL is converted, you are placed into EDIT, which lets you view or further modify the JCL prior to submitting it.\nIf you entered an output data set name, the JCL is written to that data set. If no output data set name is provided, a\ntemporary sequential file is used.\n  EDIT       SYS00222.T093343.RA000.USER01.IBJCL.H01         Columns 00001 00072\n  Command ===>                                                  Scroll ===> CSR\n  ****** ***************************** Top of Data *****************************\n  000001 //USER01A  JOB (42400000),'Demo JCL',CLASS=K,MSGCLASS=X,\n  000002 // NOTIFY=USER01\n  000003 //STEP1    EXEC PGM=CAMRBL01,REGION=4M\n  000004 //STEPLIB  DD  DISP=SHR,DSN=CAI.CAVHLOAD\n  000005 //         DD  DISP=SHR,DSN=USER01.LOADLIB\n  000006 //SYSPRINT DD  SYSOUT=*\n  000007 //SYSOUT   DD  SYSOUT=*\n  000008 //INT1OPTS DD *\n  000009   EXEC=CAMRCOBB, PROFILE=USER01\n  000010 /*\n 766", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2656ef4a88b8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  000011 //INT1PARM  DD  DISP=SHR,DSN=USER01.INTBATCH.CAVHSAMP\n  000012 //INT1LOAD  DD  DISP=SHR,DSN=USER01.INTBATCH.CAVHLOAD\n  000013 //INT1PNLL  DD  DISP=SHR,DSN=USER01.INTBATCH.CAVHPNL1\n  000014 //INT1MSGL  DD  DISP=SHR,DSN=USER01.INTBATCH.CAVHMSG0\n  000015 //INT1PROF  DD  DISP=SHR,DSN=USER01.INTBATCH.PROFLIB\n  000016 //INT1CLIB  DD  DISP=SHR,DSN=USER01.INTBATCH.CAVHSRC\n  000017 //INT1CLOG  DD  SYSOUT=*\n  000018 //INT1REPT  DD  SYSOUT=*\n  ****** **************************** Bottom of Data ***************************\n \nFor each job step selected for debugging, the following modifications are made for batch link:\n1.The PGM= field on the // EXEC statement is modified to execute CAMRBL01, the batch link driver program.\n2.The application executable library is added to the STEPLIB or JOBLIB concatenation.\n3.Additional DD statements are inserted for the application data sets used by the debugging engine, including\nINT1PARM, INT1PROF, INT1PNLL, and INT1MSGL. These additional DD statements are described in detail later.\n4.An INT1OPTS DD statement is added containing in-stream debugging options, such as the original program name\nfrom the PGM= field on the // EXEC statement.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2656ef4a88b8-1", "text": "from the PGM= field on the // EXEC statement.\n5.If you are using the dynamic symbolic support feature and you have multiple C1DEFLTS, you can concatenate to\nthe STEPLIB a fully qualified data set name containing the Endevor  site ID associated with the load module being\nmonitored. Alternatively, you can also let CAICCI discover the site id and populate the symbolic file for you.\nNOTE\nThe requirements are slightly different for DB2 applications, as described.\nWhen you are ready to submit the JCL, enter SUBMIT on the command line and press Enter. The job is submitted but you\nremain in the EDIT session. Exit the EDIT session by entering END or CANCEL on the command line and then pressing\nEnter.\nThe job begins execution and becomes available for debugging as soon as one of the selected steps begins to execute.\nJCL Conversion Limitations\nThe following JCL constructs are not currently supported by the Batch Link JCL Conversion utility:\nPartial DD overrides\nGiven the following JCL:\n //PROC1    PROC                                        \n //S1       EXEC PGM=TESTPGM                            \n //TEST1    DD   DISP=(,CATLG,DELETE),DSN=USER01.TESTDSN,\n //         UNIT=DISK,SPACE=(1,(1,1))                   \n // PEND                                                \n //MYPGM    EXEC PROC1                                  \n //S1.TEST1 DD   UNIT=SYSDA                            \n \nThe DD TEST1 will not be generated correctly in the converted JCL.\nJCL invokes a PROC that updates or adds JCL keywords to an EXEC statement.\nGiven the following JCL:\n //PROC1    PROC                       \n //S1       EXEC PGM=TESTPGM,PARM='ABC'\n //TEST1    DD   SYSOUT=*              \n 767", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a2ca4b3eaea0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n // PEND                               \n //MYPGM    EXEC PROC1,PARM='DEF'      \n \nThe PARM keyword on the EXEC card will not be updated.\nNOTE\nAny client hitting this limitation can still use the utility to do most of the conversion or you can edit the JCL and\nmake the necessary changes manually.\nWhen the application converts JCL for batch link, all the called catalogued procedures are expanded and all expanded\nsteps from the procedures are given a stepname of just  procstepname.\nWhen there are COND= parameters in the original JCL with stepname.procstepname  references, these are modified to\nuse the procstepname . As a result, the reference may no longer be unique.\nIF statements and DD statements with stepname.procstepname  references are not modified and the\nstepname.procstepname  reference is no longer valid. Therefore you must examine the converted JCL and modify these\ninstances as appropriate.\nBatch Link Selection Panel\nOption 2 of the Batch Link Option Menu displays the Batch Link Selection panel. Use this panel to select a batch job for\ndebugging.\nNOTE\nThis panel is not accessible unless the batch link facility is initialized on your system and at least one batch link\njob step is ready for debugging.\nA batch link debugging session is functionally identical to a foreground test session.\nNOTE\nFor a detailed description of the foreground test facility, see Debugging Commands.\n ----------------- CA InterTest Batch Batch Link Selection --------------------\n COMMAND INPUT ===>                                          SCROLL ===> PAGE\n            *         *         *         *         *        *         *                            \n      #     Jobname   Stepname  Program   Owner     User     Trans     SYSID                 \n      **************************** TOP OF DATA *********************************", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a2ca4b3eaea0-1", "text": "**************************** TOP OF DATA *********************************\n      1     JOB01A    STEP1     TESTPGM   USER01                       TSO01                     \n      2     JOB02A    STEP1     CAMRCOBB  USER02                       TSO02    \n      3     JOB03X    RUN       PAYROLL   USER03   LINKED BY USER03    TSO01    \n      ************************* BOTTOM OF DATA *********************************  \n \nDebugging a Job Step\nTo select a job step for debugging, type S next to the entry on the selection list, and press Enter. The Monitor Control\npanel appears and the debugging session begins.\nNOTE\nOnly one user at a time can select a batch link job step. If another user has selected a step, the entry is marked\nas 'Linked by userid '.\nSuspended Jobs\nWhen you select a batch link job step that was suspended, the debugging session resumes at the point at which the\nsession was suspended.\n 768", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a87cf894671c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo suspend a session enter the SUSPEND command after the initial debugging intercept. A session is suspended if a\nuser ID is canceled during a debugging session.\nDebugging on Foreign LPARs\nYou can debug a job that is executing within the SYSPLEX on a different LPAR than the one you are currently logged on\nto. The SYSID column displays the LPAR the job is executing on.\nAfter you select a job that is executing on a foreign LPAR, enter your user credentials to start debugging.\nNOTE\nFor more information, see Configure Batch Link and Sysplex.\nBatch Link JCL Edit Panel\nOption 3 of the Batch Link Option Menu displays the Batch Link Edit JCL panel. Use this panel to identify the library\nname (and member if the library is PDS) containing the JCL to be edited before submitting it for the batch link debugging\nsession.\nThe following table describes the Batch Link JCL Edit panel fields.\nField Name Description\nProject The high-level qualifier for the library containing the JCL to be\nedited.\nLibrary The middle-level qualifier for the library containing the JCL to be\nedited.\nType The lowest-level qualifier for the library containing the JCL to be\nedited.\nMember The name of the member to be edited when the library is\npartitioned. Leave this field blank for sequential files or to produce\na member list for a PDS.\nData Set Name If the JCL library name does not conform to\nPROJECT.LIBRARY.TYPE, enter the name of the library in this\nfield. Use quotes for fully qualified names. If quotes are omitted,\nyour ISPF prefix is appended as the high-level qualifier.\nVolume Serial If the JCL library is not catalogued, use this field to enter the\nVOLSER of the DASD volume on which the library resides.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a87cf894671c-1", "text": "VOLSER of the DASD volume on which the library resides.\nOnce you have given values to all of the necessary fields on the panel, press Enter to advance to the ISPF Edit panel.\nAfter editing, you can save your changes and submit the changed JCL for batch link execution.\nSelect a JCL Member for Editing\nIf you have not provided a member name and your JCL library is partitioned, you are prompted to select a member for\nediting.\n ----------------- CA InterTest Batch MEMBER SELECTION -------------------------\n COMMAND INPUT ===>                                           SCROLL ===> HALF\n       NAME\n       **************************** TOP OF DATA ********************************\n       ARMYCOMP\n       ARMYRUN\n       ARMY5STP\n       ASM1\n 769", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8c0f24a54b30-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n       COMPNGO\n       DB2COMP\n       DB2DEMO2\n       DB2DEMO3\n       DB2RUN\n     s DEMOJCL\n       IMSBUILD\n       *************************** BOTTOM OF DATA ******************************\n \nTo select a member, place an s in the prefix area next to the member name and press Enter.\nThe Batch Link DD Statements\nThe following table describes the additional DD statements required for batch link. You must add these DD statements to\neach job step selected for debugging:\nDDNAME Data Set Name Description\nINT1PARM CAI.CAVHSAMP Contains the parameter members used by\nthe batch debugger.\nINT1LOAD CAI.CAVHLOAD Contains the product executables.\nINT1PNLL CAI.CAVHPNL1 Contains panel skeletons.\nINT1MSGL CAI.CAVHMSG0 Contains messages.\nINT1PROF userid.PROFLIB Contains profile members used by the\ndebugger to store user preferences.\nINT1OPTS n/a Contains batch link options and control\ninformation.\n(Optional DDNAMEs)\nINT1CLIB CAI.CAVHSAMP Contains INCLUDE members.\nINT1CLOG (SYSOUT) Log output from the debugger.\nINT1REPT (SYSOUT) Report output from the HIST and XSUM\ncommands.\nBatch Link Options\nThe following table describes the batch link options that you can specify in the INT1OPTS file for job steps selected for\ndebugging.\nKeyword Description\nAUTH Specifies the USERID that is authorized to debug this application.\nBYPASS Use this option to prevent the batch link engine from stopping for\ninput at the Monitor Control panel, the Initial Intercept panel, or\nboth.\nSpecify BYPASS=MONITOR to prevent the batch link engine from", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8c0f24a54b30-1", "text": "both.\nSpecify BYPASS=MONITOR to prevent the batch link engine from\nstopping at the Monitor Control panel unless an error is detected.\nThe dynamic symbolic support feature is not supported when\nBYAPSS=MONITOR is specified in conjunction with PGM and\nPROTSYM options.\nSpecify BYPASS=INITIAL to prevent the batch link engine from\nstopping at the initial Intercept panel.\n 770", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a992e4c1f450-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDB2SP Use this option to indicate that the application you are debugging\nis a DB2 stored procedure.\nEXEC* Specifies the name of the application's main program. For most\nbatch job steps, this is the name which is replaced by CAMRBL01\nin the PGM= parameter of the // EXEC statement. For some\nspecial environments such as DB2, see Batch Link Special\nConsiderations.\nICMDS Indicates the member in your INT1CLIB DD that includes\napplication commands to be executed at the initial intercept.\nIf this command is used in conjunction with BYPASS(INITIAL),\nthese commands are not executed until a breakpoint is reached.\nIf you would like to bypass the initial intercept and would also like\na set of commands to be executed at the initial intercept, do not\nuse BYPASS(INITIAL). Instead, have GO as the last command\nexecuted at the initial intercept.\nIDLE=nn Use the IDLE command force a debugging session to time out if\nit is idle for a specified amount of time.  \"nn\" is the number of wall\nclock minutes that the debugging session will be allowed to sit\nidle before being timed out. When a time out occurs, WTOs will\nbe issued which indicate that the timer threshold was exceeded\nand the debugging session will end.  If this is not an IMSDC or\na DB2SP debugging session, the jobstep will also abend with a\nU0999 abend.\nIMSDC Use this option to indicate that the application you are debugging\nis an online IMS application.\nLOOP Specifies the interval in seconds that a batch link job step is\npermitted to execute between responses from a terminal. If this\ninterval is exceeded, the debugger cancels the batch link job step.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a992e4c1f450-1", "text": "interval is exceeded, the debugger cancels the batch link job step.\nPGM Use the PGM option to specify which programs are to be\ndebugged during the batch link session. Values specified for this\noption are used to complete the PROGRAM fields on the Monitor\nControl panel for the batch link session. You can specify only one\nprogram as a value, but the PGM option can be repeated up to\n30 times per job step. If there are no PGM values specified in\nINT1OPTS, all of the symbolic information is retrieved from the\nprofile member identified by the PROFILE option.\nHowever, if you specify PGM values in INT1OPTS, then no values\nare retrieved from the profile.\nIf specified in conjunction with BYPASS=MONITOR and\nPROTSYM option, dynamic symbolic support is not supported.\nPROFILE Specifies the name of the profile member that should be used by\nthe debugging engine. You can use a unique profile member for\neach batch link job or step if desired, or specify your own user ID\nto use your personal profile member. If not specified, the default is\nthe user ID used to submit the job.\nPROTSYM Use the PROTSYM option to specify the file that contains the\nsymbolic information for the programs you want to debug. You can\nspecify only one PROTSYM file as a value, but the PROTSYM\noption can be repeated up to seven times.\nIf the PGM option has not been specified, the PROTSYM option is\nignored.\nIf specified in conjunction with BYPASS=MONITOR and PGM\noption, dynamic symbolic support is not supported.\n 771", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "52862c002276-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nAn asterisk (*) next to a keyword indicates that the option is required on each selected step.\nSpecify options using the syntax:\n keyword=value\n \nYou can specify more than one option per line if desired, separating the options by a space or a comma.\nDB2 and IMS Schedule Menu\nOption 4 of the Batch Link Option Menu displays the DB2 and IMS Schedule Menu panel.\nDISPLAY\nDisplays a list of existing DB2 or IMS schedules. Specify DB2 or IMS in the Schedule Monitoring for field when\nyou use this option.\nNOTE\nYou can also use these lists to The Batch Link Schedule Change Panel or delete entries from the\nexisting schedule.\nADD\nAllows adding a DB2 SP or IMS/DC schedule. Specify DB2 or IMS in the Schedule Monitoring for field when you\nuse this option.\nIMPORT\nEnables importing a predefined set of schedules (DB2 SPS and IMS/DC) from an external data set.\nEXPORT\nEnables exporting all schedules (DB2 SPS and IMS/DC) to an external data set.\nSharing Schedules between LPARs in a SYSPLEX\nScheduling is not limited to the LPAR you are currently logged on to. You can:\n\u2022Add an IMS / DB2 schedule on one LPAR which is then available on all LPARs.\n\u2022Change an IMS / DB2 schedule on one LPAR, the change propagates to all LPARs.\n\u2022Delete an IMS / DB2 schedule from one LPAR which is then deleted on all LPARs.\n\u2022Trigger an IMS /DB2 schedule and select it for debugging from any LPAR.\n\u2022Use the IMPORT and EXPORT functions for all scheduled items available on the LPARs within the SYSPLEX.\nNOTE\nFor more information, see Configure Batch Link and Sysplex.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "52862c002276-1", "text": "NOTE\nFor more information, see Configure Batch Link and Sysplex.\nBatch Link Schedule Display Panel\nBased on the database type selected in the Schedule Options panel, the following active schedule entries are displayed:\n--------------- CA InterTest Batch DB2 SPS Schedule Maintenance --------------\nCOMMAND ===>                                                  SCROLL ===> CUR\n   COMMAND      : A - ADD a new entry to Schedule.\n   LINE COMMANDS: D - DELETE selected entry. C - CHANGE selected entry\n------------------------------------------------------------------------------\nCMD    REGION/JOBNAME   PROGRAM       TYPE     ONE TIME   USER       TRANSACTION   \n     **************************** TOP OF DATA *********************************\n       BIMNTH01         ASSET*        DB2      YES\n       BIMNTH01         SALES*        DB2      YES\n       WKLYPAY          TIMEATTN      DB2      YES\n 772", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c16d88627f00-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n       WKLYPAY          FCIA          DB2      YES\n       WKLYPAY          FEDW2         DB2      YES\n       WKLYPAY          STATEW2       DB2      YES\n       WKLYPAY          CASHFLOW      DB2      YES\n       QTRLY*           GL001         DB2      YES\n       QTRYL*           ASSET001      DB2      YES\n       QTRLY*           SALES001      DB2      YES\n       QTRLY*           INVNTROY      DB2      YES\n       QTRLY*           CHAININV      DB2      YES\n       QTRLY*           WHAREHSE      DB2      YES\n       QTRLY070         DSTRUTON      DB2      YES\n     *************************** BOTTOM OF DATA *******************************\nThe Batch Link IMS/DC Schedule Display panel displays IMS/DC on the first line of the panel, and IMS under the TYPE\ncolumn. The rest of the display is similar to the DB2 SPS display.\n--------------- CA InterTest\u2122 IMS/DC  Schedule Maintenance --------------\nCOMMAND ===>                                                  SCROLL ===> CUR\n   COMMAND      : A - ADD a new entry to Schedule.\n   LINE COMMANDS: D - DELETE selected entry. C - CHANGE selected entry\n------------------------------------------------------------------------------\nCMD    REGION/JOBNAME   PROGRAM   TYPE   ONE TIME   USER       TRANSACTION \n     **************************** TOP OF DATA *********************************\n       BIMNTH01         ASSET*    IMS    YES        IMSUSER1   IMSTRANS \n       BIMNTH01         SALES*    IMS    YES        USER2IMS   IMSTRX02 \n       WKLYPAY          TIMEATTN  IMS    YES        IMSU0003   IMST0003", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c16d88627f00-1", "text": "WKLYPAY          FCIA      IMS    YES        MPPUSER4   MPPTRX04\n       WKLYPAY          FEDW2     IMS    YES        USERIMS5   TESTTRAN\n       WKLYPAY          STATEW2   IMS    YES        USERMPP6   TRANSMPP\n     *************************** BOTTOM OF DATA *******************************\nBatch Link Schedule Add Panel\nSelect option 2 from the Schedule Options panel or enter A on the Schedule Display panel. The Schedule Add panel\ndisplays.\nThe Batch Link Schedule Add panel fields are described next:\nField Name Description\nREGION/JOBNAME This is usually required for IMS/DC scheduling.\nIf program name selection is independent of region, job name, or\nboth, leave this field blank, otherwise specify a maximum of eight\ncharacter IMS region name or z/OS job name that is commonly\nassociated with the program name to be monitored. Use the entire\nlength of the field, including trailing blanks as selection criteria.\nA trailing asterisk (*) denotes a generic name. Characters to the\nleft of the asterisk are used for selection. Thus ABC* matches any\nname whose first three characters start with ABC.\nAn asterisk (*) as the first character of this field denotes that any\nregion/job name is considered a match.\n 773", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "be17cbdf06e3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPROGRAM NAME This is a required field. Provide a maximum of eight-character\nvalid program name (DB2 SP name or IMS/DC name) you want\nthe application to monitor during your debugging session.\nThe entire length of the field, including trailing blanks is used as\nselection criteria.\nA trailing asterisk (*) denotes a generic name. Characters to the\nleft of the asterisk are used for selection. Thus ABC* matches any\nname whose first three characters start with ABC.\nAn asterisk (*) as the first character of this field denotes that any\nprogram name is considered a match.\nONE TIME SCHEDULE If this option is set to Y, yes, the entry is deleted from the schedule\nupon selection for monitoring.\nChange this to N, no, if you do not want the entry deleted after\nselection.\nNote that keeping the entry in the schedule means that the\nproduct always monitors the named program in a debugging\nsession when all of the selection criteria are met.\nDATABASE TYPE This field is automatically filled in based on the value you entered\nin Schedule Monitoring for ==> of the Schedule Options panel.\nUSER ID This field is used for IMS/DC only. This is the user ID assigned\nto the transaction submitted in the MPP region. If this value is\nsupplied, monitoring happens only if the specified user ID starts\nthe transaction.\nTRANSACTION This field is the IMS transaction name used for IMS/DC only. A\ntrailing asterisk (*) denotes a generic name. Characters to the left\nof the asterisk are used for selection. For example ABC* matches\nany name whose first three characters start with ABC.\nBatch Link Schedule Change Panel\nTo change displayed entries, enter C under the CMD column next to the entries you want to change:\n--------------- CA InterTest Batch DB2 SPS Schedule Maintenance --------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "be17cbdf06e3-1", "text": "--------------- CA InterTest Batch DB2 SPS Schedule Maintenance --------------\nCOMMAND ===>                                                  SCROLL ===> CUR\n   COMMAND      : A - ADD a new entry to Schedule.\n   LINE COMMANDS: D - DELETE selected entry. C - CHANGE selected entry\n------------------------------------------------------------------------------\nCMD    REGION/JOBNAME   PROGRAM       TYPE     ONE TIME   USER       TRANSACTION \n     **************************** TOP OF DATA *********************************\n       BIMNTH01         ASSET*        DB2      YES\n       BIMNTH01         SALES*        DB2      YES\nC      WKLYPAY          TIMEATTN      DB2      YES\n       WKLYPAY          FCIA          DB2      YES\n       WKLYPAY          FEDW2         DB2      YES\n       WKLYPAY          STATEW2       DB2      YES\n       WKLYPAY          CASHFLOW      DB2      YES\nC      QTRLY*           GL001         DB2      YES\nC      QTRYL*           ASSET001      DB2      YES\n       QTRLY*           SALES001      DB2      YES\n       QTRLY*           INVNTROY      DB2      YES\n       QTRLY*           CHAININV      DB2      YES\n       QTRLY*           WHAREHSE      DB2      YES\n       QTRLY070         DSTRUTON      DB2      YES\n     *************************** BOTTOM OF DATA *******************************\n 774", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d4dccb91d141-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe Schedule Change panel displays once for each selection:\n------------------ CA InterTest Batch DB2 SPS Schedule Change ----------------\n                 CHANGE any field by overtyping the displayed value.\n                 Press ENTER to accept the change, or END to cancel.\n------------------------------------------------------------------------------\n               REGION/JOBNAME     ====>  WKLYPAY\n               PROGRAM NAME       ====>  TIMEATTN\n               ONE TIME SCHEDULE  ====>  Y        (Y/N) \n               DATABASE TYPE      ====>  DB2    \n               USER ID            ====>\n               TRANSACTION        ====>        \n      PFkeys: HELP - Tutorial \n               END  - Exit    \nAfter changing the schedule and pressing Enter, the Change panel for the next marked line, if any, is displayed. This\ncontinues until all of the lines marked with C have been displayed for change.\nAfter all the changes have been done, the system refreshes the Display panel to reflect the changes.\nNOTE\nPressing the END key (PF3) only cancels the currently displayed change and any further Change panels\nqueued for display. For more information about the Change panel fields, see Batch Link Schedule Add Panel.\nBatch Link Schedule Delete Action\nTo delete an entry, enter D under the CMD column next to the entry you want to delete and press Enter:\n--------------- CA InterTest Batch DB2 SPS Schedule Maintenance --------------\nCOMMAND ===>                                                  SCROLL ===> CUR\n   COMMAND      : A - ADD a new entry to Schedule.\n   LINE COMMANDS: D - DELETE selected entry. C - CHANGE selected entry\n------------------------------------------------------------------------------\nCMD    REGION/JOBNAME   PROGRAM       TYPE     ONE TIME   USER       TRANSACTION \n     **************************** TOP OF DATA *********************************\n       BIMNTH01         ASSET*        DB2      YES", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d4dccb91d141-1", "text": "BIMNTH01         ASSET*        DB2      YES\n       BIMNTH01         SALES*        DB2      YES\nD      WKLYPAY          TIMEATTN      DB2      YES\n       WKLYPAY          FCIA          DB2      YES\n       WKLYPAY          FEDW2         DB2      YES\n       WKLYPAY          STATEW2       DB2      YES\n       WKLYPAY          CASHFLOW      DB2      YES\nD      QTRLY*           GL001         DB2      YES\nD      QTRYL*           ASSET001      DB2      YES\n       QTRLY*           SALES001      DB2      YES\n       QTRLY*           INVNTROY      DB2      YES\n       QTRLY*           CHAININV      DB2      YES\n       QTRLY*           WHAREHSE      DB2      YES\n       QTRLY070         DSTRUTON      DB2      YES\n     *************************** BOTTOM OF DATA *******************************\nThe system deletes all the marked entries and refreshes the display to reflect the deletion.\n 775", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "728d4118f151-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBatch Link Schedule Import Panel\nWhen you select option 3 from the Schedule Options panel, the Batch Link Schedule Import panel displays.\nThe Batch Link Schedule Import panel fields are described next:\nField Name Description\nProject The high-level qualifier for the data set containing the schedule to\nbe imported.\nLibrary The middle-level qualifier for the data set containing the schedule\nto be imported\nType The lowest-level qualifier for the data set containing the schedule\nto be imported.\nMember The name of the member to be imported when the data set is\npartitioned. Leave this field blank for sequential files or to produce\na member selection list for a PDS.\nData Set Name If the import data set name does not conform to\nPROJECT.LIBRARY.TYPE, enter the name of the data set in this\nfield. Use quotes for fully qualified names. If quotes are omitted,\nyour ISPF prefix is used to form the high-level qualifier.\nVolume Serial If the data set is not catalogued, use this field to enter the\nVOLSER of the DASD volume on which the data set resides.\nNote that the DCB attributes of the IMPORT data set are RECFM=FB, LRECL=80, DSORG=PS or PO.\nAlternatively you can run the schedule import function as a batch job. Use the following sample JCL to accomplish the\ntask:\n//  JOB\n/*JOBPARM SYSAFF=xxxx                                                    \n//IMPORT   EXEC PGM=CAMR40IP                                          \n//STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD          \n//INT1SKUT DD DISP=SHR,DSN=CAI.SCHEDULE.DATA(MEMBER)       \nInstead of doing a complete replacement of the schedule table, import can also perform an additive import when you code\nan execution parameter:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "728d4118f151-1", "text": "an execution parameter:\n//  JOB\n/*JOBPARM SYSAFF=xxxx                                                    \n//IMPORT   EXEC PGM=CAMR40IP,PARM='ADD'                                        \n//STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD          \n//INT1SKUT DD DISP=SHR,DSN=CAI.SCHEDULE.DATA(MEMBER)       \nEntries are added based on slot availability and using the same first available rules.\nThe following code is return code from import operations:\nRC = 0 successfully imported\nRC = 4 schedule table does not exist\nRC = 8 INT1SKUT DD statement missing.\nBatch Link Schedule Export Panel\nWhen you select option 4 from the Schedule Options panel, the Batch Link Schedule Export panel displays.\nSee the Batch Link Schedule Import panel fields for a discussion of the various similarly named fields.\n 776", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c60cf18257eb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nExport creates a new PDS member if member name provided does not exist. If one does exist, it is overwritten.\nAlternatively, you can run the schedule export function as a batch job. Use the following sample JCL to accomplish the\ntask:\n//  JOB\n/*JOBPARM SYSAFF=xxxx                                                    \n//EXPORT   EXEC PGM=CAMR40XP                                          \n//STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD          \n//INT1SKUT DD DISP=SHR,DSN=CAI.SCHEDULE.DATA(MEMBER)                   \nThe following code is return code from export operations:\nRC = 0 successfully imported\nRC = 4 schedule table does not exist\nRC = 8 INT1SKUT DD statement missing.\nBatch Link Special Considerations\n  \nThis section describes additional considerations for using batch link in special environments.\nDB2 Considerations\nUse batch link to debug DB2 applications, provided that the following JCL conversion rules are implemented:\n\u2022The main program name (IKJEFT01) is not replaced by CAMRBL01 in the PGM= parameter of the // EXEC statement.\nIf you are using the Call Attach Facility of DB2, your main program name is the application name. There are no special\nJCL conversion rules for this environment.\n\u2022SYSTSIN is modified to identify CAMRBL01 as the main program to be invoked by DB2.\n\u2022The EXEC option in INT1OPTS must identify the name of the application's main program, the name that is replaced by\nCAMRBL01 in the SYSTSIN file.\n\u2022If a LIBRARY parameter exists in the SYSTSIN file, remove it. You must add to the STEPLIB or JOBLIB concatenation", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c60cf18257eb-1", "text": "the library containing the application's main program and the library containing the batch link executables.\nConvert DB2 JCL using the Batch Link JCL Conversion dialog.\nDB2 JCL Example\nThe following example shows a DB2 job step that has been converted for batch link:\n//RUN      EXEC PGM=IKJEFT01,COND=(4,LT),DYNAMNBR=20\n//STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD\n//         DD DISP=SHR,DSN=USER01.LOADLIB\n//         DD DISP=SHR,DSN=SYS2.DB2510.MAINT.SDSNLOAD\n//SYSTSPRT DD SYSOUT=*\n//SYSOUT   DD SYSOUT=*\n//SYSTERM  DD SYSOUT=*\n//SYSPRINT DD SYSOUT=*\n//SYSIN    DD *\n/*\n//SYSTSIN   DD *\n  DSN  SYSTEM(D510)\n 777", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8af954a1b369-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  RUN PROGRAM(CAMRBL01) PLAN(DB2DEMO) \n  PARM('ABEND0C7/TRAP(OFF)')\n  END\n/*\n//INT1OPTS DD *\n  EXEC=DB2DEMO,PROFILE=USER01\n/*\n//INT1PARM  DD  DISP=SHR,DSN=CAI.CAVHSAMP\n//INT1LOAD  DD  DISP=SHR,DSN=CAI.CAVHLOAD\n//INT1PNLL  DD  DISP=SHR,DSN=CAI.CAVHPNL1\n//INT1MSGL  DD  DISP=SHR,DSN=CAI.CAVHMSG0\n//INT1PROF  DD  DISP=SHR,DSN=CAI.PROFLIB\n//INT1CLIB  DD  DISP=SHR,DSN=CAI.CAVHSRC\n//INT1CLOG  DD  SYSOUT=*\n//INT1REPT  DD  SYSOUT=*\nDebug Your DB2 Stored Procedures\nUse batch link to debug DB2 stored procedures. Confirm with your systems programmer that the necessary changes have\nbeen made to the WLM environment to support debugging DB2 stored procedures. Also, confirm that if the scheduling\nfeature is enabled, described in this section, that it is set up to debug your stored procedure. For more information on the\nrequired changes to the WLM environment, see Batch Interfaces and Compatibility. \nDB2 SP SCHEDULING CONSIDERATIONS\nSince DB2 SP currently runs under the WLM started task, the selection request for DB2 SP is made without the REGION/\nJOBNAME attribute. Thus REGION/JOBNAME Selection Phase is bypassed. You can continue to specify a REGION/", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8af954a1b369-1", "text": "JOBNAME field for DB2 SP schedule entries or you can leave that field blank.\nDebug Your Online IMS Programs\nUse batch link to debug your online IMS applications without the use of BTS. Confirm with your systems programmer\nthat the DC transaction that you want to debug has its DC region set up for batch link testing. Also, confirm that if the\nscheduling feature, described in this section, is enabled, it is set up to debug your IMS transaction.\nUse Batch Link Schedule to Enhance your DB2 SP or IMS/DC Debugging Experience\nThe batch link schedule feature helps you leverage your testing environment by letting you specify exactly which stored\nprocedures or IMS/DC transactions you want the application to monitor. All other programs run unmonitored. This lets you\nuse the same region for debugging as well as executing normal DB2 SP or IMS/DC workload.\nConfirm with your systems programmer that the product has been initialized with this feature enabled. You can also\nconfirm this by going into the product and choosing option 5, Batch Link. From there, choose option 4, Scheduling.\nFrom there, choose Option 1, supply a database type, and press Enter. If a short message of 'SCHEDULE TABLE NOT\nANCHORED' displays, this feature has not been enabled. In this case, all DB2 SPs and IMS/DC transactions will run\nunmonitored.\n 778", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6852fefa9d2d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSelect DB2 SPs or IMS/DCs for monitoring\nEntries in the schedule are organized top down and are tracked and managed by slot numbers (slot #1 through slot\n#nnnn ). Entries are added using the first available scheme. Thus when an entry in the low slot number range (for example\n#2), is deleted, the next add is added to #2, using the first available scheme:\n Slot Number   Region/Job Name   Program Name   TYPE   One Time \n1 (top) MON SP* DB2 Y\n2 MON* SP* IMS Y\n3  SP* DB2 Y\n4 MONTH* SP* DB2 N\n     \n60 (bottom)     \nSelection of an entry for monitoring is on a first-and-best  match basis and in a top down fashion (slot #1 through slot\n#60). Select an entry for monitoring only after it has passed all the Selection Phases.\n1.Enter Selection Phase - Match entries first against TYPE. Proceed to next phase if there is a match, otherwise\nexamine the next entry.\n2.REGION/JOBNAME Selection Phase - next REGION/JOBNAME of the entry having a matching TYPE is compared. If\nREGION/JOBNAME starts with an asterisk (*) or contains all blanks, any region or job name selection request would\nbe treated as a match to the REGION/JOBNAME. Trailing blanks are treated as part of the name, thus the entire\nlength (8 bytes) of REGION/JOBNAME is used for comparison (MON ). Trailing asterisk makes the name generic, thus\nthe characters and length to the left of the asterisk are used for comparison (MON).\nProceed to the next phase if there is a match, otherwise examine the next entry.\n3.Program Name Selection Phase - When the system finds a matching REGION/JOBNAME entry, it now matches its", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6852fefa9d2d-1", "text": "Program Name against the selection request. Trailing blanks are treated as part of the program name, thus the 8 byte\nProgram Name including blanks is used for comparison. A trailing asterisk makes the program name generic, thus the\ncharacters and length to the left of the asterisk are used for comparison. When the program name matches that of the\nselection request, the program is monitored.\nWe will use the table (on the previous page) to illustrate monitor selection logic and flow. Assuming we have two batch link\njobs:\n1.JOBNAME = MONDAY; PROGRAM NAME = SPECIAL1; TYPE = DB2\n2.JOBNAME = MONTH3; PROGRAM NAME = SPECIAL; TYPE = DB2\nJob 1 is ready to be monitored. Attributes in the first batch link job are used as selection criteria:\n1.Slot #1 Type Selection Phase ok. Match on TYPE DB2\n2.Slot #1 REGION/JOBNAME Selection failed. MON (with 5 trailing blanks) does not match MONTHLY.\n3.Slot #2 Type Selection Phase failed. No match on TYPE of DB2.\n4.Slot #3 Type Selection Phase ok. Match on TYPE DB2\n5.Slot #3 REGION/JOBNAME Selection ok. Match on REGION/JOBNAME (all blanks treated as a match)\n6.Slot #3 Program Name Selection Phase ok. SP of SP* matches SP of SPECIAL1.\n7.Slot #3 is deleted (ONE TIME set to Y)\n8.PROGRAM SPECIAL1 is selected for monitoring.\nJob 2 is now ready to be monitored. Attributes in the second batch link job are used as selection criteria:\n1.Slot #1 Type Selection Phase ok. Match on DB2\n2.Slot #1 REGION/JOBNAME Selection failed. MON (with 5 trailing blanks) does not match MONTHLY.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6852fefa9d2d-2", "text": "3.Slot #2 Type Selection Phase failed. No match on DB2.\n 779", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "17c51eb84526-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n4.Slot #3 deleted and is skipped.\n5.Slot #4 Type Selection Phase ok. Match on TYPE DB2.\n6.Slot #4 REGION/JOBNAME Selection Phase ok. Generic name MON of MONTH* matches MON of MONTH3\n7.Slot #4 Program Name Selection Phase ok. Generic SP of SP* matches SP of SPECIAL.\n8.Slot #4 is deleted\n9.Slot #4 is selected for monitoring.\nAssuming Job 2 is submitted before Job 1, Slot #3 is again selected for monitoring. However because its One Time\nSchedule is set to Y, Slot #3 is deleted before Job 1's selection request is made. In this case, Job 1 runs unmonitored,\nsince MONTH of MONTH* (slot #4) does not match MONDAY (Job 1's JOBNAME).\nImport and Export Schedule Files\nImporting a schedule provides you with an easy way to maintain a persistent schedule across IPLs. You can also make\nsignificant scheduling changes instead of changing individual schedules manually using the online change option.\nYou can create the schedule import file manually when you first use the scheduling feature, or you can create it later using\nthe schedule export option, since you can activate the scheduling feature with an empty schedule and later add individual\nschedules (using the online Schedule Add option) as the need arises.\nThe schedule export option is an easy way to create a backup copy of your fine-tuned schedule or a uniquely tailored\napplication system schedule to facilitate systems testing.\nSpecial Processing for DB2/IMS Schedule Export and Import\nIf a DB2/IMS schedule import file has the JOBNAME or region name specified as * (wildcard for entire name), that line is", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "17c51eb84526-1", "text": "not imported. A * in column 1 was considered as a comment on import. This solution changes the * for jobname to ? on\nexport and then on import changes the ? back to a *.\nSample Schedule Import File\nThe following example shows a sample import file and its supported record layout:\n************************************************************************\n* CA BATCH LINK SCHEDULES SAMPLE IMPORT \n* ASTERISK IN COLUMN 1 DENOTES A COMMENT LINE.                          \n* THE SYSTEM WILL VALIDATE DATABASE TYPE FIELD, AND ONE TIME SCHEDULE FI ELD.\n* VALID ONES ARE: DB2 OR IMS FOR DATABASE TYPE; Y OR N FOR ONE TIME SCHEDULE.\n* OTHER FIELDS ARE ACCEPTED ASIS, WITHOUT VALIDATION.                   \n* FORMAT OF IMPORT/EXPORT RECORD:                                       \n* COLUMN 1  - 8  REGION/JOBNAME (8 BYTES)                               \n* COLUMN 10 - 17 PROGRAM NAME   (8 BYTES)                               \n* COLUMN 19 - 19 ONE TIME SCHEDULE (1 BYTE. Y OR N)                     \n* COLUMN 21 - 23 DATA BASE TYPE (3 BYTES. DB2 OR IMS)                   \n*---+----1----+----2----+----3----+----4----+----5----+----6----+----7--\nBIMNTH01 GL001    Y DB2 \nBIMNTH01 ASSET*   Y DB2 \nBIMNTH01 SALES*   Y DB2 \nWKLYPAY  TIMEATTN Y DB2\nQTRLY080 OXLYSABN Y IMS\nQTRLY090 SAP001   Y IMS\nQTRLY100 SAP002   Y IMS\n 780", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c2590816485d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSample Schedule Export File\nThe following example shows a sample export file with a system generated record layout:\n*******************************************************************************\n* CA BATCH LINK SCHEDULES SAMPLE EXPORTED FROM SID: CA31 ON 07/14/2014 AT 09:41\n* ASTERISK IN COLUMN 1 DENOTES A COMMENT LINE.                          \n* THE SYSTEM WILL VALIDATE DATABASE TYPE FIELD, AND ONE TIME SCHEDULE FI ELD.\n* VALID ONES ARE: DB2 OR IMS FOR DATABASE TYPE; Y OR N FOR ONE TIME SCHEDULE.\n* OTHER FIELDS ARE ACCEPTED ASIS, WITHOUT VALIDATION.                   \n* FORMAT OF IMPORT/EXPORT RECORD:                                       \n* COLUMN 1  - 8  REGION/JOBNAME (8 BYTES)                               \n* COLUMN 10 - 17 PROGRAM NAME   (8 BYTES)                               \n* COLUMN 19 - 19 ONE TIME SCHEDULE (1 BYTE. Y OR N)                     \n* COLUMN 21 - 23 DATA BASE TYPE (3 BYTES. DB2 OR IMS)                   \n*---+----1----+----2----+----3----+----4----+----5----+----6----+----7--\nBIMNTH01 GL001    Y DB2 \nBIMNTH01 ASSET*   Y DB2 \nBIMNTH01 SALES*   Y DB2 \nWKLYPAY  TIMEATTN Y DB2\nQTRLY080 OXLYSABN Y IMS\nQTRLY090 SAP001   Y IMS\nQTRLY100 SAP002   Y IMS\nAn asterisk is used as a wild card character to match all or part of a name. An asterisk in the first column of a name", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c2590816485d-1", "text": "indicates that any name is matched. However, if any region/jobname will be matched, that is - the entire region/jobname\nis specified as a wildcard, then column 1 must be a ? in the import file. This will be changed to an * when imported. On an\nexport, an * in column 1 for the wildcard of an entire region/jobname will be changed to a ?. When entering the schedule\non the panel, use the * in column 1 to specify matching all region/jobnames.\nInterTest Batch Utilities\nThis section describes the functionality provided in the Utilities option. Using this option, you can display and update your\nsymbolic files (PROTSYM).\nWhen you select option U of the Primary Option Menu, the Utilities Menu displays. This menu consists of three options\n- one for listing and displaying the contents of the symbolic file, one for adding listings to a symbolic file, and one for\ndefining programs to be excluded from auto-monitoring.\nDisplay the Contents of the Symbolic File\nAfter selecting option 1 from the Utilities Menu, the PROTSYM Member Selection panel displays:\n------------- CA InterTest Batch PROTSYM Member Selection ---------------------\nCOMMAND ===>                                                 SCROLL ===> CUR \n-------------------------------------------------------------------------------\nPROTSYM Dsname  ===> 'CAI.PROTSYM'                                   \n-------------------------------------------------------------------------------\nCmd  Program   Date       Time       Size Language    Attributes              \n     **************************** TOP OF DATA ********************************\n     CAMRCOBB  12/03/2014 13:56:01     83 COBOL OS/390                        \n     CAMRCOB2  12/03/2014 13:55:47    144 COBOL OS/390                        \n     ITBMAIN   08/16/2014 08:46:02     16 COBOL II", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c2590816485d-2", "text": "ITBSUB1   08/06/2014 18:14:59     10 COBOL II           \n 781", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ebaad16a9efd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    ***************************BOTTOM OF DATA ********************************\nThis panel lists the contents of a given PROTSYM file. From this panel you can enter a valid PROTSYM file in the\nPROTSYM Dsname field. This displays the contents of this symbolic file. An example is shown in the previous screen.\nThis list displays the program name, the date and time that the program was compiled, the number of records in the\nPROTSYM that this member is using, the language that was used, and any attributes that the member has.\nUsing an S line command displays the listing for that particular program.\nAdd a Program to the PROTSYM File\nAfter selecting option 2 of the Utilities Menu, the PROTSYM Add Program Listings panel displays. Populate a PROTSYM\nfile with one or more listings using this panel.\nThe PROTSYM Add Program Listings panel contains the following fields:\nPROTSYM Dsname\nThe name of the PROTSYM data set\nListing Dsname\nThe name of the listing data set\nLibrary Type\nThe listing library data set type. Specify one of the following:\n\u2022PDS - Partitioned Data Set\n\u2022SEQ - Sequential Listing File\n\u2022PAN - Panvalet  Library\n\u2022LIB - Librarian  Library\n\u2022NDV - Endevor  Library\nFrom Member\nThe starting member name for the listing data\nTo Member\nThe ending member name for the listing data set\nView Messages\nIdentifies the message display options. Specify one of the following:\n\u2022ALL - Display all messages\n\u2022NONE - Display no messages\n\u2022RC - View a single message for each member containing the highest return code\nTo process just one member, enter the member name in the From Member field. To process a range of members, enter", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ebaad16a9efd-1", "text": "the starting member in the From Member field and the ending member in the To Member. You can also use a prefix\nending with an asterisk wildcard to process several members with a common prefix.\nYou can process a range of members using a batch utility that is described in the member IN25SYMD in the CAVHPROC\ndata set.\nExclude Programs from Auto-monitoring\nAfter selecting option 3 of the Utilities Menu, the Excluded Programs panel displays.\nUse this panel to restrict auto-monitoring of programs when wildcarding is used on the Monitor Control panel. Use a single\ntrailing asterisk to define a prefix, if desired. If a program name or wildcarded prefix has been excluded, it can only be\nmonitored by explicitly defining the full name on the Monitor Control panel. To see the list of program names that are\nalready excluded by default, type DEFAULTS on the command line.\n 782", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6ba96cb4afe1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWork With Recorded Debug Sessions\nThe Debug Session Display shows the contents of the debug session library file. Select Option 4 from the Utilities Menu to\ndisplay this panel. You can also display this panel by using the MLOG command from a debugging session.\n------------- CA-InterTest Batch Debug session Selection ----------------------\nCOMMAND ===>                                                  SCROLL ===> CUR \n                                                                               \nType B to browse session      D to delete session                              \n                                                                               \n-------------------------------------------------------------------------------\nCmd  Session  UserID   Jobname  Date    Time   Description                    \n     **************************** TOP OF DATA ********************************\n     @NAME    VUOLO01  VUOLO01  2016258 111412 MY DESCRIPTION                 \n     ASMINCL                                   Not created by MLOG            \n     ASM1     VUOLO01  VUOLO01  2016258 101424 WHY DOES LAURA MAKE ME DO THIS \n     ASSEM9   VUOLO01  VUOLO01  2016270 165101 ASSEMBLER TEST SESSION         \n     BATCH    VUOLO01  VUOLO01D 2016257 162002 BATCH DEBUG SESSION            \n     CAMRASM  VUOLO01  VUOLO01  2016258 111258 ASSEMBLER TEST                 \n     COBOL9   VUOLO01  VUOLO01  2016258 095712 TEST COBOL PROGRAM             \n     DEMOCANC VUOLO01  VUOLO01  2016292 104047 CANCEL DEMO TEST               \n     DEMOINCL                                  Not created by MLOG            \n     DEMOSTOP VUOLO01  VUOLO01  2016292 103849 STOP DEMO", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6ba96cb4afe1-1", "text": "HR       VUOLO01  VUOLO01  2016263 101008 HR NEW PROGRAM                 \n     LAURA1   VUOLO01  VUOLO01  2016263 100320 LAURA'S DEBUG SESSION          \n     MYPROG   VUOLO01  VUOLO01  2016271 083223 MY TEST PROGRAM                \n     PAYROLL  VUOLO01  VUOLO01  2016263 100728 PAYROLL DEBUGGING              \n     PLIINCL                                   Not created by MLOG            \n     *************************** BOTTOM OF DATA ******************************\n \nUse this panel to display the contents of your debug session (command library) file (INT1CLIB). This panel will display the\nsession name, userid, jobname, date and time that the debug session was created by the MLOG command, as well as a\ndescription of the session. It will also display command library files that were created outside of the MLOG command.\nThis panel displays the following information:\n\u2022Session name\n\u2022Userid, jobname\n\u2022Date and time that the debug session was created\n\u2022Description of the session\n\u2022Command library files that were created outside of the MLOG command\nThe lines marked as '*ACTIVE' are are sessions that are currently still in progress or being edited outside of Intertest\nBatch. You cannot delete these sessions from the display panel.\nYou can use the following line commands in the action field:\nB\nBrowse the command file member\nD\nDelete the command file member, if it is not active\nL\nLoad the command file member into the current debug session\n 783", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d5319b8702cb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nS\nStop the active debug session\nC\nCancel the active debug session\nNOTE\nYou can only use the L, S, and C commands from an active debugging session.\nYou can use the following primary commands at the command line:\nFind\nLocate a string on the panel. Use quotes if the text includes embedded spaces.\nRFind\nRepeat the prior Find command\nLOAD\nmember\nLoad the specified member into the current debug session\nSELECT\nmember\nDisplay the contents of the command file member\nSTOP\nmember\nStop the active debug session\nCANCEL\nmember\nCancel the active debug session\nDELETE\nmember\nDelete the saved debug session, if it is not active\nDDnames and Sample CLISTs\nDDnames Required for Proper Execution\nThis section contains a list of the ddnames that are used by the application and a brief description of their use.\nDCB information, where given, is that which is set and used by the application.\nDDname Description\nINT1LOAD Defines the partitioned data set (PDS) that contains the load\nmodules. This library is built during installation.\nINT1MSGL Defines the partitioned data set that contains the application\nmessages. This library is built during installation.\nINT1PARM Defines the partitioned data set that contains the application\nparameters. This library is built during installation.\nThe parameters are internal to the application and are\ndocumented. For information about how these parameters are\ndocumented, see Customize Options in InterTest Batch Options.\n 784", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7b38873190ea-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nINT1PNLL Defines the partitioned data set that contains the panel definitions.\nThis library is built during installation.\nINT1PROF Defines the partitioned data set used to maintain user-related\ndata from session to session. This library must be defined by\nthe installation. For information about how to allocate the profile\nlibrary, see Allocate PROFLIB in InterTest Batch Options.\nOptional DDnames\nThese ddnames are used during certain processes. If you are using the designated application facility, allocate these files\nbefore using that part of your product.\nIt is prudent to include the necessary allocation of ddnames to DSN in the CLIST that invokes the application.\nDDname Description\nINT1PRNT * Defines a sequential file that is used to print the screen images. If\nit is not allocated, the screen image feature is disabled. For more\ninformation about printing screens, see the print key description in\nProgram Function and Program Access Keys in Conventions.\nThis DD is used only under Roscoe .\nLRECL=121, BLKSIZE=6171, RECFM=FBA\nINT1REPT Defines a sequential file that is used to store the HISTogram\nand XSUM reports. If it is not allocated, the HIST and XSUM\ncommands are disabled. For more information about the reports,\nsee the HIST and XSUM Report Command descriptions in\nDebugging Commands.\nLRECL=131,BLKSIZE=6157,RECFM=FBA\nINT1ALIB Defines the partitioned data set that contains allocation sets that\nare saved under option 3, ALLOCATION. If it is not allocated, the\nsave and retrieve features are disabled. For more information\nabout allocating data sets and saving the allocations, see\nAllocations Facility for ISPF.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7b38873190ea-1", "text": "about allocating data sets and saving the allocations, see\nAllocations Facility for ISPF.\nLRECL=150, BLKSIZE=3150, RECFM=FB\nINT1CLIB Defines the partitioned data set that contains application\ncommands to be used by the INCLUDE command. If it is\nnot allocated, the INCLUDE command is disabled. For more\ninformation, see the Include Control Command in Debugging\nCommands.\nLRECL=80, RECFM=FB\nINT1CLOG Defines a sequential file that is used for the application session\nlog. If it is not allocated, logging is disabled. For more information\nabout the session log, see Session Log Facility (Review\nDebugging Session) in Debugging Commands.\nLRECL=80, BLKSIZE=6160, RECFM=FB\nSYSOUT Although SYSOUT is not used by the application, it is\nrecommended that it be allocated to the terminal to prevent\nABENDS while processing COBOL DISPLAY or EXHIBIT verbs\nthat may have been left in the program.\n 785", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1b4b63966ef4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSample CLISTs to Invoke the Application\nCAI.CAVHCLS0 contains five sample CLISTs for invoking the application in different program testing environments. The\nfollowing table describes the sample CLISTs:\nName Description\nCAMRCLST Sample CLIST for application testing.\nCAMRCIMS Sample CLIST for testing of IMS programs in foreground.\nCAMRCBTS Sample CLIST for testing of IMS programs using BTS input in\nforeground.\nCAMRCDB2 Sample CLIST for testing of DB2 programs in foreground.\nCAMRDRVR Sample CLIST that provides a front-end to the other four CLISTs.\nOther CLISTs\nThe application contains several other CLISTs for your use. They are described in the following table:\nName Description\nCAMRSTRT This gets called under an ISPF NEWAPPL and calls the program\nto start the application. CAMRKEYS can be called from this CLIST\nto set the PF Keys\nCAMRKEYS This gets called from the CLIST CAMRSTRT to set up initial PF\nkey settings for this APPL. By default, all of the PF keys are set to\nan initial value. By default, the PF keys are only set once. To have\nthe PF keys reset, modify the variable CHANGED.\nINT1ALIB This CLIST conditionally creates an ALIB data set. It can be called\nfrom your startup CLIST.\nINT1CLIB This CLIST conditionally creates a command library data set. It\ncan be called from your startup CLIST.\nINT1CLOG This CLIST conditionally creates a session log data set. It can be\ncalled from your startup CLIST.\nINT1PROF This CLIST conditionally creates an application profile data set. It\ncan be called from your startup CLIST.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1b4b63966ef4-1", "text": "can be called from your startup CLIST.\nINT1REPT This CLIST conditionally creates a user report data set. It can be\ncalled from your startup CLIST.\nBatch Abend Analysis\nSymDump  Batch provides comprehensive abend diagnostic information for batch abends in test and production\nenvironments. Its formatted reports make it easy for programmers to resolve abends without having to decipher system\ndumps. It supports all languages, with special symbolic support for COBOL, PL/I, and Assembler. It also includes detailed\ndatabase information for abending IMS, DB2, and IDMS/DB  applications. After installed, SymDump  Batch is automatically\navailable to every user.\nComponents\nThe SymDump  Batch solution consists of the following components:\n 786", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9a0e72ea0ade-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAbend Handler/Reporter\nTraps application abends and saves report data in the central VSAM repository.\nCAIPRINT Formatter\nGenerates formatted reports from the report data.\nViewing Abend Reports\nReports can be viewed using:\n\u2022CAIPRINT Repository Viewer in TSO/ISPF\n\u2022Eclipse-based Graphical User Interface\nNOTE\nFor more information on the Eclipse Interface see Release Information and Installing.\nSymbolic Postprocessors\nWrites symbolic information extracted from COBOL, PL/I, or Assembler program listings to the PROTSYM file.\nUtilities\nLets programmers perform the following tasks:\n\u2022Provide load library reports that identify and describe COBOL CSECTs in detail\n\u2022Generate a report describing which SymDump  Batch modules are currently loaded in the CSA area of LPA\n\u2022Generate a report detailing the options set as installation defaults\n\u2022List the contents of the symbolic files\n\u2022List and maintain the contents of the central VSAM repository\n\u2022Display Dynamic Symbolic Support (DSS) options for local ISPF session in a user's personal ISPF profile.\nUsing Symbolic Support\nSymDump  Batch reports on all abending programs and provides additional information for COBOL, PL/I, and assembler\nprograms. For each of these programming languages, symbolic support can be used to enhance the content of your\nAbend or Snap reports. Symbolic support is not required when using this product.\nThis section provides a brief overview of symbolic support. A complete description of symbolic support, including all of the\nsymbolic postprocessors and utilities, can be found in Symbolic Support .\nSymbolic Support Features\nWhen symbolic information is available for your programs, the following additional information can be found in your Abend\nor Snap reports:\n\u2022COBOL\n\u2013Abending or last executed COBOL source statement", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9a0e72ea0ade-1", "text": "\u2022COBOL\n\u2013Abending or last executed COBOL source statement\n\u2013Referenced variables on the last executed statement\n\u2013Merged variable displays\n\u2022PL/I\n\u2013Abending or last executed PL/I source statement\n\u2013Referenced variables on the last executed statement\n\u2013Merged variable displays\n\u2022Assembler\n\u2013Abending or last executed Assembler source statement\n\u2013Merged storage displays for active USINGs\nFor more information about how post-processors store symbolic information, see Symbolic Support.\n 787", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "90469719de57-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse Existing CSL Files\nCSL files created by Optimizer/II , Optimizer/II , or by an earlier release of SymDump  Batch can also be used as a source\nof symbolic information.\nThere is no need to convert your existing CSL files into the PROTSYM format .\nHowever, while CSL files can still be used as input for report generation, SymDump  Batch will no longer create new CSL\nmembers.\nAccess Symbolic Information at Execution Time\nAfter the symbolic information is stored in a PROTSYM or CSL file, the information can be accessed by SymDump  Batch\nto provide symbolic support for your Abend and Snap reports.\nWhen an Abend or Snap report is initially written to CAIPRINT at execution time, SymDump  Batch automatically searches\neach of the PROTSYM and CSL files defined in your installation defaults member, CAOUDFRX. You can define as many\nsymbolic files as needed for your installation, and you can freely mix PROTSYM and CSL files. You can display the list of\nsymbolic files defined at your installation using the SYM command from the CAIPRINT Repository Viewer.\nYou can also add one additional symbolic file, a PROTSYM or CSL, to your execution JCL using the CAISYM DD\nstatement. Your installation may use an alternate DD name for CAISYM. Check with your system administrator if you are\nnot sure. Alternatively, you can have one symbolic file dynamically allocated at execution time using the SYMDSN option\nin the CAIOPTS file.\nThe search order for symbolic information at execution time is as follows:\n\u2022The symbolic file defined using the CAISYM DD, if any\n\u2022The symbolic file defined using the SYMDSN option in CAIOPTS, if any", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "90469719de57-1", "text": "\u2022The symbolic file defined using the SYMDSN option in CAIOPTS, if any\n\u2022The globally defined symbolic files from your installation defaults member CAOUDFRX at the time of execution, in the\norder that they are defined, if any\nIf no exact match is found, the symbolic information retrieved from the symbolic file defined by the CAISYM DD or by the\nSYMDSN option is used. If neither is available, the most recent symbolic information is selected.\nNOTE\nA symbolic mismatch can cause unpredictable results or misleading symbolic information in the formatted\nreports. This situation can be mitigated by installing and activating DSS. For more information, see Dynamic\nSymbolic Support.\nAdd Symbolic Information Using the Viewer\nSymbolic information does not need to be available at the time an Abend or Snap report is created, provided that your\nreports are being written to a CAIPRINT repository data set. If so, you can easily add symbolic information after the report\nis written to the repository, when you actually view the report. Simply load the COBOL, PL/I, or Assembler listing file into\nthe PROTSYM using the appropriate postprocessor, then select the report for viewing.\nYou can add the symbolic information to any of the symbolic files defined in your installation defaults member,\nCAOUDFRX. Alternatively, you can add the symbolic information to your own personal symbolic file and then define\nthat symbolic file to the CAIPRINT Repository Viewer as a supplemental symbolic file. Each user can define as many\nas sixteen supplemental PROTSYM or CSL files that are only searched when that individual user selects a report from\nthe repository for viewing. For more information about supplemental symbolic files, see Using the CAIPRINT Repository\nViewer.\nWhen you select a report from the repository for viewing, SymDump  Batch tries to find an exact match for COBOL and PL/", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "90469719de57-2", "text": "I programs using the date/time stamps in both the listing and the object code.\n 788", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e646bb50cde5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe search order for symbolic information when using the viewer is as follows:\n\u2022The symbolic file that was defined using the CAISYM DD when the program was executed, if any\n\u2022The symbolic file that was defined using the SYMDSN option in CAIOPTS when the program was executed, if any\n\u2022The supplemental symbolic files that are defined for your userid at the time the report is selected for viewing, in the\norder that they are defined, if any\n\u2022The globally defined symbolic files that are defined in your installation defaults member CAOUDFRX at the time the\nreport is selected for viewing, in the order that they are defined, if any\nIf no exact match is found, the symbolic information retrieved from the symbolic file defined by the CAISYM DD or by the\nSYMDSN option is used. If neither is available, the most recent symbolic information is selected.\nNOTE\nA symbolic mismatch can cause unpredictable results or misleading symbolic information in the formatted\nreports. This situation can be mitigated by installing and activating DSS. For more information, see Dynamic\nSymbolic Support.\nReporting\nSymDump  Batch provides reports when a system dump is requested as the result of an ABEND, or when a snap request\nis made using a call to CAODSNAP. Until that time, there is no intervention of any kind. For more information, see Abend\nReporting with Language Environment (LE) later in this section.\nSymDump  Batch reports on all programs, with additional information provided for COBOL, PL/I, and Assembler programs.\nThere are several levels of information that may be available depending on the programming language and the existence\nof symbolic information. \nThe contents of a report are completely controlled by the installation defaults and override options. It is also possible to", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e646bb50cde5-1", "text": "receive a system dump in addition to abend reports. Exclusion criteria can be selected at installation time to allow for\nsystem dumps instead of abend reports for certain ABENDs.\nSymDump  Batch generates two different reports:\n\u2022The abend report eliminates much of the searching and guesswork involved in debugging programs. The abend report\npresents diagnostic information and key storage data information in a straightforward format.\n\u2022The Snap report provides snapshots of your program's data areas and other pertinent program information. To invoke\nthe Snap report, place a CALL at the spot in your program where you want the snapshot to be taken. You can specify\nmultiple snaps in a single program execution.\nHierarchy of Information\nWhen SymDump  Batch produces an abend report, all of the programs that are active at the time of the ABEND are\nincluded, unless the ACTONLY option is set to ON, or unless individual programs are excluded from reporting in your\ninstallation defaults.\nSeveral factors affect how much information is provided for each program, including:\n\u2022For COBOL or PL/I programs, storage areas and control blocks are broken out and formatted, and compiler statistics\nare provided.\n\u2022If your PROTSYM (or CSL) contains symbolic information for an active COBOL, PL/I, or Assembler program, the\nreports include the last executed source statement, the names and values of the variables, and more.\nUsage Considerations\nWhen using abend reporting, be aware of these considerations:\n 789", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "47a77c2e28b9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022SymDump  Batch does not provide any reporting for programs that abend under CICS or other teleprocessing\nenvironments.\n\u2022SymDump  Batch is only supported on z/OS systems.\n\u2022For the most productive use of SymDump  Batch, your applications should use standard IBM-type program linkage\nconventions whenever possible.\n\u2022SymDump  Batch does not provide any reporting if the abending program resides above the bar.\nReporting Options\nYou can change the default value of most SymDump  Batch options by coding an override in the options file at execution\ntime. The default DDNAME of the options file is CAIOPTS, which you can change at installation time. At execution time,\nyou can allocate the options file dynamically, allowing each user to customize their options differently without coding any\nadditional JCL.\nThe following list contains all reporting options:\nACB ON|OFF\nPrints access method control blocks for open VSAM files in an Abend or Snap report.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nAMB ON|OFF\nPrints access method blocks for open VSAM files in Abend or Snap Reports.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nAMBL ON|OFF\nPrints an access method block list for open VSAM files in an Abend or Snap report.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nASMINST ON|OFF\nDisplays the abending assembler instruction and associated operands on the Abend page.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nBINFRMT DEC|HEX\nSpecifies whether to display binary data values in decimal display or hexadecimal format on the merged Data", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "47a77c2e28b9-1", "text": "Specifies whether to display binary data values in decimal display or hexadecimal format on the merged Data\nDivision displays of an Abend or Snap report.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nBLLMAX 512|nnnn\nBecause the length of an 01-item in the linkage section cannot always be determined, this option specifies the\nmaximum number of bytes which are formatted for a BLL cell whose range is unknown. The maximum value is\n4096.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\n 790", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5e32b10d4558-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBLOCKS ON|OFF\nA data management control block option which sets all control block options, including all VSAM control block\noptions, either ON or OFF for an Abend or Snap report. This option overrides any previous control block options.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nDB2ACTIV ON|OFF\nIndicates whether to display summary information for only those packages and DBRMs that are active at the time\nof an Abend or Snap. If the option is set to OFF, summary information is displayed for all of the packages and\nDBRMs defined to the DB2 plan.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nDCB ON|OFF\nPrints data control blocks for all open files in an Abend or Snap report.\nSynonym:  None\nComponent:  Reporting\nWhen used: Execution time\nDEB ON|OFF\nPrints data extent blocks for all open files in an Abend or Snap report.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nDUMP ON|OFF\nSpecifies whether to force or suppress a system dump after it has completed its processing.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nFILES ON|OFF\nSpecifies whether to display all open files not already shown in the File Section display of an Abend or Snap\nreport.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nFIRST128 ON|OFF\nControls whether to print only the first 128 bytes of the current record of each open file or the entire record. This\noption affects both the File Section display and Open Files report of an Abend or Snap report.\nSynonym:  None", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5e32b10d4558-1", "text": "Synonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nGRPADDR ON|OFF\nControls whether to display the base locator, displacement and address of a group item on the merged Data\nDivision displays of an Abend or Snap report.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nIOB ON|OFF\nPrints input/output blocks for all open files in an Abend or Snap report.\nSynonym:  None\n 791", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "72b335cf6ffb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nComponent:  Reporting\nWhen used:  Execution time\nLINECOUNT 60|nnn\nSpecifies the number of lines on each page of output at execution time or view time. where nnn can be any\ninteger from 10 to 255, inclusive.\nSynonym:  LINECNT\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nLINKAGE ALL|NONE\nSpecifies whether to display (ALL) or suppress (NONE) the program's Linkage Section in an Abend or Snap\nreport.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nLISTLINE=0|nn\nSpecifies the number of additional listing lines to be merged into a report before and after the source statement at\nabend, snap, or transfer.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nLOCALSTOR ALL|NONE\nSpecifies whether to display (ALL) or suppress (NONE) the program's Local-Storage Section in an Abend or Snap\nreport.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nLOGROS ON|OFF\nSpecifies whether to send a message describing the abend to the Roscoe  user who submitted the job. You\nmust establish a list of Roscoe  job names in the SymDump  Batch SymDump  Batch defaults using the ROSCOE\nparameter.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nLOGTSO ON|OFF\nIndicates whether to send a message describing the abend to the TSO user who submitted the job.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "72b335cf6ffb-1", "text": "Synonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nLOGUNI ON|OFF\nIndicates whether to send a message describing the abend to the NSM  console.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nMEMMAP ON|OFF\nProduces a display of the memory map (TGT, PGT, and DSA) in an Abend or Snap report.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\n 792", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d0530854455b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMERGEDB ON|OFF\nIndicates whether to symbolically map DB2, IDMS, and IMS data. If the option is set to ON, data item information\nsuch as the name, picture clause, and usage type is merged with the dump output for those areas.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nMRGAUTO ON|OFF\nIndicates whether to symbolically map the data for PL/I automatic storage. If this option is ON, data item\ninformation such as name and definition is merged with the data.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nMRGBASED ON|OFF\nIndicates whether to symbolically map the data for PL/I based variables. If this option is ON, data item information\nsuch as name and definition is merged with the data.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nMRGCNTLD ON|OFF\nIndicates whether to symbolically map the data for PL/I controlled variables. If this option is ON, data item\ninformation such as name and definition is merged with the data.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nMRGDATA ON|OFF\nIndicates whether to set all data merging options either ON or OFF for an Abend or Snap report. This option\noverrides any previous merging options.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time\nMRGDSECT ON|OFF\nIndicates whether to symbolically map the data for Assembler storage areas when a USING is active. If this option", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d0530854455b-1", "text": "is ON, data item information such as name and definition is merged with the data.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nMRGFILES ON|OFF\nIndicates whether to symbolically map the data in the File Section display of an Abend or Snap report. If the\noption is set to ON, data item information such as the name, picture clause, and usage type is merged with the\ndata for the current logical record.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nMRGLINK ON|OFF\nIndicates whether to symbolically map the data in the Linkage Section display of an Abend or Snap report. If the\noption is set to ON, data item information such as the name, picture clause, and usage type is merged with the\ndata.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\n 793", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ac90e68da3e3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMRGLOCAL ON|OFF\nIndicates whether to symbolically map the data in the Local-Storage Section display of an Abend or Snap Report.\nIf this option is ON, data item information such as the name, picture clause, and usage type is merged with the\ndata.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nMRGPARMS ON|OFF\nIndicates whether to symbolically map the data for PL/I parameter storage. If this option is ON, data item\ninformation such as name and definition is merged with the data.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nMRGSTAT ON|OFF\nIndicates whether to symbolically map the data for PL/I static storage. If this option is ON, data item information\nsuch as name and definition is merged with the data.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nMRGWORK ON|OFF\nIndicates whether to symbolically map the data in the Working-Storage Section of an Abend or Snap report. If the\noption is set to ON, data item information such as the name, picture clause, and usage type is merged with the\ndata.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nNDVRASM=OFF|ON\nIndicates whether the symbolic file should always be dynamically populated for assembler programs which are not\nLE enabled. This option will only take affect when dynamic symbolic support (NDVRDSS) is active for Endevor .\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ac90e68da3e3-1", "text": "Component:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nNDVRDSN=dsname\nSpecifies the name of the symbolic file which will be dynamically populated when dynamic symbolic support\n(NDVRVSS) is active for Endevor . The data set specified must be a PROTSYM file. When specified, it will\nautomatically be included in the symbolic file search list.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nNDVRDSS=OFF|ON\nIndicates whether dynamic symbolic support is active for Endevor . This option will not take effect at view time,\nunless it was also specified at execution time.\nSynonym:  None\nComponent:  Reporting, CAIPRINT Formatter\nWhen used:  Execution time, view time\nOCCURS 1|nnnnnnnn|MAX\nSpecifies whether to symbolically map the maximum number of table occurrences when using the merging\noptions. If the option is set to a value lower than the number of occurrences in the table, the remainder of the table\noccurrences are dumped in hexadecimal format. If OCCURS MAX is specified, the option is set to its maximum\nvalue of 16777215.\n 794", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "58c853ba1ef0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nPLH ON|OFF\nPrints place holders for open VSAM files in an Abend or Snap report.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nPRTREPT BOTH|REPOS|PRTDD\nIndicates whether to write the CAIPRINT report to the central VSAM repository (REPOS), the CAIPRINT DD\n(PRTDD), or both.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nREADLL=ON|OFF\nIndicates whether SymDump  Batch will attempt to read LINKLIST libraries to obtain module information for\nAbend and Snap reports. If READLL is OFF, SymDump  Batch may not be able to report on those programs in the\napplication that were loaded from LINKLIST.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nREGMAX (xxx,yyy)|(128,256)\nIndicates how many bytes of addressable storage to display before and after the address in each register for\nan Assembler program. xxx represents the number of bytes before and must be within the range 0-32767.\nyyy represents the number of bytes after and must be within the range 0-4096. The REGMAX values must be\nenclosed in parentheses, and if both xxx and yyy are specified, they must be separated by a comma. If only xxx is\nspecified, yyy is assumed to have the same value.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nRPL ON|OFF\nPrints a Request Parameter List for open VSAM files in an Abend or Snap report.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "58c853ba1ef0-1", "text": "Prints a Request Parameter List for open VSAM files in an Abend or Snap report.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nRPTSZ80 ON|OFF\nIndicates whether to force all data in dump format to appear in an 80-column format.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nSAVEAREA ON|OFF\nProduces the Save Area Trace on an Abend report. The Save Area Trace displays the chained register save\nareas starting at the abending module.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nSAVEHEAP ON|OFF\nIndicates whether to save the LE heap storage when a report is created. SAVEHEAP ON is required at execution\ntime to use SHOWHEAP ON for LE enabled COBOL or Assembler programs.\n 795", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "78d3fa38df94-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nSHOWHEAP ON|OFF\nIndicates whether to display the LE or PL/I heap storage when a report is displayed. SAVEHEAP ON is required\nat execution time in order to use SHOWHEAP ON for LE enabled COBOL or Assembler programs.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nSHOWUNMRG ALL|NONE|TBLS\nIndicates whether to display storage for unmerged data when symbolic merging has been requested for the\nsection. If the section is being displayed in the standard dump format, SHOWUNMRG has no effect. Specify ALL\nto always display unmerged data, NONE to never display unmerged data, or TBLS to display unmerged data only\nfor table elements after the OCCURS limit has been reached for each table.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nSNAP 0|nnnnn|ON|OFF\nIndicates whether to generate a Snap report. You must specify the number of SNAPs to allow using nnnnn.\nThe maximum number allowed is 32,767. To use SNAP, you must include a call to CAODSNAP in your source\ncode wherever you want a snapshot to be taken. You may use the SNAP feature in the same run with the\nINTERCEPTS feature. If your program contains SNAP calls and you want to run it without them, you do not need\nto recompile; simply do not specify the SNAP option at all. WARNING! Each call to CAODSNAP generates a\nseparate SNAP report in your central VSAM repository. If your program contains multiple SNAP calls (or a SNAP", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "78d3fa38df94-1", "text": "call within a loop), you can write the output to the CAIPRINT DD alone, to avoid flooding the repository. See the\nPRTREPT option.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nSYMDSN dsname\nSpecifies to dynamically allocate the data set name of a symbolic file for retrieving symbolic information. The\ndata set can be a PROTSYM file or a CSL library. The DDNAME used for dynamic allocation is determined by\nthe value of SYMDD in the installation defaults module CAOUDFRX. SYMDSN is ignored when that DDNAME\nis already allocated. Using SYMDSN does not prevent the searching of other symbolic files defined in your\ninstallation defaults.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nUCB ON|OFF\nPrints unit control blocks for all open files in an Abend or Snap report.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nUSERID 'your text'| 'CA'\nIndicates a user identification statement (1-60 bytes). You can change the default title during product installation. It\nis included in all report headings.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\n 796", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6d5604086df9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nVSAMCAT=OFF|ON\nIndicates whether to format the VSAM catalog information for each open VSAM file.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nVSAMIDX ON|OFF\nPrints the VSAM indexed control blocks for the index portion of an open VSAM file along with the control blocks\nfor the data portion in an Abend or Snap report.\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nWORKSTOR ALL|NONE\nIndicates whether to display (ALL) or suppresses (NONE) the program's Working-Storage Section display.\nSynonym:  None\nComponent:  CAIPRINT Formatter\nWhen used:  Execution time, view time\nWTO ON|OFF\nIndicates whether to send a message describing the abend to the job log (using WTO with ROUTCDE=11).\nSynonym:  None\nComponent:  Reporting\nWhen used:  Execution time\nStandard Options\nStandard options are specified using the CAIOPTS data set.\nFor more information about application examples, see Reporting.\nFormatting Options\nThe formatting options can be modified at execution time or view time. The execution-time options are specified using the\nCAIOPTS data set. The view-time options are specified through the Report Options panel in the CAIPRINT Repository\nViewer. For more information about how to override these options at view time, see CAIPRINT Repository Viewer.\nFor more information about application examples, see Reporting.\nVSAM Control Block Options\nVSAM Control Block options are specified using the CAIOPTS data set. These options control which VSAM Control\nBlocks are displayed on the Open Files report: ACB, AMB, AMBL, PLH, RPL, and VSAMIDX. The Data Management", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6d5604086df9-1", "text": "Control Blocks, including VSAM Control Blocks, for all open files in the job step optionally display.\nNOTE\nBLOCKS ON or OFF turns all VSAM control block options ON or OFF. For example, to display open ACBs and\nno other I/O control blocks specify the following:\n BLOCKS OFF ACB ON.\n \nNo Data Management Control Blocks, except open ACBs, are displayed.\n 797", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f83800431233-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nData Management Control Block Options\nData Management Control Block options are specified using the CAIOPTS data set. The Data Management Control\nBlocks, including VSAM Control Blocks, optionally display on the File Section Display. These options control which I/O\nblocks are displayed on the Open Files Report: BLOCKS, DCB, DEB, IOB, and UCB.\nNOTE\nTo print all control blocks except one, specify BLOCKS ON with the block you do not want printed specified as\nOFF. For example, to display all Data Management Control Blocks, except UCBs, specify:\n BLOCKS ON\n UCB OFF\n \nCoding Options\nThe general rules for coding keywords and their options at execution time and view time are as follows:\n\u2022Use one or more spaces as delimiters for options.\n\u2022Use an equal sign (=) to separate a keyword from its option value. For example, DUMP=ON and DUMP ON are both\nacceptable.\n\u2022Use positions 1 through 72 and ignore positions 73 through 80.\nYou can specify the following while coding keywords:\n\u2022Options in any order; if you repeat an option, the last specified occurrence is applied.\n\u2022Any number of options on a line; however, do not split options between two lines.\nYou can also do the following:\n\u2022Denote a comment line with an asterisk in position 1.\n\u2022Input an option associated with a keyword when you specify the keyword. To obtain the total default value of the\nkeyword, omit the entire keyword and option.\nOverride Defaults\nYou can override option default values by specifying options in the card-image data set defined by the CAIOPTS DD\nstatement. You can specify this DD statement at execution time.\nAt view time, you can override options through the Report Options panel of the CAIPRINT Repository Viewer. For more", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f83800431233-1", "text": "information, see Using the CAIPRINT Repository Viewer.\nNOTE\nAny options that were fixed in the installation defaults cannot be changed. The product is shipped with all\ndefaults unfixed.\nSymDump  Batch JCL Requirements\nBy default, SymDump  Batch does not require any additional JCL at execution time. All SymDump  Batch modules must\nbe made available at installation time (through LPA or LINKLIST), and SymDump  Batch is initialized using Common\nComponents and Services  for z/OS. For more information about initializing SymDump  Batch, see Installing.\nBecause SymDump  Batch remains dormant until a dump is requested as the result of an ABEND, you must include a\nSYSUDUMP DD statement in your JCL to receive abend reports. To suppress the system dump, specify DUMP OFF in\nyour options file overrides, or DUMP=OFF in your installation defaults (CAOETABL).\n 798", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ccdc0d9a1a1c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nRepository Requirements\nThe repository used by SymDump  Batch has a default name of CAIPRTLB, which can be customized at installation time.\nThis file is dynamically allocated, if not included in the JCL, using the data set name specified at installation time. You can\nuse the user exit CAOCUPRT to select a repository library based on criteria such as the job name or userid. You can also\noverride the default repository library by specifying the PRTLIB execution option.\nReport File Requirements\nThe report file used by SymDump  Batch has a default name of CAIPRINT, which you can change during installation. This\nfile is dynamically allocated if it is not included in the JCL. The SYSOUT class for dynamic allocation is also an installation\noption with a default value of SYSOUT=*.\nOption File Requirements\nThe options file has a default name of CAIOPTS, which you can change during installation. This file can also be\ndynamically allocated if it is not included in the JCL at execution time. The high-level qualifier of the options file for\ndynamic allocation is equal to the userid, while the remainder of the data set name is selected at installation time. The\ndefault name is userid.CAIOPTS.\nSymbolic File Requirements\nThe symbolic file execution-time override has a default name of CAISYM, which you can change during installation. This\nfile is not required in the JCL, but can be used to augment the symbolic file selection list defined at installation time. If a\nsymbolic file override is specified in the JCL or through the SYMDSN execution option, it is searched first for symbolic\ninformation. This lets each user or group of users maintain their own symbolic file.\nSuppress Abend Reports", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ccdc0d9a1a1c-1", "text": "Suppress Abend Reports\nIn addition to the exclusion criteria provided with the default member CAOETABL, you can suppress an abend report for\nany job step by adding a DD statement to your JCL.\nTo suppress abend reports, add a DD statement to your JCL.\nThe STOPDD option, defined in CAOETABL, defines the name of the DD. The default value is CAOESTOP. Following is\nan example of using this DD with the default value:\n//CAOESTOP DD DUMMY\nWhen the DD statement specified in your defaults table is present, SymDump  Batch is bypassed and your standard dump\nfacility is invoked.\nReports\nFour reports are described in this section. The Execution Monitor produces two reports, the CAIOPTS File Processing\nReport and the Execution Monitor Summary. The Execution Monitor is the component of SymDump  Batch that establishes\nthe reporting environment. The CAIOPTS File Processing report displays the input options you specified to control abend\nor Snap reports. The Execution Monitor Summary displays the options in effect at the time the report was generated.\nThe following list describes the abend and Snap reports:\n\u2022The abend report is printed whenever an ABEND occurs during program execution. The report contains the following:\n 799", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8bc77d169a3d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2013Diagnostic information based on the type of ABEND.\n\u2013The COBOL, PL/I, or Assembler source statement on which the ABEND occurred, if symbolic information for the\nabending program was available. Otherwise, the machine instruction and its operands are displayed.\n\u2013The names and values of the data items referenced by the abending statement are also displayed if symbolic\ninformation is available from a PROTSYM file, or from a CSL file if MXREF was specified when the CSL member\nwas created.\n\u2013Addresses and other specifics pertinent to the ABEND.\n\u2013The module call sequence showing the hierarchy of programs that invoked the abending program.\n\u2013The contents of the abending program's registers at ABEND.\n\u2013Formatted data displays of all program variable fields, if symbolic support is available. For COBOL, this includes\nWorking Storage, Local-Storage, Linkage and File Sections. For PL/I, this includes all variables for all active\nprocedures and a dump of both static and external program storage. For Assembler, this includes storage mapping\nof all addressable storage from the USINGs in effect at the abending statement and a dump of all unmapped\naddressable storage. If symbolic support is not available, all data areas are displayed in standard dump format.\n\u2013A standard dump display of the program-level control blocks. For COBOL, this includes the PGT, TGT, and DSA.\nFor PL/I, this includes the DSA for each active procedure.\n\u2013An optional display of the memory map (TGT, PGT, DSA).\n\u2013The data control blocks of all open files not reported on in the FILE SECTION (optional).\n\u2013The Save Area Trace report showing the standard chain of register areas (optional).", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8bc77d169a3d-1", "text": "\u2013The Save Area Trace report showing the standard chain of register areas (optional).\n\u2022The Snap report provides you with a snapshot of your program at strategic points during execution. The Snap report\ncontains the same information as the abend report with the exception of the data identifying the ABEND and the\nmodule call sequence. To produce a Snap report, you must do the following:\n\u2013Insert a call to program CAODSNAP.\n\u2013Specify the SNAP ON option at execution time.\nNOTE\nEach call to CAODSNAP generates a separate Snap report in your central VSAM repository. If your program\ncontains multiple snap calls (or a snap call within a loop), you may want to write the output to the CAIPRINT\nDD alone, to avoid flooding  the repository. For more information, see the PRTREPT option in Reporting\nOptions.\nAbend Report\nThe SymDump  Batch abend report contains the following sections:\n\u2022Abend page, including abending source statement\n\u2022Module call sequence\n\u2022Program information for each active program or procedure\n\u2022Open Files report\n\u2022Save Area Trace report\n\u2022IMS report\n\u2022DB2 report\n\u2022IDMS/DB  report\nProgram information is provided for each active program or procedure at the time of the ABEND. The content depends on\nthe programming language, as follows:\n\u2022COBOL\n 800", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c5a0f8ed918f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2013Compile and link statistics\n\u2013Data division displays\n\u2013Registers\n\u2013PGT, TGT, and DSA\n\u2022PL/I\n\u2013Compile and link statistics\n\u2013Last statement executed in each active procedure\n\u2013Variables for each active procedure\n\u2013Last registers for each active procedure\n\u2013DSA for each active procedure\n\u2013Static and external storage dump\n\u2013Program storage dump\n\u2022Assembler\n\u2013Link statistics\n\u2013Program Status Word\n\u2013Registers, including access registers\n\u2013Addressable storage displays\n\u2013Program storage dump\nAbend Page\nThe abend report begins with the abend page, which displays specific information pertaining to the ABEND. A sample\nabend page follows:\n                 ****************************\n                 *             *   S-0C7    *\n                 *  A B E N D  *------------*\n                 *             *  CAOEDEMO  *\n                 ****************************\n  ********************************************************************************\n  *  CEE3207S The system detected a data exception (System Completion            *\n  *          Code=0C7).                                                          *\n  ********************************************************************************\n  *****************************************************************************************\n  *      DESCRIPTION:  S0C7 - DATA EXCEPTION: A NUMERIC FIELD CONTAINED NON-NUMERIC       *\n  *                    DATA.                                                              *\n  *                                                                                       *\n  *  POSSIBLE CAUSES:   1. NUMERIC DATA WAS NOT INITIALIZED, OR VARIABLE DATA NOT         *\n  *                        NUMERIC.                                                       *\n  *                     2. ATTEMPTED TO PERFORM A DECIMAL ARITHMETIC INSTRUCTION ON       *\n  *                        EITHER AN UNSIGNED OR UNPACKED FIELD.                          *\n  *                     3. A SUBSCRIPT OR INDEX CONTAINED AN INVALID VALUE:               *\n  *                        A. FAILURE TO INITIALIZE A SUBSCRIPT.                          *", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c5a0f8ed918f-1", "text": "*                        A. FAILURE TO INITIALIZE A SUBSCRIPT.                          *\n  *                        B. INITIALIZED A SUBSCRIPT TO ZERO, BUT FAILED TO ADD 1        *\n  *                           BEFORE ITS FIRST USE.                                       *\n  *                        C. NOT REINITIALIZING A SUBSCRIPT AFTER A LOOP USING IT.       *\n  *                        D. SUBSCRIPTING BY INPUT DATA THAT WAS NOT CHECKED FIRST FOR   *\n  *                           A VALID RANGE OF VALUES.                                    *\n  *                        E. COMPUTING THE SUBSCRIPT WITHOUT CHECKING THE RESULTS FOR    *\n  *                           A VALID RANGE OF VALUES.                                    *\n  *                                                                                       *\n 801", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8cc84d57a317-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  *       TO CORRECT:  1. REVIEW AND CORRECT THE ABOVE STATED POSSIBLE CAUSES.            *\n  *                    2. REVIEW THE LAST KNOWN I/O OR CALL INFORMATION. IT IDENTIFIES    *\n  *                       THE PROGRAM AT THE OFFSET WHERE THE LAST KNOWN I/O OR CALL WAS  *\n  *                       MADE.                                                           *\n  *                    3. REVIEW THE Z/OS BREAKING EVENT ADDRESS LINE. IF PRESENT, IT     *\n  *                       IDENTIFIES THE PROGRAM AT THE OFFSET WHERE THE BRANCH           *\n  *                       ORIGINATED.                                                     *\n  *****************************************************************************************\n  \n  **********************\n  * ABENDING STATEMENT *\n  **********************\n  \n  PROGRAM: CAOEDEMO  OFFSET: 003D78  LINE: 001285\n  \n  001285        MOVE MASK1  TO  BINARY-1\n  \n  LINE#   LEVEL/FIELD NAME                      VALUE/LOCATION                     DEFINITION\n  ------  ---------------------------------     --------------------------------  \n -------------------------------------\n  000329  03 MASK1                              ALL '*'                            X(2)\n  000178  03 BINARY-1                          +1                                  S9(4) BINARY\n  \n  ABENDING INSTRUCTION\n     4F40 D4B8         CONVERT\n  \n  OPERAND: REG  4\n    VALUE: 00000002 \n  \n  OPERAND: TEMP STORAGE CELL               DSA     DISP 0004B8\n    VALUE: 0000000000000CC5                <-- NOT NUMERIC\n  \n  INTERRUPT OCCURRED AT ADDRESS B6304686 AT OFFSET +003D7E IN PROGRAM CAOEDEMO", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8cc84d57a317-1", "text": "ENTRY POINT ADDRESS IS 36300908 AT OFFSET +000000 IN PROGRAM CAOEDEMO\n  LAST KNOWN I/O OR CALL OCCURRED AT ADDRESS 36301CDE AT OFFSET +0013D6 IN PROGRAM CAOEDEMO\n \nThe abend page begins with the abend code and associated diagnostic information:\n                 ****************************\n                 *             *   S-0C7    * [A] \n                 *  A B E N D  *------------*\n                 *             *  CAOEDEMO  * [B] \n                 ****************************\n   ********************************************************************************\n   *  CEE3207S The system detected a data exception (System Completion            *\n   * [C]        Code=0C7).                                                          *\n   ********************************************************************************\n   *****************************************************************************************\n   * [D]    DESCRIPTION:  S0C7 - DATA EXCEPTION: A NUMERIC FIELD CONTAINED NON-NUMERIC       *\n   *                    DATA.                                                              *\n   *                                                                                       *\n 802", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1c41ebbfba59-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n   *  POSSIBLE CAUSES:   1. NUMERIC DATA WAS NOT INITIALIZED, OR VARIABLE DATA NOT         *\n   * [E]                      NUMERIC.                                                       *\n   *                     2. ATTEMPTED TO PERFORM A DECIMAL ARITHMETIC INSTRUCTION ON       *\n   *                        EITHER AN UNSIGNED OR UNPACKED FIELD.                          *\n   *                     3. A SUBSCRIPT OR INDEX CONTAINED AN INVALID VALUE:               *\n   *                        A. FAILURE TO INITIALIZE A SUBSCRIPT.                          *\n   *                        B. INITIALIZED A SUBSCRIPT TO ZERO, BUT FAILED TO ADD 1        *\n   *                           BEFORE ITS FIRST USE.                                       *\n   *                        C. NOT REINITIALIZING A SUBSCRIPT AFTER A LOOP USING IT.       *\n   *                        D. SUBSCRIPTING BY INPUT DATA THAT WAS NOT CHECKED FIRST FOR   *\n   *                           A VALID RANGE OF VALUES.                                    *\n   *                        E. COMPUTING THE SUBSCRIPT WITHOUT CHECKING THE RESULTS FOR    *\n   *                           A VALID RANGE OF VALUES.                                    *\n   *                     4. A COMP-3 FIELD HAD AN INVALID SIGN.                            *\n   *                                            .                                          *\n   * [F]     TO CORRECT:  1. REVIEW AND CORRECT THE ABOVE STATED POSSIBLE CAUSES.            *\n   *                    2. REVIEW THE LAST KNOWN I/O OR CALL INFORMATION. IT IDENTIFIES    *\n   *                       THE PROGRAM AT THE OFFSET WHERE THE LAST KNOWN I/O OR CALL WAS  *\n   *                       MADE.                                                           *\n   *                    3. REVIEW THE Z/OS BREAKING EVENT ADDRESS LINE. IF PRESENT, IT     *\n   *                       IDENTIFIES THE PROGRAM AT THE OFFSET WHERE THE BRANCH           *", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1c41ebbfba59-1", "text": "*                       IDENTIFIES THE PROGRAM AT THE OFFSET WHERE THE BRANCH           *\n   *                       ORIGINATED.                                                     *\n   *****************************************************************************************\n \n[A]\nDisplays the system or user abend code.\n[B]\nDisplays the abending module name.\n[C]\nDisplays the LE message associated with the ABEND, if LE is active and a message is available.\n[D]\nDisplays a description of the abend code.\nIf the abend code indicates a DB2 ABEND (for example, S04E or S04F), the DB2 reason code is displayed with\nthe appropriate description.\n[E]\nDisplays a list of possible causes for the ABEND.\n[F]\nDisplays suggested strategies for solving the problem.\nIf the ABEND occurs in a DB2 application, the DB2 return code, SQLCODE, is displayed with the associated messages.\nThe abending statement information follows the diagnostic box:\n   **********************\n   * ABENDING STATEMENT *\n   **********************\n  \n  [A] PROGRAM: CAOEDEMO  OFFSET: 003D78  LINE: 001285\n  \n   001285        MOVE MASK1  TO  BINARY-1 [B] \n  \n 803", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "85deec8c7a21-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n   LINE#   LEVEL/FIELD NAME                      VALUE/LOCATION                     DEFINITION\n  ------  ---------------------------------     --------------------------------   --------------------\n  [C] 000329  03 MASK1                              ALL '*'                            X(2)\n   000178  03 BINARY-1                          +1                                  S9(4) BINARY\n \n[A]\nDisplays the name of the program that contains the abending statement, the offset into the program for that\nstatement, and line number of the statement.\nIf the program was compiled using PL/I, this line is followed by a line displaying the name of the procedure that\ncontains the abending statement and the offset into the procedure for that statement.\n[B]\nIf symbolic information is available for the program, displays the abending COBOL, PL/I, or Assembler source\nstatement, including the line number from the source listing.\nThe LISTLINE option lets users provide an additional context for the source statement at ABEND, snap, or\ntransfer. The value of the option is used to determine the number of additional source listing lines to display before\nand after the abending, snap, or transfer statement. If the LISTLINE option is nonzero, the specified number of\nsource listing lines leading up to the statement is displayed. This is followed by up to 10 lines of the abending,\nsnap, or transfer statement (including comment lines), with the first line delineated by dashed lines. Then the\nspecified number of source listing lines following the statement is displayed. If the LISTLINE option is zero, up\nto 10 lines of the abending, snap, or transfer statement are displayed (excluding comment lines for COBOL and\nAssembler programs).\n[C]\nDisplays the COBOL or PL/I variable names referenced by the abending source statement. This is available only", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "85deec8c7a21-1", "text": "if symbolic information is obtained from a PROTSYM file, or from a CSL if the XREF option was used when the\nCSL member was created.\nThe abending instruction is then displayed, followed by its operands. For COBOL and PL/I programs, this information is\nsuppressed when the ASMINST option is set to OFF:\n ABENDING INSTRUCTION\n  [A]  4F40 D4B8         CONVERT\n  \n  OPERAND: REG  4\n  [B] VALUE: 00000002 \n  \n  OPERAND: TEMP STORAGE CELL               DSA     DISP 0004B8\n    VALUE: 0000000000000CC5              [C] <-- NOT NUMERIC \n \n[A]\nDisplays the machine instruction that caused the ABEND.\n[B]\nDisplays the instruction operands for the abending instruction. If possible, the operands are related back to an\narea in the abending program.\n[C]\nDisplays the specific cause for the ABEND, if known.\nThe abend page ends with address information that may be helpful in debugging the ABEND.\n  INTERRUPT OCCURRED AT ADDRESS B6304686 AT OFFSET +003D7E IN PROGRAM CAOEDEMO [A] \n  \n  ENTRY POINT ADDRESS IS 36300908 AT OFFSET +000000 IN PROGRAM CAOEDEMO [B] \n  LAST KNOWN I/O OR CALL OCCURRED AT ADDRESS 36301CDE AT OFFSET +0013D6 IN PROGRAM CAOEDEMO [C] \n 804", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b432c594e60c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  THE Z/OS BREAKING EVENT INFORMATION IS NOT AVAILABLE. [D]\n[A]\nDisplays the absolute address and program offset where the interrupt occurred. If the abending program is PL/I,\nthe procedure offset is also displayed.\n[B]\nDisplays the absolute address and program offset of the entry point for the abending program.\n[C]\nDisplays the absolute address and program offset from which the last known I/O or CALL was made. If the\nabending program is PL/I, the procedure offset is also displayed. Alternatively, if the last I/O or CALL information\nis not available, that is stated here.\n[D]\nDisplays the absolute address and program offset of the last z/OS breaking event (from the breaking-event-\naddress register). If the abending program is PL/I, the procedure offset is also displayed. Alternatively, if the\nbreaking event information is not available, that is stated here.\nThe Offending Instruction\nIn the case of program check interruptions (0Cx), SymDump  Batch reports on the particular instruction that caused the\nABEND with as much supporting information as possible. SymDump  Batch can provide additional information for the\nfollowing:\n\u2022Protection\n\u2022Addressing\n\u2022Data\n\u2022Fixed-point overflow\n\u2022Fixed-point divide\n\u2022Decimal overflow\n\u2022Decimal divide\n\u2022Exponent overflow\n\u2022Significance\n\u2022Floating-point divide\nSymDump  Batch cannot always provide further analysis of the instruction, especially with the following exceptions:\n\u2022Operation\n\u2022Privileged operation\n\u2022Execution\n\u2022Specification\nModule Call Sequence\nThe next block of information is important if the application has multiple program modules. It lists the calling sequence of\nprograms that resulted in the execution of the program that produced the ABEND.\n  ************************\n  * MODULE CALL SEQUENCE  *\n  ************************", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b432c594e60c-1", "text": "************************\n  * MODULE CALL SEQUENCE  *\n  ************************\n  [A] [B] [C] [D] [E] [F] [G] [H] \n     LOAD                                PROGRAM     PROGRAM     ENTRY           COMPILE                     \n      VER/   \n     MODULE      PROGRAM/PROCEDURE                   ADDRESS     LENGTH      ADDRESS   DATE     TIME   \n LANGUAGE   REL    \n 805", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d401620dd5a6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                 -------- ------------------------- --------    -------      -------- --------  ------ \n ---------  -----  \n                         SYSTEM                      00000000    000000      36300908                        \n    \n     ASSEMBLER   \n   CALLED    CEE         CEE             00000000    000000      00000000                               \n ASSEMBLER   \n   CALLED    CAOEDEMO    CAOEDEMO        36300908    004AA8      36300908           14 MAR,2008 16.38.30 COB\n Z/OS 3.4.1  \n  (ABENDED)\n \nThe module call sequence portion displays the following information:\n[A]\nDisplays the load module name in which the called program resides.\n[B]\nDisplays the name of the called program. For COBOL and Assembler, this is the CSECT name. For PL/I this is\nthe active procedure name.\n[C]\nDisplays the storage address of the start of the called program.\n[D]\nDisplays the length of the called program.\n[E]\nDisplays the storage address of the entry point of the called program.\n[F]\nDisplays the date and time of compilation.\n[G]\nDisplays the source language in which the called program is coded.\n[H]\nDisplays the version of the COBOL or PL/I compiler used for compilation.\nNOTE\nThe register Save Area Trace portion is at the end of the abend report. If you want to know the actual contents\nof the registers when control was passed from program to program, see the Save Area Trace Report.\nCOBOL Reports\nThis section describes the information provided for COBOL programs.\nProgram Statistics\nFor each program in the report, this report contains statistics about the compile, link, and symbolic postprocessing used", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d401620dd5a6-1", "text": "when the program was built.\n  ********************\n  * PROGRAM CAOEDEMO *\n  ********************\n  [A] \n  COMPILED ON 14 MAR,2008 AT 16.38.30 WITH COBOL FOR Z/OS 3.4.1\n  COMPILE OPTIONS:ADV, APOST, NOAWO, DATA(24), NODBCS, NODECK, NODUMP, DYNAM,\n                       NOFASTSRT, NOLIB, LIST, MAP, NONAME, NONUMBER, OBJECT,    \n 806", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c07b70251db7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                       NOOFFSET, NOOPTIMIZE, NUMPROC(PFD), RENT, NOSEQUENCE, SOURCE, \n                       NOSSRANGE, NOTERM, NOTEST, TRUNC(STD), NOVBREF, NOWORD, XREF, \n                       ZWB   \n  [B] \n  SYMBOLIC INFORMATION RETRIEVED FROM USER01.PROTSYM\n  MEMBER: CAOEDEMO  DATE: 14 MAR,2008  TIME: 16.38.30   TYPE: PROTSYM\n  [C] \n  LINKED ON 14 MAR 2008 AT 16:38:33\n  LOAD LIBRARY: USER01.LOAD\n  MODULE LENGTH: 000056F8  (DECIMAL 22,264)\n  LINK OPTIONS: AC(0), AMODE(31), NOOVLY, NORENT, NOREUS, RMODE(24)\n \nThe COBOL report displays the following information for each program:\n[A]\nDisplays compile statistics, including the date and time of compilation, the compiler and release information, and\nthe options used.\n[B]\nDisplays the name of the symbolic file and the date and time of the symbolic listing used when symbolic\ninformation is used to format the report.\n[C]\nDisplays link-edit information including the date and time when the load module was created, the name of the load\nlibrary from which the program was loaded, the length of the module, and the linkage editor options used.\nData Division Displays\nThe Data Division portion of the abend report contains the following sections:\n\u2022File Section display\n\u2022Working-Storage Section display\n\u2022Local-Storage Section display\n\u2022Linkage Section display\nFile Section Display", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c07b70251db7-1", "text": "\u2022Local-Storage Section display\n\u2022Linkage Section display\nFile Section Display\nThe File Section portion of the abend report lists information for each file defined to the COBOL program, such as\nallocation information, access method, and whether the file is open or closed. If the file is open, information from the data\nmanagement control blocks, the current file status, and the contents of the current logical record are displayed. If the file\nwas accessed sequentially, the contents of the previous record may also be displayed. Optional displays include catalog\ninformation for VSAM files and dumps of data management control blocks.\nThe following example shows the beginning of the File Section portion, including the first four lines of information for an\nopen QSAM file:\n   ****************                                                                \n   * FILE SECTION  *                                                                \n   ****************                                                                \n  \n  [A] DDNAME=PRINT      DSORG=PS   QSAM   BUFNO=5    UNIT=3390,UCB    VOL=SER=WRKD28  \n    DSN=USER02.PRINT                                             RECFM=FB                    \n  [B] STATUS(OPEN)    USAGE(OUTPUT)           LRECL=120     BLKSIZE=120                 \n  [C] CURRENT FILE STATUS = 00  SUCCESSFUL                                            \n \n 807", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a3dd77335972-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe File Section portion displays the following information:\n[A]\nDisplays the data management control blocks. The data management blocks are interpreted and displayed in\nKEYWORD=value format. This information includes the ddname, data set organization, access method, number\nof buffers allocated, and data set name. For non-VSAM files, the unit type, volser and record format are also\ndisplayed.\n[B]\nIndicates the file's current status (OPEN, CLOSED), usage (INPUT, OUTPUT, etc.), and the record length. For\nnon-VSAM files, the block size is also displayed, while the feedback code, function code, and return code are\ndisplayed for VSAM files.\n[C]\nDisplays the hexadecimal value of the current file status along with a brief description of what it means.\nFor open VSAM files, the VSAM catalog information can be displayed using the VSAMCAT option. This option can be\nspecified as an execution-time override, in the CAIOPTS DD. When the option value is set to ON, the VSAM catalog\ninformation is displayed following the Current File Status field, as shown in the following example:\n   DDNAME=INDEX1 DSORG=KSDS VSAM BUFNO=253                           \n   DSN=USER02.INDEX1                                                          \n   STATUS(OPEN)  USAGE(OUTPUT)     LRECL=240    FDBK=0,FTNCD=0,RC=0  \n   CURRENT FILE STATUS = 00  SUCCESSFUL                                       \n  \n  [A] CLUSTER NAME      USER02.INDEX1                           \n     DATA COMPONENT  USER02.INDEX1.DATA                  \n     INDEX COMPONENT USER02.INDEX1.INDX                  \n  [B] ACTIVITY DATES:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a3dd77335972-1", "text": "[B] ACTIVITY DATES:   \n     CREATION DATE   2007.085    EXPIRATION DATE NEVER SCRATCH       \n  [C] DATASET DEFINITION:   \n     KEY POSITION        128        KEY LENGTH   29              \n     AVERAGE RECORD SIZE 240        MAX RECORD SIZE  240         \n     SHARE OPTIONS   2,3        BUFFER SPACE 4608            \n  [D] ALLOCATION PARAMETERS:    \n     WRITE CHECK     NO  ERASE ON DELETE NO              \n     REUSE OPTION        NO  SPANNED RECORDS NO              \n     REPLICATED INDEX    NO  \n  [E] DATA COMPONENT INFORMATION:  F    INDEX COMPONENT INFORMATION:    \n     VOLUME      OSI006          OSI006          \n     ALLOCATION UNIT TRACKS          TRACKS          \n     PRIMARY ALLOCATION  4           1               \n     SECONDARY ALLOCATION    1           1               \n     EXTENTS USED        1           1               \n     HIGH ALLOCATED RBA  147456          23552           \n     HIGH USED RBA   0           0               \n     CI SIZE     2048            512             \n  [G] STATISTICS:   \n     RECORDS RETRIEVED   0   RECORDS DELETED 0               \n     RECORDS INSERTED    0   RECORDS UPDATED 0               \n     TOTAL RECORDS   250 \n \nThe following information is displayed for open VSAM files:\n 808", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a9cbe6198354-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n[A]\nDisplays the data set names of the cluster and data components. For KSDS files, the data set name of the index\ncomponent is also displayed.\n[B]\nDisplays the date on which the file was created and the date on which it may be deleted. The dates are displayed\nin Julian format (YYYY.DDD). If the expiration date is displayed as Never Scratch , the PURGE parameter is\nalways required to delete the file.\n[C]\nDisplays the key position and length, the average and maximum lengths of the data records, the share options,\nand the minimum buffer space allocated when the file is accessed.\nThe key position and length are only displayed for KSDS files and\nvariable-length RRDS files. The key position value indicates the position of the key relative to the start of the\nrecord. For alternate index files, the key position and length refer to the alternate key within the base cluster.\nOtherwise, they refer to the prime key within the base cluster.\n[D]\nIndicates whether or not the file was allocated using the WRITECHECK, ERASE, REUSE, SPANNED, and\nREPLICATE parameters.\n[E]\nDisplays information about the volume on which the file is allocated, the allocation unit (tracks or cylinders), the\nprimary and secondary allocation amounts, the number of extents used, the highest allocated and highest used\nrelative byte address, and the size of the control interval.\n[F]\nDisplays information for the same fields described under E. This information is displayed only for KSDS files.\n[G]\nDisplays the number of times data records are retrieved, deleted, inserted, or updated since the initial load of the\nfile, as well as the total number of data records in the file.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a9cbe6198354-1", "text": "file, as well as the total number of data records in the file.\nThe contents of the current logical record are displayed following the Current File Status field or, if the file is VSAM and\nthe VSAMCAT option is ON, following the VSAM catalog information. The contents of the previous record may also be\ndisplayed for sequentially accessed files. For keyed VSAM files, the VSAM key value is displayed prior to the contents of\nthe record. Symbolic information may be merged with the current record data (as shown in the following screen), if it is\navailable.\n                  CURRENT LOGICAL KEY                                            \n  [A] \n LINE#   LEVEL/FIELD NAME                VALUE/LOCATION                                         DEFINITION  \n ------  ------------------------------  ---------------------------------------    \n ------------------------------------------- \n 000158  20 IX-FS1-KEY                   * ABCDLKJXYZ000000250ZIF,.$-+CD*            X(29)   \n  \n                   CONTENTS OF CURRENT LOGICAL RECORD                             \n  [B]                ----------------------------------                             \n LINE#   LEVEL/FIELD NAME                VALUE/LOCATION                                         DEFINITION  \n ------  -----------------------------   ----------------------------------------   \n ------------------------------------------- \n 000094  01 IX-FS1R1-F-G-240              BLF=0002+000000  (0000F078)        \n 000095  03 IX-FS1-WRK-120               *FILE=IX-FS1,RECORD=IX-F-G/0,RECN*          X(120)  \n                                   (+000032)     *O=000250,UPDT=00,ODO=0000,PGM=IX*  \n                                   (+000064)     *101,LRECL=000240,BLKSIZRC=0001,L*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a9cbe6198354-2", "text": "(+000096)     *FIL=000500,ORG=IX,LBLR=S*          \n 000096  03 IX-FS1-GRP-120                BLF=0002+000078  (0000F0F0)        \n 809", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "06b8fbc680b1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 000097  05 FILLER                       *,RECKEY=*                                          X(8)    \n 000098  05 IX-FS1-KEY                   *ABCDLKJXYZ000000250ZIF,.$-+CD*             X(29)   \n 000099  05 FILLER                       *,ALTKEY1=                                    *     X(83)   \n                                   (+000032)     *   ,ALTKEY2=                               *   \n                                   (+000064)     *                            *                               \n                                      \n  \n                     PREVIOUS KEY                                                \n  [C]                    ------------                                                \n                          LENGTH 0000001D  (DECIMAL 29)                          \n           OFFSET                                                         \n           +000000  C1C2C3C4  D3D2D1E7  E8E9F0F0  F0F0F0F0     F2F4F9E9   C9C66B4B  5B604EC3  C4         \n *ABCDLKJXYZ000000249ZIF,.$-+CD*\n  \n                  CONTENTS OF PREVIOUS RECORD                              \n                  ---------------------------                             \n                              LENGTH 000000F0  (DECIMAL 240)                         \n           OFFSET                                                         \n           +000000  C6C9D3C5  7EC9E760  C6E2F16B  D9C5C3D6     D9C47EC9  E760C660  C761F06B  D9C5C3D5  \n *FILE=IX-FS1,RECORD=IX-F-G/0,RECN*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "06b8fbc680b1-1", "text": "*FILE=IX-FS1,RECORD=IX-F-G/0,RECN*\n           +000020  D67EF0F0  F0F2F4F9  6BE4D7C4  E37EF0F0     6BD6C4D6  7EF0F0F0  F06BD7C7  D47EC9E7  \n *O=000249,UPDT=00,ODO=0000,PGM=IX*\n           +000040  F1F0F16B  D3D9C5C3  D37EF0F0  F0F2F4F0     6BC2D3D2  E2C9E9D9  C37EF0F0  F0F16BD3  \n *101,LRECL=000240,BLKSIZRC=0001,L*  \n           +000060  C6C9D37E  F0F0F0F5  F0F06BD6  D9C77EC9     E76BD3C2  D3D97EE2  6BD9C5C3  D2C5E87E  \n *FIL=000500,ORG=IX,LBLR=S,RECKEY=*  \n           +000080  C1C2C3C4  D3D2D1E7  E8E9F0F0  F0F0F0F0     F2F4F9E9  C9C66B4B  5B604EC3  C46BC1D3  \n *ABCDLKJXYZ000000249ZIF,.$-+CD,AL*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "06b8fbc680b1-2", "text": "*ABCDLKJXYZ000000249ZIF,.$-+CD,AL*  \n           +0000A0  E3D2C5E8  F17E4040  40404040  40404040     40404040  40404040  40404040  40404040  \n *TKEY1=                                   *   \n           +0000C0  4040406B  C1D3E3D2  C5E8F27E  40404040     40404040  40404040  40404040  40404040   * \n  ,ALTKEY2=                            *  \n           +0000E0  40404040  40404040  40404040  40404040                                                   *\n                 *     \n \nThe following information is displayed for the current logical record and the previous record:\n[A]\nDisplays the current logical key data only for VSAM files with defined keys (i.e. KSDS and variable-length\nRRDS files). If the MRGFILES option is on, the data may be displayed in merged format. Otherwise, the data is\ndisplayed in dump format.\n[B]\nDisplays the contents of the current logical record using the following options:\n\u2022If the FIRST128 option is specified, only the first 128 bytes of the record are displayed.\n\u2022If the MRGFILES option is specified, the data is displayed in merged format. Otherwise, the data is displayed\nin dump format.\n[C]\nDisplays previous record data for sequentially accessed files (VSAM, QSAM, and BSAM), if it is available in an I/\nO buffer and:\n 810", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "94841be6f5fa-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022The file is not a BSAM file using NOTE/POINT\n\u2022The file is not a VSAM file using skip-sequential access\n\u2022The file is not a JES managed data set, such as in-stream data or data written to a SYSOUT class\n\u2022The file does not contain unformatted, spanned, compressed, or extended records\nFor keyed VSAM files, the previous record key is displayed prior to the contents of the previous record.\nUse the Data Management Control Block options (DEB, DCB, UCB, and IOB) or VSAM Control Block options (ACB,\nAMBL, AMB, PLH, and RPL) to dump control blocks after the record data display. To dump all of the control blocks,\nspecify the BLOCKS option. These options may be specified as execution-time overrides, in the CAIOPTS DD.\nThe following example shows the Data Management Control Blocks for a QSAM file displayed in hexadecimal format.\n                  DATA MANAGEMENT CONTROL BLOCKS                           \n                  ------------------------------                           \n  \n DEB      007C2D84     LENGTH 00000088  (DECIMAL 136)                      \n            OFFSET                                                         \n           +000000  037C4E88  10000000  E8000000  0F001100     01000000  FF000000  8F00D038  047C2D60\n           +000020  187CED48  00000002  00030002  00030001     00010001  00000000  00000000  00000079", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "94841be6f5fa-1", "text": "+000040  F3C2C1D9  C1C90000  00000000  00000000     00000000  00000000  00000000  00000000   \n           +000060  00000000  00540002  007C7808  00001BE2     00000000  02002000  00000000  00000000\n           +000080  007AD998  C4E2C3C2                                       \n  \n DCB      0000D038     LENGTH 00000060  (DECIMAL 96)                       \n            OFFSET                                                         \n           +000000  22A8CA50  00000000  00020003  13F53026     002FAB98  05018FE8  00004000  00006C08\n           +000020  C6000001  840138B4  00A40048  007C2D84     92D8C2C0  00D8BE70  0A01272A  02090079\n           +000040  30013030  00006DB8  22ABAFF9  22ABAFF9     00000079  00000000  00000000  00E6E470  \n  \n UCB      007CED48     LENGTH 00000040  (DECIMAL 64)                             \n            OFFSET                                                               \n           +000000  01A8FF8C  2D050000  00000000  08E4C3C2     3030200F  00229D21  5DC00100  E6D9D2C4", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "94841be6f5fa-2", "text": "+000020  F2F51001  00A00014  02229B48  02233188     05800101  00000000  40688072  20C69F40 \n  \n IOB      00006C08     LENGTH 00000050  (DECIMAL 80)                             \n            OFFSET                                                               \n           +000000  7F000000  007C1BD0  00006C78  80006DB8     00006C78  04040004  00000000  00000000\n           +000020  00000000  00000000  00000000  00000000     00000000  00000000  00000000  00000000\n           +000040  00000000  00000000  00000000  00000000                           \n \nWorking-Storage Section, Local-Storage Section, Linkage Section Displays\nThe abend report displays the Working-Storage Section, Local-Storage Section, and the Linkage Section. An example of\na Linkage Section Display follows:\n  *******************\n  * LINKAGE SECTION  *\n  *******************\n  \n  LINE#   LEVEL/FIELD NAME                      VALUE/LOCATION                           DEFINITION  \n  ------  -----------------------------  --------------------------------   \n -------------------------------------   \n  000399  01 PARMS                               BLL=0001+000000  (36310E68) \n 811", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0b2dde0951b1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  000400  03 PARM-LENGTH                         +1                                          S9(4) BINARY    \n  000401  03 PARM-DATA                       ? X'E8'                                     X(12)   \n  \n  LINE#   LEVEL/FIELD NAME                      VALUE/LOCATION                           DEFINITION  \n  ------  ----------------------------       --------------------------------   \n -------------------------------------   \n  001353  01 INPUT-PARM                         BLL=0002+000000  (365864B0)\n  001354  03 INPUT-PARM-LENGTH                +1                                         S9(4) BINARY    \n  001355  03 INPUT-PARM-DATA                 ? X'B38C00000000000000000000'           X(12)   \n \nIf the MRGWORK (for Working-Storage), MRGLOCAL (for Local-Storage), and MRGLINK (for Linkage Section) options\nare ON, the data is displayed in merged format. Otherwise, it is displayed in dump format.\nFor more information about the merged and dumped data formats, see Merged Versus Dumped Data Display.\nRegister Contents\nThe registers at abend portion of the abend report displays the general registers, floating-point registers and vector\nregisters for the abending program:\n  **********************\n  * REGISTERS AT ABEND *\n  **********************\n  [A] \n  GENERAL REGISTERS:\n  \n  R0     36586520    DISP +A99B50 IN BLL 0002    \n  R1     365864A8    DISP +000478 IN DSA \n  R2     0001D0B8    DISP +000000 IN BLW 0000", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0b2dde0951b1-1", "text": "R3     000360B8    DISP +000000 IN BLW 0019    \n  R4     00000002    \n  R5     B630409E    DISP +003796 IN PROGRAM CAOEDEMO    \n  R6     36301C76    DISP +00136E IN PROGRAM CAOEDEMO    \n  R7     00000000    \n  R8     000340B8    DISP +000000 IN BLW 0017    \n  R9     0001B038    DISP +000000 IN TGT \n  R10    36300A70    DISP +00006C IN PGT \n  R11    3630456E    DISP +003C66 IN PROGRAM CAOEDEMO    \n  R12    36300A04    DISP +000000 IN PGT \n  R13    36586030    DISP +000000 IN DSA \n  R14    B6301CE0    DISP +0013D8 IN PROGRAM CAOEDEMO    \n  R15    00000000    \n  \n  [B] \n  FLOATING-POINT REGISTERS:\n  \n  FPC    00000000    \n  FR0    493202EA    E0000000  1.342483 E+10      FR8    00000000  00000000  0.0 \n  FR1    00000000    00000000  0.0                FR9    00000000  00000000  0.0 \n  FR2    4E000000    03923FD1  5.991624 E+07      FR10   00000000  00000000  0.0", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0b2dde0951b1-2", "text": "FR3    00000000    00000000  0.0                FR11   00000000  00000000  0.0 \n  FR4    4E000000    00025EF4  155380             FR12   00000000  00000000  0.0 \n  FR5    00000000    00000000  0.0                FR13   00000000  00000000  0.0 \n 812", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "79b8d26ecc96-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  FR6    00000000    00000000  0.0                FR14   00000000  00000000  0.0 \n  FR7    00000000    00000000  0.0                FR15   00000000  00000000  0.0\n  \n  \n  [C] \n VECTOR REGISTERS: \n \n VR0 493202EA E0000000 00000000 00000000   VR16 00000000 00000000 00000000 00000000\n VR1 00000000 00000000 00000000 00000000   VR17 00000000 00000000 00000000 00000000\n VR2 4E000000 03923FD1 00000000 00000000   VR18 00000000 00000000 00000000 00000000\n VR3 00000000 00000000 00000000 00000000   VR19 00000000 00000000 00000000 00000000\n VR4 4E000000 00025EF4 00000000 00000000   VR20 00000000 00000000 00000000 00000000\n VR5 00000000 00000000 00000000 00000000   VR21 00000000 00000000 00000000 00000000\n VR6 00000000 00000000 00000000 00000000   VR22 00000000 00000000 00000000 00000000", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "79b8d26ecc96-1", "text": "VR7 00000000 00000000 00000000 00000000   VR23 00000000 00000000 00000000 00000000\n VR8 00000000 00000000 00000000 00000000   VR24 00000000 00000000 00000000 00000000\n VR9 00000000 00000000 00000000 00000000   VR25 00000000 00000000 00000000 00000000\nVR10 00000000 00000000 00000000 00000000   VR26 00000000 00000000 00000000 00000000\nVR11 00000000 00000000 00000000 00000000   VR27 00000000 00000000 00000000 00000000\nVR12 00000000 00000000 00000000 00000000   VR28 00000000 00000000 00000000 00000000\nVR13 00000000 00000000 00000000 00000000   VR29 00000000 00000000 00000000 00000000\nVR14 00000000 00000000 00000000 00000000   VR30 00000000 00000000 00000000 00000000\nVR15 00000000 00000000 00000000 00000000   VR31 00000000 00000000 00000000 00000000\n \nThe registers at abend portion displays the following information:\n[A]\nDisplays the base address and displacement if the contents of a general register can be related directly to a base\naddress and displacement.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "79b8d26ecc96-2", "text": "address and displacement.\nFor COBOL II, COBOL/370, COBOL for MVS and VM, COBOL for OS/390 and VM, or Enterprise COBOL for z/\nOS and OS/390, the base addresses may appear as the following:\nBLF nnnn Base Locator for FILE Section\nBLW nnnn Base Locator for WORKING-STORAGE Section\nBLL nnnn Base Locator for LINKAGE Section\nBLK nnnn Base Locator for LOCAL-STORAGE Section\nBLX nnnn Base Locator for externally located data\nprogname Signature code that starts at relative location 0 of the program\nTGT Task Global Table\nPGT Program Global Table\nDSA Dynamic Save Area\nFor OS/VS COBOL the base address may appear as:\n BL\n BLL\n INIT1\n TGT\n \nA blank line following the general register display indicates that the origin of the register contents cannot be determined.\n 813", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "21e5ec67ded3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n[B]\nDisplays the floating-point control register and floating-point registers 0 through 15 if the basic floating-point\nextensions of z/OS are installed on your system. Otherwise, the floating-point registers 0, 2, 4, and 6 are\ndisplayed (as shown).\n[C]\nDisplays the vector registers 0 through 31 if the vector facility for z/Architecture is installed on your system.\nMemory Map Display\nThe following section displays the memory map, which consists of the TGT, PGT, and for some releases of COBOL, the\nDSA. For COBOL II or COBOL/370, the PGT display includes the Constant Global Table (CGT). For COBOL for MVS and\nVM, COBOL for OS/390 and VM, and Enterprise COBOL for z/OS and OS/390, the display includes the DSA. To interpret\nthe Memory Map Display, see the listing of the memory maps printed after the compiler source listing.\n  **************\n  * MEMORY MAP *\n  **************\n  DSA      36586030     LENGTH 000004F0  (DECIMAL 1,264)\n  ADDRESS  OFFSET\n  36586030 000000   00104001 36313360 00000000 B6301CE0   00000000 36586520 365864A8 000157FC  \n *.. ....-.......\\...........y....*\n  36586050 000020   0001B38C 00000000 B630409E 36301C76   00000000 000340B8 0001B038 36300A70  \n *.......... ........... .........*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "21e5ec67ded3-1", "text": "*.......... ........... .........*\n  36586070 000040   3630456E 36300A04 00000000 36586520   00000000 00000000 36586030 0001B038  \n *...>......................-.....*\n  36586090 000060   00000000 00000000 00000000 00000000   00000000 00000000 00000000 00000000  \n *................................*\n  365860B0 000080   00000000 21000000 00000003 00000000   B6301CE0 00000000 36586520 365864A8  \n *...................\\...........y*\n  365860D0 0000A0   36304214 363041F8 00000002 B630409E   36301C76 00000000 000340B8 0001B038  \n *.......8...... ........... .....*\n  365860F0 0000C0   36300A70 00000000 00000000 00000000   00000000 00000000 00000000 00000000  \n *................................*\n  36586110 0000E0   00000000 00000000 00000000 00000000   00000000 00000000 00000000 00000000  \n *................................*\n                   LINES 00000100-00000140 SAME AS ABOVE\n     .\n     .\n     .\n  TGT      0001B038     LENGTH 000003E8  (DECIMAL 1,000)\n  ADDRESS  OFFSET", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "21e5ec67ded3-2", "text": "ADDRESS  OFFSET\n  0001B038 000000   00000000 00000000 00000000 00000000   00000000 00000000 00000000 00000000  \n *................................*\n  0001B058 000020   00000000 00000000 00000000 00000000   00000000 00000000 00000000 00000000  \n *................................*\n  0001B078 000040   00000000 00000000 F3E3C7E3 00000000   06000000 64020260 36582100 000157FC  \n *........3TGT...........-........*\n  0001B098 000060   0001B420 00000001 00084927 00000000   00000000 0001B930 00000000 00000000  \n *................................*\n  0001B0B8 000080   363129C0 000003E8 00000000 00000000   00000002 00000005 E2E8E2D6 E4E34040   *...\n{...Y................SYSOUT  *\n  0001B0D8 0000A0   C9C7E9E2 D9E3C3C4 00000000 00000000   00000000 00000000 00000000 00000000  \n *IGZSRTCD........................*\n 814", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "26a63aa844f8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  0001B0F8 0000C0   00000000 00000000 00000000 00000000   00000000 00000000 00000000 00000000  \n *................................*\n  0001B118 0000E0   00000000 00000000 36300A04 00000000   0001B3BC 365823F0 36301107 00000000  \n *.......................0........*\n     .\n     .\n     .\n  PGT      36300A04     LENGTH 00000A60  (DECIMAL 2,656)\n  ADDRESS  OFFSET\n  36300A04 000000   05F5E100 3B9ACA00 000186A0 00002710   00000001 00000000 40404040 40404040  \n *.5........f.............        *\n  36300A24 000020   40404040 40404040 40404040 40404040   40404040 40400000 00000000 00000000   *            \n          ..........*\n  36300A44 000040   00000000 000C0000 0000000C 0000000F   F0F0F0F0 F0C00000 36300A70 36301504  \n *................00000{..........*\n  36300A64 000060   36302556 36303564 3630456E 36301552   3630183C 36301DFC 363020EA 36302196  \n *...........>...................o*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "26a63aa844f8-1", "text": "*...........>...................o*\n  36300A84 000080   36302376 36302556 363025F2 3630276C   363028F0 36302A46 36302AC4 36302C0A  \n *...........2...%...0.......D....*\n  36300AA4 0000A0   36302C28 36302E0E 36302EC0 36302F14   36303068 363030AE 363036E8 363036A4   *...........\n{...............Y...u*\n  36300AC4 0000C0   36303B68 36303C12 363040B2 36303CB2   36303CF6 36303D4A 36303D9E 36303DF2  \n *.......... ........6...\u00a2.......2*\n  36300AE4 0000E0   36303E46 36303E9A 363037E6 3630385C   36303914 363039DC 36303A22 36303A76  \n *...........W...*................*\n \nPL/I Reports\nThis section describes the information provided for PL/I programs.\nProgram Statistics\nFor each program in the report, this report contains statistics about the compile, link, and symbolic postprocessing used\nwhen the program was built.\n ********************\n * PROGRAM PLITEST1 *\n ********************\n  [A] \n COMPILED ON 20 APR,2004 AT 11.49.52 WITH PL/I FOR Z/OS 3.2.0\n  [B] \n SYMBOLIC INFORMATION RETRIEVED FROM CDE.DEVL.SB21.PROTSYM", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "26a63aa844f8-2", "text": "SYMBOLIC INFORMATION RETRIEVED FROM CDE.DEVL.SB21.PROTSYM\n MEMBER: PLITEST   DATE: 20 APR,2004  TIME: 11.49.52   TYPE: PROTSYM\n  [C] \n LINKED ON 20 APR 2004 AT 11:49:58\n LOAD LIBRARY: USER001.LOAD\n MODULE LENGTH: 000047C0  (DECIMAL 18,368)\n \nThe program statistics include the following information:\n 815", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9ce664816ae4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n[A]\nDisplays compile statistics, including the date and time of compilation, the compiler and release information, and\nthe options used.\n[B]\nWhen symbolic information is used to format the report, this section displays the name of the symbolic file and the\ndate and time of the symbolic listing used.\n[C]\nDisplays link-edit information including the date and time when the load module was created, the name of the load\nlibrary from which the program was loaded, the length of the module, and the linkage editor options used.\nActive Procedures\nWhen one or more PL/I programs are active at the time of an ABEND, SymDump  Batch reports on each active PL/I\nprocedure. The information provided for each procedure includes the following:\n\u2022Variables defined to the procedure\n\u2022Registers when last in control\n\u2022Dynamic Save Area (DSA)\nVariables\nThe following sample report shows the variable display for an active PL/I procedure:\n *************\n * VARIABLES *\n *************\n  \n DCL#    LVL FIELD NAME                          VALUE/LOCATION                      ATTRIBUTES  \n ------  --- ------------------------    -------------------------------------- \n --------------------------------------  \n 000365      PIC_INIT              ?     X'00000000000000000000000000000000'     AUTOMATIC CHARACTER(31) \n                                     (+000016)   X'000000000000000000000000000000'   \n 000368      01 TTP                         ADDRESS=12268BD1                     STRUCTURE AUTOMATIC \n 000368      02 TTPT                                 *  PPPP TABLE TP   PPPP                 *   CHARACTER(32)\n   \n 000368      02 TP_PICTURE_TABLE(1)         ADDRESS=12268BF1                     STRUCTURE DIM(18)   \n 000368      03 TPICTURE(1)                          **                                          CHARACTER(31)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9ce664816ae4-1", "text": "000368      03 TPICTURE(1)                          **                                          CHARACTER(31)\n VARYING   \n 000368      03 TDEC(1)                         ?    X'0000'                                     FIXED\n DECIMAL(3)    \n 000368      03 TBIN(1)                              +0                                          FIXED\n BINARY(15)    \n           <UNMERGED DATA FOR TP_PICTURE_TABLE>\n                                                 X'00000000000000000000000000000000'     LENGTH  646 \n                                                    LINES 000016-000624 SAME AS ABOVE    \n                                        (+000640)    X'000000000000' \n 000375      TTP2(1)                             +0                                          AUTOMATIC DIM(18)\n FIXED BINARY(15)  \n           <UNMERGED DATA FOR TTP2>              X'00000000000000000000000000000000'     LENGTH  34  \n                                        (+000016)    X'00000000000000000000000000000000' \n                                        (+000032)    X'0000' \n \n 816", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a855180b5898-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nVariable storage displays information in merged format or in dump format, depending on your option settings. The\nfollowing options control merging for PL/I variables:\n\u2022MRGAUTO -- Merges symbolic names onto PL/I automatic storage.\n\u2022MRGBASED -- Merges symbolic names onto PL/I based variable storage.\n\u2022MRGCNTLD -- Merges symbolic names onto PL/I controlled storage.\n\u2022MRGPARMS -- Merges symbolic names onto PL/I parameter storage.\n\u2022MRGSTAT -- Merges symbolic names onto PL/I static storage.\nFor more information about the merged and dumped data formats, see Merged Versus Dumped Data Displays.\nRegisters\nFor each procedure, the values of the general-purpose registers at the time when the procedure was last in control are\ndisplayed.\nFor abending procedures, these are the current register values, and the floating-point and vector registers are also\nincluded. For all other procedures, these are the registers when the procedure last transferred control to another\nprocedure or program.\nThe following sample report shows the PL/I procedure registers:\n **********************\n * REGISTERS AT ABEND *\n **********************\n  \n GENERAL REGISTERS:\n  \n R0   12268EA0\n R1   122683C8\n R2   00000024\n R3   12102D9A   DISP +00003A IN PROCEDURE INIT_TP   \n R4   00000000\n R5   121035E8   DISP +000000 IN STATIC  \n R6   12102FD8   DISP +000278 IN PROCEDURE INIT_TP   \n R7   00000001\n R8   000002CC\n R9   1228A868\n R10 12103604    DISP +00001C IN STATIC", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a855180b5898-1", "text": "R10 12103604    DISP +00001C IN STATIC  \n R11 122683C8\n R12 12113650\n R13 12268A78    DISP +000000 IN DSA \n R14 12268EA0\n R15 92102EF0    DISP +000190 IN PROCEDURE INIT_TP   \n  \n FLOATING-POINT REGISTERS:\n  \n FPC F0000000\n FR0 41100000 00000000  1.0            FR8  00000000 00000000  0.0   \n FR1 00000000 00000000  0.0            FR9  00000000 00000000  0.0   \n FR2 34000000 00000000  0.0            FR10 00000000 00000000  0.0   \n FR3 00000000 00000000  0.0            FR11 00000000 00000000  0.0   \n FR4 5B4EE2D6 D415B85A  1.0 E+32       FR12 00000000 00000000  0.0   \n FR5 00000000 00000000  0.0            FR13 00000000 00000000  0.0   \n FR6 4DCEF810 00000000  3.641037 E+15  FR14 00000000 00000000  0.0\n 817", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "580a73329ef6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n FR7 00000000 00000000  0.0            FR15 00000000 00000000  0.0\n  \n VECTOR REGISTERS: \n \n VR0 41100000 00000000 00000000 00000000   VR16 00000000 00000000 00000000 00000000\n VR1 00000000 00000000 00000000 00000000   VR17 00000000 00000000 00000000 00000000\n VR2 34000000 00000000 00000000 00000000   VR18 00000000 00000000 00000000 00000000\n VR3 00000000 00000000 00000000 00000000   VR19 00000000 00000000 00000000 00000000\n VR4 5B4EE2D6 D415B85A 00000000 00000000   VR20 00000000 00000000 00000000 00000000\n VR5 00000000 00000000 00000000 00000000   VR21 00000000 00000000 00000000 00000000\n VR6 4DCEF810 00000000 00000000 00000000   VR22 00000000 00000000 00000000 00000000\n VR7 00000000 00000000 00000000 00000000   VR23 00000000 00000000 00000000 00000000", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "580a73329ef6-1", "text": "VR8 00000000 00000000 00000000 00000000   VR24 00000000 00000000 00000000 00000000\n VR9 00000000 00000000 00000000 00000000   VR25 00000000 00000000 00000000 00000000\nVR10 00000000 00000000 00000000 00000000   VR26 00000000 00000000 00000000 00000000\nVR11 00000000 00000000 00000000 00000000   VR27 00000000 00000000 00000000 00000000\nVR12 00000000 00000000 00000000 00000000   VR28 00000000 00000000 00000000 00000000\nVR13 00000000 00000000 00000000 00000000   VR29 00000000 00000000 00000000 00000000\nVR14 00000000 00000000 00000000 00000000   VR30 00000000 00000000 00000000 00000000\nVR15 00000000 00000000 00000000 00000000   VR31 00000000 00000000 00000000 00000000\n \nDynamic Save Area\nFor each procedure, the Dynamic Save Area (DSA) is also displayed:\n *********************\n * DYNAMIC SAVE AREA *\n *********************\n  \n DSA      12268A78     LENGTH 00000158  (DECIMAL 344)\n ADDRESS  OFFSET", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "580a73329ef6-2", "text": "ADDRESS  OFFSET\n 12268A78 000000   10000000 122683C8 00000000 92102E3C   9219A6C8 1210326C 12268B10 00000000  \n *......cH....k...k.wH...%........*\n 12268A98 000020   12102D9A 12268B48 121035E8 12102FD8   00000001 12268B4C 1228A868 12103604  \n *...........Y...Q.......<..y.....*\n 12268AB8 000040   122683C8 00000000 00000000 12268EC8   00000000 00000000 00000000 00000000  \n *..cH...........H................*\n 12268AD8 000060   00000000 00000000 00000000 00000000   00000000 00000000 00000000 00000000  \n *................................*\n 12268AF8 000080   00000000 00000000 00000000 00000000   00000000 00000000 12268B4C 12268B48  \n *...........................<....*\n 12268B18 0000A0   12268B60 1210326C 00000000 00000000   00000000 00000000 00000000 00000000   *...-...\n%........................*\n 12268B38 0000C0   00000000 00000000 12268EA0 12268BD1   00000001 000002CB 00000002 00000002", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "580a73329ef6-3", "text": "*...............J................*\n 12268B58 0000E0   00000012 00000001 00000000 00200002   00000020 00000026 00000026 00000012  \n *................................*\n 12268B78 000100   00000001 001F8002 00000041 00000026   00000026 00000012 00000001 00000043  \n *................................*\n 12268B98 000120   00000026 00000026 00000012 00000001   00000000 00000000 122683C8 12268460  \n *..........................cH..d-*\n 818", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d7b105bd9aaa-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 12268BB8 000140   00000000 00000000 00000000 00000000   0000001C 00000000                          \n *........................*\n \nStorage\nAfter all of the active procedures are reported, the program storage is displayed. This includes both static and external\nprogram storage areas.\nStatic Storage\nStatic storage is displayed in dump format as shown in the following screen:\n ***********\n * STORAGE *\n ***********\n  \n ******************\n * STATIC STORAGE *\n ******************\n STATIC   121035E8     LENGTH 000003B4  (DECIMAL 948)\n ADDRESS  OFFSET\n 121035E8 000000   12103CB8 121036AC 12103CB8 121036C4   1228A6F8 1228A748 1228A800 1228A848  \n *...............D..w8..x...y...y.*\n 12103608 000020   1228A8A8 1228A540 1228A1E8 1228A2C0   00000000 00008000 00000002 00050002  \n *..yy..v ..~Y..s{................*\n 12103628 000040   00060002 00000000 00000000 00000000   00000000 00000000 02060000 00000004  \n *................................*\n 12103648 000060   02020240 00000005 02040240 00000005   0206FF00 00000004 02040240 00000007  \n *... ....... ............... ....*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d7b105bd9aaa-1", "text": "*... ....... ............... ....*\n 12103668 000080   02020240 0000004C 00000000 00030002   00000003 00000005 00800080 00000000  \n *... ...<........................*\n 12103688 0000A0   00000001 0C008400 00000050 00000000   00000001 00000001 00000008 00000001  \n *......d....&....................*\n 121036A8 0000C0   00010000 12289D7C 00000801 00600602   12102FD8 12103680 121036AC 1228A1AC  \n *.......@.....-.....Q..........~.*\n 121036C8 0000E0   00444042 00A3AE01 12102FE0 00000000   00000000 C5D9D9D6 D940C3D6 D5C4C9E3   *.. ..t.....\n\\........ERROR CONDIT*\n 121036E8 000100   C9D6D540 D9C1C9E2 C5C44040 40000000   0000000C 0000000A 00000005 00000001   *ION RAISED \n  ...................*\n 12103708 000120   00000002 00000005 00000001 D1C1D5C6   C5C2D4C1 D9C1D7D9 D4C1E8D1 E4D5D1E4  \n *............JANFEBMARAPRMAYJUNJU*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d7b105bd9aaa-2", "text": "*............JANFEBMARAPRMAYJUNJU*\n 12103728 000140   D3C1E4C7 E2C5D7D6 C3E3D5D6 E5C4C5C3   D0000328 00100000 6E3BFFE0 00000000  \n *LAUGSEPOCTNOVDEC}.......>..\\....*\n 12103748 000160   00000000 00000000 00000000 90010000   12102FEC 00000000 00000000 00000000  \n *................................*\n 12103768 000180   00000000 00000000 00000000 00200002   00000020 00000026 00000026 00000001  \n *................................*\n 12103788 0001A0   00000001 001F8002 00000041 00000026   00000026 00000001 00000001 00000043  \n *................................*\n 121037A8 0001C0   00000026 00000026 00000001 00000001   00000000 000A0002 0000000A 0000000D  \n *................................*\n 121037C8 0001E0   0000000F 00010000 0000000F 00020001   00000010 00000009 00000009 00000003  \n *................................*\n 819", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c01aec2c458e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 121037E8 000200   00000001 00000013 00000009 00000009   00000003 00000001 00060002 0000002B  \n *................................*\n 12103808 000220   00000004 00000003 00000002 00000001   00000001 00000003 00000001 00010002  \n *................................*\n 12103828 000240   00000000 000A0002 0000000A 0000000D   0000000F 00010000 0000000F 00020001  \n *................................*\n 12103848 000260   00000010 00000008 00000008 00000001   00000001 00000013 00000008 00000008  \n *................................*\n 12103868 000280   00000001 00000001 00000017 00000002   00000001 00000001 00000001 00000001  \n *................................*\n 12103888 0002A0   00000001 00000001 00010002 00000018   00040002 00000000 00000000 000A0002  \n *................................*\n 121038A8 0002C0   0000000A 0000000D 0000000F 00010000   0000000F 00020001 00000010 00000008  \n *................................*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c01aec2c458e-1", "text": "*................................*\n 121038C8 0002E0   00000008 00000001 00000001 00000013   00000008 00000008 00000001 00000001  \n *................................*\n 121038E8 000300   00000017 00000002 00000001 00000001   00000001 00000001 00000001 00000001  \n *................................*\n 12103908 000320   00010002 00000018 00040002 00000000   00000000 000A0002 0000000A 0000000D  \n *................................*\n 12103928 000340   0000000F 00010000 0000000F 00020001   00000010 0000000F 0000000F 00000003  \n *................................*\n 12103948 000360   00000001 00000013 00000015 0000000F   00000003 00000001 00000006 00000002  \n *................................*\n 12103968 000380   00000001 00060002 0000003D 00000004   00000003 00000002 00000001 00000001  \n *................................*\n 12103988 0003A0   00000003 00000001 00010002 00000043   00040002                                      \n *....................*\n \nExternal Storage\nEach external storage definition is displayed separately as shown in the following screen:\n ********************\n * EXTERNAL STORAGE *\n ********************\n  [A] [B] [C]", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c01aec2c458e-2", "text": "* EXTERNAL STORAGE *\n ********************\n  [A] [B] [C] \n EXTEATA       121039A0        LENGTH 00000015  (DECIMAL 21) \n ADDRESS       OFFSET    \n 121039A0      000000 [D]  C5E7E3C5 D9D5C1D3 0000001C 00000000   00000000 00              \n *EXTERNAL.............* \n  \n EXTETAX       121039B8        LENGTH 00000015  (DECIMAL 21) \n ADDRESS    OFFSET\n 121039B8      000000    00C5E7E3 C5D9D5C1 D300002C 00000000   00000000 00                      \n *.EXTERNAL............* \n  \n CNTLAR2       121039D0        LENGTH 00000004  (DECIMAL 4)  \n ADDRESS       OFFSET    \n 121039D0      000000    1228A728                                                                       \n *..x.*  \n  \n 820", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f95638e7d7c5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n CNTLAR4       121039D8        LENGTH 00000004  (DECIMAL 4)  \n ADDRESS       OFFSET    \n 121039D8      000000    1228A7C0                                                                       \n *..x{*  \n  \n CNTLTAX       121039E0        LENGTH 00000004  (DECIMAL 4)  \n ADDRESS       OFFSET    \n 121039E0      000000    1228A630                                                                       \n *..w.*  \n  \n CNTLPTR       121039E8        LENGTH 00000004  (DECIMAL 4)  \n ADDRESS       OFFSET    \n 121039E8      000000    1228A248                                                                       \n *..s.*  \n  \n ONE_VAR       121039F0        LENGTH 00000004  (DECIMAL 4)  \n ADDRESS       OFFSET    \n 121039F0      000000    00000000                                                                    *....*  \n  \n ANOTVAR       121039F8        LENGTH 00000004  (DECIMAL 4)  \n ADDRESS       OFFSET    \n 121039F8      000000    00000000                                                                       \n *....*  \n \nThe external storage portion of the report displays the following information:\n[A]\nDisplays the name of the control section created by the PL/I compiler for the external storage area.\n[B]\nDisplays the absolute address of the external storage area.\n[C]\nDisplays the length of the external storage.\n[D]\nIf the external storage display requires more than one line, each line displays the absolute address and the offset\nwithin the external storage for the data on that line.\nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f95638e7d7c5-1", "text": "within the external storage for the data on that line.\nNOTE\nExternal storage is not displayed for programs that have been compiled using Enterprise PL/I for z/OS and\nOS/390 with the RENT option.\nProgram Storage Dump\nAt the end of the formatted displays for each active PL/I program, the program storage is displayed in dump format.\n *******************\n * CSECT  PLITEST1 *\n *******************\n  \n ADDRESS  OFFSET\n 121008C0 000000   F2F0F0F4 F0F4F2F0 F1F1F4F9 F5F2F0F3   F0F2F0F0 00280801 02035B00 079E0000  \n *20040420114952030200......$.....*\n 121008E0 000020   04741F07 1F1F0F00 29612102 018C126C   36000301 0FE81210 35E80000 03B40000  \n *........./.....%.....Y...Y......*\n 821", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "879db928bfe1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 12100900 000040   47F0F022 01C3C5C5 000006B0 000029B0   47F0F001 58F0C31C 184E05EF 00000000  \n *.00..CEE.........00..0C..+......*\n 12100920 000060   07F390EB D00C58E0 D04C4100 E6B05500   C3144130 F03A4720 F01458F0 C28090F0   *.3..}..\n\\}<..W...C...0...0..0B..0*\n 12100940 000080   E0489210 E00050D0 E00418DE 58503FB2   58603FB6 58103F0A 5010D328 41100000   *\\.k.\n\\.&}\\....&...-......&.L.....*\n 12100960 0000A0   5010D32C 58203F0E 5020D330 5010D33C   58103F12 5010D340 41105008 501050DC  \n *&.L.....&.L.&.L.....&.L ..&.&.&.*\n 12100980 0000C0   D21FD300 60429200 D2FC9200 D2F81B11   4310D2F4 54103F16 4210D2F4 1B114310  \n *K.L.-.k.K.k.K8....K4......K4....*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "879db928bfe1-1", "text": "*K.L.-.k.K.k.K8....K4......K4....*\n 121009A0 0000E0   D2F45410 3F1A4210 D2F41B11 4310D2F4   54103F1E 4210D2F4 1B114310 D2F45410  \n *K4......K4....K4......K4....K4..*\n 121009C0 000100   3F224210 D2F41B11 4310D2F4 54103F26   4210D2F4 1B114310 D2F45410 3F2A4210  \n *....K4....K4......K4....K4......*\n 121009E0 000120   D2F41B11 4310D2F4 54103F2E 4210D2F4   1B114310 D2F45410 3F324210 D2F41B11  \n *K4....K4......K4....K4......K4..*\n 12100A00 000140   4310D2F0 54103F16 4210D2F0 1B114310   D2F05410 3F1A4210 D2F01B11 4310D2F0  \n *..K0......K0....K0......K0....K0*\n 12100A20 000160   54103F1E 4210D2F0 1B114310 D2F05410   3F224210 D2F01B11 4310D2F0 54103F26", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "879db928bfe1-2", "text": "*......K0....K0......K0....K0....*\n 12100A40 000180   4210D2F0 1B114310 D2F05410 3F2A4210   D2F04110 D2AC5010 D5049240 1000D23F  \n *..K0....K0......K0..K.&.N.k ..K.*\n 12100A60 0001A0   10011000 5810D504 41106020 58201000   4110D260 50201000 D206D244 606292C6  \n *......N...-.......K-&...K.K.-.kF*\n 12100A80 0001C0   D24B9286 D24C4140 00041814 5010D4EC   1A114120 D24F4180 D24F41A0 6069A71E  \n *K.kfK<. ....&.M.....K|..K|..-.x.*\n 12100AA0 0001E0   000841B0 0008189B 47B03174 18910E8A   5820D4EC 89200010 8A200010 4110D24D  \n *.............j....M.i.........K(*\n 12100AC0 000200   40201000 D208D228 6071D204 D231607A   4110D238 D206D238 607F4110 D2364120  \n * ...K.K.-.K.K.-:..K.K.K.-\"..K...*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "879db928bfe1-3", "text": "* ...K.K.-.K.K.-:..K.K.K.-\"..K...*\n 12100AE0 000220   00074020 1000D202 D21C6086 1B114310   D21F5410 3F365610 3F3A4210 D21F1B11   *.. ...K.K.-\nf....K...........K...*\n 12100B00 000240   4310D21F 54103F3E 56103F42 4210D21F   1B114310 D21F5610 3F464210 D21F4110  \n *..K...........K.....K.......K...*\n 12100B20 000260   D21F5010 D4F01B22 43201000 54203F32   56203F4A 42201000 5810D4F0 1B224320  \n *K.&.M0.............\u00a2......M0....*\n 12100B40 000280   10015420 3F4E5620 3F524220 10014110   D2269254 D2264110 D2244120 00064020   *.....\n+..........K.k.K...K..... .*\n 12100B60 0002A0   1000D206 D1D06089 D204D1D7 6090D205   D1DC6095 D202D1E2 609B4110 60245820   *..K.J}-\niK.JP-.K.J.-nK.JS-...-...*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "879db928bfe1-4", "text": "iK.JP-.K.J.-nK.JS-...-...*\n 12100B80 0002C0   10004110 D1E55020 1000D204 D1E9609E   D204D1EE 609ED204 D1F3609E D208D1F8  \n *....JV&...K.JZ-.K.J.-.K.J3-.K.J8*\n 12100BA0 0002E0   60A3D209 D20160AC D204D20B 60B64110   60285820 10004110 D2105020 1000D207   *-\ntK.K.-.K.K.-...-.......K.&...K.*\n 12100BC0 000300   D21460BB D205D147 60C39201 D14D9203   D14E9205 D14F9209 D1509211 D1519221   *K.-.K.J.-\nCk.J(k.J+k.J|k.J&k.J.k.*\n 12100BE0 000320   D1529241 D1534110 00814010 D1544110   01014010 D1564110 02014010 D1584110  \n *J.k.J....a .J..... .J..... .J...*\n 12100C00 000340   04014010 D15A4110 08014010 D15C4110   0FFF4010 D15EA718 20014010 D160A718  \n *.. .J!.... .J*.... .J;x... .J-x.*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "879db928bfe1-5", "text": "*.. .J!.... .J*.... .J;x... .J-x.*\n 12100C20 000360   40014010 D1625810 3F565010 D1645810   3F5A5010 D1685810 3F5E5010 D16C5810  \n * . .J.....&.J....!&.J....;&.J%..*\n 822", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "611fde759672-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 12100C40 000380   3F625010 D1705810 3F665010 D1745810   3F6A5010 D1785810 3F6E5010 D17C5810  \n *..&.J.....&.J....\u00a6&.J....>&.J@..*\n 12100C60 0003A0   3F725010 D1805810 3F765010 D1845810   3F7A5010 D1885810 3F7E5010 D18C5810  \n *..&.J.....&.Jd...:&.Jh...=&.J...*\n 12100C80 0003C0   3F825010 D1905810 3F865010 D1945810   3F8A5010 D1985810 3F8E5010 D19C5810  \n *.b&.J....f&.Jm....&.Jq....&.J...*\n 12100CA0 0003E0   3F925010 D1A0A718 134A4010 D1A45810   3F965010 D1A84110 003A4010 D1ACA718   *.k&.J.x..\n\u00a2 .Ju...o&.Jy.... .J.x.*\n \nThe program storage dump can be suppressed by program name or prefix using the CAOUXMOD macro in your\ninstallation defaults member, CAOUDFRX. For more information, see SymDump  Batch Options.\nAssembler Reports\nThis section describes the information provided for Assembler programs.\nProgram Statistics", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "611fde759672-1", "text": "Assembler Reports\nThis section describes the information provided for Assembler programs.\nProgram Statistics\nFor each assembler program in the report, this report contains statistics about the assemble, link, and symbolic\npostprocessing used when the program was built.\n ********************\n * PROGRAM CARXDEMA *\n ********************\n  [A] \n ASSEMBLED ON 26 JUN,2007 AT 13.25.00\n  [B] \n SYMBOLIC INFORMATION RETRIEVED FROM AD1DEV.USER001.PROTSYM\n MEMBER: CARXDEMA DATE: 26 JUN,2007 TIME: 13.25.00 TYPE: PROTSYM\n  [C] \n LINKED ON 26 JUN 2007 AT 13:25:22\n LOAD LIBRARY: USER02.LOAD\n MODULE LENGTH: 00000958 (DECIMAL 2,392)\n LINK OPTIONS: AC(0), AMODE(31), NOOVLY, RENT, REUS, RMODE(24)\n \nThe program statistics portion of the assembler reports displays the following information:\n[A]\nDisplays the data and time the program was assembled if the program is Language Environment enabled.\n[B]\nWhen symbolic information is used to format the report, this section displays the name of the symbolic file and the\ndate and time of the symbolic listing used.\n[C]\nDisplays link-edit information including the date and time that the load module was created, the name of the load\nlibrary from which the program was loaded, the length of the module, and the linkage editor options used.\nProgram Status Word\nFor the abending Assembler program, the Program Status Word (PSW) is displayed as follows:\n ***********************                                               \n * PROGRAM STATUS WORD *                                               \n ***********************                                               \n 823", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2602188b8fe1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  [A] \n 078D3000 80000000 00000000 12100E58                                   \n  [B] [C] [D] \n 31-BIT ADDRESSING MODE    CC = 3    PRIMARY-SPACE MODE                \n  \n \nThe PSW portion displays the following information.\n[A]\nDisplays the dump-formatted display of the 128-bit PSW.\n[B]\nDisplays the addressing mode (24, 31 or 64) at the time of the ABEND.\n[C]\nDisplays the value of the condition code at the time of the ABEND.\n[D]\nDisplays the address space mode at the time of the ABEND (Primary-Space, Secondary-Space, Home-Space, or\nAccess-Register).\nRegisters\nFor each active Assembler program, the values of the general purpose registers at the time when the program was last in\ncontrol are displayed.\nFor abending programs, these are the current register values, and the access registers and floating-point and vector\nregisters are also included. For all other programs, these are the registers when the program last transferred control to\nanother program.\nThe following sample report shows the registers for an abending Assembler program:\n **********************                                     \n * REGISTERS AT ABEND *                                     \n **********************                                     \n  \n GENERAL REGISTERS:                                         \n  \n R0   00000000_00000950                                      \n R1   00000000_007D06B0                                      \n R2   00000000_00006F60                                      \n R3   00000000_00000014                                      \n R4   00000001_0000001E                                      \n R5   00000000_007F2300", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2602188b8fe1-1", "text": "R5   00000000_007F2300                                      \n R6   00000000_007C4FE0                                      \n R7   00000000_7D000000                                      \n R8   00000000_007F9780                                      \n R9   00000000_007E12F8                                      \n R10 00000000_00000000                                      \n R11 00000000_007F9260                                      \n R12 00000000_12100D28      DISP +000000 IN CSECT CARXDEMA       \n R13 00000000_00006E70                                      \n R14 00000000_12100E8F      DISP +000167 IN CSECT CARXDEMA               \n R15 00000000_00000000                                                  \n  \n ACCESS REGISTERS:                                                      \n 824", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9582a671a6f6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  \n R0  - R3        00000000  00000000  00000000  40C1D9F3                      \n R4  - R7        00000000  40C1D9F5  00000000  40C1D9F7                      \n R8  - R11       00000000  40C1D9F9  00000000  00000000                      \n R12 - R15   00000000  00000000  00000000  00000000                      \n  \n  \n FLOATING-POINT REGISTERS:                                              \n  \n FPC 00000000                                                           \n FR0 00000000 00000000  0.0              FR8 00000000 00000000  0.0     \n FR1 00000000 00000000  0.0              FR9 00000000 00000000  0.0     \n FR2 00000000 00000000  0.0             FR10 00000000 00000000  0.0     \n FR3 00000000 00000000  0.0             FR11 00000000 00000000  0.0     \n FR4 00000000 00000000  0.0             FR12 00000000 00000000  0.0     \n FR5 00000000 00000000  0.0             FR13 00000000 00000000  0.0     \n FR6 00000000 00000000  0.0             FR14 00000000 00000000  0.0", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9582a671a6f6-1", "text": "FR7 00000000 00000000  0.0             FR15 00000000 00000000  0.0\n  \n VECTOR REGISTERS: \n \n VR0 00000000 00000000 00000000 00000000   VR16 00000000 00000000 00000000 00000000\n VR1 00000000 00000000 00000000 00000000   VR17 00000000 00000000 00000000 00000000\n VR2 00000000 00000000 00000000 00000000   VR18 00000000 00000000 00000000 00000000\n VR3 00000000 00000000 00000000 00000000   VR19 00000000 00000000 00000000 00000000\n VR4 00000000 00000000 00000000 00000000   VR20 00000000 00000000 00000000 00000000\n VR5 00000000 00000000 00000000 00000000   VR21 00000000 00000000 00000000 00000000\n VR6 00000000 00000000 00000000 00000000   VR22 00000000 00000000 00000000 00000000\n VR7 00000000 00000000 00000000 00000000   VR23 00000000 00000000 00000000 00000000\n VR8 00000000 00000000 00000000 00000000   VR24 00000000 00000000 00000000 00000000", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9582a671a6f6-2", "text": "VR9 00000000 00000000 00000000 00000000   VR25 00000000 00000000 00000000 00000000\nVR10 00000000 00000000 00000000 00000000   VR26 00000000 00000000 00000000 00000000\nVR11 00000000 00000000 00000000 00000000   VR27 00000000 00000000 00000000 00000000\nVR12 00000000 00000000 00000000 00000000   VR28 00000000 00000000 00000000 00000000\nVR13 00000000 00000000 00000000 00000000   VR29 00000000 00000000 00000000 00000000\nVR14 00000000 00000000 00000000 00000000   VR30 00000000 00000000 00000000 00000000\nVR15 00000000 00000000 00000000 00000000   VR31 00000000 00000000 00000000 00000000        \n \nAddressable Storage\nFor each register that contains a valid storage address, the data immediately preceding and following the storage address\nis also displayed.\nThe amount of storage displayed for each register is controlled by the REGMAX installation option. For more information\nabout the REGMAX option, see Installing.\nIn most cases, the addressable storage is displayed in dump format as follows:\n [A] [F] \n R1 = 00000000_007D06B0                   (NO ACTIVE USING)                       \n  [B] [C] [D] [E]", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9582a671a6f6-3", "text": "[B] [C] [D] [E] \n 00000000_007D0670 -00040 00000000 00000000 00000000 00000000 *................*  \n 00000000_007D0680 -00030 00000000 00000000 00000000 00000000 *................*  \n 825", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7d744b2d7a37-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 00000000_007D0690 -00020 00000000 00000000 00000000 00000000 *................*  \n 00000000_007D06A0 -00010 00000000 00000000 00000000 00000000 *................*  \n 00000000_007D06B0        00000000 00000000 00000000 00000000 *................*  \n 00000000_007D06C0 +00010 00000000 00000000 00000000 00000000 *................*  \n 00000000_007D06D0 +00020 00000000 00000000 00000000 00000000 *................*  \n 00000000_007D06E0 +00030 00000000 00000000 00000000 00000000 *................*  \n 00000000_007D06F0 +00040 00000000 00000000 00000000 7FFA1930 *............\"...*  \n 00000000_007D0700 +00050 007FBA48 80E03D6A 81509B30 00000094 *.\"...\\.\u00a6a&.....m*  \n 00000000_007D0710 +00060 007D0784 00000000 7F609000 80E03944 *.'.d....\"-...\\..*  \n 00000000_007D0720 +00070 00000C00 00000C58 00000C80 007D06F8 *.............'.8*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7d744b2d7a37-1", "text": "00000000_007D0730 +00080 80E0327A 00000004 00FC9980 007D0740 *.\\.:......r..'. *  \n 00000000_007D0740 +00090 00000000 007D0740 80E03542 00000000 *.....'. .\\......*  \n 00000000_007D0750 +000A0 00000000 007D0BF4 00000002 0000FF02 *.....'.4........*  \n 00000000_007D0760 +000B0 007FE0A8 007D0B64 0000015C 7F609000 *.\"\\y.'.....*\"-..*  \n 00000000_007D0770 +000C0 007D06F8 80E0327A 00000001 00F50280 *.'.8.\\.:.....5..*  \n 00000000_007D0780 +000D0 00000017 007D0740 80FB40D0 00000002 *.....'. .. }....*  \n 00000000_007D0790 +000E0 00000000 7F609000 7FFA1AE0 00000000 *....\"-..\"..\\....*                 \n 00000000_007D07A0 +000F0 00000000 0104111C 00000000 00000000 *................*               \n \nThe addressable storage portion displays the following information:\n[A]\nDisplays the contents of the 64-bit general purpose register containing the valid storage address.\n[B]\nDisplays the absolute address corresponding to the start of the data on the line for each line of the display.\n[C]", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7d744b2d7a37-2", "text": "[C]\nDisplays the offset from the register address corresponding to the start of the data on the line for each line of the\ndisplay.\n[D]\nDisplays the addressable data in hexadecimal dump format.\n[E]\nDisplays the addressable data converted to EBCDIC display format.\n[F]\nIf symbolic support is available, this indicates whether an active USING was in effect for this register on the\nabending statement.\nIf symbolic support is available for the program and the general register has an active USING in effect on the abending\nstatement, the storage may be displayed in merged format. The MRGDSECT option controls whether the merged format\nshould be used when possible.\nThe following example shows a merged format display:\n [A] [H] \n R13 = 00000000_36013030                  DSECT: CEEDSA                       \n  [B] [C] [D] [E] [F] [G] \n OFFSET  FIELD NAME               VALUE                                       DISPLAY                 LENGTH \n DEF    \n ------  --------------------     --------------------------------------     ------------------      ------  \n --- \n 000000  CEEDSAFLAGS              0000                                        *..*                    2      \n   X     \n 826", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3126b8644539-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 000002  CEEDSAMEMD               0000                                        *..*                    2      \n   X     \n 000004  CEEDSABKC                3600E318                                    *..T.*                  4      \n   A \n 000008  CEEDSAFWC                36013158                                    *....*                  4      \n   A     \n 00000C  CEEDSAR14                B600076A                                    *...\u00a6*                  4      \n   F \n 000010  CEEDSAR15                88EB4BB0                                    *h...*                  4      \n   F     \n 000014  CEEDSAR0                 36013158                                     *....*                 4      \n   F     \n 000018  CEEDSAR1                 3601313C                                    *....*                  4      \n   F     \n 00001C  CEEDSAR2                 3600C748                                    *..G.*                  4      \n   F \n 000020  CEEDSAR3                 00000014                                    *....*                  4      \n   F     \n 000024  CEEDSAR4                 007B0064                                    *.#..*                  4      \n   F \n 000028  CEEDSAR5                 00000000                                    *....*                  4      \n   F     \n 00002C  CEEDSAR6                 00000000                                    *....*                  4      \n   F     \n 000030  CEEDSAR7                 00000000                                    *....*                  4      \n   F     \n 000034  CEEDSAR8                 007F9448                                    *.\"m.*                  4", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3126b8644539-1", "text": "F     \n 000038  CEEDSAR9                 007FF7D0                                    *.\"7}*                  4      \n   F \n 00003C  CEEDSAR10                00000000                                    *....*                  4      \n   F     \n 000040  CEEDSAR11                360006A8                                    *...y*                  4      \n   F \n 000044  CEEDSAR12                3600D978                                     *..R.*                 4      \n   F \n 000048  CEEDSALWS                00000000                                    *....*                  4      \n   A     \n 00004C  CEEDSANAB                36013158                                    *....*                  4      \n   A     \n 000050  CEEDSAPNAB               00000000                                    *....*                  4      \n   A     \n 000054  .                                00000000 00000000 00000000 00000000 *................*      16     \n   F    \n 000064  CEEDSATRAN               00                                          *.*                     1      \n   A     \n 000064  CEEDSARENT               00000000                                    *....*                  4      \n   A \n 000068  CEEDSACILC               00000000                                    *....*                  4      \n   A \n 00006C  CEEDSAMODE               00000000                                    *....*                  4      \n   A \n 827", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3dcda8628b34-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 000070  .                                00000000 00000000                   *........*              8      \n   F \n 000078  CEEDSARMR                00000000                                    *....*                  4      \n   A \n 00007C  .                                00000000                            *....*                  4      \n   F \n 000080  CEEDSAAUTO               00                                          *.*                     1      \n   D \n 000080  CEEDSAEND                00000000 00000000                           *........*              8      \n   D \n \nThe merged format portion displays the following information:\n[A]\nDisplays the contents of the 64-bit general purpose register containing a valid storage address with an active\nUSING at the abending statement.\n[B]\nDisplays the offset within the mapping structure corresponding to the line of display.\n[C]\nDisplays the name of the field, if one exists, corresponding to the data displayed on each line.\n[D]\nDisplays the addressable data in hexadecimal dump format.\n[E]\nDisplays the addressable data converted to EBCDIC display format.\n[F]\nDisplays the length of the field being displayed.\n[G]\nDisplays the type of the field as defined in the program.\n[H]\nDisplays the name of the DSECT used to map the addressable storage in this display.\nProgram Storage Dump\nAt the end of the formatted displays for each active Assembler program, the program storage for the control section is\ndisplayed in dump format.\n *******************                                                                                         \n                      \n * CSECT  CARXDEMA *                                                                                         \n                      \n *******************                                                                                         \n                      \n  \n ADDRESS  OFFSET", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3dcda8628b34-1", "text": "*******************                                                                                         \n                      \n  \n ADDRESS  OFFSET                                                                                             \n                      \n 12100D28 000000   47F0F070 C3C1D9E7 C4C5D4C1 F0F461F2   F061F0F4 40F1F14B F2F940C1 D3D3C6E4  \n *.00.CARXDEMA04/20/04 11.29 ALLFU*  \n 12100D48 000020   E2C9D6D5 40C3C160 D6D7E3C9 D4C9E9C5   D961C9C9 40C3D6D7 E8D9C9C7 C8E3404D   *SION CA-\nOPTIMIZER/II COPYRIGHT (*  \n 828", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0a295814fd40-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 12100D68 000040   C35D40F2 F0F0F440 C3D6D4D7 E4E3C5D9   40C1E2E2 D6C3C9C1 E3C5E240 C9D5E3C5   *C) 2004\n COMPUTER ASSOCIATES INTE*  \n 12100D88 000060   D9D5C1E3 C9D6D5C1 D36B40C9 D5C34B40   90ECD00C 18CF4130 00F01803 4510C080   *RNATIONAL,\n INC. ..}......0....{.*  \n 12100DA8 000080   0A0A1821 18411F51 0E2450D0 10045010   D00818D1 41F00004 4110C2C8 5840021C  \n *..........&}..&.}..J.0....BH. ..*  \n 12100DC8 0000A0   5840400C 41404018 17334330 40001233   4780C0C8 D5074004 10004780 C0C64143   *.  ..\n  ..... .....{HN. .....{F..*  \n 12100DE8 0000C0   400047F0 C0A817FF 12FF4770 C1C29A0F   C214E340 C2BC0004 4DF0C0E4 C3C1D6C4  \n * ..0{y......AB..B.T B...(0{UCAOD*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0a295814fd40-1", "text": "* ..0{y......AB..B.T B...(0{UCAOD*  \n 12100E08 0000E0   E2D5C1D7 4100F000 1B110A08 18F005EF   4500C0FC C3C1D6C4 E2D5C1D7 0A09D25F  \n *SNAP..0......0....{.CAODSNAP..K^*  \n 12100E28 000100   D074C254 D203D0D4 C2B44110 D0D494F0   1000960F 100043E1 00004100 D0745001  \n *}.B.K.}MB...}Mm0..o.........}.&.*  \n 12100E48 000120   000042E1 00000A13 9110D0A4 47E0C1EC   FA30D050 C2D0D203 D0D8C2B8 4110D0D8   *........j.}u.\n\\A...}&B}K.}QB...}Q*  \n 12100E68 000140   43E10000 4100D074 50010000 42E10000   0A144110 D0749101 10174710 C1A01FFF  \n *......}.&...........}.j.....A...*  \n 12100E88 000160   BFF71015 58E0F000 12EE4770 C1769130   F0044770 C1A09601 10171BEE 1B11BF13   *.7...\n\\0.....A.j.0...A.o.........*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0a295814fd40-2", "text": "\\0.....A.j.0...A.o.........*  \n 12100EA8 000180   F00643E0 F0051C0E 41101008 9140F004   47E0C198 41101008 18014110 F0000A0A   *0..\\0.......j\n 0..\\Aq........0...*  \n 12100EC8 0001A0   5820D04C 181D58D0 D0044100 00F01800   41101000 0A0A58E0 D00C18F2 980CD014  \n *..}<...}}....0.........\\}..2q.}.*   \n 12100EE8 0001C0   0B0E0700 4510C1E6 00198000 E2E8E2D7   D9C9D5E3 40C4C440 D5D6E340 C6D6E4D5  \n *......AW....SYSPRINT DD NOT FOUN*   \n 12100F08 0001E0   C4000000 20000A23 47F0C130 4510C20E   001A8000 C5D9D9D6 D940D6D7 C5D5C9D5  \n *D........0A...B.....ERROR OPENIN*   \n 12100F28 000200   C740E2E8 E2D7D9C9 D5E30000 00200A23   47F0C130 40C1D9F0 40C1D9F1 00000000   *G\n SYSPRINT.......0A. AR0 AR1....*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0a295814fd40-3", "text": "SYSPRINT.......0A. AR0 AR1....*   \n 12100F48 000220   40C1D9F3 00000000 40C1D9F5 00000000   40C1D9F7 00000000 40C1D9F9 00000000   * AR3....\n AR5.... AR7.... AR9....*   \n 12100F68 000240   00000000 00000000 00000000 00000000   00000000 00000000 00000000 00000000  \n *................................*   \n 12100F88 000260   00000000 00000000 00000001 00004000   00000001 00000001 90000000 E2E8E2D7  \n *.............. .............SYSP*   \n 12100FA8 000280   D9C9D5E3 02000050 00000001 00000001   00000000 00000000 00000001 00000001  \n *RINT...&........................*   \n 12100FC8 0002A0   00000001 00000050 00000001 00000000   00000001 80100FDD 80100FE1 00000001  \n *.......&........................*   \n 12100FE8 0002C0   0000001E 00000000 E2E8E2D7 D9C9D5E3   1C                                             \n *........SYSPRINT.*\n  \n \nThe program storage dump can be suppressed by program name or prefix using the CAOUXMOD macro in your", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0a295814fd40-4", "text": "installation defaults member, CAOUDFRX. For more information about the CAOUXMOD macro see SymDump  Batch\nOptions.\nOpen Files Report\nIn the Open Files report, SymDump  Batch formats information from the data management control blocks and dumps the\ncurrent logical record for all files in the job step that remain open and are not displayed earlier in the File Section of the\n 829", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b707715ec3ba-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nabend report. If the file was accessed sequentially, the contents of the previous record may also be displayed. Optional\nsections of the report include catalog information for VSAM files and dumps of data management control blocks. The\ncontents of this report are similar to the contents of the File Section Display.\nThe Open Files report appears once near the end of the abend report. The reported files may be from COBOL programs\nnot reported on in the abend report or from any non-COBOL program in the job step. An example of the Open Files report\nfollows. For a description about the optional sections, see File Section Display.\n  *********************                                                           \n  * OPEN FILES REPORT *                                                           \n  *********************                                                           \n  \n  DDNAME=SYSUDUMP   DSORG=PS   BSAM   BUFNO=0                                     \n  DSN=USER02.USER02A.JOB59924.D0000110.?               RECFM=VBA                  \n  STATUS(OPEN)    USAGE(OUTPUT)           LRECL=125    BLKSIZE=1632               \n  \n  [A] DDNAME=PRINT      DSORG=PS   QSAM   BUFNO=5    UNIT=3390,UCB    VOL=SER=WRKD28  \n   DSN=USER02.PRINT                                     RECFM=FB                   \n  [B] STATUS(OPEN)    USAGE(OUTPUT)           LRECL=120    BLKSIZE=120                \n  \n  [C]     CONTENTS OF CURRENT LOGICAL RECORD                                \n                   ----------------------------------                             \n ADDRESS  22BBBE20   LENGTH 00000078  (DECIMAL 120)                              \n             OFFSET", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b707715ec3ba-1", "text": "OFFSET                                                                  \n            +000000 40404040 40404040 40404040 40404040   40404040 40404040 40404040 40404040    *            \n                       *   \n            +000020 40404040 40404040 40404040 40404040   40404040 40404040 40404040 40404040    *            \n                       *   \n            +000040 40404040 40404040 40404040 40404040   40404040 40404040 40404040 40404040    *            \n                       *   \n            +000060 40404040 40404040 40404040 40404040   40404040 40404040                              *    \n                       *       \n  \n  [D]     CONTENTS OF PREVIOUS RECORD                               \n                   ---------------------------                              \n                         LENGTH 00000078  (DECIMAL 120)                          \n             OFFSET                                                          \n           +000000 40404040 40404040 40404040 40404040   40404040 40404040 40404040 40404040     *            \n                       *   \n           +000020 40404040 40404040 40404040 40404040   40404040 40C3C160 E2E8D4C4 E4D4D761     *            \n             CA SYMDUMP/*  \n           +000040 C2C1E3C3 C8404040 40404040 40404040   40404040 40404040 40404040 40404040     *BATCH       \n                       *   \n           +000060 40404040 40404040 40404040 40404040   40404040 40404040                       *", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b707715ec3ba-2", "text": "*       \n  \n \nThe Open Files Report displays the following information:\n[A]\nDisplays the data management control blocks. The data management control blocks are interpreted and displayed\nin KEYWORD=value format. This information includes the ddname, data set organization, access method,\n 830", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ca029a1e4664-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nnumber of buffers allocated, and data set name. For non-VSAM files, the unit type, volser and record format are\nalso displayed.\n[B]\nIndicates the file's current status (OPEN, CLOSED) and usage (INPUT, OUTPUT, etc.), and the record length.\nFor non-VSAM files, the block size is also displayed, while the feedback code, function code, and return code are\ndisplayed for VSAM files.\n[C]\nDisplays the contents of the current logical record in hexadecimal format, with a character representation on the\nright. If the FIRST128 option was specified, only the first 128 bytes of the record are displayed.\nFor keyed VSAM files, the current record key will be displayed in the same format, prior to the contents of the\nrecord. (See File Section Display for an example.)\n[D]\nDisplays the contents of the previous record data for sequentially accessed files (VSAM, QSAM, and BSAM), if it\nis available in an I/O buffer and:\n\u2022The file is not a BSAM file using NOTE/POINT\n\u2022The file is not a VSAM file using skip-sequential access\n\u2022The file is not a JES managed data set, such as in-stream data or data written to a SYSOUT class\n\u2022The file does not contain unformatted, spanned, compressed, or extended records\nFor keyed VSAM files, the previous record key will be displayed prior to the contents of the previous record. (For\nan example, see File Section Display.)\nSave Area Trace Report\nThe Save Area Trace report assists you in tracing and debugging programs in a multiple-module environment. This report\nprints only once for any given ABEND reporting sequence. Whether the ABEND occurs in a multiple-module run and", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ca029a1e4664-1", "text": "SymDump  Batch reports on more than one program, or it is a single-module run with only the abend report, the Save Area\nTrace always prints just once.\nWhen a program calls a subordinate program, the caller's registers are stored in an eighteen-fullword save area to\nestablish the means of return. A series of calling and called programs establishes a chain of save areas, as shown in the\nfollowing example.\n *******************                                                      \n * SAVE AREA TRACE *                                                      \n *******************                                                      \n SAVE AREA FOR SYSTEM                                          \n  [A] [B] [C] [D] [E] \n SA 00006F60  WD1 00000000   BKL 00000000   FWL 00000000   RET 80FE0708   \n           F  EPA B6500888 G R0  FD000008   R1  00006FF8   R2  00000040   \n              R3  007D9D84   R4  007D9D60   R5  007FF5E0   R6  007B7FE0   \n              R7  FD000000   R8  007F8088   R9  007FF200   R10 00000000   \n              R11 007FF5E0   R12 80C999FA                                 \n  \n SYSTEM CALLED CEE  (ASSEMBLER)                                            \n SAVE AREA FOR CEE                                                         \n  \n SA 365113C0  WD1 00000000   BKL 00006F60   FWL 00000000   RET 00CA5AB0    \n              EPA 36500888   R0  00000000   R1  3650F7B8   R2  00000000", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ca029a1e4664-2", "text": "R3  00000000   R4  00000000   R5  00000000   R6  00000000    \n              R7  00000000   R8  00000000   R9  00000000   R10 00000000    \n              R11 00000000   R12 36510A20                                  \n 831", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0020e70e30d1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  \n CEE CALLED CAOEDEMO  (COBOL FOR Z/OS  NOT CA-OPT)                         \n  \n CAOEDEMO ABENDED                                                          \n \nIn this example, the program called by the system is CAOEDEMO. (The intervening save area is for the LE runtime).\nThe following are the contents of the save area (all addresses are absolute hexadecimal):\n[A]\nDisplays the system's save area location.\n[B]\nDisplays the first word of the eighteen-word save area. It is not used by the system and is usually zeros.\n[C]\nPoints backwards to the location of the prior save area (if any). BKL stands for backward link.\n[D]\nPoints forward to the location of the save area belonging to the next program. FWL is the forward link.\n[E]\nRepresents the return address (RET) as an absolute hexadecimal location.\n[F]\nRepresents the point where CAOEDEMO is entered when control is passed from the System to CAOEDEMO.\nEPA means entry point address.\n[G]\nThe next thirteen words, zero through twelve, save the contents of registers.\nAn eighteen-word save area prints for each active program in the hierarchy leading to the program that abended. The\nsave area for the abending program does not display.\nWhenever an unidentifiable program is encountered in the chain, it designates the program in the Save Area Trace as\nUNKWN nnn, where nnn is 1 to 999. SymDump  Batch does not determine the program's language.\nThe information that is supplied in this detailed version of the Save Area Trace can be valuable to the user who\nunderstands register conventions and whose problem involves more than one module.\nIMS Report", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0020e70e30d1-1", "text": "understands register conventions and whose problem involves more than one module.\nIMS Report\nThe IMS portion of the abend report is produced whenever a program abends which accesses an IMS database.\n **********************************                                            \n * IMS  8.1.0 RELATED INFORMATION *   [A] \n **********************************                                            \n  \n *****************                                                             \n * LAST IMS CALL *   [B] \n *****************                                                             \n  \n IMS FUNCTION:  ISRT   [C]\nThe IMS report begins with the following information:\n[A]\nDisplays the release of IMS.\n 832", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4acc55ec66a7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n[B]\nIf the location of the last IMS call can be determined, it is displayed in the same format as the abending statement\ninformation (not shown).\nNOTE\nCall location information is not available under the LE run time.\n[C]\nDisplays the IMS function used on the last IMS call.\nInformation about the current or last database PCB is then displayed, if it is available. An example follows:\n  ****************************************                                                                   \n                        \n  * CURRENT/LAST DATABASE PCB - DI21PART *  [A] \n  ****************************************                                                                   \n                        \n  \n  PCB PREFIX:                                                                                                \n                        \n  ADDRESS  OFFSET   [B] \n  00088CA8 000000   00500038 00020028 40404040 00000000   00000000 00000000 00000000 C4C2D3D6   *.&......  \n  ................DBLO*   \n  00088CC8 000020   C1C44040 000060E0 00000000 00000000   00088D30 00088CA8                           *AD  ..-\n\\...............y*           \n  \n  PCB:   [C] \n  \n  LINE#   LEVEL/FIELD NAME                        VALUE/LOCATION                             DEFINITION       \n                                   \n  ------  ------------------------------      --------------------------------------    \n ----------------------------------------------- \n  000096  01 PCB-AREA-1                          BLL=0001+000000  (00088CE0)                                 \n                         \n  000097  02 DBD-NAME                            *DI21PART*                                  X(08)            \n                                   \n  000098  02 SEGMENT-LEVEL                       *02*                                        X(02)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4acc55ec66a7-1", "text": "000099  02 STATUS-CODES                         SPACES                                     X(02)            \n                                   \n  000100  02 PROCESS-OPTIONS                     *L   *                                      X(04)            \n                                   \n  000101  02 FILLER                              +560296                                     S9(05) BINARY    \n                                   \n  000102  02 SEG-NAME                            *STANINFO*                                  X(08)            \n                               \n  [D] [E] [F] [G] [H] [I] \n  STATUS SEGMENT     NUMBER OF   SEGMENT     PROCESSING   KEY                                                 \n                            \n  CODE   LEVEL       SEGMENTS    NAME        OPTIONS      LENGTH                                              \n                           \n  '  '   02          5           STANINFO    L            19                                                  \n                             \n  \n  FEEDBACK FROM LAST CALL: [J] \n 833", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "514cca39d515-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  ADDRESS  OFFSET                                                                                            \n                     \n  00088D04 000000   F0F2F9F8 F9F0F3F6 60F0F0F1 40404040   40F0F2                             *02989036-001   \n  02*           \n  \n  TRACE OF DATABASE CALLS (NEWEST ENTRY FIRST):                                                              \n                     \n  -0 ISRT            OK         [K] \n  -1 ISRT            OK                                                                                      \n                     \n  -2 ISRT            OK                                                                                      \n                     \n  -3 ISRT            OK                                                                                      \n                     \n  -4 ISRT            OK                                                                                      \n                     \n  -5 ISRT            OK                                                                                      \n                    \n \nThe IMS report displays the following information about the current or last database PCB:\n[A]\nDisplays the PCB name.\n[B]\nDisplays the address and contents of the PCB prefix (IMS 4.1.0 and above).\n[C]\nDisplays the address and contents of the PCB. The PCB is displayed in merged format if all of these conditions\nare met:\n\u2022The MERGEDB option is ON.\n\u2022The PCB is defined in the most active COBOL, PL/I, or Assembler program.\n\u2022Symbolic information is available for that program.\nOtherwise, the PCB is displayed in dump format.\n[D]\nDisplays the status code.\n[E]\nDisplays the segment level.\n[F]\nDisplays the number of segments.\n[G]\nDisplays the name of the last retrieved segment.\n[H]\nDisplays the processing options.\n[I]\nDisplays the key length.\n[J]\nDisplays the key feedback.\n 834", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "660d6636d9ac-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n[K]\nDisplays the call trace information for the JCB.\nThe rest of the information about the last IMS call is displayed as follows:\n  ************************                                                                                   \n       \n  * CURRENT/LAST SEGMENT  *    [A] \n  ************************                                                                                   \n                        \n  \n  LINE#   LEVEL/FIELD NAME                       VALUE/LOCATION                      DEFINITION               \n                           \n  ------  ------------------------------ -----------------------------   -------------------------------------\n   \n  000081  01 SEG00060-INSERT-AREA                 BLW=0000+0004A8  (3667F578)                                 \n                           \n  000082  02 FILLER                              *02                    742          *   X(61)                \n                               \n                                         (+000032)   *               1200  96      *                          \n                               \n  000083  02 RIGHT-MAKE-SPAN                   +63           S9(03)                                          \n    \n  000084  02 FILLER                               SPACES         X(06)                                       \n        \n  000085  02 WRONG-MAKE-SPAN                ?    *06C*           9(03)                                       \n        \n  000086  02 FILLER                               SPACES         X(12)                                       \n        \n  \n  *********************                                                                                      \n                        \n  * SSA FOR LAST CALL  *      [B] \n  *********************                                                                                      \n                        \n  \n  ARGUMENT 1:                                                                               \n  \n  LINE#   LEVEL/FIELD NAME                       VALUE/LOCATION                      DEFINITION               \n                           \n  ------  ------------------------------ -----------------------------   -------------------------------------\n   \n  000044  01 SEG00010-SSA                     BLW=0000+0003D0  (3667F4A0)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "660d6636d9ac-1", "text": "000045  02 SEG-NAME-00010                  *PARTROOT*          X(08)                                       \n        \n  000046  02 BEGIN-OP-00010                  *(*         X(01)                                               \n  000047  02 KEY-NAME-00010                  *PARTKEY *          X(08)                                       \n        \n  000048  02 REL-OPER-00010                  * =*            X(02)                                           \n    \n  000049  02 KEY-VALUE-00010                 *02989036-001     *     X(17)                                   \n            \n 835", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c902f0943919-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  000050  02 END-OP-00010                    *)*                         X(01)                               \n        \n \nThe IMS report displays the following information about the current/last segment and the Segment Search Argument\n(SSA) for last call:\n[A]\nDisplays the current or last segment returned in the user I/O area.\n[B]\nDisplays the SSA for the last database call, if available. If multiple search arguments were passed on the last call,\nthey are displayed in the order in which they were passed.\nThe segment and SSAs are displayed in merged format if all of the following conditions are met:\n\u2022The MERGEDB option is ON.\n\u2022The area is defined in the most active COBOL, PL/I, or Assembler program.\n\u2022Symbolic information is available for that program.\nOtherwise, they are displayed in dump format.\nAll of the program communication blocks (PCBs) used by the program are displayed, beginning with the terminal PCBs,\nas shown next:\n  ********************************                                               \n  * PROGRAM COMMUNICATION BLOCKS  *                                             \n  ********************************                                               \n  [A] [B] \n  ****************************************************                           \n  * TERMINAL PCB FOR          - RELATIVE NUMBER 1         *  (CURRENT OR LAST USED)  \n  ****************************************************                          \n  \n  PCB PREFIX:   [C] \n  ADDRESS   OFFSET                                                                \n  00049084 000000   00400038 00010018 40404040 00000000   00000000 00000000 00000000 C9D6D7C3   *. ......     \n  .............IOPC    *", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c902f0943919-1", "text": ".............IOPC    *       \n  000490A4 000020   C2404040 00000000 00000000 40404040   40404040 00049084 *B       ........        ...d*   \n        \n  \n  PCB:       [D] \n  ADDRESS   OFFSET                                                                                           \n                         \n  000490BC 000000   40404040 40404040 10004040 40404040   40404040 40404040 40404040 40404040   *        ..   \n                       *       \n  000490DC 000020   40404040 40404040 40404040 40404040   00000000 00000000 00000000 00000000   *             \n     ................. *       \n  [E] [F] [G] [H] \n  STATUS     DATE AND TIME OF    MESSAGE     FORMATTING                                                      \n                        \n  CODE       LAST MESSAGE        COUNT                                   \n  '  '       N/A                 N/A         N/A         \n  \n \nThe Program Communication Blocks portion displays the following information:\n 836", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d8492fa446b4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n[A]\nDisplays the PCB name and number.\n[B]\nIndicates whether it is the current or last used terminal PCB.\n[C]\nDisplays the address and contents of the PCB prefix (IMS 4.1.0 and above).\n[D]\nDisplays the address and contents of the PCB. The PCB is displayed in merged format if all of these conditions\nare met:\n\u2022The MERGEDB option is ON.\n\u2022The PCB is defined in the most active COBOL, PL/I, or Assembler program.\n\u2022Symbolic information is available for that program.\nOtherwise, the PCB is displayed in dump format.\n[E]\nDisplays the status code of the PCB.\n[F]\nDisplays the date and time of the last message.\n[G]\nDisplays the message count.\n[H]\nDisplays the formatting attributes.\nThe following screen displays the database PCBs:\n [A] [B] \n  ****************************************************                                                       \n                        \n  * DATABASE PCB FOR DI21PART - RELATIVE NUMBER 2    *  (CURRENT OR LAST USED)                               \n                        \n  ****************************************************                                                       \n                        \n  \n  PCB PREFIX:   [C] \n  ADDRESS  OFFSET                                                                                            \n                        \n  00088CA8 000000   00500038 00020028 40404040 00000000   00000000 00000000 00000000 C4C2D3D6    *.&......  \n  ................DBLO*      \n  00088CC8 000020   C1C44040 000060E0 00000000 00000000   00088D30 00088CA8                      *AD  ..-\n\\...............y*              \n  \n  PCB:    [D]", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d8492fa446b4-1", "text": "\\...............y*              \n  \n  PCB:    [D] \n  \n   LINE#   LEVEL/FIELD NAME                      VALUE/LOCATION                      DEFINITION               \n                           \n  ------ -----------------------------   -----------------------------   -------------------------------------\n   \n  000096     01 PCB-AREA-1                        BLL=0001+000000  (00088CE0)                                 \n                           \n 837", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b33ac3518152-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  000097     02 DBD-NAME                         *DI21PART*                              X(08)                \n                               \n  000098     02 SEGMENT-LEVEL                    *02*                                    X(02)                \n                               \n  000099     02 STATUS-CODES                      SPACES                                 X(02)                \n                               \n  000100     02 PROCESS-OPTIONS                  *L   *                                  X(04)                \n                               \n  000101     02 FILLER                           +560296                                 S9(05) BINARY        \n                               \n  000102     02 SEG-NAME                         *STANINFO*                              X(08)                \n                               \n  [E] [F] [G] [H] [I] [J] \n  STATUS     SEGMENT     NUMBER OF   SEGMENT     PROCESSING   KEY                                             \n                                   \n  CODE       LEVEL       SEGMENTS    NAME        OPTIONS      LENGTH                                          \n                                   \n  '  '       02          5           STANINFO    L            19                                              \n                           \n  \n  FEEDBACK FROM LAST CALL:                                                                                   \n                        \n  ADDRESS  OFFSET   [K] \n  00088D04 000000   F0F2F9F8 F9F0F3F6 60F0F0F1 40404040   40F0F2                                 *02989036-001\n     02*                   \n  \n  TRACE OF DATABASE CALLS (NEWEST ENTRY FIRST):                                                              \n                        \n  -0 ISRT            OK                                                                                      \n                        \n  -1 ISRT            OK   [L] \n  -2 ISRT            OK                                                                                      \n                        \n  -3 ISRT            OK", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b33ac3518152-1", "text": "-3 ISRT            OK                                                                                      \n                        \n  -4 ISRT            OK                                                                                      \n                        \n  -5 ISRT            OK                                                                                      \n                       \n \nThe Database PCBs portion displays the following information:\n[A]\nDisplays the PCB name and number.\n[B]\nIndicates whether it is the current or last used database PCB.\n[C]\nDisplays the address and contents of the PCB prefix (IMS 4.1.0 and above).\n[D]\nDisplays the address and contents of the PCB. The PCB is displayed in merged format if all of these conditions\nare met:\n 838", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f5a0f71a4809-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022The MERGEDB option is ON.\n\u2022The PCB is defined in the most active COBOL, PL/I, or Assembler program.\n\u2022Symbolic information is available for that program.\nOtherwise, the PCB is displayed in dump format.\n[E]\nDisplays the status code.\n[F]\nDisplays the segment level.\n[G]\nDisplays the number of segments.\n[H]\nDisplays the name of the last retrieved segment.\n[I]\nDisplays the processing options.\n[J]\nDisplays the key length.\n[K]\nDisplays the key feedback.\n[L]\nDisplays the call trace information for the JCB.\n  ******************                                                                                         \n                        \n  * PARAMETER LIST *   [A] \n  ******************                                                                                         \n                        \n  ADDRESS  OFFSET                                                                                            \n                        \n  00006FC8 000000   C4D3C96B C4C6E2E2 C1D4F0F1 6BC4C6E2   E2C1D4F0 F16BF76B F0F0F0F0 6B6BF06B  \n *DLI,DFSSAM01,DFSSAM01,7,0000,,0,*   \n  00006FE8 000020   6BD56BF0 6BE36B6B 6BD56BD5 6B6BD56B   6B6B                                 \n *,N,0,T,,,N,N,,N,,,*                 \n  \n  \n  \n  *******************                                                                                        \n                        \n  * MODULE DFSPRPX0 *  [B] \n  *******************                                                                                        \n                        \n  ADDRESS  OFFSET", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f5a0f71a4809-1", "text": "*******************                                                                                        \n                        \n  ADDRESS  OFFSET                                                                                            \n                        \n  000078B0 000000   00000000 00006FC0 00000000 00007900   00007A58 000079B0 000078D0 00000000   *......?\n{......`...:...`....}....*   \n  000078D0 000020   C4C6E2D7 C3C3F3F0 00000000 00008E90   00000000 000322F8 00000000 00000000  \n *DFSPCC30...............8........*   \n  000078F0 000040   00000000 C4C6E2D4 D7D34040 00007C80   00007910 0000FFFF 00049060 007D8B58   *....DFSMPL\n  ..@...`........-.'..*   \n  00007910 000060   E2C3C8C4 D3D6C1C4 E4D5D3C4 040000F0   C4C6E2E2 C1D4F0F1 C4C6E2E2 C1D4F0F1  \n *SCHDLOADUNLD...0DFSSAM01DFSSAM01*   \n 839", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b85055a09b65-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  00007930 000080   40404040 40404040 40404040 40404040   C1404040 00070000 00000000 00000000   *            \n    A   ............*   \n  00007950 0000A0   00000000 00000000 00007954 80007A84   00000000 F0000122 00009B00 F080D5D5  \n *..........`...:d....0.......0.NN*   \n  .                     .                                              .                                     \n    .       \n  .                     .                                              .                                     \n    .       \n  .                     .                                              .                                     \n    .   \n  00007DF0 000540   00000000 00000000 00000000 00000000   00000000 00000000 00000000 00000000  \n *................................*  \n \nNext, the following information is displayed:\n[A]\nDisplays the parameter list passed to IMS.\n[B]\nDisplays a dump of module DFSPRPX0.\n[C]\nDisplays a dump of module DFSECP10 or DFSECP20, if available (not shown).\nFinally, the following report is produced when the ABEND occurs in an LE environment:\n  ********************                                                         \n  * ENVIRONMENT DATA *                                                         \n  ********************                                                         \n  \n  [A] IMS IDENTIFIER                  IVP1                                       \n  [B] IMS CONTROL REGION TYPE         BATCH                                      \n  [C] IMS APPLICATION REGION TYPE     BATCH                                      \n  [D] IMS REGION IDENTIFIER           1                                          \n  [E] APPLICAITON PROGRAM NAME        DFSSAM01                                   \n  [F] PSB NAME                        DFSSAM01", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b85055a09b65-1", "text": "[F] PSB NAME                        DFSSAM01                                   \n  [G] TRANSACTION NAME                NO TRANSACTION NAME                        \n  [H] USERID FROM PST                 UNAVAILABLE                                \n \nThe Environment Data portion displays the following information:\n[A]\nDisplays the identifier from the execute parameters.\n[B]\nDisplays the control region type; BATCH, DB/DC, and so on.\n[C]\nDisplays the Application region type; BATCH, MPP, BMP, and so on.\n[D]\nDisplays the region identifier.\n[E]\nDisplays the name of the application program being run.\n 840", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "592d39067588-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n[F]\nDisplays the name of the PSB currently allocated.\n[G]\nDisplays the name of the current transaction, if applicable.\n[H]\nDisplays the user ID from the PST, if available.\nDB2 Report\nThe DB2 portion of the abend report is produced whenever a program that accesses a DB2 database using DB2 for MVS/\nESA Release 4.1.0 or above abends. The first page of the DB2 report displays the following information:\n  ****[A]***********************************************                          \n  * DB2 8.1.0 RELATED INFORMATION FOR SUBSYSTEM D81A * [B] \n  ****************************************************                          \n  \n  **********************************                                            \n  * RETURN CODE FROM LAST SQL CALL *  [C] \n  **********************************                                            \n  \n  DSNT400I SQLCODE = 000,  SUCCESSFUL EXECUTION                                 \n  \n  \n  **********************                                                        \n  * LAST SQL STATEMENT *                                                        \n  **********************                                                        \n  \n  STATEMENT LOCATION:  [D] \n  \n  COLLECTION-ID      OPT2DB2DEMO                                                \n  PACKAGE NAME       DB2DEMO                                                    \n  CONSISTENCY TOKEN  1841B4DE029F3FE6                                           \n  SECTION NUMBER     00012                                                      \n  STATEMENT NUMBER   00755                                                      \n  \n  \n  SQL STATEMENT: [E] \n  \n  SELECT EMP , FIRSTNAME , LASTNAME , DEPT , MANAGER INTO :DCLEMPLOY.EMPLOY-EMP \n  :EMP-IND-1.EMP-IND-EMP , :DCLEMPLOY.EMPLOY-FIRSTNAME :EMP-IND-1.EMP-IND-FNAME ,", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "592d39067588-1", "text": ":DCLEMPLOY.EMPLOY-LASTNAME :EMP-IND-1.EMP-IND-LNAME , :DCLEMPLOY.EMPLOY-DEPT  \n  :EMP-IND-1.EMP-IND-DEPT , :DCLEMPLOY.EMPLOY-MANAGER :EMP-IND-1.EMP-IND-MANAGER\n  FROM EMPLOY WHERE EMP = :DCLJOB.JOB-EMP                                       \n \nThe DB2 and the LAST SQL Statement portions of the abend report display the following information:\n[A]\nDisplays the release of DB2.\n[B]\nDisplays the DB2 subsystem-ID.\n 841", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9b7d0b7d51b7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n[C]\nDisplays the SQL return code, SQLCODE, and the message associated with that code. If SQLCODE is non-zero,\nthe SQLSTATE value also displays.\n[D]\nDisplays the location of the last SQL statement executed. (This is the last SQL statement before the ABEND or\nthe abending SQL statement.)\nIf the DB2 program containing the last SQL statement is bound into a package, the location information includes\nthe collection-ID, package name, consistency token, section number, and statement number (as shown in the\nexample).\nIf the DB2 program is not bound into a package, the location information includes the plan name, DBRM name,\nconsistency token, section number, and statement number.\nIn both cases, the statement number refers to the listing generated by the SQL precompile, not the COBOL\ncompile listing.\n[E]\nDisplays the last or abending SQL statement. If there is an associated cursor declaration, it is also displayed.\nIf the last SQL statement is not found in the DB2 catalog (for packages or plans which were bound remotely, for example),\nthe statement type displays.\n ********************************                                            \n * SQL DESCRIPTOR AREA (OUTPUT)  *    [A] \n ********************************                                            \n  \n  \n LINE#    LEVEL/FIELD NAME                   VALUE/LOCATION                          DEFINITION               \n                           \n ------  ------------------------------- ---------------------------------------\n --------------------------------------  \n 001225  05 SQL-AVAR-LIST31                   BLW=0001+0008B4  (000669EC)        \n 001226  10 PRE-SQLDAID                    ? X   'E2D8D3C4C1404008'                      X(8)                 \n                               \n 001227  10 PRE-SQLDABC                      +236                                        S9(9) BINARY", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9b7d0b7d51b7-1", "text": "001228  10 PRE-SQLN                         +5                                          S9(4) BINARY         \n                               \n 001229  10 PRE-SQLLD                        +5                                          S9(4) BINARY         \n                               \n 001230  10 PRE-SQLVAR                        BLW=0001+0008C4  (000669FC)        \n 001231  12 SQLVAR-BASE1                      BLW=0001+0008C4  (000669FC)        \n 001232  15 SQL-AVAR-TYPE1                   +501                                        S9(4) BINARY         \n                               \n 001233  15 SQL-AVAR-LEN1                    +2                          \n .                                               .                                   \n .                                               .                                   \n .                                               .                                   \n ***************************                                                 \n * HOST VARIABLES (OUTPUT)  *   [B] \n ***************************                                             \n  \n LINE#    LEVEL/FIELD NAME                   VALUE/LOCATION                          DEFINITION               \n                           \n ------  ------------------------------- ---------------------------------------\n --------------------------------------  \n 842", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7ce0e25b33fb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 000311  01 DCLEMPLOY                         BLW=0000+000940  (00065A78)        \n 000312  10 EMPLOY-EMP                   +7                                          S9(4) BINARY             \n                           \n 000322  01 EMP-IND-TABLE                     BLW=0000+000988  (00065AC0)        \n 000323  10 EMP-IND-1                         BLW=0000+000988  (00065AC0)        \n 000324  20 EMP-IND-EMP                      +0                                          S9(4) BINARY         \n                               \n 000331  10 EMP-IND-2(1)                     +0                                          S9(4) BINARY\n REDEFINES EMP-IND-1    \n \nThe SQL Descriptor Area and the Host Variables portions of the report display the following information:\n[A]\nDisplays the contents of the SQLDAs for the last SQL statement, if applicable. If the MERGEDB option is ON and\nsymbolic information is available for the program, the SQLDA is mapped. Otherwise, the SQLDA is displayed in\ndump format.\n[B]\nDisplays the contents of the host variables for the last SQL statement, if applicable. If relevant, the output host\nvariables are displayed following the SQLDA for the output variables, and the input host variables are displayed\nfollowing the SQLDA for the input variables. If the MERGEDB option is ON and symbolic information is available\nfor the program, the host variables are mapped. Otherwise, the fully qualified names of the host variables are\ndisplayed, with the address, length, and data in dump format.\nIf DB2 objects are referenced by the last SQL statement, the names and types of the objects are displayed after the Host", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7ce0e25b33fb-1", "text": "Variables. Similarly, if columns in a table or view are referenced, the contents of the referenced columns are displayed.\n ***************************                                                                                 \n                       \n * SQL COMMUNICATIONS AREA  *  [A] \n ***************************                                                                                 \n                       \n  \n  \n LINE#    LEVEL/FIELD NAME                   VALUE/LOCATION                          DEFINITION               \n                           \n ------  ------------------------------- ---------------------------------------\n --------------------------------------  \n 000219  01 SQLCA                                 BLW=0000+000848  (00065980)                                 \n                           \n 000220  05 SQLCAID                              *SQLCA   *                                  X(8)             \n                                   \n 000221  05 SQLCABC                              +136                                        S9(9) BINARY     \n                                   \n 000222  05 SQLCODE                              +0                                          S9(9) BINARY     \n                                   \n 000223  05 SQLERRM                               BLW=0000+000858  (00065990)                                 \n                           \n 000224  49 SQLERRML                             +0                                          S9(4) BINARY     \n                                   \n 000225  49 SQLERRMC                              SPACES                                     X(70)            \n                                   \n 000226  05 SQLERRP                              *DSN     *                              X(8)                 \n                               \n 843", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c6e0fc5ff0f7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 000227  05 SQLERRD(1)                           +0                                          S9(9) BINARY\n OCCURS 6                               \n           <UNMERGED DATA FOR SQLERRD>    X  '0000000000000000FFFFFFFF00000000'      LENGTH  20               \n                           \n                                   (+000016)    X    '00000000'                                               \n                               \n 000229  05 SQLWARN                               BLW=0000+0008C0  (000659F8)                                 \n                           \n 000230  10 SQLWARN0                          SPACES                                     X   \n \nThe SQL Communications Area portion of the report displays the following information:\n[A]\nDisplays the contents of the SQLCA. If the MERGEDB option is ON and symbolic information is available for\nthe program, data item information such as the data name, picture clause, and usage type are merged with the\nSQLCA storage. Otherwise, the address, length, and contents of the SQLCA are displayed in dump format.\nThe connection information is displayed, as shown in the following example:\n  **************************                                                     \n  * CONNECTION INFORMATION  *                                                    \n  **************************                                                     \n  \n  [A] CONNECTION MODE   BACKGROUND                                                  \n  [B] CONNECTION TYPE   BATCH                                                       \n  [C] CONNECTION ID     BATCH                                                       \n  [D] CORRELATION ID    USER001D                                                    \n  [E] AUTHORIZATION ID  USER001                                                     \n \nThe Connection Information portion of the report displays the following information:\n[A]\nDisplays the connection mode.\n[B]\nDisplays the connection type.\n[C]\nDisplays the connection ID.\n[D]\nDisplays the correlation ID.\n[E]\nDisplays the authorization ID.\nThe plan information follows the connection information:\n  *****************************", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c6e0fc5ff0f7-1", "text": "Displays the authorization ID.\nThe plan information follows the connection information:\n  *****************************                                                 \n  * APPLICATION PLAN OPT2DEMO *  [A] \n  *****************************                                                 \n  \n  BIND DATE/TIME  06 MAR,2008 14.57.54   [B] \n  BOUND BY        USER001  [C] \n  \n  \n  BIND OPTIONS: [E] \n 844", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0c25c7c9d4a5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  \n  ACQUIRE(USE), CACHESIZE(3072), CURRENTDATA(YES), CURRENTSERVER(),              \n  DBPROTOCOL(DRDA), NODEFER(PREPARE), DEGREE(1), DISCONNECT(EXPLICIT),           \n  DYNAMICRULES(RUN), ENCODING CCSID(500), EXPLAIN(NO),                           \n  FUNCTIONTS(2008-03-06-14.57.54.294632), GROUP MEMBER(), IMMEDWRITE(NO),        \n  ISOLATION(CS), KEEPDYNAMIC(NO), OPERATIVE(YES), OPTHINT(), OWNER(USER001 ),    \n  PATHSCHEMAS(), QUALIFIER(CAOPTII ), RELBOUND(L), RELEASE(DEALLOCATE),          \n  REOPT(NONE), SQLRULES(DB2), VALID(YES), VALIDATE(RUN)                          \n  \n  \n  TABLE DEPENDENCIES: [F] \n  \n  CAOPTII.DEPART                                                                 \n  CAOPTII.DIVISN                                                                 \n  CAOPTII.EMPLOY                                                                 \n  CAOPTII.JOB                                                                    \n  CAOPTII.TITLES                                                                 \n  \n  \n  TABLE SPACE DEPENDENCIES: [F] \n  \n  CAOPTII.DEPART                                                                 \n  CAOPTII.DIVISN                                                                 \n  CAOPTII.EMPLOY                                                                 \n  CAOPTII.JOB                                                                    \n \nThe Application Plan portion of the report displays the following information:\n[A]\nDisplays the application plan name.\n[B]\nDisplays the date and time when the plan was bound.\n[C]\nDisplays the ID of the user who bound the plan.\n[D]\nDisplays the comment associated with the plan, if applicable (not shown).\n[E]\nDisplays the bind options.\n[F]", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0c25c7c9d4a5-1", "text": "[E]\nDisplays the bind options.\n[F]\nDisplays the database objects on which the plan is dependent.\nThe package information is displayed for each package in the plan. If the DB2ACTIV option is specified, package\ninformation is displayed only for the packages that are active at the time of the ABEND. An example showing the package\ninformation follows:\n  *************************************                                                       \n  * PACKAGE SUMMARY FOR PLAN OPT2DEMO  *                                                       \n  *************************************                                                       \n  \n  ********************                                                                        \n  * PACKAGE DB2ADD     *  [A] \n 845", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "74fab8ddbf84-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  ********************                                                                        \n  \n  [B] COLLECTION-ID             OPT2DB2DEMO                                                             \n  [C] BIND DATE/TIME            06 MAR,2008 14.57.52                                                    \n  [D] PRE-COMPILE DATE/TIME     06 MAR,2008 14.57.22                                                    \n  [E] CONSISTENCY TOKEN         1841B4DE1D8BFF84                                                        \n  [F] DBRM LIBRARY              USER001.DBRMLIB.D810                                                    \n  \n  \n  [H] BIND OPTIONS:                                                                               \n  \n  CREATOR(USER001), DBPROTOCOL(DRDA), CURRENTDATA(C), DEGREE(1),                              \n  ENCODING CCSID(500), EXPLAIN(NO), FUNCTIONTS(2008-03-06-14.57.52.723939),                   \n  GROUP MEMBER(), IMMEDWRITE(NO), ISOLATION(CS), KEEPDYNAMIC(NO), OPERATIVE(YES),             \n  OPTHINT(), OWNER(USER001), PATHSCHEMAS(), QUALIFIER(CAOPTII), RELBOUND(L),                       \n  RELEASE(DEALLOCATE), REMOTE(NO), REOPT(NONE), SQLERROR(NOPACKAGE),                               \n  TYPE(BINDPKG), VALID(YES), VALIDATE(RUN)                                                         \n  \n  \n  PRE-COMPILE OPTIONS: [I] \n  \n  APOST, DEC(31), NOGRAPHIC, HOST(IBMCOB), NOTKATAKANA, PERIOD, VERSION()                          \n  \n  \n  TABLE DEPENDENCIES: [J] \n  \n  CAOPTII.DEPART                                                                                   \n  CAOPTII.DIVISN                                                                                   \n  CAOPTII.EMPLOY                                                                                   \n  CAOPTII.JOB", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "74fab8ddbf84-1", "text": "CAOPTII.EMPLOY                                                                                   \n  CAOPTII.JOB                                                                                      \n  CAOPTII.TITLES                                                                                   \n  \n  \n  TABLE SPACE DEPENDENCIES:                                                                        \n  \n  CAOPTII.DIVISN                  \n  CAOPTII.EMPLOY                  \n  CAOPTII.DEPART                  \n  CAOPTII.JOB                    \n \nThe Package Summary portion consists of the following information:\n[A]\nDisplays the package name.\n[B]\nDisplays the collection ID.\n[C]\nDisplays the bind date and time.\n[D]\nDisplays the precompile date and time.\n 846", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5a887f19a643-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n[E]\nDisplays the consistency token.\n[F]\nDisplays the library where the DBRM resides.\n[G]\nDisplays the comment associated with the package, if applicable (not shown).\n[H]\nDisplays the bind options.\n[I]\nDisplays the precompile options.\n[J]\nDisplays the database objects on which the package is dependent.\nFinally, SymDump  Batch displays the information for DBRMs within the plan not bound into a package. If the DB2ACTIV\noption is specified, DBRM information is displayed only for the DBRMs that are active at the time of the ABEND.\n   **********************************                                          \n   * DBRM SUMMARY FOR PLAN OPT2DEMO * [A] \n   **********************************                                          \n  \n   *****************                                                           \n   * DBRM DB2DEL   *                                                           \n   *****************                                                           \n  \n  [B] PRE-COMPILE DATE/TIME  06 MAR,2008 14.57.26                                 \n  [C] CONSISTENCY TOKEN      1841B4DF0D4A201A                                     \n  [D] DBRM LIBRARY           USER001.DBRMLIB.D810                                 \n  \n  \n   PRE-COMPILE OPTIONS: [E] \n  \n   APOST, DEC(31), NOGRAPHIC, HOST(IBMCOB), NOTKATAKANA, PERIOD, VERSION()     \n  \n \nThe DBRM Summary for Plan portion consists of the following information:\n[A]\nDisplays the DBRM name.\n[B]\nDisplays the precompile date and time.\n[C]\nDisplays the consistency token.\n[D]\nDisplays the library where the DBRM resides.\n[E]\nDisplays the precompile options.\n 847", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cde4c20fde24-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIDMS/DB  Report\nThe IDMS/DB  portion of the abend report is produced whenever a program that accesses an IDMS/DB  database using\nIDMS/DB  r12.0 or above abends. The reports are generated based on the SYSIDMS parameters specified. Information\nabout these parameters can be found in the IDMS/DB  documentation.\nThe first page of the IDMS/DB  report follows:\n  ******************                                                              \n  * CA-IDMS REPORT  *                                                              \n  ******************                                                              \n  \n  CA-IDMS abend trace         Tape Genlevel: G0GJ6M       Release: 1600  [A] \n  \n  User=USER02  [B]  Batch Local Job                                                 \n  \n  DBNODE=          DBNAME=EMPDEMO   DICTNODE=          DICTNAME=  [C] \n  \n  *****************                                                               \n  * SYSIDMS parms  *  [D] \n  *****************                                                               \n  \n    ECHO=ON                                                                       \n    DMCL=R160DMCL                                                                 \n    DBNAME=EMPDEMO                                                                \n    ABENDTRACE=ON  ABENDTRACE_ENTRIES=255                                         \n    ABENDTRACE_VIBSNAP=ON                                                         \n    ABENDTRACE_SUBSCHEMA_DISPLAY=ON                                                                          \n                        \n  \n  ************************************                                                                       \n                        \n  * DML trace for subschema=EMPSS01   *  [E] \n  ************************************                                                                       \n                        \n  \n  VERB=59  BIND SUBSCHEMA-->EMPSS01  DBNAME=EMPDEMO   PROGRAM=CAO2IDMS               Caller=CAO2IDMS \n DMLSEQ=000001  *** I D M S", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cde4c20fde24-1", "text": "DMLSEQ=000001  *** I D M S \n  VERB=48  BIND Record                    REC-->STRUCTURE            ADDR=000403A0       Caller=CAO2IDMS \n DMLSEQ=000002  *** I D M S \n  VERB=48  BIND Record                    REC-->SKILL                ADDR=000403B0       Caller=CAO2IDMS \n DMLSEQ=000003  *** I D M S \n  VERB=48  BIND Record     [F]              REC-->OFFICE               ADDR=00040400       Caller=CAO2IDMS \n DMLSEQ=000004  *** I D M S \n  VERB=48  BIND Record                    REC-->NON-HOSP-CLAIM       ADDR=00040450       Caller=CAO2IDMS \n DMLSEQ=000005  *** I D M S \n  VERB=48  BIND Record                    REC-->JOB                  ADDR=00040870       Caller=CAO2IDMS \n DMLSEQ=000006  *** I D M S \n  VERB=48  BIND Record                    REC-->INSURANCE-PLAN       ADDR=00040998       Caller=CAO2IDMS \n DMLSEQ=000007  *** I D M S \n  VERB=48  BIND Record                    REC-->HOSPITAL-CLAIM       ADDR=00040A20       Caller=CAO2IDMS \n DMLSEQ=000008  *** I D M S \n  VERB=48  BIND Record                    REC-->EXPERTISE            ADDR=00040B50       Caller=CAO2IDMS \n DMLSEQ=000009  *** I D M S \n 848", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "55ae6110e291-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  VERB=48  BIND Record                    REC-->EMPOSITION           ADDR=00040B60       Caller=CAO2IDMS \n DMLSEQ=000010  *** I D M S \n  VERB=48  BIND Record                    REC-->EMPLOYEE             ADDR=00040B80       Caller=CAO2IDMS \n DMLSEQ=000011  *** I D M S \n  VERB=48  BIND Record                    REC-->DEPARTMENT           ADDR=00040BF8       Caller=CAO2IDMS \n DMLSEQ=000012  *** I D M S \n  VERB=48  BIND Record                    REC-->DENTAL-CLAIM         ADDR=00040C30       Caller=CAO2IDMS \n DMLSEQ=000013  *** I D M S \n \nThe first page of the IDMS  report displays the following information:\n[A]\nDisplays the genlevel and version of IDMS/DB .\n[B]\nDisplays the userid used to submit the job and the job type.\n[C]\nDisplays the DBNODE, DBNAME, DICTNODE, and DICTNAME that were used.\n[D]\nDisplays the SYSIDMS parameters that were used.\n[E]\nDisplays the subschema name.\n[F]\nDisplays a trace of DML verbs for the subschema (the number of commands displayed in the trace is a user-\nspecifiable option).\nCurrencies for all areas, records, and sets in the subschema at the time of the ABEND are displayed. An example follows:\n  *************************************                                         \n  * Currencies for subschema=EMPSS01  *                                          \n  * Compiled: 2007-08-07  13.51.57    *                                         \n  *************************************", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "55ae6110e291-1", "text": "*************************************                                         \n  \n  Current DBKEY=X'01250505' (75013:5)         For Area EMP-DEMO-REGION           \n  Current DBKEY=X'01259801' (75160:1)         For Area ORG-DEMO-REGION           \n  \n  Current DBKEY=X'01259801' (75160:1)         For Record DEPARTMENT              \n  Current DBKEY=X'01250505' (75013:5)         For Record EMPLOYEE                \n  \n  Current DBKEY=X'01250505' (75013:5)         For Set DEPT-EMPLOYEE              \n    Owner DBKEY=X'01259601' (75158:1)         For Set DEPT-EMPLOYEE              \n    Prior DBKEY=X'01251701' (75031:1)         For Set DEPT-EMPLOYEE              \n     Next DBKEY=X'01251809' (75032:9)         For Set DEPT-EMPLOYEE              \n  \n  Current DBKEY=X'01250505' (75013:5)         For Set EMP-COVERAGE               \n    Owner DBKEY=X'01250505' (75013:5)         For Set EMP-COVERAGE               \n    Prior DBKEY=X'01256404' (75108:4)         For Set EMP-COVERAGE               \n \nBuffer information is displayed for each record in the subschema, as shown:\n    Record Name         Record Size   Bind Buff   'Prev' Buff   'Curr' Buff      \n    -----------         -----------   ---------   -----------   -----------     \n 849", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6cfc23d16e4e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  [A] [B] [C] [D] [E] \n     COVERAGE               20         00040FD8     * none *      * none *       \n     DENTAL-CLAIM           932        00040C30     * none *      * none *       \n     DEPARTMENT             56         00040BF8     363BC888      363BC8C0       \n     EMPLOYEE               120        00040B80     363BC908      363BC980       \n     EMPOSITION             32         00040B60     * none *      * none *       \n     EXPERTISE              12         00040B50     * none *      * none *       \n     HOSPITAL-CLAIM         300        00040A20     * none *      * none *       \n     INSURANCE-PLAN         132        00040998     * none *      * none *       \n     JOB                    296        00040870     * none *      * none *       \n     NON-HOSP-CLAIM         1052       00040450     * none *      * none *       \n     OFFICE                 76         00040400     * none *      * none *       \n     SKILL                  76         000403B0     * none *      * none *       \n     STRUCTURE              12         000403A0     * none *      * none *       \n \nThe buffer information consists of the following:\n[A]\nDisplays the name of the record.\n[B]\nDisplays the size of the bind buffer.\n[C]\nDisplays the address of the bind buffer.\n[D]\nDisplays previous buffer address.\n[E]\nDisplays current buffer address.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6cfc23d16e4e-1", "text": "[D]\nDisplays previous buffer address.\n[E]\nDisplays current buffer address.\nThe buffer information is followed by displays of the previous, current, and bind record images for accessed records, as\nshown:\n  ***********************************************                                                            \n                       \n  * Previous image for record DEPARTMENT            *   [A] \n  ***********************************************                                                            \n                       \n  \n  ADDRESS  363BC888     LENGTH 00000038  (DECIMAL 56)                                                        \n                        \n  ADDRESS  OFFSET                                                                                            \n                        \n  363BC888 000000   F2F0F0F0 40404040 40404040 40404040   40404040 40404040 40404040 40404040    *2000       \n                    *   \n  363BC8A8 000020   40404040 40404040 40404040 40404040   40404040 40404040                      *           \n            *           \n  \n  \n  ***********************************************                                                            \n                       \n  *  Current image for record DEPARTMENT            *   [B] \n  ***********************************************                                                            \n                       \n 850", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "85952c4b6cfc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  \n  ADDRESS  363BC8C0     LENGTH 00000038  (DECIMAL 56)                                                        \n                        \n  ADDRESS  OFFSET                                                                                            \n                        \n  363BC8C0 000000   F2F0F0F0 C1C3C3D6 E4D5E3C9 D5C740C1   D5C440D7 C1E8D9D6 D3D34040 40404040   \n *2000ACCOUNTING AND PAYROLL     *   \n  363BC8E0 000020   40404040 40404040 40404040 40404040   40F0F0F1 F1000000                      *           \n      0011  *           \n  \n  ************************************************                                                           \n                        \n  *     Bind image for record DEPARTMENT              *  [C] \n  ************************************************                                                           \n                        \n  \n  \n  LINE#   LEVEL/FIELD NAME                      VALUE/LOCATION                       DEFINITION               \n                           \n  ------  ----------------------------   -----------------------------      \n ----------------------------------------------- \n  000396  01 DEPARTMENT                       BLW=0000+000B40  (00040BF8)                                    \n                        \n  000397  02 DEPT-ID-0410                     9999                                   9(4)                     \n                           \n  000398  02 DEPT-NAME-0410                  *ACCOUNTING AND PAYROLL       *     X(45)                       \n                        \n                                         (+000032)   *             *                                         \n                        \n  000399  02 DEPT-HEAD-ID-0410               11                                  9(4)                        \n                        \n  000400  02 FILLER                             LOW-VALUES                           XXX     \n \n[A]", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "85952c4b6cfc-1", "text": "[A]\nDisplays the previous record image for the record.\n[B]\nDisplays the current record image for the record.\n[C]\nDisplays the bind record image for the record. The record image is mapped if these conditions are met:\n\u2022The MERGEDB option is ON.\n\u2022The record is defined in the most active COBOL, PL/I, or Assembler program.\n\u2022Symbolic information is available for that program.\nOtherwise, the address, length, and contents of the record are displayed in dump format.\nSnaps of the IDMS/DB  VIB (Variable IB50 for subschema) and IDMS/DB  VARS are displayed as following:\n ********************                                                                                        \n                     \n * CA-IDMS VIB snap  *                                                                                       \n                      \n 851", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7ee57fc4425a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n ********************                                                                                        \n                     \n  \n ADDRESS  36459008     LENGTH 00001658  (DECIMAL 5,720)                                                      \n                     \n ADDRESS  OFFSET                                                                                             \n                     \n 36459008 000000   E5C2F5F0 00000005 363BBD88 363BBE0E   363BBEE0 363BBEF2 363BBE2E 00000000  \n *VB50.......h.......\\...2........* \n 36459028 000020   00000000 00000000 00000000 00000000   3640DD08 3643A348 3645A6D4 3645B128  \n *................. ....t...wM....* \n 36459048 000040   00000000 00000000 00000000 00000000   00000000 00000000 00000008 36459B54  \n *................................* \n 36459068 000060   000642F8 D3D6C3D3 00000003 00000000   00075FC0 363BC2F0 363BC2F0 364593A0  \n *...8LOCL..........\u00ac{..B0..B0..l.* \n 36459088 000080   36459148 36459194 363BC2F0 00000000   00000000 40000000 00000000 08000000  \n *..j...jm..B0........ ...........*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7ee57fc4425a-1", "text": "*..j...jm..B0........ ...........* \n 364590A8 0000A0   0000FF08 C5D4D7C4 C5D4D640 00000000   3643AA70 3643A4F0 3645A6FC F0F0F0F0  \n *....EMPDEMO ..........u0..w.0000* \n 364590C8 0000C0   00000000 01250505 C3C1D6F2 C9C4D4E2   00000000 3643AA70 3643AA70 3643AA70  \n *........CAO2IDMS................* \n 364590E8 0000E0   00000022 00000000 00000000 3643AA70   3645A8F4 3643B6B4 3643B4D8 3645ADA4  \n *..................y4.......Q...u* \n 36459108 000100   00000000 0B220B22 0B220B22 00000000   00000000 01250505 3643AA70 00000000  \n *................................* \n 36459128 000120   01000000 00000000 00000000 3643A348   F0F461F0 F361F0F8 F1F3F0F6 F3F6F2F8  \n *..............t.04/03/0813063628* \n 36459148 000140   00000009 00000000 00000009 00000000   00000000 00000000 00000000 0000000C", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7ee57fc4425a-2", "text": "*................................* \n 36459168 000160   0000000B 00000019 00000000 00000000   00000000 00000000 00000000 00000001  \n *................................* \n 36459188 000180   00000003 D3D6C3D3 00000003 00000000   00000000 00000000 00000000 00000000  \n *....LOCL........................*\n .                     .                                              .                                      \n         .      \n .                     .                                              .                                      \n         .  \n .                     .                                              .                                      \n         .  \n *********************                                                                                       \n                       \n * CA-IDMS VARS snap  *                                                                                      \n                        \n *********************                                                                                       \n                       \n  \n ADDRESS  3645A6D4     LENGTH 00000A54  (DECIMAL 2,644)                                                      \n                       \n ADDRESS  OFFSET                                                                                             \n                       \n 3645A6D4 000000   E5C1D9E2 40404040 C5D4D7E2 E2F0F140   00000000 3641DC98 00000000 00000000   *VARS   \n EMPSS01 .......q........*   \n 852", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7d9b1b379463-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 3645A6F4 000020   3641DC98 00000000 04038003 01250505   01250505 3643AA70 36459008 3641480C  \n *...q............................*   \n 3645A714 000040   00000000 00000000 00000000 00000000   FFFFFFFF 000124F9 0001252A 0001252A  \n *.......................9........*   \n 3645A734 000060   000124FE 0001252A 0001252A 000124FA   000124FD 000124FD 04038003 FFFFFFFF  \n *................................*   \n 3645A754 000080   FFFFFFFF 00000000 36459008 364149E0   00000000 00000000 00000000 00000000  \n *...............\\................*   \n 3645A774 0000A0   FFFFFFFF 0001255D 00012575 00012575   00012562 00012575 00012575 0001255E  \n *.......).......................;*   \n 3645A794 0000C0   00012561 00012561 04038003 01259801   01259801 3643A9D8 36459008 36414BB4  \n *.../.../......q...q...zQ........*   \n 3645A7B4 0000E0   00000000 00000000 00000000 00000000   FFFFFFFF 0001258F 000125A7 000125A7", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7d9b1b379463-1", "text": "*...........................x...x*   \n 3645A7D4 000100   00012594 000125A7 000125A7 00012590   00012593 00012593 FFFFFFFF FFFFFFFF  \n *...m...x...x.......l...l........*   \n 3645A7F4 000120   FFFFFFFF 00000000 00000000 00000000   00000000 00000000 00000000 FFFFFFFF  \n *................................*   \n 3645A814 000140   0005B0B0 FFFFFFFF FFFFFFFF FFFFFFFF   00000000 00000000 00000000 00000000  \n *................................*   \n 3645A834 000160   00000000 00000000 FFFFFFFF 0005B0B0   FFFFFFFF FFFFFFFF FFFFFFFF 00000000  \n *................................*   \n 3645A854 000180   00000000 00000000 00000000 00000000   00000000 FFFFFFFF 0005B0B0 FFFFFFFF  \n *................................*  \n \nFinally, SymDump  Batch shows the following areas:\n                            SUBSCHEMA=EMPSS01                                                                \n                        \n                Compiled=2007-08-07  13.51.57           [A] \n             Subschema Structure is Network and Unbound   [B] \n  \n      Area Name          Segment                                                                             \n                          \n  -----------------    --------                                                                              \n                        \n  \n  EMP-DEMO-REGION        n/a                                                                                 \n                        \n  INS-DEMO-REGION        n/a  [C] \n  ORG-DEMO-REGION        n/a", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7d9b1b379463-2", "text": "ORG-DEMO-REGION        n/a                                                                                 \n                        \n  \n      Record Name                Stored  Rec ID      Area Name     Data Length   Prefix Length    Procedures \n         \n  --------------------------     ------  ------  ---------------   -----------   -------------  \n ----------------------  \n  \n  COVERAGE                       VIA     400     INS-DEMO-REGION   20             20                         \n       \n  DENTAL-CLAIM                   VIA     405     INS-DEMO-REGION   936            12                         \n       \n 853", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7983531cef23-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  DEPARTMENT         [D]         CALC    410     ORG-DEMO-REGION   56             16                         \n       \n  EMPLOYEE                       CALC    415     EMP-DEMO-REGION   120            72                         \n       \n  EMPOSITION                     VIA     420     EMP-DEMO-REGION   32             24                         \n       \n  EXPERTISE                      VIA     425     EMP-DEMO-REGION   12             20                         \n       \n  HOSPITAL-CLAIM                 VIA     430     INS-DEMO-REGION   300            8                          \n      \n  INSURANCE-PLAN                 CALC    435     INS-DEMO-REGION   132            8                          \n      \n  JOB                            CALC    440     ORG-DEMO-REGION   300            24        IDMSCOMP Before\n STORE   \n                                                                                            IDMSCOMP Before\n MODIFY  \n                                                                                            IDMSDCOM After GET\n      \n  .          .   \n  .          .   \n .           .   \n  \n  Chain Sorted-> CALC            Next,Prior                                                                  \n    \n  Owner -------> SR1             Next=00  Prior=04                                                           \n    \n  Member ------> SR6   [E]         Next=00  Prior=04                                                         \n      \n  Member ------> SR7             Next=00  Prior=04                                                           \n    \n                         Ckey  Offset=16   Length=16     Data Type=Character                                  \n                                   \n  Member ------> DEPARTMENT                              Next=00  Prior=04                                    \n                           \n                     Ckey  Offset=16   Length=4      Data Type=Numeric (Unsigned)                             \n                               \n  Member ------> EMPLOYEE                                Next=00  Prior=04", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7983531cef23-1", "text": "Member ------> EMPLOYEE                                Next=00  Prior=04                                    \n                           \n                     Ckey  Offset=72   Length=4      Data Type=Numeric (Unsigned)                             \n                               \n  Member ------> INSURANCE-PLAN                          Next=00  Prior=04                                    \n                           \n                     Ckey  Offset=8    Length=3      Data Type=Character                                      \n                               \n  Member ------> JOB                                     Next=00  Prior=04                                    \n                           \n                     Ckey  Offset=28   Length=4      Data Type=Numeric (Unsigned)                             \n                               \n  Member ------> OFFICE                                  Next=00  Prior=04                                    \n                           \n                     Ckey  Offset=16   Length=3      Data Type=Character                                      \n                               \n 854", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d69c2d7f6145-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  Member ------> SKILL                                   Next=00  Prior=04                                    \n                           \n                     Ckey  Offset=20   Length=4      Data Type=Numeric (Unsigned)                             \n                               \n  \n  Chain Last --> COVERAGE-CLAIMS                         Next,Prior                                           \n                           \n  Owner -------> COVERAGE                                Next=12  Prior=16                                    \n                           \n  Via Member --> DENTAL-CLAIM                            Next=00  Prior=04                                    \n                           \n  Via Member --> HOSPITAL-CLAIM                          Next=00  Prior=04                                    \n                           \n  Via Member --> NON-HOSP-CLAIM                          Next=00  Prior=04       \n \nThe preceding screen consists of the following information:\n[A]\nDisplays the compile date and time of the subschema.\n[B]\nDisplays the subschema structure and whether it is bound or unbound.\n[C]\nDisplays the associated segment for each area, if applicable.\n[D]\nDisplays detailed information about each record in the subschema, including storage mode, record ID, area name,\ndata length, prefix length, and db procedures.\n[E]\nDisplays detailed information about each set in the subschema, including owner record, member records, set\ntype, and set pointers.\nSnap Report\nThe Snap report lets you view a snapshot of a program's data areas from various points of execution without forcing the\nprogram to abend. Each report is produced by calling the snap interface program, CAODSNAP, from any COBOL, PL/\nI, or Assembler program. Much of the information in this report is similar to the information provided in an abend report;\nhowever, only the most active program (the one which called CAODSNAP) is included in the report.\nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d69c2d7f6145-1", "text": "NOTE\nEach call to CAODSNAP generates a separate Snap report in your central VSAM repository. If your program\ncontains multiple snap calls (or a snap call within a loop), you may want to write the output to the CAIPRINT DD\nalone, to avoid flooding  the repository.\nSnap Page\nThe Snap report begins with some specific information pertaining to the snap.\n********************\n* SNAP OF CAO2DEMO *\n********************\n \nCOMPILED ON 23 APR,2004 AT 12.02.38 WITH COBOL II 1.4.0\n 855", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5160b6d65aac-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCOMPILE OPTIONS: ADV, APOST, NOAWO, NOCMPR2, DATA(31), DBCS, NODECK, NODUMP,\n                 DYNAM, NOFASTSRT, NOFDUMP, NOLIB, LIST, MAP, NONAME, NONUMBER,\n                 OBJECT, NOOFFSET, NOOPTIMIZE, NUMPROC(PFD), RENT, RESIDENT,\n                 NOSEQUENCE, SOURCE, NOSSRANGE, NOTERM, NOTEST, TRUNC(STD),\n                 NOVBREF, NOWORD, XREF, ZWB\n \nSYMBOLIC INFORMATION RETRIEVED FROM AD1DEV.MIKED.PROTSYM\nMEMBER: CAO2DEMO  DATE: 23 APR,2004  TIME: 12.02.38   TYPE: PROTSYM\n \nLINKED ON 23 APR 2004 AT 00:00:00\nLOAD LIBRARY: MIKED.QA.LOAD\nMODULE LENGTH: 00006528  (DECIMAL 25,896)\nLINK OPTIONS: AC(0), AMODE(31), NOOVLY, NORENT, NOREUS, RMODE(24)\n \n******************************\n* LAST STATEMENT BEFORE SNAP *\n******************************\n \nPROGRAM: CAO2DEMO  OFFSET: 004F92  LINE: 001413\n \n         IF PARM-MODE = 'DTE'\n \n LINE#    LEVEL/FIELD NAME                  VALUE/\nLOCATION                  DEFINITION                                          \n ------  -----------------------------  -----------------------------   ----------------------------------------------- \n000157      03 PARM-MODE                            *DTE*                                   X(3)    \n \nSNAP WAS CALLED FROM ADDRESS 0E505A80 AT OFFSET +004FA8 IN PROGRAM CAO2DEMO", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5160b6d65aac-1", "text": "SNAP COUNT IS       1\n \nENTRY POINT ADDRESS IS 0E500AD8 AT OFFSET +000000 IN PROGRAM CAO2DEMO\nENTRY COUNT IS      1\nThe contents of a Snap report depends on the language of the program that called the snap interface program\nCAODSNAP. The preceding screen was produced by a call from a COBOL program. For all languages, program\ninformation is provided only for the most active program, but may include multiple active procedures for PL/I.\nThe Snap report contains the following program information:\nCOBOL\n\u2022Compile and link statistics\n\u2022Last statement or instruction before the snapshot\n\u2022Data division displays\n\u2022Registers\n\u2022PGT, TGT, and DSA\n 856", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "73dc1745fcd1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPL/I\n\u2022Compile and link statistics\n\u2022Last statement executed in each active procedure\n\u2022Variables for each active procedure\n\u2022Last registers for each active procedure\n\u2022DSA for each active procedure\n\u2022Static and external storage dump\n\u2022Program storage dump\nAssembler\n\u2022Link statistics\n\u2022Program status word\n\u2022Registers, including access registers\n\u2022Addressable storage displays\n\u2022Program storage dump\nIf the application is connected to an IMS, DB2, or IDMS  database at the time of the Snap call, the appropriate database\nsection will be included in the Snap report.\nCAIOPTS File Processing Report\nThe CAIOPTS File Processing report displays the input options read from the data set defined by the CAIOPTS DD, if\npresent. The report displays each 80-byte record exactly as they appear in the CAIOPTS data set.\n....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8                      \n  PRTLIB CAI.PRTLIB                                                                                   \n  PRTREPT BOTH                                                                                   \n  REGMAX (128,256)\n  SYMDSN CAI.PROTSYM\n  DUMP OFF                                                                                        \nCAPC012I INPUT OPTION DISPLAY COMPLETE.                                                            \nReport Summary\nThis report is produced during termination. The report lists alphabetically the options that were in effect at the time the\nreport was generated.\nThe operating system is displayed at the top of the report as z/OS.\nAn example of the Report Summary appears next:\nEXECUTION ON: Z/OS                                                              \n                                                                                \n  EXECUTION OPTIONS IN EFFECT:                  FORMATTING OPTIONS IN EFFECT:   \n                                                                                \n  ACB           OFF                             ASMINST     ON  \n  AMB           OFF                             BINFRMT     DEC", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "73dc1745fcd1-1", "text": "AMB           OFF                             BINFRMT     DEC \n  AMBL          OFF                             FILES       ON  \n  BINDER        ON                              FIRST128    OFF \n  COBONLY       OFF                             GRPADDR     ON  \n  DB2ACTIV      OFF                             LINKAGE     ALL \n 857", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "74a2325c8676-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  DCB           OFF                             LISTLINE    0   \n  DEB           OFF                             LOCALSTOR   ALL \n  DUMP          ON                              MEMMAP      ON  \n  IOB           OFF                             MERGEDB     ON  \n  LOGROS        ON                              MRGAUTO     ON  \n  LOGTSO        ON                              MRGBASED    ON  \n  LOGUNI        OFF                             MRGCNTLD    ON  \n  PLH           OFF                             MRGDSECT    ON  \n  PRTLIB        CAI.PRTLIB                      MRGFILES    ON  \n  PRTREPT       BOTH                            MRGLINK     ON  \n  READLL         ON                             MRGLOCAL    ON  \n  REGMAX        (128,256)                       MRGPARMS    ON  \n  RPL           OFF                             MRGSTAT     ON  \n  SAVEHEAP      OFF                             MRGWORK     ON  \n  SCRSZ80       OFF                             NDVRASM     OFF \n  SNAP          0                               NDVRDSN     \n  SYMDSN        CAI.PROTSYM                     NDVRDSS     OFF \n  UCB           OFF                             OCCURS      1   \n  VSAMCAT       OFF                             SAVEAREA    ON  \n  VSAMIDX       OFF                             SHOWHEAP    OFF \n  WTO           ON                              SHOWUNMRG   TBLS    \n                                                WORKSTOR    ALL \n                                                                               \nMerged Versus Dumped Data Displays\nSymDump  Batch displays all of the storage areas for your COBOL, PL/I, or Assembler program. If symbolic information is\navailable for the program, a variety of merging options are provided for mapping variable names and definitions onto the\ncorresponding storage areas. Otherwise, storage areas are displayed in dump format.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "74a2325c8676-1", "text": "corresponding storage areas. Otherwise, storage areas are displayed in dump format.\nMerged Display\nThe following list describes the merging options:\nMERGEDB ON|OFF\nMerges symbolic names onto database reports.\nMRGAUTO ON|OFF\nMerges symbolic names onto PL/I automatic storage.\nMRGBASED ON|OFF\nMerges symbolic names onto PL/I based variable storage.\nMRGCNTLD ON|OFF\nMerges symbolic names onto PL/I controlled storage.\nMRGDATA ON|OFF\nMerges symbolic names onto all data areas.\nMRGDSECT ON|OFF\nMerges symbolic names onto Assembler DSECT storage.\nMRGFILES ON|OFF\nMerges symbolic names onto file section for COBOL.\nMRGLINK ON|OFF\nMerges symbolic names onto linkage section for COBOL.\n 858", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1e3ae3b0d792-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMRGLOCAL ON|OFF\nMerges symbolic names onto local storage for COBOL.\nMRGPARMS ON|OFF\nMerges symbolic names onto PL/I parameter storage.\nMRGSTAT ON|OFF\nMerges symbolic names onto PL/I static storage.\nMRGWORK ON|OFF\nMerges symbolic names onto working storage for COBOL.\nThe following example shows a merged data display for the WORKING-STORAGE section of a COBOL program.\n***************************\n* WORKING-STORAGE SECTION *\n***************************\n[A]                                                                               [D]   [E]    \n LINE#    LEVEL/FIELD NAME              VALUE/LOCATION                          \n DEFINITION                                          \n ------  -----------------------------  --------------------------------------  ----------------------------------------    \n000136  77 FILLER                          [G]    *THIS PROGRAM IS PROPRIETARY PROP*  X(80)   \n[B]         [C]                         (+000032) *ERTY OF COMPUTER ASSOCIATES INTE*  \n                                        (+000064) *RNATIONAL, INC. *  \n000139  77 FILLER                                 *COPYRIGHT (C) 1986-1999 BY COMP*   X(80)   \n                                   [H]  (+000032) *UTER ASSOCIATES INTERNATIONAL, I*  \n                                        (+000064) *NC.             *  \n000142  77 ERROR-FLAG                            ZEROS                                        X(1)    \n000143  77 DATA-PICX10                            ALL '&'                                     X(10)   \n000144  77 ROW-3D                                 1                                           99 BINARY   \n000145  77 COLUMN-3D                              1                                           99 BINARY   \n000146  77 RANGE-3D                               1                                           99 BINARY", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1e3ae3b0d792-1", "text": "000146  77 RANGE-3D                               1                                           99 BINARY   \n000148  01 PARAMETER-ONE                        BLW=0000+0000D0  (0E77A528) [F]\n000149  03 FILLER                                 *PARAMETERONE*                              X(12)   \n000154  01 PARM-PASSED-BY-JCL                 BLW=0000+0000E0  (0E77A538)\n000155  03 PARM-MSG                               *WSINIT  *                                  X(8)    \n000156  03 PARM-FLAG                              *WSINIT  *                                  X(8)    \n000157  03 PARM-MODE                              *DTE*                                       X(3)    \n000159  01 TABLE-1                                  BLW=0000+0000F8  (0E77A550)   \n000160  05 ARRAY(1)                                 BLW=0000+0000F8  (0E77A550)        OCCURS 5    \n000161  10 DATA-NAME1(1)                         ALL '&'                                       XXX \n000162  10 DATA-NAME2(1) [I]                    ALL '&'                                XXX \n          <UNMERGED DATA FOR ARRAY> [J]    X        '50505050505050505050505050505050' LENGTH  24  \n                                  (+000016)    X    '5050505050505050'  \n \n    :     :\n    :     :\n \n000315  01 LIST-1M                               BLW=0001+003860  (0E77ECB8)           PACKED-DECIMAL", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1e3ae3b0d792-2", "text": "000316  03 LIST-1(1)                      ? X   '50505050'                                  S9(6) PACKED-\nDECIMAL OCCURS 100 \n 859", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3253f720a47c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n           <UNMERGED DATA FOR LIST-1>     X '50505050505050505050505050505050'         LENGTH  396 \n                                             LINES    000016-000368 SAME AS ABOVE   \n                                     (+000384) X' 505050505050505050505050'\n            INX                                  473380382                                  INDEX=0001 [K]    \nA merged data display for the WORKING-STORAGE section of a COBOL program contains the following information:\n[A]\nDisplays the header describing the report columns.\n[B]\nDisplays the source line number where the data item was defined.\n[C]\nDisplays the level number and name of the data item.\n[D]\nDisplays the definition for the field. For COBOL, this includes the PICTURE and USAGE clauses and any\nREDEFINES or OCCURS clauses for the field.\n[E]\nFor some fields, indicates one of the following USAGE types of the data item:\n\u2022COMP and COMP-4 items are identified as BINARY.\n\u2022COMP-1 items are identified as FLOATING-POINT.\n\u2022COMP-2 items are identified as LONG FLOATING-POINT.\n\u2022COMP-3 items are identified as PACKED-DECIMAL.\n\u2022DISPLAY-1 items are identified as DBCS.\n[F]\nDisplays the base locator and displacement of the item for group items. The address of the item is also identified,\nin parentheses. (The base locator prints as BL, BLL, or SBL for OS/VS COBOL and as BLF, BLW, BLL, BLK, BLV,\nor BLX for COBOL II and above. For COBOL II and above, the displacement may exceed 4 KB.) If the GRPADDR", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3253f720a47c-1", "text": "option is set to OFF, this information is suppressed.\n[G]\nDisplays the value of the item for elementary items. The value is displayed in a format determined by the USAGE\nof the data item and the validity of the data.\nFor example:\n\u2022DISPLAY data is shown in display format\n\u2022PACKED-DECIMAL, BINARY, and INDEX data are shown in decimal display format (DEC) or hexadecimal\nformat (HEX), depending on the value of the BINFRMT option.\n\u2022POINTER, PROCEDURE-POINTER, FLOATING-POINT and DBCS data are shown in hexadecimal format (for\nexample, X'nnnnnnnn').\nIf the value of a data item is invalid, a question mark(?) precedes the data value and the data is displayed in\nhexadecimal format.\nIf the address of a data item is invalid, a question mark(?) precedes the data value column. The words 'INVALID\nADDRESS' are displayed in the value column, followed by the address, in parentheses.\n[H]\nDisplays the offset of the continued data (from the beginning of the data item) in decimal, on each successive line.\nIf the data is too long to fit on the current line (32 bytes for display format, 16 bytes for hexadecimal format) it is\ncontinued on the next line.\n[I]\nDisplays the first n occurrences of the table in merged format (where n is the OCCURS option value) if the value\nspecified in the OCCURS option is less than the number of occurrences defined to the table. The rest of the table\n 860", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2c1a68a3732e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nis identified as '<UNMERGED DATA FOR tablename>'. The length is displayed in the DEFINITION column and\nthe data is displayed in hexadecimal format.\nThe OCCURS option was set to the default value of 1 for this report. The maximum value for the OCCURS option\nis 16777215.\n[J]\nIndicates the mapping status of the data in COBOL programs. If the COBOL program contains data that does\nnot map to a data item (such as slack bytes or unmerged data items from a COPY... SUPPRESS statement), the\ndata is identified as '<UNMERGED DATA>'. The length is displayed in the DEFINITION column and the data is\ndisplayed in hexadecimal format.\n[K]\nDisplays the index name, cell number, and current value on the line following the OCCURS data item if an\nINDEXED clause is specified on an OCCURS data item. If the current index value cannot be determined, 'N/A' is\ndisplayed in the value column.\nWhen displaying a variable length table, if the size of the table has not yet been defined or cannot be determined, the\nmaximum table size is used.\nDumped Display\nAn example of a dumped report follows:\n***************************                                                                                             \n* WORKING-\nSTORAGE SECTION *                                                                                                        \n***************************                                                                                                        \nADDRESS[A]32FB7128 [B]LENGTH 00000DAE  (DECIMAL 3,502)                                                                             \nBLW=0000  +000000 F0F00000 00000000 00000000 00000000 [E]\n F0F5C000 00000000 00000000 00000000 [F]*00..............05{.............*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2c1a68a3732e-1", "text": "[C]    [D]+000020 F0F5F000 00000000 003B0000 00000000    \n 000A0000 00000000 00000000 00000000   *050.............................*   \n          +000040 001C0000 00000000 002B0000 00000000    \n 00070000 00000000 F0000000 00000000   *........................0.......*   \n          +000060 00000000 00000000 00000000 00000000    \n 00000000 00000000 00000000 00000000   *................................*   \n          +000080 00010000 00000000 00000000 00000000    \n 00010000 00000000 00000000 00000000   *................................*   \n          +0000A0 00000000 00000000 00000000 00000000    \n FFFF0000 00000000 FFFF0000 00000000   *................................*   \n          +0000C0 00050000 00000000 00000000 00000000    \n 00000000 00000000 E5D7E4E3 40404040   *........................VPUT    *   \n          +0000E0 E5C7C5E3 40404040 C3C8C1D9 40404040    \n E5D9C5D7 D3C1C3C5 E5C4C5C6 C9D5C540   *VGET    CHAR    VREPLACEVDEFINE *    \nA dumped report contains the following information:\n[A]\nDisplays the address of the dumped storage.\n[B]", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2c1a68a3732e-2", "text": "[A]\nDisplays the address of the dumped storage.\n[B]\nDisplays the length of the dumped storage in decimal and hexadecimal.\n 861", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4ce68da67d5d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n[C]\nDisplays the base locator cell associated with the dumped storage (The base locator prints as BL, BLL, or SBL for\nOS/VS COBOL and as BLF, BLW, BLL, BLK, BLV, or BLX for COBOL II and above.)\n[D]\nDisplays the displacement of the storage from the specified base locator, in hexadecimal. (For COBOL II and\nabove, the displacement can exceed 4 KB.)\n[E]\nDisplays the data in hexadecimal format.\n[F]\nDisplays the data in display format.\nCAIPRINT Repository Viewer\nThe CAIPRINT Repository Viewer can be used to view SymDump  Batch reports that are written to your central VSAM\nrepository. Each report is automatically written to the repository defined in your run-time defaults member, CAOUDFRX, if\nthe PRTREPT option is set to REPOS or BOTH.\nThe CAIPRINT Repository Viewer provides the following benefits:\n\u2022A single interface for viewing, printing, and maintaining SymDump  Batch reports\n\u2022Easy access to multiple CAIPRINT repositories\n\u2022View-time control over the formatting options\n\u2022View-time addition of symbolic information to your reports\n\u2022Utilities for adding, viewing, printing, and maintaining symbolic information\nDuring installation, the ISPF Primary Option menu must be updated to include a selection for the CAIPRINT Repository\nViewer. If this is not completed, see Installing for additional information.\nSelect the appropriate option from the menu to start the viewer. The Report Index panel displays.\nReport Index\nThe Report Index panel displays all SymDump  Batch reports that are written to the selected repository, sorted in\ndescending order by date and time.\n CA SymDump Batch ------------ Report Index ------------------- Line 1 of 68\n Command ===>                                                   Scroll ===> CSR", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4ce68da67d5d-1", "text": "Command ===>                                                   Scroll ===> CSR\n CAPI100I Repository contains 68 report(s) -------------------------------------\n Repository Dsname: CAI.PRTLIB                                       \n    1754 Data Records      680 Used    38.7% Full                              \n Filter: Jobname *        Step/Tsk *        Program *        Offset *          \n         Comp    *        UserID   *        Lock    *        System *          \n ------------------------------------------------------------------------- Lvl 1\n Cmd  JobName   Step/Tsk  Program   Offset   Comp    Date        Time   UserId \n  .   WANDA07D  TESTCOB2  SUBCOB    000026A  S=0C7   2007/03/05  12.41  TSTUSR7\n  .   USRSC01A  STEP1     CARXDEMA  000013C  S=0C7   2007/03/02  18.35  TSTUSR1\n  .   USER002R  RUN       n/a       n/a      RC=0000 2007/03/02  18.34  TSTUSR3\n  .   WANDA07D  TESTCOB2  SUBCOB    000026A  S=0C7   2007/03/02  18.20  TSTUSR7\n  .   WANDA07C  TESTCOB2  SUBCOB    000026A  S=0C7   2007/03/02  17.09  TSTUSR7\n  .   WANDA07C  TESTCOB2  SUBCOB    000026A  S=0C7   2007/03/02  16.25  TSTUSR7", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4ce68da67d5d-2", "text": ".   WANDA07A  S0C1      RENTSCAN  0000AFA  S=0C2   2007/03/01  11.00  TSTUSR7\n  .   USER002A  RUN       CAOEDEMO  0003D48  S=0C7   2007/03/01  10.41  TSTUSR3\n  .   USER002A  RUN       CAOEDEMO  0003D48  S=0C7   2007/03/01  10.34  TSTUSR7\n 862", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "16b97ba960be-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  .   USER002A  RUN       CAOEDEMO  0003D48  S=0C7   2007/02/28  10.06  USER01 \n  .   WANDA07Z  S0C1      TESTSCAN  0000AFA  S=0C2   2007/02/28  09.43  USER01 \n  .   USRSC01B  RUN       CARXDEMA  000013C  S=0C7   2007/02/23  14.34  USER02 \n  .   USRSC01A  RUN       CEEPLPKA  00BAE7A  U=0666  2007/02/23  14.33  USER02 \n  .   USRSC01A  STEP1     CARXDEMA  000013C  S=0C7   2007/02/23  14.28  USER02 \n  .   USRSC01A  RUN       ABEND1    0000014  U=0001  2007/02/21  15.26  TSTUSR2\n \nWhen the viewer is started for the first time, the repository data set name is determined using your installation defaults.\nFor all subsequent executions, the value is retrieved from your personal user profile.\nSelect a Repository\nYou have an option of selecting a repository of your choice.\nFollow these steps:\n1.Use the SETINDEX command to switch to a different repository.\nYou are prompted for the new repository name as shown in the following screen:\n CA SymDump Batch---------- Report Index ------------------- Line 1 of 68\n Command ===>                                                   Scroll ===> CSR \n -------------------------------------------------------------------------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "16b97ba960be-1", "text": "Command ===>                                                   Scroll ===> CSR \n -------------------------------------------------------------------------------\n Repository +------------------------------------------------------+            \n    1754 Da |                                                      |            \n Filter: Jo | Enter Repository Dsname:                             |            \n         Co |                                                      |            \n ---------- | ===>                                                 | ----- Lvl 1\n Cmd  JobNa |                                                      |    UserId  \n  .   WANDA +------------------------------------------------------+ 1  TSTUSR7 \n  .   USRSC01A  STEP1     CARXDEMA  000013C  S=0C7   2007/03/02  18.35  TSTUSR1 \n  .   USER002R  RUN       n/a       n/a      RC=0000 2007/03/02  18.34  TSTUSR3 \n  .   WANDA07D  TESTCOB2  SUBCOB    000026A  S=0C7   2007/03/02  18.20  TSTUSR7 \n  .   WANDA07C  TESTCOB2  SUBCOB    000026A  S=0C7   2007/03/02  17.09  TSTUSR7 \n  .   WANDA07C  TESTCOB2  SUBCOB    000026A  S=0C7   2007/03/02  16.25  TSTUSR7 \n  .   WANDA07A  S0C1      RENTSCAN  0000AFA  S=0C2   2007/03/01  11.00  TSTUSR7", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "16b97ba960be-2", "text": ".   USER002A  RUN       CAOEDEMO  0003D48  S=0C7   2007/03/01  10.41  TSTUSR3 \n  .   USER002A  RUN       CAOEDEMO  0003D48  S=0C7   2007/03/01  10.34  TSTUSR7 \n  .   USER002A  RUN       CAOEDEMO  0003D48  S=0C7   2007/02/28  10.06  USER01  \n  .   WANDA07Z  S0C1      TESTSCAN  0000AFA  S=0C2   2007/02/28  09.43  USER01  \n  .   USRSC01B  RUN       CARXDEMA  000013C  S=0C7   2007/02/23  14.34  USER02  \n  .   USRSC01A  RUN       CEEPLPKA  00BAE7A  U=0666  2007/02/23  14.33  USER02  \n  .   USRSC01A  STEP1     CARXDEMA  000013C  S=0C7   2007/02/23  14.28  USER02  \n  .   USRSC01A  RUN       ABEND1    0000014  U=0001  2007/02/21  15.26  TSTUSR2\n \n2.Type the new data set name, fully qualified and enclosed in single quotation marks, or leave this field blank to view the\ndefault repository for the current system.\nReport Index Fields", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "16b97ba960be-3", "text": "default repository for the current system.\nReport Index Fields\nA static information area is displayed at the top of the display, immediately below the command line and separated by\ndashed lines.\nThe following information is displayed in this area:\n 863", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "88a727b54adb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nRepository Dsname\nDisplays the data set name of the currently selected repository.\nData Records\nDisplays the number of data records available in the selected repository.\nUsed\nDisplays the number of used data records in the selected repository.\nFull\nDisplays the percentage of used data records.\nFilters\nLists eight updatable fields (Jobname, Step/Tsk, Program, Offst, Comp, UserID, Lock, System) that can be used\nto filter the list of reports that can be selected.\nThe final static line in this display is the highlighted header line, containing all of the column headers for the report list.\nThe data portion of the display is horizontally and vertically scrollable and can be sorted in ascending or descending order\non any column header.\nFor each report in the list, the following information is displayed:\nJob\nDisplays the name of the job that produced the report.\nStep/Tsk\nDisplays the name of the step that produced the report or the IMS DC task ID if the report was generated in an\nIMS DC environment under LE.\nProgram\nDisplays the name of the abending program that caused the report to be produced.\nOffset\nDisplays the offset in the abending program where the abend occurred.\nComp\nDisplays the completion code from the step that produced the report.\nDate\nDisplays the date on which the report was produced.\nTime\nDisplays the time when the report was produced.\nUserid\nDisplays the name of user who submitted the job that produced the report.\nLock\nDisplays the name of the user that owns a lock on the report to prevent deletion.\nSystem\nDisplays the name of the system on which the report was created.\nAsid\nDisplays the address space ID of the job which created the report.\n#Recs\nDisplays the number of physical repository records occupied by the report.\nS I P", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "88a727b54adb-1", "text": "#Recs\nDisplays the number of physical repository records occupied by the report.\nS I P\nIndicates whether the report contains Snaps, Intercepts, or Parmchk.\n 864", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2c96ac324489-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPrimary Commands\nThe following primary commands are available from the Report Index panel:\nBOTTOM\nScrolls the display to the last line.\nDOWN\nScrolls the display forward.\nFIND\nLocates text in the current display.\nFM\nInvokes File Master Plus  to view a data set.\nHELP\nRequests help for a command, message, or topic.\nKEEP\nAdds data from the current display to the Keep Window.\nLEFT\nScrolls the display to the left.\nOPTIONS\nDisplays the current installation options in effect.\nPRINT\nPrints all or part of the current display.\nPROFILE\nViews and updates display preferences.\nREFRESH\nRefreshes the current display.\nRFIND\nRepeats a previous FIND command.\nRIGHT\nScrolls the display to the right.\nSET\nSelects a new repository.\nSORT\nSorts the current display on any column heading.\nSYM\nDisplays the Symbolic Utilities menu.\nTOP\nScrolls the display to the first line.\nUP\nScrolls the display backward.\nA description of each primary command can be found later in this section.\nFor viewing the online help for any primary command, type HELP command-name.\nLine Commands\nThe following line commands can be entered in the Cmd column:\n 865", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e5cea22670a1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDelete a Report\nYou can delete a report that is not required from the repository.\nFollow these steps:\n1.Type the D line command.\nYou are prompted for confirmation to prevent accidental deletion as shown in the following screen:\n CA SymDump Batch ------------ Report Index ------------------- Line 1 of 68\n Command ===>                                                   Scroll ===> CSR\n -------------------------------------------------------------------------------\n Repository  +----------------------------------------------------+            \n    1754 Dat | Press ENTER to confirm the delete request for      |            \n Filter: Job | the selected report:                               | *          \n         Com |                                                    | *          \n ----------- | Program: CARXDEMA  Offset: 000013C  Comp: S=0C7    | ------ Lvl 1\n Cmd  JobNam | Created: 2007/02/23 at 14.28                       | e   UserId \n  .   WANDA0 |                                                    | 41  TSTUSR7\n  .   USRSC0 | Press END to cancel the delete request.            | 35  TSTUSR1\n  .   USER00 |                                                    | 34  TSTUSR3\n  .   WANDA0 | Display this message? (Y/N) ===> Y                 | 20  TSTUSR7\n  .   WANDA0 +----------------------------------------------------+ 09  TSTUSR7\n  .   WANDA07C  TESTCOB2  SUBCOB    000026A  S=0C7   2007/03/02  16.25  TSTUSR7\n  .   WANDA07A  S0C1      RENTSCAN  0000AFA  S=0C2   2007/03/01  11.00  TSTUSR7", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e5cea22670a1-1", "text": ".   USER002A  RUN       CAOEDEMO  0003D48  S=0C7   2007/03/01  10.41  TSTUSR3\n  .   USER002A  RUN       CAOEDEMO  0003D48  S=0C7   2007/03/01  10.34  TSTUSR7\n  .   USER002A  RUN       CAOEDEMO  0003D48  S=0C7   2007/02/28  10.06  USER01 \n  .   WANDA07Z  S0C1      TESTSCAN  0000AFA  S=0C2   2007/02/28  09.43  USER01 \n  .   USRSC01B  RUN       CARXDEMA  000013C  S=0C7   2007/02/23  14.34  USER02 \n  .   USRSC01A  RUN       CEEPLPKA  00BAE7A  U=0666  2007/02/23  14.33  USER02 \n  d   USRSC01A  STEP1     CARXDEMA  000013C  S=0C7   2007/02/23  14.28  USER02 \n  .   USRSC01A  RUN       ABEND1    0000014  U=0001  2007/02/21  15.26  TSTUSR2\n \n2.Press Enter to delete the report, or press END to cancel the request.\nYou can suppress confirmation for the remainder of the session by entering N in the Display this message? field located at", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e5cea22670a1-2", "text": "the bottom of the confirmation window.\nUse PROFILE command to suppress all delete confirmations for your ID.\nLock and Unlock Reports\nYou can lock a report to ensure that it is not edited or deleted by other users.\nFollow these steps:\n1.Type the L line command.\nYour userid appears in the Lock column, indicating that you have requested a lock for the report. While a report is\nlocked, it cannot be deleted from the repository.\n2.Type the U line command to unlock a report that was previously locked.\nUse the Electronic Notepad\nYou can use the Electronic Notepad as a scratch pad while debugging a problem.\nTo use the electronic notepad, type the N line command to open the Electronic Notepad for a report.\n 866", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "00208e652fe6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nYour notes are stored in your user profile, are unique to the selected report, and can only be viewed from your own userid.\nNOTE\nFor more information about a complete description of the Electronic Notepad, see Advanced Techniques.\nModify Formatting Options\nWhen a report is created, your installation defaults and CAIOPTS overrides are used to select formatting options for the\nreport. Using the Repository Viewer, you can change many of these formatting options dynamically to control the format\nand content of your reports.\nFollow these steps:\n1.Type the O line command to display the Report Options panel.\nThe following screen is displayed:\n CA SymDump Batch ------------ Report Options ----------------- Line 1 of 15\n Command ===>                                                   Scroll ===> CSR\n -------------------------------------------------------------------------------\n JobName  USER002A   Step/Tsk  RUN       UserId  USER002     Date  2007/01/25  \n Program  CAOEDEMO   Offset    0003D48   Comp    S=0C7       Time  12.40       \n ------------------------------------------------------------------------- Lvl 2\n Display Options               Merging Options                                 \n ASMINST    ===> ON            BINFRMT    ===> DEC                             \n FILES      ===> ON            GRPADDR    ===> ON                              \n FIRST128   ===> OFF           MERGEDB    ===> ON                              \n LINECNT    ===> 60            MRGAUTO    ===> ON                              \n LINKAGE    ===> ON            MRGBASED   ===> ON                              \n LISTLINE   ===> 0             MRGCNTLD   ===> ON                              \n LOCALSTOR  ===> ON            MRGDSECT   ===> ON                              \n MEMMAP     ===> ON            MRGFILES   ===> ON                              \n RPTSZ80    ===> OFF           MRGLINK    ===> ON                              \n SAVEAREA   ===> ON            MRGLOCAL   ===> ON", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "00208e652fe6-1", "text": "SAVEAREA   ===> ON            MRGLOCAL   ===> ON                              \n SHOWHEAP   ===> OFF           MRGPARMS   ===> ON                              \n WORKSTOR   ===> ON            MRGSTAT    ===> ON                              \n                               MRGWORK    ===> ON                              \n                               OCCURS     ===> 1                               \n                               SHOWUNMRG  ===> TBLS                            \n \n2.Modify the following formatting display and merging options as required:\n\u2013Display Options:\n\u2013ASMINST ON|OFF\nDisplays the abending Assembler instruction.\n\u2013FILES ON|OFF\nDisplays the Open Files report.\n\u2013FIRST128 ON|OFF\nDisplays only the first 128 bytes of each record.\n\u2013LINECNT nnn\nDisplays the number of lines per formatted page.\n\u2013LINKAGE ON|OFF\nDisplays the linkage section for COBOL programs.\n\u2013LISTLINE nn\n 867", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "85298c1590f3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDisplays the number of additional listing lines to be merged into a report before and after the source statement at\nabend or snap.\n\u2013LOCALSTOR ON|OFF\nDisplays local storage for COBOL programs.\n\u2013MEMMAP ON|OFF\nDisplays the TGT, DSA, and PGT memory maps.\n\u2013RPTSZ80 ON|OFF\nFormats when possible using 80-byte output.\n\u2013SAVEAREA ON|OFF\nDisplays the Save Area Trace report.\n\u2013SHOWHEAP ON|OFF\nDisplays LE or PL/I heap storage.\nNOTE\nSHOWHEAP ON requires SAVEHEAP ON at execution time for LE enabled COBOL or Assembler\nprograms.\n\u2013WORKSTOR ON|OFF\nDisplays the working storage for COBOL programs.\n\u2013Merging Options:\n\u2013BINFRMT DEC|HEX\nDisplays binary values as decimal or hexadecimal.\n\u2013GRPADDR ON|OFF\nDisplays the group address for 01-items.\n\u2013MERGEDB ON|OFF\nMerges symbolic names onto Database reports.\n\u2013MRGAUTO ON|OFF\nMerges symbolic names onto PL/I automatic storage.\n\u2013MRGBASED ON|OFF\nMerges symbolic names onto PL/I based variable storage.\n\u2013MRGCNTLD ON|OFF\nMerges symbolic names onto PL/I controlled storage.\n\u2013MRGDSECT ON|OFF\nMerges symbolic names onto Assembler DSECT storage.\n\u2013MRGFILES ON|OFF\nMerges symbolic names onto file section for COBOL.\n\u2013MRGLINK ON|OFF\nMerges symbolic names onto linkage section for COBOL.\n\u2013MRGLOCAL ON|OFF\nMerges symbolic names onto local storage for COBOL.\n\u2013MRGPARMS ON|OFF", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "85298c1590f3-1", "text": "\u2013MRGPARMS ON|OFF\nMerges symbolic names onto PL/I parameter storage.\n\u2013MRGSTAT ON|OFF\nMerges symbolic names onto PL/I static storage.\n\u2013MRGWORK ON|OFF\nMerges symbolic names onto working storage for COBOL.\n\u2013OCCURS nnn|MAX\nDisplays the number of table elements to display for each array.\n\u2013SHOWUNMRG ALL|NONE|TBLS\nDisplays storage for unmerged data.\n3.Modify the formatting options as desired, press END.\n 868", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "86ef825b315b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nYour changes are saved to the repository. Press CANCEL to return to the Report Index panel without saving.\nPrint a Report\nYou have an option of printing a report to a printer, file, or other destination.\nFollow these steps:\n1.Type the P line command to send a report to a printer, file, or other destination.\nThe Print Options pop-up window displays:\n CA SymDump Batch ------------ Report Index ------------------- Line 1 of 68\n Command ===>                                                   Scroll ===> CSR\n -------------------------------------------------------------------------------\n Repo +------------------------------------------------------------------+     \n    1 |                                                                  |     \n Filt | Print Options:                    * Press ENTER to PRINT *       |     \n      |                                                                  |     \n ---- | Printer     ===> SYSTEM1A.USER01                                 | Lvl 1\n Cmd  |   or                                                             | rId \n  P   | Dsname      ===> 'USER01.RPTFILE'                                | USR7\n  .   | Member      ===> NEWMEM      Disposition ===>  NEW               | USR1\n  .   |                                                                  | USR3\n  .   | Copies      ===> 001                                             | USR7\n  .   | Class       ===> X                                               | USR7\n  .   | PageDef     ===>                                                 | USR7\n  .   | FormDef     ===>                                                 | USR7\n  .   | Chars       ===>                                                 | USR3\n  .   |                                                                  | USR7\n  .   | Format Y/N  ===> Y                                               | R01 \n  .   |                                                                  | R01 \n  .   |                                                                  | R02 \n  .   |                                                                  | R02 \n  .   |                                                                  | R02 \n  .   +------------------------------------------------------------------+ USR2\n \n2.Complete the following fields and press Enter.\nPrinter", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "86ef825b315b-1", "text": "2.Complete the following fields and press Enter.\nPrinter\nLets you define the destination to which the printed output is sent. You\ncan specify a printer name, node.userid, or leave the field blank to spool the printed output to your TSO userid.\nDsname\nLets you define the name of a data set to which the printed output is written. If this field is non-blank, it overrides\nthe Printer field. When entering a data set name, it must be fully qualified and enclosed in single quotation marks.\nOtherwise, your ZPREFIX value is used as the leading qualifier.\nMember\nLets you define the member name if you are printing the report to a partitioned data set.\nDisposition\nLets you specify the disposition of the data set to which the output should be printed. This field is relevant only if\nprinting to a data set. If the value is NEW or MOD, a second window pops up to request allocation parameters.\nValues: SHR, OLD, NEW, and MOD\nNOTE\nFor a description of the fields on the window, see the PRINT command.\n 869", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "38aecbeb9919-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCopies\nLets you define the number of copies to be printed.\nClass\nLets you define the sysout class to use to allocate the print data set.\nPageDef\nLets you define the name of the library member that PSF uses to define the page layout for printing on a 3800\nPrinting Subsystem Model 3.\nFormDef\nLets you define the name of the library member that PSF uses to define the form layout for printing on a 3800\nPrinting Subsystem Model 3.\nChars\nLets you define the name of the character arrangement tables for printing on a 3800 Printing Subsystem Model 3.\nFormat\nLets you specify whether to print reports for viewing at your installation.\nDefault: Y\nValues:\nY\nPrints reports for viewing at your installation.\nN\nDoes not print reports for viewing. Set this field to N only when instructed to do so by Broadcom Support  for\ndiagnostic purposes.\n3.Press CANCEL to return to the Report Index panel without printing.\nUsage Notes:\n\u2022When one or more fields are changed before pressing Enter, the fields are validated and redisplayed along with the\nmessage Press Enter to Print. To continue, press Enter again.\n\u2022Reports are printed using the formatting options defined in the repository. Use the O line command prior to printing to\nconfirm these options.\nSelect a Report for Viewing\nTo select a report for viewing, type the S line command.\nWhen a report is selected for viewing, the report data is formatted using your customized formatting options and the\navailable symbolic information. The report is then loaded into memory, a table of contents called the Report Tree is built,\nand the Report Tree panel displays.\nReport Tree\nThe Report Tree panel displays all of the key report sections within your report, sorted in the order in which they appear. It", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "38aecbeb9919-1", "text": "provides a shortcut to any section within the selected report.\nCA SymDump Batch ------------ Report Tree -------------------- Line 1 of 10\nCommand ===>                                                   Scroll ===> CSR\nCAPI052I Profile restored as of 11:31:59 on 2007/01/26 ------------------------\nJobName  USER002A   Step/Tsk  RUN       UserId  USER002     Date  2007/01/25  \nProgram  CAOEDEMO   Offset    0003D48   Comp    S=0C7       Time  12.40       \n------------------------------------------------------------------------- Lvl 2\nCmd  LineNo.   Description                                                    \n 870", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6844cb1dfc3e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n .         1 - Job=USER002A                                                   \n .         1   |-Input Options Display                                        \n .         6 - |-Abend S=0C7 (CAOEDEMO)                                       \n .        20   | |-Abending Statement                                         \n .        34   | |-Abending Instruction                                       \n .        51   | |-Module Call Sequence                                       \n .        63 + | |-Program CAOEDEMO                                           \n .       811 + | |-Open Files                                                 \n .       819   | |-Save Area Trace                                            \n .       843   |-Execution Summary                                            \n-------------------------------------------------------------------------------\nTo instantly position your display to any section in the report, Type S in the Cmd column next to that section and press\nEnter. To position your display to the top of the report, type S next to the first entry in the Report Tree.\nAfter your display is positioned within the report, you can reposition your display using the standard positioning commands\n(UP, DOWN, FIND, RFIND, LOCATE) or press END to return to the tree and select a different shortcut.\nReport Tree Fields\nA static information area is displayed at the top of the panel, immediately below the command line and separated by\ndashed lines.\nThe following information is displayed in the static information area:\nJob Name\nDisplays the  name of the job for which the report was created.\nStep/Tsk\nDisplays the  name of the step that produced the report or the IMS DC task ID if the report was generated in an\nIMS DC environment under LE.\nUserid\nDisplays the  name of the user owning the job for which the report was created.\nDate\nDisplays the  date on which the report was created.\nProgram\nDisplays the  name of the program in control at the time of the error.\nOffset", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6844cb1dfc3e-1", "text": "Program\nDisplays the  name of the program in control at the time of the error.\nOffset\nDisplays the  offset within the program at the time of the error.\nComp\nDisplays the  completion code (S= xxx, U=dddd , or RC= dddd ).\nTime\nDisplays the  time at which the report was captured.\nThe final static line in this display is the highlighted header line, containing all of the column headers for the Report Tree\npanel.\nThe data portion of the display is scrollable but cannot be sorted.\nFor each entry in the Report Tree, the following information is displayed:\nLineNo\nDisplays the  line number within the report where the report section corresponding to the tree entry begins.\n 871", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "880ef75fe209-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDescription\nDisplays a brief description of the report section, generally matching the header found at the top of the section in\nthe report.\nPrimary Commands\nThe following primary commands are available from the Report Tree panel:\nCommand Description\nBOTTOM Scrolls the display to the last line.\nDOWN Scrolls the display forward.\nFIND Locates text in the current display.\nFM Invokes File Master Plus  to view a data set.\nHELP Requests help for a command, message or topic.\nKEEP Adds data from the current display to the Keep Window.\nLEFT Scrolls the display to the left.\nOPTIONS Displays the current installation options in effect.\nPRINT Prints all of part of the current display.\nPROFILE Views and updates display preferences.\nRFIND Repeats a previous FIND command.\nRIGHT Scrolls the display to the right.\nSYM Displays the Symbolic Utilities menu.\nTOP Scrolls the display to the first line.\nUP Scrolls the display backward.\nVIEW Displays symbolic listing for a program.\nA description of each primary command can be found later in this section.\nFor viewing the online help for any primary command, type HELP command-name .\nLine Commands\nThe following line commands are available from the Report Tree panel:\nCommand Description\n+ Expands an entry in the tree to view its subordinate sections.\n- Collapses an entry in the tree to hide its subordinate sections.\n! Explodes an entry in the tree by first expanding the entry and then\nexpanding each of its subordinates, recursively, until all of the\nsections are visible.\n/ Toggles an entry between the expanded and collapsed views.\nS Selects a report section for viewing.\n 872", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c9d7ba8c6584-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nExpand and Collapse the Tree View\nSome report sections are logical subsets of other larger sections, and this relationship is represented in the tree using\nindentation and an increasing number of vertical bars.\nIn the following example, an Abend report for program SBDEMOC, which begins on line eight, has six subordinate report\nsections.\n.     8-    | -Abend S=0C7 (SBDEMOC)            \n.    22 | |-Abending Statement              \n.    36 | |-Abending Instruction            \n.    53 | |-Module Call Sequence            \n.    65+    | |-Program SBDEMOC                 \n.   802+    | |-Open Files                      \n.   810 | |-Save Area Trace \nThe Abend report for program SBDEMOC is displayed with only one vertical bar. Each of the six subordinate sections are\ndisplayed with two vertical bars, demonstrating that they are each logically part of the Abend report.\nA section in the report tree is expanded when its subordinate sections are visible in the display and collapsed when its\nsubordinate sections are not visible. An expanded section is identified in the display by the - symbol immediately to the\nright of the line number, while a collapsed section is identified by a + symbol. When neither symbol appear, the report\nsection has no subordinate sections.\nThis example shows the same report tree, except that the entry for program SBDEMOC is expanded to show its\nsubordinate sections. This view now contains a direct shortcut  to all of this program's data sections and other key reports.\n.     8-    |-Abend S=0C7 (SBDEMOC)                     \n.    22 | |-Abending Statement                      \n.    36 | |-Abending Instruction                    \n.    53 | |-Module Call Sequence", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c9d7ba8c6584-1", "text": ".    53 | |-Module Call Sequence                    \n.    65-    | |-Program SBDEMOC                         \n.    84+    | | |-File Section                          \n.   110 | | |-Working-Storage Section               \n.   575 | | |-External Working-Storage Section      \n.   584 | | |-Linkage Section                       \n.   600     | | |-Registers at Abend                    \n.   637+    | | |-Memory Maps                           \n.   802+    | |-Open Files                              \n.   810 | |-Save Area Trace     \nBy expanding and collapsing the Report Tree view, you can easily zoom in to easily locate any areas of interest within\nyour report.\nView a Report\nWhen you use the S line command from the Report Tree panel, your display is positioned directly to the selected section\nof the report as shown in the following screen:\nCA SymDump Batch ----------- Report ----------------------- Line 8 of 915\nCommand ===>                                                   Scroll ===> CSR \n-------------------------------------------------------------------------------\nJobName  SBDEMOC    Step/Tsk  RUN       UserId  MIKED       Date  2004/05/17   \n 873", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5d2d11f997c9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nProgram  SBDEMOC    Offset    0003B94   Comp    S=0C7       Time  15.33        \n------------------------------------------------------------------------- Lvl 3\n....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....\n               ****************************                                    \n               *             *   S-0C7    *                                    \n               *  A B E N D  *------------*                                    \n               *             *  SBDEMOC   *                                    \n               ****************************                                    \n*******************************************************************************\n*      DESCRIPTION:  S0C7 - A NUMERIC FIELD CONTAINED NON-NUMERIC DATA.        \n*                                                                              \n*  PROBABLE CAUSES:   1. NUMERIC DATA WAS NOT INITIALIZED.                     \n*                     2. A SUBSCRIPT OR INDEX CONTAINED AN INVALID VALUE.      \n*                     3. A COMP-3 FIELD HAD AN INVALID SIGN.                   \n*                     4. A GROUP MOVE OVERLAYED A NUMERIC FIELD WITH NON-NUMERI\n*******************************************************************************\n                                                                               \n**********************                                                         \n* ABENDING STATEMENT *                                                         \n**********************                                                        \nReport View Fields\nThe static information area displayed at the top of the Report Tree panel continues to display while viewing the report.\nThe final static line in this display is the highlighted ruler, which scrolls left and right automatically as you scroll the data.\nThe data portion of the display is both vertically and horizontally scrollable when the report length or width cannot be fully\naccommodated by your screen dimensions.\n \nAdvanced Techniques\nSeveral easy-to-master techniques involving simple primary commands can make your report viewing sessions more\nproductive. We recommend that you set your PF keys to some of these primary commands to facilitate their use:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5d2d11f997c9-1", "text": "\u2022The Keep Window and the Electronic Notepad help you with your diagnostic procedure. Use the KEEP command to\ncopy data from any display into your Keep Window.\n\u2022The NOTES command lets you maintain notes for each report as you view.\n\u2022The TAG and LOCATE commands let you quickly maneuver through different sections of a report.\nThis section provides a detailed description of each of these advanced techniques.\nSet PF Keys\nUsing PF keys to execute some of the more common commands helps save time and reduce keystroke errors when\nentering commands.\nFollow these steps:\n1.Type KEYS  on any Repository Viewer command line and press Enter.\nThe PF Keys panel displays, which lets you change your PF key settings for the product.\n 874", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1fc931e843cd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nIf your Repository Viewer was invoked using the NEWAPPL keyword, it executes under its own unique\napplication ID and therefore has its own unique set of PF key settings. Therefore, setting your PF keys for\nthe viewer will not affect your settings for other ISPF applications.\nThe following screen shows the PF Keys panel:\n                  PF Key Definitions and Labels - Primary Keys\n Command ===>\n                                                                    More:     +\n Number of PF Keys . . . 24                          Terminal type  . . 3278\n Enter \"/\" to select . .           (Enable EURO sign)\n \n PF1 . . . HELP\n PF2 . . . SPLIT\n PF3 . . . END\n PF4 . . . DUMP\n PF5 . . . RFIND\n PF6 . . . MAP\n PF7 . . . UP\n PF8 . . . DOWN\n PF9 . . . SWAP\n PF10  . . LEFT\n PF11  . . RIGHT\n PF12  . . RETRIEVE\n \n PF1  Label  . .            PF2  Label  . .           PF3  Label  . .\n PF4  Label  . .            PF5  Label  . .           PF6  Label  . .\n PF7  Label  . .            PF8  Label  . .           PF9  Label  . .\n PF10 Label  . .           PF11  Label  . .           PF12 Label  . .\n2. Use the PF Keys panel to assign any PF key to any primary command.\nIt is recommended to only reassign those keys whose functions are not used by the viewer. For example, some of your PF\nkeys may already be assigned to some of these functions used by the viewer:\n\u2022DOWN\n\u2022END\n\u2022HELP\n\u2022LEFT\n\u2022RFIND", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1fc931e843cd-1", "text": "\u2022DOWN\n\u2022END\n\u2022HELP\n\u2022LEFT\n\u2022RFIND\n\u2022RETRIEVE\n\u2022RIGHT\n\u2022SPLIT\n\u2022SWAP\nHowever, you can replace the following keys that are not used by the viewer:\n\u2022RCHANGE\n\u2022RETURN\nWe strongly recommend that you set one of your available PF keys to KEEP to facilitate the use of this cursor-sensitive\ncommand.\n 875", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0d464c4b3c94-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse the Keep Window\nThe Keep Window is a dynamic area located just above the highlighted header line on any display. The size of the window\nis dynamic depending on the number of data lines added. When the window is empty, its borders are not displayed. You\ncan copy any data line from any viewer display into this area, causing that data line to remain in view even after you exit\nthe display.\nExamples of data you might add to your Keep Window include:\n\u2022Text from a HELP command\n\u2022Source statements from the SYM command\n\u2022Key data values from anywhere in your report\n\u2022Compile and link information for a program\nTo add a data line to your Keep Window, first type KEEP  on the command line, then place your cursor on the desired data\nline and press Enter. Alternatively, if you have set a PF key for KEEP, place your cursor on any data line and press that\nkey. The data line is added automatically to your Keep Window.\nThe following example shows compile information for program SBDEMOC in the Keep Window:\nCA SymDump Batch ------------ Report ----------------------- Line 22 of 898\nCommand ===>                                                   Scroll ===> CSR\n-------------------------------------------------------------------------------\nJobName  SBDEMOC    Step/Tsk  RUN       UserId  USER02      Date  2007/06/05  \nProgram  SBDEMOC    Offset    0003B94   Comp    S=0C7       Time  12.05       \n----------------------------------- (Keep) ------------------------------------\nCOMPILED ON 21 MAY,2007 AT 16.30.20 WITH COBOL FOR Z/OS 3.4.1                 \nCOMPILE OPTIONS: ADV, APOST, NOAWO, DATA(31), DBCS, NODECK, NODUMP, DYNAM,", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0d464c4b3c94-1", "text": "NOFASTSRT, LIB, LIST, MAP, NONAME, NONUMBER, OBJECT, NOOFFSET,\n                 OPTIMIZE, NUMPROC(PFD), RENT, SEQUENCE, SOURCE, NOSSRANGE,\n                 NOTERM, NOTEST, TRUNC(STD), NOVBREF, NOWORD, XREF, ZWB\n------------------------------------------------------------------------- Lvl 3\n....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....\n**********************                                                        \n* ABENDING STATEMENT *                                                        \n**********************                                                        \n                                                                              \nPROGRAM: SBDEMOC   OFFSET: 003B8E  LINE: 001284                               \n                                                                              \n001284        MOVE MASK1  TO  BINARY-1                                        \n                                            \nLINE#   LEVEL/FIELD NAME                      VALUE/LOCATION                  \n------  ---------------------------------     --------------------------------\n000329  03 MASK1                              ALL '*'                          \nEach user has a separate Keep Window for each report they view. The contents of each is saved in the user profile when\na report viewing session is ended and is restored to the same state the next time that same dump is selected for viewing.\nNOTE\nYou can also use the KEEP command from the Report Index panel, but that window is maintained separately, is\nnot preserved across sessions, and cannot be viewed while a report is loaded.\nTo remove a data line from the Keep Window, first type KEEP  on the command line, place your cursor on the line being\nremoved, and press Enter. If you have a PF key set for KEEP, place your cursor on the line being removed and press that\nkey.\n 876", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "59c8b41467dc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo prevent your Keep Window from being displayed without removing its contents, type KEEP OFF  on the command line\nand press Enter. Type KEEP ON  to restore the display at any time. The status of your window display (ON or OFF) is also\nsaved in the user profile for each report you view.\nNOTE\nWhen the Keep Window status is OFF, the data in your Keep Window is not lost; it is simply not displayed until\nthe window display is reactivated. Data cannot be added or removed from the Keep Window while its status is\nOFF.\nOn some terminals, adding several lines to your Keep Window can dramatically reduce the number of visible lines of\nreport data. If this is a problem, you can use the PROFILE command to suppress the information area at the top of the\ndisplay.\nUse the Electronic Notepad\nThe Electronic Notepad lets users maintain notes for each report they view. The notepad is free-format and dynamically\nsized, which lets you enter any of your thoughts, ideas, or comments while viewing the report. You can also copy and\npaste report information into the notepad for easy retrieval.\nNotepad records are 126 bytes wide to fill a 132-column screen format and are horizontally scrollable for 80-column\ndisplays. You can type any kind of data in the notepad because there is no syntax checking.\nTo open a notepad from the Report Index panel, type N in the Cmd column next to the report entry and press Enter.\nTo open a notepad for an open report while viewing, type NOTES  on the command line and press Enter.\nThe first time you open the notepad for a report, the following message displays:\nCA SymDump Batch ------------ Report Index ------------------- Line 1 of 68\nCommand ===>                                                   Scroll ===> CSR\n-------------------------------------------------------------------------------\nRepositor +--------------------------------------------------------+", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "59c8b41467dc-1", "text": "Command ===>                                                   Scroll ===> CSR\n-------------------------------------------------------------------------------\nRepositor +--------------------------------------------------------+          \n   1754 D |                                                        |          \nFilter: J | No notes were found for the report you selected.       |          \n        C |                                                        |          \n--------- | Press ENTER to start a new notepad for this report.    | ---- Lvl 1\nCmd  JobN |                                                        |   UserId \n N   WOND | Program: SUBCOB    Offset: 000026A  Comp: S=0C7        |   TSTUSR7\n .   DAVS |                                                        |   TSTUSR1\n .   RYAR | Press END to cancel the notes request.                 |   TSTUSR3\n .   WOND |                                                        |   TSTUSR7\n .   WOND +--------------------------------------------------------+   TSTUSR7\n .   WANDA07C  TESTCOB2  SUBCOB    000026A  S=0C7   2007/03/02  16.25  TSTUSR7\n .   WANDA07A  S0C1      RENTSCAN  0000AFA  S=0C2   2007/03/01  11.00  TSTUSR7\n .   USER002A  RUN       CAOEDEMO  0003D48  S=0C7   2007/03/01  10.41  TSTUSR3\n .   USER002A  RUN       CAOEDEMO  0003D48  S=0C7   2007/03/01  10.34  TSTUSR7", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "59c8b41467dc-2", "text": ".   USER002A  RUN       CAOEDEMO  0003D48  S=0C7   2007/02/28  10.06  USER01 \n .   WANDA07Z  S0C1      TESTSCAN  0000AFA  S=0C2   2007/02/28  09.43  USER01 \n .   USRSC01B  RUN       CARXDEMA  000013C  S=0C7   2007/02/23  14.34  USER02 \n .   USRSC01A  RUN       CEEPLPKA  00BAE7A  U=0666  2007/02/23  14.33  USER02 \n .   USRSC01A  STEP1     CARXDEMA  000013C  S=0C7   2007/02/23  14.28  USER02 \n .   USRSC01A  RUN       ABEND1    0000014  U=0001  2007/02/21  15.26  TSTUSR2\nPress Enter to create a new notepad for the report, or press END to cancel the request.\nA new notepad, like the one shown in the following screen, initially contains ten blank records:\n 877", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9fe88728bf35-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCA SymDump Batch ------------ Notes -------------------------- Line 1 of 10\nCommand ===>                                                   Scroll ===> CSR\n-------------------------------------------------------------------------------\nProgram: SUBCOB       Offset: 000026A     Comp: S=0C7                         \nLast Update: None                                                             \n------------------------------------------------------------------------- Lvl 2\nCmd  ....+....1....+....2....+....3....+....4....+....5....+....6....+....7....\n .                                                                            \n .                                                                            \n .                                                                            \n .                                                                            \n .                                                                            \n .                                                                            \n .                                                                            \n .                                                                            \n .                                                                            \n .                                                                            \n-------------------------------------------------------------------------------\nThe information area located at the top of the display identifies the report for which the notepad was created.\nThe final static line in this display is the highlighted ruler that scrolls left and right automatically as you scroll your notes.\nThe data portion of the display is both vertically and horizontally scrollable when the length or width of the notepad cannot\nbe fully accommodated by your screen dimensions.\nType the I line command to insert a new blank record following any existing record in the notepad. Type the D line\ncommand to delete an existing record from the notepad.\nWhen you have completed your updates, press END to save your updates and return to the display from which the\nnotepad was entered. Use CANCEL to exit without saving your changes.\nUse TAG and LOCATE\nFor large reports, it may be necessary to create placeholders for sections of the report that do not appear in the Report\nTree panel.\nUse the TAG primary command to define a tag or label for any location in your report. You are prompted for a tag name,\nas shown in the following screen:\nCA SymDump Batch ----------- Report --------------------- Line 115 of 915\nCommand ===>                                                   Scroll ===> CSR \n-------------------------------------------------------------------------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9fe88728bf35-1", "text": "Command ===>                                                   Scroll ===> CSR \n-------------------------------------------------------------------------------\nJobName  SBDEMOC  +----------------------------------------+ ate  2004/05/17   \nProgram  SBDEMOC  |                                        | ime  15.33        \n----------------- | Enter Tag Name:                        | ------------ Lvl 3\n....+....1....+.. | ===>                                   | ...+....7....+....\n000062  77 FILLER |                                        |  PROPRIETARY PROP*\n                  +----------------------------------------+ R ASSOCIATES INTE*\n                                  (+000064)  *RNATIONAL, INC. *                \n000065  77 FILLER                            * COPYRIGHT (C) 1986-1999 BY COMP*\n                                  (+000032)  *UTER ASSOCIATES INTERNATIONAL, I*\n                                  (+000064)  *NC.             *                \n000068  77 ERROR-FLAG                         ZEROS                            \n 878", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b5700912d735-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n000069  77 DATA-PICX10                        LOW-VALUES                       \n000070  77 ROW-3D                             1                                \n000071  77 COLUMN-3D                          1                                \n000072  77 RANGE-3D                           1                                \n000074  01 PARAMETER-ONE                      BLW=0000+0000D0  (121B1188)      \n000075  03 FILLER                            *PARAMETERONE*                    \n000080  01 PARM-PASSED-BY-JCL                 BLW=0000+0000E0  (121B1198)      \n000081  03 PARM-MSG                          *NONE    *                        \n000082  03 PARM-FLAG                         *NONE    *                        \n000083  03 PARM-MODE                         *DTE*                     \nType a name for your tag, from 1 to 32 characters and press Enter to create your tag. Leading periods are ignored.\nAlternatively, you can create a tag using the .label  method by entering your tag name on the command line with a leading\nperiod. For example, to create a tag named EF for a variable named ERROR-FLAG, position your display to that variable\nand type .EF on the command line. Press Enter to create the tag.\nNOTE\nIf you create a tag with a duplicate name, the new tag replaces the previously existing tag.\nAfter you create your tag, you can position your display immediately to that line using the LOCATE command or L as an\nabbreviation. In the example above, type L EF  to locate the variable ERROR-FLAG. If you enter a LOCATE command\nwithout any tag name, you are prompted for a tag name as shown in the following screen:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b5700912d735-1", "text": "without any tag name, you are prompted for a tag name as shown in the following screen:\nCA SymDump Batch ----------- Report ---------------------- Line 22 of 915\nCommand ===>                                                   Scroll ===> CSR \n-------------------------------------------------------------------------------\nJobName  SBDEMOC  +----------------------------------------+ ate  2004/05/17   \nProgram  SBDEMOC  |                                        | ime  15.33        \n----------------- | Enter Tag Name:                        | ------------ Lvl 3\n....+....1....+.. | ===>                                   | ...+....7....+....\n***************** |                                        |                   \n* ABENDING STATEM +----------------------------------------+                   \n**********************                                                         \n                                                                               \nPROGRAM: SBDEMOC   OFFSET: 003B8E  LINE:  00128                                \n                                                                               \n           MOVE MASK1  TO  BINARY-1                                            \n                                                                               \nLINE#   LEVEL/FIELD NAME                      VALUE/LOCATION                   \n------  ---------------------------------     -------------------------------- \n000329  03 MASK1                              ALL '*'                          \n000178  03 BINARY-1                          +1                                \n                                                                               \n                                                                               \nABENDING INSTRUCTION                                                           \n                                                                               \n   4F30 D4B8         CONVERT                                                  \nTags are not stored in the user profile, so all tags are cleared when you exit a report viewing session.\nSymbolic Utilities\n 879", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1b6543821215-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse the SYM primary command from anywhere in the Repository Viewer to display the Symbolic Utilities menu as shown\nin the following screen:\nCA SymDump Batch------- Report Index ---------------- Line 1 of 33\nCommand ===>                                            Scroll ===> CSR \n-----------------------------------------------------------------------\nRep +------------------------------------------------------------+     \n    |  Select a Symbolic Utility ===>                            |     \n--- |                                                            | vl 1\nCmd |   1. List the contents of a symbolic file                  | Id  \n .  |   2. Add listings to a PROTSYM file                        | C01 \n .  |   3. List globally defined symbolic files                  | C01 \n .  |   4. Add or Remove supplemental symbolic files             | C01 \n .  |   5. Dynamic Symbolic Support for CA Endevor SCM           | D01 \n.   |                                                            | O02 \n .  |  Symbolic File Dsname:                                     | O02 \n .  |  ==> 'CAI.PROTSYM'                                         | O02 \n .  +------------------------------------------------------------+ O02 \n.   USER002A  RUN  AO2DEMO  00041B6  S=0C7   2004/03/05  14.47  USER002 \n .  USER002S  RUN  PLITEST1 0001002  S=0C7   2004/03/04  16.29  USER002 \n .  USER002S  RUN  PLITEST1 0001002  S=0C7   2004/03/04  16.18  USER002", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1b6543821215-1", "text": "USER002P  RUN  PLITEST1 0001E22  S=0C7   2004/03/04  14.36  USER002 \n    USER002P  RUN  PLITEST1 0001C46  S=0C7   2004/03/04  14.35  USER002 \n .  USRSC01A  RUN  COMP2    00001E8  S=0C7   2004/02/25  17.46  USRSC01 \n .  USRSC01A  RUN  COMP1    00003FE  S=0C7   2004/02/24  18.06  USRSC01 \n    USRSC01A  RUN  COMP1    00003FE  S=0C7   2004/02/24  17.46  USRSC01 \n    USRSC01A  RUN  COMP1    00003FE  S=0C7   2004/02/24  17.37  USRSC01 \n    USRSC01A  RUN  COMP2    00001E8  S=0C7   2004/02/24  11.51  USRSC01\nThe symbolic utilities can be used to:\n\u2022List the contents of your symbolic files\n\u2022Delete a member from a symbolic file\n\u2022Print a program listing from a symbolic file\n\u2022View a listing from a symbolic file\n\u2022Add a listing to your PROTSYM file\n\u2022List your globally defined symbolic files\n\u2022Add or remove your supplemental symbolic files\n\u2022Add or change DSS options for the Viewer ISPF session.\nSelect one of the valid options from the menu to continue.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1b6543821215-2", "text": "Select one of the valid options from the menu to continue.\nList the Contents of a Symbolic File\nSelect SYM option 1 to list the contents of a symbolic file. For this option, you must also type the data set name for the\nPROTSYM or CSL file that you want to view. To enter a fully-qualified data set name, enclose the name in single quotation\nmarks. Otherwise, your ZPREFIX value is appended to the name as the high-level qualifier.\nNOTE\nEvery time you access a symbolic file using one of the online utilities, the data set name is stored in your profile.\nAfter you type a symbolic file name, press Enter to list the contents of the file.\nCA SymDump Batch----------- PROTSYM Directory -------------- Line 1 of 42\nCommand ===>                                                    Scroll ===> CSR \n 880", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c8c477e07480-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n-------------------------------------------------------------------------------\nPROTSYM Dsname: CAI.PROTSYM                                           \n------------------------------------------------------------------------- Lvl 2\nCmd  Program    Date         Time       Size    Language       Attributes      \n .   APF1       2003/07/16   18.44.00      11   HLASM                          \n .   APF2       2003/07/16   18.34.00      10   HLASM                          \n .   ASMTEST    2003/08/25   10.30.00      11   HLASM                          \n .   ATTNTEST   2003/07/03   11.28.00      12   HLASM                          \n .   BIGSEQ     2003/01/16   10.50.30      16   COBOL OS/390                   \n .   BIGVAR     2003/02/26   14.31.11      15   COBOL OS/390                   \n .   BLLSUB     2002/09/09   18.38.02      11   COBOL II                       \n .   BLLTEST    2002/09/09   17.05.07      11   COBOL II                       \n .   BLVTEST    2002/09/26   14.25.35      16   COBOL OS/390                   \n .   CALLDETH   2003/10/06   14.33.21      11   COBOL II                       \n .   CAMRTPIP   2003/08/22   15.52.00      21   HLASM                          \n .   CAOUMMAN   2003/12/09   12.50.00      43   HLASM", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c8c477e07480-1", "text": ".   CAO2DEMO   2004/03/12   16.35.54      90   COBOL MVS      CA-OPT          \n .   COMPODO    2003/09/04   15.46.56      32   COBOL II                       \n .   DFSLET1    2003/10/08   16.39.00      10   HLASM                          \n .   DISASMT    2003/11/05   17.07.00      26   HLASM                          \n .   FSSC10     2004/03/03   17.37.14      64   COBOL II                       \n .   IDECLARE   2002/08/28   15.15.44      42   COBOL OS/390                  \nThe PROTSYM (or CSL) Directory panel displays an entry for each available member in your symbolic file.\nPROTSYM Members\nFor PROTSYM members, the following information is displayed:\nDate and Time\nDisplays the  date and time  when the program member was compiled.\nSize\nDisplays the number of PROTSYM records occupied by the member.\nLanguage\nDisplays the compiler used.\nAttributes\nIndicates whether a program was Broadcom -optimized or loaded into the PROTSYM with the NOPURGE option.\nCSL Members\nFor CSL members, the following information is displayed:\nDate and Time\nDisplays the  date and time when the program member was compiled.\nGenlevel\nDisplays the maintenance level of the Optimizer or postprocessor used to create the member.\nRelease\nDisplays the release number of the Optimizer or postprocessor used to create the member.\nCompiler\nDisplays the compiler used.\n 881", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a77844ff45b7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDelete a Member from a Symbolic File\nFollow these steps:\n1.Select SYM option 1 to display the PROTSYM Directory or CSL Directory panel.\n2.Type the D line command to delete the desired member.\nBecause this action is potentially destructive, you are prompted for confirmation before the member is deleted, as\nshown in the following screen:\nCA SymDump Batch ----------- PROTSYM Directory -------------- Line 1 of 42\nCommand ===>                                                    Scroll ===> CSR \n-------------------------------------------------------------------------------\nPROTSYM Ds +------------------------------------------------------+            \n---------- |                                                      | ----- Lvl 2\nCmd  Progr | Press ENTER to confirm delete for member ATTNTEST    | butes      \n .   APF1  | or END to cancel the delete request.                 |            \n .   APF2  |                                                      |            \n .   ASMTE | Display this message? (Y/N) ===> Y                   |            \n .   ATTNT |                                                      |            \n .   BIGSE +------------------------------------------------------+            \n .   BIGVAR     2003/02/26   14.31.11      15   COBOL OS/390                   \n .   BLLSUB     2002/09/09   18.38.02      11   COBOL II                       \n .   BLLTEST    2002/09/09   17.05.07      11   COBOL II                       \n .   BLVTEST    2002/09/26   14.25.35      16   COBOL OS/390                   \n .   CALLDETH   2003/10/06   14.33.21      11   COBOL II", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a77844ff45b7-1", "text": ".   CAMRTPIP   2003/08/22   15.52.00      21   HLASM                          \n .   CAOUMMAN   2003/12/09   12.50.00      43   HLASM                          \n .   CAO2DEMO   2004/03/12   16.35.54      90   COBOL MVS      CA-OPT          \n .   COMPODO    2003/09/04   15.46.56      32   COBOL II                       \n .   DFSLET1    2003/10/08   16.39.00      10   HLASM                          \n .   DISASMT    2003/11/05   17.07.00      26   HLASM                          \n .   FSSC10     2004/03/03   17.37.14      64   COBOL II                       \n .   IDECLARE   2002/08/28   15.15.44      42   COBOL OS/390                  \n3. Press Enter to delete the member, or END to cancel the request.\nTo suppress confirmation for the remainder of the session, type N in the Display this message? field located at the bottom\nof the confirmation pop-up window.\nTo suppress all delete confirmations for your ID, use the PROFILE command.\nNOTE\nIf you are using passwords (SYMPSWD=password), a password must be entered before a member can be\ndeleted from a PROTSYM file. The password is established during product installation. Check with your system\nadministrator and obtain the password before attempting to delete a PROTSYM member. Use the PROFILE\ncommand to store the password in your profile so you do not need to enter it every time.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a77844ff45b7-2", "text": "command to store the password in your profile so you do not need to enter it every time.\nIf you are using an external security interface (EXTSEC=ALL/SYMBOLIC), verify that you have delete authority\nand that the security functions have been defined.\nFor more information, see Global Options.\nPrint a Program Listing from a Symbolic File\nFollow these steps:\n1.Select SYM option 1 to display the PROTSYM Directory or CSL Directory panel.\n 882", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f64175f7da6d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n2.Type the P line command to print the desired program listing.\nYou are prompted for the destination as shown in the following screen:\nCA SymDump Batch ------------ PROTSYM Directory -------------- Line 1 of 42\nCommand ===>                                                   Scroll ===> CSR\n-------------------------------------------------------------------------------\nPROT +------------------------------------------------------------------+     \n---- |                                                                  | Lvl 2\nCmd  | Print Options:                    * Press ENTER to PRINT *       |     \n P   |                                                                  |     \n .   | Printer     ===> USILDAVC.USER01                                 |     \n .   |   or                                                             |     \n .   | Dsname      ===> 'USER01.APDSN'                                  |     \n .   | Member      ===> NEW         Disposition ===> NEW                |     \n .   |                                                                  |     \n .   | Copies      ===> 001                                             |     \n .   | Class       ===> X                                               |     \n .   | PageDef     ===>                                                 |     \n .   | FormDef     ===>                                                 |     \n .   | Chars       ===>                                                 |     \n .   |                                                                  |     \n .   |                                                                  |     \n .   |                                                                  |     \n .   |                                                                  |     \n .   |                                                                  |     \n .   |                                                                  |     \n .   +------------------------------------------------------------------+     \n3.Fill in the following fields and press Enter to print the member listing:\nPrinter\nLets you specify  the destination to which the printed output is routed. This can be specified as a printer name,\nnode.userid, or blank to spool the printed output to your own TSO userid.\nDsname\nLets you define the name of a data set to which the printed output is written. If this field is non-blank, it overrides\nthe Printer field. When entering a data set name, it must be fully qualified and enclosed in single quotation marks.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f64175f7da6d-1", "text": "Otherwise, your ZPREFIX value is used as the high-level qualifier.\nMember\nLets you specify the member name if you are printing the listing to a partitioned data set.\nDisposition\nLets you specify the disposition of the data set to which the output should be printed.  This field is relevant only if\nprinting to a data set. If the value is NEW or MOD, a second window pops up to request allocation parameters.\nValues: SHR, OLD, NEW, and MOD\nNOTE\nFor a description of the fields on the window, see the Repository Viewer Commands.\nCopies\nLets you specify the number of copies to be printed.\nClass\nLets you specify the sysout class that is used to allocate the print data set.\nPageDef\nLets you specify the name of the library member that PSF uses to define the page layout for printing on a 3800\nPrinting Subsystem Model 3.\n 883", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "04889b0f46b3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFormDef\nLets you specify the name of the library member that PSF uses to define the form layout for printing on a 3800\nPrinting Subsystem Model 3.\nChars\nLets you specify the name of the character arrangement tables for printing on a 3800 Printing Subsystem Model\n3.\nView a Program Listing from a Symbolic File\nFollow these steps:\n1.Select SYM option 1 to display the PROTSYM Directory or CSL Directory panel.\n2.Type the S line command to select the desired listing for viewing.\nCA SymDump Batch ----------- CAO2DEMO ------------------ Line 620 of 2714\nCommand ===>                                                   Scroll ===> CSR \n-------------------------------------------------------------------------------\nPROTSYM Dsname: CAI.PROTSYM                                           \n------------------------------------------------------------------------- Lvl 3\n....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....\n  000478               ********************************************************\n  000479               **            P R O C E D U R E    D I V I S I O N      \n  000480               ********************************************************\n  000481                                                                       \n  000482               ********************************************************\n  000483                MAIN-PROGRAM-LOGIC SECTION.                            \n  000484                                                                       \n  000485                    PERFORM PRE-INIT.                                  \n  000486                    PERFORM INITIALIZE-DEMO.                           \n  000487                                                                       \n  000488                MAIN-REPEAT-LOOP SECTION.                              \n  000489                    IF COUNT-TIMES LESS THAN 1 GO TO COMPLETE-DEMO.    \n  000490                    SUBTRACT 1 FROM COUNT-TIMES.                       \n  000491                                                                       \n  000492                    PERFORM SECTION-A.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "04889b0f46b3-1", "text": "000491                                                                       \n  000492                    PERFORM SECTION-A.                                 \n  000493                    PERFORM SECTION-B.                                 \n  000494                    PERFORM SECTION-C.                                 \n  000495                    PERFORM SECTION-D.                                 \n  000496                    PERFORM SECTION-E.                                 \n  000497                    PERFORM SECTION-F.                                 \n  000498                    PERFORM SECTION-G.                                 \n  000499                    PERFORM SECTION-H.                                 \n  000500                    PERFORM SECTION-I.                                 \n  000501                    PERFORM SECTION-J.                                 \n  000502                    PERFORM SECTION-K.                                 \n  000503                    PERFORM SECTION-L.                                 \n  000504                    PERFORM SECTION-M.                                 \n  000505                    PERFORM SECTION-N.                                 \n  000506                    PERFORM SECTION-O.                                 \n  000507                    PERFORM MAIN-MLT-PARAGRAPH                         \n  000508                       THRU MAIN-MLT-PARAGRAPH-EXIT.                  \nThe static information area at the top of the display continues to show the data set name of the selected symbolic file.\n 884", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1487ed62d421-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIf your Keep Window is active and contains data, it continues to display.\nThe final static line in this display is the highlighted ruler, which scrolls left and right automatically as you scroll the listing.\nThe data portion of the display is both vertically and horizontally scrollable when the report length or width cannot be fully\naccommodated by your screen dimensions.\nAdd a Listing to a PROTSYM File\nFollow these steps:\n1.Select SYM option 2 to add one or more listings to a PROTSYM file.\nThis option provides an online interface to the symbolic loader. It can be used to add a single listing, a range of\nmembers, or an entire library at one time. It supports program listings generated by any of the supported IBM\ncompilers and residing in any of the supported library formats.\nThe Add Listing to Protsym pop-up window prompts you for update parameters, as shown in the following screen:\nCA SymDump Batch ------------ Report Index ------------------ Line 1 of 68\nCommand ===>                                                   Scroll ===> CSR\n-------------------------------------------------------------------------------\nRe +----------------------------------------------------------------------+   \n   |  Add Listing to Protsym                                              |   \nFi |                                                                      |   \n   |  Protsym Dsname ===> 'CAI.PROTSYM'                                   |   \n-- |  Listing Dsname ===> 'USER01.LISTINGS'                               | l 1\nCm |  Library Type   ===> PDS             (PDS, SEQ, PAN, LIB, NDV)       | d \n . |  From Member    ===> COB2DEMO                                        | R7\n . |  To Member      ===>                                                 | R3\n . |  View Messages  ===> ALL             (ALL, NONE, RC)                 | R1\n . |                                                                      | R7\n . +----------------------------------------------------------------------+ R7", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1487ed62d421-1", "text": ". |                                                                      | R7\n . +----------------------------------------------------------------------+ R7\n .   WANDA07C  TESTCOB2  SUBCOB    000026A  S=0C7   2007/03/02  16.25  TSTUSR7\n .   WANDA07A  S0C1      RENTSCAN  0000AFA  S=0C2   2007/03/01  11.00  TSTUSR7\n .   USER002A  RUN       CAOEDEMO  0003D48  S=0C7   2007/03/01  10.41  TSTUSR3\n .   USER002A  RUN       CAOEDEMO  0003D48  S=0C7   2007/03/01  10.34  TSTUSR7\n .   USER002A  RUN       CAOEDEMO  0003D48  S=0C7   2007/02/28  10.06  USER01 \n .   WANDA07Z  S0C1      TESTSCAN  0000AFA  S=0C2   2007/02/28  09.43  USER01 \n .   USRSC01B  RUN       CARXDEMA  000013C  S=0C7   2007/02/23  14.34  USER02 \n .   USRSC01A  RUN       CEEPLPKA  00BAE7A  U=0666  2007/02/23  14.33  USER02", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1487ed62d421-2", "text": ".   USRSC01A  STEP1     CARXDEMA  000013C  S=0C7   2007/02/23  14.28  USER02 \n .   USRSC01A  RUN       ABEND1    0000014  U=0001  2007/02/21  15.26  TSTUSR2\n2. Fill in the following fields and press Enter to update the PROTSYM file:\nPROTSYM Dsname\nLets you specify the data set name of any PROTSYM file. When fully qualified, you must type the name in single\nquotation marks. Otherwise, the value of ZPREFIX is added as the high-level qualifier.\nListing Dsname\nLets you  specify the data set name of your listing data set or library. When fully qualified, you must type the name\nin single quotation marks. Otherwise, the value of ZPREFIX is added as the high-level qualifier.\nLibrary Type\nLets you specify one of the following supported listing library types:\nPDS\nPartitioned data sets\n 885", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c5ae41834bf9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSEQ\nSequential listing file\nPAN\nPanvalet  library\nLIB\nLibrarian  library\nNDV\nEndevor  library\nFrom Member\nLets you add the member names.  To add a single member, type the member name in this field. For multiple\nmembers whose names share a common prefix, type the prefix in this field with a single trailing asterisk (*) to\nindicate wild-carding. To add a range of members, type the first member of the range.\nTo Member\nLets you  specify a range of members, To add a range of members, type the name of the last member in this field.\nOtherwise, leave this field blank.\nView Messages\nLets you view messages using the following options:\n\u2022ALL -- Shows all messages generated while the listings are being added to the PROTSYM file.\n\u2022RC -- Shows a single message for each member containing the highest return code produced while adding the\nmember.\n\u2022NONE -- Suppresses all messages.\nIf you have requested to view output messages from the utility, the output appears automatically after the utility is\ncompleted, as shown in the following screen:\nCA SymDump Batch ------------ Add to PROTSYM ---------------- Line 1 of 28\nCommand ===>                                                   Scroll ===> CSR\n-------------------------------------------------------------------------------\nPROTSYM Dsname: CAI.PROTSYM                                   From: COB2DEMO  \nListing Dsname: USER01.LISTINGS                                 To:           \n------------------------------------------------------------------------- Lvl 2\n....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....\nCOB2DEMO POST-PROCESSING ENDED, IN25COB2 RETURNED 00000000", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c5ae41834bf9-1", "text": "IN25COB2 6.2 - 02/18/2004 10.25                                               \n \n SYM036 PASSED PARAMETER STATEMENTS                                            \n \n COB2DEMO,LISTER=ALL,CUTPRINT=ALL                                              \n \n \n SYM010 PROCESSING HAS BEGUN FOR PROGRAM - COB2DEMO                            \n \n SYM006 LISTER=ALL    REQUESTED                                                \n SYM007 CUTPRINT=ALL    REQUESTED                                              \n \n NESTED PROGRAMS                 ID      WS      LS      PD      EP            \n ------------------------------  ------  ------  ------  ------  ------        \n COB2DEMO                        000003  000023  000864  000875  000000       \n \n 886", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e854a7cfa566-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n SYM024 INPUT FILE PROCESSED                                                  \n \n SYM020 SYMBOLIC FILE UPDATED SUCCESSFULLY                                    \n \n SYM021   117 SOURCE STATEMENTS SAVED                                         \n \n SYM022   143 TOTAL RECORDS INSERTED INTO SYMBOLIC FILE                       \n \n SYM023 POST-PROCESSOR TERMINATED                                             \n \n ----------------------------------------------------------------------------- \n3. Press END to return to the Add Listing to PROTSYM pop-up window.\nList Globally Defined Symbolic Files\nSelect SYM option 3 to list the names of the symbolic files which are globally defined in your installation defaults member,\nCAOUDFRX. These symbolic files are automatically available for report formatting by any user or job.\nCA SymDump Batch----------- Global Symbolic Files ----------- Line 1 of 5\nCommand ===>                                                    Scroll ===> CSR \n------------------------------------------------------------------------- Lvl 2\nCmd  Symbolic File Dsname                            Type                      \n .   'AD1DEV.SB21.PROD.PROTSYM'                      Protsym     \n .   'AD1DEV.SB21.DEVL.PROTSYM'                      Protsym     \n .   'AD1DEV.UTILITY.RROTSYM'                        Protsym     \n .   'AD1DEV.SB20.PROD.CSL'                          CSL\n .   'AD1DEV.UTILITY.CSL'                            CSL          \n-------------------------------------------------------------------------------\nGlobally defined symbolic files can be PROTSYM or CSL format and there is no limit to the number of files that can be\ndefined for your installation.\nThe following additional functions can be performed by entering line commands in the Cmd column on this panel:\nA\nAdds listings to this symbolic file. This command displays the Add Listing To PROTSYM pop-up window. Only\nlistings can be added to PROTSYM files.\nS", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e854a7cfa566-1", "text": "listings can be added to PROTSYM files.\nS\nSelects a symbolic file for viewing. This command displays the PROTSYM Directory or CSL Directory panel,\ndepending on the file format.\nTo globally define additional symbolic files, contact your system administrator.\nList Supplemental Symbolic Files\nSelect SYM option 4 to list the names of the symbolic files which you have locally defined for your use. This option lets\nyou maintain and use your own personal symbolic files for your own testing environments without affecting other users.\nYour locally defined supplemental symbolic files are stored in your user profile.\nCA SymDump Batch----------- Supplemental Symbolic Files ---- Line 1 of 16\nCommand ===>                                                    Scroll ===> CSR \n------------------------------------------------------------------------- Lvl 2\nCmd  Symbolic File Dsname                            Type                      \n .   'USRSC01.TEST.PROTSYM'                          Protsym                   \n .   'AD1DEV.MIKED.PROTSYM'                          Protsym                   \n 887", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6179d2c4e318-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n .   'CDE.DEVL.IB31.PROTSYM'                         Protsym                   \n .   'CDE.PROD.IB31.PROTSYM'                         Protsym                   \n .                                                                             \n .                                                                             \n .                                                                             \n .                                                                             \n .                                                                             \n .                                                                             \n .   'MIKED.QA.CSL'                                  CSL                       \n .   'USRSC01.CSL'                                   CSL                       \n .   'USER002.CSL'                                   CSL                       \n .                                                                             \n .                                                                             \n .                                                                             \n-------------------------------------------------------------------------------                               \n                                                \nLocally defined supplemental symbolic files can be PROTSYM or CSL format and you can have up to 16 supplemental\nfiles defined at any one time.\nTo add a new file, type the data set name on an empty line. When fully qualified, you must type the name in single\nquotation marks. Otherwise, the value of ZPREFIX is added as the high-level qualifier.\nTo remove a supplemental symbolic file, clear the data set name from the line.\nThe following additional functions can be performed by entering line commands in the Cmd column on this panel:\nA\nAdds listings to this symbolic file. This command displays the Add Listing To Protsym pop-up window. Only listings\ncan be added to PROTSYM files.\nS\nSelects a symbolic file for viewing. This command displays the PROTSYM Directory or CSL Directory panel,\ndepending on the file format.\nView Dynamic Symbolic Support Options\nUse the Dynamic Symbolic Support\\- Options pop-up to view dynamic symbolic support options for the Repository Viewer.\nTo view the dynamic symbolic support options, select option 5 from the Symbolic Utilities menu.\nThe Dynamic Symbolic Support\\- Options pop-up opens.\nCA SymDump Batch ------------ Report Index ------------------ Line 1 of 68 \nCommand ===>                                                   Scroll ===> CSR\n -------------------------------------------------------------------------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6179d2c4e318-1", "text": "Command ===>                                                   Scroll ===> CSR\n -------------------------------------------------------------------------------\n Re +----------------------------------------------------------------------+   \n    |  Dynamic Symbolic Support Options           * Press ENTER to Save *  |   \n Fi |                                                                      |   \n    |  NDVRDSS ===>  Y (Y/N/ )  Activate Dynamic Symbolic Support          |   \n -- |  NDVRASM ===>  Y (Y/N/ )  Always Populate non LE-enabled Assembler   | l 1\n Cm |  NDVRDSN ===>  'USER07.PROTSYM'                                      | d \n  . |                                                                      | 7\n  . |  To use the option value in effect at the time a report was          | 7\n  . |  created, leave it blank.                                            | 7\n  . |                                                                      | 7\n  . +----------------------------------------------------------------------+ 7\n 888", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ae1516b1fb73-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  .   WANDA07A  FDCHCK    CEEPLPKA  00C3A0C  U=4038  2007/09/12  14.12  USER07\n  .   WANDA07A  S0C1      LEASM0C1  00000F2  S=0C1   2007/09/12  14.12  USER07\n  .   WANDA07A  CAMRCOB2  SUBCOB2   000035E  S=0C7   2007/09/12  14.11  USER07\n  .   WANDA07B  CAMRPLI   CAMRPLI1  00006F2  S=0C7   2007/09/12  14.07  USER07\n  .   USER002R  RUN       LEASM0C1  00000F2  S=0C1   2007/09/12  13.47  USER02\n  .   WANDA07B  TESTBEAR  UNKWN1    0000000  S=0C1   2007/09/12  13.00  USER07\n  .   WANDA07B  TESTBEAR  UNKWN1    0000000  S=0C1   2007/09/12  12.40  USER07\n  .   WANDA07B  CAMRPLI   CAMRPLI1  00006F2  S=0C7   2007/09/12  12.38  USER07", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ae1516b1fb73-1", "text": ".   WANDA07B  TESTBEAR  UNKWN1    0000000  S=0C1   2007/09/12  10.26  USER07\n  .   WANDA07B  CAMRPLI   CAMRPLI1  00006F2  S=0C7   2007/09/11  16.16  USER07\n  .   WANDA07B  CAMRPLI   CAMRPLI1  00006F2  S=0C7   2007/09/11  16.12  USER07\n  .   WANDA07A  TESTBEAR  UNKWN1    0000000  S=0C1   2007/09/11  16.04  USER07\n  .   USER002R  RUN       @BMPERRI  000068E  U=4038  2007/09/10  13.59  USER02\n  .   USRSC01A  STEP1     T64       00000D2  S=0C7   2007/09/07  13.37  USER01\nOverride Dynamic Symbolic Support Options\nUse the Dynamic Symbolic Support\\- Options pop-up to change dynamic symbolic support options for the Repository\nViewer.\nFollow these steps:\n1.View the Dynamic Symbolic Support\\- Options pop-up as described in the previous procedure.\n2.Update the following fields and press Enter.\nNDVRDSS\nLets you specify whether to activate or deactivate dynamic symbolic support for Endevor .\nValues:\nY --\nActivates dynamic symbolic support for your ISPF session.\nN --\nDeactivates dynamic symbolic support for your ISPF session.\nBlank --", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ae1516b1fb73-2", "text": "N --\nDeactivates dynamic symbolic support for your ISPF session.\nBlank --\nUses the option value in effect for each report at the time the report was created.\nNDVRASM\nLets you specify whether to auto-populate the symbolic file for non-LE enabled Assembler programs when\nviewing reports in your ISPF session. This option takes effect only when the NDVRDSS option is set to ON.\nValues:\nY --\nAlways auto-populates symbolic files for non-LE-enabled Assembler programs when viewing reports\nduring your ISPF session.\nN --\nSkips auto-populate of symbolic files for non-LE-enabled Assembler programs when viewing reports\nduring your ISPF session.\nBlank --\nUses the option value in effect for each report at the time the report was created.\nNDVRDSN\nLets you specify the data set name of a PROTSYM file designated as the receiver of auto-populated symbolic\nfiles.\nWhen the data set name is fully qualified, enclose the name in quotes. If you do not use quotes, the value of\nZPREFIX  is added as the leading qualifier.\n 889", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a89937376533-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nLeave the NDVRDSN field blank to use the DSN in effect for each report at the time the report was created.\nNOTE\n\u2022When you change one or more fields before pressing Enter, the fields are validated and redisplayed.\nTo continue, press Enter one more time.\n\u2022The option values specified on this screen are locally defined and are only used when formatting a\nreport using the Repository Viewer in your ISPF session.\n\u2022The NDVRDSN value specified here is concatenated with your other symbolic files. In addition, if you\nspecified an NDVRDSN value (or CAINDVR DD) at execution time, that data set is included in the\nsearch list as well.\nRepository Viewer Commands\nThis section contains an alphabetical listing of the CAIPRINT Repository Viewer primary commands.\nFIND\nUse the FIND command to locate a string in the current display.\nSyntax\n Find <string> [P|F|L] [col1 [col2]] \n \nSynonyms\nNone.\nParameters\nstring\nLets you specify a 1- to 32-character text string (including quotes) that you can use as a search argument. If it\ncontains blanks or commas, it must be enclosed in quotes.\nP\nLets you locate the string by searching backward from the current cursor position.\nValues:\nP or PREV\nF\nLets you locate the first occurrence of the string by searching forward from the top of the data.\nValues:\nF or FIRST\nL\nLets you locate the last occurrence of the string by searching backward from the bottom of the data.\nValues:\nL or LAST\ncol1\nLets you specify a 1-origin column number in which the string must begin, or the 1-origin column number that\nbegins the range of columns in which the entire string must be found.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a89937376533-1", "text": "begins the range of columns in which the entire string must be found.\ncol2\nLets you specify a 1-origin column number that ends the range of columns in which the entire string must be\nfound.\nUsage Notes:\n 890", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4730c2899af3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022If the string is found, the cursor is positioned to the start of the string.\n\u2022If the string was found on a line or in a column that was not previously in view, the display is scrolled just enough to\ndisplay the string.\n\u2022Use the RFIND command, or FIND without an argument, to repeat the previous search from the current cursor\nposition.\n\u2022If the previous search reached the top or bottom of the file without successfully locating the search argument, a repeat\nfind command starts searching from the other end of the display, but always in the same direction as the previous\nsearch.\n\u2022Following a successful FIND command using the FIRST or LAST options, RFIND can be used to locate the next or\nprevious occurrence, respectively.\n\u2022Searching for non-displayable data is not supported.\nFM\nUse the FM command to view the contents of a data set using File Master Plus .\nSyntax\nFM     < data-set-name >\nSynonyms\nNone\nParameters\ndata-set-name\nData-set-name lets you specify the data set whose contents you would like to view using File Master Plus .\nUsage notes:\n\u2022If no argument is specified, the FM command is sensitive to the current cursor position. To view the contents of a data\nset whose name is currently displayed in the data area of the screen, place your cursor on the data set name and\npress Enter.\n\u2022You must have File Master Plus  installed and customized for this command to work. For more information, see\nConfiguring and File Master Plus  documentation.\nHELP\nUse the HELP command to display information about any command, message, topic, or panel.\nSyntax\n Help <arg |COMMANDS|MESSAGES|SCREENS|TOPICS|ALL>\n \nSynonyms\nNone.\nParameters\narg", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4730c2899af3-1", "text": "Synonyms\nNone.\nParameters\narg\nLets you specify the name of any Repository Viewer command, message, panel, or other help topic. For example,\nto request help for the PRINT primary command, type HELP PRINT  on the command line and press Enter.\nCOMMANDS\nLets you request a list of all Repository Viewer commands, from which you can select any command to request\nHELP.\n 891", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "86b5114b4f9a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMESSAGES\nLets you request a list of all Repository Viewer messages, from which you can select any message to request\nHELP.\nSCREENS\nLets you request a list of all Repository Viewer panels, including pop-up windows, from which you can select any\npanel to request HELP.\nTOPICS\nLets you request a list of all Repository Viewer help topics other than commands, messages, or panels, from\nwhich you can select any topic to request HELP.\nALL\nLets you request a list of all Repository Viewer help topics, from which you can select any topic to request HELP.\nUsage Notes:\n\u2022To request HELP for any Repository Viewer message currently displayed on your panel, no argument is required.\nSimply press the PF key you have set for HELP, or type HELP  on the command line and press Enter.\n\u2022If no message is currently displayed on your panel, entering a HELP command without any argument produces the\nhelp topic for the current panel or pop-up window.\nKEEP\nUse the KEEP command to add a data line from the current display to the Keep Window, to remove a previously added\ndata line from the Keep Window, or to change the display status of the Keep Window.\nSyntax\n Keep [ON|OFF]\n \nSynonyms\nNone.\nParameters\nON\nLets you enable the Keep Window display, if the window is not empty.\nOFF\nLets you disable the Keep Window display, suppressing the contents without discarding it.\nUsage Notes:\n\u2022If no argument is specified, the KEEP command is sensitive to the current cursor position. When the cursor is\npositioned on a data line within the display, that line is added to the Keep Window. When the cursor is positioned on a\nline within the Keep Window, that line is removed from the Keep Window.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "86b5114b4f9a-1", "text": "line within the Keep Window, that line is removed from the Keep Window.\n\u2022Data cannot be added or removed from the Keep Window when the window is disabled.\nLOCATE\nUse the LOCATE command while viewing an abend report to position your display to a previously established tag.\nSyntax\n Locate <name>\n \nSynonyms\n 892", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3e0e5e1798d2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNone.\nParameters\nname\nLets you specify the 1- to 32-character name of the previously defined tag, which will be used to reposition your\ndisplay.\nUsage Notes:\nNone.\nNOTES\nUse the NOTES command to open the Electronic Notepad for the current report.\nSyntax\n Notes\n \nSynonyms\nNone.\nParameters\nNone.\nUsage Notes:\n\u2022If a notepad does not exist for a report, you are prompted for confirmation before a new notepad is created.\n\u2022Notes are stored in your profile, which is keyed by abending program name, abending program offset, and completion\ncode. Therefore, two or more reports which share these attributes will also share a notepad.\n\u2022You can launch the electronic notepad for any report from the Report Index panel using the n line command.\nOPTIONS\nUse the OPTIONS command to view a report of your system-wide installation options, including component genlevels and\ncurrent status.\nSyntax\n Options\n \nSynonyms\n Opts\n \nParameters\nNone.\nUsage Notes\nThe same report can be obtained in batch by executing program CAOUOPTS using the sample JCL provided in\nCAI.CAVHJCL.\n 893", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "635191254dc3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPRINT\nUse the PRINT command at any time to print all or part of the current display to a printer, node. userid destination, your\nTSO userid, or a data set.\nWhen you type a PRINT command, your print options appear in the Print Options pop-up window.\nModify the following values and press Enter to print, or press END to cancel the request.\nSyntax\n PRint\n \nSynonyms\nNone.\nParameters\nThe PRINT command prompts you for input parameters using the Print Options pop-up window with the following fields:\nPrinter\nLets you specify the destination to which the printed output should be routed. This can be specified as a printer\nname, node.userid, or blank to spool the printed output to your TSO userid.\nDsname\nLets you specify the name of a data set to which the printed output is written. If this field is non-blank, it overrides\nthe Printer field. When entering a data set name, it must be fully qualified and enclosed in single quotation marks.\nOtherwise, your ZPREFIX value is used as the high-level qualifier.\nMember\nLets you specify the member name if you are printing the listing to a partitioned data set.\nDisposition\nLets you specify the disposition of the data set to which the output should be printed. This field is relevant only if\nprinting to a data set. If the value is NEW or MOD, a second window pops up to request allocation parameters.\nValues: SHR, OLD, NEW, and MOD\nTitle\nLets you specify the 1- to 32-character title that appears at the top each page.\nPrint Lines\nLets you specify the starting and ending lines to be printed. By default the starting line is set to one and the ending\nline is set to the number of lines in the report.\nCopies", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "635191254dc3-1", "text": "line is set to the number of lines in the report.\nCopies\nLets you specify the number of copies to be printed.\nClass\nLets you specify the sysout class that will be used to allocate the print output data set.\nLines / Page\nLets you specify the number of logical lines per page, including the title and header lines.\nRecord Size\nLets you specify the logical record length that will be used for the print data set. By default this is the maximum\nwidth of the data being printed. You can increase or decrease this value to fit your printer as needed. Decreasing\nthe record size may result in truncation of data.\nPageDef\nLets you specify the name of the library member that PSF uses to define the page layout for printing on a 3800\nPrinting Subsystem Model 3.\n 894", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3a31edd5ec0c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFormDef\nLets you specify the name of the library member that PSF uses to define the form layout for printing on a 3800\nPrinting Subsystem Model 3.\nChars\nLets you specify the name of the character arrangement tables for printing on a 3800 Printing Subsystem Model\n3.\nUsing a Disposition of New or MOD\nLets you specify the disposition to be used. When a disposition of NEW or MOD is used, a second pop-up panel\nis displayed.\nModify the following values and press Enter to allocate the file and print, or press End to cancel the request.\nSpace\nLets you specify the space unit for allocating the data set.  Type TRK to allocate in tracks, CYL to allocate in\ncylinders, or BLK to allocate in blocks.\nPrimary\nLets you specify the primary space quantity.  Type a number from 1 to 999.\nSecondary\nLets you specify the secondary space quantity.  Type a number from 0 to 999.\nDirectory\nLets you specify the number of blocks to be contained in the directory of the partitioned data set.  If no member\nwas specified when the data set was entered, this field is not updatable.\nDataclas\nLets you specify the data class of an SMS-managed data set.\nStorClas\nLets you specify the storage class of an SMS-managed data set.\nMgmtClas\nLets you specify the management class of an SMS-managed data set.\nBlkize\nLets you specify the block size of the data set.\nLRecl\nLets you specify the logical record length of the data set.  This field is not updatable.\nUnit\nLets you specify the Unit specification of the data set.\nVolser", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3a31edd5ec0c-1", "text": "Unit\nLets you specify the Unit specification of the data set.\nVolser\nLets you specify the volume serial on which the data set will reside. If creating a new data set using DISP=MOD,\nthis field must be left blank.\nUsage Notes:\n\u2022When one or more fields are changed before pressing Enter, the fields are validated and redisplayed along with the\nmessage Press Enter to Print. To continue, press Enter one more time.\n\u2022At the top of each printed page, the page header appears. The header contains your specified title, centered on the\nline, and the page number at the far right.\n\u2022On the first page only, following the header line, the information area is printed with double-space carriage control.\n\u2022On every page, the contents of the panel header line is printed next, also with double-space carriage control. This may\nconsist of column headings for a member list, report index or report tree display, or a ruler for listings and abend report\ncontents.\n 895", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1da7564f222f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPROFILE\nUse the PROFILE command to view or update your personal viewer preferences.\nSyntax\n PROfile\n \nSynonyms\nNone.\nParameters\nThe PROFILE command displays the Profile Settings pop-up window. You are prompted for input parameters using the\nfollowing fields:\nConfirm Exit from Reports\nLets you specify whether to request a confirmation pop-up window or to suppress the information when you close\nan open report.\nValues:\n\u2022Y -- Requests a confirmation pop-up window whenever you attempt to exit an open report.\n\u2022N -- Suppresses the confirmation.\nConfirm Report Deletes\nLets you specify whether to request a confirmation pop-up window or to suppress the confirmation when you\nattempt to delete a report.\nValues:\n\u2022Y -- Requests a confirmation pop-up window when you attempt to delete a report.\n\u2022N -- Suppresses the confirmation.\nConfirm Sym Member Deletes\nLets you specify whether to request a confirmation pop-up window or to suppress the confirmation when you\nattempt to delete a member from a symbolic file.\nValues:\n\u2022Y -- Requests a confirmation pop-up window.\n\u2022N -- Suppresses the confirmation.\nForce Upper Case Viewer\nLets you specify whether to force all output from the Repository Viewer, including output form the PRINT\ncommand, to be displayed entirely in uppercase or to enable mixed-case displays and printing.\nValues:\n\u2022Y -- Displays all output from the Repository Viewer entirely in uppercase.\n\u2022N -- Enables mixed-case displays and printing.\nDisplay Information Area\nLets you specify whether to let the information area display immediately below the command line in every viewer\ndisplay or to suppress the information area on all displays.\nValues:\n\u2022Y -- Enables the information area to display immediately below the command line in every viewer display.\n\u2022N -- Suppresses the information area on all displays.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1da7564f222f-1", "text": "\u2022N -- Suppresses the information area on all displays.\nNote:  Filters are part of the information area. If this field is set to N, the filters will not be displayed. However, their\nvalues will still affect the Report Index selection list.\n 896", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a8e0e06e7180-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMessage Alarm Severity\nLets you specify the lowest message severity I, W, or E, which should trigger the alarm to sound when messages\nof equal or greater severity are displayed on your panel.\nPROTSYM Password (Hidden)\nLets you specify the one- to eight-character password for your PROTSYM files that was created by your system\nadministrator when this product was installed. If omitted, you are prompted for a PROTSYM file in each session.\nUsage Notes:\n\u2022Press END to cancel the update request, or Enter to save your changes.\n\u2022When one or more fields are changed before pressing Enter, the fields are validated and redisplayed. To continue,\npress Enter one more time.\n\u2022Profile changes take effect immediately.\nREFRESH\nUse the REFRESH command from the Report Index panel to refresh the contents of the current display.\nThis has the same effect as using a SETINDEX command to reload the repository index without changing the repository\ndata set name.\nSyntax\n REFresh\n \nSynonyms\nNone.\nParameters\nNone.\nUsage Notes:\nNone.\nRFIND\nUse the RFIND command to repeat a previous search.\nSyntax\n RFind\n \nSynonyms\nNone.\nParameters\nNone.\nUsage Notes:\n 897", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "373e876082b5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Using RFIND produces exactly the same results as using FIND without a search argument.\n\u2022If no previous FIND existed, the RFIND command ends in error.\n\u2022If the string was found on a line or in a column that was not previously in view, the display is scrolled just enough to\ndisplay the string.\n\u2022If the previous search reached the top or bottom of the file without successfully locating the search argument, a repeat\nFIND command starts searching from the other end of the display, but always in the same direction as the previous\nsearch.\n\u2022Searching for non-displayable data is not supported.\nSETINDEX\nUse the SETINDEX command from the Report Index panel to switch your view to another repository data set.\nSyntax\n SETindex <dsname>\n \nSynonyms\nNone.\nParameters\ndsname\nLets you specify the data set name of the new repository file. If the data set name is enclosed in single quotation\nmarks, it is fully qualified. Else, your ZPREFIX value is used for the leading qualifier.\nIf the data set name is specified, this value is used to populate the dsname field in the Enter Repository Dsname\npop-up window that displays when a SETINDEX command is entered.\nUsage Notes:\n\u2022If you enter an invalid repository name, or the repository contains no abend reports, you are presented with a blank\nindex display. Repeat the command using a valid data set name.\n\u2022To select the installation default repository data set for your system, do not enter a data set name when prompted.\n\u2022The repository data set name is stored in your personal profile and retrieved again the next time you start the viewer.\nSORT\nUse the SORT command to sort the current display in ascending or descending order on any column header. The SORT\ncommand is only valid from the following displays:\n\u2022Report Index panel", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "373e876082b5-1", "text": "command is only valid from the following displays:\n\u2022Report Index panel\n\u2022Symbolic File Member select list panel\nSyntax\n Sort <column-header> [A|D] [H]\n \nSynonyms\nNone.\nParameters\ncolumn-header\nLets you specify the name of the column on which the sort should be performed, from the header line at the top of\nthe display.\n 898", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "50c4e0c9471c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nA|D\nLets you specify the values A or D to sort the display in ascending or descending order.\nValues: A, D\nH\nLets you sort the hexadecimal numeric values. This allows digits A - F to compare greater than 0 - 9.\nUsage Notes:\nAfter sorting a display, SORT * returns the display to its original order.\nSYM\nUse the SYM command to display the Symbolic Utilities menu.\nSyntax\n SYM <option>\n \nSynonyms\n CSL, CPP, LISTcsl, PROTsym, Utilities, DSS\n \nParameters\noption\nLets you prime the selection field to any of the valid menu items:\n\u2022List the contents of a PROTYSM or CSL symbolic file. After the list is displayed, you can browse, print, or\ndelete members using line commands from the selection list.\n\u2022Add listings to a PROTSYM file.\n\u2022List symbolic files defined globally in your installation options table CAOUDFRX. After the list is displayed,\nuse the S line command to list the contents of any symbolic file, or the A line command to add members to a\nPROTSYM file.\n\u2022Add or Remove supplemental symbolic files defined locally to your viewer profile. After the list is displayed,\nuse the S line command to list the contents of any symbolic file, or the A line command to add members to a\nPROTSYM file.\n\u2022View or change the Endevor  symbolic support options defined locally to your viewer profile. Once the options\ndisplay, overtype the values to change them.\nUsage Notes:\n\u2022The last symbolic file referenced by any of the symbolic utilities is automatically saved in the Symbolic File Dsname\nfield.\n\u2022For online help for a symbolic utility, select the option for that utility and press PF1.\nTAG", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "50c4e0c9471c-1", "text": "TAG\nUse the TAG command while viewing a report to equate a line number to your current position within the report.\nSyntax\n TAG <name>\n \nSynonyms\n .name\n 899", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d55da42834a3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n \nParameters\nname\nLets you specify any 1- to 32-character name that will become equated with your current position within the report\nyou are viewing.\nUsage Notes:\n\u2022Entering a duplicate tag name replaces the previous tag with the new report position. Two tags cannot share the same\nname.\n\u2022Use the LOCATE command to position your display using a previously defined tag.\n\u2022All tags are automatically deleted when you close and exit a report.\nVIEW\nUse the VIEW command while viewing a report to display the listing for a specified program.\nThe VIEW command displays the version of the listing that was used to provide symbolic information when the report was\nformatted. If no symbolic information was provided for the program in the report you are viewing, use the SYM command\ninstead.\nSyntax\n View <program-name>\n \nSynonyms\nNone.\nParameters\nprogram-name\nLets you specify the program name that was formatted with symbolic information in the report you are viewing.\nSymDump  Batch Utilities\nThe following reporting facilities are provided to measure the use and effectiveness of the product:\n\u2022The Management Reporting System (MRS) provides a means for you to audit your load module libraries.\n\u2022The Initialization Summary generates a report describing which SymDump  Batch modules are currently loaded in the\nCSA area of LPA.\n\u2022The Options Summary reports on the options set as installation defaults.\n\u2022The CSL Summary reports on the contents of a specified CSL or on all of the CSLs defined as installation defaults.\n\u2022The CAIPRINT Repository Utility provides a means for you to list and maintain the contents of the central VSAM\nrepository.\nSymbolic file (PROTSYM) utilities are also provided. For a description of these utilities, see Symbolic Support.\nManagement Reporting System (MRS)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d55da42834a3-1", "text": "Management Reporting System (MRS)\nThe Management Reporting System scans any load module library and reports on the COBOL programs contained within\neach member. MRS produces two reports, a detailed report and a summary report, indicating the size and characteristics\nof each load module in a selected library.\n 900", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6e67cfe9eaad-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMRS reads the members of a specified library and identifies and lists COBOL CSECTs and load modules that contain\nthem. It also provides compilation and size information for these CSECTS and indicates whether they are processed by\nOptimizer/II  or Optimizer/II .\nJCL\nA procedure called CAIMRSII is provided to invoke MRS. To obtain detail and summary reports for library\nPROD1.LOADLIB, specify the following:\n // EXEC CAIMRSII,LIBRARY='PROD1.LOADLIB'\n \nThe MRS program, CAOUMRS, uses the following DD statements:\nDD Statement Description\nSTEPLIB Defines the library containing MRS.\nSYSPRINT Defines the MRS report file.\nSYSLIB Defines the library to be analyzed.\nNOTE\nThe ddname for the library to be analyzed is an installation option with a default of SYSLIB. If the ddname was\nchanged during installation, ensure that the procedure CAIMRSII was changed too.\nReports\nMRS provides the following two reports for each load library that is scanned:\n\u2022The Load Library Analysis Detailed Report is a detailed listing of all COBOL CSECTs in the library.\n\u2022The Load Library Analysis Summary Report is a summary of all of the library's statistics.\nLoad Library Analysis Detailed Report\nThe Load Library Analysis Detailed report lists all of the load modules in the library that contain COBOL CSECTs. A\nsample report is shown next:\n LEGEND FOR OPTIMIZER OPTIONS:\n D=DTECT C=XCOUNT X=XTIME P=PFLOW S=SUBRNGCK R=PARMCHK B=DBGSLEEP F=FDCHECK W=WSINIT I=CICS E=EOS L=WSCLEAR\n H=PUSHPOP O=CASORT", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6e67cfe9eaad-1", "text": "H=PUSHPOP O=CASORT\n MODULE  MODULE-SIZE CSECT   CSECT-SIZE  PROC-SIZE   DATA-SIZE   COMPILER-ID  RE  DATE       TIME      CA-OPT\n REL DCXPSRBFWIELHO    \n IX101A   9,376 IX101A        8,276      3,826       4,450       C2  5668-958 3.2 08/13/2003 13.54.45  NONE  \n IX102A  12,440 IX102A       11,340      6,432       4,908       C2  5668-958 3.2 08/13/2003 13.54.45  NONE  \n IX103A  13,128 IX103A       12,028      6,952       5,076       C2  5668-958 3.2 08/13/2003 13.54.46  NONE  \n IX104A  12,880 IX104A       11,782      6,266       5,516       C2  5668-958 3.2 08/13/2003 13.54.45  NONE  \n IX105A  17,048 IX105A       15,950      9,128       6,822       C2  5668-958 3.2 08/13/2003 13.54.46  NONE  \n IX106A  22,824 IX106A       21,726     10,990      10,736       C2  5668-958 3.2 08/13/2003 13.54.45  NONE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6e67cfe9eaad-2", "text": "IX107A  15,536 IX107A       14,440      8,762       5,678       C2  5668-958 3.2 08/13/2003 13.54.46  NONE  \n IX108A  20,560 IX108A       19,458     12,840       6,618       C2  5668-958 3.2 08/13/2003 13.54.09  NONE  \n IX109A  15,968 IX109A       14,868      7,070       7,798       C2  5668-958 3.2 08/13/2003 13.54.15  NONE  \n IX110A  10,048 IX110A        8,948      4,168       4,780       C2  5668-958 3.2 08/13/2003 13.54.15  NONE  \n IX111A   9,584 IX111A        8,486      3,454       5,032       C2  5668-958 3.2 08/13/2003 13.54.15  NONE  \n IX112A  14,224 IX112A       13,124      5,772       7,352       C2  5668-958 3.2 08/13/2003 13.54.16  NONE  \n IX113A  12,472 IX113A       11,372      4,206       7,166       C2  5668-958 3.2 08/13/2003 13.54.16  NONE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6e67cfe9eaad-3", "text": "IX114A  11,944 IX114A       10,844      3,814       7,030       C2  5668-958 3.2 08/13/2003 13.54.15  NONE  \n 901", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6c0ccafd2578-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n IX115A  11,896 IX115A       10,796      3,770       7,026       C2  5668-958 3.2 08/13/2003 13.54.49  NONE  \n IX116A  11,888 IX116A       10,788      3,762       7,026       C2  5668-958 3.2 08/13/2003 13.54.52  NONE  \n IX117A  11,896 IX117A       10,796      3,766       7,030       C2  5668-958 3.2 08/13/2003 13.54.51  NONE  \n IX118A  11,928 IX118A       10,828      3,806       7,022       C2  5668-958 3.2 08/13/2003 13.54.52  NONE  \n IX119A  12,168 IX119A       11,068      3,976       7,092       C2  5668-958 3.2 08/13/2003 13.54.51  NONE  \n IX120A  11,704 IX120A       10,604      3,580       7,024       C2  5668-958 3.2 08/13/2003 13.54.52  NONE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6c0ccafd2578-1", "text": "IX121A  12,952 IX121A       11,852      4,660       7,192       C2  5668-958 3.2 08/13/2003 13.54.52  NONE  \n IX201A   9,424 IX201A        8,324      3,826       4,498       C2  5668-958 3.2 08/16/2003 12.26.51  NONE  \n IX202A  12,504 IX202A       11,404      6,468       4,936       C2  5668-958 3.2 08/16/2003 12.26.52  NONE  \n IX203A  13,128 IX203A       12,028      6,910       5,118       C2  5668-958 3.2 08/16/2003 12.26.53  NONE  \n IX204A  12,896 IX204A       11,798      6,298       5,500       C2  5668-958 3.2 08/16/2003 12.26.53  NONE  \n IX205A  19,728 IX205A       18,288      9,518       8,770       C2  5668-958 3.2 08/16/2003 14.13.25  OPT/II\n 2.0 DCXPSR.FW.....", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6c0ccafd2578-2", "text": "2.0 DCXPSR.FW..... \n IX206A  13,904 IX206A       12,804      7,572       5,232       C2  5668-958 3.2 08/16/2003 12.26.55  NONE  \n IX207A  15,960 IX207A       14,864      8,760       6,104       C2  5668-958 3.2 08/16/2003 12.26.56  NONE  \n IX208A  24,776 IX208A       23,680     17,004       6,676       C2  5668-958 3.2 08/16/2003 12.26.56  NONE  \n IX209A  39,504 IX209A       38,404     26,034      12,370       C2  5668-958 3.2 08/16/2003 12.26.56  NONE  \n IX210A  33,616 IX210A       32,520     20,650      11,870       C2  5668-958 3.2 08/16/2003 12.26.57  NONE  \n IX211A  19,072 IX211A       17,972      8,240       9,732       C2  5668-958 3.2 08/16/2003 12.26.57  NONE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6c0ccafd2578-3", "text": "IX212A  18,936 IX212A       17,840     11,292       6,548       C2  5668-958 3.2 08/16/2003 12.26.57  NONE  \n IX213A  18,328 IX213A       17,232     11,240       5,992       C2  5668-958 3.2 08/16/2003 12.26.57  NONE  \n IX214A  34,032 IX214A       32,936     21,034      11,902       C2  5668-958 3.2 08/16/2003 12.26.59  NONE  \n IX215A  48,584 IX215A       47,486     33,168      14,318       C2  5668-958 3.2 08/16/2003 12.27.01  NONE  \n IX216A  13,400 IX216A       12,298      6,610       5,688       C2  5668-958 3.2 08/16/2003 12.27.02  NONE  \n IX217A  11,400 IX217A       10,302      5,168       5,134       C2  5668-958 3.2 08/16/2003 12.27.01  NONE  \n IX218A  10,648 IX218A        9,550      4,474       5,076       C2  5668-958 3.2 08/16/2003 12.27.04  NONE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6c0ccafd2578-4", "text": "IX301M   3,264 IX301M        2,164        694       1,470       C2  5668-958 3.2 08/16/2003 12.27.08  NONE  \n IX302M   3,896 IX302M        2,796        136       2,660       C2  5668-958 3.2 08/16/2003 12.27.08  NONE  \n IX401M   3,496 IX401M        2,398        464       1,934       C2  5668-958 3.2 08/16/2003 12.27.08  NONE  \n RL206A  13,256 RL206A       11,814      5,248       6,566       C2  5668-958 3.2 09/16/2003 10.57.29  OPT/II\n 2.0 DCXPSR.FW..... \n SQ124A  20,968 SQ124A       19,522     10,368       9,154       C2  5668-958 3.2 06/18/2002 13.32.01  OPT/II\n 2.0 DCXPSR.FW..... \n ST140A  22,232 ST140A       20,778     11,162       9,616       C2  5668-958 4.0 06/25/2002 15.35.57  OPT/II\n 2.0 DCXPSR.FW..... \n TOTALS: 719,416            668,576    363,338     305,238", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6c0ccafd2578-5", "text": "The report displays the following information:\nLEGEND FOR OPTIMIZER OPTIONS\nLets you specify the meaning of each letter that appears in the last column. All the options for execution-time\nfacilities that can be specified at compile/optimize time are listed in the report.\nMODULE\nLists the names of the load modules that contain at least one COBOL CSECT.\nMODULE-SIZE\nDisplays the total number of bytes in each load module listed.\nNOTE\nFor overlay modules, the size specifies the maximum amount of memory used by the module and not\nthe sum of the CSECTs contained in it.\n 902", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0d0263330724-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCSECT\nLists all the COBOL CSECT names in each load module. Multiple COBOL CSECTs within a given load module\nprint on a separate line.\nCSECT-SIZE\nDisplays the total number of bytes in each COBOL CSECT.\nPROC-SIZE\nDisplays the number of bytes for the program's Procedure code. See Usage Considerations for more information.\nDATA-SIZE\nDisplays the number of bytes of storage generated by the compiler for the COBOL program's Data Division. For\nmore information about Data Division, see Usage Considerations.\nCOMPILER-ID\nIdentifies the type of COBOL compiler used and the compiler's program product number and version number.\nMRS copies the program product number and the version number directly from the COBOL module.\nREL, DATE, and TIME\nDisplays the release of the COBOL compiler used and the date and time of the program's compilation (copied\ndirectly from the COBOL module).\nCA-OPT version release\nVerifies whether the COBOL CSECT is processed with an Optimizer/II  product. The release number indicates the\nrelease with which the CSECT was optimized.\n\u2022YES indicates that the CSECT was optimized with an earlier release that did not retain release numbers in the\nload module.\n\u2022NONE indicates that the CSECT is not processed with Optimizer/II .\nIn some instances, the compiler program product number, version number, and the date and time of compilation\nmay not be available. In this case, an UNAVAILABLE message appears.\nThe last column shows whether certain Optimizer/II  or Optimizer/II  execution-time options were specified at\ncompile or optimize time. If the program was optimized using Optimizer/II , then only the letters for DTECT,", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0d0263330724-1", "text": "PFLOW, or XCOUNT appear even if the options FDCHECK, SUBRNGCK, or WSINIT were specified at compile\ntime.\nThe last line of the report specifies the following totals in bytes (1024 KB):\n\u2022Load modules listed on the report\n\u2022COBOL CSECTs\n\u2022Number of data bytes\n\u2022Number of procedure bytes from the COBOL CSECTs\nLoad Library Analysis Summary Report\nThe Load Library Analysis Summary report follows the Load Library Analysis Detailed report and provides summarized\nstatistical information about the library being scanned.\n COMPILER-ID   REL MODULES  CSECTS   OPTOS OPTII   DTE   XCO   XTI   PFL   SUB   PAR   DBG   FDC   WSI   CIC \n  EOS   WSC   PUS   CAS \n  C2  5668-958 3.2      44      44   0     3     3     3     3     3     3     3     0     3     3     0     0\n     0     0     0 \n  C2  5668-958 4.0       1       1   0     1     1     1     1     1     1     1     0     1     1     0     0\n     0     0     0 \n TOTALS: COBOL          45      45   0     4     4     4     4     4     4     4     0     4     4     0     0\n     0     0     0 \n         IGZ            45      45\n         CAO             4       4", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0d0263330724-2", "text": "IGZ            45      45\n         CAO             4       4\n 903", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "20f20e351b12-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n         ALL            45      94\n *----------------------------------------------------------------------------------------------------------------------------------\n*\n * For programs which have been compiled using CA-OPTIMIZER, only DTECT, XCOUNT, and CICS are reflected in\n these MRS reports.       *\n * More information regarding the options used during optimization is only available for programs compiled\n using CA-OPTIMIZER/II.   *\n *----------------------------------------------------------------------------------------------------------------------------------\n*\n \nFor programs that are compiled using Optimizer/II , only DTECT, XCOUNT, and CICS are reflected in these MRS reports.\nMore information regarding the options used during optimization is only available for programs compiled using Optimizer/\nII.\nThe Load Library Analysis Summary report displays the following information:\nIGZ, CEE, CAO\nDisplays the number of modules containing COBOL CSECTs and the total number of COBOL CSECTs.\nALL\nDisplays the total number of modules and CSECTs in the library.\nThe next part of the Summary Report provides a summary of Optimizer/II  and Optimizer/II  options in effect by compiler\ntype and version.\nCOMPILER ID\nLists the compiler type and version used.\nOPTOS\nDisplays the number of programs compiled under the listed compiler version that were compiled and optimized\nwith Optimizer/II .\nOPTII\nDisplays the number of programs compiled under the listed compiler version that were compiled and optimized\nwith Optimizer/II .\nTOTALS\nDisplays the total number of programs that were optimized using the various options listed.\nUsage Considerations\nMRS analyzes any standard IBM load module library, but does not support concatenated load library data sets. Specify\neach load library to be analyzed in a separate MRS execution run.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "20f20e351b12-1", "text": "each load library to be analyzed in a separate MRS execution run.\nMRS recognizes COBOL CSECTs that are compiled using the following IBM COBOL compilers: V2, V3, V4, OS/VS\nCOBOL, COBOL II, COBOL 370, COBOL for MVS and VM, COBOL for OS/390 and VM, Enterprise COBOL for z/OS and\nOS/390, and Enterprise COBOL for z/OS.\nOS/VS COBOL Reporting\nMRS makes a distinction between data bytes and procedure bytes in the detailed report. Data bytes include the storage\nsize in the CSECT that is directly generated by the COBOL CSECTs Data Division plus the INIT1 code. (Data bytes are\nfigured from the beginning of the program to the TGT.) Procedure bytes include the storage size of the remainder of the\nCSECT. The sections of the CSECT that make up the procedure bytes are as follows:\n 904", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "96283e245470-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022TGT\n\u2022PGT\n\u2022Report Writer Routines\n\u2022COBOL Procedure Division\n\u2022Q Routines\n\u2022INIT2\n\u2022INIT3\nCOBOL II and Above\nWhen reporting for COBOL II and above, MRS distinguishes between data and procedure bytes. The data bytes include\nonly the areas in the program generated at compile time, and do not include data areas acquired dynamically at execution\ntime for a program compiled with the RENT option. The sections of the CSECT that make up the procedure bytes are as\nfollows:\n\u2022Signature Code\n\u2022INITD Code (for RENT programs)\n\u2022Q Routines\n\u2022Procedure Division\nOptions Summary Report\nThe Options Summary produces a report detailing your installations default options.\nJCL\nA procedure called CAIOPTNS is provided to invoke the Options Summary program. To obtain an options summary for\nyour data center, specify the following:\n// EXEC   CAIOPTNS\nThe initialization summary program, CAOUOPTS, uses the following DD statements:\nDD Statement Description\nSTEPLIB Defines the library containing SymDump  Batch Options Summary\nprogram and options modules.\nSYSPRINT Defines the report file.\nReport\nA sample of the Options Summary is as follows:\n*                                                            \n*  EXECUTION TIME DEFAULTS:                                  \n*                                                            \n*  CEEDUMP    =  OFF                                         \n*  DUPLIM     =  5                                           \n*  EXPDAYS    =  0                                           \n     .           .\n     .           .\n 905", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dda536ed2197-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n*  SYSOUTD    =                                              \n*  UNIT       =  SYSDA                                       \n*                                                            \n*  CAOUXMOD   =  CAO                                         \n*  CAOUXMOD   =  CEE                                         \n*  CAOUXMOD   =  IGZ                                         \n*  CAOUXMOD   =  ILBO                                        \n*  CAOUXMOD   =  IN25                                        \n*                                                            \n*  CAOUSYM    =  CAI.PROTSYM                            \n*                                                                        \n*************************************************************************\n    SUPPORT IS ACTIVE                                                    \n    SQA ANCHOR LOADED AT 82A3D2F0                                        \n                                                                         \n                                                                         \n    REPORTING OPTIONS:                                                   \n                                                                         \n    OPTION         STATUS         FIXED                                  \n                                                                         \n    ACB            =  OFF                                                \n    ACTONLY        =  OFF                                                \n    AMB            =  OFF                                                \n     .                .\n     .                .\n    WORKSTOR       =  ON                          \n    WTOXCL         =  ON                          \n                                                  \n    LOGGING OPTIONS:                              \n                                                  \n    OPTION         STATUS         FIXED           \n                                                  \n    LOGTSO         =  ON                          \n    LOGNET         =  OFF                   \n    LOGROS         =  ON                    \n    LOGUNI         =  OFF                   \n    LOGWTO         =  ON                    \n    LOGWTL         =  OFF                   \n    SMF            =  OFF                   \n                                            \n    CONTROL OPTIONS:                        \n                                            \n    MCHAR VALUE  = ?                        \n    PCHAR VALUE  = *                        \n    RCHAR VALUE  = :                        \n    SYSOUT VALUE = *                        \n    MAXBLL       = 512                      \n                                            \n    DEFAULT DATA SET NAMES:                 \n                                            \n    NTMGCCTL       CAI.NTMMGCTL", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dda536ed2197-1", "text": "NTMGCCTL       CAI.NTMMGCTL             \n    NTMPI          CAI.NTMPI                \n    NTMSC          CAI.NTMSC                \n 906", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "52edc9983087-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    CAIOPTS FILE SUFFIX           CAIOPTS  \nCSL Summary Report\nThe CSL Summary produces a report of all members in the Condensed Source Listing library. The user can select to\nreport on a single CSL or on all of the CSLs defined as installation defaults.\nNOTE\nSymDump  Batch no longer writes symbolic information using the CSL format. This utility provides summary\ninformation for CSL libraries that were populated by earlier versions of the product. These CSL libraries may\nstill be used as input to the report formatter. However, as programs are recompiled, their updated symbolic\ninformation can only be written using the PROTSYM format.\nJCL\nA procedure called CAICSLD is provided to invoke the Condensed Source Listing Summary program. To obtain a CSL\nSummary for your data center, specify the following:\n// EXEC   CAICSLD\nThe CSL summary program, CAOUOPTS, uses the following DD statements:\nDD Statement Description\nSTEPLIB Defines the library containing SymDump  Batch CSL Summary\nprogram.\nSYSPRINT Defines the report file.\nCAISYM (Optional) Defines the Condensed Source Listing library to be\nreported on.\nNOTE\nThe ddname for the CSL is an installation option that can be modified. If it is modified at your installation, be\nsure to also change the ddname in procedure CAOUCSLD. If omitted, CAOUCSLD reports on all of the CSLs\ndefined as installation defaults.\nReport\nThis sample report shows the information and the format of the condensed source listing summary:\n                    CONDENSED SOURCE LIBRARY\n                     DATA SET NAME = USER002.CSL\nPROGRAM ID      DATE COMPILE   TIME COMPILED GENLEVEL  RELEASE  COMPILER", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "52edc9983087-1", "text": "PROGRAM ID      DATE COMPILE   TIME COMPILED GENLEVEL  RELEASE  COMPILER    \n--[A]------     ----- [B]--------- [C]----------- [D]-------[E]-------- [F]---\nABEND           05 May,2004    12:55:21     0004OX220   2.2     COBOL II    \nCALLDETH        24 Nov,2003    16:42:27     9906OX210   2.1     COB OS390   \nCALLIVP1        23 Jan,2004    12:05:01     9912RX220   2.2     COB OS390   \nCAOUTC2K        16 Jan,2004    16:56:51     9912HH100   1.0     COB OS390   \nCAO2DB2         05 Apr,2004    14:37:22     0002RX220   2.2     COB OS390   \nCAO2DEMO        14 Jul,2003    16:25:47     0007W9800   1.0     COB OS390   \nCAO2DEMR        06 NOV,2003    17:27:03     9709OX210   2.1     COB OS390   \nCAO2IDMS        04 Apr,2003    13:29:58     0002RX220   2.2     COB OS390   \nCCDEMO03        08 Nov,2002    10:53:01     9909OX220   2.2     COB OS390   \n 907", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "561f0acb34b2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCOB0C7          05 May,2004    14:20:08     0004RX220   2.2     COB OS390   \nDB2ADD          26 Apr,2004    09:35:19     0106AOX00   3.0     COB OS390   \nDB2CAF          24 Mar,2004    16:20:46     0002OX220   2.2     COB OS390   \nDB2DEL          26 Apr,2004    09:35:28     0106AOX00   3.0     COB OS390   \nDB2DEMO         26 Apr,2004    09:35:10     0106A0X00   3.0     COB OS390   \nDB2LIST         08 Sep,2002    18:24:28     9909OX220   2.2     COB OS390   \nDB2LISTM        07 Sep,2002    14:01:07     9909OX220   2.2     COB OS390   \nDB2LIST2        08 Sep,2002    18:25:05     9909OX220   2.2     COB OS390   \nDB2MSG          07 Sep,2002    14:08:38     9909OX220   2.2     COB OS390   \nDB2PLANS        25 Apr,2003    10:41:17     0002OX220   2.2     COB OS390", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "561f0acb34b2-1", "text": "DB2TBLS         07 Mar,2003    15:07:54     0002OX220   2.2     COB OS390   \nDB2UPD          25 Apr,2003    09:35:39     0106AOX00   3.0     COB OS390   \nDFSSAM01        14 Jul,2003    10:27:44     0007OX220   2.2     COBOL II    \nENTRIES         05 Feb,2002    17:08:55     9812HH100   1.0     COB OS390   \nIC114A          11 Jul,2003    12:59:13     0007OX220   2.2     COB OS390   \nMAINPGM         05 Feb,2002    17:08:47     9812HH100   1.0     COB OS390   \nMAINPROG        30 Apr,2002    17:09:41     9903OX210   2.1     COB OS390   \nMAIN1           06 DEC,2002    17:37:45     9912OM610   6.1     VS COBOL    \nMWP503          11 Feb,2004    16:16:51     9912OX220   2.2     COB OS390   \nMWP635          08 May,2003    09:35:31     0004RX220   2.2     COBOL II    \nM648884A        06 Jun,2003    17:50:29     0106AOX00   3.0     COBOL II", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "561f0acb34b2-2", "text": "OPIMSDMO        11 Jul,2003    18:27:50     0007RX220   2.2     COBOL MVS   \nPSIMPLE         13 JAN,2002    15:46:02     9712OX210   2.1     COBOL MVS   \nSTOPRUN         03 May,2004    10:48:28     0004RX220   2.2     COBOL II    \nSUBPGM          06 Oct,2002    16:09:37     9813OX220   2.2     COBOL II    \nSUBPROG         20 May,2002    13:13:03     9504OX130   1.3     COBOL II    \nSUBPROGA        30 Apr,2002    17:09:36     9903OX210   2.1     COB OS390   \nSVTEST          28 Mar,2003    11:18:37     0002OX220   2.2     COBOL II    \nTESTMRG         11 Feb,2003    14:57:15     9912OX220   2.2     COB OS390   \nXACD912         26 Jun,2003    11:37:38     9912HH100   1.0     COB OS390   \nTOTAL NUMBER OF COBOL II PROGRAMS       =   8   [G]   \nTOTAL NUMBER OF VS COBOL PROGRAMS       =   1   \nTOTAL NUMBER OF COBOL FOR MVS PROGRAMS      =   2   \nTOTAL NUMBER OF COBOL FOR OS/390 PROGRAMS   =   28", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "561f0acb34b2-3", "text": "TOTAL NUMBER OF COBOL FOR OS/390 PROGRAMS   =   28  \nTOTAL NUMBER OF PROGRAMS            =   39  \nThe Condensed Source Listing Summary report displays the following information:\n[A]\nLists the program IDs.\n[B]\nDisplays the date when the program was compiled.\n[C]\nDisplays the time when the program was compiled.\n[D]\nDisplays the genlevel of SymDump  Batch when the CSL was created.\n[E]\nDisplays the release of SymDump  Batch when the CSL was created.\n[F]\nDisplays the compiler used.\n 908", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "519d506e3bce-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n[G]\nDisplays the totals for each CSL reported on.\nCAIPRINT Repository Utility\nThe CAIPRINT repository utility provides a batch facility to list and maintain the contents of the central VSAM repository.\nJCL\nA procedure called CAIPRTU is provided to invoke the CAIPRINT Repository Maintenance Utility, CAOUPRTU. To display\nor maintain the contents of your repository, specify the following:\n// EXEC CAIPRTU \n//PRTU.SYSIN DD * \n(commands go here) \n/*\nCAOUPRTU uses the following DD statements:\nDD Statement Description\nSTEPLIB Defines the library containing SymDump  Batch.\nSYSPRINT Defines the report file.\nSYSUT1 Defines the work file used for some requests.\nCommands\nThe syntax of any command is:\nkeyword <selection criteria>\nkeyword\nLets you specify one of the command keywords listed in this section.\nselection criteria\nLets you specify the selection criteria comprised of an argument and optionally an operator and a value.\nExample:\nLIST DATE GT 2004/04/06\nIn this example, the LIST keyword is used to display a summary of reports that were created in the repository after\nApril 6, 2004. The selection criteria is comprised of the DATE argument, the GT (for Greater Than) operator and\nthe value 2004/04/06.\nCommand Keywords\nFollowing are the supported command keywords:\nCOPY\nLets you copy reports from a secondary repository (ODSN) to your primary repository (DSN). Requires that both\nDSN and ODSN be specified.\nDELETE\nLets you delete selected reports from a repository (DSN). The DSN must be specified.\n 909", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e40f54b54a49-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDSN\nLets you define the dsname for your primary CAIPRINT repository. The dsname must be specified prior to using\nany other commands.\nERRSUM\nLists a summary of abend reports contained within a repository (DSN). The summary includes the program name,\noffset, and abend code, and a count indicating the number of reports found with the same information. The entries\nare displayed in alphabetical order, by program name. Requires that DSN be specified.\nINIT\nLets you initialize a newly defined repository (DSN). Requires that DSN be specified.\nJOBSUM\nLists a summary of abend reports contained within a repository (DSN), by job name. The summary includes the\njob name, program name, offset, and abend code, and a count indicating the number of reports found with the\nsame information. The entries are displayed in alphabetical order by job name and program name. Requires that\nDSN be specified.\nLIST\nLists a summary of reports contained within a repository (DSN). Requires that DSN be specified.\nLOCK\nLets you lock one or more reports in a repository (DSN) to prevent deletion. Requires that DSN be specified.\nODSN\nLets you specify  the dsname for a secondary CAIPRINT repository. Must be specified prior to using the COPY\ncommand.\nUNLOCK\nLets you unlock one or more locked reports in a repository (DSN) to enable the deletion. Requires that DSN be\nspecified.\nNOTE\nThe dsname must be specified prior to using any other commands.\nArguments\nValid arguments for selection criteria include the following:\nAGE\nLets you select reports by the number of days since they were created. This argument requires an operator and a\n1- to 3-digit value.\nExample:\nDELETE AGE GT 5\nALL", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e40f54b54a49-1", "text": "1- to 3-digit value.\nExample:\nDELETE AGE GT 5\nALL\nLets you select every report unconditionally, with no operator or value specified.\nExample:\nUNLOCK ALL\nCODE\nLets you select reports by the completion code of the step that produced the report. This argument requires an\noperator and a 4- to 7-character value.\nExample:\nLIST CODE EQ S0C7\n(or) LIST CODE EQ U1125\n(or) LIST CODE EQ RC0004\n(or) LIST CODE EQ CEE3250\nSystem abend codes must begin with S followed by three hexadecimal digits.\n 910", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "be3ebfa8b2fc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUser abend codes must begin with U followed by four decimal digits. Return codes must begin with RC followed\nby four decimal digits. IBM message codes must be 1- to 7-characters.\nDATE\nLets you select reports by the date on which they were created. This argument requires an operator and a value\nin the format yyyy/mm/dd.\nExample:\nDELETE DATE LT 2004/04/06\nJOB\nLets you select reports by the name of the job that produced the report. This argument requires an operator and a\n1- to 8-character value.\nExample:\nUNLOCK JOB NE OPTJOB1\nLOCK\nLets you select reports by the ID of the user that owns a lock on the report. This argument requires an operator\nand a 1- to 7-character value.\nExample:\nLIST LOCK EQ OPTUSER\nPGM\nLets you select reports by the name of the abending program that caused the report. This argument requires an\noperator and a 1- to 8-character value.\nExample:\nDELETE PGM EQ CAO2DEMO\nSTEP\nLets you select reports by the name of the step that produced the report. This argument requires an operator and\na 1- to 8-character value.\nExample:\nLIST STEP NE GO\nNOTE\nIf the abend report was generated in an IMS DC environment under LE, STEP represents the Task ID.\nSYSTEM\nLets you select reports by the 1- to 8-character name of the system on which the report was created.\nExample:\nCOPY SYSTEM EQ PRODZ1\nUSER\nLets you select reports by the ID of the user who submitted the job that produced the report. This argument\nrequires an operator and a 1- to 7-character value.\nExample:\nLOCK USER EQ OPTUSER\nOperators", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "be3ebfa8b2fc-1", "text": "Example:\nLOCK USER EQ OPTUSER\nOperators\nValid operators include the following:\nEQ\nSelects reports if the value of the argument is equal to the value specified.\nGE\nSelects reports if the value of the argument is greater than or equal to the value specified.\n 911", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3fe99257f468-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nGT\nSelects reports if the value of the argument is greater than the value specified.\nLE\nSelects reports if the value of the argument is less than or equal to the value specified.\nLT\nSelects reports if the value of the argument is less than the value specified.\nNE\nSelects reports if the value of the argument is not equal to the value specified.\nRANGE\nSelects reports if the value of the argument is between the two values specified.\nDynamic Symbolic Support\nThe dynamic symbolic support feature, when activated, dynamically retrieves the compiler or assembler listing of the\nprogram being printed or viewed from a listing data set managed by Endevor  and loads it into the designated PROTSYM\nfile. For this feature to work, the load module library (JOBLIB or STEPLIB) where the load module is loaded and the listing\ndata set containing the module listing must be under the control of Endevor .\nFollow these steps:\n1.Specify the option NDVRDSS=ON in your installation options table CAOUDFRX using the CAIOPTS DD statement, or\nin the SYM Option 5 panel.\n2.Designate a PROTSYM file to receive the dynamic populated symbolic using the NDVRDSN option.\nThe designated PROTSYM file can be any existing PROTSYM file and is searched ahead of all other PROTSYM files\nspecified.\nWhen the dynamic symbolic support feature is activated, it loads the correct symbolic information whenever a matching\nsymbolic version is not found.\nYou can reload the symbolic files associated with programs that do not contain a time stamp in the executable, such as\nnon-LE-enabled Assembler programs, every time they are printed or viewed. You can activate this behavior using the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3fe99257f468-1", "text": "additional option NDVRASM=ON. Default is not to refresh the symbolic. This option, when suppressed (NDVRASM=OFF),\nnever refreshes the symbolic of a non-LE-enabled Assembler program.\nNOTE\nThe dynamic symbolic support feature cannot differentiate between multiple listing outputs created by a single\nEndevor  processor for the same element. Thus, dynamic symbolic support using listing outputs from multiple\ncompiles or assemblies from a single Endevor  GENERATE or MOVE action for the same element may produce\nunpredictable results.\nDynamic Symbolic Support Return Codes\nDynamic symbolic support provides an integrated service using API calls that deploy various proven components\nincluding Endevor , PROTSYM post processors, z/OS dynamic allocation, CSVQUERY, and binder services.\nFor specific information about the return codes, see message CAPU309E in Messages and Codes.\nC1DEFLTS Consideration\nFollowing are the considerations for single and multiple C1DEFLTS:\n\u2022Single C1DEFLTS -- In an Endevor  single C1DEFLTS environment, dynamic symbolic support invokes Endevor  API\ndirectly, provided the C1DEFLTS data set and Endevor  AUTHLIB and CONLIB data sets are in the LNKLIST.\n\u2022Multiple C1DEFLTS -- In an Endevor  multiple C1DEFLTS environment, dynamic symbolic support normally invokes\nEndevor  API through a listing server dedicated to a unique C1DEFLTS. For more information, see Installing.\n 912", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e329fbb70d85-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTroubleshooting\nThis section contains information about identifying and resolving problems.\nCollect Diagnostic Data\nExecution-Time Problems\nGather the following information on the execution environment:\n\u2022In an Online Data Communication environment, the name of the package (if it is not an in-house developed product),\nthe version/release and maintenance level, and a vendor contact, if available.\n\u2022Non-COBOL programs being invoked by the program. Assembler language subroutines may be of interest to us in\nresolving the problem. Have the source available.\n\u2022The CAIPRINT report, if applicable.\nFormatting Problems\nGather the following documentation:\n\u2022Print the member listing from the PROTSYM or CSL file. See examples later in this section for more information. For\nsome problems, you may also be required to unload one or more members from a PROTSYM file using the batch\nutility IN25UTIL. For more information about unloading members with IN25UTIL, see Symbolic Support.\n\u2022Use IDCAMS REPRO to create a sequential file of your central VSAM repository. (If the repository is very large or you\nonly want to send the data for a single report, you can copy the report to a temporary repository and REPRO that file.)\nSee Copying Repository Data for Diagnostic Purposes.\n\u2022For clients that do not use the repository, Broadcom Support  may require the unformatted data used to generate the\nreport. To provide that data, you will need to add the following DD to your execution time JCL and rerun the job:\n //CAIPRTWK DD DSN=data-set-name,DISP=(NEW,CATLG,CATLG),\n //           UNIT=SYSDA,SPACE=(CYL,(1,1)),", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e329fbb70d85-1", "text": "//           UNIT=SYSDA,SPACE=(CYL,(1,1)),             \n //           DCB=(LRECL=133,BLKSIZE=13300,RECFM=FBA)  \n \nThe data set can then be sent to Broadcom  as a BINARY file.\nSymbolic Postprocessors\nReview all output from the postprocessor for error messages. If any messages are found, locate the message in Symbolic\nSupport, then review the reason and suggested action(s).\nGather the following documentation:\n\u2022All output from the postprocessor\n\u2022The listing file used as input to the postprocessor\nFor all problems, gather:\n\u2022The full IBM system SYSUDUMP if an abend has occurred. Although there are other products that, like SymDump\nBatch, produce very neat, easy-to-read, condensed dumps appropriate for debugging user programs, they generally\ndo not contain enough information for our purposes.\n\u2022All JCL, JOBLOG information, and messages for the job that ended in error.\n\u2022You may occasionally encounter a problem involving a COBOL program purchased from another vendor that is\nconsidered proprietary. While you are usually allowed to send the source listing on paper, you may not be permitted\nto send it on tape. Check. Arrangements can usually be made, including the signing of nondisclosure agreements by\nBroadcom .\n 913", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c2acf7665b46-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterpret Diagnostic Data\nWhen you have collected the specified diagnostic data, write down your answers to the following questions:\n1.What was the sequence of events prior to the error condition?\n2.What circumstances existed when the problem occurred and what action did you take?\n3.Has this situation occurred before? What was different then?\n4.Did the problem occur after a particular PTF was applied or after a new version of the software was installed?\n5.Have you recently installed a new version of the operating system or Language Environment (LE)?\n6.Has the hardware configuration (tape drives, disk drives, and so forth) changed?\nFrom your response to these questions and the diagnostic data, try to identify the cause and resolve the problem.\nPrint a Symbolic File Member for Diagnostic Purposes\nThere are two ways to print a symbolic file member or symbolic file directory. Either method is adequate for diagnostic\npurposes.\nUse the Viewer\nFollow these steps:\n1.Start the SymDump  Batch Repository Viewer the way you normally do.\n2.Enter the SYM primary command.\nThe Symbolic Utilities menu is displayed.\n3.Select Option 1 (List) and type the name of your PROTSYM or CSL file in the field provided.\n4.Press Enter to list the contents of your symbolic file\n5.Use the PRINT primary command to print a copy of the display to a printer, file, or other desired destination.\n6.After the directory is printed, type the p line command next to any member to print that member.\nUse the Batch Utilities\nSample JCL is provided for three utility programs that can be used to display the contents of your symbolic files:\n\u2022CAOUCSLD -- Use this program to generate a member list for your CSL library.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c2acf7665b46-1", "text": "\u2022CAOUCSLD -- Use this program to generate a member list for your CSL library.\n\u2022CAORMAIN -- Use the PRINTCSL function of CAORMAIN to print a member from your CSL library.\n\u2022IN25UTIL -- Use the REPORT function of IN25UTIL to generate a list of symbolic members in your PROTSYM and use\nthe PRINT function to print a symbolic listing for any member.\nCopy Repository Data for Diagnostic Purposes\nBroadcom Support  may require the data for one or more reports in your CAIPRINT repository for diagnostic purposes. To\nprovide that data, you must create a sequential data set from your VSAM repository.\nIf your CAIPRINT repository is very large, or you only want to send the data for selected reports, you can use the following\nsteps:\n1.Create a temporary VSAM repository.\n2.Copy the required reports to that repository.\n3.Create a sequential data set from the temporary repository.\nOtherwise, if you want to send the data for all reports, you can skip directly to Step 3. Create a Sequential Data Set\nfrom a VSAM Repository.\n 914", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b942ced9d3f9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCreate a Temporary VSAM Repository\nMember CARXREPO in the CAI.CAVHJCL library contains JCL to create and initialize a CAIPRINT repository.\nFollow these steps:\n1.Make a copy of the JCL member and modify the appropriate fields, such as the data set name, space, and volume.\n(Ensure to change the data set name in both the CLUSTER and DATA definitions.)\n2.Submit the JCL to create your temporary repository.\nCopy the Report to a Temporary VSAM Repository\nUse the COPY command of the CAIPRINT Repository Utility, CAOUPRTU, to copy one or more reports from your central\nVSAM repository to the temporary repository you just created.\nFor example, the following JCL copies the report for job TESTJOB from the central VSAM repository (CAI.PRTLIB) to a\ntemporary VSAM repository (TEMP.PRTLIB).\n// EXEC CAIPRTU\n//PRTU.SYSIN DD * \n  ODSN  CAI.PRTLIB\n   DSN   TEMP.PRTLIB\n   COPY  JOB EQ TESTJOB\n/*\nNOTE\nIf there is more than one report in the central VSAM repository with a job name of TESTJOB, the example above\ncopies all of the reports by that name.\nCreate a Sequential Data Set from a VSAM Repository\nUse IDCAMS REPRO to create a sequential file from your VSAM repository. For example, the following JCL creates a\nsequential file (TEMP.PRTLIB.BACKUP) from a temporary VSAM repository (TEMP.PRTLIB).\n//REPRO    EXEC PGM=IDCAMS\n//PRTLIB   DD  DSN=TEMP.PRTLIB,DISP=SHR", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b942ced9d3f9-1", "text": "//PRTLIB   DD  DSN=TEMP.PRTLIB,DISP=SHR\n//BACKUP   DD  DSN=TEMP.PRTLIB.BACKUP,DISP=(NEW,CATLG),\n//             UNIT=SYSDA,VOL=SER=vvvvvv,SPACE=(CYL,(3,3),RLSE),\n//             DCB=(RECFM=FB,LRECL=4085,BLKSIZE=4085)\n//SYSPRINT DD  SYSOUT=*\n//SYSIN    DD  *\n REPRO INFILE(PRTLIB) OFILE(BACKUP)\n/*\nUsing the Batch REST API\nUse the SymDump Batch REST Application Programming Interface (API) to perform the following actions:\n 915", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b3f147836554-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Display a report list\n\u2022Retrieve a report with index\n\u2022Lock a report\n\u2022Unlock a report\n\u2022Delete a report\n\u2022Display installation options\n\u2022Update Report Options\n\u2022Display Report Options\nFor instructions about how to install the SymDump  REST API, see Install Testing Tools Server and REST API.\nExample Use Cases\nAs a developer or DevOps admin, you can use the SymDump Batch REST API for the following actions:\nReports\nDisplays a list of ABEND reports\nFull Dump with index\nRetrieves an ABEND analysis report with an index\nLOCK\nLocks an ABEND report to prevent accidental deletion\nUNLOCK\nUnlocks an ABEND report to allow deletion\nDELETE\nDeletes an ABEND report\nOPTIONS\nDisplays the current product installation options\nREPORT OPTIONS\nDisplays and updates the current ABEND report options\nAuthentication\nREST API communication is secured through the HTTP or HTTPS protocol. To authenticate, the REST API server uses\nthe Basic authentication type and the mainframe username and password.\nTroubleshoot Errors\nFor errors that occur during request processing, the API returns an HTTP status code to the calling client. An error is\nindicated by a 4nn code or a 5nn code. For example:\nStatus: 400 Bad Request.\nSome errors might include a JSON object/response that contains a message with a description of the error. Use this\ninformation to diagnose the error.\nThis section contains the detailed API documentation in JSON format.\nPlease refer to the online format for OpenAPI content.\nBatch REST API: Reports\nUse the SymDump Batch REST API reports endpoint to display a report list.\n 916", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f9fd6691babb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nHTTP Method and URI Path\nThe SymDump Batch REST API URI path for the Reports endpoint has the following format:\nGET   http://host:port/symdump/api/v1/batch/prtlib/{prtlib}/reports\nWhere:\nhost\nSpecifies the address of the server that runs the REST API\nport\nSpecifies the port of the server that runs the REST API\nPRTLIB\nSpecifies the dump repository data set name\nHeaders\nAuthorization: Basic Auth with mainframe username and password\nExample:  Retrieve a report list.\nGET /symdump/api/v1/batch/prtlib/CAI.PRTLIB/reports\nREST API Response and Return Codes\nExpected Response\nOn completion, the service returns an HTTP response. This response includes a status code that indicates whether the\nrequest completed. The status code 200 OK  indicates success.\nExample:\n{\n  \"data\": [\n    {\n      \"abend\": \"string\",\n      \"date\": \"string\",\n      \"jobName\": \"string\",\n      \"key\": \"string\",\n      \"lock\": \"string\",\n      \"offset\": \"string\",\n      \"program\": \"string\",\n      \"stepName\": \"string\",\n      \"system\": \"string\",\n      \"time\": \"string\",\n      \"userID\": \"string\"\n    }\n  ],\n  \"messages\": [\n    {\n      \"messageContent\": \"string\",\n      \"messageNumber\": \"string\",\n      \"messageType\": \"string\"\n    }\n  ],\n  \"metadata\": [\n    {\n      \"messageTime\": \"string\",\n 917", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "409fdd1bf725-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n      \"messageVersion\": \"string\",\n      \"serviceName\": \"string\",\n      \"sessionID\": \"string\"\n    }\n  ]\n}\nBatch REST API: Full Dump with Index\nUse the SymDump Batch REST API full dump with index endpoint to retrieve a report.\nHTTP Method and URI Path\nThe SymDump Batch REST API URI path for the full dump with index endpoint has the following format:\nGET   http://host:port/symdump/api/v1/batch/prtlib/{prtlib}/reports/{key}/full-dump-with-index\nWhere:\nhost\nSpecifies the address of the server that runs the REST API\nport\nSpecifies the port of the server that runs the REST API\nPRTLIB\nSpecifies the dump repository data set name\nKey\nReport key used to locate a particular report from the report list\nHeaders\nAuthorization: Basic Auth with mainframe username and password\nRequest Body\nSupply a JSON request document (Content-Type=application/json, character-encoding=UTF-8) with the following input\nparameters:\nprotsymList\nList of PROTSYM data set names\nndvrDSSdsn\nThe data set name of a PROTSYM file that is designated as the receiver of Dynamic Symbolic Support auto\npopulation. Specify this parameter to activate Dynamic Symbolic Support for Endevor .\nndvrDSSasm\nActivate or deactivate auto population for non-LE enabled ASSEMBLER programs\nValues: Y, N\nExample:  Retrieve a report\n \nGET/symdump/api/v1/batch/prtlib/CAI.PRTLIB/reports/{key}/full-dump-with-index    \n      {\n  \"options\": {\n    \"ndvrDSSdsn\": \"CAI.ENDV.PROTSYM\",\n    \"ndvrDSSasm\": \"Y\"\n  },", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "409fdd1bf725-1", "text": "\"ndvrDSSasm\": \"Y\"\n  },\n 918", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b59fd1d6091e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  \"protsymList\": [\n    \"CAI.D1.PROTSYM\",\n    \"CAI.D2.PROTSYM\"\n  ]\n}\nREST API Response and Return Codes\nExpected Response\nOn completion, the service returns an HTTP response. The response includes a status code that indicates whether the\nrequest completed. The status code 200 OK  indicates success.\nExample:\n{\n  \"data\": \"string\",\n  \"dump\": {\n    \"abend\": \"string\",\n    \"date\": \"string\",\n    \"jobName\": \"string\",\n    \"key\": \"string\",\n    \"lock\": \"string\",\n    \"offset\": \"string\",\n    \"program\": \"string\",\n    \"stepName\": \"string\",\n    \"system\": \"string\",\n    \"time\": \"string\",\n    \"userID\": \"string\"\n  },\n  \"index\": [\n    {\n      \"children\": [\n        \"string\"\n      ],\n      \"description\": \"string\",\n      \"lineNo\": \"string\"\n    }\n  ],\n  \"messages\": [\n    {\n      \"messageContent\": \"string\",\n      \"messageNumber\": \"string\",\n      \"messageType\": \"string\"\n    }\n  ],\n  \"metadata\": [\n    {\n      \"messageTime\": \"string\",\n      \"messageVersion\": \"string\",\n      \"serviceName\": \"string\",\n      \"sessionID\": \"string\"\n    }\n  ]\n}\n 919", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aa2cda1e480f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBatch REST API: Lock\nUse the SymDump Batch REST API Lock endpoint to lock a report.\nHTTP Method and URI Path\nThe SymDump Batch REST API URI path for the Lock endpoint has the following format:\nPOST   http://host:port/symdump/api/v1/batch/prtlib/{prtlib}/reports/{key}/lock\nWhere:\nhost\nSpecifies the address of the server that runs the REST API\nport\nSpecifies the port of the server that runs the REST API\nPRTLIB\nSpecifies the dump repository data set name\nKey\nReport key used to locate a particular report from the report list\nHeaders\nAuthorization: Basic Auth with mainframe username and password\nExample:  Lock a report:\nPOST /symdump/api/v1/batch/prtlib/CAI.PRTLIB/reports/{key}/lock\nREST API Response and Return Codes\nExpected Response\nOn completion, the service returns an HTTP response. The response includes a status code that indicates whether the\nrequest completed. The status code 200 OK  indicates success.\nExample:\n{\n  \"dump\": {\n    \"abend\": \"string\",\n    \"date\": \"string\",\n    \"jobName\": \"string\",\n    \"key\": \"string\",\n    \"lock\": \"string\",\n    \"offset\": \"string\",\n    \"program\": \"string\",\n    \"stepName\": \"string\",\n    \"system\": \"string\",\n    \"time\": \"string\",\n    \"userID\": \"string\"\n  },\n  \"messages\": [\n    {\n      \"messageContent\": \"string\",\n      \"messageNumber\": \"string\",\n      \"messageType\": \"string\"\n 920", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f0d5be6b3e4f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    }\n  ],\n  \"metadata\": [\n    {\n      \"messageTime\": \"string\",\n      \"messageVersion\": \"string\",\n      \"serviceName\": \"string\",\n      \"sessionID\": \"string\"\n    }\n  ]\n}\nBatch REST API: Unlock\nUse the SymDump Batch REST API Unlock endpoint to unlock a report.\nHTTP Method and URI Path\nThe SymDump Batch REST API URI path for the Unlock endpoint has the following format:\nPOST   http://host:port/symdump/api/v1/batch/prtlib/{prtlib}/reports/{key}/unlock\nWhere:\nhost\nSpecifies the address of the server that runs the REST API\nport\nSpecifies the port of the server that runs the REST API\nPRTLIB\nSpecifies the dump repository data set name\nKey\nReport key used to locate a particular report from the report list\nHeaders\nAuthorization: Basic Auth with mainframe username and password\nExample:  Unlock a report:\nPOST /symdump/api/v1/batch/prtlib/CAI.PRTLIB/reports/{key}/unlock\nREST API Response and Return Codes\nExpected Response\nOn completion, the service returns an HTTP response. The response includes a status code that indicates whether the\nrequest completed. The status code 200 OK  indicates success.\nExample:\nExample:\n \n{\n  \"dump\": {\n    \"abend\": \"string\",\n    \"date\": \"string\",\n    \"jobName\": \"string\",\n 921", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ee887df0b710-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    \"key\": \"string\",\n    \"lock\": \"string\",\n    \"offset\": \"string\",\n    \"program\": \"string\",\n    \"stepName\": \"string\",\n    \"system\": \"string\",\n    \"time\": \"string\",\n    \"userID\": \"string\"\n  },\n  \"messages\": [\n    {\n      \"messageContent\": \"string\",\n      \"messageNumber\": \"string\",\n      \"messageType\": \"string\"\n    }\n  ],\n  \"metadata\": [\n    {\n      \"messageTime\": \"string\",\n      \"messageVersion\": \"string\",\n      \"serviceName\": \"string\",\n      \"sessionID\": \"string\"\n    }\n  ]\n}\nBatch REST API: Delete\nUse the SymDump Batch REST API Delete endpoint to delete a report.\nHTTP Method and URI Path\nThe SymDump Batch REST API URI path for the Delete endpoint has the following format:\nDELETE   http://host:port/symdump/api/v1/batch/prtlib/{prtlib}/reports/{key}\nWhere:\nhost\nSpecifies the address of the server that runs the REST API\nport\nSpecifies the port of the server that runs the REST API\nPRTLIB\nSpecifies the dump repository data set name\nKey\nReport key used to locate a particular report from the report list\nHeaders\nAuthorization: Basic Auth with mainframe username and password\nExample:  Delete a report:\nDELETE /symdump/api/v1/batch/prtlib/CAI.PRTLIB/reports/{key}\n 922", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8abbdbc0beb6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nREST API Response and Return Codes\nExpected Response\nOn completion, the service returns an HTTP response. The response includes a status code that indicates whether the\nrequest completed. The status code 200 OK  indicates success.\nExample:\n{\n  \"dump\": {\n    \"abend\": \"string\",\n    \"date\": \"string\",\n    \"jobName\": \"string\",\n    \"key\": \"string\",\n    \"lock\": \"string\",\n    \"offset\": \"string\",\n    \"program\": \"string\",\n    \"stepName\": \"string\",\n    \"system\": \"string\",\n    \"time\": \"string\",\n    \"userID\": \"string\"\n  },\n  \"messages\": [\n    {\n      \"messageContent\": \"string\",\n      \"messageNumber\": \"string\",\n      \"messageType\": \"string\"\n    }\n  ],\n  \"metadata\": [\n    {\n      \"messageTime\": \"string\",\n      \"messageVersion\": \"string\",\n      \"serviceName\": \"string\",\n      \"sessionID\": \"string\"\n    }\n  ]\n}\nBatch REST API: Options\nUse the SymDump Batch REST API Options endpoint to display installation options.\nHTTP Method and URI Path\nThe SymDump Batch REST API URI path for the options endpoint has the following format:\nGET  http://host:port/symdump/api/v1/batch/options\nWhere:\nhost\nSpecifies the address of the server that runs the REST API\nport\nSpecifies the port of the server that runs the REST API\n 923", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "04500cc29599-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nHeaders\nAuthorization: Basic Auth with mainframe username and password\nExample:  Display installation options:\nPOST /symdump/api/v1/batch/options \nREST API Response and Return Codes\nExpected Response\nOn completion, the service returns an HTTP response. The response includes a status code that indicates whether the\nrequest completed. The status code 200 OK  indicates success.\nExample:\n{\n   \"data\":\"string\",\n   \"messages\":[\n      {\n         \"messageContent\":\"string\",\n         \"messageNumber\":\"string\",\n         \"messageType\":\"string\"\n      }\n   ],\n   \"metadata\":[\n      {\n         \"messageTime\":\"string\",\n         \"messageVersion\":\"string\",\n         \"serviceName\":\"string\",\n         \"sessionID\":\"string\"\n      }\n   ]\n}\nBatch REST API: Display Report Options\nUse the SymDump Batch REST API Display Report endpoint to display formatting options for a report.\nHTTP Method and URI Path\nThe SymDump Batch REST API URI path for the Display Report endpoint has the following format:\nGET \nhttp://host:port/symdump/api/v1/batch/prtlib/{prtlib}/reports/{key}/options\nWhere:\nhost\nSpecifies the address of the server that runs the REST API\nport\nSpecifies the port of the server that runs the REST API\nPRTLIB\nSpecifies the dump repository data set name\nPKey\nReport key used to locate a particular report from the report list\n 924", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "44bdb63ada12-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nHeaders\nAuthorization: Basic Auth with mainframe username and password\nExample:  Display a report:\nGET /symdump/api/v1/batch/prtlib/CAI.PRTLIB\n/reports/{key}/options\nREST API Response and Return Codes\nExpected Response\nOn completion, the service returns an HTTP response. The response includes a status code that indicates whether the\nrequest completed. The status code 200 OK indicates success.\n{\n  \"displayOptions\": {\n    \"asminst\": \"ON\",\n    \"files\": \"ON\",\n    \"first128\": \"ON\",\n    \"linecnt\": \"60\",\n    \"linkage\": \"ON\",\n    \"listline\": \"10\",\n    \"localstor\": \"ON\",\n    \"memmap\": \"ON\",\n    \"rptsz80\": \"ON\",\n    \"savearea\": \"ON\",\n    \"showheap\": \"ON\",\n    \"workstor\": \"ON\"\n  },\n  \"dump\": {\n    \"abend\": \"string\",\n    \"date\": \"string\",\n    \"jobName\": \"string\",\n    \"key\": \"string\",\n    \"lock\": \"string\",\n    \"offset\": \"string\",\n    \"program\": \"string\",\n    \"stepName\": \"string\",\n    \"system\": \"string\",\n    \"time\": \"string\",\n    \"userID\": \"string\"\n  },\n  \"mergingOptions\": {\n    \"binfrmt\": \"HEX\",\n    \"grpaddr\": \"ON\",\n    \"mergedb\": \"ON\",\n    \"mrgauto\": \"ON\",\n    \"mrgbased\": \"ON\",\n    \"mrgcntld\": \"ON\",", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "44bdb63ada12-1", "text": "\"mrgbased\": \"ON\",\n    \"mrgcntld\": \"ON\",\n    \"mrgdsect\": \"ON\",\n    \"mrgfiles\": \"ON\",\n    \"mrglink\": \"ON\",\n    \"mrglocal\": \"ON\",\n 925", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "42e22153c616-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    \"mrgparms\": \"ON\",\n    \"mrgstat\": \"ON\",\n    \"mrgwork\": \"ON\",\n    \"occurs\": \"MAX\",\n    \"showunmrg\": \"ON\"\n  },\n  \"messages\": [\n    {\n      \"messageContent\": \"string\",\n      \"messageNumber\": \"string\",\n      \"messageType\": \"string\"\n    }\n  ],\n  \"metadata\": [\n    {\n      \"messageTime\": \"string\",\n      \"messageVersion\": \"string\",\n      \"serviceName\": \"string\",\n      \"sessionID\": \"string\"\n    }\n  ]\n}\nBatch REST API: Update Report Options\nUse the SymDump Batch REST API Update Report endpoint to update options for a report.\nHTTP Method and URI Path\nThe SymDump Batch REST API URI path for the Update Report Options endpoint has the following format:\n      POST \n      http://host:port/symdump/api/v1/batch/prtlib/{prtlib}/reports/{key}/options\nWhere:\nhost\nSpecifies the address of the server that runs the REST API\nport\nSpecifies the port of the server that runs the REST API\nPRTLIB\nSpecifies the dump repository data set name\nKey\nReport key used to locate a particular report from the report list\nHeaders\nAuthorization: Basic Auth with mainframe username and password\n 926", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e05d37cea014-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nRequest Body\nSupply a JSON request document (Content-Type=application/json, character-encoding=UTF-8) with the following input\nparameters:\nDisplay Options:\nAsminst\nDisplays the abending assembler instruction\nValues: ON, OFF\nFiles\nDisplays the Open Files report\nValues: ON, OFF\nFirst128\nDisplays only the first 128 bytes of each record\nValues: ON, OFF\nLinecnt\nSpecifies the number of lines on formatted pages\nValues: A numeric Value\nLinkage\nDisplays the Linkage Section for COBOL programs\nValues: ON, OFF\nListline\nSpecifies the number of additional source lines to display before and after the abending (or snap) statement\nValues:\nLocalstor\nDisplays Local Storage for COBOL programs\nValues: ON, OFF\nMemmap\nDisplays the TGT, DSA, and PGT memory maps\nValues: ON, OFF\nRptsz80\nSpecifies to format using 80-byte output when possible\nValues: ON, OFF\nSavearea\nDisplays the Save Area Trace report\nValues: ON, OFF\nShowheap\nDisplays LE or PL/I heap storage\nValues: ON, OFF\nWorkstor\nDisplay the Working Storage for COBOL programs\nValues: ON, OFF\nMerging Options:\nBinfrmt\nSpecifies how to display binary values\nValues: DEC (Decimal), HEX (Hexadecimal)\n 927", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "16f0ac3e53a0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nGrpaddr\nSpecifies whether to display the base locator, displacement, and address of a group item on the merged Data\nDivision displays\nValues: ON, OFF\nMergedb\nSpecifies whether to merge symbolic name into Database reports\nValues: ON, OFF\nMrgauto\nSpecifies whether to merge symbolic names into PL/I automatic storage\nValues: ON, OFF\nMrgbased\nSpecifies whether to merge symbolic names into PL/I based variable storage\nValues: ON, OFF\nMrgcntld\nSpecifies whether to merge symbolic names into PL/I controlled storage.\nValues: ON, OFF\nMrgdsect\nSpecifies whether to merge symbolic names into Assembler DSECT storage\nValues: ON, OFF\nMrgfiles\nSpecifies whether to merge symbolic names into the File Section for COBOL\nValues: ON, OFF\nMrglink\nSpecifies whether to merge symbolic names into the Linkage Section for COBOL\nValues: ON, OFF\nMrglocal\nSpecifies whether to merge symbolic names into Local Storage for COBOL\nValues: ON, OFF\nMrgparms\nSpecifies whether to merge symbolic names into PL/I parameter storage.\nValues: ON, OFF\nMrgstat\nSpecifies whether to merge symbolic names into PL/I static storage\nValues: ON, OFF\nMrgwork\nSpecifies whether to merge symbolic names into Working Storage for COBOL\nValues: ON, OFF\nOccurs\nSpecifies the number of table elements to display for each array\nValues: MAX, a numeric value\nShowunmrg\nDisplays storage for unmerged data\nValues: OFF, ON, TBLS\nExample:  Update a report:\nPOST /symdump/api/v1/batch/prtlib/CAI.PRTLIB\n/reports/{key}/options\n 928", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "65d13bc18c4d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n{\n    \"displayOptions\": {\n        \"asminst\": \"ON\",\n        \"files\": \"ON\",\n        \"first128\": \"OFF\",\n        \"linecnt\": \"60\",\n        \"linkage\": \"ON\",\n        \"listline\": \"0\",\n        \"localstor\": \"ON\",\n        \"memmap\": \"ON\",\n        \"rptsz80\": \"OFF\",\n        \"savearea\": \"ON\",\n        \"showheap\": \"OFF\",\n        \"workstor\": \"ON\"\n    },\n    \"mergingOptions\": {\n        \"binfrmt\": \"DEC\",\n        \"grpaddr\": \"ON\",\n        \"mergedb\": \"ON\",\n        \"mrgauto\": \"ON\",\n        \"mrgbased\": \"ON\",\n        \"mrgcntld\": \"ON\",\n        \"mrgdsect\": \"ON\",\n        \"mrgfiles\": \"ON\",\n        \"mrglink\": \"ON\",\n        \"mrglocal\": \"ON\",\n        \"mrgparms\": \"ON\",\n        \"mrgstat\": \"ON\",\n        \"mrgwork\": \"ON\",\n        \"occurs\": \"1\",\n        \"showunmrg\": \"TBLS\"\n    }\n}\nREST API Response and Return Codes\nExpected Response\nOn completion, the service returns an HTTP response. This response includes a status code that indicates whether the\nrequest completed. The status code 200 OK indicates success.\nExample:\n{\n  \"dump\": {\n    \"abend\": \"string\",\n    \"date\": \"string\",\n    \"jobName\": \"string\",\n    \"key\": \"string\",\n    \"lock\": \"string\",", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "65d13bc18c4d-1", "text": "\"key\": \"string\",\n    \"lock\": \"string\",\n    \"offset\": \"string\",\n    \"program\": \"string\",\n    \"stepName\": \"string\",\n    \"system\": \"string\",\n 929", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5551e4ccfb74-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    \"time\": \"string\",\n    \"userID\": \"string\"\n  },\n  \"messages\": [\n    {\n      \"messageContent\": \"string\",\n      \"messageNumber\": \"string\",\n      \"messageType\": \"string\"\n    }\n  ],\n  \"metadata\": [\n    {\n      \"messageTime\": \"string\",\n      \"messageVersion\": \"string\",\n      \"serviceName\": \"string\",\n      \"sessionID\": \"string\"\n    }\n  ]\n}\nUsing CICS Tools\nInterTest for CICS is an interactive tool for testing and debugging CICS COBOL, PL/I, and Assembler programs.\nInterTest for CICS\nTesting and debugging are the most time consuming and important phases of application development. The interactive\ntesting facilities of InterTest for CICS dramatically improve testing efficiency and application quality. InterTest for CICS\nworks online to trap all known CICS application errors. You can resolve multiple errors interactively as the errors occur\nwithout having to recompile or end the test session.\nSymDump  for CICS\nSymDump  for CICS is a powerful online tool that brings application dumps back to life. SymDump  for CICS improves\nyour ability to analyze and resolve application program problems. Ideally, you could monitor every program and catch\nevery error with a product like InterTest for CICS. Realistically, this scenario is not possible because of overhead or\nbecause you may not want to monitor security programs or programs using nonstandard code. As a result, dumps occur,\nespecially in production where even a thoroughly debugged program abends because of bad data, scheduling errors,\ninvalid parameters, and other factors beyond programmer control.\nHelp File Printout", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5551e4ccfb74-1", "text": "invalid parameters, and other factors beyond programmer control.\nHelp File Printout\nThe InterTest for CICS Help file contains extensive tutorial information that is available to you online by entering HELP  or\npressing PF1 from any InterTest for CICS screen. The file has a browse capability from any point of access. You can print\nthe Help file once it is loaded from the distribution tape using the JCL in the following examples. The program prints one\nscreen image per page. The input to the program is the VSAM KSDS file that was loaded from the distribution tape.\n\u2022The printout is formatted as 81-byte fixed-length records. The first byte contains the ANSI print control character, such\nas 1 for new page or a plus sign (+) to overprint the same line.\n\u2022The file is produced in uppercase and lowercase to enhance readability.\n\u2022The output is over 1000 pages.\n\u2022If your printer cannot handle lowercase characters, specify PARM=UPPER in the EXEC statement of the JCL.\n 930", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "04a07f0cef82-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSample MVS JCL to Print the Help File\nUse the following MVS JCL to print the Help file.\n//PRINHELP JOB.... \n//STEP1 EXEC PGM=IN25PRIH,REGION=256K  \n//STEPLIB DD DSN=YOUR.INTRTST.LOADLIB,DISP=SHR\n//PROTHLF DD DSN=INTRTSTV.PROTHLF,DISP=SHR \n//OUTPUT DD SYSOUT=A\n//\nCICS Debugging\nInterTest for CICS Product Features\nInterTest for CICS is an interactive testing and debugging product for CICS applications written in COBOL, PL/1, and\nAssembler. Specific compilers support includes:\n\u2022Assembler\n\u2022COBOL\n\u2022COBOL II\n\u2022COBOL/370\n\u2022COBOL II or COBOL/370 with Optimizer/II\n\u2022IBM Enterprise COBOL for z/OS\n\u2022PL/1\n\u2022PL1/370\n\u2022PL/1 for MVS\n\u2022IBM Enterprise PL/1 for z/OS\nInterTest for CICS is an essential tool for both application and system programmers:\n\u2022It makes CICS testing faster, easier, and more effective.\n\u2022It prevents CICS crashes by automatically detecting and preventing application errors before they damage CICS.\n\u2022It provides powerful capabilities for examining and modifying main and auxiliary storage.\nFast, Easy Testing\nThe primary function of InterTest for CICS is to help application programmers test and debug their programs quickly and\nefficiently. InterTest for CICS has many features that simplify testing, including:\n\u2022Interactive testing ability through the InterTest for CICS monitor\n\u2022Error detection and prevention\n\u2022Diagnostic information display screens\n\u2022Program interruption through setting breakpoints", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "04a07f0cef82-1", "text": "\u2022Error detection and prevention\n\u2022Diagnostic information display screens\n\u2022Program interruption through setting breakpoints\n\u2022Isolated test sessions through monitoring by CICS User ID\nInteractive Testing The InterTest for CICS Monitor\nInterTest for CICS allows interactive testing. When InterTest for CICS detects an error, you can correct it dynamically (or\ngo around it) and resume testing, allowing you to correct many errors in one test session.\nWith InterTest for CICS, you no longer need dumps. All the information you need to diagnose and correct errors is\navailable online. You can continue testing without recompiling your program or waiting for new printouts.\n 931", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dce5db2cc68d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterTest for CICS acts as an intermediary between your CICS program and the CICS system. Here is how InterTest for\nCICS operates:\n\u2022You instruct InterTest for CICS to monitor a program, and then run the program.\n\u2022InterTest for CICS inspects every instruction and CICS command before it executes to make sure neither the program\nnor CICS itself will fail.\n\u2022If an error is detected, InterTest for CICS automatically interrupts the program. This temporary interruption in program\nexecution is called a breakpoint .\n\u2022InterTest for CICS then displays a diagnostic screen explaining the nature of the problem and provides detailed\ntechnical information for correcting it.\nError Detection and Prevention\nInterTest for CICS detects and prevents errors before they occur. This means your programs will not abend. InterTest for\nCICS does not permit storage violations that could corrupt the data of other programs or cause CICS to fail.\nInterTest for CICS inspects every COBOL, PL/1 statement or Assembler instruction and every CICS Command. InterTest\nfor CICS can detect and prevent the following errors:\n\u2022All storage violations (attempts to modify storage not owned by your program)\n\u2022Any CICS abend that can occur in a command level program\n\u2022All improper or invalid CICS requests (Commands)\n\u2022Any statement that would cause a program check or other abend\n\u2022All illegal or invalid instructions (for example, STOP RUN)\n\u2022All wild branches\n\u2022All violations of CICS standards\nDiagnostic Information\nInterTest for CICS provides the information you need to diagnose and correct errors. When InterTest for CICS detects\nan error, it halts the program before the error occurs. This temporary halt in program execution is called an automatic", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dce5db2cc68d-1", "text": "breakpoint . InterTest for CICS then displays a screen of diagnostic information indicating the statement or instruction\ntriggering the breakpoint, and InterTest for CICS explains why the error occurred.\nThe breakpoint display explains why InterTest for CICS halted the program. The program instruction that triggered the\nbreakpoint is highlighted. You can use all of the InterTest for CICS facilities to find and correct the error without analyzing\na dump.\nInterrupt Programs by Setting Breakpoints\nTo help you test and debug CICS programs effectively, you can also interrupt program execution at any point by setting\nbreakpoints. You can set four types of breakpoints:\nUnconditional  -- the program stops when it reaches a specified location.\nConditional  -- the program stops when it reaches a specified location and a prescribed condition is met (for example, a\nvariable exceeds a certain limit).\nVariable-change -- the program stops at any location if the value of a specified variable has changed (COBOL and\nAssembler only).\nRequest  -- the program stops when it reaches specified CICS Commands, calls to DL/I or DB2, and calls to subroutines,\nsuch as database software.\nYou also can instruct InterTest for CICS to halt your program each time it executes a specified number of COBOL verbs,\nPL/1 statements, or Assembler instructions.\n 932", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d5e465acede5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nControlling the pace at which a program executes makes it easier to pinpoint and correct logic errors. For example, when\na program is halted, you can inspect the values of program variables and test data to determine whether processing is\nproceeding as planned. You can also dynamically change the value of a data item or generate additional test records\nbefore resuming execution.\nWhen a program is stopped at a breakpoint, you can resume execution at any time and from any point. This means you\ncan go around errors or dynamically alter the order in which certain routines are executed. When your program is halted at\na breakpoint, you can do the following tasks:\n\u2022View your program listing and compiler output online and search for a data string\n\u2022Display data items in a Keep window to observe changes in their values\n\u2022Display and modify main storage\n\u2022Display and modify auxiliary storage\n\u2022Set and remove breakpoints\n\u2022Instruct InterTest for CICS to halt the program after it executes a specified number of COBOL verbs, PL/1 statements,\nor Assembler instructions\n\u2022Write and execute indirect commands, which are statements you insert during a test session, without recompiling the\nsource code\n\u2022Display the path (backtrace) that brought the program to its current point\n\u2022Display the execution counts of the lines that brought the program to its current point\n\u2022Resume program execution or abend the task\n\u2022Initiate any CICS transaction\nStable CICS Test and Production Systems\nInterTest for CICS protects CICS test and production systems because it will not permit errors that could damage CICS.\nIn your test CICS system, you can instruct InterTest for CICS to inspect every program for errors. In addition to spotting\nprogram errors, InterTest for CICS detects and prevents all CICS storage violations. With InterTest for CICS, CICS test", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d5e465acede5-1", "text": "systems are less likely to crash, so programmers can work more productively. Additionally, program errors are confined\nto a single program -- other programs remain unaffected. Therefore, system throughput improves because trial and error\ntesting is eliminated, test programs need fewer recompiles, and CICS is much more stable.\nInterTest for CICS also helps maintain stable CICS production systems. Using InterTest for CICS in CICS test systems\nmeans programs are less likely to have bugs when they go into production. InterTest for CICS can also monitor new,\nmodified, and problem programs in production until they are completely debugged. In an emergency, InterTest for CICS\ncan even monitor all the programs in the production system until you isolate the error. Special options let you adapt\nInterTest for CICS to specific production situations.\nExamine and Modify Main and Auxiliary Storage\nInterTest for CICS has powerful facilities for examining and modifying main and auxiliary storage. You can take advantage\nof these facilities while testing a program. For example, you can interrupt program execution at various points to see how\nthe values of program variables and test data have changed. And, you can dynamically modify storage as your testing\nprogresses.\nExample\nYou can halt your program, change the value in a flag, initialize a counter, or change the data in a test record, and then\nresume execution -- all without recompiling.\nYou can inspect and modify main and auxiliary storage at any time -- even when no program is executing and InterTest\nfor CICS is otherwise inactive. System programmers can use InterTest for CICS to fine-tune CICS. They can display the\ncontents of CICS control blocks and tables in main storage, making changes as necessary.\n 933", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5e9f690a1ae9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterTest for CICS also makes it easy to maintain files online without writing one-time programs. You can use InterTest for\nCICS to add, update, and delete records in VSAM and BDAM files and DL/I, DB2 and SQL/DS databases. With InterTest\nfor CICS, it is easy to browse a file and search for a character string. InterTest for CICS also lets you create and delete\ntransient data and temporary storage records.\nGet HELP\nThe InterTest for CICS comprehensive Help facility is available from every InterTest for CICS screen. Online help explains\nhow to use all of the InterTest for CICS facilities, provides important information on diagnosing and correcting program\nerrors, and includes examples. You can access the Help facility by entering Help on a blank screen. Press PF1 to access\ncontext-sensitive help from any screen. For example, when InterTest for CICS halts your program at an automatic\nbreakpoint, you can press PF1 to get more information on the error that caused the breakpoint.\nUser-Defined Help for Abends\nYou can define your own abend codes and descriptions or replace the delivered abend descriptions with your own text.\nIf user-defined text is defined for an abend code, InterTest for CICS displays your site's help text instead of the delivered\nhelp text at an automatic breakpoint. For more information, see InterTest for CICS Options.\nOnline Access to Source Listings and Compiler Output\nWith InterTest for CICS, you never have to wait for printouts. InterTest for CICS provides online access to your source\nlistings and compiler output, such as maps, cross-reference tables, and messages -- information your online editor cannot\nprovide. Working directly from your source listing makes it easy to set breakpoints and display main storage.\nSymbolic Support", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5e9f690a1ae9-1", "text": "Symbolic Support\nInterTest for CICS lets you reference all program locations by the names you have defined in the program, so you\ncan forget about displacements or address changes after recompiling. You can inspect the contents of a data item simply\nby specifying its name. If you set breakpoints at symbolic locations and then recompile your program, InterTest for CICS\ncan transfer those breakpoints to the recompiled program. You can also access all CICS system-related areas by field\nnames. InterTest for CICS even provides full symbolic support for programs that consist of separately compiled modules\nbrought together when the program is link-edited. These modules can be written in the same or different languages.\nInterTest for CICS supports both PROTSYM and DWARF formats for debugging COBOL programs. For more information,\nsee Symbolic Support.\nInterTest for CICS Components\nInterTest for CICS consists of these CICS transactions:\nITST  \u2013 Displays the ISPF-like Primary Option Menu, which provides access to all other InterTest for CICS and SymDump\nfor CICS Option facilities without having to know any other transaction or command.\nLIST  -- Displays online COBOL, PL/1, and Assembler source listings and compiler output.\nCNTL  -- Controls program monitoring.\nCORE  -- Inspects and modifies main storage.\nFILE  -- Displays and updates CICS files, DL/I, DB2, and SQL/DS databases, temporary storage, or transient data.\nHELP  -- Provides online assistance for using InterTest for CICS.\nYou can use any of these transactions at any time. Your program does not have to be executing for you to use CORE to\ndisplay or change the contents of main storage, and you can use FILE to update a file or create a test file whether or not\nInterTest for CICS is monitoring any programs.\n 934", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9ca30f8b446a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDifferent Methods of Using InterTest for CICS\nNovice CICS programmers will learn to take advantage of the many features of InterTest for CICS because it is not\nnecessary to learn command syntax. Standard ISPF-like menus and selection screens make it easy to access any\ncomponent in InterTest for CICS at any time.\nThe ITST transaction displays the Primary Option Menu from which you can access any InterTest for CICS function.\nSpecially formatted displays and screens also enable you to bypass menu processing by using special commands or\nsingle keystrokes for the most frequently used testing functions. For example, you can instruct InterTest for CICS to set\nmonitoring, breakpoints or display main storage simply by pressing a PF key or entering a single action character next to a\nline in your source listing display. A command line on the top of any Source Listing or Breakpoint display lets you access a\nmain menu or a specific menu function by entering its fastpath syntax (=X.Y.Z).\nMore experienced users often find it faster to enter transaction-based commands for LIST, CNTL, CORE, and FILE\nfacilities directly.\nExample\nEntering LIST=COBDEMO directly from CICS immediately displays the Source Listing Display of the program\nCOBDEMO, where you can quickly set breakpoints before you begin executing the program.\nYou can also mix and match different methods during a single test session to meet your testing needs.\nMenus and Displays\nThis article explains how to use the ISPF-like menus and selection lists to get around InterTest for CICS before, during,\nand after your test sessions.\nThe menus are always available and use a standard set of PF keys.\nAdditional menu features include the following:\n\u2022Support a subset of ISPF commands, including the fast-path Jump (=x.y.z) command for quick navigation", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9ca30f8b446a-1", "text": "\u2022Simplify navigation among the Source Listing, Monitoring (CNTL), Main Storage (CORE), Auxiliary Storage (FILE), and\nSymDump  for CICS (SYMD) displays\nThis article also explains how to use the Monitoring Status display, an expandable tree-like display of current monitoring\nentries. You will find the Status display saves testing time, since you can quickly remove any monitoring, breakpoint, or\nmonitoring option directly from it.\nPrimary Option Menu\nThe menus offer easy access to the InterTest for CICS LIST, CNTL, CORE, FILE, and SYMD facilities. The Primary\nOption Menu is available at all times, even if you did not start the session from a menu. For example, if you started your\nInterTest for CICS session using LIST=COBDEMO, from the Source Listing Display you can still use PF6 Menu to display\nthe Primary Option Menu. If you used single-line commands to set monitoring and breakpoints for your program, and then\nexecute the program and reach a breakpoint, PF 6 Menu displays the Breakpoint Primary Option Menu and Option 1 Main\nMenu accesses the Primary Option Menu.\nTo access the Primary Option Menu, enter ITST from CICS, from any Source Listing display or breakpoint, or any\nInterTest for CICS menu.\n\u2022Before a test session, sign on to CICS, and then enter the ITST  transaction\n\u2022From any Source Listing display or breakpoint display, type ITST on the command line\n\u2022From the Breakpoint Primary Option Menu, type ITST or select option 1 Main Menu\nFollowing is a list of each menu option and the subsequent menu options that are available.\n\u2022Option 1 --  Source\n 935", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c477044ac10a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n1 -- Source listings\n2 -- Symbolic files\nSelecting options from this menu launches relevant source listing displays. (LIST=progname)\n\u2022Option 2 -- Monitoring\n1 -- Programs\n2 -- Transactions\n3 -- Terminals\n4 -- Status\n5 -- Active tasks\n6 -- System-wide\n7 -- Debugging sessions\nSelecting options from this menu launches relevant monitoring menus and CNTL menus and subsequent monitoring\nstatus displays.\n\u2022Option 3 -- Main Storage\n1 -- System Areas\n2 -- Task Areas\n3 -- Breakpoint Areas\nSelecting options from this menu launches relevant storage displays of CORE\n\u2022Option 4 -- Auxiliary Storage\n1 -- Files\n2 -- DB2 database\n3 -- DL/I database\n4 -- TS queues\n5 -- TD queues\nSelecting options from this menu launches relevant displays of FILE\n\u2022Option 5 -- SymDump\n1 -- Analysis\n2 -- Tracing\n3 -- Configuration\n4 -- Start\n5 -- Stop\n6 -- Source\n7 -- Status/Maintenance\n8 -- What's New?\nX -- Exit\nSelecting options from this menu launches relevant SymDump selection panels and displays\n\u2022Option 6 -- Product Help\nThis option launches the main menu for all help topics.\n\u2022Option 7 -- Status/Maintenance\n1 -- Product Status\n2 -- Abend Descriptions\nSelecting options from this menu launches relevant displays for programs, transactions, file statuses, global options,\nand symbolic file names for InterTest for CICS and SymDump  for CICS, as well as abend code maintenance panels.\n\u2022Option 8 -- What's New?\nThis option launches the portion of the help facility that describes the new product features.\n\u2022X -- Exit\nBreakpoint Primary Option Menu", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c477044ac10a-1", "text": "\u2022X -- Exit\nBreakpoint Primary Option Menu\nWhen you are at a breakpoint, InterTest for CICS includes a Breakpoint Primary Option Menu, from which you can access\nthe following options. Press PF6 to access the Breakpoint Primary Option menu.\n 936", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9fa9888d2662-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMain menu\nDisplay the InterTest primary option menu\nStatus\nDisplay or remove current monitoring options\nAbend\nAbend the breakpointed task\nResume\nResume breakpointed task menu options\nOverride\nOverride automatic breakpoint default processing\nDump\nCause dump, resume from next sequential instruction\nDisconnect\nDisconnect the breakpoint from this terminal\nHogan SMART\nInvoke Hogan System's debugging facility\nExit\nTerminate breakpoint menu processing\nOption Selection\nOption selection for the new menus follows standard ISPF conventions. To select a menu option, enter its number in the\nOption==> field and press Enter . If you have questions about menu usage, press PF1 for menu-specific help.\nFast-path Option Selection (=x.y.z)\nThe Option field of menus (and the command line of the Source Listing Facility) support the Jump (=x.y.z) command\nnotation, also known as fastpath notation. Jump notation lets you bypass intermediate menus by making a series of\nselections in the format x.y.z. The equal sign indicates your selection starts from the top level menu in the current\nhierarchy. If you do not include the equal sign, your selection starts from the current menu.\nFast-path Notation\nWhen a submenu to a Primary Option Menu is discussed in this article, its fast-path from the Primary Option Menu is\nwritten in parentheses following the menu name.\nExample\n ... Program Monitoring menu (2.1)...\nthe notation indicates that the Program Monitoring menu is option 2 Monitoring on the Primary Option Menu, and then\noption 1 Programs on the Monitoring Menu.\nPF Keys\nAll menus and selection lists have a standard set of PF keys.\nPF1 Help\nDisplays a Help menu relating to the current menu or display. At an automatic breakpoint, gives help for the\nspecific problem. Use Clear to exit help.\nPF3 End", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9fa9888d2662-1", "text": "specific problem. Use Clear to exit help.\nPF3 End\nEnds the current display and returns to the previous menu or display.\n 937", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e8f1fa617d8d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPF4 Return\nReturns to the highest level menu, either the Primary Option Menu or the Breakpoint Primary Option Menu.\nPF7 Backward\nScrolls a list back one page, or scrolls back to the list item indicated by the user's cursor.\nPF8 Forward\nScrolls a list forward one page, or scrolls down to the list item indicated by the user's cursor.\nSelection and Navigation Commands\nInterTest for CICS and the SymDump  for CICS support the following standard ISPF commands in the top OPTION==>\nline of menus and COMMAND ==> line of Selection Lists. These commands let you quickly navigate through screens with\nselection lists and tree structures.\nNOTE\nAll commands do not apply to all screens.\nExample\nEXPAND and COLLAPSE apply only to screens with tree structure displays, and LOCATE applies only to selection lists\ndisplayed in alphanumeric order.\nBACKWARD BWD\nSame as PF7, scrolls backwards or towards the top of the selection list.More: - (minus sign) indicates there are\nmore selections to view using PF7 or BACKWARD.\nBOTTOM\nBOT\nScrolls to the bottom of a selection list.\nCOLLAPSE\nSame as PF5 Collapse. Collapses a branch in a tree structure to show only the base entry. A minus sign in front\nof tree structure entry indicates the branch can be collapsed.\nDOWN\nSame as FORWARD.\nEND\nSame as PF3. Ends the current function and returns to the previous menu or display.\nEXPAND\nExpands a branch in a tree structure to show all related entries. A plus sign in front of a tree structure entry\nindicates the branch can be expanded.\nFORWARD\nFWD\nSame as PF8, scrolls the display list forward towards the bottom of the selection list. The More: + (plus) field", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e8f1fa617d8d-1", "text": "indicates there are more entries to view using PF8 or FORWARD. Use the cursor to go to an entry in the middle of\na display and press PF8 (Forward) to position that entry at the top of the display.\nHELP\nSame as PF1, displays help for the current screen. Once in the help facility, follow the help panel instructions to\naccess additional or related help topics. To exit help, use PF3 or Clear.\nLOCATE\nLOC\nL\nLocates a selection in a list based on the character string you enter. For example, LOC COBDEMO locates\nCOBDEMO in the current selection list. Accepts masking characters * and ?\n 938", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6f7f0664b1a2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMAIN\nSame as PF4 Return. Returns you to the highest level menu, such as the Primary Option Menu.\nREFRESH\nSame as PF2 Refresh. Refreshes or redraws the current display to reflect recent modifications. For example, after\nremoving options from a Monitoring Status display, use REFRESH to eliminate the removed entries from the tree\nview.\nRETURN\nSame as PF4 Return. Returns you to the highest level menu, such as the Primary Option Menu (before a test\nsession) or the Breakpoint Primary Option Menu (at a breakpoint).\nSELECT\nSEL\nS\nSelects an option on a menu.\nTERMINAL\nTERM\nDisplays the current Terminal ID.\nTIME\nDisplays the current time.\nTOP\nScrolls to the first entry in a selection list.\nUP\nSame as PF7, Backward.\nUSER\nDisplays the current CICS user ID.\nDiagnostic Information\nInterTest for CICS provides the information you need to diagnose and correct errors. When InterTest for CICS detects\nan error, it halts the program before the error occurs. This temporary halt in program execution is called an automatic\nbreakpoint . InterTest for CICS then displays a screen of diagnostic information indicating the statement or instruction\ntriggering the breakpoint, and InterTest for CICS explains why the error occurred.\nThe breakpoint display explains why InterTest for CICS halted the program. The program instruction that triggered the\nbreakpoint is highlighted. You can use all of the InterTest for CICS facilities to find and correct the error without analyzing\na dump.\nMonitoring Status Display\nThe Monitoring Status display shows you current monitoring, breakpoints and monitoring options in effect for one, or for all\nmonitoring entries.\nSample Status\nThe following screen is a sample Monitoring Status display for the program COB2DEMO. This example shows the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6f7f0664b1a2-1", "text": "expanded monitoring entry for the Program COB2DEMO.\n                     CA InterTest for CICS  MONITORING STATUS\nCOMMAND ===>                                                                   \n \n  Type + to expand or  collapse option levels displayed below,                \n         or R to remove option(s).                                            \n 939", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "212cac3f0240-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                                                      More:   +\n    Option     Description                Attributes                           \n_ COB2DEMO  Program monitor entry      COBOL II                             \n    |       Waiting at breakpoint      Task 00043, UBP since 08:48 a.m.    \n_   |.ANY   User monitoring options    Active                               \n_   |.ANY   User monitoring options    Deactivated                          \n     |      Symbolic listing file      PROTDEM                              \n     |      Symbolic listing file      PROTDEM                              \nr    |RBP   Request breakpoint(s)      DSNHLI calls                         \n     |      Option ID                  CB1E38D7                             \n     |      From, to terminals         X508, X508                           \n     |      On count, times thru, left 39, 0, 39                            \n_ +  |UBP   Unconditional breakpoint   #386                                 \n_ +  |UBP   Unconditional breakpoint   #389                                 \n_    |SLB   Source listing breakpoints .ANY                                 \n_    |SLB   Source listing breakpoints X508                                 \n \nPF1 Help       2 Refresh    3 End        4 Return     5 Collapse   6 Expand    \nPF7 Backward   8 Forward    9           10           11           12      \nReview the following list to remember what each Option listed on this status display means.\n\u2022The COB2DEMO option identifies the program being monitored is COB2DEMO, a COBOL program. Notice the rest of\nthe Options are indented under COB2DEMO, indicating they are options to this monitoring entry.\n\u2022The .ANY option indicates this program is being monitored under .ANY user. If you were monitoring under a single", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "212cac3f0240-1", "text": "User ID, you would see a specific User ID, such as MARY01, instead of .ANY.\n\u2022Notice the rest of the options are indented under .ANY. This indicates they are options for the monitoring entry\nCOB2DEMO when executed by .ANY user.\n\u2022The RBP option identifies a request breakpoint was set for this monitoring entry for all DSNHLI calls. Notice that the\nbreakpoint is assigned the Option ID# CB1E38D7. This request breakpoint takes affect when the program executes at\nthe terminal X508 and displays on the terminal X508 (the current terminal).\n\u2022The SLB option indicates the Source Listing Breakpoint display is the default for all breakpoint displays.\nAccess\nThe Monitoring Status display is conveniently accessed from the menus and the Source Listing facility.\nTo get a Monitoring Status for a single monitoring entry, such as a single program:\n\u2022From the Source Listing Display or Source Listing Breakpoint screen, enter STATUS in the COMMAND ===> line\nwhen the current program is displayed and press Enter , or press PF12 Status .\n\u2022From the Breakpoint Primary Option Menu, select option 2 Status .\nFrom the Primary Option Menu, complete the Monitoring Menus for the Program (2.1), Transaction (2.2), or Terminal (2.3),\nand select the Status option from the option list.\nTo get a Monitoring Status for all monitoring entries, perform the following steps:\n\u2022From the Source Listing Display or Source Listing Breakpoint screen, enter STATUS ALL in the COMMAND ===> line.\n\u2022From the Primary Option Menu, select Option 2.4 Monitoring Status.\nThe following screen shows a Monitoring Status display for all entries.\n                    CA InterTest for CICS MONITORING STATUS\n COMMAND ===>                                                                   \n \n   Type + to expand or  collapse option levels displayed below,                \n 940", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "84adb5f0e987-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n          or R to remove option(s).                                            \n \n     Option     Description                Attributes                           \n _ + COBDEML    Program monitor entry      COBOL                                \n _ + COBDEMO    Program monitor entry      COBOL                                \n _ + COB2DEMO   Program monitor entry      COBOL II                             \n _ + PL1DEMO    Program monitor entry      PL/I                                 \n                *** End of data ***                                             \n \n \n \n PF1 Help       2 Refresh    3 End        4 Return     5 Collapse   6 Expand    \n PF7 Backward   8 Forward    9           10           11           12         \nExpand and Collapse Entries\nCollapse and expand entries on the monitoring status display. An option preceded by a plus sign (+) can be expanded,\nand an option preceded by a minus sign (-) can be collapsed.\n\u2022To collapse all entries, press PF5 Collapse or use the COLLAPSE command.\n\u2022To fully expand all entries, press PF6 Expand or use the EXPAND command.\n\u2022To collapse all entries below an option, tab to the selection field in front of the option, type - (a minus sign), and press\nEnter .\n\u2022To expand all entries for a specific option, tab to the selection field in front of the option, type + (a plus sign), and press\nEnter .\nRemove Monitoring, Breakpoints, or Other Options\nEnter the letter   r  in the selection field next to any option to remove it. This removes the option and any options in that\nbranch. For example, removing monitoring for COB2DEMO removes all monitoring options and breakpoints too.\nRemoving breakpoints, especially request breakpoints, is simple using the status display. First, display the status report", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "84adb5f0e987-1", "text": "Removing breakpoints, especially request breakpoints, is simple using the status display. First, display the status report\nfor the monitored entry and expand the monitored entry to view all options. Next, enter r next to the breakpoint you want to\nremove, and press Enter.\nThe following screen is an example of removing the request breakpoint for COB2DEMO, monitored under ANY user.\n               CA InterTest for CICS MONITORING STATUS\nCOMMAND ===>                                                                   \n \n  Type + to expand or  collapse option levels displayed below,                \n         or R to remove option(s).                                            \n                                                                      More:   +\n    Option     Description                Attributes                           \n_  COB2DEMO   Program monitor entry      COBOL II                             \n   |          Waiting at breakpoint      Task 00043, UBP since 08:48 a.m.    \n_  |.ANY      User monitoring options    Active                               \n_  |.ANY      User monitoring options    Deactivated                          \n    |         Symbolic listing file      PROTDEM                              \n    |         Symbolic listing file      PROTDEM                              \nr   |RBP      Request breakpoint(s)      DSNHLI calls                         \n              Option ID                  CB1E38D7                             \n    |         From, to terminals         X508, X508                           \n    |         On count, times thru, left 39, 0, 39                            \n 941", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a6ea1ba8f6f2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n_ + |UBP      Unconditional breakpoint   #386                                 \n_ + |UBP      Unconditional breakpoint   #389                                 \n_   |SLB      Source listing breakpoints .ANY                                 \n_   |SLB      Source listing breakpoints X508                                 \n \nPF1 Help       2 Refresh    3 End        4 Return     5 Collapse   6 Expand    \nPF7 Backward   8 Forward    9           10           11           12           \nRefresh the Display\nAfter removing an option, refresh the display to reflect your changes. Use the REFRESH Command or press PF2 Refresh.\nExit the Status Display\nPress  PF3  End or PF4 Return to exit the Status display.\nSource Listing Facility for InterTest\nUse the InterTest for CICS Source Listing facility to debug your program while viewing your source code. You can access\nall of the other InterTest for CICS facilities -- ITST, CNTL, CORE, FILE, HELP and SYMD (for SymDump  for CICS licensed\nusers) directly from the Source Listing facility using menus or single-line commands.\nAs you become familiar with the Source Listing facility, keep in mind that there is no such thing as a cookbook method of\nusing InterTest for CICS. How you use it depends on your particular testing needs.\nFor more information, see Composite Module Testing.\nPrepare Your Program\nNOTE\n\u2022This section describes the procedure for using PROTSYM as a symbolic format. For instructions on\npreparing your program with DWARF as a debugging format, see DWARF.\n\u2022For detailed instructions on how to modify your JCL, see Symbolic Support.\nTo prepare a program for source listing testing and symbolic testing, you must modify the compile or assemble JCL to", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a6ea1ba8f6f2-1", "text": "include an InterTest for CICS post-processor step. For source listing testing, the LISTER parameter of the post-processor\nis required. After modifying the JCL, recompile or reassemble the program. This puts the program's listing in the InterTest\nfor CICS Symbolic File.\nStart InterTest in Your CICS Region\nInterTest for CICS is generally started once a day. At many sites, InterTest automatically starts during CICS initialization.\nAdditionally, InterTest automatically starts whenever you complete a monitoring-related request from the Monitoring\nMenus or Submenus (Option 2 on the Primary Option Menu).\nTo start InterTest for CICS or to verify that InterTest for CICS is up and running, sign on to CICS and issue the following\ncommand on a Clear screen:\nCNTL=START\nInterTest for CICS responds with a message stating either that it has successfully started or that it is already active. If\nCICS responds with a message stating that CNTL is an invalid transaction, the systems programmer who installed\nInterTest for CICS probably changed the name of the CNTL transaction. Find out the new transaction ID and try again.\n 942", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "52bf194e9fad-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterTest for CICS Transaction IDs\nInterTest for CICS has the following standard transaction IDs: ITST, CNTL, CORE, FILE, LIST, HELP, and an additional\ntransaction ID for licensed SymDump  for CICS users: SYMD. These IDs might have been modified when InterTest for\nCICS was installed. If the HELP transaction ID was not modified, you can learn your current transaction IDs by entering\nHelp on a Clear screen.\nStart a Test Session\nTo begin testing, be sure you have compiled or assembled your program with the InterTest for CICS post-processor step\nusing the LISTER parameter, and then set monitoring and breakpoints in your program.\nFollow these steps:\n1.Perform CICS sign on.\n2.Display your source code.\n3.Set monitoring.\n4.Set breakpoints.\n5.Initiate your program and begin testing.\nPerform CICS Sign On\nIf you are working in a secure CICS region, always sign on to CICS before using InterTest for CICS. InterTest for CICS\nmonitoring is sensitive to CICS user IDs.\nDisplay Your Source Code\nAccess the InterTest for CICS Source Listing facility using the following methods to view the compiled or assembled listing\nof your program:\n\u2022ITST Primary Menu Option access, Option 1 Source\n\u2022Command access: LIST=  progname\nMenu Access\nUse the ITST Primary Menu, Option 1 Source , to select your program from a selection list by program name or by\nSYMBOLIC file name. For details, see Source Selection List.\nCommand Access\nTo use the single-line CICS command, sign on to CICS. On a clear screen, enter:\nLIST=progname\nprogname\nSpecifies the name of your program.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "52bf194e9fad-1", "text": "LIST=progname\nprogname\nSpecifies the name of your program.\nInterTest for CICS displays your program on the Source Listing Display screen. From this screen set monitoring and\nbreakpoints.\nIf a message informs you that the listing is not available, consider the following:\n\u2022Is the program name correct?\n\u2022Is the program in the InterTest for CICS Symbolic File?\n\u2022Was the program compiled or assembled with the LISTER option?\nIf there are multiple copies of the program you specified, InterTest for CICS asks you to select the program that you want\nto run. When you make your selection and press Enter, InterTest for CICS displays the Source Listing of your program.\nFor more information, see Maintain Synchronized Processing.\n 943", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dc582936dd70-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSet Monitoring\nWhile viewing the program listing, enter monitor  in the top Command Line. This is the same as pressing PF5 Monitor .\nNOTE\nInterTest for CICS monitoring and breakpoints include a CICS user ID option. For a discussion of this option, see\nSet Monitoring.\nSet Breakpoints\nSetting breakpoints enables you to control program execution. InterTest for CICS halts program execution when the\nprogram reaches a breakpoint, which lets you use any InterTest for CICS facility before continuing execution.\nInitiate Program and Begin Testing\nTo exit to CICS, press PF3 End  or Clear  to terminate the Source Listing facility. If you entered through the menus, exit the\nmenus using =X or PF3 End.\nTo begin testing, execute the program as you normally would. In a secure CICS region, be sure to sign on to CICS before\nexecuting the program.\nThe Source Selection List\nFrom CICS, use the ITST transaction to display the InterTest for CICS Primary Option Menu. Select Option 1 Source  to\ndisplay the InterTest Source Menu.\nThis menu has two uses:\n\u2022Display a listing or a list of listings (type 1 in the Option field).\n\u2022Display a symbolic file or a list of symbolic files (type 2 in the Option field), and then select a Symbolic file to display\nthe Program Listings for that file.\nIn the unlabeled text fields, enter either the listing name or the InterTest for CICS Symbolic File name. Use masks to filter\nthe selection list for items matching the filter criteria:\n\u2022Use * in place of a string of any length.\n\u2022Use + for a single character.\nExample", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dc582936dd70-1", "text": "\u2022Use + for a single character.\nExample\nA mask of COBD++O filters for any seven letter item that begins with the letters COBD, has an O in the last position, and\nhas any valid character in the fifth and sixth positions. For instance, COBDEMO, COBDXXO, and COBDABO would all\nmeet the mask criteria, but COBDEML or COBDEM would not.\n\u2022Leave the fields blank to display all symbolic files or listings.\nOnce you specify a listing, file or mask and press Enter, InterTest for CICS displays the Source Listing Selection menu,\nshowing all the files or listings meeting the criteria you specified on the Source Menu. Type S next to the file or listing\nyou want and press Enter  to display that file or listing in the Source Listing display. The following screen shows a sample\nresult of the criteria entered on the Source Menu shown previously.\nCA InterTest for CICS SOURCE LISTING SELECTION\n COMMAND ===>                                                                   \n                                                                                \n   Name     File        Created      Size  Attributes                           \n _ CICSCOBA PRTSYM1  09/20/13 16:38    29  COBOL II, no purge                   \n _ CICSCOBB PRTSYM1  09/20/13 16:13    21  COBOL II, no purge                   \n _ COBDEML  PROTSYM  07/07/13 09:32    17  COBOL, no purge, composite           \n _ COBDEMO  PROTSYM  07/07/13 09:25    70  COBOL, no purge                      \n 944", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a1f3b277a626-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _ COB2DEML PROTSYM  07/07/13 09:33    25  COBOL II, no purge, composite        \n _ COB2DEMO PROTSYM  07/21/13 10:34   158  COBOL II, no purge                   \n _ COB2DMLX PRTSYM1  09/21/13 16:10    26  COBOL II, no purge, composite        \n _ COB2INSP PRTSYM1  02/01/13 09:11   155  COBOL II, no purge                   \n _ COB2IN25 PROTSYM  07/07/13 09:31    11  COBOL II, no purge                   \n _ COB2XCTL PRTSYM1  09/22/13 13:38   159  COBOL II, no purge                   \n _ CSBIN25  PROTSYM  07/07/13 09:29     8  COBOL, no purge                      \n _ C370DEML PROTSYM  07/07/13 09:33    27  COBOL/370, no purge, composite       \n _ C370DEMO PROTDGG  12/12/13 12:51   161  COBOL/370, no purge                  \n _ C370DEMO PROTWSD  12/12/13 12:51   161  COBOL/370, no purge                  \n _ C370DEMO PROTSYM  07/21/13 16:35   161  COBOL/370, no purge", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a1f3b277a626-1", "text": "_ C370IN25 PROTSYM  07/07/13 09:32    12  COBOL/370, no purge                  \n   *** End of data ***                                                          \n                                                                                \n PF1 Help       2 Refresh    3 End        4 Return     5            6           \n PF7 Backward   8 Forward    9           10           11           12\nExamine the Source Listing Display Screen\nA sample COBOL source listing is shown next:\n  CA InterTest for CICS - PROTSYM FILE SOURCE LISTING DISPLAY\n  COMMAND ==>                                                                  \n  Program= COBDEMO  Option #       Stmt #                            Margin= 01\n                                         Search=                               \n OPTS 1 Proc div  2 Workstor 3 Link sect  4 Dmap      5 Clst/Pmap More: \u2018+ \n       6 Data xref 7 Proc xref 8 Err msgs   9 Srch fwd  10 Srch bwd  \n PFKS 1 Help      2           3 End        4 Profile    5 Monitor    6 Menu   \n       7 Backward  8 Forward   9 Next Wnd   10           11           12 Status \n------------------------------------------------------------------------------\n       _ 00001 ID DIVISION.                                                   \n       _ 00002 PROGRAMID. COBDEMO.                                           \n       _ 00003 ENVIRONMENT DIVISION.                                          \n       00004 DATA DIVISION.                                                \n       _ 00005 WORKINGSTORAGE SECTION.                                       \n       _ 00006 77  S999FIELD1             PIC S9(3).                         \n      _00007 77  S999FIELD2              PIC S9(3)       VALUE +50.          \n       _ 00008 77  999FIELD1              PIC 9(3).", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a1f3b277a626-2", "text": "_ 00008 77  999FIELD1              PIC 9(3).                         \n       _ 00009 77  999FIELD2              PIC 9(3)        VALUE 50.          \n       _ 00010 77  FIRSTSCREENLEN        PIC S9(4) COMP  VALUE +1696.      \n       _ 00011 77  MSGSCREENLEN          PIC S9(4) COMP  VALUE +1040.       \n       _ 00012 77  THIRDSCREENLEN        PIC S9(4) COMP  VALUE +960.       \n       _ 00013 77  FOURTHSCREENLEN       PIC S9(4) COMP  VALUE +1761.       \n       _ 00014 77  ERRORSCREENLEN        PIC S9(4) COMP  VALUE +960.       \n         00015*77  COMMAREALEN            PIC S9(4) COMP  VALUE +39.\nField Definitions\nThis section explains the Source Listing Display screen.\nThe top of the screen displays the title and indicates when a monitor session is being recorded. A flashing \"REC\" at the\nend of the title indicates active recording.\nFields in which you enter commands and information:\n 945", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ecb121f973ed-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCOMMAND ===>\nEnter any InterTest for CICS transaction, transaction-based command, or a Source Listing Display command.\nEnter =X.Y.Z for fast-path menu access to Primary Option Menu X.Y.Z. You cannot use this command line to enter\na system-wide CNTL command.\nProgram=\nChange the program whose code displays.\nOption #\nEnter an option listed on OPTS lines by number, or enter shortcut codes for CNTL functions.\nStmt #\nDisplay a specific statement.\nNested=\nIndicates the displayed COBOL nested program or the program to be searched.\nNOTE\nThe COBDEMO program does not contain nested programs. However, if a program does contain a\nnested program, it displays here.\nMargin=\nAdjust the display margins to view code past position 80.Source Listings Command Line\nSearch=\nInstruct InterTest for CICS to search for a data name or string.\nOPTS\nLists entries for the Option # field. Valid options for COBOL, Assembler, and PL/I are listed in Source Listing\nOption Field Entries.\nPFKS\nDescribes the PF key functions. The bottom half of the Source Listing display screen displays source code from\nthe program named in the Program= field.\nPosition 1 (represented by the underscore _) of each line is reserved for entering single-letter commands and for\nbreakpoint-related functions.When a breakpoint takes effect during execution, it is identified in position 1 with one of the\nfollowing letters:\nA\nAutomatic, detected by InterTest for CICS\nU\nUncon ditional \"before\" breakpoint (stops execution before  the specified item)\n)\nUnconditional \"after\" breakpoint (stops execution after the specified item)\nC\nConditional\nV\nVariable-change\nR\nRequest", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ecb121f973ed-1", "text": "C\nConditional\nV\nVariable-change\nR\nRequest\nThe bottom of the Source Listing Display contains the source code. The numbers on the left side of each line are the\nCOBOL or PL/I statement numbers from the compiled listing, or the Assembler hexadecimal location number from the\nassembled listing.\nFor COBOL and PL/I programs, there are more OPTS to view. A More field displays to the right of the OPTS entries. Tab\nto More +  and press Enter  to view OPTS 5 to the end. Tab to More -  and press Enter to view OPTS 1 to 10.\n 946", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e2bb53d7e4c4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nThe display screen's format varies by terminal type. For 132-column terminals, lines of code display as is and\nyou view them in full. For 80-column terminals, InterTest for CICS automatically reformats the compiler output so\nthat you view most of the code in columns 1 to 80. Code beyond column 80 is viewed by changing the display\nmargins in the Margin= field. For details, see Adjust the Margins.\nSource Listing Option Field Entries\nThe numbers listed in the following table are used in the Option # field to display specific sections of the source listing or\nto search for data. Using these options makes it easy to locate specific sections of your program.\nNOTE\nFor PL/I programs, all of the OPTS labels cannot be displayed at once. Tab to the More  field and press Enter  to\nview options not currently displayed.\nOption COBOL PL/I Assembler\n1 * Procedure Division Data Name XREF First CSECT\n2 * Working-Storage Aggregate Length Table -\n3 * Linkage Section Storage Requirements -\n4 Data Division Map Static Storage Map -\n5 CLIST/Pmap Variable Storage Map Macro and Copy Source\nCatalog for high level output\n6 Data Name XREF Table of Offsets Cross Reference\n7 Procedure Cross Reference Generated Code (Assembler-\nlike)Literals Cross Reference\n8 Error Messages Error Messages Error Messages\n9 Search Forward Search Forward Search Forward\n10 Search Backward Search Backward Search Backward\n11 Indirect Commands Indirect Commands\n12 Unconditional/Conditional \n Breakpoint OptionsUnconditional/Conditional\nBreakpoint OptionsUnconditional/Conditional \n Breakpoint Options\n13 *Local-Storage Procedure Cross Reference -\n14 - Labels Cross Reference -\n20 Window: None Window: None Window: None\n21 Window: Titles Window: Titles Window: Titles", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e2bb53d7e4c4-1", "text": "21 Window: Titles Window: Titles Window: Titles\n22 Window: Registers Window: Registers Window: Registers\n23 Window: Keep Window: Keep Window: Keep\n24 Window: Program Window: Program Window: Program\n* Use these options with NESTED= entries to request a display of these sections for a specific nested program.\nThe sections available for display depend on which version of the post-processor LISTER parameter was used to compile\nor assemble the program.\nSource Listing Command Line\nThe command line is located at line 2 of the Source Listing display so it is always available, regardless of what view\noptions are currently in use. Use this command line to enter any InterTest for CICS transaction, a transaction-based\n 947", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d166bb3db4c1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nline command (such as a CNTL command or CORE command), and the Source Listing Display commands listed in the\nfollowing table.\nNOTE\nYou cannot use this command line to enter InterTest for CICS system-wide CNTL options.\nCommand PF Key Description\nABEND None Display the Abend Breakpointed Task\nscreen (this command is available only at a\nbreakpoint)\nABI ON None Default. Turn Abend Intercept on --\nintercepts all CICS abends and produce\nan automatic breakpoint screen providing\nthere a CICS HANDLE ABEND LABEL/\nPROGRAM is not active. If you want to\nintercept CICS abends for programs that\nhave an active CICS HANDLE LABEL/\nPROGRAM then see the ABI FORCE\ncommand.\nABI OFF None Turn Abend Intercept off -- causes InterTest\nfor CICS to stop intercepting CICS abends.\nNo automatic breakpoint screen appears\nand the program abends.\nABI FORCE None Turn Abend Intercept on for all CICS\nABENDS -- even if a program has an\noutstanding HANDLE ABEND active or\nissues a CICS HANDLE ABEND command.\nUse this option when you want an\nautomatic breakpoint screen for programs\nthat also have active HANDLE ABENDS to\nprocess their own errors.\nADVANCE n\nADV n\nA nNone Advances n entries in the statement trace\ntable and displays the resulting statement.\n(If n is not specified, it defaults to 1.) If data\nmonitoring is active, past data values for\nthe statement can also be displayed. Use\nthis command to redisplay the execution\nsequence of a program. Statement tracing\nmust be active for the ADVANCE command\nto function (see the TRACE option).\nNote:  This command is only valid for\nCOBOL programs.\nAUTOSTEP x y", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d166bb3db4c1-1", "text": "COBOL programs.\nAUTOSTEP x y\nAS x yNone Resume execution x verbs at a time\ndisplaying the current source statement\nfor a y interval of time. This command is\nonly available at a breakpoint. One verb at\na time until next CALL/COMMAND is the\ndefault.\nNote: This command is available only at a\nbreakpoint.\nBOTTOM\nBOTNone GO to bottom of source\nBPO None Jump to Breakpoint Option screen\n 948", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "04038eac9869-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBWD PF7 Scrolls backward. The scroll amount is set\non the Source Listing Profile.\nCALLTRACE None Shows the program call flow leading up to\nthe currently breakpointed program. Select\nprograms having symbolic support from the\nlist and display their data areas.\nCHANNEL None Displays the currently allocated channel\nand the containers in the channel. From the\nselection list you can also display the data\nwithin a container. This feature is only valid\nin CICS releases that support CHANNELs\nand Containers.\nCNTL None Displays the CNTL Command Menu.\nNote: The Monitoring Menu (2) is an\nalternative to using the CNTL menu; for\ndetails, see Monitoring Menu Options.\nCOMPOSITE None Sets composite monitoring options for\nmonitoring of subprograms. This command\nis used to establish the current load module\nname when setting/removing breakpoint\noptions on subprograms that are monitored\nunder the same name in more than one\ncomposite load module. For more details,\nsee Composite Support.\nCORE None Displays the Main Storage menu. Select\nan option to view a main storage (CORE)\ndisplay.\nCOUNTS SHOW None Turns the Code Coverage COUNTER\ndisplay on. To activate Code Coverage see\nCustomizing the Source Listing Profile or\nissue PROFILE command.\nCOUNTS NOSHOW None Turns the Code Coverage COUNTER\ndisplay off. To deactivate Code Coverage\nsee Customizing the Source Listing Profile\nor issue the PROFILE command.\nCOUNTS RESET None Resets the program Code Coverage\nstatement counters to zero.\nCOUNTS op value None Turns the Code Coverage COUNTER\ndisplay on and highlights program\nstatements that match the criteria. The\nsource listing is repositioned to the first\nstatement matching the criteria.\nOp can be: EQ or =, NE or <>, LT or <, GT", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "04038eac9869-1", "text": "Op can be: EQ or =, NE or <>, LT or <, GT\nor >, LE or <= or =<, GE or >= or =>\nValid values: 0 to 9999\nCOUNTS NEXT None Repositions the source listing to the next\nstatement that matches the previously\nspecified COUNT op value criteria.\nCOUNTS ALL None Removes previously specified COUNT op\nvalue criteria and redisplays source listing\nwithout special COUNTER highlighting.\n 949", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "95cbb07d8c8f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDATAMON\nDMNone Displays the Monitoring Command Builder\nmenu to set and remove statement tracing\nand data monitoring.\nNote: This command is only valid for\nCOBOL programs.\nDATAMON ON\nDM ONNone Turns data monitoring on. This causes\nInterTest for CICS to capture data values\nfor each executed statement in the\nprogram. You will then be able to redisplay\nthese values at a breakpoint, by tracing\nbackward and forward through the entries\nin the statement trace table using the PREV\nand ADVANCE commands. DATAMON ON\nforces TRACE ON.\nNote: This command is only valid for\nCOBOL programs.\nDATAMON OFF\nDM OFFNone Turns data monitoring off. This causes\nInterTest for CICS to stop capturing data\nvalues for each executed statement in the\nprogram. In addition, you are no longer\nable to display captured data values when\ntracing backward and forward through the\nentries in the statement trace table using\nthe PREV and ADVANCE commands.\nNote: This command is only valid for\nCOBOL programs.\nDISPLAY data-item\nD data-itemNone Displays the storage of a data-name. (this\ncommand is available only at a breakpoint)\nDOWN None Shifts listing down\nEND PF3 Returns to the prior display or menu.\nFILE None Displays the Auxiliary Storage Menu. Select\nan option to view a file or queue.\nFIND\nFNone Find a string.\nFP None Find paragraph.\nFS None Find statement number.\nFWD PF8 Scrolls forward the amount indicated on the\nSource Listing Profile.\nHELP PF1 Displays help for the Source Listing Facility.\nIC None Jump to Indirect Command screen.\nITST See MENU Displays the ITST Primary Option Menu.\nKEEP data-item", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "95cbb07d8c8f-1", "text": "ITST See MENU Displays the ITST Primary Option Menu.\nKEEP data-item\nK data-itemNone Add a data-item to the static Keep window\nLEFT None Shift listing left.\nLOCATE\nLOC\nLNone Locate line number, a label, or part of the\nlisting.\nMARGIN\nMARNone Shift listing to specific margin.\n 950", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b127a8b4df77-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMENU PF6 Displays the high-level menu. When not\nat a breakpoint, it is the ITST Primary\nOption Menu; when at a breakpoint, it is the\nBreakpoint Primary Option Menu.\nMLOG None Displays, starts, stops, cancels, or loads\nrecorded monitoring sessions.\nMONITOR PF5 Sets monitoring for the current program\nusing the CICS user ID displayed on the\nProfile.\nOFFALL None Removes all breakpoints set by active\nUSER or TERMINAL Active USERID\nis used if a valid USERID is signed on.\nOtherwise, the active TERMINAL is used\nALL breakpoints for ALL programs/\ntransactions/ will be removed that were set\nby the active USERID or active TERMINAL.\nOFFALL TERM None Removes all breakpoints set by active\nTERMINAL\nOFFALL USER None Removes all breakpoints set by active\nUSER.\nPO None Sets or removes storage protection options\nPREV n\nP nNone Backs up n entries in the statement trace\ntable and displays the resulting statement.\n(If n is not specified, it defaults to 1.) If data\nmonitoring is active, you can also display\npast data values for the statement. Use this\ncommand to step backward through the\nexecution of a program. Statement tracing\nmust be active for the\nPREV command to function (see the\nTRACE option).\nNote: This command is only valid for\nCOBOL programs.\nPROFILE PF4 Displays Source Listing Profile, where you\ncan change settings for the current session.\nRBP None Sets or removes request breakpoints\nRIGHT Shifts listing right\nRO None Sets or removes replacement options\nRUN None Resumes execution ignoring all\nbreakpoints. This command is available\nonly at a breakpoint.\nSET None Initializes a data-item's value. This\ncommand is available only at a breakpoint.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b127a8b4df77-1", "text": "SET None Initializes a data-item's value. This\ncommand is available only at a breakpoint.\nSO None Sets or removes special options\nSDFDATA None Set to display data in structure display\nformat for the current program.\nSDFHEX None Set to display data in hexadecimal/\ncharacter format for the current program.\n 951", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9884ac228df0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSTATUS PF12 Displays the Monitoring Status report\n(Option 2.4 on the Primary Option Menu)\nfor the current program. You can remove\nmonitoring, breakpoints, and options\ndirectly from the Status display.\nSTATUS ALL None Displays the Monitoring Status report for\nall programs, transactions, and terminals\nInterTest for CICS is monitoring in the\nregion.\nSTORAGE None Displays a listing off all USER and CICS\nclass storage associated with the currently\nbreakpointed task (most storage acquired\nby InterTest for CICS is not displayed),\nthis command also validate the crumple\nzones for each piece of storage. See The\nSTORAGE Facility.\nTOP None Go to top of source.\nTRACE\nTRNone Displays the Monitoring Command Builder\nmenu to set and remove statement tracing\nand data monitoring.\nNote: This command is only valid for\nCOBOL programs and is unrelated to the\nbacktrace facility.\nTRACE ON\nTR ONNone Turns statement tracing on. The number of\nentries saved in the statement trace table\nis determined by the STMTTRCE option in\nIN25OPTS. The default is 1000.\nNote: This command is only valid for\nCOBOL programs and is unrelated to the\nbacktrace facility.\nTRACE OFF\nTR OFFNone Turns statement tracing off. TRACE OFF\nforces DATAMON OFF.\nNote: This command is only valid for\nCOBOL programs and is unrelated to the\nbacktrace facility.\nUP None Shift listing up.\n=x.y.z None Fast-path to Primary Menu Option x.y.z.\nAction Characters Supported from a Source Listing Display or Breakpoint\nYou can perform the following list of the functions by entering a single character on your source listing.\nDocumentation Action Character Function\nu Unconditional; sets an unconditional", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9884ac228df0-1", "text": "Documentation Action Character Function\nu Unconditional; sets an unconditional\nbreakpoint that stops before  the specified\nitem.\n) Unconditional; sets an unconditional\nbreakpoint that stops after the specified\nitem.Using Breakpoints\nc Conditional; sets a conditional breakpoint.\n 952", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3cb5354289dd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nv Variable-change; sets a variable-change\nconditional breakpoint (for COBOL or\nAssembler programs).\nx Remove; removes a breakpoint or removes\na variable from the Keep window.\n+ Start Segmented Monitoring  at this\nprogram statement.\n- Stop Segmented Monitoring  at this\nprogram statement.\nd Display; displays program or variable\nstorage at a breakpoint.\nk Keep; keeps a variable in the Keep window.\nm Modify; modifies a variable at a breakpoint.\n@ Display; displays the main storage area\npointed to by a data item for a 24-bit\naddress.\n% Display; displays the main storage area\npointed to by a data item for a 31-bit\naddress.\n< Scroll keep data left the   width of the\ndisplay area. To scroll a specific number of\nbytes,   specify a value after the < .\n> Scroll keep data right the   width of the\ndisplay area. To scroll a specific number of  \nbytes, specify a value after the > .   \n+ Increment (Keep window only); increases\nCOBOL index item value. To increase by a\nspecific value, specify a value after the +.Breakpoint Activities\n- Decrement (Keep window only); decreases\nCOBOL index item value. To decrease by a\nspecific value, specify a value after the -.\nResume and Execution Options b Bypass; bypasses monitoring of an\ninstruction at an automatic breakpoint.\ng Go (resume execution) at this program\nstatement.\nNOTE\nThe v, d, @, %, k, and m functions should be entered next to a statement that references or defines the variable\nthat you want to display, keep, or modify. If the statement references the variable, you must also position the\ncursor under the variable name before pressing Enter.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3cb5354289dd-1", "text": "cursor under the variable name before pressing Enter.\nShortcut Commands for CNTL Functions\nTo access a CNTL function, enter a code using the following format in the Option # field, and press Enter:\n=nns  OR  =nnr\n=\nRequired.\nnn\nSpecifies function number (10 to 33) from the CNTL main menu.\n 953", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3e74d4cd4648-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\ns or r\nSpecifies setting or removing the option .\nNOTE\nWhile the CNTL shortcut commands are supported, you will find it easier to use the Monitoring Menus, available\nfrom Primary Option Menu Option 2 Monitoring .\nThe following table summarizes the Option # codes you can enter for the standard CNTL Selection Menu functions:\nOption # Command CNTL Selection Menu Function\n=10s Sets monitoring for the program displayed; same as PF5.\n=10r Removes monitoring, breakpoints, and all other options for the\nprogram displayed.\n=11s and 11r Sets and removes unconditional breakpoints.\n=12s and 12r Sets and removes conditional breakpoints.\n=13s and 13r Sets and removes request breakpoints.\n=14s and 14r Sets and removes Segmented Monitoring On option.\n=15s and 15r Sets and removes Segmented Monitoring Off option.\n=16s and 16r Sets and removes statement tracing and data monitoring.\n=20s and 20r Sets and removes Replace options.\n=21s and 21r Sets and removes Protection options.\n=22s and 22r Sets and removes Special options.\n=23s Sets Composite Support.\n=24 Accesses the Indirect Commands facility.\n=30 Shows the Status Display screen.\n=31 Sets Utility Options screen.\n=33 Resumes task execution.\nSource Listing PF Keys\nThe following table summarizes the PF key functions for the Source Listing Display screen. PF key assignments are\nstandard across all InterTest for CICS menus.\nNOTE\nThe ITST menus and relocated command line eliminate the need to assign CNTL, CORE, and FILE to PF keys.\nNavigate to these facilities using the menus, or use the command line to enter the transaction or desired single-\nline command.\nPF Key Function", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3e74d4cd4648-1", "text": "line command.\nPF Key Function\nPF1 Help Help; displays a Help menu relating to the current Source Listing\nDisplay screen.\nPF2 Unassigned.\nPF3 End End or Clear; terminates the Source Listing Facility. Displays an\nearlier ITST panel, if applicable, or CICS.\nPF4 Profile Displays the Source Listing Profile screen, where you can set\nvalues for your current session.\nPF5 Monitor Turns monitoring on for the program whose listing is being viewed\nusing the CICS user ID on the Profile.\n 954", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "653eee2bbf11-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPF6 Menu Displays the Primary Option Menu.\nPF7 Backward Scrolls the compiler output backward by one page unless the\nsetting was changed on the Profile. Does not apply within the\nKeep window.\nPF8 Forward Scrolls the compiler output forward by one page unless the setting\nwas changed on the Profile. Does not apply within the Keep\nwindow.\nPF9 Switch to next window\nPF10, PF11 Unassigned.\nPF12 Status Displays the Monitoring Status for the current program. You can\nremove breakpoints and options directly from the Status display.\nSearch for Data\nYou can request InterTest for CICS to define, search for, and display any character string (such as a data item, label, or\nparagraph name). This is a quick way to go to different areas in a listing when you want to set a breakpoint or check your\ncode.\nSearch for data using the Search=field, or by entering a FIND or LOCATE command on the command line.\nIf you know the line number that you want to view, use the line command to position the listing accordingly. For details,\nsee View the Online Listing.\nFind a Definition or Search Using the Search = Field\nUse the Search= field to define or search for data as follows.\nTo display the definition of a data item:\n1.Enter a data item name up to 31 characters in the Search=  field.\n2.Press Enter to begin the search. InterTest for CICS highlights the data item and its definition.\nTo search for a data item:\n1.Enter up to 31 characters in the Search= field.\n2.Specify the search direction in the Option # field. (Option # 9 is Search Forward; Option # 10 is Search Backward.)\n3.Press Enter  to begin the search.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "653eee2bbf11-1", "text": "3.Press Enter  to begin the search.\nFor COBOL nested programs, InterTest for CICS first searches the current nested program (indicated in the NESTED=\nfield) for the specified data item. If the data item is not found in the indicated program, InterTest for CICS then searches\nthe main program and other nested programs for the item.  It is not necessary to enter the entire data item, label, or\nparagraph name; enter the first few characters to start your search.\nExample\nIf you wanted to search for TASKNUM, you could enter TASK, TASKN, and so on, in the Search= field.\nSearch the Program Online Listing\nTo find the next string within a program online listing, enter:\nFIND string NEXT\nString\nSpecifies any valid string (up to 31 characters in length). If the string contains a blank, it must be enclosed in\napostrophes ('). If the string contains an apostrophe ('), it must be enclosed in quotes (\").\nTo find the previous string within a program online listing, enter:\n 955", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d3fd3d2359ee-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFIND string PREV\nTo repeat the find request, press Enter .\nLocate an Area Within the Program Online Source Listing\nTo locate a label, line-number, offset, or special area within the program online source listing, enter:\nLOCATE label | line-number | hex-offset | .xx\nlabel\nIndicates any valid label with an ASSEMBER, COBOL or PL/1 program including datanames, CSECT, procedure,\nand paragraph names (up to 31 characters in length).\nNOTE\nAn all numeric COBOL paragraph name cannot be located; it is interpreted as a line number.\nLine-number\nIndicates any line number within an ASSEMBLER, COBOL or PL/1 program.\nHex-offset\nIndicates any offset within an ASSEMBER program and is indicated with a leading + character.\n.xx\nIndicates a special indicator depending on language as follows:\nCOBOL:\nPD = Procedure Division\nWS = Working-Storage Section\nLC = Local-Storage Section\nLS = Linkage Section\nDM = DMAP\nPM = COBOL/VS PMAP/CLIST\nCL = COBOL/VS PMAP/CLIST\nOF = COBOL II OFFSET/LIST\nLI = COBOL II OFFSET/LIST\nDX = Data Name Cross Reference\n.PX = Procedure Cross Reference\n.EM= Error Messages\nPL/1:\n.AG = Aggregate List\n.SR = Storage Registers\n.SS = Static Storage\n.VS = Variable Storage\n.OF = Offsets\n.GC = Generated Code\n.PX = Procedure Cross Reference\n.LX = Label Cross Reference\n.DX = Data Name Cross Reference\n.EM = Error Messages\nASSEMBLER:\n.C1 = 1st CSECT\n.1C = 1st CSECT", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d3fd3d2359ee-1", "text": ".C1 = 1st CSECT\n.1C = 1st CSECT\n.MC = Macro Catalog\n.XR = Cross Reference\n.LI = Literals\n 956", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "254d806511bd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n.EM = Error Messages\nView the Online Listing\nUse the command line commands to position or shift the view of the listing. You can go to the top or bottom of the listing,\nshift the listing to the right or left a specific number of characters, or position the listing to a specific line.\nPosition Listing at Top\nTo position the listing at the top of the source code within the complete online listing, enter TOP.\nPosition Listing at Bottom\nTo position the listing at the bottom of the source code within the complete online listing, enter BOTTOM.\nShift Listing to the Right\nTo shift the listing to the right a specific number of characters, enter\nRIGHT char-count\nchar-count\nIndicates any valid number of characters between 1 and 49.\nDefault : 10\nNOTE\nThe RIGHT command cannot be used on Mod5 terminals.\nShift Listing to the Left\nTo shift the listing to the left a specific number of characters, enter:\nLEFT char-count\nchar-count\nIndicates any valid number of characters between 1 and 49.\nDefault : 10\nNOTE\nThe LEFT command cannot be used on Mod5 terminals.\nShift Listing Down\nTo shift the listing down a specific number of lines, enter:\nDOWN line-count\nline-count\nIndicates any valid number of lines between 1 and 9999.\nDefault : 1\nShift Listing Up\nTo shift the listing up a specific number of lines, enter:\nUP line-count\nline-count\nIndicates any valid number of lines between 1 and 9999.\n 957", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ff3306e93b14-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDefault : 1\nShift Listing to a Margin Position\nTo shift the listing to a specific margin position, enter:\nMARGIN margin value\nmargin value\nIndicates any valid number of characters between 1 and 50.\nNOTE\nThe MARGIN command cannot be used on Mod5 terminals.\nPosition Listing to a Line Number\nTo position the listing to a specific line number, enter:\nFS line-number\nline-number\nIndicates any line number within an ASSEMBLER, COBOL, or PL/1 program.\nPosition Listing to a Label\nTo position the listing to a specific paragraph, procedure, or label, enter:\nFP label\nlabel\nIndicates any valid label within an ASSEMBLER, COBOL or PL/1 program including datanames, CSECT,\nprocedure, and paragraph names.\nNavigate to the Indirect Commands Build Screen\nTo navigate to the Indirect Commands build screen, enter IC.\nNavigate to the Breakpoint Options Build Screen\nTo navigate to the Breakpoint Options build screen, enter BPO .\nNOTE\nThe BPO command does not require any parameters. However a corresponding U, ), R, or C must be placed in\nthe left line command area of the statement requiring the breakpoint option.\nScroll Forward and Backward\nPF7 and PF8 scroll the compiler output backward and forward, respectively. The default scroll amount is one page;\nhowever, you can change the scroll amount on the Source Listing Profile screen.\nPF7 and PF8 do not apply to the Keep window, within which PF19 and PF20 perform the scroll forward and backward\nfunctions.\nChange the Program\nAt any time during testing, InterTest for CICS lets you to change the program with which you are working.\nProgram=\n 958", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "be00a5ea055e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo change the program displayed, follow these steps:\n1.Enter the desired program name in the Program= field.\n2.Press Enter to display the listing from the beginning of the program, or use the Option #, Statement #, or Search=\nfields to select another point of initial display before pressing Enter.\nPosition the Display\nWhen you initiate the Source Listing Facility, you can easily name the program and position the display at any statement\nnumber with a single command:\nLIST=progname,#nnnnn\nprogname\nSpecifies the name of the program you want to view\n#\nRequired\nnnnnn\nIndicates the statement number from 1 to 99999. If the requested statement number is greater than the number of\nstatements in the listing, the greatest number is displayed.\nAssembler Programs\nWhen you initiate the Source Listing Facility you can position the Assembler display at a specific offset location in a\nCSECT. Use the command form:\nLIST=progname,offset\nprogname\nSpecifies the name of the program you want to view\noffset\nSpecifies a one to six hexadecimal number from 0 to FFFFFF\nExample\nTo position the Source Listing display of program COBDEMO with statement 99 highlighted near the top of the display\narea enter:\nLIST=COBDEMO,#99\nPosition the Source Listing display of program ASMDEMO with offset 0007E8 highlighted near the top of the display area\nenter:\nLIST=ASMDEMO,7E8\nPosition the display area to include more data, source listing, or storage items using the Option #, Statement #, Margin=,\nand Search = fields of any Source Listing screen.\nOption #\nTo display a specific section, select an Option # from the OPTS.\nStatement #", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "be00a5ea055e-1", "text": "To display a specific section, select an Option # from the OPTS.\nStatement #\nTo display a particular statement, enter the desired statement number from 1 to 9999 in the Statement # field, and\npress Enter .\nNested=\nTo display a particular nested program, enter the program name in the Nested = field, and press Enter .\n 959", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1387240df371-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSearch=\nTo display the code defining a particular data item in Working-storage, Local-Storage, or the Linkage section,\nenter the data name in the Search = field, and press Enter .\nTo display the code surrounding a particular paragraph or label, enter the paragraph name or label name in the\nSearch = field, and press Enter.\nDisplacement=\nTo display the listing at a specific displacement in an Assembler program, enter the displacement from 0 to\nFFFFFF in the Displacement= field.\nAdjust the Margins\nBecause certain compiler output (particularly Assembler and Optimizer/II  output) extends beyond 80 positions, it might be\nnecessary to adjust the display margins to view more of your program's Source Listing.\nMargin=\nTo adjust the output display to view portions of the listing to the right of position 80, perform the following steps:\n1.Enter the position number of the desired left margin in the Margin= field. Valid entries are 1 through 50.\n2.Press Enter . The screen displays the output beginning at the position specified, as shown in the following example.\nExample\nAssembler users often set the Margin= field to 28 as shown next.\nCA InterTest for CICS - PROTDEM FILE SOURCE LISTING DISPLAY\nCOMMAND ==>\nProgram= ASMDEMO  Option #       Stmt #      Displacement=      Margin= 28\n                                        Search=\nOPTS 1 1st CSECT 2           3            4           5          6 Xref\n     7 Literals  8 Err msgs  9 Srch fwd  10 Srch bwd 11         12 Bkpt opts\nPFKS 1 Help      2           3 End        4 Profile   5 Monitor  6 Menu", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1387240df371-1", "text": "7 Backward  8 Forward   9 Next Wnd  10          11         12 Status\n-----------+---------------------------------------------------------------\n      LOC   STMT       SOURCE STATEMENT\n    000000   463+        STM   14,12,12(13)        SAVE CALLER'S REGISTERS\n             464+*************************************************************\n             465+*             ESTABLISH CODE ADDRESSIBILITY\n             466+*************************************************************\n             467+        USING *4,2,3,4,7   \n    000004   468+        LR    2,15\n    000006   469+        LR    3,2\n    000008   470+        AH    3,DFHEI4K\n    00000C   471+        LR    4,3\n    00000E   472+        AH    4, DFHEI4K\n    000012   473+        LR    7,4\n    000014   474+        AH    7,DHEI4K\n             475+**************************************************************\n             476+              OBTAIN DYNAMIC STORAGE          \nNOTE\n 960", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5e80c658a7e0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022The statement or location numbers stay on the screen as the rest of the display shifts left or right. A plus sign\n(+) in the line above the display area indicates the column where shifting begins.\n\u2022If there is no output beyond position 80, InterTest for CICS overrides a margin setting greater than 1 and\nredisplays positions 1 through 80.\nLog a Monitoring Session\nWhen you monitor a program, you can log, or record, the monitoring session and save it to PROTMLOG. You can then\nuse this file to repeat your monitoring session later.\nYou can issue the following monitoring session commands from the listings facility command line. All monitoring session\ncommands are applied to the user ID and terminal that issue the commands:\nMLOG\nDisplays the InterTest for CICS SAVED DEBUG SESSIONS screen (ITST 2.7).\nMLOG START [name [description ]]\nStarts recording a new monitor session.\n\u2022name\n(Optional) Specifies a name for the session. If you omit the name, the session is saved with the same name as\nthe program.\nLimits:  1 to 8 characters\n\u2022description\n(Optional) Describes the session.\nLimits:  1 to 35 characters\nWhen you issue the START command, the active recording session is indicated by a flashing REC on the Source\nListing Display screen.\nMLOG STOP\nStops recording and saves the monitor session.\nWhen you issue the STOP command, the flashing REC disappears from the Source Listing Display screen.\nMLOG CANCEL\nCancels the current session and deletes all entries that were recorded since the START command was issued.\nWhen you issue the CANCEL command, the flashing REC disappears from the Source Listing Display screen.\nMLOG LOAD [ name ]\nLoads an existing session.\n\u2022name", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5e80c658a7e0-1", "text": "MLOG LOAD [ name ]\nLoads an existing session.\n\u2022name\n(Optional) Specifies the session. If you omit the name, the session that has the same name as the program is\nloaded.\nLimits:  1 to 8 characters\nCustomize the Source Listing Profile\nInterTest for CICS was designed with the user in mind. The Source Listing Profile lets you set specific functions that help\nyou meet your testing needs.\nAccess\nTo access the Profile, type profile  on the command line and press Enter , or press PF4 while viewing the Source Listing or\nBreakpoint screen. The Profile appears at the bottom of your screen.\nIt is not necessary to change the options in the Profile screen unless you want to change the default settings for your test\nsession.\n 961", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fc526e1346a2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInfo Area\nThe info area is located at the top of the Source Listing Display screen under the Search field. The info area displays\nvarious windows depending on the value in the Display window field in the Source Listing Profile.\nTo change the information displayed in the info area, change the value in the Display window field.\nFollow these steps:\n1.On the Source Listing screen, either type profile  in the command line and press Enter , or press PF4.\nThe Profile screen appears.\n2.Specify the desired value in the Display window field, and press Enter .\nThe info area displays the information that you requested.\n3.Alternatively, type 20-24 in the Option # field to display the required window. See Source Listing Option Field Entries.\n\u2013Press PF9 to switch between the windows in order. PF9 does not switch between the windows when the Backtrace\nFacility is active.\nThe Display window field has the following values:\nN (None)\nDisables the info area so that you are able to see more of the source code.\nT (Titles)\nDisplays the Title window in the info area. The Title window shows the title and header lines of your Source Listing\nDisplay, including the option and PF key descriptions. T is the default value for the Display window field unless\nchanged during the product installation.\nR (Registers)\nDisplays the Register window in the info area. The Register window shows the registers and attributes of your\nprogram.\nK (Keep)\nDisplays the Keep window in the info area. The Keep window shows your program data items. If the AUTOKEEP\noption is ON, the window always switches to the Keep window whenever there are any data items to be\ndisplayed.\nP (Program)\nDisplays the Program window in the info area. The Program window enables you to specify the load module name", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fc526e1346a2-1", "text": "Displays the Program window in the info area. The Program window enables you to specify the load module name\nand view the symbolic file information.\nRegister Window\nThe Register window allows you to display and modify the contents of registers, and view an area where a register points\nto.\nThe following screen shows the Register window:\n   CA InterTest for CICS - PROTSYM FILE  ABEND DETECTED BREAKPOINT             \nCOMMAND ===>                                                                        \nProgram= COBDEMO  Option #       Stmt #                                             \n                                        Search=                                     \n------------------------------------------------------------------------------------\n R0-R7  3520A424 35209220 00100100 3520B5C8 3520A540 350F79E0 350F7998 B5200108     \n R8-R15 3520A5C8 3520A2C0 3651B15C 3651B904 3651B11C 352090D0 B651C242 00000000     \n Cond. Code = 0   Amode = 31   ExecKey = USER   TransIsolate = YES                  \n------------------------------------------------------------------------------------\n _ 000412 CONTINUE-TASK.                                                            \n   000413**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED                              \n A    ==>     ADD +1 TO TASKNUM.                                                    \n 962", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e8e4d9238e08-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n...\nThe Register window contains the following fields:\n\u2022R0-R7\n\u2022R8-R15\nDisplays the contents of registers at the current statement of the program.\n\u2022Cond. Code\nIndicates the current condition code.\n\u2022Amode\nDisplays the current addressing mode of the program.\n\u2022ExecKey\nDisplays the ExecKey for the current program if the CICS Storage Protection Option is active, depending on the option\nspecified in the program definition.\n\u2022TransIsolate\nDisplays the transaction isolation option of the current task if the CICS Transaction Isolation Option is active.\nTo modify the program registers, overtype the displayed contents with the desired value, and press Enter . To view the\narea pointed to by a register, overtype the first displayed character of the register with either an at sign (@) for a 24-bit\naddress, or with a percent sign (%) for a 31-bit address, and press Enter .\nProgram Window\nThe Program window enables you to specify the name of a composite load module, and set breakpoints for subprograms\nthat belong to that composite load module.\nThe following screen shows the Program window:\n   CA InterTest for CICS - PROTSYM FILE  SOURCE LISTING DISPLAY                \nCOMMAND ===>                                                                        \nProgram= CSBIN25  Option #       Stmt #                                             \n                                        Search=                                     \n Load module= COBDEML                                                               \n Symbolic file: PROTSYM  Timestamp: 2014-05-27 05:05 Language: IBMCOB 4.2           \n---------+--------------------------------------------------------------------------\n _ 000023 PROCEDURE DIVISION USING COMM-TEXT.                                       \n _ 000024     MOVE ZERO TO DIVCT.                                                   \n...\nThe Symbolic file, Timestamp and Language fields provide information about the subprogram specified in the Program", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e8e4d9238e08-1", "text": "The Symbolic file, Timestamp and Language fields provide information about the subprogram specified in the Program\nfield, not the load composite module in the Load module field.\nScroll Amount\nThe scroll amount determines how much more of your source listing displays each time you use PF7 or PF8.\nTo set the scroll amount for scrolling backward and forward (PF7 and PF8), perform the following steps:\n1.Type profile  on the command line and press Enter, or press PF4 from a Source Listing screen to display the Profile\nscreen.\n2.Overtype the current PF7/8 Amount=entry with one of the following:\nPAGE\nThe size (number of lines) of the display area on the Source Listing Display and Breakpoint screens.\nHALF\nHalf the size of the display area.\n 963", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "95b83b60f90c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nnnnn\nAny number of lines from 1 to 9999.\nSTOP\nGo to the next or previous breakpoint in the program.\n3.Press Enter. The change takes effect immediately, and you return to the Source Listing Display screen.\nNOTE\n\u2022Setting the Scroll Amount to STOP is an excellent way to review all of the breakpoints set in your program\n\u2022PF7 and PF8 do not apply to the Keep window, within which PF19 and PF20 perform the forward and\nbackward functions\nStep Timing\nStep timing determines where the Step or Next command stops statement execution.\nTo set Step timing to After, type After  and press Enter .\nAFTER\nThe program is stopped after the next verb, statement or instruction is executed.\nBEFORE\nThe program is stopped before the next verb, statement or instruction is executed. (Default)\nStep Amount\nThe step amount determines how many COBOL verbs, Assembler instructions, or PL/I statements will be executed at a\ntime when you use PF10 to single-step through your program.\nStepping Amount=\nTo set the step amount for PF10, perform the following steps:\n1.Type profile  on the command line and press Enter, or press PF4 to access the Profile screen from any Source Listing\nscreen.\n2.Enter the desired number of COBOL verbs, Assembler instructions, or PL/I statements from 1 to 999 in the Stepping\namount= field.\n3.Press Enter . When the Source Listing Breakpoint screen is redisplayed, the new step amount is reflected in the PF10\n(Single-step) definition, as shown in the following example.\nExample\nThe Source Listing Breakpoint display in the following figure shows a PF10 step amount set to 004 Verbs.\nCA InterTest for CICS - PROTDEM FILE SOURCE LISTING BREAKPOINT", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "95b83b60f90c-1", "text": "CA InterTest for CICS - PROTDEM FILE SOURCE LISTING BREAKPOINT \nCommand ==>\nProgram= COBDEMO  Option #       Stmt #                           Margin= 01 \n                       Search=\nOPTS 1 Proc div  2 Work-stor 3 Link sect 4 D-map      5 Clst/Pmap More:   + \n     6 Data xref 7 Proc xref 8 Err msgs  9 Srch fwd  10 Srch bwd\n            \nPFKS 1 Help      2            3 Det Bkpt  4 Profile    5 Resume     6 Menu \n     7 Backward  8 Forward    9          10 004 Verbs 11 Backtrace 12 Status  \n---------------------------------------------------------------------------- \n  _ 00880 CONTINUETASK. \n    00881**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED \n  A   ==>     ADD +1 TO TASKNUM. \n 964", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d723da03a0d2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n      ==> \n      ==> ASRA abend (0C7) detected and prevented. Caused by invalid decimal \n      ==> arithmetic data format. \n      ==> \n      ==>      Press PF1 for a detailed description. \n      ==> \n  _ 00883     IF TASKNUM = 1 \n  _ 00884         MOVE 'DMAPASR'  TO MAPNAME. \n  _ 00885     IF TASKNUM = 2 \n  _ 00886         MOVE 'DMAPSUM'  TO MAPNAME. \n  _ 00887     IF TASKNUM GREATER 2 \n  _ 00888         GO TO SENDENDMSG.\nNOTE\nThe step value of PF10 on the Source Listing Breakpoint screen does not apply to the PF10 definition on the\nDetailed Breakpoint screen.\nUse the Stepping Amount parameter to enable the automatic tracing feature of the Source Listing Backtrace. When the\nStepping Amount is set to any number greater than one, the new value becomes the number of statements InterTest for\nCICS traces on the Source Listing Backtrace. (PF9 traces backward; PF10 traces forward).\nTurn on Automatic Single-Stepping\nAutomatic single-stepping lets you to go through your source listing a specified number of steps at specified time intervals.\nAuto-stepping= ON\nTo access the Auto-stepping Parameters screen, perform the following steps:\n1.Type profile  on the command line and press Enter, or press PF4 from any Source Listing display. The Source Listing\nProfile is displayed.\n2.Specify Auto-stepping= ON.\n3.Press PF4 to activate your specification. The auto-stepping parameters are displayed.\nWhen Auto stepping= ON, the defaults are as follows:\n\u2022Pause one second  before repeating single-stepping or automatic tracing", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d723da03a0d2-1", "text": "\u2022Pause one second  before repeating single-stepping or automatic tracing\n\u2022Stop at the next CICS command or call\nTo change the automatic stepping amount, perform the following steps:\n1.Type profile  on the command line and press Enter, or press PF4 from the Profile screen to access the auto-stepping\nparameters.\n2.Specify the following options:\nWait amount\nEnter the number of seconds from 1 to 59 that InterTest for CICS should pause at each single-step breakpoint.\nStop value\nEnter a value that determines when automatic single-stepping should terminate, either at a CICS command or\ncall, or after a specified number of steps are executed.\n3.Press Enter to process the new settings and return to the Profile screen.\n4.Press Enter  again to return to the Source Listing display or breakpoint screen.\nBreakpoint Display Mode\nInterTest for CICS has two breakpoint displays:\n 965", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "60d1af516b70-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022The Source Listing Breakpoint version lets you to test directly from your source listing.\n\u2022The Detailed Breakpoint display requires you to use one-line InterTest for CICS commands and other menus.\nThe initial display mode depends on the setting chosen when InterTest for CICS was installed; however, you can change\nthe display mode at any time by using the Profile screen. This change remains in effect until the Source List BKPT=\nsetting is changed.\nSource List BKPT=\nTo change the breakpoint display mode, perform the following steps:\n1.Type profile  on the command line and press Enter, or press PF4 to display the Profile screen. The Source List BKPT=\nfield shows the current setting.\n2.Overtype the current value with one of the following:\nON\nDisplays the Source Listing Breakpoint.\nOFF\nDisplays the Detailed Breakpoint.\n3.Press Enter to process the new setting and to return to the Source Listing Display screen.\nFrom and BKPT Terminal IDs\nFrom Terminal ID=\nFrom Terminal ID identifies where the program executes. The default for the From Terminal ID setting depends on your\nsystem's installation option value for DFLTUSER.\n\u2022When DFLTUSER=.ANY is in effect, the default is the terminal displaying the source listing.\n\u2022When DFLTUSER=SPECIFIC is in effect and you are signed on to CICS, the default is .ANY. This entry tells InterTest\nfor CICS to monitor the program when it runs from .ANY terminal wherever you are signed on to CICS.\nTo change the default From Terminal ID, perform the following steps:\n1.Type profile  on the command line and press Enter, or press PF4 from the Source Listing display to access the Source\nListing Profile screen.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "60d1af516b70-1", "text": "Listing Profile screen.\n2.Overtype the entry in the From Terminal ID field to specify where the program will run. Valid entries are as follows:\nterminal ID\nRuns from the specified terminal\n*\nRuns from current terminal displaying this profile screen\n.ANY\nRuns from any terminal or even without a terminal\n.NO\nMonitors only when this program runs as a background transaction without a terminal.\nNOTE\nThe BKPT terminal ID must be set to a specific 3270-type terminal that will receive the breakpoints. If\nFrom terminal ID is .N and the BKPT terminal ID is .NO or .ANY, the breakpointed task is abended with\nan INTE abend when the first breakpoint is encountered.\n3.Press Enter to process the new From Terminal ID setting and to return to the Source Listing Display.\nBKPT Terminal ID=\nFrom Terminal ID identifies the terminal where breakpoints display. The default for the BKPT Terminal ID depends on your\nsystem's installation option value for DFLTUSER. To view your system's installation options online, use ITST Option 7.1.2.\n 966", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "042312ad1f7b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022When DFLTUSER=.ANY is in effect, the default is the terminal that is displaying the source listing.\n\u2022When DFLTUSER=SPECIFIC is in effect and you are signed on to CICS, the default is .ANY. This entry tells InterTest\nfor CICS to send the breakpoints to any terminal where the user is signed on to CICS.\nTo change the default, perform the following steps:\n1.Type profile  on the command line and press Enter, or press PF4 from the Source Listing display to access the Source\nListing Profile screen.\n2.Overtype the entry in the BKPT Terminal ID field to specify the terminal to receive the breakpoint displays. Valid entries\nare:\nterminal ID\nDisplays breakpoints at the specified terminal.\n*\nDisplays breakpoints at the terminal displaying this profile screen.\n.ANY\nFor transactions executing at a 3270-type terminal, the breakpoint displays on the executing terminal.\n.NO\nIf the transaction runs as a background task without a terminal, the transaction abends with an INTE abend when\nthe first breakpoint is displayed.\nThe breakpointed task abends with an INTE abend when the first breakpoint is displayed.\n3.Press Enter to process the new BKPT Terminal ID setting and to return to the Source Listing Display.\nSet the User ID\nInterTest for CICS monitoring is sensitive to user IDs. Monitor programs and set breakpoints and other monitoring options\nwith the user ID set to .ANY, or the user ID set to a specific CICS user ID (in a secure CICS region). When the user ID is\nset to .ANY, everyone is monitored and the breakpoints and other monitoring options that you set take effect only if the\nprogram executes from the terminal used to set the breakpoints. When the user ID is set to a specific user ID, only that", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "042312ad1f7b-1", "text": "user is monitored, and the breakpoints and other monitoring options are directed to wherever the specified user is logged\nonto CICS.\nUser ID=\nThe default is either the current CICS user, or .ANY. To change the default, perform the following steps:\n1.Type profile  on the command line and press Enter, or press PF4 from the Source Listing display, to access the Source\nListing Profile screen.\n2.Overtype the entry in the User ID field to specify the CICS user who must execute the program for monitoring and\nbreakpoints to take effect. Valid entries are:\nspecific user-ID\nMonitoring and breakpoints take effect only when the specific CICS user executes the program.This establishes a\npersonal debugging session for the CICS user and directs breakpoints to the terminal on which the user is signed\non.\n.ANY\nMonitoring and breakpoints take effect when anyone executes the program.\n3.Press Enter to process the new user ID setting and to return to the Source Listing Display.\nNOTE\nIf you override the default user ID setting, check the Profile before each Source Listing Session and before you\nset additional breakpoints during a test session.\n 967", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e941c35c5b67-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSet the Keep Window to Display Variables in Current Statement\nAUTOKEEP lets you display items in the Keep window concerning the currently highlighted statement.\nThe initial setting for AUTOKEEP is chosen when InterTest for CICS is installed. If the IN25OPTS parameter SLBAKEEP\nis set to yes, which is the default, AUTOKEEP will be active. However, use the Profile screen to turn AUTOKEEP off or on\nagain at any time.\nAutoKeep Display=\nTo change the setting for AUTOKEEP, perform the following steps:\n1.Type profile  on the command line and press Enter, or press PF4 to access the Profile screen from any Source Listing\nScreen. The AutoKeep Display = field shows the current setting.\n2.Overtype the current value with one of the following:\nYES\nDisplays in the Keep window, the variables being manipulated in the current statement, along with any data items\nyou requested.\nNO\nDisplays in the Keep window only the data items you requested.\n3.Press Enter to process the new setting and to return to the Source Listing Display screen.\nSet Code Coverage\nCode Coverage (Counts) lets you see the number of times a verb was executed.\nThe initial setting for Code Counting is off, which is the default. However, use the Profile screen to turn Code Coverage off\nor on again at any time.\nHow the counts are displayed or not displayed is handled by the primary line command COUNTS with its associated\nparameters.\nThis feature, due to its nature, causes overhead during monitoring and should be turned off as soon as it is no longer\nneeded.\nCode Counting=\nTo change the setting for Code Coverage, perform the following steps:\n1.Type profile  on the command line and press Enter, or press PF4 to access the Profile screen from any Source Listing", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e941c35c5b67-1", "text": "Screen. The Code Counting= field shows the current setting.\n2.Overtype the current value with one of the following:\nYES\nEnables code counting and turns on the COUNTER display feature.\nNO\nRemoves the COUNTER display and stops the counting feature.\n3.Press Enter to process the new setting and to return to the Source Listing Display screen.\nSet Structure Display Form\nSDF defaults to the value set in the IN25OPTS macro, a value of HEX displays structured data in dump format and a\nvalue of DATA displays structured data in display format.\nTo change the current structure display format type profile on the command line and press Enter, or press PF4 to access\nthe Profile screen from the Source Listing Screen. The SDF = field shows the current setting.\n 968", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "95ce5f21150d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTesting Activities\nThis section discusses testing activities for monitoring users.\nSet Monitoring\nA CICS user ID is assigned to all monitoring requests. Depending on how InterTest for CICS was installed at your site, the\ndefault may be to set monitoring for .ANY  user, or to set monitoring for a specific CICS user. The following topics discuss\nhow these settings affect your test session.\nAs long as you are working in a secure CICS region, you can override the default user ID setting using the Profile display.\nYou should check how the user ID is set prior to setting breakpoints or monitoring for a program.\nMonitor with User ID=.ANY\nSetting monitoring with a user ID of .ANY  is the same as monitoring in earlier CICS releases: the program is monitored\nwhen ANY user executes the program, and breakpoints are displayed by default on the same terminal where they were\nset.\nMonitor with a Specific User ID\nWhen you set monitoring for a program with a specific user ID, InterTest for CICS only monitors the program when it is\nexecuted by that user. In addition, breakpoints display at whatever terminal that user is signed on to. Of course, this option\nrequires a secure CICS region and the user to be signed on to CICS when testing the program.\nMonitoring with your specific user ID has the following advantages over monitoring with user ID=.ANY:\n\u2022You can change terminals and your breakpoints and monitoring options will follow you\n\u2022Your testing will not interfere with any one else testing the same program\n\u2022You can use a multi-session terminal emulator package and have breakpoints directed to whatever terminal session\nyou are using\nView and Set the User ID\nTo view or set the user ID that will be used for monitoring and breakpoints, access the Source Listing Profile. To access", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "95ce5f21150d-1", "text": "the Profile, either enter PROFILE  on the command line and press Enter, or press PF4. The User ID field is at the bottom\nof the Profile. To change its value, delete the current entry, type in the new entry, and press Enter .\nAlso check the Terminal ID field just above the User ID field. Generally, you want Terminal ID set to .ANY when User ID is\nspecific , and Terminal ID set to a specific terminal ID when User ID is .ANY.\nSet Monitoring for a Displayed Program\nTo set monitoring for the program you are viewing, enter MONITOR in the command line, or press PF5. InterTest for CICS\nprocesses the request immediately using the user ID value currently set in the Source Listing Profile.\nNOTE\nIf you are going to set any breakpoints, skip this step; setting a breakpoint automatically sets monitoring for the\nprogram.\nMonitoring Multiple Programs\nIf you plan to test more than one program, you need to set monitoring and breakpoints for each program. If a program to\nbe tested passes control to another program using XCTL or LINK, you also must set monitoring for the receiving program.\nTo display another program, overtype the program name in the Program= field. Specify where you want to begin the\nprogram's display by using the Option #, Stmt #, and Search = or Assembler Displacement fields. Press Enter to process\nyour request. For details, Change the Program and Position the Display.\n 969", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f85229224313-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWith the new program displayed, repeat the steps to set monitoring and breakpoints.\nDisplay and Search Through Nested Programs\nInterTest for CICS provides support for COBOL nested programs.\nCOBOL nested programs let non-unique paragraph and data names to be defined across nested programs. Therefore,\nInterTest for CICS supports qualified  names for COBOL programs. A qualified name consists of a one- to 30-byte COBOL\nprogram name, a colon, and a one- to 30-byte paragraph or data name.\nExample\nprogram1:datanam1 is a qualified name. Qualified names ensure that the correct version of datanam1, which you define\nin multiple programs, is displayed. Qualified names are supported by the Source Listing facility, the Breakpoint facility,\nCNTL commands and menus, and by the Indirect Commands facility.\nWhen InterTest for CICS displays the source code for a nested program, the Nested= field appears below the Program=\nfield. The Nested= field is 30 bytes long, and indicates the name of the nested program for the currently displayed source\ncode. If you are using the Source Listing facility to display a COBOL nested program and you press PF8 to scroll through\nthe entire source code of the program, the Nested= field changes each time the source code for a different nested\nprogram is displayed.\nThe names of all nested programs within a specific COBOL program are listed at the end of the Procedure Name Cross\nReference section (Option  # 7).\n    CA InterTest for CICS - PROTDEM FILE SOURCE LISTING DISPLAY\nCOMMAND ===>                                                                    \nProgram= ACME2000 Option #       Stmt #                             Margin= 01  \n Nested=                                Search=", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f85229224313-1", "text": "Nested=                                Search=                                 \nOPTS 1 Proc div  2 Work-stor 3 Link sect 4 D-map      5 Clst/Pmap More:   + \n     6 Data xref 7 Proc xref 8 Err msgs  9 Srch fwd  10 Srch bwd  PFKS        \n     1 Help      2           3 End       4 Profile    5 Monitor   6 Menu      \n     7 Backward  8 Forward   9 Next Wnd 10           11           12 Status   \n---------+------------------------------------------------------------------\n _ DEFINED      PROCEDURE NAMES         REFERENCES                              \n _   122 3000REGISTERHANDLER          P107                                    \n _   131 4000FORCEABEND               P108                                    \n _   139 5000HANDLEROUTINE            D129                                    \n _   152 9000RETURN                    P109                                    \n _   168 9999GOBACK                                                            \n _   227 9999GOBACK                    P221                                    \n DEFINED   CROSSREFERENCE OF PROGRAMS     REFERENCES                           \nEXTERNAL   ACME200A . . . . . . . . . . . 120                                  \n     171   ACME200N . . . . . . . . . . . 229 114                              \n       2   ACME2000 . . . . . . . . . . . 230                                  \nEXTERNAL   ACME2001 . . . . . . . . . . . 117                                  \nEXTERNAL   DFHEI1 . . . . . . . . . . . . 127 137 147 160 166                  \nNESTED PROGRAM MAP                                                              \nPROGRAM ATTRIBUTE CODES (RIGHTMOST COLUMN) HAVE THE FOLLOWING MEANINGS:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f85229224313-2", "text": "PROGRAM ATTRIBUTE CODES (RIGHTMOST COLUMN) HAVE THE FOLLOWING MEANINGS:\nThe Nested= field also indicates the nested program to which Option # 1, 2, 3, and 13 apply, and the nested program\nthat InterTest for CICS searches first for any data name or paragraph name that you specify in the Search= field. If a\nparagraph name or data name is not found in the specified nested program, InterTest for CICS then searches the main\nprogram.\nExample\n 970", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c8808061ee24-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIf Option # 2 and Nested=program2 are specified, the Working Storage section for nested program program2 appears.\nAlso, if Nested=program3 and Search=datanam1are specified, nested program program3 is searched first for datanam1; if\ndatanam1 is not found, the main program is searched for datanam1.\nMaintain Synchronized Processing\nWhen InterTest for CICS searches the symbolic files for the COBOL and PL/I programs that you specify, it tries to match\nthe date and time in the symbolic file to that of the load module. If a match is not found, either a Symbolic Version List or a\nwarning message displays.\nWhen InterTest for CICS searches the symbolic files for the Assembler programs you specified, the Symbolic Version List\ndisplays if multiple symbolic versions of a program are found.\nCOBOL and PL/I Symbolic Version Processing\nWhen you use LIST= program , ITST, or CNTL to request a COBOL or PL/I program that has no previously declared\nbreakpoints or monitoring options set, InterTest for CICS matches the date and time of the most recently compiled\nversion of the program from the symbolic files to the load module date and time.\n\u2022If an exact match is found and there are no later versions, InterTest for CICS automatically selects that version of the\nlisting and displays it.\n\u2022If a match is not found, InterTest for CICS displays the Symbolic Version List from which you can either:\n\u2013Select the appropriate symbolic file and program version\n\u2013Ignore symbolic processing for the program\n\u2013The Symbolic Version List screen might also explain the cause of the mismatch. The following are possible causes\nfor the mismatch:\n\u2013There was no matching program listing for the load module.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c8808061ee24-1", "text": "for the mismatch:\n\u2013There was no matching program listing for the load module.\n\u2013A matching listing was found for the load module, but it is not the most recently compiled version. You can select the\nmatching listing at this point or new copy the load module so that it matches the most recently compiled version and\nthen retry the LIST or CNTL command.\nDuring Automatic Breakpoint processing, if a program has no previously selected symbolic file, InterTest for CICS will\nattempt to match the load module's date and time to a symbolic file program listing.\n\u2022If an exact match is found, InterTest for CICS automatically selects and displays it.\n\u2022If a match is not found, InterTest for CICS displays the Symbolic Version List from which you can choose a non-\nmatching program listing version or ignore symbolic processing for the program.\nOnce a symbolic file is selected for a program, InterTest for CICS continues to use the selected file and program version.\nIf a new version of the program is compiled and linked and you have one or more breakpoints set by Statement # or\nOffset, then you should deactivate monitoring for the program, new copy the program , and then reset any Statement\n# or Offset breakpoints. This will insure that your breakpoints are in sync with the new program version. Alternatively, if\nyou do not have any breakpoints set or only breakpoints set by paragraph-name, you can execute a CNTL=NEW,PROG=\ncommand or ITST Option 2.1 NEWCOPY, which will reset monitoring for the new program version.\nFor PL/I Programs\nSuccessful date and time matching for PL/I modules requires that PL/I programs be compiled using the default\nTSTAMP=YES option.\nAssembler Symbolic Version Processing\nAssembler programs have no internal date and time generated by the compiler, which prevents date and time matching.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c8808061ee24-2", "text": "Assembler programs have no internal date and time generated by the compiler, which prevents date and time matching.\nHowever, when LIST=program  or CNTL=ON,PROG= program  is requested for an Assembler program with multiple\nsymbolic versions of the listing and no previously declared breakpoints or monitoring options, InterTest for CICS displays a\n 971", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "789f4a735fac-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSymbolic Version List from which you select the appropriate symbolic file and listing version or ignore symbolic processing\nfor the program.\nOnce a symbolic file and program version is selected for an Assembler program, InterTest for CICS continues to use\nthe selected file and program version. If a new version of the program is compiled and linked and you have one or more\nbreakpoints set by Statement # or Offset , then you should deactivate monitoring for the program, new copy the program ,\nand then reset any Statement # or Offset breakpoints. This will insure that your breakpoints are in sync with the new\nprogram version. Alternatively, if you do not have any breakpoints set or only breakpoints set by paragraph-name, you can\nexecute a CNTL=NEW,PROG= command or ITST Option 2.1 NEWCOPY, which will reset monitoring for the new program\nversion.\nThe Symbolic Version List\nThe Symbolic Version List lets you select the appropriate symbolic file or exit InterTest for CICS and find out why a date\nand time mismatch occurred.\n\u2022To select a symbolic File ID, place an S next to the File ID.\n\u2022To exit InterTest for CICS without viewing any symbolic file, press PF3.\n\u2022To see why a mismatch occurred, consult the Comment column.\nThe following screen shows a sample Symbolic Version List that appears when the LIST or CNTL transactions cannot\ndetermine which symbolic file to use.\n        CA InterTest for CICS - Symbolic Version List\n                                                                               \n Program = COBDEMO   Load Module Date and time =  07/07/94   9.44.13   \n   Loadlib = COBDEMO.loadlib                               Volume = volser   \n                                          \n   File ID    Date      Time    Language     Comments", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "789f4a735fac-1", "text": "File ID    Date      Time    Language     Comments                           \n _ PROTDEM  07/24/94  11.44.13  COBOL      Latest Version                       \n _ PROTTST  07/24/94  10.59.00  COBOL      Update Mode\n _ PROTACC  07/23/94  12.52.00  COBOL \n _ PROTPRO  07/23/94  10.01.00  COBOL \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n        S  Select which Symbolic file to use for program display               \n----------------------------------------------------------------------- \n \u2019\n PFKEYS:  1 Help      2           3 No File   4           5           6         \n          7           8           9          10          11          12         \n \u201cCAIN8000 The latest Symbolic version does not match the current load module \nThis screen shows the following information:\n\u2022Specifies the name of the program being processed.\n\u2022Displays the internal date and time from the COBOL or PL/I load module. This field is not displayed for Assembler\nprograms or for PL/I programs compiled with a compiler that was installed with the TSTAMP=NO installation option.\n\u2022Displays the names of each version of the symbolic file containing a copy of the specified program.\n\u2022Lists dates and times that each version of the symbolic file was compiled.\n\u2022Displays the language of the compiled program.\n\u2022Displays information about the version listed in the File ID column, and also explains the reason for the date and time\nmismatch. Comments include:\n 972", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "abb3cbd19dfb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUpdate Mode\nSpecifies the program is being updated by the batch post-compiler utility. It could also mean that the PROTSYM\nran out of space while a post-compiler was processing this program.\nDate and time Match\nSpecifies the program compile date and time matches the load module date and time, but it is not the most\nrecently compiled version of the program.\nLatest Version\nSpecifies the program compile date and time is the most recently compiled version of the program, but it does not\nmatch the load module date and time.\n\u2022Lists the PF keys available from this screen.\n\u2022PF1\nAccesses the Help facility.\nPF3\nExit the Symbolic Version List and ignore symbolic processing.\nSet Breakpoints\nA breakpoint halts execution of your program. InterTest for CICS halts the program before the instruction at a breakpoint\nlocation is executed.\nThe following table shows the types of breakpoints that you can set in a program:\nBreakpoint Action\nUnconditional Stops at a specified program location.\nConditional Stops at a specified program location when a specified condition is\nmet.\nVariable-change Stops when the value of a specified variable changes; for\nCOBOL and Assembler only.\nRequest Stops at a CICS command or at calls to software.\nSet breakpoints from the Source Listing Display prior to program execution, from any breakpoint during program\nexecution, or from the Monitoring menus at any time.\nRemove Breakpoints\nRemove user breakpoints as quickly as they were set. In addition to the previously supported methods of removing\nbreakpoints, use the Monitoring Status display to quickly remove any type of breakpoint.\nRemove automatic breakpoints only if the error is corrected. However, you can go around the error and begin execution\nfrom another point.\nStatement Tracing", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "abb3cbd19dfb-1", "text": "from another point.\nStatement Tracing\nStatement tracing causes InterTest for CICS to add entries to the statement trace table for each executed statement.\nThen view the executed statements at any breakpoint by stepping backward and forward through the trace table entries\nusing the PREV and ADVANCE commands. Statement tracing is only valid for COBOL programs and is unrelated to the\nbacktrace facility.\nSet statement tracing from the Source Listing Display prior to program execution, from any breakpoint during program\nexecution, or from the Monitoring menus at any time. Remove statement tracing using one of those methods. In addition,\nuse the Monitoring Status display to quickly remove statement tracing.\n 973", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fe7b0cb4e3b4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nData Monitoring\nData monitoring causes InterTest for CICS to capture data values for each statement executed in a program. The\ncaptured data values are associated with an entry in the statement trace table. Redisplay them at any breakpoint\nby stepping backward and forward through the trace table entries using the PREV and ADVANCE commands. Data\nmonitoring requires that statement tracing be active and is only valid for COBOL programs.\nSet or remove data monitoring from the Source Listing Display prior to program execution, from any breakpoint during\nprogram execution, or from the Monitoring menus at any time.\nRun Your Program\nAfter setting monitoring and breakpoints for each program you want to test, you are ready to begin testing. To begin\ntesting, perform the following steps:\n1.Exit the Source Listing facility by pressing PF3 or Clear . If you accessed an InterTest for CICS screen outside the\nSource Listing facility, you might have to press Clear  more than once to return to CICS. InterTest for CICS responds\nwith the message:\n    Lister Function Terminated.\n2.Initiate the program as you normally would from CICS. Depending on the breakpoints you set and the processing\npaths your program takes, one of the following occurs:\n\u2013InterTest for CICS stops the transaction at a breakpoint (either one you set or one InterTest for CICS automatically\ntriggered) because the program was about to violate a CICS coding standard.\n\u2013The application runs to completion without being stopped by InterTest for CICS. The results might not be correct.\nNOTE\nIf the program ends and you get incorrect results or need to test other logic paths, initiate LIST again and set\nadditional breakpoints before retesting the program. You do not have to reset monitoring -- it remains in effect\nuntil specifically removed.\nExit the Source Listing Facility", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fe7b0cb4e3b4-1", "text": "until specifically removed.\nExit the Source Listing Facility\nType END  on the command line and press Enter to exit the Source Listing Facility or exit the menus using =X.\nUsing Breakpoints\nThese topics explain how to use the Source Listing facility and the menus to set and remove breakpoints in your\nprograms. The following bullets show the user-breakpoint types:\n\u2022Unconditional\n\u2022Conditional\n\u2022Variable-change\n\u2022Request breakpoints\nThe first topics describe how to set each type breakpoint type, giving alternative methods from the Source Listing and the\nmenus. The later topics discuss how to remove the breakpoints.\nSet Breakpoints\nA breakpoint halts execution of your program. InterTest for CICS halts the program at a breakpoint location before the\ninstruction executes.\nThe following bullets show the types of breakpoints that you can set in a program:\nUnconditional\nStops at a specified program location.\n 974", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "56474f55bcb5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nConditional\nStops at a specified program location when a specified condition is met.\nVariable-change\nStops when the value of a specified variable changes.\nRequest\nStops at a CICS command or at calls to software.\nSetting a breakpoint automatically sets monitoring for that program, so if you are setting a breakpoint before you execute\na program, you do not need to set monitoring for the program.\nWhere Should You Set Breakpoints?\nSet breakpoints to control program execution and to pinpoint errors in logic.At a breakpoint, use InterTest for CICS to do\nthe following tasks:\n\u2022Set additional breakpoints\n\u2022Execute line-by-line (single step)\n\u2022Examine or change the program path\n\u2022Display or change main storage\n\u2022Code and execute indirect commands\n\u2022Display or change auxiliary files\nWhen Should You Set Breakpoints?\nSet breakpoints before program execution or whenever the program stops at a breakpoint during execution. You do\nnot have to set all breakpoints in advance. Set one, start executing, and then set more when you reach a breakpoint.\nTo review your breakpoints or remove them, use the Status Display (PF12) at any time: before execution, from any\nbreakpoint, or after your session.\nWhy Should You Set Breakpoints?\nYou might want to set a breakpoint at the first statement in the COBOL\nProcedure Division, the Assembler CSECT, or PL/I program. This gives you the opportunity to set the execution pace and\nto determine the program path that you want to take during testing. If program control is passed from another program,\nexamine the COMMAREA at this point.\nOften, breakpoints are set at the following locations for debugging purposes:\n\u2022At paragraph names to examine variables at the start of the sections\n\u2022Before a branch to dynamically control the program path during execution", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "56474f55bcb5-1", "text": "\u2022Before a branch to dynamically control the program path during execution\n\u2022At each location named in an EXEC CICS HANDLE CONDITION to verify error handling\nAn easy way to track data items during testing is to set a variable-change breakpoint on troublesome data, and then add\nthe data item to a Keep window.During program execution, the program stops each time the variable\u2019s value changes, and\nits value displays at the top of your screen in the Keep window.\nUnconditional Breakpoints\nThese topics review setting unconditional breakpoints from the Source Listing and from the menus.\nSet Unconditional Breakpoints from the Source Listing\nWhile you are viewing your source listing (either before execution or during a breakpoint), set unconditional breakpoints\ndirectly in your program code, or indirectly from the Procedure Names and Cross-Reference sections of the output.\n 975", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "83b416d056b3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo set an unconditional breakpoint from a Source Listing or Breakpoint screen, follow these steps:\n1.Enter u or ) in position 1 of the line in the program listing where you want the breakpoint set, but do not press Enter.\n(You can add more than one breakpoint at a time). A \"u\" stops execution before  the selected item. A \")\" stops\nexecution after the selected item.\nYou can add a breakpoint next to the following items.\n\u2013A line of executable code\n\u2013A COBOL paragraph name\n\u2013An Assembler label\n\u2013A PL/I label\nA breakpoint set at a paragraph name or label occurs before (or after) execution of the first verb or instruction in the\nparagraph.\n2.Optionally, and before pressing Enter, use the Option # field and enter 12 (Bkpt Options) to access the menu for\nspecifying breakpoint options to your unconditional breakpoints. These options let you specify:\n\u2013If the program should stop at this breakpoint before statement execution (default) or after statement execution\n\u2013How often the program should stop at this breakpoint (every nth time, instead of every time)\n\u2013The terminal where breakpoints take effect\n\u2013The terminal that receives the breakpoints\n\u2013Indirect commands statement numbers to execute at this breakpoint\n\u2013The user ID (or .ANY) that executes the program\n3.Press Enter  to set the breakpoints. InterTest for CICS flags each unconditional breakpoint with a U or a ).\nIf you used Option # 12 to set Breakpoint Options, the Breakpoint Locations Menu appears. Using this menu specify\nyour options for the breakpoint. Complete the menu. For more information, see Specify Breakpoint Options. After\ncompleting this menu, press Enter to set the breakpoint and return to the Source Listing display or breakpoint.\nThe following sample screen shows how to set unconditional breakpoints.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "83b416d056b3-1", "text": "The following sample screen shows how to set unconditional breakpoints.\n   CA InterTest for CICS  - PROTSYM FILE SOURCE LISTING DISPLAY    \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \nOPTS 1 Proc div  2 Work-stor 3 Link sect 4 D-map      5 Clst/Pmap More:   + \n     6 Data xref 7 Proc xref 8 Err msgs  9 Srch fwd  10 Srch bwd            \nPFKS 1 Help      2           3 Det Bkpt  4 Profile    5 Resume     6 Menu      \n     7 Backward  8 Forward   9 Next Wnd 10 001 Verb  11 Backtrace 12 Status    \n------------------------------------------------------------------------------- \n _ 01205     PERFORM CICS-LOOP 50 TIMES.                                       \n _ 01206     GO TO MXS-OPTION.                                                 \n u 01207 CICS-LOOP.                                                            \n   01208*EXEC CICS ASKTIME                                                      \n   01209*          END-EXEC.                                                   \n _ 01210      MOVE '         00849   ' TO DFHEIV0                               \n u 01211     CALL 'DFHEI1' USING DFHEIV0.                                      \n   01212                                                                        \n u 01213 MXS-OPTION.                                                           \n _ 01214     IF  TASK-SWITCH3 EQUAL SPACE                                       \n _ 01215         MOVE 'A' TO TASK-SWITCH3                                       \n _ 01216         MOVE 'DMAP06' TO MAPNAME                                       \n _ 01217         GO TO SEND-REWRITE-RETURN.                                    \n   01218*EXEC CICS HANDLE CONDITION     \n   01219*          NOSTG(NO-STORAGE)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "83b416d056b3-2", "text": "01219*          NOSTG(NO-STORAGE)  \n 976", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "83cf6ba4eca0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nIf you want to recompile your program and keep the same breakpoints in the recompiled version, set breakpoints\nnext to paragraph names or labels, not lines of executable code. Then, use the InterTest for CICS New Program\nCopy function, explained in Monitoring Menu Options, to transfer the breakpoints to the same paragraph names\nor labels in the recompiled program. If you set breakpoints at lines of executable code, New Program Copy\ntransfers the breakpoints to the same statement numbers  or offsets   in the recompiled program, which might not\nbe what you want.\nIf you compiled or assembled your program with the post-processor parameter value, LISTER=ALL, you can set\nunconditional breakpoints using the Cross-Reference section. This method sets breakpoints at all references to the\nselected data name. To use this method, follow these steps:\n1.Display the Cross-Reference section using the Option # field.\n2.Enter u or ) in column 1 next to the data name.\n3.Press Enter to set the breakpoints. InterTest for CICS sets the breakpoints at all references to the COBOL, Assembler,\nor PL/I data name. Then, InterTest for CICS displays the  breakpoint indicators in the Cross-Reference section and on\nthe lines in the Procedure Division or CSECT where the data name is referenced.\nTo set breakpoints at specific paragraph names, labels, or procedure names, follow these steps:\n1.Display the Cross-Reference section using the Option # field. For more information, see Source Listing Facility for\nInterTest.\n2.Enter a u  or ) next to the:\n\u2013Specific paragraph name, label, or procedure name in the COBOL Cross-Reference listing\n\u2013Symbol line in the Cross-Reference section of the Assembler listing", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "83cf6ba4eca0-1", "text": "\u2013Symbol line in the Cross-Reference section of the Assembler listing\n\u2013Specific label or procedure name in the Xref section of the PL/I listing\n3.Press Enter. The breakpoints apply to the specific paragraph names, labels, or procedure names.\nThe following screen shows how to set breakpoints at Procedure Names.\n  CA InterTest for CICS  - PROTSYM FILE SOURCE LISTING DISPLAY    \nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \nOPTS 1 Proc div  2 Work-stor 3 Link sect 4 D-map      5 Clst/Pmap More:   + \n     6 Data xref 7 Proc xref 8 Err msgs  9 Srch fwd  10 Srch bwd            \nPFKS 1 Help      2           3 End       4 Profile    5 Monitor    6 Menu      \n     7 Backward  8 Forward   9 Next Wnd 10           11           12 Status    \n------------------------------------------------------------------------------- \n _ PROCEDURE NAMES                 DEFN     REFERENCE                           \n u AFTER-REWRITE                   01328                                        \n _ CICS-LOOP                       01207  01205                                 \n _ CONTINUE-TASK                   00895  00824 00888                           \n _ DATA-NAME                       01080                                        \n u DO-READ-VAR                     01099  01096                                 \n _ EXPANDED-DEMO                   00971  00821 00892 00893                     \n _ GEN-ERR                         01289  00802 00854 01047                     \n _ LAST-SCREEN                     00954  00947                                 \n _ LINK-COBDEML                    01381  01372                                 \n u LOOP-RTN                        01204", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "83cf6ba4eca0-2", "text": "u LOOP-RTN                        01204                                        \n _ MOVE-RECORD                     01148                                        \n _ MXR-OPTION                      01199  01372\nTo set breakpoints at all paragraph names, labels, or procedure names, follow these steps:\n1.Display the Procedure Names section using the Option # field.\n 977", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3ecb44c3c29a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n2.Enter a u  or ) next to the:\n\u2013Procedure-Names line in the COBOL Cross-Reference listing\n\u2013Symbol line in the Cross-Reference section of the Assembler listing\n\u2013Declare line in the Xref section of the PL/I listing\n3.Press Enter .\n4.When prompted, press PF3 to confirm the request for multiple breakpoints. The breakpoints apply to all paragraph\nnames, labels, or PL/I procedures.\nSet Unconditional Breakpoints from the Menus\nYou can set all types of breakpoints from the Monitoring submenus of the Primary Option Menu.\nTo set one or more unconditional breakpoints from the menus, follow these steps:\n1.Access the Primary Option Menu, and select Option  2 Monitoring .\n2.If you already set monitoring for the program, transaction, or terminal, repeat the entry that duplicates the monitoring\nrequest. Check this by viewing the Monitoring Status display. In most cases, this is Option 1 Program .\nIf you have not set monitoring, select whether you want to monitor a program (option 1), transaction (option 2), or\nterminal (option 3). Most users monitor the program.\n3.On the Program, Transaction, or Terminal Monitoring Menu:\n\u2013Complete the top part of the Monitoring menu to specify (or duplicate) how the program, terminal, or transaction will\nbe monitored.\n\u2013Complete the bottom part of the menu by entering s next to the UBP option for Unconditional Breakpoints.\n\u2013Press Enter to process your request.\nSpecify Breakpoint Locations\nTo set breakpoint locations, complete the fields on the Breakpoint Locations panel as follows:\n\u2022For a COBOL program, you can specify a paragraph name or data name, a statement number, or the hexadecimal\ndisplacement (offset) from the beginning of the program.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3ecb44c3c29a-1", "text": "displacement (offset) from the beginning of the program.\n\u2022For an Assembler program, breakpoint locations can be Assembler labels, data names, or offsets.\n\u2022For a PL/I program, breakpoint locations can be offsets or, if you have the PL/I symbolic option, PL/I labels or\nstatement numbers. PL/I labels can be qualified by Procedure Name using the syntax: Procedure-Name:Label.\nUse the following rules when specifying information:\n\u2022If you specify statement # 1, InterTest for CICS sets a breakpoint at the first executable instruction in a COBOL\nProcedure Division, Assembler CSECT, or PL/I procedure.\n\u2022COBOL statements can contain more than one verb. In specifying statement numbers, indicate the verb at which the\nbreakpoint should occur. A statement number of nnn or nnn indicates the first verb in the statement, nnn.1 indicates\nthe second verb, nnn.2 indicates the third verb, and so on. For example, a statement number entered as 503.3\nspecifies a breakpoint at the fourth verb in statement number 503.\n\u2022If you specify a COBOL, Assembler, or PL/I data name, breakpoints are set at every reference to that data name.\n\u2022Enter an X in the All paragraph names field (COBOL), All Assembler labels field, All Labels field (PL/I), or All\nProcedure Names field (PL/I) to set breakpoints at all of the indicated locations.\n\u2022Enter an X in the After field to stop after the statement executes.\nNOTE\nYou can specify up to nine breakpoints.\nSpecify Breakpoint Options\nThe following specifications are optional:\n 978", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "feede445224d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nEnter 'n' to stop only every n'th time\nSpecifies how often the program should be halted when you set a breakpoint within a loop.\nTerm ID (or .ANY or .NO) where breakpoints will take effect\nSpecifies ID of the terminal where the program must be executing for breakpoints to take effect. If you leave this\nfield blank, it defaults to your current terminal. Enter . ANY  to have breakpoints take effect at all terminals, even\nwhen the program executes without a terminal. Enter . NO to have breakpoints take effect only when the program\nexecutes without a terminal.\nTerm ID (or .ANY) that will receive the breakpoints\nSpecifies the ID of the terminal to receive breakpoint displays. If you leave this field blank, it defaults to your\ncurrent terminal. Enter . ANY  to have breakpoint screens displayed at the terminal where the program is executing\nwhen the breakpoints occur.\nStatement no. of indirect command(s) to be executed\nSpecifies the statement number of the indirect command that you want to invoke at the breakpoint you have set.\nUser ID (or .ANY) who will execute the program\nSpecifies the CICS ID of the user who must execute the program for the breakpoint to take effect. Valid entries are\na specific CICS user ID or .ANY . The default varies depending on your installation option settings for DFLTUSER.\nExample\nThe following example shows how to set unconditional breakpoints at four locations in the COBOL program COBDEMO.\n      CA InterTest MONITORING COMMAND BUILDER   COBOL BREAKPOINT LOCATIONS  11 \n \n    SET breakpoint locations for PROG=COBDEMO  in any of the following fields:   \n                           \u2193                        \n  Para/Data return-transid_________________      ______________________________\n     Names: _______________________________      ______________________________\n            _______________________________      ______________________________", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "feede445224d-1", "text": "Names: _______________________________      ______________________________\n            _______________________________      ______________________________\n  Statement  \u2193         \u2193         \u2193                         \n   Numbers: 1____    136__    174.2    _____    _____    _____    _____    _____ \n \n   Offsets: _____    _____    _____    _____    _____    _____    _____    ____\n \n            All paragraph names:  _                                    After:_\n \n            Enter 'n' to stop only every n'th time:                         ___\n            Term ID (or .ANY or .NO) where breakpoints will take effect:    ___\n            Term ID (or .ANY) that will receive the breakpoints:            ___\n            Statement no. of indirect command(s) to be executed:                \n            user ID (or .ANY) who will execute the program: BARNEY1\n \n \n \n PF1 Help       2            3 End        4 Return     5            6          \n PF7            8            9           10           11           12\nThe information in the previous example causes breakpoints to occur at:\n\u2022Paragraph RETURN-TRANSID\n\u2022Statement 1, the beginning of the Procedure Division\n\u2022The first verb in statement 136\n\u2022The third verb in statement 174\n 979", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1f14c1ea8ab4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBecause the user ID field is specified as BARNEY1 and the terminal identification fields are left blank, these breakpoints\ntake effect only if COBDEMO is executed by the user ID BARNEY1. The breakpoints display at whatever terminal\nBARNEY1 is signed on under CICS.\nConditional Breakpoints\nThis section reviews setting conditional breakpoints from the Source Listing and from the Menu.\nSet Conditional Breakpoints from the Source Listing\nTo set conditional breakpoints, specify the location and then the condition. Following these steps, specify one or more\nlocations directly from the Source Listing.\n1.Enter c in column 1 of any line in:\n\u2013Your program listing (next to a paragraph, label, or executable code)\n\u2013The Procedure Names section of the COBOL Cross-Reference listing (for all paragraphs or selected paragraphs)\n\u2013The Cross-Reference section of COBOL, Assembler, or PL/I programs (next to a data name, label, or all labels)\n\u2013If you enter  c next to a data name in the Cross-Reference section, the breakpoint takes effect at all locations where\nthe item is referenced.\n\u2013If you enter c next to the Procedure-Names line in the Procedure names section of the COBOL Cross-Reference\nlisting or next to the Symbol line in the Cross-Reference section of the Assembler listing, the breakpoints takes\neffect at all paragraph names or labels.\nNOTE\nYou can specify more than one c before pressing Enter.\n2.Optionally, select Option # 12  Breakpoint Options to set options for your conditional breakpoints.\n3.Press Enter .\nAnother way of specifying the same condition for multiple locations in your program is to use the ITST menus to specify\nboth the locations and the conditions.\nTo set conditional breakpoints that apply to multiple locations in a program, follow these steps:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1f14c1ea8ab4-1", "text": "To set conditional breakpoints that apply to multiple locations in a program, follow these steps:\n1.Enter a c in column 1 of each  line in your source code at which you want to set a conditional breakpoint.\n2.Press Enter. InterTest for CICS displays the first conditional breakpoint locations screen.\n3.Specify one or more conditional breakpoint locations. InterTest for CICS displays a Conditional Breakpoint menu.\nThe For Location  field indicates the statement number with the source code at which you specified c on the Source Listing\ndisplay. Typing an S in the drop monitoring on a true condition field causes monitoring to be dropped for the rest of the\ncurrent task when the conditional breakpoint is true.\nNOTE\nThe For Location field does not display when you specify the location using the menus.\nPress Enter  after completing the Conditional Breakpoint menu. InterTest for CICS sets the conditional breakpoints and\nreturns you to the Source Listing display.\nNotes:\n\u2022Conditional Breakpoint menus for Assembler and PL/I programs and the complex Conditional Breakpoint menu for\nCOBOL programs have additional entry fields.\n\u2022To replace an unconditional breakpoint with a conditional breakpoint, you must first remove the unconditional\nbreakpoint. Overtype the u or ) with x and press Enter. Then enter c at the same location, and press Enter.\n 980", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dee755d7cdc0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSet Conditional Breakpoints from the Menus\nConditional breakpoints are set from the same Monitoring submenus used to set monitoring and unconditional\nbreakpoints. Follow the same steps given in Set Conditional Breakpoints from the Menus. However, instead of entering s\nnext to the UBP option, enter s next to the CBP option for conditional breakpoints.\nSetting Conditional Breakpoints for COBDEMO, monitored for BARNEY1\nFirst, InterTest for CICS displays the Conditional Locations screen.\nThis screen is similar to the screen used to specify unconditional breakpoints, and you should enter the information in the\nsame way. For more information, see Set Unconditional Breakpoints from the Menus.\nOne special feature lets you set a conditional breakpoint at all instructions. Enter an  x in the All Instructions field to\nrequest this option, as shown in the previous example. If you request the All Instructions option and set a variable-change\nbreakpoint, the breakpoint takes effect whenever the value of the variable changes.\nAfter specifying the breakpoint locations, press Enter to display the Conditional Breakpoint screen. On this screen specify\nthe condition that must be satisfied for the breakpoint to take effect.\nThere are two versions of the Conditional Breakpoint screen: a simplified version for COBOL users, and a detailed version\nfor PL/I and Assembler users and for those COBOL users who prefer this version. Using either version you specify the\ncondition in this format:\nleft side relational operator right side\nVariable-Change Breakpoints\nCOBOL and Assembler users set a conditional breakpoint to take effect whenever the value of a variable changes. To do\nthis, type x in the All Instructions field on the Conditional Locations screen.\nCOBOL  users must specify the variable name on the Conditional Breakpoint screen. The condition for a variable-change\nbreakpoint is:\nvariableA NE variableB", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dee755d7cdc0-1", "text": "breakpoint is:\nvariableA NE variableB\nAssembler  users must specify the variable name on the Detailed Conditional Breakpoint screen. For more information,\nsee The Detailed Conditional Breakpoint Screen.\nThe specified operator determines whether the breakpoint occurs whenever the value of the variable changes (NE), or\nonly when the value increases, decreases, or does not change. Whenever you re-execute the program, the initial value of\nthe variable resets to its value at the beginning of program execution.\nLiteral Formats\nSpecify four types of literals for the right side of the comparison:\nCharacter\nSpecify character literals for comparisons with any field except a COBOL data name defined as COMP or\nCOMP-3. Enter the literal as C'character data' , X' hexadecimal data', or a combination of both. For example,\nC'ABC', Xv0102',or C'ABC'X'0102'.\nPacked\nSpecify packed decimal literals for comparisons only with COBOL data names defined as COMP-3. Enter the\nliteral as P'number'. The number can be preceded by a minus sign. For example, P'123' or P'-123'.\nHalfword\nSpecify halfword literals for comparisons with COBOL data names defined as COMP with a length of four, as in\nS9(4) COMP. Enter the literal as H'number'. The number can be preceded by a minus sign. For example, H'12' or\nH'-12'\n 981", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e50ed37cc931-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFullword\nSpecify fullword literals for comparisons with COBOL data items defined as COMP with a length of eight, as in\nS9(8) COMP. Enter the literal as F'num'100' or F' -100'.\nFigurative Constants\nSpecify the following figurative constants for the right side of the comparison:\nValid Right Side Specifications for the Comparison\nZERO\nZEROS\nZEROESnumeric value 0 HIGH-VALUE\nHIGH-VALUEScharacter value X' FF'\nSPACE\nSPACESblank (X'40') LOW-VALUE\nLOW-VALUEScharacter value X'00'\nExample\nThe following screen shows how to set a conditional breakpoint in a COBOL program:\n\u2022The left side of the comparison specifies the data name TOLEN.\n\u2022The relational operator is LT (less than).\n\u2022The right side of the comparison specifies the literal 80.\n           CA InterTest MONITORING COMMAND BUILDER  CONDITIONAL BREAKPOINT   \n \n   Enter LEFT SIDE    \u2193                                                    \n       Data Name tolen ________________________________________________________\n \n                                               \u2193\n   Enter OPERATOR (EQ, NE, GT, LT, GE, LE):  lt                               \n \n   Enter RIGHT SIDE                                                           \n       Data Name ______________________________________________________________\n          OR     \u2193                                                 \n       Literal 80______________________________________________________________\n \n  _ ENTER  S  to Drop monitoring on true condition                             \n \n          Press PF9 to go to complex conditional screen if necessary            \n \n \n \n  F1 Help       2            3 End        4 Return     5            6           \n PF7            8            9 Complex   10           11           12\nThis breakpoint takes effect only if the value in the data name TOLEN is less than 80. The breakpoint locations are all the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e50ed37cc931-1", "text": "instructions, as previously specified on the Conditional Locations screen.\nThe Detailed Conditional Breakpoint Screen\nAssembler and PL/I users who want to specify conditional breakpoints should complete the Conditional Locations screen\nand press Enter, the Conditional Breakpoint screen appears. COBOL users access this screen by pressing PF9 from the\nCOBOL Conditional Breakpoint screen.\n 982", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "77ae8fcad7f9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nEnter LEFT SIDE of condition\nSpecifies the left side of the comparison that must be an area of core. Enter information in one of the following\nfields:\n\u2022Data name\n\u2022Register\n\u2022COBOL BLL cell\n\u2022Area identified by a CORE keyword\nEnter OPERATOR\nSpecifies the relational operator:\n\u2022EQ for equal\n\u2022NE for not equal\n\u2022GT for greater than\n\u2022LT for less than\n\u2022GE for greater than or equal to\n\u2022LE for less than or equal to\nLength\nOptionally define the length of the left side or right side of the comparison. (For more information, see the Length\nof the Comparison.)\nEnter RIGHT SIDE of condition\nSpecifies the right side of the comparison, which is an area of core or a literal. Enter information in one of these\nfive fields: a data name, a register, a COBOL BLL cell, an area identified by a CORE keyword, or a literal. For\nmore information, see the section and see Literal Formats.\nOptional offset\nOptionally adjusts a CORE location by specifying offsets (displacements). Each offset must be preceded by one of\nthe following operands:\n\u2022+\n\u2022-\n\u2022@ - Indirect addressing below the 16-megabyte line\n\u2022% - Indirect addressing above the 16-megabyte line (XA systems only)\nNOTE\nLiterals cannot be modified by offsets.\nLength of the Comparison\nYou can explicitly define how many bytes of either the left side or right side specification should be compared. Certain\nstorage locations have implicit lengths:\n\u2022A register or COBOL BLL cell has an implicit length of four bytes.\n\u2022The storage locations referred to by the CORE keywords MXR, MXS, and TAL have implicit lengths of four bytes.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "77ae8fcad7f9-1", "text": "\u2022The implicit length of a COBOL data name is its field length as defined in the DMAP.\n\u2022The length of a literal is the number of bytes it contains; any length specification is ignored.\nDefine both left side and right side lengths for a packed decimal (COMP-3) comparison. For all other comparisons, define\nonly one length. If you define both lengths, the smaller length is used.\nThe maximum permissible length for the left side or right side is 16 bytes for packed decimal data, and 255 bytes for all\nother data types.\n 983", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "74f27c9a1b6e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nLiteral Formats\nFor more information about specifying literals, see Figurative Constants.\nCORE Keywords\nSpecify the following CORE keywords on the left side or right side of the comparison:\nCSA\nFirst byte of the CSA\nCURR\nNext Assembler instruction to be executed\nCWA\nFirst byte of the CWA\nCWK\nFirst byte of the COBOL program's Working-storage\nDSA\nFirst byte of program's DSA\nITBE\nFirst byte of the next instruction to be executed\nLCL\nFirst byte of the COBOL program's local-storage\nMXR\nInterTest for CICS maximum CICS request counter (implicit length = 4)\nMXS\nInterTest for CICS maximum storage counter (implicit length = 4)\nOPFL\nFirst byte of the Optional Features List\nPGM=*\nFirst byte of the monitored program.\nPREV\nLast Assembler instruction that was executed\nRnn\nA register ( nn is a decimal from 1 to 15) (implicit length = 4)\nTAL\nInterTest for CICS tally fullword (implicit length = 4)\nTERM=*\nFirst byte of the terminal table entry of the current terminal\nTGT\nFirst byte of the COBOL TGT for the monitored task\nTIOA\nFirst byte of the first TIOA of the task\nTWA\nFirst byte of the TWA of the monitored task\n 984", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ec5afe50929e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nVariable-Change Breakpoints\nA variable-change breakpoint is a special type of conditional breakpoint that takes effect when the value of a specified\nCOBOL or Assembler variable changes. If you set a variable-change breakpoint while the variable is also listed in the\nKeep window, the variable's new value immediately appears at the top of the breakpoint display when the breakpoint is\ntriggered.\nTo set a variable-change breakpoint from a Source Listing screen, follow these steps:\n1.Enter v in position 1 of any line in the program listing that defines or references the variable.\n2.If the statement references  the variable, place the cursor under any character in the variable name. (Omit this step if\nthe statement defines the variable.)\n3.Press Enter.\nTo set a variable-change breakpoint for a variable in the Keep window, follow these steps:\n1.Enter v next to the variable name in the Keep window.\n2.Press Enter.\nSet variable-change breakpoints before or during program execution. If you set the breakpoint before execution, the\nvariable's initial value is its value when it first becomes known to InterTest for CICS during execution. Any change from\nthis initial value triggers the variable-change breakpoint.\nSet Conditional Breakpoints from the Menus explains how to set variable-change breakpoints when the value of a variable\nincreases or decreases.\nRequest Breakpoints\nThis section reviews setting request breakpoints from the source listing and from the menus.\nSet Request Breakpoints from the Source Listing\nSet request breakpoints to halt a program prior to CICS commands and other program calls (such as calls to DL/I, DB2,\nor SQL/DS). Instruct InterTest for CICS to halt the program before every CICS command, or a type of CICS command,", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ec5afe50929e-1", "text": "such as File Control or Program Control commands. Specify that the program halts before specific commands, such as all\nREAD or WRITE commands. Once the program is halted, use all of the InterTest for CICS facilities to inspect and modify\nmain storage or auxiliary storage or to set additional options.\nSet request breakpoints easily from the source listing by entering the RBP command. Once set, request breakpoints are\nidentified by an R  during program execution. Set them also from the Monitoring menus and they are most easily removed\nfrom the Monitoring Status display (STATUS command).\nAfter completing the RBP menus, press PF4 Return  until InterTest for CICS returns you to the Source Listing display.\nSet Request Breakpoints from the Menus\nWhen viewing a program listing before or after a breakpoint, specify the RBP command to display the RBP menus.\nAlternatively use the Program Monitoring (2.1), Transaction Monitoring (2.2), or Terminal Monitoring (2.33) menu to set\nrequest breakpoints. Complete the top of the menu according to how you are monitoring or want to monitor the program,\nterminal, or transaction, and select the RBP option on the bottom of the menu. Detailed steps on how to do this are given\nnext for users unfamiliar with the monitoring menus.\n1.Access the Primary Option Menu, and select 2 Monitor  to access the Monitoring Menu.\n2.Select option 1 Program  to have the request breakpoints apply to a monitored program. Alternatively, select another\nmonitoring option if you are monitoring by Transaction (2) or Terminal (2).\n3.On the Monitoring submenu, complete the monitoring entry for the Program (Terminal or Transaction) and user ID, and\nthen type s next to the RBP Option for Request Breakpoints and press Enter .\n 985", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a5174cd37357-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAfter specifying the RBP command from the Source Listing screen or completing the monitoring menu with the RBP\noption selected, InterTest for CICS displays the Request Breakpoint Selection menu.\nOn this screen enter an x next to the options you want to select. You can specify any of the following breakpoints:\nALL commands\nThe program halts prior to all CICS commands.\nDL/I\nThe program halts prior to all DL/I calls.\nDB2\nThe program halts prior to all calls to DSNHLI (for DB2 users) or prior to all calls to ARIPRDI (for SQL/DS users).\nCALLS\nThe program is halted prior to calls to software that InterTest has been instructed to recognize at installation time.\nA second screen, where you specify the calls, displays.\nNOTE\nIf you select a type of CICS command, InterTest for CICS displays a second screen. For example, if you select\nFile Control, InterTest for CICS displays the File Control screen.\nWhen you have entered all of the necessary information, press Enter. If you entered an x next to a type of command,\nInterTest for CICS displays a second screen.\nExample\nIf you selected the File Control option, the Monitoring Command Builder Request Breakpoint Selection screen displays.\n     CA InterTest MONITORING COMMAND BUILDER   REQUEST BREAKPOINT SELECTION \n \n              Set  one or more types of File Control commands in:            \n                                  PROG=COBDEMO                               \n \n                _ All commands                                               \n \n                  \u2192  x READ                                                  \n                  \u2192  x WRITE                                                  \n                      _ REWRITE                                              \n                      _ DELETE                                                \n                      _ UNLOCK                                                \n                      _ STARTBR                                                \n                      _ READNEXT                                               \n                      _ READPREV                                               \n                      _ ENDBR", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a5174cd37357-1", "text": "_ READNEXT                                               \n                      _ READPREV                                               \n                      _ ENDBR                                                  \n                      _ RESETBR                                               \n \n                Enter 'n' to stop only every n'th time   ____                  \n \n \n PF1 Help       2            3 End        4 Return     5            6          \n PF7            8            9           10           11           12    \nUsing this screen specify that the program be halted at all File Control commands, or select specific File Control\ncommands. In this example, the user specified that program COBDEMO be halted at all READ and WRITE commands.\n 986", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5f08693b201c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nRemove Breakpoints\nThere are several ways to remove breakpoints. One of the easiest is to enter an R next to any breakpoint entry on the\nMonitoring Status display. This section discusses two other ways of removing breakpoints:\n\u2022From your Source Listing Breakpoint or Display\n\u2022From the Monitoring Menus (using STATUS command)\nRemove Breakpoints Flagged on Your Source Listing\nYou can remove breakpoints as quickly as you set them. Statements where you previously set unconditional breakpoints\nare flagged with a U or ) in column 1. Statements with conditional breakpoints are flagged with a C. During program\nexecution, locations where InterTest for CICS stops because of a variable-change or request breakpoint are flagged with\nV or R, respectively.\n\u2022To change the type of breakpoint at a given location, first remove the existing breakpoint, and then set the next one.\n\u2022Remove automatic breakpoints only if the error is corrected. However, you can go around the error and start execution\nfrom another point.\nThe following list explains how to remove each type of breakpoint.\nUnconditional, Conditional or Variable-change breakpoints\nWhile viewing the source at a breakpoint, type an x over the U, ), C, or V; press Enter.\nUnconditional or Conditional breakpoints set at all COBOL paragraph names, or Assembler or PL/I\nprocedures\nEither enter x to the left of the Procedure-Names or Symbol header line or Declare line in the Cross-Reference\nsection of the listing and press Enter, or type an R next to the UBP or CBP entry on the Monitoring Status display\nand press Enter.\nUnconditional or Conditional breakpoints set at all references to a COBOL or Assembler data name\nType an x over the C in the Cross-Reference section of the listing and press Enter, or type an R next to the UBP", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5f08693b201c-1", "text": "or CBP entry on the Monitoring Status display, and press Enter.\nRequest breakpoints\nSpecify the STATUS command then type R next to the RBP entry on the Monitoring Status display, and\npress Enter, or repeat the menu steps for setting the breakpoint, but enter an R next to the RBP option on the\nMonitoring menu. Complete the menus as you did when setting the request breakpoints.\n* All breakpoints\nRemove monitoring for the program. For more information, see Monitoring Menu Options. Do this from the\nMonitoring Status display.\nWARNING\nIf the program is being monitored for .ANY user, remove the breakpoints instead of the monitoring entry.\nRemoving monitoring for a program that others might also be testing is risky.\nNOTE\nIf you set more than one type of breakpoint at the same location, InterTest for CICS flags and intercepts only one\nat a time -- the first one you set. Once you remove the first one, the next one you set is flagged and activated,\nand so on.\nRemove Unconditional Breakpoints from the Menus\nRemove unconditional breakpoints using the monitoring menus of the Primary Option Menu or using the STATUS\ncommand menu when at a source listing breakpoint display.\n 987", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b7ce76b35620-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo remove an unconditional breakpoint using the menus, access the Program Monitoring (2.1), Transaction Monitoring\n(2.2), or Terminal Monitoring (2.3) menu, and follow these steps:\n1.Repeat the monitored entries for the following items:\n\u2013Program, transaction, or terminal (whichever is being monitored)\n\u2013User ID under which the entry is being monitored\n2.Enter r next to the UBP Option for Unconditional Breakpoints and press Enter\nThe Remove Breakpoint Locations screen appears.\nTo remove all unconditional breakpoints from a program, enter .ALL  in the Para/Data field and press Enter.\nYou can also remove breakpoints using the Set Breakpoint Locations screen.\nRemove Conditional Breakpoints from the Menus\nTo remove conditional breakpoints from the menus, use the monitoring menus of the Primary Option Menu.\nOn the Program Monitoring (2.1), Transaction Monitoring (2.2), or Terminal Monitoring (2.3) menu, follow these steps:\n1.Repeat the monitored entries for the:\n\u2013Program, transaction, or terminal (whichever is being monitored)\n\u2013User ID under which the entry is being monitored\n2.Enter r next to the CBP Option for Conditional Breakpoints.\n3.Press Enter.\nThe Remove Conditional Locations screen displays.\nTo remove all conditional breakpoints from a program, enter .ALL  in the Para/Data field and press Enter.\nYou can also remove breakpoints using the Set Conditional Breakpoints screen.\nRemove Request Breakpoints\nTo remove request breakpoints from the menus, use the monitoring menus of the Primary Option Menu.\nOn the Program Monitoring (2.1), Transaction Monitoring (2.2), or Terminal Monitoring (2.3) menu, follow these steps:\n1.Repeat the monitored entries for the:\n\u2013Program, transaction, or terminal (whichever is being monitored)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b7ce76b35620-1", "text": "\u2013Program, transaction, or terminal (whichever is being monitored)\n\u2013User ID under which the entry is monitored\n2.Enter r next to the RBP Option for Request Breakpoints.\n3.Press Enter.\nThe Remove Request Breakpoints screen appears. Enter the information exactly as you originally defined it.\nBreakpoint Activities\nExamine the Source Listing Breakpoint Screen\nWhen InterTest for CICS V10 - monitors a program, it halts program execution each time it detects an error or a user-\nspecified breakpoint; it then displays a breakpoint screen. The following screen shows an automatic breakpoint.\n   CA InterTest for CICS - PROTDEM FILE SOURCE LISTING BREAKPOINT           \nCOMMAND ===>                                                                   \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01 \n                                        Search= \n 988", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "489ea7a01140-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nOPTS 1 Proc div  2 Work-stor 3 Link sect 4 D-map      5 Clst/Pmap More:   + \n     6 Data xref 7 Proc xref 8 Err msgs  9 Srch fwd  10 Srch bwd            \nPFKS 1 Help      2           3 Det Bkpt  4 Profile    5 Resume     6 Menu \n     7 Backward  8 Forward   9 Next Wnd 10 001 Verb  11 Backtrace 12 Status  \n--------------------------------------------------------------------------------\n   _ 00880 CONTINUETASK.\n     00881**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED \n   A   ==> ADD +1 TO TASKNUM. \n       ==> \n     ==> ASRA abend (0C7) detected and prevented. Caused by invalid decimal \n       ==> arithmetic data format. \n       ==> \n       ==>      Press PF1 for a detailed description. \n       ==> \n   _ 00883     IF TASKNUM = 1 \n   _ 00884         MOVE 'DMAPASR'  TO MAPNAME. \n   _ 00885     IF TASKNUM = 2 \n   _ 00886         MOVE 'DMAPSUM'  TO MAPNAME. \n   _ 00887     IF TASKNUM GREATER 2 \n   _ 00888         GO TO SENDENDMSG.\nA\nIndicates the type of breakpoint that occurred:\nA\nAutomatic, detected by InterTest for CICS\nU\nUnconditional breakpo int that stops before  the specified item\n)\nUnconditional breakpoint that stops after the specified item\nC\nConditional\nV\nVariable-change\nR\nRequest\nADD +1 TO TASKNUM", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "489ea7a01140-1", "text": "C\nConditional\nV\nVariable-change\nR\nRequest\nADD +1 TO TASKNUM\nIndicates the statement or offset where the breakpoint occurred.\nASRA abend ...\nThese lines tell you why an automatic breakpoint occurred. For more information, press  PF1 . To remove these\nlines, press Enter  or scroll using PF7 or PF8 to see additional lines of source listing code.\nSource Listing Breakpoint Commands\nThe command line at a Source Listing Breakpoint supports all of the commands described for a Source Listing Display\nplus the following commands: AUTOSTEP, BTRACE, CS, FO, GO, NEXT, RESUME, RESETBKP, and RUN. These\ncommands are defined in the following table. In addition, use the command line to enter InterTest for CICS single-line\ncommands for CNTL, CORE, and FILE. See the online help and other topics in this area for information about single-line\ncommands.\n 989", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "09aba7a1fea6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nYou cannot use this command line to enter InterTest for CICS system-wide CNTL options.\nCommand PF Key Description\nABEND None Display the Abend Breakpointed Task\nscreen\nABI ON None Turn abend intercept on (default). This\nintercepts all CICS abends and produces\nan automatic breakpoint screen providing a\nCICS HANDLE ABEND LABEL/PROGRAM\nis not active.\nIf you want to intercept CICS abends for\nprograms having an active CICS HANDLE\nLABEL/PROGRAM, see the ABI FORCE\ncommand.\nABI OFF None Turn abend intercept off. This causes\nInterTest for CICS to stop intercepting CICS\nabends. No automatic breakpoint screen\nappears and the program abends.\nABI FORCE None Turn Abend Intercept on for all CICS\nABENDS, even if a program has an\noutstanding HANDLE ABEND active or\nissues a CICS HANDLE ABEND command.\nUse this option when you want an\nautomatic breakpoint screen for programs\nthat also have active HANDLE ABENDS to\nprocess their own errors.\nADVANCE n\nADV n\nA nNone Advances n entries in the statement trace\ntable and displays the resulting statement.\n(If n is not specified, it defaults to 1.) If\ndata monitoring is active, past data values\nfor the statement are also displayed. Use\nthis command to redisplay the execution\nsequence of a program. Statement tracing\nmust be active for the ADVANCE command\nto function (see the TRACE option).\nNote: This command is only valid for\nCOBOL programs.\nAUTOSTEP x y\nAS x yNone Resume execution x verb(s) at a time\ndisplaying the current source statement\nfor a y interval of time. This command is\navailable only at a breakpoint. Default: One", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "09aba7a1fea6-1", "text": "for a y interval of time. This command is\navailable only at a breakpoint. Default: One\nverb at at time until next CALL/COMMAND.\nBOTTOM\nBOTNone GO to bottom of source.\nBPO None Jump to Breakpoint Option screen.\nBTRACE PF11 Backtrace. Displays the backtrace\nsummary. This command is available only\nat a breakpoint.\nBWD PF7 Scroll backward. Set the scroll amount on\nthe Source Listing Profile. Does not apply\nwithin the Keep window.\n 990", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "727104ea91b7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCALLTRACE None Shows the program call flow leading up to\nthe currently breakpointed program. Select\nprograms having symbolic support from\nthe list and display their data areas. Select\nchannels at a specific program level from\nthe CALLTRACE program list.\nCHANNEL None Displays the currently allocated channel\nand the containers in the channel. Display\nthe data within a container from the\nselection list .This feature is only valid in\nCICS releases that support CHANNELs\nand Containers.\nCNTL None Displays the CNTL Command Menu.\nNote: The Monitoring Menu (=1.2) is an\nalternative to using the CNTL menu.\nCOMPOSITE None Set composite monitoring options for\nmonitoring of sub-programs.\nCORE None Displays the Main Storage menu. Select\nan option to view a main storage (CORE)\ndisplay.\nCOUNTS SHOW None Turns on the code coverage COUNTER\ndisplay. To activate code coverage, see\nCustomizing the Source Listing Profile or\nissue PROFILE command.\nCOUNTS NOSHOW None Turns off the code coverage COUNTER\ndisplay. To deactivate code coverage, see\nCustomizing the Source Listing Profile or\nissue the PROFILE command.\nCOUNTS RESET None Resets the program code coverage\nstatement counters to zero.\nCOUNTS op value None Turns on the code coverage COUNTER\ndisplay and highlights program statements\nthat match the criteria. The source listing is\nrepositioned to the first statement matching\nthe criteria.\nOp values: EQ or =, NE or <>, LT or <, GT\nor >, LE or <= or =<, GE or >= or =>\nValues: 0 to 9999\nCOUNTS NEXT None Repositions the source listing to the next\nstatement that matches the previously\nspecified COUNT op value criteria.\nCOUNTS ALL None Removes previously specified COUNT op", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "727104ea91b7-1", "text": "specified COUNT op value criteria.\nCOUNTS ALL None Removes previously specified COUNT op\nvalue criteria and redisplays source listing\nwithout special COUNTER highlighting.\nCS None Go to current breakpoint source statement.\nThis command is available only at a\nbreakpoint.\nDATAMON\nDMNone Displays the Monitoring Command Builder\nmenu to set and remove statement tracing\nand data monitoring.\nNote: This command is only valid for\nCOBOL programs.\n 991", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "199a895a2938-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDATAMON ON\nDM ONNone Turns data monitoring on. This causes\nInterTest for CICS to capture data values\nfor each executed statement in the\nprogram. You are then able to redisplay\nthese values at a breakpoint, by tracing\nbackward and forward through the entries\nin the statement trace table using the PREV\nand ADVANCE commands. DATAMON ON\nforces TRACE ON.\nNote: This command is only valid for\nCOBOL programs.\nDATAMON OFF\nDM OFFNone Turns data monitoring off. This causes\nInterTest for CICS to stop capturing data\nvalues for each executed statement in the\nprogram. In addition, you can no longer\ndisplay captured data values when tracing\nbackward and forward through the entries\nin the statement trace table using the PREV\nand ADVANCE commands.\nNote: This command is only valid for\nCOBOL programs.\nDISPLAY data-item\nD data-itemNone Displays the storage of a data name.\nDOWN None Shift listing down.\nEND PF3 Returns to the prior display or menu.\nFILE None Displays the Auxiliary Storage menu. Select\nan option to view a file or queue.\nFIND\nFNone Find a string\nFO None Find hexadecimal offset. This command is\navailable only at a breakpoint.\nFP None Find paragraph.\nFS None Find statement number.\nFWD PF8 Scrolls forward the amount indicated on the\nsource listing Profile. Does not apply within\nthe Keep window.\nGO None Continue until the next intercept occurs.\nThis command is available only at a\nbreakpoint.\nHELP PF1 Displays help for the source listing facility.\nIC None Jump to Indirect Command screen.\nITST None Displays the Primary Option menu.\nKEEP data-item\nK data-itemNone Add a data-item to the static Keep window\nLEFT None Shift listing left.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "199a895a2938-1", "text": "K data-itemNone Add a data-item to the static Keep window\nLEFT None Shift listing left.\nLOCATE\nLOC\nLNone Locate line number or part of the listing.\nMARGIN\nMARNone Shift listing to specific margin.\n 992", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8e86825352be-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMENU PF6 Displays the Breakpoint Primary Option\nmenu.\nMONITOR None Sets monitoring for the listed program.\nNEXT\nNPF10 Execute the next verb in a program. This\ncommand is available only at a breakpoint.\nNEXT OVER None Continue the test session when stopped\non a PERFORM or CALL until the lexical\nstatement following the PERFORM or CALL\nis encountered, where a breakpoint occurs.\nNEXT RETURN None Continue the test session when stopped\nwithin a paragraph or subroutine until\nthe session encounters the lexical\nstatement following the PERFORM or\nCALL that invoked the current paragraph\nor subroutine, where a breakpoint occurs.\nTRACE ON must be enabled.\nOFFALL None Removes all breakpoints set by active\nUSER or TERMINAL. Active USERID\nis used if a valid USERID is signed on.\nOtherwise, the active TERMINAL is used.\nALL breakpoints for ALL programs/\ntransactions/ are removed that were set by\nthe active USERID or active TERMINAL.\nOFFALL TERM None Removes all breakpoints set by active\nTERMINAL.\nOFFALL USER None Removes all breakpoints set by active\nUSER.\nPO None Set or remove storage protection options\nPREV n\nP nNone Backs up n entries in the statement trace\ntable and displays the resulting statement.\n(If n is not specified, it defaults to 1.) If\ndata monitoring is active, display also past\ndata values for the statement. Use this\ncommand to step backward through the\nexecution of a program. Statement tracing\nmust be active for the PREV command to\nfunction (see the TRACE option).\nNote: This command is only valid for\nCOBOL programs.\nPROFILE PF4 Displays the source listing Profile, where\nyou change settings for the current session.\nRBP None Set or remove Request Breakpoints", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8e86825352be-1", "text": "you change settings for the current session.\nRBP None Set or remove Request Breakpoints\nRESETBKP Clear Repositions breakpointed task at current\nbreakpoint.\nRESUME PF5 Resumes breakpointed task at next\nsequential instruction. This command is\navailable only at a breakpoint.\nRIGHT None Shift listing right.\nRO None Set or remove replacement options\n 993", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3f13f1e1c0e7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nRUN None Resume execution ignoring all breakpoints.\nThis command is available only at a\nbreakpoint.\nSET None Initialize a data-item's value\nSO None Set or remove special options\nSDFDATA None Displays data in Structure Display Format\nfor the current program.\nSDFHEX None Displays data in hexadecimal/character\nformat for the current program.\nSTATUS PF12 Displays the Monitoring Status report\n(Option 2.4 on the Primary Option\nMenu) for the current program. Remove\nmonitoring, breakpoints, and options\ndirectly from the Status display.\nSTATUS\nALLNone Displays the Monitoring Status report for\nall programs, transactions, and terminals\nInterTest for CICS is monitoring in the\nregion.\nStorage None Displays a listing off all USER and CICS\nclass storage associated with the currently\nbreakpointed task (most storage acquired\nby InterTest for CICS is not displayed), this\ncommand also checks the crumple zones of\neach piece of storage for validity.\nTRACE\nTRNone Displays the Monitoring Command Builder\nmenu to set and remove statement tracing\nand data monitoring.\nNote: This command is only valid for\nCOBOL programs and is unrelated to the\nBacktrace facility.\nTRACE ON\nTR ONNone Turns statement tracing on. The number of\nentries to be saved in the statement trace\ntable is determined by the STMTTRCE\noption in IN25OPTS. The default is 1000.\nNote: This command is only valid for\nCOBOL programs and is unrelated to the\nBacktrace facility.\nTRACE OFF\nTR OFFNone Turns statement tracing off. TRACE OFF\nforces DATAMON OFF.\nNote: This command is only valid for\nCOBOL programs and is unrelated to the\nBacktrace facility.\nTOP None Go to top of source.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3f13f1e1c0e7-1", "text": "Backtrace facility.\nTOP None Go to top of source.\nUP None Shift listing up.\n=x.y.z\n=1.x.y.zNone Fast-path to Breakpoint Primary Menu\nOption x.y.z, discussed in Breakpoint\nActivities. The equivalent ITST Primary\nOption Menu fast-path entries are = 1.x.y.z.\n<{nnnn} None Used in the Keep window to scroll data item\nstorage left nnnn bytes.\n>{nnnn} None Used in the Keep window to scroll data item\nstorage right nnnn bytes.\n 994", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "638444728782-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n+{nnnn} None Used in the Keep window to increase\nCOBOL index item value by nnnn (if no\nvalue is entered the default is 1).\n-{nnnn} None Used in the Keep window to decrease\nCOBOL index item value by nnnn (if no\nvalue is entered the default is 1).\nSource Listing Breakpoint PF Keys\nThe following PF keys are available for Source Listing Breakpoint:\nPF1 Help\nDisplays a Help menu relating to the current Source Listing Breakpoint screen.\nPF2\nUnassigned.\nPF3 Det Bkpt\nDisplays the Breakpoint Information screen for the current breakpoint. This function is available only at a\nbreakpoint.\nPF4 Profile\nDisplays the Source Listing Profile screen.\nPF5 Resume\nContinues program execution at the next sequential instruction. This function is available only at a breakpoint.\nPF6 Menu\nDisplays the Breakpoint Primary Options Menu discussed here.\nPF7 Backward\nScrolls the compiler output backward one page or the amount set on the source listing profile. Does not apply\nwithin the Keep window.\nPF8 Forward\nScrolls the compiler output forward one page or the amount set on the source listing profile. Does not apply within\nthe Keep window.\nPF9\nSwitch to next window.\nPF10 001 Verb\n001 Verb/Instr/Stmt or Autostep single steps or auto steps through execution, as indicated by the PF key label.\nUse PF4 to specify the stepping function and amount on the source listing Profile. This function is available only at\na breakpoint.\nPF11 Backtrace\nDisplays the Backtrace Summary. This function is available only at a breakpoint.\nPF12 Status\nDisplays the Monitoring Status for the current program. Remove breakpoints and monitoring directly from the\nStatus report.\nPF19", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "638444728782-1", "text": "Status report.\nPF19\nScrolls forward within the Keep window.\nPF20\nScrolls backward within the Keep window.\nClear\nRedisplays the current breakpoint.\n 995", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6fde732b814e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nRespond to Automatic Breakpoints\nAn automatic breakpoint occurs when InterTest for CICS detects an error. When a program is stopped at an automatic\nbreakpoint, either correct the error or go around it.\nTo find out what caused the error and for instructions on how to fix it, press PF1 from any automatic breakpoint display\nwith the error message displayed. InterTest for CICS Help provides additional information about the specific error. In most\ncases, Help recommends how to handle the error.\nBypass the Monitoring of a Statement that Triggered an Automatic Breakpoint\nSometimes InterTest for CICS stops you at an automatic breakpoint when the program is working according to your\nspecifications. These are usually instances when you are intentionally violating a CICS coding standard. To continue\nprogram execution without removing the error, bypass the statement, as described next, or set an InterTest for CICS\nmonitoring option so that you are not stopped again (such as NOM).\nWARNING\nThis function bypasses monitoring only of the individual Assembler instruction. For high-level COBOL or PL/I\nprograms, there might be more than one Assembler instruction per statement, which could trigger more than one\nautomatic breakpoint for a single statement. As a result, you might have to invoke this function more than once\nto continue past a statement stopped at an automatic breakpoint.\nThere are two methods of bypassing an automatic breakpoint: temporarily and permanently. A temporary override works\nfor the current breakpoint only. A permanent bypass works each time the statement is executed.\nTemporary Override\nTo temporarily bypass the monitoring of a statement that triggered an automatic breakpoint:\n1.Press PF6 to display the Breakpoint Primary Option Menu.\n2.Select Option 5 Override Automatic Breakpoint.\nNOTE\nFor fast-path entry, enter =5 on the command line of the Breakpoint display.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6fde732b814e-1", "text": "NOTE\nFor fast-path entry, enter =5 on the command line of the Breakpoint display.\nThe override lets the statement that caused the breakpoint to be executed for this instance, only.\nPermanent Bypass\nTo permanently bypass the monitoring of a statement that triggered an automatic breakpoint:\n1.Overtype the A on the Source Listing Breakpoint with b .\n2.Press PF5 or PF10  to resume execution. This lets the statement causing the breakpoint to be executed; that is, the\nbypass function lets the error to occur.\nNOTE\nThis command may be password protected.\nWork with Data at a Breakpoint\nWhen InterTest for CICS detects a breakpoint, it halts the program before the instruction at the breakpoint location is\nexecuted. While at a breakpoint, InterTest for CICS preserves the task's main storage for examination or modification prior\nto task resumption. Here is a summary of how to work with your data at a breakpoint. Each function is explained later.\nNOTE\nWhen using DWARF as a debugging format, a copy of the source is displayed, not a listing.\n 996", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "48d2eaa60fa2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nView or Search for Data\nView any portion of your compiler output and search for occurrences of data strings.\nKeep Data in Window\nKeep the values of data items, displayed up to 6 at a time, at the top of your source listing in the Keep window.\nThis lets you observe changes in their values as the program executes without having to leave the source listing\ndisplay.\nWhen the Keep window is active, the header lines listing the InterTest for CICS options and PF key functions are\nreplaced with a command line. To view options and PF keys, press PF4, then press Enter to return.\nCode Coverage Counters in Window\nDisplay a counter for each line of code and check its verb execution count. This lets you observe changes in the\nexecution value as the program executes without having to leave the source listing display.\nDisplay or Modify Main Storage\nDisplay and dynamically change data in main storage at any breakpoint. If there is an error, fix it in main storage,\nand then continue execution as if the error never existed.\nOnline access to main storage means you do not have to wait for and analyze a dump. To make accessing main\nstorage easy, InterTest for CICS provides a structured display of main storage with data names on the left and\nboth hexadecimal and character values on the right.\nDisplay or Modify Auxiliary Storage\nView, modify, or create test data using the FILE transaction. At a breakpoint, verify test data, and even create test\nrecords.\nSearch for Data\nAsk InterTest for CICS to define, search for, and display any character string (such as a data item, label, or paragraph\nname). This is a quick way to go to different areas in a listing when you want to set a breakpoint or check your code.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "48d2eaa60fa2-1", "text": "Search for data using the Search=field, or by entering a FIND or LOCATE command on the command line. If you know the\nline number, hex number, or the label that you want to view, use the line commands to position the listing accordingly.\nFind a Definition or Search Using the Search = Field\nUse the Search= field to define or search for data as follows.\nTo display the definition of a data item, follow these steps:\n1.Enter a data item name up to 31 characters in the Search= field.\n2.Press Enter to begin the search. InterTest for CICS highlights the data item and its definition.\nTo search for a data item, follow these steps:\n1.Enter up to 31 characters in the Search=  field.\n2.Specify the search direction in the Option # field. (Option # 9 is Search Forward; Option # 10 is Search Backward.)\n3.Press Enter to begin the search.\nFor COBOL nested programs, InterTest for CICS first searches the current nested program (indicated in the NESTED=\nfield) for the specified data item. If the data item is not found in the indicated program, InterTest for CICS then searches\nthe main program and other nested programs for the item.\nIt is not necessary to enter the entire data item, label, or paragraph name; enter the first few characters to begin your\nsearch.\nExample\nIf you wanted to search for TASKNUM, you could enter TASK, TASKN, and so on, in the Search= field.\n 997", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0baffae0a6b0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe Online Listing\nUse the command line commands to position or shift the view of the listing. Go to the top or bottom of the listing, shift\nthe listing to the right or left a specific number of characters, position the listing to a specific line. Described next are two\nadditional commands that are available only at a source listing breakpoint. These commands enable you to position a\nlisting at specific hex number, or position the listing to a specific label or to the current breakpointed line.\nPosition Listing to a Hex-Offset\nTo position the listing to a specific hex-number, enter:\nFO hex-number\nHex-number\nIndicates any hex number within an Assembler program.\nNOTE\nFO is available only during breakpoint processing.\nPosition Listing to Current Breakpoint Processing\nTo position the listing to the current breakpointed line, enter CS. CS is available only during breakpoint processing.\nThe Keep Window\nDisplay items from main storage in a window at the top of the Source Listing display. Keeping items in the Keep window\nlets you easily compare values and observe changes in values. It also lets you to dynamically modify the displayed values\nas the program executes.\nAdd a Storage Item\nDisplay up to six data items at one time in the Keep window whenever the source listing is displayed. Identify the data\nitems whose values you want to observe. If you identify more than six items, the first six items that you specify are\ndisplayed. When one item is removed from the Keep window, another item appears. If there are more than six items in\ntotal, view these by scrolling forward.\nThe following screen shows four data items displayed, in hexadecimal format, in the Keep window on the source listing\nbreakpoint display.\n     CA InterTest for CICS - PROTDEM FILE SOURCE LISTING BREAKPOINT \nCOMMAND ===>", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0baffae0a6b0-1", "text": "COMMAND ===>                                                                   \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01 \n                                        Search=   \n \n --------------------------------------------------------------------------- \n  |    TASKNUM                       | 000000                                \n  |    TASKIDNO                      | 000F                                 \n  |    TASKDATE                      | F0F961F1 F561F8F9                 \n  |    VARLENGTHDATA                 | 00                                    \n ----------------------------------------------------------------------------  \n  _ 00880 CONTINUETASK.                                                       \n    00881**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED                         \n  A   ==>     ADD +1 TO TASKNUM.                                               \n      ==>                                                                      \n      ==> ASRA abend (0C7) detected and prevented. Caused by invalid decimal   \n      ==> arithmetic data format.                                              \n      ==>                                                                      \n 998", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "10e9927c7aa8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n      ==>      Press PF1 for a detailed description.                           \n      ==>                                                                      \n  _ 00883     IF TASKNUM = 1     \n  _ 00884         MOVE 'DMAPASR'  TO MAPNAME.           \nTo add a data item from where it is defined, follow these steps:\n1.Enter k to the left of the statement defining it.\n2.Press Enter . InterTest for CICS places the data item in the Keep window.\nTo add a data item from where it is referenced, follow these steps:\n1.Enter k to the left of the statement referencing it.\n2.Place the cursor under any character in the data item.\n3.Press Enter . InterTest for CICS places the data item in the Keep window.\nNOTE\nData items remain in the Keep window until you remove them or until you turn off InterTest for CICS monitoring\nfor the program -- except for items added using the AUTOKEEP facility. AutoKeep items appear in high intensity\nin the Keep window; permanent Keep items appear in low intensity.\nUsing AUTOKEEP\nAUTOKEEP lets you to display items in the Keep window concerning the currently highlighted line, in addition to any data\nitems you requested displayed permanently.\nAUTOKKEEP is active when the IN25OPTS parameter SLBAKEEP is set to Yes, which is the default. However, use the\nSource Listing Profile Screen to turn AUTOKEEP off or on again at any time.\nChange an AutoKeep Item into a Permanent Keep Item\nTo change an AutoKeep item into a permanent item, follow these steps:\n1.Enter k to the left of the data item.\n2.Press Enter . The item now appears in low intensity indicating that it is a permanent item.\nScroll Forward and Backward", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "10e9927c7aa8-1", "text": "Scroll Forward and Backward\nScroll forward and backward through the Keep window when there are more than six Keep Table entries. Up to six entries\nappear in the Keep window at one time. If there are more than six entries, the heading line, MORE: + (plus) displays in the\nKeep window indicating that there are more entries to view forward. The additional entries appear in the next window as\nyou scroll forward. The heading line, More: - (minus), indicates that there are more entries to view backward. Use  PF19  to\npage forward to the next Keep window; use  PF20  to page backward.\nScroll Left and Right\nScroll each data item in the Keep window left or right by using the arrow (< >) line commands. To scroll a data item left,\ntype < in the first position of the line command area and press Enter. A < line command alone scrolls the data left the\nwidth of the display area. To scroll a specific number of bytes specify a numeric offset value after the line command, such\nas <5. This causes the data to scroll 5 bytes left or +5 bytes from the start of the data. To scroll back to the start of the\ndata enter >5 or > without an offset. Data item values with lengths that are less than the display area cannot be scrolled. A\ndata item value cannot be scrolled right, > unless it has been first scrolled left ( <).\nIncrease or Decrease COBOL Index Item Value\nIncrease or decrease COBOL index item values in the Keep window using the plus (+) or minus (-) line commands.\n 999", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6dcb590cb04e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022To increase an index item value, type + in the first position of the line command area and press Enter. By default the +\nline command increases the value by one.\n\u2022To increase by a specific value specify a number after the line command.\nExample: +5\nThe - line command decreases the value.\nThis functionality is applicable for COBOL indices defined by INDEXED BY phrase only.\nRemove Items\nTo remove a data item from the Keep window, follow these steps:\n1.Enter x to the left of the data item.\n2.Press Enter .\nWhen all data items are removed, the command line and the Keep window are replaced by the options and PF key\nfunctions.\nView and Change Main Storage Display from the Keep Window\nWhen the Keep window is active, InterTest for CICS replaces the title lines for the InterTest for CICS options and PF key\nfunctions with expanded source display area. This is the No Titles format. The No Titles format lets you to use InterTest for\nCICS commands and the options and PF keys to perform InterTest for CICS functions.\n\u2022To see the options and PF key functions, enter PROFILE  in the command line and press Enter\n\u2022To exit the Profile, press Enter\nFor each item in the Keep window, InterTest for CICS displays the data name and its value in main storage in hexadecimal\nor character format depending on the SDF profile setting. Use the PF2 key to toggle between hexadecimal and character\nformats.\nTo request a main storage display, follow these steps:\n1.Enter d in column 1 to the left of the item listed in the Keep window.\n2.Press Enter  to process your request. InterTest for CICS displays the main storage for the data item and all items\nbelow it in the same structure.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6dcb590cb04e-1", "text": "below it in the same structure.\nTo modify data values using a pre-formatted MOVE command, follow these steps:\n1.Enter m in column 1 to the left of the item listed in the Keep window.\n2.Press Enter to make the change. InterTest for CICS displays the MOVE command screen. For more information,\nsee Display or Modify Main Storage (CORE).\nTo change the values of the data items, follow these steps:\n1.Overtype the bytes displayed in the Keep window in either hexadecimal or character format.\n2.Press Enter to change the values that appear in the Keep window.\nAn effective debugging tool is to observe data values in the Keep window as you single-step through execution using\nPF10 . You may also have InterTest for CICS automatically repeat single-stepping every few seconds. Use the Profile\ndisplay to set the PF10 value for automatic single-stepping.\nDisplay or Modify Main Storage (CORE)\nDisplay and modify easily the value of any data item or register in main storage directly from the source listing display\nscreen. All main storage functions are functions of the CORE facility, but you do not have to access the CORE menus to\nuse the functions described here.\n 1000", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2cccf387d008-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nWhen you request main storage displays directly from your breakpoint screen, InterTest for CICS responds with\na structured display whenever the request is for a data item defined in a structure.\nMain storage functions include the following benefits:\n\u2022Displaying the value of a data item\n\u2022Modifying the value of a data item with a formatted MOVE command\n\u2022Modifying a data item by overtyping the main storage display or Keep window display\n\u2022Displaying and modifying program registers\nThe first three functions are discussed in the sections that follow. For more information about displaying and modifying\nprogram registers, see Source Listing Facility.\nNOTE\nKeep storage items displayed directly on your Source Listing Breakpoint screen by using the Keep window. For\nmore information, see The Keep Window.\nDisplay the Value of a Data Item\nDisplay data items from where they are defined (for example, from the Working-Storage, Local-Storage, or Linkage\nsections), or from where the data items are referenced in the code.\nTo display the value of a data item from where it is defined, follow these steps:\n1.Enter d to the left of the line defining it. For multiple data items, enter d next to the definition of each item that you want\nto display.\n2.Press Enter . InterTest for CICS responds with a main storage display.\nIf you requested more than one item for display, InterTest for CICS responds with a structured CORE storage display for\nthe first item selected. The message line on the screen prompts you to press Clear to view the next item, or press PF3\nto cancel the remaining requests. After the last item is displayed, press Clear to return to the Source Listing Breakpoint\ndisplay.\nTo display the value of a data item from where it is used in the code, follow these steps:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2cccf387d008-1", "text": "1.Enter  d to the left of any line in the compiled listing that contains the item.\n2.Move the cursor under any alphanumeric character in the data item.\n3.Press Enter .\nInterTest for CICS responds with a main storage display. The first field on the display screen is the value of the data item\nyou requested.\nWARNING\nIf an Assembler variable is redefined in the code with a using statement other than the original DSECT in which\nit was originally contained, then the display of the data item should be made from where it is defined, not from\nwhere referenced.\nUse the Cursor\nFollow these rules when using the cursor to display main storage:\n\u2022Place the cursor under any character in a data name, Assembler register, or Assembler label.\n\u2022Do not place the cursor under a comma, parenthesis, COBOL verb, Assembler masks, Assembler data items in the\nform A+B or A-B+n, or under any comment area.\nTo display complex data items, use one of the following methods:\n 1001", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4a0c312376b1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Display qualified data names as follows: For X of Y, place the cursor under X in any line of code.\n\u2022Display subscripted or indexed data names as follows:\nFor Y(s1, s2, s3):\n\u2013To get the value of Y at s1, s2, s3, place the cursor under Y\n\u2013To get the value of s1, place the cursor under s1\nExample\nTo display the value of TASKNUM from the Automatic Breakpoint screen, overtype the A with d, move the cursor under\nany letter in TASKNUM, and press Enter.\nThe following display of main storage for TASKNUM panel displays.\n   CA InterTest for CICS  - MAIN STORAGE UTILITY  \n  Starting at Address =  2142A8                Hexadecimal            Character\n \n 02 TASKNUM                         | 000000                     | ...          \n 02 TASK TEXT                       | 00000000 00000000 00000000 | ............ \n                                    | 00000000 00000000 00000000 | ............ \n                                    | 00000000 00000000          | ........     \n \n \n \n \n  _______________________________________________________________________________  \nPFKEYS 1 Help     2           3 End       4 Return    5            6 Menu \n       7 Backward 8 Forward   9 Caps Off 10           11 Redisplay 12 Structure \n CORE='TASKNUM'                                                             \n CAIN0452 FIELD DOES NOT CONTAIN A VALID PACKED DECIMAL (COMP 3) VALUE   \nWARNING\nIf you enter d to the left of a statement and forget to place the cursor under the data item, you will see the object", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4a0c312376b1-1", "text": "code for the statement instead. Press Clear  or PF3 to return to the Source Listing Breakpoint.\nModify a Data Item by Overtyping the Main Storage Display\nFrom any InterTest for CICS main storage display or Keep window, modify main storage by following these steps:\n1.Overtype the desired bytes in the character or hexadecimal area.\n2.Press Enter  to process the change.\nUse this method to correct invalid data or data that was not initialized. Remember that these modifications are dynamic --\nthey are one-time fixes that do not prevent the same error from occurring again.\nExample\nIn the previous screen, you could initialize TASKNUM by overtyping the final 0 in the hexadecimal field for TASKNUM with\nC and pressing Enter.\nNotes:\n\u2022Display and modify task-related and system-related areas of CICS main storage using the CORE facility menus or\ncommands.\n\u2022If you try to change a password-protected storage area not owned by your program, InterTest for CICS prompts you to\nenter the password.\n 1002", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "48db2b576041-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nModify the Value of a Data Item with a MOVE Command\nCOBOL and PL/I\nInterTest for CICS provides a preformatted MOVE command that lets you easily modify the value of a COBOL or PL/I data\nitem. Request the MOVE command from the following places:\n\u2022Where the data item is defined in the source listing\n\u2022A Keep window\n\u2022Any place in the listing where the data item is referenced\nTo modify a data item from the statement where it is defined or from a Keep window, follow these steps:\n1.Type m to the left of the statement. To modify more than one data item, type m next to each item in the order in which\nthey appear.\n2.Press Enter. InterTest for CICS generates a fill-in-the-blank MOVE command for each data item selected.\nTo modify a data item from where it is referenced, follow these steps:\n1.Enter m to the left of any statement in the listing containing the data item.\n2.Place the cursor under the data item.\n3.Press Enter. InterTest for CICS generates a fill-in-the-blank MOVE command for each data item selected.\nNOTE\nThis function is not supported for Assembler users.\nExample\nType m to the left of the fields TASKNUM and TASK-TEXT from their definitions in Working-storage and press Enter. The\nformatted MOVE commands display.\nTo change the value of a data item, follow these steps:\n1.Enter one of the following in the entry field:\n\u2013A data name\n\u2013ZEROS, SPACES, LOW-VALUES, HIGH-VALUES, QUOTES\n\u2013A numeric literal with or without a leading + or - sign\n\u2013An alphanumeric literal enclosed in single quotes", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "48db2b576041-1", "text": "\u2013An alphanumeric literal enclosed in single quotes\n\u2013ALL literal  to fill the data item with a specified literal string. For example: ALL ' - ' fills the field with dashes.\n2.Press Enter to execute the MOVE command. InterTest for CICS responds with a main storage display showing the\nresult of the first MOVE. For multiple moves, the storage displays are shown one at a time; press Clear  to process the\nnext one.\nNOTE\nIf you do not press Clear, the remaining MOVE commands will not execute.\n3.From the CORE display, press Clear  or PF3 to return to the source listing breakpoint display.\nNOTE\nAll modifications to main storage are dynamic. This means that the changes are one-time fixes   to current\nvalues, and will not prevent the same error from occurring again. For a more permanent correction, specify a set\nof indirect commands to be executed at a particular program location.\nThe Statement Trace Facility (COBOL programs only)\nThe Statement Trace Facility lets you view the logic flow of your program at the statement level. When used with data\nmonitoring, it also lets you to view data values from the time that the statement was executed.\n 1003", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "420f77f79658-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nThis feature is only valid for COBOL programs. Use the Backtrace facility for tracing information for other\nlanguages.\nEnable Statement Tracing and Data Monitoring\nUse the TRACE command to enable the statement tracing facility. If a statement trace table was not created for the\ntransaction, it will be created prior to executing the next statement in the program. The number of entries in the table is\ndefined by the STMTTRCE option in IN25OPTS. Once statement tracing is activated, InterTest for CICS saves information\nabout each statement in the program, as it is executed. When all of the statement table entries are used, the table will\nwrap around and the oldest entry is reused for the current statement.\nUse the DATAMON command, or DM, to enable data monitoring for a program. Since the statement trace facility is\nrequired for data monitoring, it will also be enabled if it is not already active. Once data monitoring is active, InterTest for\nCICS captures the data values for each statement in the program, as it is executed.\nNavigate the Statement Trace Table\nOnce statement information is saved in the trace table, use the PREV and ADVANCE commands to determine the\nexecution path of the program, by stepping backward and forward through the executed statements.\nUse the PREV, or P, command to cause the display to back up one or more entries in the statement trace table. Consider\nthe following breakpoint:\n    CA InterTest for CICS   - PROTSYM FILE SOURCE LISTING BREAKPOINT \nCOMMAND ===> prev                                                              \nProgram= COB2DEMO Option #       Stmt #                             Margin= 01  \n                                        Search=                                \n-------------------------------------------------------------------------------\n _____ TASKNUM                         | 000000                                 \n---------+---------------------------------------------------------------------\n _ 000531 CONTINUE-TASK.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "420f77f79658-1", "text": "---------+---------------------------------------------------------------------\n _ 000531 CONTINUE-TASK.                                                        \n   000532**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED                          \n A    ==>     ADD +1 TO TASKNUM.                                                \n      ==>                                                                        \n      ==> ASRA ABEND (0C7) detected and prevented. Caused by invalid decimal     \n      ==> arithmetic data format.                                                \n      ==>                                                                        \n      ==>      Press PF1 for a detailed description.                             \n      ==>                                                                        \n _ 000534     IF TASKNUM = 1                                                    \n _ 000535         MOVE 'DMAPASR'  TO MAPNAME.                                   \n _ 000536     IF TASKNUM = 2                                                    \n _ 000537         MOVE 'DMAPSUM'  TO MAPNAME.                                   \n _ 000538     IF TASKNUM GREATER 2                                              \n _ 000539         GO TO SEND-END-MSG. \n _ 000540     GO TO REWRITE-TSQ.  \nThe PREV command backs up to the previous entry in the table, resulting in the following display:\nCA InterTest for CICS  - PROTSYM FILE SOURCE LISTING BREAKPOINT     \nCOMMAND ===> prev                                                              \nProgram= COB2DEMO Option #       Stmt #                             Margin= 01  \n                                        Search=                                \n-------------------------------------------------------------------------------\n _____ TASKNUM                         | 000000                                 \n 1004", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "69bff9ca56ca-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n---------+---------------------------------------------------------------------\n000522          MOVE '   00209 '    TO DFHEIV0  \n_ 000523    CALL 'DFHEI1' USING DFHEIV0.    \n_ 000524    IF EIBAID = DFHENTER GO TO CONTINUE-TASK.   \n_ 000525    IF EIBAID = DFHCLEAR GO TO SEND-END-MSG.    \n_ 000526    IF EIBAID = DFHPF3 GO TO SEND-END-MSG.  \n_ 000527    IF EIBAID = DFHPF15 GO TO SEND-END-MSG. \n_ 000528    IF EIBAID = DFHPF2 GO TO EXPANDED-DEMO. \n_ 000529    IF EIBAID = DFHPF14 GO TO EXPANDED-DEMO.    \n_ 000530    GO TO SEND-FIRST-SCREEN.    \n_ 000531 CONTINUE-TASK.                                                        \n   000532**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED                          \n A    ==>     ADD +1 TO TASKNUM.                                                \n _ 000534     IF TASKNUM = 1                                                    \n _ 000535         MOVE 'DMAPASR'  TO MAPNAME.                                   \n _ 000536     IF TASKNUM = 2                                                    \n _ 000537         MOVE 'DMAPSUM'  TO MAPNAME. \nStatement number 524 was the last statement executed prior to the abend at statement number 533. To back up 10\nentries in the table, specify PREV 10. After using the PREV command to back up one or more entries in the statement\ntrace table, use the ADVANCE, or A, command step forward through the table. Return at any time to the current statement", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "69bff9ca56ca-1", "text": "using the CS command or the clear key.\nView Past Data Values\nWhile navigating the trace table, display the data values that were captured as each statement was executed, if data\nmonitoring is active. If the AUTOKEEP display is ON, the past data values associated with an executed statement\nautomatically appear in the Keep window when the statement is displayed. In addition, use the DISPLAY, KEEP, and\nCORE commands to display past data values for any data item or COBOL language area (for example, TGT). However,\nthese values are protected and, therefore, cannot be updated while viewing past data values.\nIn general, past data values are not captured for database areas or CICS task areas. However, a few of these areas, such\nas DFHEIBLK or SQLCA, are defined within the COBOL program and, therefore, reside in COBOL storage. For these\nareas, display past data values by specifying the data name defined in the COBOL program. If the CORE keyword is used\n(for example, CORE=EIB), current data values are displayed.\nUsage Notes\nData monitoring is very CPU intensive and requires a significant amount of storage over and above the storage required\nby the programs being monitored. Compute the storage requirements as follows:\n500 bytes * number of transaction entries as defined by the STMTTRCE\noption + size of mirror area for each program in the transaction for which data monitoring is active, where the mirror area\nis equal to the size of storage for the monitored program.\nIf you should encounter storage problems while using the data monitoring feature, perform one or more of the following\nactions:\n\u2022Reduce the use of data monitoring in the region\n\u2022Make the STMTTRCE value smaller in the default options table, IN25OPTS\n\u2022Increase the EDSALIM for the CICS region\n 1005", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1b07b9718c7e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDisplay or Modify Auxiliary Storage (FILE)\nUse the InterTest for CICS FILE facility even when no program is executing to display and modify auxiliary storage.\nAccess this facility from the ITST Primary Option Menu, Option 4 Auxiliary Storage . The Auxiliary Storage Menu\nappears.\nFrom this menu you can examine or modify files, DB2 and SQL/DS databases, DL/I databases, and CICS temporary\nstorage and transient data records.\nNOTE\nIf you type FILE on the command line of a breakpoint display, you bypass this menu and go to the initial file\nfacility display. To access the Auxiliary Storage menu from a Breakpoint, type ITST  on the command line; then\nselect option 4 from the Primary Option Menu.\nFILE at a Breakpoint\nUse FILE at a breakpoint to add test records. For example, you can have 12 records in a test file, one for each of 12 test\nconditions. However, when you get to a breakpoint you realize there is another test condition. To test the condition in the\ncurrent test run and have a complete test file for future runs, go to FILE, add another test record, return to the breakpoint,\nand continue program execution so the program reads the new record.\nIf you are using FILE, you do not have to enter a record from scratch. Retrieve a current record, modify it, and then add it\nas a new record to the file.\nFILE Changes Do Not Affect Main Storage at a Breakpoint\nFILE changes do not automatically affect main storage.\nExample\nIf you are stopped at a breakpoint and you use FILE to change the record that your program is processing, the change\nyou made using FILE is not automatically reflected in your program's main storage because your program has already\nread the record.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1b07b9718c7e-1", "text": "read the record.\nTo make the change in main storage, return to the breakpoint screen, and do one of the following actions:\n\u2022Instruct the program to read the record again\n\u2022Repeat the changes to main storage that you made to the record or database\nNOTE\nIf multiple fields need to changing, select multiple items for display or modification from the Working-storage or\nLocal-Storage section of a COBOL program.\nTo return to the breakpoint display after using FILE, press PF3 or Clear . (If you also accessed the InterTest for CICS\nCNTL, CORE, or Help facilities, you might need to press Clear  more than once.)\nChanges to data using FILE are permanent updates  to the records or database. It is as if you wrote a batch program to\nperform the updates.\nThe Breakpoint Primary Option Menu\nTo access the Breakpoint Primary Option Menu from any Breakpoint, enter MENU  on the command line or press PF6\nMenu . Use this menu to access the following options:\nMain menu\nDisplay the InterTest primary option menu\nStatus\nDisplay/remove current monitoring options\n 1006", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "43dd4fb25898-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAbend\nAbend the breakpointed task\nResume\nResume breakpointed task menu options\nOverride\nOverride automatic breakpoint default processing\nDump\nCause dump, resume from next sequential instruction\nDisconnect\nDisconnect the breakpoint from this terminal\nHogan SMART\nInvoke Hogan System's debugging facility\nExit\nTerminate breakpoint menu processing\nPress PF3 End to exit this menu and return to your breakpoint display.\nThe CALLTRACE Facility\nThe CALLTRACE facility enables you to view the logic flow of a group of programs. Once the CALLTRACE mode is active\nview the storage for each program in the same way it is viewed from a breakpoint. Use the CALLTRACE command only if\nyour programs adhere to standard linkage conventions as follows:\n\u2022COBOL dynamic or static calls to other COBOL programs\n\u2022EXEC CICS LINKED or XCTLed to PROGRAMs\n\u2022Standard MVS save area linkage\nIn the following example the CALLTRACE was issued while program C370SUB2 was stopped at a breakpoint. The\nCALLTRACE screen shows how program C370SUB2 received control.\n                 CA InterTest for CICS Program Call Trace  \nCOMMAND ===>                                                                   \n \n  Type:  S to select program source                                            \n         C display channel/containers                                          \n  ------- Program Call Sequence --------                                       \n  Program   Csect     Return  Language    Call Type                            \n_ C37LINK   C37LINK   000674  IBM COBOL   Linked to                            \n_ C37READF  C37READF  0004DA  IBM COBOL   Dyn call                             \n_ C370SUB1  C370SUB1  0005DC  IBM COBOL   Dyn call                             \n_ C370SUB2  C370SUB2  0003E4  IBM COBOL   Curr PGM                             \n  *** End of data ***", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "43dd4fb25898-1", "text": "*** End of data ***                                                          \n \n \n \n \nPF1 Help       2            3 End        4 Return     5            6           \nPF7 Backward   8 Forward    9           10           11           12\nSelect any program in the list having symbolic data by typing an S to the left of the program name. The source listing\ndisplay facility runs in a special mode and positions the listing at the point where it transferred control.\n 1007", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4c13ba36bb1d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nOnce the source listing display is in calltrace mode, display program variables the same way as they are for the currently\nbreakpointed program.\nThe CHANNEL Command\nThe CHANNEL command enables you to list each of the active channels and view each of the containers within each\nchannel.\nTo display the channels and containers, use one of these two commands:\n\u2022Enter the CHANNEL command on the command line from any breakpoint\n\u2022Enter a c line command next to any program in the CALLTRACE display\n                 CA InterTest for CICS  CHANNEL/CONTAINER STORAGE  \nCOMMAND ===>                                                                  \n \n  Type S to display main storage.                                     More:   \n \n  Channel          Container     Curr CPGID Length    Character Data          \n_ LNK0CHAN-01      LNK0CONT-00      x 00037 0008106 * 2 LNK0CH02 CONTAI..... *\n_                    +000FD8                        * ********************** *\n_                    +001FB0                        * ********************** *\n_                    +002F88                        * ********************** *\n_                    +003F60                        * ********************** *\n_                    +004F38                        * ********************** *\n_                    +005F10                        * ********************** *\n_                    +006EE8                        * ********************** *\n_                    +007EC0                        * ********************** *\n_ LNK0CHAN-01      LNK0CONT-01      x 00037 0008106 * 1 LNK0CH01 CONTAI..... *\n_                    +000FD8                        * ********************** *\n_                    +001FB0                        * ********************** *\n_                    +002F88                        * ********************** *\n_                    +003F60                        * ********************** *\n_                    +004F38                        * ********************** *", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4c13ba36bb1d-1", "text": "_                    +004F38                        * ********************** *\n \nPF1 Help       2            3 End        4 Return     5            6          \nPF7 Backward   8 Forward    9           10           11           12\nEach entry in the display represents a container, or in the case of larger containers, a segment of a container. The display\nshows the following information:\nChannel\nThe name of the channel in which the container has been stored\nContainer\nThe name of the container, or the segment offset withing the container\nCurr\nAn X indicates that this container was passed to the current program\nCPGID\nThe code page identifier for this container in EBCDIC format\nLength\nThe full length of the container\nCharacter Data\nAn EBCDIC display of the first twenty-two bytes of each container or segment\n 1008", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eb8d668f563d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo view the storage within a container or segment, place an s on the line next to that container or segment and press\nEnter .\nThe Storage Facility\nWhile stopped in the source listing facility for the currently breakpointed program enter the STORAGE command on the\ncommand line. The following example is a sample Storage facility screen.\n                     CA InterTest for CICS     USER STORAGE  \n COMMAND ===>                                                                   \n \n   Type S to display main storage.                                              \n \n      Usage:  User24:     3.12KB      CICS24:     0.00KB                        \n              User31:   259.54KB      CICS31:     0.00KB                        \n \n   Type  Address  (length)  Storage at that location                            \n _ SU24  00200470 (0000810) 00000043 000004B0 0003D61B 0004B100 ..........O.....\n _ SU24  00200000 (0000470) 00B46EC4 C6C8C5C9 E4E24040 40404040 ..>DFHEIUS      \n _ SU31  1DC3FE30 (0001000) C8C1D5C3 1DC36FF8 1DC3CCC8 00000000 HANC.C?8.C.H....\n _ SU31  1DC3EE30 (0001000) E2E3D2E4 1DC392DC 1DC39700 00000FF0 STKU.Ck..Cp....0\n _ SU31  1DC3CCC0 (0002170) C8C1D5C3 1DC3FE38 1DC36FF8 00000000 HANC.C...C?8....", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eb8d668f563d-1", "text": "_ SU31  1DC34B20 (00081A0) 00000000 00000000 00000000 00000000 ................\n _ SU31  1DC0BA20 (0029100) C8C1D5C3 1DC05CC8 1DC05CC8 00000000 HANC.{*H.{*H....\n _ SU31  1DC037F0 (0008230) 1DC037C8 1DC061A8 1D3D3BCB 1DD44602 .{.H.{/y.....M..\n _ SU31  1DC00040 (00037B0) 1DC02CE0 00000000 1DC00058 00000000 .{.\\.....{......\n _ SU31  1DC00000 (0000040) 4C4CD9E4 E6D76E6E 00000000 00008190 <<RUWP>>......a.\n   *** End of data ***                                                          \n \n \n PF1 Help       2            3 End        4 Return     5            6           \n PF7 Backward   8 Forward    9           10           11           12   \nSelect any piece of storage from the list resulting in a core dump of the selected area.\nAt the time the screen is built each piece is inspected to see if there is valid leading and trailing crumple zone. If not, a\nmessage is produced indicating there is a corrupted storage area, the list shows an * next to the corrupted areas.\nThe Backtrace Facility\nThe Backtrace facility lets you view the logic flow of your program. It is designed to answer the question, \"How did I get to\nthis point?\"\nThe Backtrace facility enables you to do the following tasks:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eb8d668f563d-2", "text": "this point?\"\nThe Backtrace facility enables you to do the following tasks:\n\u2022View the Backtrace Summary for a summary of the program's execution path\n\u2022View the Source Listing Backtrace for a statement-by-statement look at the program's execution path\n\u2022Use special PF keys to trace the program's execution path\n\u2022Reposition the source listing to view the program's execution path from different backtrace positions\nIn addition to the Backtrace PF keys, all other source listing options (such as the Keep window), setting and removing\nbreakpoints, and the ability to scroll backward and forward from the current position are available in the Backtrace facility.\n 1009", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "811a45c9eb97-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAccess the Backtrace Facility\nTo access the Backtrace facility from the source listing facility and to view the Backtrace Summary, enter BTRACE  on the\ncommand line and press  Enter, or press PF11 from the Source Listing Breakpoint screen. InterTest for CICS positions the\nBacktrace Summary at the last executed statement , which is the current breakpoint location. To view your program's\nbacktrace statement-by-statement, press PF2 from the Backtrace Summary to access the Source Listing Backtrace.\nNOTE\nWhile you are using the Backtrace facility, the execution PF keys are disabled and replaced with special forward\nand backward tracing PF keys.\nFrom the Backtrace Summary, perform the following actions:\n\u2022Access the Source Listing Backtrace to view statement-by-statement details of the program's execution path by:\n\u2013Pressing PF2\n\u2013Marking a statement block with S to indicate a starting position, and then pressing Enter\n\u2022Assign a bookmark, consisting of one to four characters, to one or more backtrace positions for faster and easier\nnavigation through the Backtrace Summary\nThe following screen shows the Backtrace Summary.\n       CA InterTest for CICS  - BACKTRACE SUMMARY                            \nProgram= COBDEMO                                      From 0001 To 0011 Of 0011\n \nSpecify S then ENTER to display Source Listing BACKTRACE                 \n--------------------------------------------------------------------------------\nPFKS 1 Help      2 Backtrace 3 End        4            5 1st Stmt   6 Last Stmt\n     7 Backward  8 Forward   9 Next Wnd  10           11 Prev Bloc 12 Next Bloc\n--------------------------------------------------------------------------------\n S Bkmk       Stmt Block  | Source Listing                                     \n _ ____    #790.0...#791.0|  PROCEDURE DIVISION USING DFHEIBLK DFHCOMMAREA.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "811a45c9eb97-1", "text": "_ ____    #791.0...#801.0|      CALL 'DFHEI1'.                                \n _ ____    #801.0...#802.0|      CALL 'DFHEI1' USING DFHEIV0                   \n _ ____    #804.0...#804.0|      IF EIBAID = DFHCLEAR                          \n s ____    #812.0...#813.0|       MOVE '  Y    i 00557   ' TO DFHEIV0          \n _ ____    #813.0...#818.0|      CALL 'DFHEI1' USING DFHEIV0  TSQNAME TASKSTR\n _ ____    #822.0...#823.0|      IF EIBCALEN = 0                               \n _ ____    #878.0...#881.0|       MOVE '  }            00598   ' TO DFHEIV0    \n _ ____    #881.0...#887.0|      CALL 'DFHEI1' USING DFHEIV0  DFHC0070 DFHEICB \n _ ____    #887.0...#888.1|      CALL 'DFHEI1' USING DFHEIV0.                  \n * ____    #897.0... Bkpt |      ADD +1 TO TASKNUM.                            \n \n  CAIN2988 First and Last Backtrace Stmt Block\nFrom field\nIndicates the relative backtrace statement blocks displayed on the screen. There are a maximum of 580 backtrace\nstatement blocks that record a program's execution path. The oldest statement blocks are re-used as needed.\nTo reposition the Source Backtrace Summary, overtype the information in the From field with a relative statement\nblock number or with a one- to four-byte user-specified tag or bookmark.\nSelect (S) column", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "811a45c9eb97-2", "text": "Select (S) column\nPositions a display of the Source Listing Backtrace at a selected backtrace statement. Enter S next to any entry\nand press Enter. The Source Listing Backtrace displays from the specified backtrace position. Only one S  is\nallowed.\nNote: An * in the Select column indicates the current backtrace position.\n 1010", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "82786a1ba8e2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBookmark (Bkmk)\ncolumn\nAssigns a unique tag or ID to one or more backtrace positions.\nSpecify multiple bookmarks.\nEach bookmark must contain at least one non-numeric character. For example, P103, UB7, T1, A, and so on.\nEach bookmark must be unique.\nOnce a bookmark is assigned to a specific backtrace position , it remains attached to that backtrace position\nuntil the bookmark is replaced or removed by subsequent program execution.\n\u2022There are 580 backtrace positions, and the oldest entries are replaced.\n\u2022If a backtrace position is not replaced between breakpoints, use the bookmark to reposition your Backtrace\nSummary by specifying the   bookmark name in the From field of the Backtrace Summary screen.\nStatement (Stmt) Block column\nIdentifies a block of contiguously executed statement numbers.\nEach line entry is a pair of program locations identifying the first and last statement numbers or offsets for a piece\nof sequentially executed code.\nFor COBOL programs, the decimal value of the statement number indicates a specific verb in a statement. The\nfirst verb is 0, the second is 1, and so on.\nThe top left entry was executed first, and the bottom right entry was executed most recently.\nAfter each statement number or offset in the right column there was a break in sequential execution, such as a\nCALL to CICS or a branch to another location in the program. Each break results in a new line entry.\nPlus signs indicate offsets; for example, +204.\nSource Listing Summary column\nDisplays the source code associated with the first statement executed in the statement block, which is identified\nby the statement number in the left column. The left margin default is 01 for COBOL and PL/I programs, and 34\nfor Assembler programs.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "82786a1ba8e2-1", "text": "for Assembler programs.\nNote:  For display purposes, the starting column is either the left margin default or the Margin= value that was\nspecified on the Source Listing Breakpoint screen, whichever is greater.\nMessage Line\nDisplays any messages about the section of backtrace that you are currently viewing.\nThe Backtrace Summary\nThe Backtrace Summary summarizes the program's execution path using statement blocks. The statement block column\nis located on the left side of the screen and contains two columns of numbers:\n\u2022Statement numbers in the left column receive control from a branch, a command level CALL, a PERFORM, or a\nGOTO\n\u2022Statement numbers in the right column issue  the branch to the next statement identified\nBy tracing the execution path, block-by-block, follow the flow of your program's logic.\nExample\nTo use the information in the statement block columns, first look at the last entry, as in the previous screen:\n#897.0... Bkpt\nThis block answers the question: How did I get to the current breakpoint? In this case, the program entered statement 897\nand executed all of the machine instructions up to the current breakpoint.\nThe next question you might ask is: How did statement 897 receive control? To answer this question, you must look at the\npreceding statement block:\n#887.0...#888.1\n 1011", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a9b61c1e705a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe statement number in the right column, 881.1, is the statement that caused a branch to statement 897.\nNOTE\nYou might see a statement branch to itself, as in the following example from the previous figure:\n    #812.0...#813.0 \u2190\n  \u2192 #813.0...#818.0\nThis happens when a CICS command is issued and execution was returned to the same statement.\nBacktrace Summary Screen PF Key Assignments\nThe first Backtrace Summary screen always displays the most recently executed backtrace entries at the bottom of the\nbacktrace table. Use the From field  or the following PF keys to navigate through the Source Backtrace Summary.\nPF1 Help\nDisplays online Help for the current screen.\nPF2 Backtrace\nRedisplays the Source Listing Backtrace screen from the current backtrace position. The current backtrace\nposition is indicated by an asterisk (*).\nPF3 End\nDisplays the Source Listing Breakpoint screen at the last breakpoint.\nPF5 1st Stmt\nRepositions the Backtrace Summary to the first (oldest) entry in the Backtrace.\nPF6 Last Stmt\nRepositions the Backtrace Summary to the last (newest) entry in the Backtrace.\nPF7 Backward\nScrolls the Backtrace Summary backward (up) a full screen.\nPF8 Forward\nScrolls the Backtrace Summary forward (down) a full screen.\nPF11 Prev Bloc\nDisplays the previous statement block.\nPF12 Next Bloc\nDisplays the next statement block.\nNOTE\nA column of backtrace statement blocks is available on the Detailed Breakpoint screen. For more information,\nsee the Detailed Breakpoint Screen.\nThe Source Listing Backtrace", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a9b61c1e705a-1", "text": "see the Detailed Breakpoint Screen.\nThe Source Listing Backtrace\nTo switch to the Source Listing Backtrace and to view the backtrace statement by statement, press PF2 or type S next to a\nstatement block in the Select column of the Backtrace Summary to select a starting position and press Enter , as shown in\nthe previous screen.\nThe following screen shows the Source Listing Backtrace.\nCA InterTest for CICS  - PROTDEM FILE SOURCE LISTING BACKTRACE              \nCOMMAND ===>                                                                   \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01 \n                                        Search=                     \nOPTS 1 Proc div  2 Work-stor 3 Link sect 4 D-map      5 Clst/Pmap More:   + \n     6 Data xref 7 Proc xref 8 Err msgs  9 Srch fwd  10 Srch bwd            \n 1012", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5eff945c0a95-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPFKS 1 Help      2 Summary   3 End       4 Profile    5 1st Stmt   6 Last Stmt\n     7 Backward  8 Forward   9 Prev Stmt 10 Next Stmt 11 Prev Bloc 12 Next Bloc\n========> Backtrace at #00812  (00812 > 00813 executed     1 times) <=========\n   00810*          ITEM(TSQITEM)                                              \n   00811*          ENDEXEC.                                                   \n _ ====>      MOVE '  Y    i 00557   ' TO DFHEIV0                               \n _ 00813     CALL 'DFHEI1' USING DFHEIV0  TSQNAME TASKSTRUCTURE TSQLEN       \n   00814     DFHDUMMY TSQITEM.                                                \n   00815                                                                       \n   00816                                                                       \n   00817                                                                       \n _ 00818     IF EIBAID = DFHPF2                                                 \n _ 00819      OR EIBAID = DFHPF14                                              \n _ 00820      OR TASKSWITCH = DFHPF2                                          \n _ 00821         GO TO EXPANDEDDEMO.                                          \n _ 00822     IF EIBCALEN = 0                                                    \n _ 00823         GO TO SENDFIRSTSCREEN.                                      \n _ 00824     GO TO CONTINUETASK.\nRead the Source Listing Backtrace\nTo clearly specify the program\u2018s execution path statement-by-statement, source statements executed from the current\nbacktrace position  are highlighted. However, when you specify a non-backtrace Source Listing option or use PF7 or\nPF8 to reposition the Source Listing Backtrace, the highlighting of executed statements is temporarily suspended until a\nbacktrace PF key is entered.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5eff945c0a95-1", "text": "backtrace PF key is entered.\nWhen in Source Listing Backtrace mode, the current backtrace position  always appears on the line just above the first\nsource statement. This line displays as follows:\n======>BACKTRACE AT #nnnnn (nnnnn -> nnnnn executed  nnnnn  times)<=====\nThe information on the previous line indicates:\n\u2022#nnnnn: The program statement or offset number where the backtrace is currently positioned\n\u2022nnnnn -> nnnnn: The first and last statement numbers of the statement block\n\u2022nnnnn times: How many times a statement block was executed\nOn the Source Listing Backtrace, each relevant backtrace position is indicated in the listing by an arrow or a line:\n\u2022====> indicates the first statement in a statement block\n\u2022<==== indicates the last statement in a statement block\n\u2022===== indicates all other statements within a statement block\nSource Listing Backtrace PF Keys\nTrace your program's execution path on the Source Listing Backtrace display using the following PF keys:\nPF1 Help\nInitiates the InterTest for CICS online help facility.\nPF2 Summary\nDisplays the Backtrace Summary.\nPF3 End\nTerminates the backtrace session and redisplays the Source Listing Breakpoint screen at the last breakpoint.\n 1013", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d77d02fe036b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPF4 Profile\nAccesses the Source Listing Profile, where you set source listing features and PF9 and PF10 stepping amount\nsettings.\nPF5 1st Stmt\nRepositions screen to the first (oldest) entry in the backtrace.\nPF6 Last Stmt\nRepositions screen to the last (newest) entry in the backtrace.\n*\nPF7 Backward\nScrolls screen backward (up) a full screen.\n*\nPF8 Forward\nScrolls screen forward (down) a full screen.\nPF9 Prev Stmt\nRepositions the Source Listing Backtrace to the previously executed statement.\nPF10 Next Stmt\nRepositions the Source Backtrace to the next statement.\nPF10 Next\nnnn\nAutomatically traces forward the number of statements set in the Stepping Amount= field on the Source Listing\nProfile (PF4). Stepping Amount value is nnn.\nPF11 Prev Bloc\nDisplays the previous statement block.\nPF12 Next Bloc\nDisplays the next statement block.\n*PF keys 7 and 8 temporarily suspend backtrace highlighting until PF5, 6, 9, 10, 11, or 12 are specified.\nNavigate Through Program Execution\nTrace your program's execution path by performing the following actions:\n\u2022Using PF5, PF9, and PF11 to go backward\n\u2022Using PF6, PF10, and PF12 to go forward\n\u2022Setting the Source Listing Profile Stepping Amount   and Wait Amount, and then using PF9 and PF10 to\nautomatically trace the execution backward or forward\nWhen you first access the Source Listing Backtrace by pressing PF2 on the Backtrace Summary screen, the following\nscreen appears. Access this screen also from any other section of backtrace by pressing PF6, which positions the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d77d02fe036b-1", "text": "backtrace at the last statement executed (the current breakpoint).\n    CA InterTest for CICS  - PROTDEM FILE SOURCE LISTING BACKTRACE \nCOMMAND ===>                                                                   \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01 \n                                        Search=                                \nOPTS 1 Proc div  2 Work-stor 3 Link sect 4 D-map      5 Clst/Pmap More:   + \n     6 Data xref 7 Proc xref 8 Err msgs  9 Srch fwd  10 Srch bwd            \nPFKS 1 Help      2 Summary   3 End        4 Profile    5 1st Stmt   6 Last Stmt\n     7 Backward  8 Forward   9 Prev Stmt 10 Next Stmt 11 Prev Bloc 12 Next Bloc\n========> Backtrace at #00897  (00897 > curr. executed     1 times) <=========\n _ 00895 CONTINUETASK.                                                        \n 1014", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2495d2a5f3bb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n   00896**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED                          \n A   ==>     ADD +1 TO TASKNUM.                                                \n _ 00898     IF TASKNUM = 1                                                    \n _ 00899         MOVE 'DMAPASR'  TO MAPNAME.                                   \n _ 00900     IF TASKNUM = 2                                                    \n _ 00901         MOVE 'DMAPSUM'  TO MAPNAME.                                   \n _ 00902     IF TASKNUM GREATER 2                                              \n _ 00903         GO TO SENDENDMSG.                                           \n _ 00904     GO TO REWRITETSQ.                                                \n _ 00905 REWRITETSQ.                                                          \n   00906*EXEC CICS WRITEQ TS                                                   \n   00907*          REWRITE                                                     \n   00908*          QUEUE(TSQNAME)                                             \n   00909*          FROM(TASKSTRUCTURE)\nTo reposition the source listing to the first statement of the current statement block or to the beginning of the previously\nexecuted statement block, press PF11 Prev Bloc.\nExample\nIf PF11 was pressed from the Source Listing Backtrace screen shown previously, the following screen appears.\nCA InterTest for CICS  - PROTDEM FILE SOURCE LISTING BACKTRACE  \nCOMMAND ===>                                                                   \nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \nOPTS 1 Proc div  2 Work-stor 3 Link sect 4 D-map      5 Clst/Pmap More:   + \n     6 Data xref 7 Proc xref 8 Err msgs  9 Srch fwd  10 Srch bwd", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2495d2a5f3bb-1", "text": "PFKS 1 Help      2 Summary   3 End        4 Profile    5 1st Stmt   6 Last Stmt \n     7 Backward  8 Forward   9 Prev Stmt 10 Next Stmt 11 Prev Bloc 12 Next Bloc \n========> Backtrace at #00897  (00897 > curr. executed     1 times) <========= \n     00885*          ENDEXEC.         \n   _ 00886      MOVE ' 00604   ' TO DFHEIV0         \n   _ ====>      CALL 'DFHEI1' USING DFHEIV0.         \n   _ 00888     IF EIBAID = DFHENTER GO TO CONTINUETASK.       \n   _ 00889     IF EIBAID = DFHCLEAR GO TO SENDENDMSG.         \n   _ 00890     IF EIBAID = DFHPF3   GO TO SENDENDMSG.         \n   _ 00891     IF EIBAID = DFHPF15  GO TO SENDENDMSG.         \n   _ 00892     IF EIBAID = DFHPF2   GO TO EXPANDEDDEMO.        \n   _ 00893     IF EIBAID = DFHPF14  GO TO EXPANDEDDEMO.        \n   _ 00894     GO TO SENDFIRSTSCREEN.         \n   _ 00895 CONTINUETASK.        \n     00896**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED          \n  A   ==>     ADD +1 TO TASKNUM.         \n   _ 00898     IF TASKNUM = 1          \n   _ 00899         MOVE 'DMAPASR'  TO MAPNAME.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2495d2a5f3bb-2", "text": "_ 00899         MOVE 'DMAPASR'  TO MAPNAME.\nTo reposition the source listing to the beginning of the next backtrace statement block, press PF12  Next Bloc.\nExample\nIf you pressed PF12  from the Source Listing Backtrace shown previously, the following screen appears.\nCA InterTest for CICS - PROTDEM FILE SOURCE LISTING BACKTRACE     \nCOMMAND ===>                                                                   \n 1015", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9f4058ccef97-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nProgram= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                        Search=                                 \nOPTS 1 Proc div  2 Work-stor 3 Link sect 4 D-map      5 Clst/Pmap More:   + \n     6 Data xref 7 Proc xref 8 Err msgs  9 Srch fwd  10 Srch bwd            \nPFKS 1 Help      2 Summary   3 End        4 Profile    5 1st Stmt   6 Last Stmt \n     7 Backward  8 Forward   9 Prev Stmt 10 Next Stmt 11 Prev Bloc 12 Next Bloc \n========> Backtrace at #00897  (00897 > curr. executed     1 times) <========= \n     00885*          ENDEXEC.         \n   _ 00886      MOVE ' 00604   ' TO DFHEIV0         \n   _ ====>      CALL 'DFHEI1' USING DFHEIV0.         \n   _ 00888     IF EIBAID = DFHENTER GO TO CONTINUETASK.       \n   _ 00889     IF EIBAID = DFHCLEAR GO TO SENDENDMSG.         \n   _ 00890     IF EIBAID = DFHPF3   GO TO SENDENDMSG.         \n   _ 00891     IF EIBAID = DFHPF15  GO TO SENDENDMSG.         \n   _ 00892     IF EIBAID = DFHPF2   GO TO EXPANDEDDEMO.        \n   _ 00893     IF EIBAID = DFHPF14  GO TO EXPANDEDDEMO.        \n   _ 00894     GO TO SENDFIRSTSCREEN.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9f4058ccef97-1", "text": "_ 00894     GO TO SENDFIRSTSCREEN.         \n   _ 00895 CONTINUETASK.        \n     00896**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED          \n  A   ==>     ADD +1 TO TASKNUM.         \n   _ 00898     IF TASKNUM = 1          \n   _ 00899         MOVE 'DMAPASR'  TO MAPNAME.\nEnding a Source Listing Backtrace Session\nTo toggle between the Source Listing Backtrace and the Backtrace Summary, press PF2.\nTo turn off the backtrace display mode, press Clear or PF3 . InterTest for CICS redisplays the Source Listing Breakpoint\nscreen positioned at the last breakpoint.\nAdditional Breakpoint Displays\nThe Breakpoint Information screen and the Detailed Breakpoint screen provide you with more information than the Source\nListing Breakpoint screen. However, you cannot test from the Breakpoint Information screen, and the Detailed Breakpoint\nscreen requires you to specify most functions by completing another menu or entering single-line commands.\nLook at the Breakpoint Information screen from any Source Listing Breakpoint screen:\n\u2022When you are at a Source Listing Breakpoint, press PF3  DET BKPT to look at the Breakpoint Information screen.\n\u2022To return to the Source Listing Breakpoint screen, press PF4 Source.\nNOTE\nIf the Source List BKPT= ON, InterTest for CICS displays the Source Listing Breakpoint version. If the Source\nList BKPT= OFF, InterTest for CICS displays the Detailed Breakpoint version.\nThe following screen shows the Breakpoint Information screen when Source List BKPT=ON. The format does not include\nlines of the program listing.\nProgram COBDEMO stopped by CA InterTest in statement 882.0 (Offset +01A8E)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9f4058ccef97-2", "text": "CAIN3628 Automatic breakpoint; ASRA abend (0C7) detected and prevented.\n     Caused by invalid decimal arithmetic data format.                   \n                                                                  Backtrace\nTran= DEMC from term L6D1 monitored as PROG=COBDEMO             #776.0   #786.0\nDFHCOMMAREA does not exist.                                     #786.0   #787.0\n                                                                #789.0   #789.0\n                                                                #797.0   #798.0\n 1016", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "98de00d33a2c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                                                #786.0   #787.0\n                                                                #814.0   #815.0\n                                                                #815.0   #816.0\nDepress PF3 for Source Listing Display.                         #821.0   #823.0\n                                                                #823.0   #833.0\n                                                                #833.0   #838.0\n                                                                #838.0   #839.0\n                                                                #841.0   #851.0\nThe two fields shown are at address 01C2A4 and 2B817C:          #851.0   #866.0\n000000                               *...             *         #866.0   #872.0\n1C                                   *.               *         #872.0   #873.1\n                                                                #882.0 to here. \n==> CNTL=GO,TASK=00290,A                                             Margin:     \n Overtype the above or use a PF key or press ENTER to abend without a dump.    \n 1 Help       2            3 Source      4           5 Resume      6 Menu\n 7            8            9 1 instruc  10 1 verb   11 Backtrace  12 Status\nNOTE\nThe information displayed on the Breakpoint Information screen is also available on the Detailed Breakpoint\nscreen, which is discussed in the Detailed Breakpoint screen.\nAll fields except the command line are protected.\n\u2022Program COBDEMO ...\nIdentifies the statement or offset location where the breakpoint occurred in your program. For COBOL programs, the\ndecimal value of the statement number indicates which verb halted execution. The first verb is 0, the second verb is 1,\nand so on.\n\u2022TRAN=", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "98de00d33a2c-1", "text": "and so on.\n\u2022TRAN=\n\u2022Identifies the transaction and terminal ID where the program is executing, and how monitoring was requested, such as\nfor a program, transaction, or terminal.\n\u2022Backtrace\nShows the backtrace as described in the section Tracing Program Execution. Additional backtrace entries are\naccessed using PF11. To return, press Clear .\n\u2022The two fields ...\nIndicates, in hexadecimal and character format, the address and contents of main storage relevant to the breakpoint.\n\u2022CNTL=GO\nDisplays the command line with a CNTL default command. Override this command with any other InterTest for CICS\ncommand or transaction ID, such as HELP or CORE. It is followed by a line that indicates any errors or messages.\nEnter also a fast-path command to jump to a menu, such as =1.2.1 to go to the Program Monitoring menu.\n\u2022Overtype ...\nLists the PF keys that are available from the Breakpoint Information screen. For more information, see the Detailed\nBreakpoint PF Keys.\nThe Detailed Breakpoint Screen\nThe Detailed Breakpoint display is designed for experienced InterTest for CICS users with knowledge of InterTest for CICS\ncommands and CICS. It contains more diagnostic information than the Source Listing Breakpoint display. It is displayed\nwhen the Source Listing Profile setting Source List BKPT=OFF.\nFrom the Detailed Breakpoint display access the Breakpoint Primary Option Menu, but you cannot use the one-character\ncommands that are available on the Source Listing Breakpoint display, such as m to modify or d to display. Instead,\naccess the Main Storage Menus (fast-path entry is =1.3) or enter a one-line command in the command field on the bottom\nof the screen.\nA Detailed Breakpoint screen appears when Source List BKPT=OFF. A sample screen follows.\n 1017", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b10a0bbcb294-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nProgram COBDEMO stopped by CA InterTest in statement 882.0 (Offset +01A8E)\n  CAIN3628 Automatic breakpoint; ASRA abend (0C7) detected and prevented.\n       Caused by invalid decimal arithmetic data format.                            \n                                                                 Backtrace   \nTran= DEMC from term L6D1 monitored as PROG=COBDEMO            #776.0  #786.0\nDFHCOMMAREA does not exist.                                    #786.0  #787.0\n                                                               #789.0  #789.0\n  00879     GO TO SEND FIRST SCREEN.                           #797.0  #798.0\n  00880 CONTINUE TASK.                                         #786.0  #787.0\n  00881**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED           #814.0  #815.0\n  00882     ADD +1 TO TASKNUM.                                 #815.0  #816.0\n  00883     IF TASKNUM = 1                                     #821.0  #823.0\n  00884         MOVE 'DMAPASR'  TO MAPNAME.                    #823.0  #833.0\n  00885     IF TASKNUM = 2                                     #833.0  #838.0\n  00886         MOVE 'DMAPSUM'  TO MAPNAME.                    #838.0  #839.0\n                                                               #841.0  #851.0\n  The two fields shown are at address 033DA4 and 2AE17C:       #851.0  #866.0\n  000000                               *...             *      #866.0  #872.0", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b10a0bbcb294-1", "text": "000000                               *...             *      #866.0  #872.0\n  1C                                   *.               *      #872.0  #873.1\n                                                               #882.0 to here.\n \n ==> CNTL=GO,TASK=00378,A                                             Margin:     \n Overtype the above or use a PF key or press ENTER to abend without a dump.       \n 1 Help       2            3 Source      4           5 Resume      6 Menu   \n 7            8            9 1 instruc  10 1 verb   11 Backtrace  12 Status  \nNOTE\nAll fields except the command line are protected.\nProgram COBDATA ...\nIdentifies the statement or offset location where the breakpoint occurred in your program. For COBOL programs,\nthe decimal value of the statement number indicates which verb halted execution. The first verb is 0, the second\nverb is 1, and so on.\nCAIN3628 ...\nIndicates what kind of breakpoint occurred. For a review of what each letter means, see the Examine the Source\nListing Breakpoint screen. If an automatic breakpoint occurred, the reason for it follows.\nTRAN= ...\nIdentifies the name of the transaction and terminal ID where the program is executing and how monitoring was\nrequested (such as for a program, transaction, or a terminal).\nBlank area in front of Backtrace column\nFor PL/I and Assembler programs, this area displays the machine instruction that triggered the breakpoint, the\nmachine instruction that last executed, and its offset or absolute address. (This is not shown in this screen.)\nBacktrace\nShows the backtrace, which is described in the section Tracing Program Execution. Additional backtrace entries\nare accessed using PF11.\nDFHCOMMAREA ...\nIndicates the COMMAREA status and size.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b10a0bbcb294-2", "text": "DFHCOMMAREA ...\nIndicates the COMMAREA status and size.\n00883 ...\nDisplays source listing code, only if you:\n 1018", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "50982f371e57-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Saved the listing in the InterTest for CICS symbolic file\n\u2022Choose Source List BKPT=OFF on your Source Listing Profile screen. Without this option specified, InterTest\nfor CICS does not display this screen at all. The Breakpoint Information screen displays instead.\nThese two fields ...\nIndicates, in hexadecimal and character format, the address and contents of main storage relevant to the\nbreakpoint.\nCNTL=GO...\nDisplays the command line with a default CNTL command. Override this command with an InterTest for CICS\ncommand or transaction ID. It is followed by a line that indicates any errors or messages.\nOvertype ...\nLists the PF keys that are available from the Detailed Breakpoint Display screen.\nRead the Backtrace on the Detailed Breakpoint Screen\nUse the Source Listing Facility Backtrace feature to examine the path your program took during execution, and to help\nsolve logic problems. On the Detailed Breakpoint screen, only one column at-a-time of backtrace entries is available.\nTo access additional backtrace entries, press PF11 or switch to the Source Listing Breakpoint display mode for a more\ndetailed backtrace listing.\nThe backtrace shows the path of the most recently executed code.\n\u2022The top left entry was executed first, and the bottom right entry was executed last.\n\u2022Each line entry is a pair of program locations identifying the first and last statement numbers or offsets for a piece of\nsequentially executed code.\n\u2022The decimal value after statement numbers for COBOL code indicates which verb in the statement was executed last.\nThe first verb is given a decimal value of 0, the second 1, and so on.\n\u2022After each statement number or offset in the right column there is a break in sequential execution, such as a CALL to", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "50982f371e57-1", "text": "CICS or a branch to another location in the program. Each break results in a new line entry.\n\u2022If a program loops through a section of code more than once, the backtrace displays the number of times the loop was\nexecuted below the line entry, instead of repeating the execution sequence.\n\u2022Plus signs indicate offsets; for example, +204.\nTo return to the breakpoint display, press PF3 or Clear .\nThe detailed breakpoint PF keys follow.\nPF1 Help\nInitiates the InterTest for CICS online help facility.\nPF2\nUnassigned.\nPF3 Source\nDisplays the Source Listing version of the breakpoint.\nPF4\nUnassigned.\nPF5 Resume\nResumes execution at the next instruction using the amount set on PF10.\nPF6 Menu\nDisplays the Breakpoint Primary Option Menu.\nPF7\nUnassigned.\n 1019", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5d32fbe4a3e2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPF8\nUnassigned.\nPF9 1 Instruc\nExecutes the next machine instruction and then stops.\nPF10 001 Verb\nFor COBOL, executes the next COBOL verb and then stops.\nPF10 001 Stmt\nFor PL/I, executes the next PL/I statement and then stops.\nPF 10 Registers\nFor Assembler, toggles registers on and off the screen.\nPF11 Backtrace\nDisplays the column of backtrace available at this breakpoint.\nPF12 Status\nDisplays a monitoring status report for the monitored entry (program, transaction, or terminal) that caused the\nbreakpoint.\nPF22 Shift Left\nShifts source code left; COBOL and PL/I programs shift 10 characters at a time; Assembler programs shift to 02,\n40, 50, and then 61. If you have only 12 PF keys, use the Margin= field to shift your source code.\nPF23 Shift Right\nShifts source code to the right the same amounts as PF22.\nContinue Execution\nTo continue execution from the Detailed Breakpoint or the Breakpoint Information screen, perform these steps:\n\u2022Press PF9 or PF10 to single-step.\n\u2022Press  PF5 Resume to continue execution starting with the next instruction.\n\u2022Press PF6 Menu  to access the Breakpoint Primary Option Menu, where you abend, override an automatic breakpoint,\nstep, or access the Resume Menu for additional execution options. For details, The Breakpoint Primary Option Menu.\n\u2022Enter a CNTL command on the command line.\n\u2022Enter GO, NEXT, or RUN on the command line.\nSingle-Stepping\nPress PF9 or PF10  to execute a single machine instruction, COBOL verb, or PL/I statement, as indicated in the PF key", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5d32fbe4a3e2-1", "text": "definition on the bottom of the screen. Use this method to see what data values are being moved into main storage.\nNotes:\n\u2022The step amount for PF9 and PF10 cannot be changed. However, select alternative step amounts by entering CNTL\ncommands or by using the Resume Menu options. Access the Resume menu using PF6, and select Option 4 Resume\n(the fast-path command is  =4).\n\u2022When you use PF10 to single-step through nested COBOL IF statements, it might appear that InterTest for CICS is not\nexecuting one verb at a time. This is a function of how the compiler generates the object code. To follow closely the\nexecution of nested IFs, use PF9 (execute 1 instruction) instead.\nResume Execution\nAccess the Resume Menu by pressing PF6 from the Detailed Breakpoint screen, then selecting Option 4 Resume.\nAlternatively, jump to the Resume menu by entering =4 in the command line on the Detailed Breakpoint screen.\nUsing the Resume Menu, perform the following functions:\n 1020", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a111477fd64e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Resume program execution until the next breakpoint occurs or the transaction ends\n\u2022Resume program execution from a new location, such as a COBOL paragraph name, Assembler or PL/I label, COBOL\nor PL/I statement number or offset\n\u2022Move or disable the current breakpoint\n\u2022Execute a specified number of PL/I instructions or COBOL verbs before stopping\n\u2022Abend the transaction with or without a dump\nCNTL Commands\nInterTest for CICS provides a default command at each breakpoint display, as shown following:\n\u2022The default command at an automatic breakpoint is:\nCNTL=GO,task=xxxxx,A\nA means abend the task without a dump.\n\u2022The default command at other breakpoints is:\nCNTL=GO,task=xxxxx,C \nC means continue execution from where you left off.\nTo execute the default command, press Enter .\nTo modify the default command, overtype the existing command and press Enter .\nContinue Processing During Breakpoint Processing\nTo continue processing from either the current line or a specified line number or label until the next breakpoint is\nencountered, an abend occurs, or the program runs to normal completion, enter:\nGO line-number | label\nLine-number\nIndicates any line number within an ASSEMBLER, COBOL, or PL/1 program from which you want the execution\nto continue.\nDefault : The current statement.\nLabel\nIndicates any valid paragraph or procedure label within an ASSEMBLER, COBOL, or PL/1 program (up to 31\ncharacters in length) from which you want the execution to continue.\nDefault : The current statement.\nNOTE\nGO is available only during breakpoint processing.\nContinue Processing During Breakpoint Processing Until Specified Verbs Are Executed\nNOTE\nThe NEXT command replaces the obsolete STEP command.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a111477fd64e-1", "text": "NOTE\nThe NEXT command replaces the obsolete STEP command.\nNEXT verb-count\nVerb-count\nIndicates number of verbs to execute before the next display of the Breakpoint Display screen.\nDefault : Value of Stepping Amount in Profile.\nNOTE\nNEXT is available only during breakpoint processing.\n 1021", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d055aa51cce8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nContinue Processing Until a COBOL PERFORM Has Been Completed Avoiding Breakpoints\nNEXT OVER\nSpecifies that the NEXT command is used to execute through a verb, instruction, or statement and return to that line. This\nis to avoid breakpoints.\nContinue Processing After a COBOL Program Breakpoint Until the Next Call Or Perform Statement\nNEXT RETURN\nSpecifies that the NEXT command is used to continue execution until the next CALL or PERFORM verb. Execution stops\nwhen it hits a CALL or PERFORM execution.\nContinue Processing During Breakpoint Processing Ignoring Preset Breakpoints\nTo continue processing from the current statement ignoring all preset breakpoints until an abend occurs or the task runs to\nnormal completion, enter:\nRUN\nNOTE\nRUN is available only during breakpoint processing.\nContinue Processing During Breakpoint One Verb at-a-Time\nTo continue processing from the current statement one verb at a time displaying the Breakpoint Display screen for a\nspecified time interval until either a specified number of verbs have been executed or the next \"CALL\" statement is\nencountered, enter:\nAUTOSTEP interval stop-count\n\u2022Interval\nIndicates number of seconds (between 1 - 59) to display each Breakpoint Display screen.\nDefault : Wait Amount in Profile.\n\u2022Stop-count\nIndicates number of verbs to execute before stopping.\nDefault : Stop value in Profile.\nNOTE\nAUTOSTEP is available only during breakpoint processing.\nSee More Code on the Detailed Breakpoint Display\nWhile viewing the Detailed Breakpoint display, you might not see all of the program's source code on your screen. To see\nmore code, perform the following steps:\n1.Tab to the Margin= field, enter a number from 0 to 99 to indicate the starting position of the left margin, and press\nEnter.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d055aa51cce8-1", "text": "Enter.\nInterTest for CICS redisplays the source code beginning in the position you requested. A Margin= value of 0 begins the\ndisplay from position 1.\n2.Press PF22  to shift the source code left. Press PF23  to shift the source code right. COBOL and PL/I programs shift 10\ncharacters at a time; Assembler programs shift to positions 02, 40, 50, and then 61.\nRestore the Detailed Breakpoint Display\nOnce you leave the Detailed Breakpoint screen (for example, by pressing PF3 to view the source listing), restore the\nDetailed Breakpoint display by pressing PF3 or Clear . If you accessed an InterTest for CICS facility such as CNTL,\nCORE, HELP, or FILE, you might need to press PF3 or Clear more than once to restore the breakpoint display.\n 1022", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "44e78cc1ee77-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSwitch Between Breakpoint Screens\nIf the first InterTest for CICS breakpoint screen you see is a Detailed Breakpoint display, you might want to switch to the\nSource Listing Breakpoint Display version for your program testing. To switch from the Detailed Breakpoint screen to the\nSource Listing Breakpoint screen, perform these steps:\n1.Press PF3 Source. You should now see the Source Listing Breakpoint Display.\n2.Enter PROFILE in the command line and press Enter. The Source Listing Profile screen appears.\n3.Enter ON in the Source List BKPT= field and press Enter. You are returned to the Source Listing Breakpoint display.\nOnce you complete these steps, InterTest for CICS displays the Source Listing Breakpoint version at future breakpoints in\nyour test session. For more information, see the Source Listing Facility.\nTo switch from the Source Listing Breakpoint to the Detailed Breakpoint display, perform these steps:\n1.Enter PROFILE  in the command line of a Source display and press Enter. The Source Listing Profile appears.\n2.Enter OFF in the Source List BKPT= field and press Enter.\n3.Press PF3 DET BKPT. You should now see the Detailed Breakpoint display version.\nNOTE\nThe default value of the Source List BKPT= field is set by your System Administrator when installing InterTest for\nCICS.\nIndirect Commands\nThe InterTest for CICS indirect commands facility enables you to define a set of commands that execute automatically,\nor indirectly, at a predetermined location in a monitored COBOL or PL/I program. Invoke these commands from an\nunconditional, conditional, or request breakpoint.\nIn effect, indirect commands are executed at breakpoints within your program just as other InterTest for CICS line\ncommands issued from the Source Listing Display, such as MOVE and GO, are used to alter the flow of your program's", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "44e78cc1ee77-1", "text": "logic. The difference is that indirect commands are executed automatically without issuing a breakpoint display. Once the\nindirect commands are performed, your program continues to execute normally.\nIndirect commands save you from having to recompile a program or manually correct an area of code every time it is\nencountered during a debugging session. With the indirect commands facility, you can perform the following actions:\n\u2022Change the flow of control in your program\n\u2022Test conditions based on specified variables\n\u2022Change the value of specified variables\n\u2022Create and execute commands as a group, like adding a new subroutine\n\u2022Automatically resume execution of your program at the same or different location\n\u2022Define abbreviations for variables with long names\nNOTE\nIndirect commands are not available for Assembler programs.\nHow Can You Use Indirect Commands?\nUse indirect commands to correct the following sample program problems:\n 1023", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "34da2b4c8cbb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022A variable is not being initialized during processing. Using indirect commands initialize the variable every time the\nprogram is run and continue execution without recompiling.\n\u2022A new routine is needed in your program. Insert the code using indirect commands and continue executing your\nprogram without recompiling.\n\u2022A section of code is bad. To continue executing or testing without recompiling, write and invoke indirect commands to\ndirect InterTest for CICS to go around the bad source code or execute a new series of indirect command statements.\n\u2022You must debug a COBOL or PLI program, which is invoked by a web process or run as background task and is not\nassociated with a specific terminal or userID. You must specify your own criteria when the programs breakpoints\nshould be taken or ignored.\nOverview of Steps\nTo invoke indirect commands in your program, perform these steps:\n1.Enter the statement numbers and indirect command statements on the Indirect Commands screen. To access the\nIndirect Commands screen, use Option #11 from a Source Listing screen, or select the Command option on the\nProgram Monitoring menu.\n2.Use the Monitoring Menus or Source Listing facility to set a breakpoint (unconditional, conditional, or request) where\nthe indirect commands will take effect. As you set the breakpoint, you must access the Breakpoint Options menu\nand specify the first statement number of the Indirect Command as an option to that breakpoint. Option #12\n(Bkpt Opt) on the Source Listing screen provides access to the Breakpoint Options menu.\n3.Specify the terminal ID (terminal ID, .ANY, or .NO) or user ID for the indirect commands to take effect.\nThe following section describes each of these steps in detail.\nNOTE\nSet the breakpoint and give the starting indirect command number before you code the indirect commands. The", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "34da2b4c8cbb-1", "text": "NOTE\nSet the breakpoint and give the starting indirect command number before you code the indirect commands. The\norder is up to you. However, new users often find it easier to code the indirect commands first, and then attach\nthem to breakpoints.\nSet a Breakpoint to Execute an Indirect Command\nBefore accessing the indirect commands facility, first set an unconditional, conditional, or request breakpoint that includes\nan option to execute an Indirect Command statement number.\nFollow the steps listed next when setting an unconditional or conditional breakpoint from the Source Listing Breakpoint:\n1.From the Source Listing Breakpoint, set an unconditional or conditional breakpoint that will invoke the indirect\ncommands.\nThe following table summarizes how to set the breakpoints from the Source Listing Facility:\nBreakpoint Source Listing Entries\nUnconditional Specify:\nOption # 12 (Bkpt Opts).\nU or ) to the left of one or more statements. The U breakpoint\nstops before  the statement. The ) breakpoint stops after the\nstatement.\nPress Enter.\nConditional Specify:\nOption #  12 (Bkpt Opts).\nC to the left of one or more statements.\nPress Enter.\nRequest Use Monitoring Menus.\nNote:  To jump to the Program Monitoring Menu from a breakpoint\ndisplay, enter =1.2.1  on the command line.\n 1024", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a40a884abe1e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe following screen shows how to set an unconditional breakpoint for indirect commands from the Source Listing facility.\nNotice the required Option # 12 entry at the top of the screen.\nCA InterTest for CICS - PROTDEM FILE PROTDEM FILE SOURCE LISTING BREAKPOINT\n COMMAND ==>                 \u2193\n Program= COBDEMO  Option # 12    Stmt #                            Margin= 01 \n                   Label/Search Arg= \n OPTS 1 Proc div  2 Work-stor 3 Link sect 4 D-map      5 Clst/Pmap More:   + \n     6 Data xref 7 Proc xref 8 Err msgs  9 Srch fwd  10 Srch bwd            \n PFKS 1 Help     2            3 Det BKPT   4 Profile    5 Resume      6 Menu \n      7 Backward 8 Forward    9           10 Do 1 Verb 11 Backtrace 12 Status\n-----------------------------------------------------------------------------  \n    00788     03  OPTSPROTHLF        PIC X(8).                                  \n    00789\n \n    00790 PROCEDURE DIVISION USING DFHEIBLK DFHCOMMAREA.       \n \n  U 00791     CALL 'DFHEI1'. \n \u2191                                                   \n\u2022Enter Option # 12 and U on Source Listing for Indirect Commands.\n\u2022After pressing Enter, InterTest for CICS displays the Breakpoint Locations menu with the location you selected on the\nSource Listing already indicated.\n\u2022On the Breakpoint Locations menu, specify the (still to be written) one- to five-digit statement number of the first\nindirect command that you want to be executed at the breakpoint you are setting. For example, enter 10 or 50.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a40a884abe1e-1", "text": "CA InterTest MONITORING COMMAND BUILDER - COBOL BREAKPOINT LOCATIONS      11\n     SET breakpoint options for   PROG=COB2DEMO for location:\n             000791     CALL 'DFHEI1'.\n                                                                       After: \n            Enter 'n' to stop only every n'th time:                         ____\n            Term ID (or .ANY or .NO) where breakpoints will take effect:    \n            Term ID (or .ANY) that will receive the breakpoints:            \n            Statement no. of indirect command(s) to be executed:           50___\n            User ID (or .ANY) who will execute the program:             .ANY\n PF1 Help       2            3 End        4 Return     5            6\n PF7            8            9           10           11           12\n\u2022Press Enter. InterTest for CICS processes the breakpoint as usual, and displays a message to that effect.\n\u2022InterTest for CICS displays the Indirect Commands screen containing the following fields:\nTerm ID\nIndicates the terminal where the specified indirect commands execute. This value must match the terminal ID\nspecified at the breakpoint that invokes these indirect commands. Enter one of the following values:\nxxxx \u2014 indicates a specific terminal.\n.ANY \u2014 indicates that these commands will execute at all terminals.\n 1025", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3796573afbc6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nIf indirect commands are specified for both .ANY and your specific terminal, the indirect commands\nspecified for your  terminal take precedence.\n.NO\u2014 indicates that these commands execute with no terminal.\nDelete ALL\nDeletes all previously specified indirect commands for the program you are testing. Enter one of the following\noptions:\nNO \u2014  indicates that the indirect commands at the specified terminal will not be deleted (default).\nYES\u2014 indicates that the indirect commands at the specified terminal will be deleted.\nLine\nIndicates the one- to five-digit sequence number, from 1 to 99999, of the indirect command, which must be\nfollowed by at least one blank space. This number must be the first item entered except for continued commands,\nand must begin in the first position of the input line.\nCommand\nDisplays the actual command text to be performed during Indirect Command execution from a breakpoint. For a\ncomplete listing of indirect commands, see Indirect Command Syntax.\nCode Indirect Commands\nUse the Indirect Commands screen to code all indirect commands for your program. For more information about syntax,\nsee COBOL Variable Syntax and PL/I Variable Syntax.\nWhen you are finished coding an indirect command statement, perform these steps:\n1.Press Enter. InterTest for CICS translates everything you entered into uppercase characters and checks the command\nfor syntactical accuracy. If the command is correct, one of the following messages is displayed:\nCAIN1261 Indirect command(s) added.\nIndirect command(s) replaced.\n2.When you have coded all of your indirect commands, press PF3 or Clear.\nFrom Source Listing\nIf you are working from the Source Listing facility, you return to the Source Listing display.\nIndirect Command Examples\nThe following examples explain how to use indirect commands to correct the errors in the InterTest for CICS demo", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3796573afbc6-1", "text": "program COBDEMO.\n1.To prevent the ASRA problem caused by the invalid decimal arithmetic data value assigned to the COBOL data-item\nTASKNUM:\n\u2013Using Source Listing Option # 12 with a U line command, set an unconditional breakpoint at statement number 500.\n\u2013Specify 10 as the indirect command statement number that you want to execute at the breakpoint.\n\u2013Using the Source Listing Option # 11, access the indirect commands facility. Then, enter the indirect commands on\nthe Indirect Commands screen, as shown next.\nCA InterTest MONITOR COMMAND BUILDER    COBDEMO  INDIRECT COMMANDS     24 \n \n    Term ID (or .ANY or .NO): X001                   Delete ALL: NO             \n \n LINE  COMMAND                                                                 \n------------------------------------------------------------------------------ \n 00010  /* INITIALIZE TASKNUM */\n 1026", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e443a5923681-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 00020  MOVE 1 TO TASKNUM\n 00030  EXIT \n \n \n  1 Help       2            3 End        4           5                6         \n  7 Backward   8 Forward    9 Top       10 Bottom   11               12         \n  CAIN1261 Indirect commands added.\nNOTE\nSetting TASKNUM to 1 alters the demo results. The clear key must be used to complete the termination of\nthe demo when the \"You have completed the sample InterTest for CICS test session\" screen appears.\n2.To avoid the storage violation that occurs in COBDEMO:\n\u2013Using Source Listing option 12 with a U line command, set an unconditional breakpoint at statement number 978\n\u2013Specify 50 as the indirect command statement number that you want to execute at the breakpoint\n\u2013Using the Source Listing Option # 11, access the indirect commands facility, and then add the following commands.\nCA InterTest MONITOR COMMAND BUILDER    COBDEMO  INDIRECT COMMANDS 24   \n    Term ID (or .ANY or .NO): X001                   Delete ALL: NO      \n-----------------------------------------------------------------------                                   \n                        \n \n 00010  /* INITIALIZE TASKNUM */\n 00020  MOVE 1 TO TASKNUM\n 00030  EXIT \n 00040  *\n 00050  /* CIRCUMVENT STORAGE VIOLATION */\n 00060  GOTO 'SENDMAP00'\n \n  1 Help       2            3 End        4           5                6 \n  7 Backward   8 Forward    9 Top       10 Bottom   11               12  \n  CAIN1261 Indirect commands added.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e443a5923681-1", "text": "CAIN1261 Indirect commands added.\n3.To perform the code that was bypassed at statement 1369 at another location where it will not cause a storage\nviolation:\n\u2013Using the Source Listing Option # 12 with a U line command, set an unconditional breakpoint at statement number\n974\n\u2013Specify 80 as the indirect command statement number that you want to execute at the breakpoint\n\u2013Using the Source Listing Option # 11, access the indirect commands facility, then add the following commands.\nCA InterTest MONITOR COMMAND BUILDER    COBDEMO  INDIRECT COMMANDS    24 \n \n    Term ID (or .ANY or .NO): X001                   Delete ALL: NO        \n----------------------------------------------------------------------------                              \n                             \n  LINE  COMMAND                                                            \n \n 00010  /* INITIALIZE TASKNUM */\n 00020  MOVE 0 TO TASKNUM\n 00030  EXIT \n 00040  *\n 00050  /* CIRCUMVENT STORAGE VIOLATION */\n 00060  GOTO 'SENDMAP00'\n 00070  *\n 00080  /* INSERT MOVE AT A SAFE LOCATION */\n 00090  IF NEWDATA > ZEROES THEN MOVE NEWDATA TO STGAREA1\n 1027", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "760ab5e75c59-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 00100  EXIT\n \n  1 Help       2            3 End        4           5                6    \n  7 Backward   8 Forward    9 Top       10 Bottom   11               12    \n  CAIN1261 Indirect commands added.\n4.To debug a program that is invoked by multiple transaction IDs and take breakpoints only when a particular transaction\nID is specified:\n\u2013Using the Source Listing Option # 10 with a U line command, set an unconditional breakpoint at the beginning of\nthe procedure division.\n\u2013Specify the indirect command statement number that you want to execute at the breakpoint.\n\u2013Specify the FROM Terminal, where the breakpoint should take effect, as .ANY.\nNow, all other program breakpoints that are set may be taken only when the conditions specified by the indirect\ncommand 10 are true.\nCA InterTest MONITOR COMMAND BUILDER    COBDEMO  INDIRECT COMMANDS    24 \n \n    Term ID (or .ANY or .NO): X001                   Delete ALL: NO        \n----------------------------------------------------------------------------                                 \n                          \n  LINE  COMMAND       \n  00010 IF EIBTRNID =  \u2018DEC2\u2019 THEN BREAK\n  00020 RUN \n  00030 EXIT\n \n  1 Help       2            3 End        4           5                6    \n  7 Backward   8 Forward    9 Top       10 Bottom   11               12    \n  CAIN1261 Indirect commands added.\nView Indirect Commands on the Status Report\nThe status report displays a list of all active indirect commands, and all active breakpoints and other monitoring options.\nEach line on the report shows the type of breakpoint, the presence of indirect commands, and the terminal at which they", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "760ab5e75c59-1", "text": "are set to take effect.\nAccess\nTo access the status report from the Source Listing display or breakpoint enter the command STATUS, or press PF12\nStatus. The following screen shows how indirect commands are represented on the InterTest Status Report:\n         CA InterTest for CICS - MONITORING STATUS               \n COMMAND ===>                                                                 \n \n   Type + to expand or   collapse option levels displayed below,              \n          or R to remove option(s).                                           \n \n     Option     Description                Attributes                         \n _   COBDEMO    Program monitor entry      COBOL                              \n _ + | .ANY     User monitoring options    Active                             \n _   | CARAR01  User monitoring options    Active                             \n       |        Symbolic listing file      PROTSYM                         \n _     | UBP    Unconditional breakpoint   'CONTINUE TASK'            \n       |        Option ID                  4B893C0                      \n 1028", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6bcb9d5b3f06-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n       |        From, to terminals         .ANY, .ANY                       \n       |        Execute indirect command   100                                \n _     | CMD    Indirect commands defined  .ANY                               \n       |        Option ID                  90AB36F1                           \n _     | SLB    Source listing breakpoints .ANY                               \n                *** End of data ***                                           \n \n \n \n PF1 Help       2 Refresh    3 End        4 Return     5 Collapse   6 Expand  \n PF7 Backward   8 Forward    9           10           11           12\nThe previous figure shows the status report expanded for the program COBDEMO when monitored by user ID CARAR01.\nNotice the unconditional breakpoint entries and indirect command entries, which are discussed next.\nUBP\nThe UBP entry identifies the unconditional breakpoint set at the procedure-name Continue-Task. Notice the last\nline of the UBP description is Execute indirect command ... 100.\nCMD\nThe CMD entry identifies the indirect commands. Notice the indirect commands are assigned the option ID\n90AB36F1.\nTo return to the Source Listing display from the Status Report, press PF3 or Clear .\nEdit Indirect Command Definitions\nTo view, add, change, or delete indirect commands directly from the Source Listing facility, enter 11 in the Option # field.\nInterTest for CICS displays the indirect commands defined for the default terminal, which is either the terminal you are\nworking at or the terminal specified on the Source Listing Profile.\nITST Access to Indirect Commands\nThe ITST Monitoring Menus and the CNTL menu allow direct access to the indirect commands facility, where you can\ncode or edit indirect commands to be executed by breakpoints.\nFrom any menu or Source Listing screen, perform these steps:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6bcb9d5b3f06-1", "text": "From any menu or Source Listing screen, perform these steps:\n1.Access the ITST Program Monitoring menu (ITST 2.1).\nThe fast-path command entry from a breakpoint is:\nCommand ==> =1.2.1 .\n2.On the Program Monitoring menu, complete the Program name  and type S next to the Commands (indirect\ncommands) Option.\n3.Press Enter to continue to the next screen. The Indirect Commands screen displays.\nOptionally, specify the terminal ID where the indirect commands will take effect and the user ID that executes the program\nwhen the indirect commands are to take effect.\nNOTE\nGenerally, accept the defaults. Press PF1 for help in completing these fields, if necessary.\nTo edit indirect commands previously coded for a program, ensure the terminal ID and user ID entries match those initially\nused to code the indirect commands.\nPress Enter  to continue. InterTest for CICS displays the Indirect Commands screen for the requested program, terminal\nID, and user ID.\nFor details on how to insert insert, copy, edit, and delete the commands, see Format Indirect Commands.\n 1029", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ead685b50061-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIndirect Command Syntax\nThis section discusses execution flow and syntax.\nExecution Flow Control\nIf a breakpoint is set to invoke indirect commands, when you run your program the commands are automatically executed\nwithout stopping first. Execution is returned to the program according to the exi t command that you specified in your\nindirect commands.\nTo return execution to your program following the indirect commands processing, use one of the following exit commands:\nBREAK\nInterTest for CICS halts indirect commands processing and issues a breakpoint display from where the indirect\ncommands were invoked in the program.\nGOTO\nInterTest for CICS resumes execution at the program statement number, offset, paragraph name, or indirect\ncommand statement number specified after the GOTO command.\nEXIT\nInterTest for CICS resumes program execution at the breakpoint location from which the indirect commands were\ninvoked and continues debugging the program until the next breakpoint.\nRUN\nInterTest for CICS resumes program execution at the breakpoint location from which the indirect commands were\ninvoked and ignores all subsequent breakpoints.\nCommand Syntax\nThe syntax for the basic commands available in the indirect commands facility is described next.\nNote: All bold characters are required in the syntax of the command.\nEquate Command\nThis command equates a one- to eight-character symbol of your choice to a relatively long data name. A maximum of ten\nEQuate symbols can be active concurrently.\nThe syntax is:\nEQuate symbol [TO] data-name\nsymbol\nIndicates any user-defined symbol that observes the rules for data names.\ndata-name\nSpecifies the corresponding variable name.\nBrackets, [ ], indicate an optional entry.\nExample\nEQ TN TASKNUMBER\nExit Command\nThe Exit command returns control to the statement following the last executed PErform indirect command. If no PErform", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ead685b50061-1", "text": "is active, indirect processing is terminated and control is returned to the program, where execution continues from the\nbreakpoint. Any relational operands entered with this command are ignored.\n 1030", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cf7dcce94b13-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nExample\nEX\nGoto Command\nThis command resumes execution at a specified location. The syntax controls where execution resumes.\nTo resume execution at the specified indirect command sequence number, use this syntax:\nGOto *nnnnn\nTo resume execution at the specified statement number, use this syntax:\nGOto #nnnnn\nTo resume execution at the specified hexadecimal displacement, use this syntax:\nGOto +nnnnn\nTo resume execution at the specified paragraph-name, use this syntax:\nGOto 'paragraph-name'\nExample\nGO *1150\nIF, THEN Statement\nThis statement tests a conditional expression. If the expression is true, the THEN portion is processed.\nThe syntax is:\nIF expression THEN indirect command\nexpression\nSpecifies any valid condition.\nindirect command\nSpecifies any valid indirect command.\nExample\nIF (A+B)*C=D\n  THEN GOTO *1150\nBreak and Pause Commands\nThe BReak and PAuse commands terminate indirect command processing and redisplay the Breakpoint display. Any\noperands included with these commands are ignored by InterTest for CICS.\nExample\nBR\nMove Command\nThis command moves the specified source-item to the target data-name. Follow COBOL MOVE statement rules when\nformatting an indirect command Move.\nThe syntax is:\n 1031", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "977bdab76850-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMove [source-item] TO data-name\nNote: Brackets,[ ], indicate a choice of source-items.\nValid source-items follow.\n\u2022[ALL,]' char-data '\n[ALL,]\" char-data \"\n'char-data ' or \"char-data \" is a non-numeric character string.\n\u2022[ALL,] x'hex-data ' [ALL,] x\"hex-data \"\nx'hex-data ' or x\"hex-data\" is a hexadecimal string.\n\u2022numeric literal\nnumeric literal  is valid only if the target data-name is a numeric variable.\n\u2022figurative constant\nfigurative constant  is any valid COBOL figurative constant.\n\u2022floating-point literal\nfloating-point literal  is valid only if the target data-name is COMPUTATIONAL-1, COMPUTATIONAL-2 (COBOL) or\nFLOAT (PL/I).\n\u2022arithmetic expression\narithmetic expression  is any valid InterTest arithmetic expression.\n\u2022bit literal\nbit literal  is any bit literal string.\nNOTE\nFor more information about each of these source items, see Format Indirect Commands.\ndata-item\nRefers to a COBOL or PL/I variable name. Qualifiers and subscripting are allowed.\ndata-name\nRefers to another COBOL or PL/I variable name. If the data-name is a COBOL Index cell, the MOVE command\nmoves exactly the data specified into the Index cell. No mathematical calculation is performed.\nPerform Command\nThis command transfers control to the specified indirect command sequence number as a subroutine call. A maximum of\nfive PErform commands can be active concurrently.\nThe syntax is:\nPErform nnnnn\nnnnnn\nIndicates the indirect command sequence number to which control is transferred.\nExample\nPE 2250\nRun Command", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "977bdab76850-1", "text": "Example\nPE 2250\nRun Command\nThe RUN command resumes program execution at the breakpoint location from which the indirect commands were\ninvoked and ignores all subsequent breakpoints.\nExample\nRUN\n 1032", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7e6511c9d473-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFormat Indirect Commands\nRules\nIndirect commands and their arguments are free-form. However, there are several rules to keep in mind as you format\nyour commands:\n\u2022All arguments must be separated by at least one blank space.\n\u2022Only one indirect command displays on a line (with the exception of the IF command), but one indirect command\nspans several lines.\n\u2013The first line of a command must begin with a line number followed by a blank space\n\u2013Consecutive lines of a single command must begin with at least one blank space\nExample\n10 IF DATA-COUNTER <> 0\nTHEN M 0 TO DATA-COUNTER\n20 BR\n\u2022New indirect commands are entered by:\n\u2013Overtyping an existing command\n\u2013Entering new indirect commands on blank lines below existing ones\nExample\nIf you have indirect command 10 followed by indirect command 20, to insert commands between the two you would tab\nto the next blank line, enter indirect commands 11 through 19. Press Enter. InterTest for CICS places the commands in\nnumeric sequence.\n\u2022Duplicate indirect commands by changing only the sequence number of an existing indirect command. The original\ncommand is not affected; it is duplicated at the specified sequence number.\nNote: Be sure to overtype the entire line number when duplicating a command. Failure to do so can result in an\nerroneous move. For example, if you want command 00010 to be copied to line 00045, you must overtype the entire\nline number 00010 with 00045 or 45 b b b (where b is a blank). If you only overtype the first two digits with 45, the\ncommand will be copied to line 45010, not 00045.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7e6511c9d473-1", "text": "command will be copied to line 45010, not 00045.\n\u2022Enter comments in place of commands. To enter a comment, specify a sequence number followed by at least one\nspace, and then enter either an asterisk (*) or a backslash and an asterisk (/*) followed by at least one space and your\ncomment.\nExample:\n00035  * THIS IS A COMMENT LINE\n\u2022Indirect commands are verified after you press Enter, but some errors might not be detected until the indirect\ncommands are actually processed.\n\u2022Delete an entire set of indirect commands by specifying YES in the Delete ALL= field.\nDelete a specific indirect command by overtyping the line number with DEL.\nData Names and Variables\nIndirect commands reference any data name in the Data Division Linkage section of the program that you are testing.\nFor COBOL (prior to COBOL II Release 1.3)\n\u2022One group-item qualifier is allowed. It is any group that contains the item in question:\n 1033", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d0f7f65f8d27-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2013Immediate parent\n\u201301-level\n\u2013Any level in between the immediate parent and the 01-level\n\u2022Up to three levels of subscripting are allowed. Subscripts include:\n\u2013Positive integer numeric literal\n\u2013Another variable defined as a positive integer numeric field (no sign or decimal portion)\n\u2013INDEX item (either INDEXED BY or USAGE INDEX)\nFor COBOL II (Releases 1.3 and higher)\n\u2022One program-ID qualifier is allowed.\nNOTE\nIf your COBOL II source listing contains a nested program that has a local variable with a name identical to a\nvariable in the main program, use the appropriate program-ID to indicate which variable you are referencing.\n\u2022One group-item qualifier is allowed. It can be any group containing the item in question:\n\u2013Immediate parent\n\u201301-level\n\u2013Any level in between the immediate parent and the 01-level\n\u2022Up to seven levels of subscripting are allowed. Subscripts include:\n\u2013Positive integer numeric literal\n\u2013Another variable defined as a positive integer numeric field (no sign or decimal portion)\n\u2013INDEX item (either INDEXED BY or USAGE INDEX)\nExample\nDATE OF INVOICE\nTABLE-ENTRY(4,TABLE-INDEX)\nFor PL/I Programs\n\u2022Only items declared as STATIC, AUTOMATIC, BASED, and POINTER type variables that are declared as parameters\nto the entry point of the MAIN procedure are supported.\n\u2022One procedure-name qualifier is allowed. If your PL/I source contains an internal procedure that has a local variable\nwith a name matching a variable in the main procedure, use the appropriate procedure-name to indicate to which\nvariable you are referencing.\n\u2022Up to 15 structure-name qualifiers are allowed. You must follow PL/I notation conventions; for example: A.B.C.D.E.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d0f7f65f8d27-1", "text": "\u2022Up to 15 levels of subscripting are allowed. A subscript includes:\n\u2013Integer numeric literal\n\u2013Another variable defined as an integer numeric field (no decimal portion)\n\u2022The subscript value must be within the actual declared bounds of the array.\nExample\nIf the array is declared as (100:200), subscript values must be within the range of 100 to 200, inclusive.\n\u2022The base address for a variable is supplied with the base locator notation. One item supplies the base address for\nthe next item, which in turn supplies the base address for the next variable, up to a limit of 15 items. This feature is\nintended for BASED variables, but it is used to map any declaration over any addressable storage.\nExample:\nDATE OF INVOICE\nTABLE_ENTRY(4,TABLE_INDEX)\n 1034", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aaa6517efd77-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nLiterals in Indirect Commands\nNumeric   is a string of one to eighteen digits with no intervening commands or decimal point, such as 7954. If the target\nvariable contains an implied decimal point, then the decimal point must also be implied in the literal.\nFloating point   is appropriate only for COMPUTATIONAL-1 and COMPUTATIONAL-2 target variables that consist of the\nfollowing:\n\u2022A sign\n\u2022A string of up to seven digits with an optional decimal point\n\u2022The character E followed by an optional signed exponent\nAlphanumeric   is a character string enclosed within single quotation marks ( '), or double quotation marks (\"), such as\n'RALPH9' or \"RALPH9\".\nHexadecimal   is a string of an even number of characters consisting of 0 to 9 and A to F, enclosed within single\nquotation marks ( '), or double quotation marks (\"), and prefixed with X, such as X'F0'.\nBit  is a string of the characters 1 and 0 enclosed in single quotation marks ( '), or double quotation marks (\") such\nas '11110000'. The maximum length of a bit literal is determined by its context and the maximum allowed indirect\ncommand length.\nFigurative Constants in Indirect Commands\nUse the following figurative constants in formatting indirect commands:\nValid Figurative Constants\nZERO\nZEROS\nZEROESnumeric value 0 HIGH-VALUE\nHIGH-VALUEScharacter value X'FF'\nSPACE\nSPACESblank (X'40') LOW-VALUE\nLOW-VALUEScharacter value X'00'\nQUOTE\nQUOTESquotation mark (') ALL literal any literal  to fill a field\nConditional Expressions in Indirect Commands\nIndirect commands support the following types of expressions:\n\u2022Conditional expressions, used with indirect commands IF statements", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aaa6517efd77-1", "text": "\u2022Conditional expressions, used with indirect commands IF statements\n\u2022Arithmetic expressions, used with indirect commands IF and MOVE statements\nOperands in these expressions are one of the following expressions:\n\u2022Figurative constants\n\u2022Literals\n\u2022Variables\nNote: Qualified data names and subscripts are also supported.\nThe following is a list of acceptable relational operators and their meanings.\n=\nEqual to\n< >\nNot equal to\n<\nLess than\n 1035", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "da596c8b2c80-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n>\nGreater than\n< =\nLess than or equal to\n> =\nGreater than or equal to\nCOBOL Variable Syntax\nThe general syntax for a COBOL variable in InterTest for CICS indirect commands is as follows:\n[prog-id:] data-name [IN grp-name][ ({sub-name OR ind-name OR number}[, ...]) ]\nor\n[prog-id:] data-name [OF grp-name][ ({sub-name OR ind-name OR number}[, ...]) ]\nprog-id\nIdentifies the program-ID of the program to which the variable belongs. If used, the prog-id  must immediately be\nfollowed by a colon (:). If omitted, the default is the main program's program-ID.\ndata-name\nIndicates COBOL data item.\ngrp-name\nIdentifies the COBOL identifier of a group item to which the data-name belongs. This clause lets qualification of an\nidentifier that displays in more than one group.\nsub-name\nSpecifies a COBOL identifier to use as a subscript. This identifier must follow all the COBOL rules for valid\nsubscripts.\nind-name\nIndicates a COBOL index-name.\nnumber\nSpecifies a positive integer that is used as a valid subscript for a data-name.\nNOTE\nOR is not part of the command syntax.\nExamples:\nThe following are examples of valid COBOL data-names:\nTOTAL-AMT\nCUST-NO OF CUST-REC\nMONTHLY-BAL (8) \nYEARLY-TOT (W-YR, 3, W-DEPT)\n SUBRTN1:ITEM-A\nSUBRTN1:ITEM-B IN INP-REC(3, SUB-2, 4, SUB-3)\nPL/I Variable Syntax", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "da596c8b2c80-1", "text": "PL/I Variable Syntax\nThe general syntax for a PL/I variable in InterTest for CICS indirect commands is as follows:\nexpression-1 [-> expression-2 ...]\n 1036", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "969938f3c6f5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n->\nDefines the address for symbol. It indicates that the expression on the left provides the address on which the\nthe expression on the right is based. If the expression on the left is a PL/I POINTER variable, the contents of the\nPOINTER variable is use. The -> notation is provided for referencing PL/I BASED variables whose addresses\ncannot be resolved at compile time, but are used for referencing any PL/I variable.\nexpression  is defined as follows:\n[procnm:] var-name-1[,var-name-2 ...] [({sub-name OR number}[, ...])]\nprocnm\nIndicates the label of the procedure to which the variable belongs. If used, procnm  must immediately be followed\nby a colon (:). If omitted, it defaults to the MAIN procedure name.\nvar-name\nIdentifies the PL/I variable name.\nsub-name\nDefines a PL/I variable name to use as a subscript. This identifier must follow all PL/I rules for valid subscripts.\nnumber\nSpecifies a positive integer that is a valid subscript for var-name .\nNOTE\nOR is not part of the command syntax.\nExamples\nThe following are examples of valid PL/I variables:\nTOTALAMT\nCUSTREC.CUSTNO.PREFIX\nMONTHLYBAL (8)\n YEARLYTOT (WYR, 3, WDEPT)\n SUBRTN1:ITEMA\nSUBRTN1:INPREC.ITEMB (3, SUB2, 4, SUB3)\nExample\nPRT1 is a POINTER variable that provides the base address for BASED variable BASEDSTRUCT1.\nPRT1 -> BASEDSTRUCT1\nExample\nPRT1 is a POINTER variable that provides the base address for BASED variable BASEDSTRUCT1. It contains another", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "969938f3c6f5-1", "text": "POINTER variable, PRT2, which is used as the base address for the BASED variable BASEDSTRUCT2, containing\nITEMA.\nPRT1 -> BASEDSTRUCT1.PRT2 -> BASEDSTRUCT2.ITEMA\nExample\nSTRUCTA is not a pointer variable but a structure. The address of STRUCTA is used to map the variable names defined\nin STRUCTB.\nSTRUCTA -> STRUCTB\n 1037", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bf5f9890245f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nComposite Support\nComposite support lets you test and debug a subprogram as if it were a separate program. This means you can set\nbreakpoints and other monitoring options individually for any subprogram. InterTest for CICS provides full symbolic\nsupport for subprograms if you provide the symbolic information when the programs are compiled or assembled.\nFollow these steps:\n1.Access the Composite Support screen using one of the following ways:\n\u2013Program Monitoring Menu.\n\u2013Source Listing Facility.\n\u2013CNTL Function Selection Menu.\n2.Provide the monitoring information online on the Composite Support menu. See Composite Module Testing for more\ninformation about the Composite Support menu.\nComposite Support Screen\nThe Composite Support screen lists link-edit information for the subprograms. The link-edit information is obtained\ndynamically using the Binder API, or from a PROTSYM where it was saved by the optional batch job step (IN25LINK).\nSubprograms with prefixes CEE, DFH, DFS, ILB, IBM, IGZ and @@ are automatically excluded from the list unless you\nspecifically name the subprograms in the batch job step. All listed subprograms are automatically selected for monitoring\nby default.\nThe following figure shows the Composite Support screen:\n       CA InterTest for CICS  - Composite Support Builder                   \nCOMMAND ===>                                                      SCROLL: PAGE\nDefine composite support for BIGMOD   and press PF5.        Row 00001 of 00004 \n \n * *           *          *        *        *          *\n _ Link name   Monitor    Offset   Length   Language   Comments                 \n S MAINMOD     BIGMOD        160     78A8   COBOL                          \n S SUBMODA     ASMMODA      7CA0     1200   ASSEMBLER", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bf5f9890245f-1", "text": "S SUBMODB     ASMMODB      8EA0     1001   ASSEMBLER\n S SUBMODC     ASMMODC      9EA1      93A   ASSEMBLER                          \n _ SUBMODD     ________     A8DB      A11  __________ symbolics not available\n \n \n \n \n PF1 Help       2            3 End        4            5 Process    6 RFind     \n PF7 Backward   8 Forward    9           10           11           12  \nThe Composite Support screen contains the following fields:\nFilter\nEnables you to specify various criteria to filter the subprograms that are displayed on the Composite Support\nscreen.\nSelect All\nEnables you to select or deselect all subprograms for testing.\nValues:A (selects all subprograms that meet the specified filter criteria), N (deselects all subprograms that meet\nthe specified filter criteria)\nSelection\nIndicates whether a subprogram is selected for testing or not.\n 1038", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "893785d96214-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nValues:S (subprogram is selected), _ (subprogram is not selected).\nLink-name\nIdentifies the name of a COBOL program, Assembler CSECT, or PL/I Control Section as listed in the link-edit\nmap.\nMonitor\nSpecifies the name under which InterTest for CICS monitors the program.\nThe following rules apply to monitor names:\n\u2022Each monitor name must be unique.\n\u2022The monitor name of a subprogram cannot have a PPT entry unless the subprogram is the main subprogram.\n\u2022A monitor name can be identical to a link-name.\n\u2022If you want symbolic information for a program or subprogram, its monitor name must be identical to the name\nused in the post-processor batch job step that provides the symbolic information to InterTest for CICS.\n\u2022Use the monitor name *DWARF* to monitor a subprogram with DWARF symbolic data.\nOffset\nDisplays the hexadecimal offset of the program as listed in the link-edit map.\nLength\nDisplays the hexadecimal length of the program as listed in the link-edit map.\nLanguage\nIdentifies the language in which the program is written. If InterTest for CICS has symbolic information for the\nprogram, it uses the language specified in the post-processor batch job. If InterTest for CICS does not have\nsymbolic information, it assumes that the subprogram is written in the language specified in the PPT entry of the\ncomposite module.\nComments\nDisplays optional comments or warnings, which describe symbolic information available for the program:\nsymbolics not available\nInterTest for CICS does not have symbolic information for the program.\nsymb data after linkedt\nThe program might have been recompiled or reassembled after the link-edit. Composite support\ninformation might be outdated.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "893785d96214-1", "text": "information might be outdated.\nUse PF8 and PF7 to scroll forward and backward through the list of programs.\nSelect Subprograms for Testing\nSelect only the subprograms that you want to test to reduce overhead. Use the Select All and Selection fields to select the\nsubprograms that you want to test. Change monitor names of subprograms to meet your testing needs.\nSelect or Deselect Individual Subprograms\n\u2022To select a subprogram, type S in the Selection field next to the subprogram that you want to select.\n\u2022To deselect a subprogram, clear the Selection field next to the subprogram that you want to deselect.\nSelect or Deselect All Subprograms\n\u2022To select all subprograms, type A in the Select All field.\n\u2022To deselect all subprograms, type N in the Select All field.\n 1039", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eba5176512f7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSelect or Deselect Subprograms That Meet Specific Criteria\nTo select subprograms that meet specific criteria, follow these steps:\n1.Apply a filter that specifies the desired criteria.\nThe list of the displayed subprograms changes.\n2.Type A in the Select All field.\nOnly the subprograms that meet the specified criteria get selected.\nTo deselect subprograms that meet specific criteria, follow these steps:\n1.Apply a filter that specifies the desired criteria.\nThe list of the displayed subprograms changes.\n2.Type N in the Select All field.\nOnly the subprograms that meet the specified criteria get deselected.\nNOTE\nSelection or deselection does not affect the subprograms that do not match the specified criteria.\nExample:\nComposite module BIGMOD is displayed on the Composite Support screen in InterTest for CICS. You want to test\nSUBMODD, but you do not want to test SUBMODA, SUBMODB, and SUBMODC.\n       CA InterTest for CICS  - Composite Support Builder                   \nCOMMAND ===>                                                      SCROLL: PAGE\nDefine composite support for BIGMOD   and press PF5.        Row 00001 of 00004 \n \n \n * *           *          *        *        *          *                        \n _ Link name   Monitor    Offset   Length   Language   Comments                 \n S MAINMOD     BIGMOD        160     78A8   COBOL                          \n S SUBMODA     ASMMODA      7CA0     1200   ASSEMBLER                          \n S SUBMODB     ASMMODB      8EA0     1001   ASSEMBLER\n S SUBMODC     ASMMODC      9EA1      93A   ASSEMBLER", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eba5176512f7-1", "text": "_ SUBMODD     ________     A8DB      A11  __________ symbolics not available\n \n \n \n \n PF1 Help       2            3 End        4            5 Process    6 RFind     \n PF7 Backward   8 Forward    9           10           11           12  \nFollow these steps:\n1.Clear the Selection fields for SUBMODA, SUBMODB, and SUBMODC to exclude those subprograms from testing.\n2.Provide a monitor name for SUBMODD to test the subprogram separately.\nYou get the following screen:\n       CA InterTest for CICS  - Composite Support Builder                   \n COMMAND ===>                                                      SCROLL: PAGE\n Define composite support for BIGMOD   and press PF5.        Row 00001 of 00004 \n \n \n * *           *          *        *        *          *                        \n _ Link name   Monitor    Offset   Length   Language   Comments                 \n S MAINMOD     BIGMOD        160     78A8   COBOL                          \n _ SUBMODA     ASMMODA      7CA0     1200   ASSEMBLER                          \n 1040", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5edcce11682e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _ SUBMODB     ASMMODB      8EA0     1001   ASSEMBLER\n _ SUBMODC     ASMMODC      9EA1      93A   ASSEMBLER                          \n S SUBMODD     ASMMODD      A8DB      A11   ASSEMBLER \n \n \n \n \n \n PF1 Help       2            3 End        4            5 Process    6 RFind     \n PF7 Backward   8 Forward    9           10           11           12 \nNOTE\nChanges made to the Composite Support screen are saved temporarily and remain in effect until the monitoring\nof the module is disabled. If you want to monitor the module again, you need to re-enter the changes.\nSORT Command - Sort Subprograms\nUse the SORT command on the Composite Support screen to sort subprograms by the values in a specific column in an\nascending or descending order.\nThe command has the following format:\nSORT [ columnname | OFFSET ] [ order | A | D ]\ncolumnname\n(Optional) Specifies the name of the column that you use as the restrictive criteria for sorting.\nValues: LINKNAME, MONITOR, OFFSET, LENGTH, LANGUAGE, COMMENTS\nDefault:  OFFSET\norder\n(Optional) Specifies the order that you use for sorting.\nValues: ASCENDING, DESCENDING\nDefault:  ASCENDING\nExample:\nThe following command sorts subprograms by the Length column in a descending order:\nSORT LENGTH D\nFIND and RFIND Commands - Search for Subprograms\nUse the FIND and RFIND commands on the Composite Support screen to search for subprograms in a specific column or\nall columns.\nThe FIND command has the following format:\nFIND searchdata [ columnname ]\nsearchdata\nSpecifies your search string.\nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5edcce11682e-1", "text": "FIND searchdata [ columnname ]\nsearchdata\nSpecifies your search string.\nNOTE\nIf the string contains spaces, place the string in single quotes.\ncolumnname\n(Optional) Specifies the name of the column where you want to perform the search.\nValues: LINKNAME, MONITOR, OFFSET, LENGTH, LANGUAGE, COMMENTS\nDefault:  All columns\n 1041", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "54e422e8f5a6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe RFIND command repeats the FIND command and displays the next match.\nExample:\nThe following command searches for string ASMMODA in the Monitor column:\nFIND ASMMODA MONITOR\nScroll Commands and Options\nUse the scroll commands, the SCROLL field, or PF7 and PF8 keys on the Composite Support screen to navigate in the\nlist of subprograms.\nScroll Commands\nUse the TOP and BOTTOM commands in the command line to navigate to the beginning or end of the subprogram list.\nUse the UP and DOWN commands with a number between 1 and 9999 to navigate up and down the list.\nExample:\nTo navigate 5 rows down the list, enter the following command:\nDOWN 5\nScroll Options\nUse the PF7 and PF8 keys to scroll up and down in the subprogram list. The SCROLL field defines the default number of\nrows by which you scroll.\nThe SCROLL field has one of the following values:\n\u2022PAGE\n\u2022HALF\nEnables you to scroll by half a page.\n\u2022CSR\nEnables you to scroll to the position of the cursor in the list. If you scroll down, the line indicated by the cursor appears\nat the top of the screen. If you scroll up, the line indicated by the cursor appears at the bottom of the screen. If the\ncursor is not positioned in the list, you scroll by page.\n\u20221-14\nSpecifies the number of rows by which you scroll.\nCommand Line Scroll Options\nEnter one of the following values in the command line to override the default number of rows by which you want to scroll,\nand press PF7 or PF8:\nMAXIMUM\nEnables you to scroll to the beginning or end of the subprogram list.\n1-9999\nSpecifies the number of rows by which you scroll.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "54e422e8f5a6-1", "text": "1-9999\nSpecifies the number of rows by which you scroll.\nExample:\nType 10 in the command line, and press PF8 to scroll 10 rows down in the list of subprograms.\nFilter Subprograms\nUse the filter fields above each column on the Composite Support screen to filter subprograms. When you apply several\nfilter values to different columns, only rows that match all values are displayed.\nThe filter fields support the following wildcards:\n 1042", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bee1ad99ceb6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n*\nMatches 0 or more characters.\n%\nMatches one character that can be a space.\n+\nMatches one character that cannot be a space.\nTo filter subprograms in the Offset and Length columns, you can also use > or < (the greater or less than signs) for\nnumeric comparisons.\nExamples:\nThe following value entered in the Link name filter field displays rows whose Link name starts with A and ends with 25:\nA*25\nThe following value entered in the Link name filter field displays rows whose Link name has exactly seven characters and\nthe first five characters are ASBIN:\nASBIN++\nThe following value entered in the Link name filter field displays rows whose Link name has six or seven characters and\nthe first five characters are ASBIN:\nASBIN+%\nThe following value entered in the Offset filter field displays rows with the Offset value greater than 100A:\n>100A\nAssembler Programs with Multiple CSECTs\nAssembler programs may consist of multiple CSECTs that are assembled together as one program. To monitor these\nAssembler programs, enter a plus sign (+) in the Monitor field for each CSECT that follows the first CSECT.\nExample:\nSubprograms ASMA, ASMB, and ASMC are treated as one program. Set breakpoints and other options for all CSECTs\nunder the name ASMA, which is the monitor name specified for subprogram ASMA.\n       CA InterTest for CICS  - Composite Support Builder                   \n COMMAND ===>                                                      SCROLL: PAGE\n Define composite support for BIGMOD   and press PF5.        Row 00001 of 00004 \n \n \n * *           *          *        *        *          *                        \n _ Link name   Monitor    Offset   Length   Language   Comments", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bee1ad99ceb6-1", "text": "_ Link name   Monitor    Offset   Length   Language   Comments                 \n S ASMLINK     ASMLINK        48     2000   ASSEMBLER                         \n S ASMA        ASMA         2048      68B   ASSEMBLER                          \n S ASMB        +            2F98      1BC   ASSEMBLER  Multi-CSECT monitoring\n S ASMC        +            3B00      290   ASSEMBLER  Multi-CSECT monitoring\n \n \n \n \n PF1 Help       2            3 End        4            5 Process    6 RFind     \n PF7 Backward   8 Forward    9           10           11           12         \n 1043", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "97cfdba957ad-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nThe Composite Support screen might already have plus signs joining Assembler CSECTs. This means the\nCSECTs were treated as one program in the post-processor batch job step that provided symbolic information to\nInterTest for CICS.\nRemove Composite Support\nThis section describes how to remove composite support from a status report or from the menu.\nFrom a Status Report\nTo remove composite support, remove monitoring for the composite module.\nFollow these steps:\n1.Access the Monitoring Status Report (2.4).\n2.Scroll to the monitoring entry for the composite module, type R to the left of the entry, and press Enter .\nNOTE\nRemember, removing monitoring from the composite module also removes monitoring from all subprograms of\nthe composite module. As a result, all breakpoints and options set for all  subprograms of the composite module\nare removed.\nFrom the Menus\nTo remove composite support from the menus, follow these steps:\n1.Access the Program Monitoring menu (2.1).\n2.Specify the composite module name, and type  R to the left of the Monitor field. Press Enter  to remove monitoring for\nthat program.\nSet Breakpoints for Duplicate Composite Subprograms\nExample\nThe following example shows how to enable composite monitoring and set unconditional breakpoints for duplicate\nsubprograms:\nSuppose you have two composite load modules: MAINMOD1 and MAINMOD2. Both modules contain a subroutine with\nthe same name - SUBPROG. You want to set unique breakpoints for subroutine SUBPROG in each module.\nFollow these steps:\n1.Use LIST=MAINMOD1, type COMPOSITE in the command line, and enable composite monitoring. Repeat step 1 for\nMAINMOD2.\n2.Change the current program name to SUBPROG.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "97cfdba957ad-1", "text": "MAINMOD2.\n2.Change the current program name to SUBPROG.\n3.Type 24 in the Option # field to access the Program window, change the load module name to MAINMOD1, and press\nEnter.\n4.Set a breakpoint by typing U in the desired location.\nYou set an unconditional breakpoint for SUBPROG of MAINMOD1.\n5.In the Program window, change the load module name to MAINMOD2, and press Enter.\n6.Set a breakpoint by typing U in the desired location.\nYou set an unconditional breakpoint for SUBPROG of MAINMOD2.\nWhen a source listing breakpoint occurs in a subprogram, the current load module is automatically set to the load module\nthat owns the subprogram.\n 1044", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "55c81c25ac5a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCustomize Symbolic Information Using the Batch Method\nCustomizing symbolic information saves your monitoring configuration for future reuse and is optional. To customize\nsymbolic information required for testing composite modules, submit a batch job to run IN25LINK.\nNOTE\nFor more information about how to use the IN25LINK program, see Symbolic Support.\nThe InterTest for CICS batch job step, executed after the composite module is link-edited, reads the link-edit map to\ndetermine the link-name, offset, and length of each subprogram. This step also specifies the names under which InterTest\nfor CICS monitors each program.\nResume and Execution Options\nControl and Resume Execution from a Breakpoint\nYou can control program execution from a breakpoint in several ways:\n\u2022Single-stepping through the execution\n\u2022Setting additional breakpoints\n\u2022Jumping to another location\n\u2022Resume program execution ignoring all breakpoints\nSingle-step Through Execution\nAn effective way to debug a program is to reach a breakpoint, add data items whose values you want to track to the Keep\nwindow, and execute a few instructions at a time or single-step through the program to see how the values change.\nSet Additional Breakpoints\nYou also can set additional breakpoints in your program. This means that you do not have to decide in advance which\nprogram paths to execute for the entire test session. Decide at any breakpoint how to continue your test session.\nJump to Another Location\nAt a breakpoint, continue execution from where the program stopped or from another location to:\n\u2022Go around a problem area\n\u2022Force execution of bypassed code\n\u2022Change the logical flow for testing purposes\nContinue Execution\nTo continue execution from an automatic breakpoint, you must do one of the following:\n\u2022Dynamically correct the error. To dynamically modify main storage to correct the error and for instructions on using the\nindirect commands facility.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "55c81c25ac5a-1", "text": "indirect commands facility.\n\u2022Set an InterTest for CICS protection option. For more information, see Monitoring Menu Options.\n\u2022Go around the error. For details, see Jump to Another Location and Using the Resume Menu. Options 2, 3, and 4 on\nthe Resume menu offer easy ways to specify where you want to continue execution.\nInterTest for CICS lets you control where execution resumes and how much code executes at a time. Resume execution\nfrom where you stopped or from another location; and either single-step through execution or continue until InterTest for\nCICS reaches the next breakpoint or the end of the program.\n 1045", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c9a5a4cfe79c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPress PF5 or specify GO on the command line to continue from the current breakpoint. Execution continues until another\nbreakpoint occurs or the program ends, whichever comes first.\nSingle-Step Through Execution\nPress PF10  or enter the NEXT command on the command line to single-step through a specific number of verbs,\ninstructions, or statements. The default is one verb, instruction or statement, but this can be changed by specifying NEXT\nvalue  or pressing PF4 to access the Source Listing Profile screen.\nWhen stopped on a PERFORM or CALL, the NEXT OVER command causes the test session to continue until the lexical\nstatement following the PERFORM or CALL is encountered, where a breakpoint occurs.\nWhen stopped within a paragraph or subroutine, the NEXT RETURN  command causes the test session to continue until\nthe session encounters the lexical statement following the PERFORM or CALL that invoked the current paragraph or\nsubroutine, where a breakpoint occurs. You must have TRACE ON to use NEXT RETURN.\nNOTE\nWhen you use PF10  or the NEXT command to single-step through nested COBOL IF statements, it might\nappear that InterTest for CICS is not executing one verb at a time. This is a function of how the compiler\ngenerates the object code.\nWARNING\nTo more closely follow the execution of nested IF statements, use the PF9 on the Detailed Breakpoint display to\nexecute one instruction at a time.\nJump to Another Location\nTo specify a new location for resuming execution, Specify the GO line-number|label command or do one of the following:\nDisplay the statement or instruction where you want to resume execution.\n\u2022Enter g  to the left of the line number in column 1.\n\u2022Press PF5 to continue to the next breakpoint or until program execution ends, or press PF10  to single-step execution.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c9a5a4cfe79c-1", "text": "Use this option with caution in COBOL and Assembler programs and optimized code.  Certain uses trigger difficulties in\ngetting proper addressability.\nWhen an error occurs in a paragraph containing a CICS command, resume program execution at the paragraph-\nname rather than at the specific instruction, because some CICS internal processing might have occurred prior to that\ncommand.\nIn PL/I programs, do not resume execution at a new location if it results in a jump between PROCS/BLOCKS.\nDebug Optimized Applications\nInterTest for CICS supports the debugging of programs that have been optimized, either by the COBOL compiler's\nOPTIMIZE option or by Optimizer/II  or Optimizer/II . However, debugging these programs sometimes results in unexpected\nbehavior.\nNOTE\nThe PL/I compilers are optimizing compilers.\nOften, as part of the optimization process, a compiler will relocate individual instructions, statements, or even entire\nparagraphs so that the optimized program will run more efficiently. This means that some or all of the instructions\ngenerated for a given statement may be moved to another statement, or that some or all of the statements in a\nparagraph may be moved to another paragraph. When this type of optimization occurs, the resulting object program and\ncorresponding listing may not accurately represent the relationship between the source statements and their generated\nobject code, or even between a paragraph label and the statements contained within the paragraph. As a result, there\nmay be times when the breakpoint intercept does not occur, or when the wrong sequence of statements appears to be\n 1046", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4644a07fc308-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nexecuted while single-stepping. There may also be times when the debugger appears to highlight the wrong statement at\na breakpoint intercept.\nThese unexpected displays do not indicate that a program is being executed incorrectly. They indicate that the debugger\nsometimes cannot accurately identify which object code corresponds to which source statement, or which statement is\ncontained within which paragraph.\nInterTest for CICS uses the information in the compiler-generated procedure map or offset report to establish the program\noffset for each statement and label in the program. During execution, the debugger recognizes the start of the new\nstatement or label by matching the program offset of the currently executing instruction with the PROTSYM information\nobtained from the compiler listing. Therefore, the accuracy with which the debugger represents a breakpoint or other\nintercept is only as good as the information in the compiler listing.\nInaccuracies might include, but will not be limited to:\n\u2022Incorrect execution when using GO line-number.\n\u2022Failure to stop at a breakpoint at a paragraph label or statement.\n\u2022Unexpected or out-of-sequence highlighting of statements when single-stepping.\nAlso, application abends may result from the use of the GO line-number command because the optimized object code\nmay have register requirements that do not support changes to the flow of control. These commands should be avoided\nwhen debugging an optimized program.\nFor the best debugging results, avoid using optimization whenever possible in your testing environment. Production\napplications may be compiled with optimization, and debugging these applications as they exist without recompiling is\nsupported. However, you may experience some of the inaccuracies listed previously under these circumstances.\nNOTE\nFor more information about debugging optimized COBOL and the OPTIMIZE option, see COBOL OPTIMIZE\nCompiler Option .\nResume Program Execution Ignoring All Breakpoints", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4644a07fc308-1", "text": "Compiler Option .\nResume Program Execution Ignoring All Breakpoints\nTo continue processing from the current statement ignoring all preset breakpoints and indirect commands until the task\neither abends or runs to normal completion, specify the RUN command on the Source Listing Breakpoint Command Line.\nThe Resume Menu\nOption 4 Resume on the Breakpoint Primary Option menu displays the Resume menu. The fast-path command entry to\naccess the Resume menu from any breakpoint display is =4.\nResume at the Next Instruction\nResume Menu Option 1 Next  Instruction immediately resumes execution at the next instruction. This is the same as using\nPF5 Resume on the Breakpoint display. The fast-path entry from the Breakpoint display is =4.1.\nResume Task from a Label\nSelect Option 2 Label  from the Resume Menu to display the Resume Task From a Label menu. Enter the name of a label\nfrom which to resume execution and press Enter. The program resumes execution from the label you specified.\nThe fast-path entry to display this menu from a breakpoint is =4.2.\nResume Task from a Statement\nSelect Option 3 Statement  from the Resume Menu to display the Resume Task From a Statement Number menu. Enter\na statement number from which to resume execution and press Enter . The program resumes execution from the label you\nspecified.\n 1047", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e0de2d4c8f1c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe fast-path entry to display this menu from a breakpoint is =4.3.\nResume Task from an Offset\nSelect Option 4 Offset  from the Resume Menu to display the Resume Task From an Offset menu. Enter a hexadecimal\nvalue of an offset from which to resume execution and press Enter. The program resumes execution from the offset you\nspecified.\nThe fast-path entry to display this menu from a breakpoint is =4.4.\nResume Task from an Indirect Command Sequence\nSelect Option 5 Indirect Commands from the Resume Menu to display the Execute an Indirect Command Sequence\nmenu. Enter the statement number of an indirect command and press Enter. The program resumes execution with the\nindirect command that you specified.\nThe fast-path entry to display this menu from a breakpoint is =4.5.\nResume Until Next EXEC/CALL\nThe Resume menu option 6 Next EXEC/CALL  lets you execute until the next EXEC command or external call in your\nprogram. For example, using this option might produce the breakpoint shown in the following illustration, which is stopped\nat an external call. The fast-path entry to display this menu from a breakpoint is =4.6.\n       CA InterTest for CICS  PROTSYM FILE REQUEST BREAKPOINT          \n COMMAND ===>                                                                    \n Program= COBDEMO  Option #       Stmt #                             Margin= 01  \n                                         Search=                                 \n OPTS 1 Proc div  2 Work-stor 3 Link sect 4 D-map      5 Clst/Pmap More:   + \n      6 Data xref 7 Proc xref 8 Err msgs  9 Srch fwd  10 Srch bwd            \n PFKS 1 Help      2           3 Det Bkpt  4 Profile    5 Resume     6 Menu", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e0de2d4c8f1c-1", "text": "7 Backward  8 Forward   9 Next Wnd 10 001 Verb  11 Backtrace 12 Status    \n --------------------------------------------------------------------------------- \n    00912*          ENDEXEC.                                                   \n  _ 00913      MOVE '  Y      00624   ' TO DFHEIV0                               \n  _   ==>     CALL 'DFHEI1' USING DFHEIV0  TSQNAME TASKSTRUCTURE TSQLEN       \n  _ 00915     DFHDUMMY TSQITEM.                                                \n    00916                                                                        \n    00917                                                                        \n    00918                                                                        \n .\n .\n .             \n \nResume Task for nnn Steps\nUse Option 7 from the Resume Menu to enter the number of steps you want to execute at this time. The fast-path entry to\ndisplay this menu from a breakpoint is =4.7.\nThis option is a one-time execution of the steps you specify and does not change the value of PF 10 on a Breakpoint\ndisplay. To set the value for PF 10, use the Source Listing Profile, PF4 from any Source Listing display.\n 1048", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fa27373e036b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nResume Task for nnn Machine Instructions\nUse Option 8 from the Resume Menu to enter the number of instructions you want to execute at this time. The fast-path\nentry to display this menu from a breakpoint is =4.8.\nThis option is a one-time execution of the steps you specify and does not change the value of PF9 on a Detailed\nBreakpoint Display.\nAbend the Task\nYou have the option to abend a task, with or without a dump, at any breakpoint. To abend a task from a breakpoint, follow\nthese steps:\n1.Restore the breakpoint display by pressing Clear . If you are returning from the InterTest for CICS CNTL, CORE, HELP\nor FILE facilities, you might need to press Clear repeatedly.\n2.Enter ABEND  on the command line and press Enter. InterTest for CICS prompts you to enter an Abend code if you\nwant a dump.\n3.From the Abend menu screen, you have several options:\n\u2013Press Clear  to cancel the abend and return to the breakpoint display.\n\u2013To abend without a dump:\n\u2022To take a normal abend without a dump, accept an abend code of blanks and press Enter.\n\u2022To cancel all program exits without a dump, specify the code: XXXX , and press Enter.\n\u2013To abend with a dump, specify any four-character dump code except XXXX . Do not specify a code starting with the\nletter A.\nInterTest for CICS displays a message confirming the abend request and dump code. Follow any online instructions to\ncomplete the abend. After an abend, you return to CICS.\nReview Program Status After Execution\nWhen your transaction terminates normally or with an abend, you return to CICS. At this point, review the following items:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fa27373e036b-1", "text": "\u2022Status of your program source code\n\u2022InterTest for CICS monitoring and monitoring options\n\u2022Auxiliary files and databases accessed by your program\nYour Program Source Code\nYour program source code is not modified. It is exactly the same as before you began testing.\nExample\nIf InterTest for CICS detected an ASRA and you used InterTest for CICS to correct the error, the original error still exists in\nyour code.\nIf you modified main storage, that change was only temporary. Your program remains unchanged.\nThe InterTest for CICS copy of your program from the compiled or assembled output also remains unchanged. If you rerun\nthe transaction, you will see the same display of your program in the Source Listing Facility as you did the first time.\nInterTest for CICS Monitoring and Monitoring Options\nInterTest for CICS monitoring and monitoring options, which you set before or during testing, remain in effect until you\nremove them. These include all breakpoints set before or during program execution that were not removed during the test\nsession.\n 1049", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a823ce138820-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo get a status display of monitoring activity and options in effect for one program, perform these steps:\n1.Display the Source for the program.\n2.Enter the command STATUS.\nTo get a status display of monitoring activity and options in effect for all programs, enter the command STATUS ALL.\nTo get global status display from the Primary Option Menu, perform these steps:\n1.Access the Primary Option Menu.\n2.Select Option 2 Monitoring .\n3.Select Option 4 Status .\nNOTE\nThe fast-path entry for a Monitoring Status Report from CICS is ITST 2.4\nAlternatively, enter one of the following commands on a clear screen under CICS:\n\u2022For a program:\n CNTL=INQ,PROG=progname\n \n\u2022For multiple programs:\n CNTL=INQ,PROG=(prog1,prog2,prog3)\n \nExample\nTo display the InterTest for CICS monitoring status for the program COBDEMO, enter the following command under CICS:\n CNTL=INQ,PROG=COBDEMO\n \nFiles and Databases\nAny files or databases updated by the program are permanently modified unless the No File Updating (NUP) option was\nset in advance. The NUP option is set using any Monitoring Menu.\nWARNING\nFile or database changes that you make using the InterTest for CICS FILE facility are permanent, whether or not\nthe NUP option is set.\nContinue to Test\nIn some testing situations, you might want to re-execute the program without changing the source code. Doing this\nmeans you will see the same automatic breakpoints that you saw the first time. When it is easy to correct or get around\nthe errors, this method can be the most efficient route to continue testing because you do not have to recompile your", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a823ce138820-1", "text": "program.\nUse the indirect commands facility to continue to test your program without recompiling it.\nCorrect Your Source Code\nWhen you decide to continue testing from a new version of your program, perform these steps:\n1.Modify the program source code (outside InterTest for CICS).\n2.Recompile or re-assemble the modified programs using the InterTest for CICS post-processor. For more information,\nsee Source Listing Facility for InterTest. The InterTest for CICS post-processor automatically updates the InterTest for\nCICS Symbolic File and the Source Listing facility with the new version of the program.\n 1050", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a40cbb368e65-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n3.Execute the InterTest for CICS New Program Copy option, if desired. This option is on the Program Monitoring menu\n(2.1). New Copy performs the following functions:\n\u2013Resets the CICS entry in the PPT table to the program's new library address\n\u2013Transfers all symbolically set breakpoints and other monitoring options to the recompiled program\nNOTE\nTo recompile your program and keep the same breakpoints in the recompiled version, set breakpoints at\nparagraph names or labels, not at lines of executable code. Then use the InterTest for CICS New Program Copy\nfunction to transfer the breakpoints to the recompiled program. If you set breakpoints at lines of executable\ncode, New Program Copy transfers the breakpoints to the same statement numbers  or offsets in the recompiled\nprogram, which might not be what you want.\nReset Breakpoints after Recompiling or Re-Assembling\nIf breakpoints were set at executable statements or locations, you might need to adjust their locations after recompiling a\nprogram, as follows:\n\u2022To reset the breakpoint locations, adjust the locations one at a time or remove them all and re-enter them.\n\u2022To scroll through your program one breakpoint at a time, set the scroll amount to STOP on the Source Listing Profile\nscreen, accessed by typing PROFILE  or pressing PF4 from a Source Listing display.\n\u2022To remove all breakpoints at once for a program that is being monitored with User ID=.ANY, you must first check that\nno one else is executing the program before you remove monitoring. Get a Monitoring Status Display for the program.\nIf no one else is executing the program, remove monitoring or remove all breakpoints directly from the Monitoring\nStatus report.\nWARNING\nUse this option with caution! Removing monitoring for a program clears all breakpoints and all monitoring\noptions.\nMonitoring Menu Options", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a40cbb368e65-1", "text": "options.\nMonitoring Menu Options\nThe primary task of InterTest for CICS is to monitor programs to detect and prevent errors. When you set monitoring for\na program, InterTest for CICS detects and prevents errors before they occur. That means monitored programs will not\nabend or commit storage violations.\nThis article describes the Monitoring Menu Options (Option 2 on the Primary Option Menu) that let you take advantage of\nthe full range of InterTest for CICS monitoring capabilities. For example, use the monitoring menus to set monitoring for\nprograms, all programs executed by a transaction, or all the programs executed from a terminal. Use the menu to invoke\nmany options for monitoring, such as breakpoints, data monitoring, indirect commands, CICS resource replacement\noptions, and system-wide options. The monitoring menus also enable you to get a selective Monitoring Status report.\nMonitor Status\nFor more information about how to access and use the Primary Option Menu and Status Report, see Menus and Displays.\nBreakpoints\nFor more information about how to set or remove breakpoints from the Monitoring Menu, see Using Breakpoints.\nData Monitoring\nFor more information about how to use Data Monitoring, see Breakpoint Activities.\n 1051", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e165977f19f2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIndirect Commands\nFor more information about how to use indirect commands, see Breakpoint Activities.\nCNTL Commands\nTo use the CNTL transaction, alternate menus, and transaction-based commands to specify monitoring options.\nMonitoring Menu Functions (ITST 2)\nThe Monitoring Menu has the following options to perform monitoring-related functions:\n\u2022Programs\n\u2022Transactions\n\u2022Terminals\n\u2022Status\n\u2022Active tasks\n\u2022System-wide\n\u2022Debug sessions\nPrograms\nDisplays the Program Monitoring screen, which lets you set and remove monitoring, breakpoints, monitoring options, and\nmonitoring-related functions for one or more programs. Monitoring related functions include the following items:\n\u2022Status report to display and remove monitoring and monitoring options for programs, transactions, and terminals\n\u2022Setting and removing monitoring, breakpoints, and monitoring options\n\u2022Setting and removing statement tracing and data monitoring\n\u2022New copy function to reset monitoring for a recompiled program\n\u2022Indirect commands to enable inline adjustments to programs without recompiling\n\u2022Composite support to provide symbolic support for separately compiled programs brought together when they are link-\nedited\nTransactions\nDisplays the Transaction Monitoring screen which lets you set and remove monitoring, and monitoring options for one or\nmore transactions. Monitoring options for transactions include request breakpoints, statement tracing and data monitoring,\nand replace, protect and special options.\nTerminals\nDisplays the Terminal Monitoring screen, which lets you set and remove monitoring and monitoring options for all the\nprograms executing from a terminal.\nStatus\nDisplays the status report (2.4) for all monitoring activity in the current CICS region. Use the status report to quickly\nremove a monitoring option or monitoring entry.\nActive Tasks\nDisplays the list of active tasks that are being monitored by InterTest. If the system-wide purge option is turned on, the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e165977f19f2-1", "text": "Active Tasks screen lets you to purge a task. If you previously disconnected a task from a terminal, the Active Tasks\nscreen lets you reconnect the task and continue testing.\n 1052", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "57709192382c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSystem-Wide\nDisplays the System-Wide Options submenu (2.6), which lets you display and modify monitoring options for the entire\nsystem. These include automatic breakpointing, checkpointing, dumping all abends, global logging, InterTest for CICS\ntracing, and breakpointed task purging.\nNOTE\nAdditional monitoring options, specified by CNTL commands, are available to perform more specialized\nfunctions.\nDebug Sessions\nDisplays the monitor logging records of previously recorded debug sessions. Allows you to view, delete, and load\npreviously recorded debug sessions.\nAccess\nThe Monitoring Menu is Option 2  on the Primary Option Menu.\nTo access the Monitoring Menu from a Source Listing display, perform these steps:\n1.Type the command MENU  or press PF6 to access the Primary Option Menu.\n2.Select Option 2.\nNOTE\nThe fast-path command entry is =2.\nTo access the Monitoring Menu from a Source Listing Breakpoint display, type the command MENU  or press PF6 to\naccess the Breakpoint Primary Option Menu, and then select Option 1.2. The fast-path command entry is =1.2.\nPF Keys\nExit any Monitoring Menu by pressing a PF key. The following bullets describe the function of each PF key.\nPF1 or 13\nInitiates the InterTest for CICS online help facility.\nPF2 or 14\nUnassigned\nPF3 or 15\nTerminates the current processing and returns to the previous display.\nPF4 or 16\nReturns you to the top-level menu, the Primary Option Menu.\nPF5 or 17\nUnassigned\nPF6 or 18\nUnassigned\nPF7\nScrolls a display list backward towards the top of the list.\nPF8\nScrolls a display list forward towards the bottom of the list.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "57709192382c-1", "text": "PF8\nScrolls a display list forward towards the bottom of the list.\nPF9 to 12 and PF21 to 24\nUnassigned\n 1053", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "be79132a0e07-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe User ID Monitoring Option\nWhen you set monitoring, breakpoints or options for a specific program, transaction, or terminal, InterTest for CICS\ncreates an entry for that program, transaction, or terminal in the monitoring table. For releases after Version 5.3, each\nmonitoring table entry also includes a user monitoring option. The user option is .ANY or a specific CICS user ID. The\nuser option indicates for whom the program, transaction, or terminal will be monitored. The following table describes how\nthe value of the user monitoring option affects monitoring and breakpoints.\nUser ID = .ANY\nEveryone is monitored, regardless of the CICS user ID. Breakpoints are directed to the terminals where they were\nset unless a specific option was set to redirect the breakpoints.\nUser ID = specific CICS user ID\nMonitoring occurs only for the specified user based on the CICS user ID. This restricts the monitoring entry to\na single user in a secure CICS system, and lets you move from one terminal to another, preserving breakpoint\nsettings and options.\nMonitor for a User ID\nThe following status report shows the program COBDEMO, which will be monitored for a single user, MARY01. The\nunconditional breakpoint is directed to any terminal where CICS user MARY01 is signed on.\n          CA InterTest for CICS  - MONITORING STATUS                \n  COMMAND ===>                                                                   \n  \n    Type + to expand or   collapse option levels displayed below,                \n           or R to remove option(s).                                            \n  \n      Option     Description                Attributes                           \n  _   COBDEMO    Program monitor entry      COBOL                                \n  _   | MARY01   User monitoring options    Active                             \n        |        Symbolic listing file      PROTSYM", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "be79132a0e07-1", "text": "|        Symbolic listing file      PROTSYM                              \n  _     | UBP    Unconditional breakpoint   #1                                   \n        |        Option ID                  DD103243                            \n        |        From, to terminals         .ANY, .ANY                         \n  _     | SLB    Source listing breakpoints .ANY         \n \nMonitoring with a specific user ID gives you the ability to do the following actions:\n\u2022Isolate monitoring and debugging to a specific user, and not all users\n\u2022Move from terminal to terminal (or use a multi-session manager) and automatically redirect monitoring options and\nbreakpoints to your current session, provided the from and to terminals default to .ANY\n\u2022Have two users concurrently debug a program, but with different monitoring options\nNOTE\nYou can also set the User ID to .ANY to monitor for any user of the program.\nWhat Is Your User ID Default?\nThe default user ID appears in the User ID field on the Source Listing Profile display. On the submenus related to\nMonitoring (Program Monitoring, Transaction Monitoring, and Terminal Monitoring), issue the USER command.\n\u2022If you are working in a CICS region without login security, the user ID value is always set to .ANY\n\u2022If you are working in a secure CICS region, the InterTest for CICS installation option DFLTUSER determines whether\nthe default value assigned to the user ID is .ANY or your CICS user ID\n 1054", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a789e3681d82-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe following table explains how the default values work when you are and are not signed on to CICS.\nDFLTUSER Setting Signed on to CICS Not Signed on to CICS\n.ANY By default, everyone is monitored.\nBreakpoints are directed to the terminal\nwhere they were set.Everyone is monitored. Breakpoints are\ndirected to the terminal where they were\nset.\nspecific By default, monitoring applies only to your\nuser ID and breakpoints are displayed at\nwhatever terminal you are using.Not recommended, but takes the value of\nthe default CICS user ID specified by the\nSystems Programmer in the CICS startup\nJCL. Type USER command to display this\nvalue.\nLook up the current DFLTUSER value from the Primary Option Menu (fast-path 7.1.2) by performing these steps:\n1.Use option 7 Status/Maintenance.\n2.Select Option 1 Product Status.\n3.Select Option 2 Global Options\nThis displays all installation options for IN25OPTS in alphabetic order. The DFLTUSER setting shows the default user ID\nsetting for your system.\nOverride the User ID Default\nOverride the default user ID setting using any of the following methods:\n\u2022From the Source Listing Facility, change the user ID on the Profile screen before  you set monitoring or breakpoints\nfrom the Source Listing Display\n\u2022From the Monitoring menus, change the user ID on the Program Monitoring (2.1), Transaction Monitoring (2.2), or\nTerminal Monitoring (2.3) submenus when you set monitoring, breakpoints, or other options\n\u2022When using transaction-based commands, enter the USR= option with any CNTL monitoring command\nIf you override the default user ID setting before you set monitoring, make sure to use the same user ID when you set", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a789e3681d82-1", "text": "a breakpoint or other monitoring option. Otherwise, the breakpoints or other monitoring options are not attached to the\noriginal monitoring entry. View the Monitoring Status report to check the entries.\nEstablish a Personal Debugging Session\nIn a secure CICS region, set the user ID to your own CICS user ID to establish a personal debugging session. When you\nset monitoring, specify the program or transaction and specify your own CICS user ID. The monitoring request is then\ninvoked only when you execute the program. In addition, specify your own CICS user ID when you set breakpoints and\nother monitoring options. When you do this, the monitoring request and any breakpoints and options are automatically\ndirected to any terminal you are signed on to under CICS.\nOverride the To and From Terminal Defaults for Breakpoints\nThe From and To terminal values on the Monitoring Status display specify where breakpoints take effect and appear. If\nyou are monitoring under a specific CICS user ID, the default From and To terminal values are set to .ANY. If you are\nmonitoring under .ANY user, the default From and To terminal values are set to the terminal where the breakpoints were\nset.\nIf you have special testing needs, set breakpoints that include a From and To terminal value that you specify. To do this,\nset your breakpoints using one of these methods:\n\u2022Program, Transaction, or Terminal Monitoring menus (2.1, 2.2, or 2.3). For more information, see Using Breakpoints\n\u2022CNTL transaction-based commands. For more information, see CNTL Commands and Menus\n 1055", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4add4e01f9bd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMonitoring Submenus\nThis section describes how to use the Monitoring submenus and screens to perform the following monitoring-related\nfunctions. The order in which the functions are described corresponds to their order on the Monitoring Programs,\nTransactions, and Terminals submenus.\nSetting and Removing Monitoring\nBegin and end monitoring for programs, transactions, or terminals.\nStatus Display\nDisplay the monitoring status of a program, transaction, or terminal.\nUsing the New Copy Option\nReset monitoring for a recompiled program.\nSetting and Removing Replacement Options\nDynamically change CICS resources (programs, files, transient data queues, temporary storage).\nSetting and Removing Protection Options\nBypass InterTest for CICS rules that protect main storage, the CSA, and load modules.\nSetting and Removing Special Options\nModify monitoring rules (for example, prevent a program from updating a file, let a program to branch to another\nprogram, limit the number of times a program is monitored).\nSetting and Removing Composite Support\nProvide symbolic support for a program consisting of separately compiled modules.\nViewing and Setting System-Wide Options\nRequest and revise monitoring options on a system-wide basis.\nMonitor Options for Programs, Transactions and Terminals\nFrom the Monitoring Programs, Monitoring Transactions, and Monitoring Terminals submenus, set the following options\nfor a monitored program, terminal, or transaction:\nReplace\nDynamically replace one or more CICS resources (programs, files, temporary storage, transient data queues)\nused by a program.\nProtect\nOverride default protection rules.\nSpecial\nSet and remove special monitoring options (such as limiting the number of times a program is monitored or\npreventing a program from updating a file).\nComposite\nProvide symbolic support for programs consisting of separately compiled modules brought together when the\nprogram is link-edited (composite support). Available from the Monitoring Programs submenu only.\nInitiate Monitoring", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4add4e01f9bd-1", "text": "Initiate Monitoring\nThe InterTest for CICS CNTL transaction performs all monitoring functions. However, InterTest for CICS provides a\nnumber of ways to initiate monitoring and perform other CNTL functions as shown following:\n\u2022Source Listing Facility\n\u2022Monitoring Menu, Option 2 on the Primary Option Menu\n\u2022CNTL menus and fill-in screens\n\u2022CNTL commands\n 1056", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b4e802e54ded-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse one method exclusively, or mix-and-match methods (even during one test session) depending on your specific testing\nneeds.\nExample\nUse the Source Listing facility to initiate monitoring and set breakpoints, the Monitoring Menu and screens to set special\noptions, and a single-line command to resume execution of a task.\nThe easiest way to turn on monitoring and set breakpoints for a single program is to use the Source Listing facility. For\na new or infrequent user, this method is strongly recommended. Turn on monitoring by pressing a PF key, and set a\nbreakpoint by entering a single keystroke directly on your program's source listing.\nTo take advantage of the full range of InterTest for CICS monitoring capabilities, use the Monitoring Menu, which is Option\n2 on the Primary Option Menu. Additional submenus guide you through selecting monitoring for programs, terminals, or\ntransactions, with or without monitoring options.\nOnline help is available from every screen. Press PF1 from any menu or panel for details on how to use it.\nIf you prefer, enter single-line CNTL commands to specify monitoring functions. More experienced users often find it faster\nto enter commands directly.\nWhen you set breakpoints, replacement, protection, special options, or composite support, you automatically set\nmonitoring for the programs, transactions, or terminals that you specify. So, for example, it is not necessary to set\nmonitoring and set breakpoints. Simply setting breakpoints accomplishes both functions.\nHowever, when you remove  breakpoints, replacement, protection, special options, or composite support, you do not\nremove monitoring for the programs, transactions, or terminals that you specify. Monitoring remains in effect until you\nexplicitly instruct InterTest for CICS to remove monitoring.\nThe Program Monitoring Submenu", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b4e802e54ded-1", "text": "explicitly instruct InterTest for CICS to remove monitoring.\nThe Program Monitoring Submenu\nUse the Program Monitoring submenu (2.1) to view, set, or remove monitoring, breakpoints, and monitoring options for\nprograms. To select an option, enter or modify the Program and User ID field values, and then tab to the desired Option.\nType an S to set the option or an  R to remove the option, and then press Enter to process the function. Press PF1 for field\nlevel help at any time.\nScroll the Options List\nThe More field on the right side of the display indicates additional options are available. More: + indicates you can scroll\nforward to view additional options. More: - indicates you can scroll backward to view additional options. Press PF8 to\nscroll forward and view additional options; PF7 to scroll backward and view previous options.\nAfter you process an option that requires an additional screen, when you return to this submenu the option you processed\nbecomes the first option on the list. Enter the Command TOP to display the Options list from the top. Press PF7 to scroll\nbackward, PF8 to scroll forward.\nNOTE\nIf a program is stopped at a breakpoint, press PF6 to access the Breakpoint Menu, and then select option 1.2.1\nto access the Program Monitoring submenu. Jump to the menu by entering  =1.2.1 in the command line of the\nbreakpoint display.\nGeneric Specification of Programs, Transactions, or Terminals\nUse the Monitoring submenus or CNTL transaction-based commands to set monitoring or monitoring options generically.\nGeneric specification in InterTest for CICS lets you specify asterisks, *, and plus signs, +, to replace characters in a\nprogram name, transaction code, or terminal name. These specifications are interpreted according to the rules for the\nCICS CEMT transaction, as follows:\n 1057", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "987ddabf74d0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022An asterisk specifies any number of characters, including no characters. Specify more than one asterisk in a program\nname, transaction code, or terminal name. However do not specify an asterisk by itself.\n\u2022A plus sign specifies one character in a particular position. Specify more than one plus sign in a name or code.\nHowever do not specify a plus sign by itself.\n\u2022Combine asterisks and plus signs.\nExamples\nThe following table shows how the generic entry specifications are processed:\nABC*\nSpecifies all names or codes that begin with ABC, including ABC.\n*ABC\nSpecifies all names or codes that end with ABC, including ABC.\nAB*C\nSpecifies all names or codes that begin with AB and end with C and that could have an unspecified number of\ncharacters in the middle.\nABC+\nSpecifies all four-character names or codes that begin with ABC followed by any one character.\n+ABC\nSpecifies all four-character names or codes that begin with any character followed by ABC.\nAB+C\nSpecifies all four-character names or codes that begin with AB followed by any one character and C.\nAB+C*\nSpecifies all names or codes that begin with AB followed by one character, C, and an unspecified number of\ncharacters.\nMonitor All Programs\nInterTest for CICS enables you to establish system-wide monitoring of all applications in the CICS region except for those\nwith the prefix DFH (IBM CICS programs) or IN25 ( InterTest for CICS programs). Establish system-wide monitoring that\napplies to .ANY user in the CICS region or a specific CICS user. Typically, this option is password protected.\nMenu Entries\nTo set monitoring for all programs, enter the following on the Program Monitoring menu (2.1):\nProgram\n.ALL\nUser ID", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "987ddabf74d0-1", "text": "Program\n.ALL\nUser ID\n.ANY  to apply system-wide monitoring for all users or specific user ID  to apply monitoring to all programs\nexecuted by a specific user.\nType S next to Monitor and press Enter .\nHierarchy Rules for Monitored Entries\nIt is important to know the priorities InterTest for CICS observes if more than one entry in the Monitoring Table applies to\nthe same program.\n 1058", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "551ded812795-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022A specific or generic program entry overrides a transaction entry, a terminal entry, and an .ALL specification\n\u2022A transaction entry overrides a terminal entry and an .ALL specification\n\u2022A terminal entry (specific or generic) overrides an .ALL specification\nExample\nSuppose you specify monitoring options for program ABC1 and different options for transaction TRN1. ABC1 executes\nas part of that transaction. When ABC1 executes, the options specified for ABC1 override the options specified for TRN1.\nSimilarly, it is important to understand the priorities InterTest for CICS observes when a program, transaction, or terminal\nis specifically and generically declared for monitoring. A specific entry overrides a generic entry except when you request\nStatus Display. In that case, the generic specification takes precedence.\nSuppose you specify monitoring options for program ABC1 and different monitoring options for program ABC*. The\noptions specified for ABC* affect all programs whose names begin with ABC except for program ABC1 (and any other\nprograms beginning with ABC that have their own entries in the Monitoring Table). Monitoring for ABC1 is controlled by\nthe specific entry for that program. However, if you request a Status Display for program ABC*, you get monitoring status\nreports for all programs that begin with ABC, including program ABC1 that has a separate Monitoring Table entry.\nMonitoring\nSet and remove monitoring for programs, transactions, or terminals directly from the Monitoring Submenus for Program,\nTerminals, or Transactions.\nSet Monitoring\nWhen you set monitoring for a:\n\u2022Program, InterTest for CICS monitors the program from whatever terminal it executes, even if it executes as part of a\nnon-terminal owning task. Use the replacement, protection, or special options screen if you want to restrict monitoring\nto a specific terminal.\n\u2022Transaction, InterTest for CICS monitors all of the transaction's programs.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "551ded812795-1", "text": "\u2022Transaction, InterTest for CICS monitors all of the transaction's programs.\n\u2022Terminal, InterTest for CICS monitors every program that executes at that terminal.\nNOTE\nInterTest for CICS does not monitor programs that begin with the prefix DFH (IBM CICS programs) or IN25\n(InterTest for CICS programs).\nIf you set monitoring for a transaction or terminal, and a program executing as part of that transaction or at that terminal\nis stopped at an automatic breakpoint, InterTest for CICS automatically creates an individual entry in the Monitoring\nTable for that program. This lets you set breakpoints and monitoring options specifically for that program. Similarly, if\nyou specify .ALL in the Program Names field on the Function Selection Menu or if you specify a generic program name,\nInterTest for CICS creates an individual Monitoring Table entry for any program monitored under that entry that it stops at\nan automatic breakpoint.\nRemove Monitoring\nWhen you remove monitoring, you also remove all breakpoints and monitoring options specified for that program,\ntransaction, or terminal. A quick way of creating a new testing scenario for a program is to remove monitoring and reset it\nwith different breakpoints and options.\nBefore you remove monitoring for a program, terminal, or transaction being monitored under .ANY user ID, you might\nwant to view the status report of all InterTest for CICS monitoring activity to make sure other users are not currently testing\nthe same programs. Option 2.4 gives a Monitoring Status report of all monitoring activity.\n 1059", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1bea85f30a97-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFrom the Status Report\nFrom the status report, remove monitoring quickly for any entry. Just locate the monitoring entry, enter r in the field to\nthe left of the entry, and press Enter . After the request is processed, an asterisk in front of the Monitoring Status entry\nindicates the entry was removed. If you press PF2 Refresh, the entry is deleted from the display.\nFrom the Menus\nTo remove monitoring for programs, transactions, or terminals using the Monitoring submenus, access the appropriate\nsubmenu from the Monitoring Menu, and then enter the program name, transaction code, or terminal name, the user ID\nfor whom the program is monitored, and R next to the Monitor Option. Press Enter.\nNOTE\nRemember that you can also set monitoring by setting breakpoints, replacement, protection, special options, or\ncomposite support. However, if you remove breakpoints, options, or composite support, monitoring remains in\neffect for the specified programs until you specifically instruct InterTest for CICS to stop monitoring.\nSet and Remove Statement Trace Options\nNOTE\nThese options are unrelated to the backtrace facility.\nSet and remove statement tracing and data monitoring for programs, transactions or terminals. However, these options\nare only valid for COBOL programs and, when specified for a transaction or terminal, will only take affect when a COBOL\nprogram is executed. In addition, if either option is specified for more than one program in a transaction, only one\nstatement trace table will be allocated for the transaction.\nWhen you set statement tracing for a COBOL program, if a statement trace table was not created for the transaction, it is\ncreated prior to executing the next statement in the program. If a statement trace table exists for the transaction, it will be\nused by all programs in the transaction for which statement tracing was specified.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1bea85f30a97-1", "text": "used by all programs in the transaction for which statement tracing was specified.\nWhen you set statement tracing for a transaction, a statement trace table is created prior to executing the next COBOL\nstatement in the transaction. When you set statement tracing for a terminal, a statement trace table is created for each\ntransaction that executes a COBOL program at that terminal.\nWhen you set data monitoring for a program, transaction, or terminal, statement tracing is automatically set for that entity.\nUnlike statement tracing, however, data monitoring must be restricted to a specific terminal or user ID.\nTo set or remove statement trace options, access the appropriate Monitoring submenu:\nOption Used For Monitoring\n2.1 Programs\n2.2 Transactions\n2.3 Terminals\nSet Statement Trace Options\nOn the Monitoring submenu, enter the program name, transaction code, or terminal name for which the option will be set.\nIf the option will be set by user ID, specify this. Select the STMT  Trace option, using S, and press Enter. The Statement\nTrace Options screen opens.\nSpecify the following options on the Statement Trace Options screen. The equivalent option used in CNTL transaction-\nbased commands is specified in parentheses.\nStatement tracing (TRC)\nInstructs InterTest for CICS to save trace information for every executed COBOL statement.\n 1060", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5def401ff9b3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nData monitoring (DM)\nInstructs InterTest for CICS to capture data values for every executed COBOL statement. If data monitoring is\nselected, statement tracing will automatically be activated. In addition, a specific terminal ID or user ID is required.\nTerm ID (or .ANY or .NO) where trace options will take effect\nSpecifies that the program be monitored and that statement trace options, if specified, take effect only when the\nprogram is executed at any terminal (.ANY), no terminal (.NO), or a specific terminal.\nUser ID (or .ANY) who will execute the program\nSpecifies that the program be monitored and that statement trace options, if specified, take effect only when the\nprogram is executed by any user (.ANY) or a specific user (a CICS user ID).\nOnce you have specified the required information, press Enter. You are returned to the monitoring submenu where you\nselected the Statement Trace option.\nRemove Statement Trace Options\nThis section describes how to remove statement trace options from a status report or from the menu.\nFrom a Status Report\nTo remove statement tracing, access the Monitoring Status display (2.4), scroll to the monitoring entry for which you\nspecified the option, and locate the statement trace option. Type r next to the option and press Enter. If data monitoring is\non, it is also removed.\nFrom the Menus\nAlternatively, use the same menus and screens you used to set the option, but instead of entering s next to Trace, enter r\nnext to Trace.\nTo remove statement tracing, enter R next to the Statement Trace option. If data monitoring is on, it is also removed. To\nremove data monitoring without removing statement tracing enter x next to Data monitoring. Enter the terminal ID and\nuser ID exactly as you originally defined them.\nNew Copy Option", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5def401ff9b3-1", "text": "user ID exactly as you originally defined them.\nNew Copy Option\nAfter you recompile a program, use the New Copy option on the Program Monitoring menu (2.1) to reset symbolically\nspecified breakpoints for paragraphs, procedures, or routines. The InterTest New Copy also executes a CICS New Copy\nto bring the program into storage. However, if you have breakpoints set by Statement # or Offset and you recompile a\nprogram, you should deactivate monitoring for the program first, use the New Copy option to reload the new program, and\nthen reset your Statement # or Offset breakpoints. This will insure that your breakpoints are in sync with the new program\nversion.\nNOTE\nCNTL=NEW is the equivalent CNTL command for the New Copy monitoring menu option.\nReplacement Options\nThis section explains how to set and remove replacement options. Set replacement options to dynamically change the\nnames of CICS resources (programs, files, transient data queues, and temporary storage) specified in CICS CALLS by\na monitored program. Remove the replacement options when you want the program to use the resources defined in the\nprogram.\nWhen you specify replacement options for a transaction, the resources are replaced in all of its programs. When you\nspecify replacement options for a terminal, the resources are replaced in all programs executing from that terminal.\n 1061", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0e53fc4715ed-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo set or remove replacement options, access the appropriate Monitoring subenu to which the monitoring option applies:\nOption Used For Monitoring\n2.1 Programs\n2.2 Transactions\n2.3 Terminals\nSet Replacement Options\nOn the Monitoring submenu, enter the program names, transaction codes, or terminal names and the user ID option for\nwhom the entry will be monitored. Then select the Replace  option using S, and press Enter. The Replacement Options\nscreen appears.\nSpecify the following options. The equivalent option used in CNTL transaction-based commands is specified in\nparentheses.\nReplace program name (RPC)\nLets a program name be replaced. Specify the original program name and the new name.\nReplace file name (RFC)\nLets a file name be replaced. Specify the original file name and the new name. The sample screen shown previously\nspecifies that program COBDEMO use file TFILE instead of PFILE.\nReplace TD queue name (RTD) Lets a transient data queue name be replaced. Specify the original TD queue name and\nthe new name.\nTS selection mask; TS replacement mask (RTS) Lets a temporary storage ID be replaced. Specify the original\ntemporary storage ID in the TS selection mask field and the new temporary storage ID in the TS replacement mask field.\nSpecify both masks as eight bytes in either character (Cdata) or hexadecimal (Xdata) format.\nExample\nSTORAGE2 replaces STORAGE1 in all temporary storage requests issued by the program.\n TS selection mask:   C'STORAGE1'\n TS replacement mask: C'STORAGE2'\n \nLimit monitoring (TON)\nSpecifies that the program be monitored and that replacement options, if specified, take effect only when the\nprogram executes at the current terminal (*), a specific terminal (termid), or without a terminal (.NO).", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0e53fc4715ed-1", "text": "User ID (or .ANY) who will execute the program\nSpecifies that the program be monitored and that replacement options, if specified, take effect only when the\nprogram is executed by any user (.ANY) or a specific user (a CICS user ID).\nWhen you have specified the required information, press Enter. You are returned to the monitoring submenu where you\nselected the Replace option.\nRemove Replacement Options\nThis section describes how to remove replacement options from a status report or from the menu.\nFrom a Status Report\nTo remove a replacement option, access the Monitoring Status display (2.4), scroll to the monitoring entry for which you\nspecified the option, and locate the specific replacement option. Type r next to the option and press Enter.\n 1062", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b84bcb1dd1f2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFrom the Menus\nAlternatively, use the same menus and screens you used to set the option, but instead of entering s next to Replace, enter\nr next to Replace. Specify the information exactly as you entered it.\nTo remove all replacement options of a specific type, use the menus and enter .ALL  in the appropriate field on the\nRemove Replacement Options screen. This example removes all file replacement options previously set for the\ntransaction DEMC.\nProtection Options\nSet options to override the InterTest for CICS default protection rules for modifying main storage, the CSA, and load\nmodules. Remove the protection options to re-instate the default protection rules.\nNOTE\nBecause the protection options can potentially damage your CICS system if misused, exercise caution in\nspecifying them. These options are password protected unless your site removed this restriction.\nTo set or remove protection options, access the appropriate Monitoring submenu to which the monitoring option applies:\nOption Used For Monitoring\n2.1 Programs\n2.2 Transactions\n2.3 Terminals\nSet Protection Options\nOn the Monitoring submenu, enter the program names, transaction codes, or terminal names and the user ID option\nfor whom the entry will be monitored. Then select the Replace  option using s, and press Enter. The Protection Options\nscreen displays.\nSpecify the following options on the previous screen. In the description of each option, the command syntax equivalent for\neach monitoring option is specified in parentheses.\nBypass storage protection (BYP)\nPermits a specified section of program code to do the following:\n\u2022Modify any area of main storage\n\u2022Issue SVC instructions\n\u2022Issue BALR, BASSM, or BASR 14,15 or 14,14 instructions\nSpecify the beginning and ending program addresses or program offsets. Specify addresses as six- to eight-hexadecimal", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b84bcb1dd1f2-1", "text": "digits, and offsets as one- to five-hexadecimal digits.\nIf you specify .ANY in the From field and an address or offset in the To field, InterTest for CICS suspends monitoring when\nany BALR, BASSM, or BASR 14,15 or 14,14 instruction passes control to the specified location. Monitoring resumes when\nthe routine executed by the instruction returns control to the next byte after the instruction.\nAt a breakpoint, specify * in the From field and leave the To field blank to instruct InterTest for CICS to bypass the current\ninstruction.\nUnprotect CSA (CSA)\nPermits a program to modify areas in the CSA. Specify the offset and the length in hexadecimal.\nUnprotect CWA (CWA)\nPermits a program to modify areas in the CWA. Specify the offset and the length in hexadecimal.\n 1063", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "50e19c194177-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUnprotect main storage area (LET)\nPermits a program to modify a designated area of storage. Specify the beginning address as six to eight\nhexadecimal digits. Specify the length of the area in hexadecimal.\nUnprotect load module (LET)\nPermits a program to modify a load module.\nProtect main storage area (PRO)\nPrevents a program from modifying a designated area of storage not protected by InterTest for CICS. Specify the\nbeginning address as six- to eight-hexadecimal digits. Specify the length of the area in hexadecimal.\nLimit monitoring (TON)\nSpecifies that the program be monitored and that the protection options, if specified, take effect only when the\nprogram executes at the current terminal (*), a specific terminal (termid), or without a terminal (.NO).\nUser ID (or .ANY) who will execute the program (USR)\nSpecifies that the program be monitored and that protection options, if specified, take effect only when the\nprogram is executed by any user (.ANY), or a specific user (a CICS user ID).\nOnce you have specified the required information, press Enter. You return to the monitoring submenu where you selected\nthe Protect option.\nRemove Protection Options\nThis section describes how to remove protection options from a status report or from the menu.\nFrom a Status Report\nTo remove a protection option, access the Monitoring Status display (2.4), scroll to the monitoring entry for which you\nspecified the option, and locate the specific protection option. Type r next to the option and press Enter .\nFrom the Menus\nAlternatively, to remove protection options, access the Monitoring submenu, specify monitoring entry, (program,\ntransaction, or terminal and user ID), type R next to the Replace option and press Enter. Then enter the information\nexactly as you originally defined it.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "50e19c194177-1", "text": "exactly as you originally defined it.\nTo remove all options of a specific type, enter  .ALL  in the appropriate field of the Protection Options menu.\nExample\nTo remove all Bypass Storage Protection options, enter .ALL  in the first Bypass Storage Protection field.\nSpecial Options\nSet special options to alter the standard InterTest for CICS monitoring procedures. Remove the special options to\nreinstate the default monitoring rules.\nTo set or remove protection options, access the appropriate Monitoring submenu to which the monitoring option applies:\nOption Used For Monitoring\n2.1 Programs\n2.2 Transactions\n2.3 Terminals\n 1064", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a6632dde0712-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSet Special Options\nOn the Monitoring submenu, enter the program names, transaction codes, or terminal names and the user ID for whom\nthe entry will be monitored. Then select the Special option using S, and press Enter. The Special Options screen opens.\nYou can specify many options on this screen. The equivalent option used in CNTL transaction-based commands is\nspecified in parentheses.\nSource Listing Breakpoint (SLB)\nSpecifies that the Source Listing Breakpoint screen be displayed rather than the detailed breakpoint display\nscreen.\nNo file updating (NUP)\nSpecifies that a monitored program not update any files. This option only affects VSAM and BDAM files;\ndatabases are unaffected.\nReentrancy check (RNT)\nPrevents a program from modifying its own code.\nFollow monitoring (FOL)\nInstructs InterTest for CICS to continue monitoring a program even if it branches directly to another program (wild\nbranch). All monitoring options remain in effect. Specify the following:\n\u2022ON when control passes to a program that does not have a PPT entry\n\u2022The name of the program when control passes to a program that has a PPT entry\n\u2022NOPPT instead of ON to reduce overhead when a program often branches to a program that does not have a\nPPT entry\nNote: The FOL option should not be specified if control is passed to a program by a LINK or XCTL instruction.\nSuch a program is monitored only if monitoring was specified for it.\nNumber of times to be monitored (MUS)\nLimits the number of times a program should be monitored.\nLimit total size of CICS storage (MXS)\nLimits the amount of storage, including program storage, a program acquires.\nLimit total number of CICS requests (MXR)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a6632dde0712-1", "text": "Limit total number of CICS requests (MXR)\nLimits the number of requests a transaction issues. This option is useful when a program is in a loop that includes\na CICS request.\nSetting for Structure Display Format (SDF)\nUse this option to override, by program, the global default setting. Specify the following:\nHEX\nDisplay data in hexadecimal / character format.\nDATA\nDisplay data in Structure Display Format\nSet local automatic breakpoint (ABP)\nActivates the automatic breakpoint facility for a particular program, transaction, or terminal.\nSpecify the terminal to receive automatic breakpoint displays. An asterisk, *, routes the display to the current\nterminal. A termid routes the display to a particular terminal. .ANY routes the display to all terminals. OFF  instructs\nInterTest for CICS to abend the task instead of halting it at an automatic breakpoint.\nNote:  This option is useful when you do not want the breakpoint display routed to the terminal where the program\nis running or when the display cannot  be routed to that terminal (for example, a non-terminal task or a task\nrunning on a non-3270 terminal). In those cases, specify the terminal to which breakpoint displays should\nbe routed. The local automatic breakpoint option is also useful in a production environment when the global\nAutomatic Breakpoint facility is disabled and you want to monitor a specific program, transaction, or terminal.\n 1065", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ab5fae51327d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nLimit monitoring (TON)\nSpecifies that the program be monitored and that the special options, if specified, take effect only when the\nprogram executes at the current terminal (*), at a specific terminal (termid), or without a terminal (.NO).\nUser ID (or .ANY) who will execute the program (USR)\nSpecifies that the program be monitored and that special options, if specified, take effect only when the program\nis executed by any user (.ANY) or a specific user (a CICS user ID).\nOnce you have specified the required information, press Enter . You are returned to the monitoring submenu where you\nselected the Protect option.\nRemove Special Options\nThis section describes how to remove special options from a status report or from the menu.\nFrom a Status Report\nTo remove a special option, access the Monitoring Status display (2.4), scroll to the monitoring entry for which you\nspecified the option, and locate the specific special option. Type R next to the option and press Enter.\nFrom the Menus\nTo remove special options, access the same monitoring menu and specify R next to Special, complete the Special\nOptions menu by enter an x next to the options you want to remove, or enter the information exactly as you originally\ndefined it.\nDisconnect, Reconnect, and Purge Active Tasks\nThis section describes how to disconnect or reconnect a terminal to InterTest for CICS.\nDisconnect a Task\nTo disconnect a terminal from InterTest for CICS while at a breakpoint, use Breakpoint Primary Menu Option 7 Disconnect.\nThis option lets non- InterTest for CICS or non-CICS functions be performed at the terminal.\nReconnect a Task\nTo reconnect a terminal to the InterTest for CICS breakpoint, use the ITST Monitoring Menu to reconnect a task.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ab5fae51327d-1", "text": "Monitoring Menu Option 5 Active-Tasks, lets you reconnect, disconnect, and purge active tasks. From CICS, enter ITST\n2.5 and the Active Tasks menu displays.\nType an R next to a task you want to reconnect to your terminal, or type a P next to a task you want to purge.\nNOTE\nFor more information, see Special Considerations for MRO Support for reconnection considerations for tested\ntransactions in implicit routing sessions in MRO environments.\nView and Set System-Wide Options\nSet certain options on a system-wide basis from the Monitoring System-Wide Options submenu (2.6).\nNOTE\nThese options are password protected unless your site has removed this restriction.\nThere are six options to select from on this screen. The equivalent option used in single-line commands is specified in\nparentheses. Type S next to the option to select it, and then complete the following screen. In many cases, you enter ON\nto set an option and OFF to remove it.\n 1066", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b3bca8e03775-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nABP Option: Automatic breakpointing  sets the Automatic Breakpoint Facility for the entire system. Default. Breakpoint\ndisplays are routed to the terminal where the program is running. Specify a terminal ID to indicate where breakpoint\ndisplays should be routed for non-terminal attached tasks and for tasks executing from non-3270 terminals.\nIf you specify OFF for the ABP option, you might want to use the Special Options from the Program Monitoring submenu\n(2.1) to set the local Automatic Breakpoint option for one or more programs. The local Automatic Breakpoint option\noverrides the system Automatic Breakpoint option.\nCKPT Option: Option Checkpointing  instructs the Checkpoint Recording Facility to periodically record the status of\nInterTest for CICS monitoring so that you can use the restart feature. The first checkpoint occurs when the option is\nspecified. Subsequent checkpoints occur at the end of the interval, specified in hours and minutes in hhmm format. The\nminimal time interval is ten minutes.\nITTRACE Option: InterTest for CICS  tracing instructs InterTest for CICS to write trace records to the CICS trace during\nmonitoring.\nPurge breakpointed tasks (PURGE)  instructs InterTest for CICS to periodically purge tasks halted at a breakpoint for\nlonger than the specified interval. The first purge occurs when the option is specified. Subsequent purges occur at the end\nof the interval, specified in hours and minutes in this format hhmm . The minimal time interval is 20 minutes.\nWork With Recorded Debug Sessions\nUse option 7 of the InterTest for CICS MONITORING MENU (ITST 2.7) to display monitor logging records of debug\nsessions that were previously recorded.\nThe index record for each recorded debug session is displayed. You can sort and filter records using the command areas", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b3bca8e03775-1", "text": "above each column header. Use the command area to the left of each record to browse, cancel, delete, load, or stop the\nrecording session. If a debug session is currently active, the menu display shows the date as \"*ACTIVE\" and the time as\n\"------\".\nYou can use the following line commands in the action field:\nB\nBrowse the command file member\nD\nDelete the command file member, if it is not active\nL\nLoad the command file member into the current debug session\nS\nStop the active debug session\nC\nCancel the active debug session\n                   CA InterTest for CICS SAVED DEBUG SESSIONS          U11IC9N4\n COMMAND ===>\n \n   Type B to browse session   L to load session    D to delete session\n        S to stop session     C to cancel session\n                                                                       More:   +\n   *        *        *        *       *      *\n   Session  Userid   Applid   Date    Time   Description\n _ .ANYTEST CICSUSER U11IC9N4 2016260 101947\n _ ACTVLOAD CICSUSER U11IC9N4 2016288 160607\n _ APPLID   CICSUSER U11IC9N4 2016245 144837 DESCRIPTION USERID TIME DATE SESSIO\n _ BIGDEMO  CICSUSER U11IC9N4 2016218 113302 EVEN BIGGER SESSION\n _ BIGSESS  CICSUSER U11IC9N4 2016204 102613 TEST LARGE NUMBER OF RECORDS\n 1067", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a42ef8968aea-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _ BROWETST CICSUSER U11IC9N4 2016239 150803\n _ COBDEMO  CICSUSER U11IC9N4 2016218 105545\n _ DATANEW  CICSUSER U11IC9N4 2016274 082857 ANOTHER DATAPGM SESSION TEST\n _ DATAPGM  CICSUSER U11IC9N4 2016195 152741\n _ LOADACTV CICSUSER U11IC9N4 2016288 143051\n _ MSGTEST  CICSUSER U11IC9N4 2016302 115332 TEST MISSING MESSAGE\n _ OTHERACT CICSUSER U11IC9N4 2016288 143421\n \n \n PF1 Help       2 Refresh    3 End        4 Return     5            6 RFind\n PF7 Backward   8 Forward    9           10           11           12 \nFilter\nLets you to specify criteria to filter the subprograms that are displayed on the Composite Support screen.\nSORT\nUse the SORT command on the Debug Sessions screen to sort sessions by the values in a specific column in an\nascending or descending order. The command has the following format:\nSORT [ columnname ] [ order | A | D ]\ncolumnname\n(Optional)\nSpecifies the name of the column that you use as the restrictive criteria for sorting. Values: Session, Userid,\nApplid, Date, Time, Default: Session\norder\n(Optional)\nSpecifies the order that you use for sorting. Values: ASCENDING, DESCENDING Default: ASCENDING\nExample:\nThe following command sorts sessiosn by the Session column in a descending order:\nSORT Session D\nSpecial Monitoring Situations\nSpecial Monitoring Situations", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a42ef8968aea-1", "text": "SORT Session D\nSpecial Monitoring Situations\nSpecial Monitoring Situations\nThis article describes the following special monitoring situations:\n\u2022Monitoring programs with LE/370 condition handlers\n\u2022Monitoring dynamically called COBOL II and COBOL/370 programs\n\u2022Production environment monitoring\n\u2022Monitoring tasks that execute without terminals\n\u2022Monitoring tasks that execute at non-3270 terminals\n\u2022Use segmented monitoring to handle special situations\n\u2022Use programmed breakpoints\n\u2022CICS/ESA 3.3 FEPI applications monitoring\nSegmented monitoring applies to users of HOGAN Systems software and the MSA Corporation's DCI Interface.\nProgrammed breakpoints are used primarily by PL/I users who want to display data areas that InterTest for CICS normally\ncannot display or who do not have symbolic information for their programs.\n 1068", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ac83b8f37350-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMonitor Programs with LE/370 Condition Handlers\nLE/370 condition handlers do not receive control in the same manner as a normal CICS COBOL program. Therefore, they\nmust be monitored using the InterTest Segmented Monitoring and ABI=OFF options.\nTo monitor COBOL/370 programs containing calls to enable or disable LE/370 condition handlers, perform these steps:\n1.Use normal monitoring.\n2.Specify ABI=OFF for the main program, and if there is a composite module, for all subprograms.\nNOTE\nDo not specify ABI=OFF for the LE/370 condition handler module if you want InterTest for CICS to intercept\nabends that occur within the LE/370 condition handler. ABI=OFF is needed for all programs except the\ncondition handler to prevent  InterTest for CICS from intercepting the abend before  the LE/370 condition\nhandler is invoked.\nBecause LE/370 condition handlers do not receive control the same way a normal CICS program does, you must start\nand stop monitoring for the condition handler routine or program by using the Segmented Monitoring breakpoint options\n(+ and -). For example, use the Source Listing facility to display the condition handler routine or program, and then set a\nstart monitoring (+) breakpoint at the first statement number, which causes InterTest for CICS to begin monitoring when\nthe condition handler is invoked by LE/370. Set normal breakpoints, such as unconditional, conditional and so on, in the\ncondition handler program. For more information on segmented monitoring, see Segmented Monitoring to Handle Special\nSituations.\nYou must set a stop monitoring breakpoint (-) before or at the GOBACK statement of the condition handler or\nunpredictable results might occur.\nMonitor Dynamically Called COBOL Programs\nThe monitoring and debugging of dynamically called COBOL programs is handled as follows:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ac83b8f37350-1", "text": "The monitoring and debugging of dynamically called COBOL programs is handled as follows:\n\u2022In the same way as other CICS COBOL programs without necessarily monitoring higher level programs\n\u2022Using the FOL=PPT option\nRequest monitoring for dynamically called COBOL programs through the Source Listing and CNTL facilities the same way\nyou request monitoring for first level CICS COBOL programs.\nProduction Environment Monitoring\nAt times, use InterTest for CICS to monitor programs running in a production environment.\nExample\nYou might want to monitor recently installed or modified applications until you are sure they are free of errors, or even\nmonitor the entire production system if you have errors that cannot otherwise be isolated.\nWhen you use InterTest for CICS in a production environment, you should consider the following items:\n\u2022Where to route automatic breakpoint displays\n\u2022How many times to monitor a program\n\u2022Whether to restrict monitoring to a single terminal or user ID\n\u2022What to do if you must monitor the entire system\nControl Automatic Breakpoint Displays\nWhen you monitor a program in a production environment, you usually do not want the breakpoint display to appear at the\noperator's terminal because the information is meaningless. Instead, InterTest for CICS either abends the task or routes\nthe Breakpoint Display.\n 1069", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "412d55d39e28-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAbend the Task\nIf you want InterTest to abend the task before it damages CICS and writes a transaction dump (INTE), deactivate the\nglobal automatic breakpoint facility. This facility instructs InterTest for CICS to generate a breakpoint each time it detects\nan error in a program that it is monitoring.\nTo deactivate this facility, select System-Wide Options from the Monitoring Menu (Primary Menu Option 2.6), and enter\nOFF in the Automatic Breakpoint field, or enter the command:\n CNTL=ABP,OFF\n \nWhen the global automatic breakpoint facility is deactivated, you might want to specify the local automatic breakpoint\noption for certain programs, transactions, or terminals.\nRoute the Breakpoint Display\nTo route breakpoint displays to a programmer's terminal, specify the local automatic breakpoint option and direct the\nbreakpoint displays to a programmer's terminal. The local automatic breakpoint option instructs InterTest for CICS to\ngenerate a breakpoint each time it detects an error in the specified program, transaction, or terminal, and it overrides the\nglobal automatic breakpoint facility.\nTo specify this option, select Special Options from the Monitoring submenus (2.1, 2.2, or 2.3) and specify the programs,\ntransactions, or terminals. Then specify the terminal to which breakpoint displays should be routed. You could also enter\nthe command:\n CNTL=ON,promid,ABP=termid\n \nControl the Number of Times a Program Is Monitored\nWhen a new or modified program goes into production, limit the number of times InterTest for CICS monitors it. The\nMUS option lets you specify the number of times InterTest for CICS should monitor a program. To specify the MUS", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "412d55d39e28-1", "text": "option, select Special Options from the Monitoring submenus (2.1, 2.2, or 2.3) and specify the programs, transactions, or\nterminals. On the Special Options menu, specify the number of times monitoring should occur in the MUS field. You can\nalso enter this command:\n CNTL=ON,promid,MUS=nnn\n \nMonitor a Program for a Single User ID\nWhen a program fails in the production system, use InterTest to monitor it so you can find and correct the error. In a\nsecure CICS region, restricting monitoring to a single user ID means you test the program thoroughly without  interfering\nwith the work of other users.\nAll monitoring methods let you specify a single CICS user ID when setting monitoring. This limits monitoring to only that\nuser, but permits the user to go to any terminal. Monitoring by user ID can be the default in your system. If it is not, you\nmust specify the user ID each time you set monitoring or a monitoring option. If you are using the Source Listing facility\nor the menus to set monitoring, press PF1 to get help on how to monitor by user ID. If you are using CNTL commands,\nspecify the USR option when you set monitoring, as follows:\n CNTL=ON,promid,USR=userid\n \n 1070", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6ae22010ffd0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMonitor a Program at a Single Terminal\nWhen a program fails in the production system, use InterTest for CICS to monitor it to find and correct the error.\nRestricting monitoring to a single terminal means you test the program thoroughly without  interfering with the work of other\nusers.\nIf you are using the CNTL Monitoring Command Builder menus, limit monitoring to a single terminal on the Replacement\nOptions, Protection Options, and Special Options screens. If you are using commands, specify the TON option when you\nset monitoring, as follows:\n CNTL=ON,promid,TON=termid\n \nMonitor the Entire Production System\nYou usually want to avoid monitoring the entire production system because of the high overhead involved. But what if your\nproduction system has a serious error and you cannot isolate the problem program? In that case, instruct InterTest for\nCICS to monitor all the programs in the production system for every user or for a specific user only.\nIf your system is experiencing sporadic problems that are difficult to isolate, you might want to monitor all programs\nexecuted by the user experiencing the problems. In a secure CICS region, use the following global monitoring command\nwith the user ID option for the user experiencing the problem:\n CNTL=ON,PROG=.ALL,USR=cics-userid\n \nNOTE\nEnsure that each user signs on to CICS before executing programs.\nWhile InterTest is monitoring all of the programs, use the Active Tasks display (Primary Menu Option 2.5 Monitoring\nActive Tasks) to check for problems. When InterTest for CICS finds that a program is about to commit an error, it halts the\nprogram at an automatic breakpoint and automatically creates a Monitoring Table entry for that program. The monitoring", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6ae22010ffd0-1", "text": "program at an automatic breakpoint and automatically creates a Monitoring Table entry for that program. The monitoring\nstatus report provides that information. As soon as you see that InterTest for CICS has identified the problem program,\nturn monitoring off for the system and monitor the problem program for a single user or at a single terminal until you\nresolve the error.\nAlternatively, monitor a certain percentage of your programs until InterTest for CICS finds the problem program.\nExample\nYou might monitor 10 percent of your programs one week, another 10 percent the next week, and a third 10 percent the\nfollowing week.\nThis approach minimizes overhead, and takes advantage of the ability of InterTest for CICS to track down problems that\nare otherwise very difficult to resolve.\nMonitor Tasks That Execute Without Terminals\nSpecial steps must be taken when InterTest for CICS monitors tasks that execute without a terminal. This includes tasks\nthat are automatically initiated by an interval control request or a transient data trigger.\nUnconditional, Conditional, and Request Breakpoints\nIf you set unconditional, conditional, and request breakpoints and you want to see the breakpoint display, you must\nindicate that the task is running without a terminal. Specify the terminal to receive breakpoint displays.\nIf you specify .ANY  for the terminal at which the task must be executing, the breakpoint occurs at all terminals -- even\nwhen the task runs without a terminal. If you specify .NO, the breakpoint occurs only when the task executes without a\nterminal.\n 1071", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8e0f4cf9ad72-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSpecify the ID of the terminal to receive breakpoint displays. If omitted, it defaults to the terminal at which the breakpoint\nwas set. Do not specify .ANY for the terminal to receive breakpoint displays.\nNOTE\nIf you set a breakpoint, the local automatic breakpoint option is automatically set for the program.\nAutomatic Breakpoints\nIf the global automatic breakpoint facility is on and a program is executing without a terminal, the task abends. To prevent\nthis, route automatic breakpoint displays to 3270-type terminals. Use the global or local automatic breakpoint terminal\noptions to identify the terminal to receive automatic breakpoint displays.\nTo identify a terminal to receive breakpoint displays for a specific program or transaction, select Special Options on the\nMonitoring Submenu for the Program (2.1) or Transaction (2.2). Specify a terminal ID for the local automatic breakpoint\noption on the Special Options menu. For more information, see Monitoring Menu Options.\nTo identify a terminal to receive breakpoint displays for all non-terminal attached tasks and for tasks executing from\nnon-3270 terminals, select System-Wide Options from the Monitoring Menu (Primary Menu Option 2.6, Breakpoint Menu\nOption 1.2.6). On the System-Wide menu, specify a terminal ID for the global automatic breakpoint option.\nSet Monitoring for Non-Terminal Execution\nMonitor a task only when it executes without a terminal. Specify this by selecting Replacement Options, Protection\nOptions, or Special Options from Monitoring submenus (2.1, 2.2, or 2.3). Specify .NO in the Limit Monitoring field. You can\nalso enter the following command:\n CNTL=ON,promid,TON=.NO\n \nMonitor Tasks That Execute at Non-3270 Terminals\nMonitoring commands for tasks executing at non-3270 terminals must be entered at 3270-type terminals.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8e0f4cf9ad72-1", "text": "Set Monitoring for Non-Terminal Execution\nMonitor a task only when it executes without a terminal. Specify this by selecting Replacement Options, Protection\nOptions, or Special Options from the Monitoring submenus, and then specify .NO in the Limit Monitoring field. For more\ninformation, see Monitoring Menu Options. You can also enter this command:\n CNTL=ON,promid,TON=.NO\n \nAutomatic Breakpoints\nWhen a task is running on a non-3270 terminal, route automatic breakpoint displays to a 3270-type terminal. Use the\nglobal or local automatic breakpoint terminal options, described previously in MonitorTasksThatExecuteWithoutTerminals,\nto identify the terminal to receive automatic breakpoint displays.\nUnconditional, Conditional, and Request Breakpoints\nIf you set unconditional, conditional, and request breakpoints and you want to get the breakpoint display, you must\nspecify .ANY or a terminal ID for the terminal at which the task must be executing for breakpoints to take effect.\nRoute breakpoint displays to a specific terminal. To change the terminal ID: use the Source Listing Profile, and change the\nsetting prior to setting any breakpoints.To see your current terminal's ID, enter TERM  on the command line of any Source\nListing or Breakpoint display.\n 1072", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "94b3b8f64a86-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIf InterTest for CICS was installed with the DFLTUSER value in IN25OPTS set to SPECIFIC, Terminal ID =.ANY is the\ndefault terminal setting. When the DFLTUSER option is set to .ANY, the default terminal ID is the terminal used to set the\nbreakpoint. To view your IN25OPTS settings, use Primary Menu Option 7.12.\nSegmented Monitoring to Handle Special Situations\nUsers of the following might require segmented monitoring:\n\u2022HOGAN Systems\n\u2022DCI Interface of the MSA Corporation\n\u2022LE/370 condition handlers\n\u2022Some composite programs\nInterTest for CICS normally controls whole application programs. Segmented monitoring provides a way for InterTest for\nCICS to control only small portions (code segments) of application programs.\nUse segmented monitoring sparingly for special debugging needs, such as when only certain pieces of code should be\nmonitored because of excessive overhead or because they get control directly from programs (or interfaces) that must not\nbe monitored by InterTest for CICS.\nWARNING\nImproper use of segmented monitoring options could damage your CICS system because InterTest for CICS\nplaces invalid machine instructions in application programs at the segmented monitoring locations specified by\nthe user. Before you use segmented monitoring, see Notes and Warnings .\nSegmented Monitoring Situations\nThe monitoring problems that follow are solved with segmented monitoring.\nHOGAN Systems Users\nProblem:\nInterTest for CICS must not monitor most of the HOGAN Systems code. However, you need to monitor and test\nthe application code that you wrote. This code does not receive control from CICS in the usual way.\nSolution:\nPlace a MON option to start InterTest for CICS monitoring at the beginning of your application program's", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "94b3b8f64a86-1", "text": "Place a MON option to start InterTest for CICS monitoring at the beginning of your application program's\nProcedure Division. Monitoring begins at the MON location and continues until an activity #1 PEM call is\nencountered. The InterTest for CICS IN25UEX routine for HOGAN applications detects this call and stops the\nmonitoring. Set breakpoints within this segment of code. When you execute the transaction, InterTest for CICS\nmonitors the specified code segment.\nYou must also set the InterTest for CICS option USH=ON to prevent automatic breakpoints from being triggered\nwhen your HOGAN Application program references CICS shared-storage areas.\nMSA Programs with Special Interfaces\nProblem:\nThe application programs that hook into large packages such as MSA do not receive control directly from\nCICS, and thus cannot be monitored independently from the MSA packages using standard InterTest for CICS\nmonitoring. Monitoring the entire load module incurs too much overhead and often results in numerous abends\nbecause of non-standard CICS programming practices (such as passing control using direct branches).\nSolution:\nMonitor only the application program that you wrote by setting a MON option near the beginning of the program\nand a NOM at the end of the program. Set breakpoints within this segment of code. When you execute the\ntransaction, InterTest for CICS monitors only the specified code segment.\n 1073", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e244fccf1733-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nFor MSA programs set the MON after the secondary entry point.\nThe Segmented Monitoring Options Monitor (MON) and No Monitor (NOM)\nSegmented monitoring consists of two independent monitoring options:\n\u2022MON, an option to turn monitoring on\n\u2022NOM, an option to turn monitoring off (No Monitor)\nMonitor On Option (MON)\nMON turns InterTest for CICS monitoring on beginning with the machine instruction of the specified location (regardless of\nhow this piece of application program got control). If InterTest for CICS monitoring was already on, monitoring continues.  \nAfter a MON entry, monitoring continues unless InterTest for CICS encounters one of the following:\n\u2022A NOM entry\n\u2022An XCTL\n\u2022A RETURN\nNo Monitor Option (NOM)\nNOM stops InterTest for CICS monitoring at the specified location and gives control to the machine instruction on which\nthe NOM option was specified.  If the code was not already being monitored, it continues unmonitored. After a NOM\nentry, the program continues unmonitored unless InterTest for CICS encounters a MON entry or a LINK/XCTL to another\nprogram already being monitored.\nSpecify these options in your program at the same type of locations you use to set individual breakpoints, such as at\nCOBOL paragraph names or statement numbers. Each option takes effect as it is encountered during program execution.\nEach MON and NOM option is an independent   request to start or stop InterTest for CICS monitoring, regardless of the\ncurrent monitoring status.\nNOTE\nThe MON and NOM options are not CICS user ID or terminal sensitive. An option set from one terminal applies\nwhen the program executes from any terminal by any CICS user.\nWhen using MON and NOM, specify breakpoints and other options in your program. If you set a MON or NOM option at", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e244fccf1733-1", "text": "the same location   as a breakpoint or other option, the MON or NOM option executes first. This means the MON option\nstarts monitoring and hits the breakpoint, but since NOM drops monitoring before the breakpoint is encountered, you\nnever receive the breakpoint that is set where a NOM is also set.\nInstallation Requirements and Password Protection\nThe segmented monitoring option must be enabled as part of the installation and customization procedure. Enable it with\nor without CNTL menu support, and with or without password protection.\nTo check the status of the segmented monitoring option on your system, select Primary Menu Option 7 Status/\nMaintenance, and then Option  1.2 Global Options. The current IN25OPTS values are displayed alphabetically. Look for\nthe option MONOM.\nThe following are MONOM values:\nMENU\nSegmented monitoring is enabled for all methods: Source Listing, CNTL menus, and CNTL commands.\nNOMENU\nSegmented monitoring is enabled for Source Listing and CNTL command methods only.\n 1074", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c1b42b8972e5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNO\nSegmented monitoring is disabled.\nThe MONOMSEC keyword option tells you if a password is required. If MONOMSEC=YES, you need the password to set\nMON or NOM using any method.\nNOTE\nInterTest for CICS releases prior to 5.1 do not support segmented monitoring.\nMethods for Setting and Removing MON and NOM\nThere are three methods for setting and removing MON and NOM, as shown following:\n\u2022Source listing\n\u2022CNTL menus\n\u2022CNTL one-line commands\nThe Source listing method is easiest to use.\nUse Your Source Listing\nThis method requires a listing version that corresponds to your load module. If you use an old listing version, you can\nexperience unpredictable results during execution -- ranging from no effect, to unexpected abends, to data corruption.\nSet MON and NOM\nTo set a location for a MON option in your source listing, enter a plus sign, +, to the left of the statement in your listing\nwhere you want monitoring to begin , and press Enter. Likewise, to set a location for a NOM option, enter a minus sign, -,\nto the left of the statement in your listing where you want monitoring to stop, and press Enter. If a password is required,\nenter the password at the prompt.\nExample\nThe following screen shows setting MON and NOM in your source listing.\n     CA InterTest for CICS   - PROTDEM FILE SOURCE LISTING DISPLAY  \n  COMMAND ===>                                                                 \n  Program= COBDEMO  Option #       Stmt #                             Margin= 01\n                    Label/Search Arg=                                           \n  OPTS 1 Proc div  2 Work-stor 3 Link sect 4 D-map      5 Clst/Pmap More:   +", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c1b42b8972e5-1", "text": "6 Data xref 7 Proc xref 8 Err msgs  9 Srch fwd  10 Srch bwd            \n  PFKS 1 Help      2           3 End        4 Profile    5 Monitor    6 Menu \n       7 Backward  8 Forward   9 Next Wnd  10           11           12 Status  \n  \n    _ 01057     MOVE ALL '*' TO TASKTEXT OF TASKSTRUCTURE2.                  \n    _ 01058     GO TO SENDMAP00.                                               \n \u2192 +  01059 INITIALIZETABLE.                                                   \n    _ 01060     MOVE SUB1 TO STATENUMBER (SUB1),                             \n    _ 01061                   COUNTYNUM1 (SUB1, SUB2).                      \n    _ 01062     MOVE ','   TO COUNTYCOMM (SUB1, SUB2).                       \n    _ 01063     MOVE SUB2 TO COUNTYNUM2 (SUB1, SUB2).                       \n    _ 01064                                                                     \n \u2192 -  01065 DATANAME.                                                        \n    _ 01066     IF  TASKSWITCH3 EQUAL SPACE                                  \n    _ 01067     MOVE 'A' TO TASKSWITCH3                                        \n    _ 01068     MOVE 'DMAP02' TO MAPNAME                                        \n    _ 01069     GO TO SENDREWRITERETURN.                                     \n 1075", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "56632e03b589-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    _ 01070     GO TO SENDMAP00.                                            \n    _ 1071 SETVARREC.      \n \nSet breakpoints within the execution path of the MON and the NOM locations in the program by using the + and - line\ncommands. The + line command activates or starts segmented monitoring when that program statement is executed. The\n- command stops segmented monitoring when the program statement is executed. These commands will not take effect if\nthe program statement is never executed.\nNOTE\nIf you specify a MON or NOM option and a breakpoint at the same location, InterTest for CICS displays the\ncharacter for the first option entered in column 1, although both options are set. To obtain a status display of the\noptions in effect, enter STATUS in the command line, and press Enter .\nRemove MON and NOM\nTo remove a MON or NOM option location, overtype the plus sign, +, or minus sign, -, with an X. Press Enter , and the\noption is removed.\nTo quickly remove all segmented monitoring options for a program, turn monitoring off for the program, remove the options\nfrom the Monitoring Status display, or use the .ALL entry on the CNTL Segmented Monitoring ON and OFF menus.\nAccess the specific CNTL menu directly from the Source Listing Display by making the following entries in the Option #\nfield:\nOption # Entry CNTL Menu Function\n=14S Set segmented monitoring on\n=14R Remove segmented monitoring on\n=15S Set segmented monitoring off\n=15R Remove segmented monitoring off\nThe CNTL Menus\nWhen segmented monitoring is enabled with MENU support, set and remove segmented monitoring for programs directly\nfrom the following CNTL Function Selection Menu, using Options 14 (Segmented Monitoring On) and 15 (Segmented\nMonitoring Off).\nNotes:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "56632e03b589-1", "text": "Monitoring Off).\nNotes:\n\u2022If Options 14 and 15 do not display on the Function Selection menu, menu support for segmented monitoring is not\navailable to you.\n\u2022If segmented monitoring is password protected, you are prompted to enter the password.\n\u2022Specifying NOM options with the menus is tricky because of double negatives:\n\u2013Use 15S to set a segmented monitoring off, or NOM, location.\n\u2013Use 15R to remove a segmented monitoring off, or NOM, location that you previously set.\nSpecify segmented monitoring locations like you would specify individual breakpoint locations on the Segmented\nMonitoring On and Off screens.\nCNTL Function 14S Set Monitor On Screen\nThe following screen is used to set the monitor on locations in COBOL programs. The sample entry (\u2192) specifies that\nmonitoring begins (or continues) whenever user CARAR01 executes the first executable statement in the paragraph A-\nTEST.\n 1076", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b4c8bb1e1488-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    CA InterTest MONITORING COMMAND BUILDER  SEGMENTED MONITORING LOCATIONS  14\n  \n   SET `monitor on' option for  PROG=COBDEMO in any of the following fields:  \n    (For qualification by nested program name, specify 'Programid:Label')      \n \u2192 Paragraph A-TEST_______________________     _______________________________ \n      Names: _______________________________     _______________________________ \n             _______________________________     _______________________________ \n   Statement                                                                    \n    Numbers: _____    _____    _____    _____    _____   _____    _____    _____\n  \n    Offsets: _____    _____    _____    _____    _____   _____    _____    _____\n  \n  \n  \n             user ID (or .ANY) who will execute the program:             CARAR01\n \nThere are similar versions of this menu for Assembler and PL/I users. Specify multiple monitors on locations on this menu.\nValid locations are as follows:\n\u2022COBOL (paragraph names, statement numbers, or hexadecimal offsets)\nNOTE\nYou cannot specify COBOL data names as segmented monitoring locations.\n\u2022Assembler (labels or hexadecimal offsets)\n\u2022PL/I (PL/I labels, statement numbers, or hexadecimal offsets)\nPress Enter  after specifying the locations.\nCNTL Function 14R Remove Monitor On Screen\nRemove any option directly from the Monitoring Status display. For more information, see Menus and Displays. Specify\nindividual locations to be removed exactly as you set them or by the ID number shown on the InterTest for CICS status\ndisplay. To quickly remove all locations at once, enter .ALL  in the first field as shown on the menu (\u2192) and enter the same\nuser ID (or .ANY) used to set the options.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b4c8bb1e1488-1", "text": "user ID (or .ANY) used to set the options.\nThe following screen is used to remove the monitor on locations that were previously set in the program for user ID\nCARAR01.\n     CA InterTest MONITORING COMMAND BUILDER  SEGMENTED MONITORING LOCATIONS  14\n  \n     Remove `monitor on' option for  PROG=COBDEMO in any of the following fields: \n    (For qualification by nested program name, specify 'Programid:Label')      \n \u2192Paragraph .ALL___________________     _______________________________ \n     Names:  _______________________________     _______________________________ \n             _______________________________     _______________________________ \n   Statement                                                       \n    Numbers: __    _____    _____    _____    _____   _____    _____    _____ \n  \n    Offsets: _____    _____    _____    _____    _____   _____    _____    _____ \n  \n  \n            user ID (or .ANY) who will execute the program:             CARAR01\n To remove by ID # shown in status display enter ID # s: -------------   \n \n 1077", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3e6044170623-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAfter specifying the locations, press Enter .\nCNTL Function 15S Set Monitor Off Screen\nThe following screen is used to set locations for no monitoring in COBOL programs; it specifies two locations:\n\u2022Specifies the first executable statement in paragraph A-TEST-EXIT.\n\u2022Indicates statement number 125 in the program.\nProgram monitoring is dropped (or continues unmonitored) whenever these locations are executed.\n   CA InterTest MONITORING COMMAND BUILDER  SEGMENTED MONITORING LOCATIONS  14\n  \n     SET `monitor off' option for  PROG=COBDEMO in any of the following fields: \n    (For qualification by nested program name, specify 'Programid:Label')      \n \u2192Paragraph A-TEST-EXIT___________________     _______________________________ \n     Names:  _______________________________     _______________________________ \n             _______________________________     _______________________________ \n   Statement \n \u2192  Numbers: 125__    _____    _____    _____    _____   _____    _____    _____ \n  \n    Offsets: _____    _____    _____    _____    _____   _____    _____    _____ \n  \n  \n            user ID (or .ANY) who will execute the program:             CARAR01        \n \nNOTE\nThere are similar versions of this menu for Assembler and PL/I users.\nSpecify multiple monitor off locations on this menu. Valid locations are as follows:\n\u2022COBOL (paragraph names, statement numbers, or hex offsets)\nNOTE\nYou cannot specify COBOL data names as segmented monitoring locations.\n\u2022Assembler (labels or hex offsets)\n\u2022PL/I (PL/I labels, statement numbers, or hex offsets )\nAfter specifying the locations, press Enter .\nCNTL Function 15R Remove Monitor Off Screen", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3e6044170623-1", "text": "After specifying the locations, press Enter .\nCNTL Function 15R Remove Monitor Off Screen\nSpecify individual locations to be removed exactly as you set them, or by the ID number shown on the InterTest for CICS\nstatus display. To quickly remove all locations at once, enter .ALL  in the first field on the menu and the same user ID\n(or .ANY) used to set the options. The Monitoring Command Builder Segmented Monitoring Locations screen is used to\nremove the monitor off locations that were previously set in the program using the ID number shown in the status report.\nPress Enter  after specifying the locations.\nCNTL Commands\nBefore using command syntax to specify segmented monitoring, see Notes and Warnings.\nSet MON and NOM Options\nTo set one or more MON options; use either of the commands shown next. To set one or more NOM options; use NOM\ninstead of MON in these commands.\n 1078", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aefe815151a7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n CNTL=ON,PROG=progname,MON=locn\n CNTL=ON,PROG=progname,MON=(locn1,locn2, ...,locn9)\n \nprogname\nIndicates one program.\nlocn\nSpecifies an address (from six- to eight-hexadecimal digits), offset (from one- to five-hexadecimal digits),\nstatement number (a decimal number preceded by #), COBOL paragraph name, Assembler or PL/I label\n(enclosed in apostrophes).\nTo specify a location, use the same format as for breakpoints.\nAt a breakpoint display, enter the abbreviated command form to see this Monitor Table entry:\n CNTL=ON*,MON=... or  CNTL=ON*,NOM=...\n \nOther options, including breakpoints, precede or follow within the same CNTL command.\nRemove MON and NOM Options\nTo remove one or more MON options, use one of the following command forms. To remove all NOM options, use NOM\ninstead of MON in these commands\n CNTL=OFF,PROG=progname,MON=ID=id\n CNTL=OFF,PROG=progname,MON=locn\n CNTL=OFF,PROG=progname,MON=ID=(id1,id2, ...,id9)\n CNTL=OFF,PROG=progname,MON=(locn1,locn2, ...,locn9)\n \nprogname\nIndicates the name of one program.\nid\nIndicates same number as the ID= number displayed by the InterTest for CICS Inquiry Report (obtained by\nCNTL=INQ or, at breakpoint, by pressing PF3).\nlocn", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aefe815151a7-1", "text": "CNTL=INQ or, at breakpoint, by pressing PF3).\nlocn\nSpecifies an address (from - to eight-hexadecimal digits), offset (from one to five hexadecimal digits), statement\nnumber (a decimal number preceded by #), COBOL paragraph name, Assembler or PL/I label (enclosed in\napostrophes).\nTo specify a location, use the same format as for breakpoints.\nSpecify up to nine IDs or locations, separated by commas and enclosed in parentheses.\nTo remove all MON options for a Monitor Table entry, use the form:\n CNTL=OFF,PROG=progname,MON=.ALL\n \nAt a breakpoint, use the abbreviated command form to see this Monitor Table entry:\n CNTL=OFF*,MON=...\n CNTL=OFF*,NOM=...\n \nOther options, including breakpoints, precede or follow within the same CNTL command.\n 1079", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ecec9b8aa66d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nThe command CNTL=OFF,PROG=progname  does not remove the MON or NOM entries for a program. To\nremove the MON and NOM options, you must explicitly specify them.\nExamples\nThe following are command examples of specifying MON and NOM options.\nTo selectively monitor the program COBPROGA from paragraph A-TEST to the paragraph name A-TEST-EXIT, specify:\n CNTL=ON,PROG=COBPROGA,MON='A-TEST'\n \nThis command declares a MON option for the first machine instruction in A-TEST. InterTest for CICS monitoring starts\nwhen the first machine instruction at A-TEST is executed.\nThe following command declares a NOM option for the first machine instruction in statement 123. InterTest for CICS\nmonitoring stops prior to the execution of this statement.\n CNTL=ON,PROG=COBPROGA,NOM=#123\n \nThe following command declares a NOM option for the first machine instruction in the paragraph A-TEST-EXIT.\n CNTL=ON,PROG=COBPROGA,NOM='A-TEST-EXIT'\n \nThe following command declares the same options as the three preceding commands.\n CNTL=ON,PROG=COBPROGA,MON='A-TEST',NOM=(#123,'A-TEST-EXIT')\n \nThe following command selectively removes the two NOM options that were displayed by an Inquiry Report with ID=\nnumbers 02 and 03.\n CNTL=OFF,PROG=COBPROGA,NOM=ID=(02,03)\n CNTL=OFF,PROG=COBPROGA,MON=.ALL,NOM=.ALL,LET=.ALL\n \nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ecec9b8aa66d-1", "text": "NOTE\nAny non-sequential passing of control (such as PERFORM, GO TO, and so on), executed between the MON\nlocation at A-TEST and the NOM location at\nA-TEST-EXIT could result in InterTest for CICS monitoring outside the designated range.\nNotes and Warnings\nThe following information contains notes and warning that you should be aware of when using InterTest for CICS.\nLocation Restrictions\nThe following bullets list location restrictions:\n 1080", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eadf4a1d621e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Regardless of how they are set (Source Listing, Menu, or single-line command); each of these options must be placed\non the first byte (the op-code) of a machine instruction that resides in non-store-protected virtual storage. Because the\ncode must not be store-protected, the application programs must not reside in the LPA, ELPA, or ERDSA.\n\u2022Regardless of how they are set (Source Listing, Menu, or single-line command); each of these options must be placed\non the first byte (the op-code) of a machine instruction that resides in non-store-protected virtual storage. Because the\ncode must not be store-protected, the application programs must not reside in the LPA, ELPA, or ERDSA.\n\u2022Any piece of code with these options must remain resident at the same virtual storage address until the options are\nremoved.\n\u2022These options cannot be placed on sequential statement numbers or instruction addresses; that is, these options must\nbe separated by at least one machine instruction.\n\u2022In Command Level CICS applications within code generated by an EXEC CICS, these options must not be placed on\nthe LOAD 15 that precedes the BALR 14,15 or on that BALR.\nUsage Notes and Restrictions\nThe following bullets list usage notes and restrictions:\n\u2022Declare other InterTest for CICS options, such as breakpoints, bypasses, and so on, at the same locations as the MON\nand NOM options\n\u2022MON and NOM options are not remembered by the InterTest for CICS checkpoint, nor are they restored by the\nInterTest for CICS restart (CNTL=RESTART).\n\u2022The InterTest for CICS New Copy function does not work until all MON and NOM options are removed from the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eadf4a1d621e-1", "text": "affected program. The CEMT SET PROG (xxxxxxxx) NEWCOPY must not be performed until all MON and NOM\noptions have been removed.\n\u2022RELOAD=YES cannot be used for a Program Definition if the program will be debugged using MON or NOB options.\n\u2022You cannot use the CICS installation parameter 'RENTPGM=PROTECT' if you plan on using MON or NOM options for\nany program that is linked as RENT, AMODE=31 and RMODE=ANY.\n\u2022There is a limit of 255 MON or NOM options per CICS region.\n\u2022A MON option causes InterTest for CICS monitoring, regardless of the InterTest Exclusion Table.\n\u2022Use these options to control application programs only. InterTest for CICS will accept them outside the scope of\napplications programming, such as CICS Exits or subsystem interfaces, but the results are unpredictable.\n\u2022Do not place MON entries in programs that are used in PLT shutdown processing.\n\u2022InterTest for CICS monitoring for a program cannot be removed until any MON and NOM options declared for the\nprogram are removed. To remove all MON and NOM options, specify:\n CNTL=OFF,PROG=progname,MON=.ALL,NOM=.ALL\n \nProgrammed Breakpoints Usage\nProgrammed breakpoints (PBP) are intended primarily for users of PL/I who want to display data areas that InterTest\nfor CICS normally cannot display or who do not have symbolic information for their programs. Incorporate programmed\nbreakpoints into COBOL and Assembler code.\nProgrammed breakpoints differ from other InterTest for CICS breakpoints because they are actually coded by the\nprogrammer into the tested program. A programmed breakpoint occurs because it was written into the monitored\nprogram in the form of a special CALL statement that identifies the data areas to display. The Detailed Breakpoint display", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eadf4a1d621e-2", "text": "automatically shows, in dump format, up to three data areas named in the CALL statement parameters. There is no need\nto enter CORE commands to display these areas. However, if there are more than three data areas, use the command\nCORE=ARGnn to display them.\nIf you are using the Source Listing Breakpoint facility, InterTest for CICS stops the program at the programmed breakpoint.\nPress  PF3 DET BKPT to display the Detailed Breakpoint screen to view the requested data areas.\n 1081", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f927887ce64f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe programmed breakpoint will not occur unless the automatic breakpoint facility is active. If this facility is not active,\nthe programmed breakpoint CALL has no effect  on program execution. The programmed breakpoint also does not affect\nprogram execution if the program is not monitored by InterTest for CICS (the called routine only does a return). However,\na small amount of overhead is added to the program's execution. For this reason, programmed breakpoints should be\nremoved before the program is put into production.\nProgrammed Breakpoints Coding\nTo execute a programmed breakpoint, add a special CALL statement to the program source code at the location where\nyou want the breakpoint to occur. The CALL statement passes control to an entry point named PBP. Code the CALL\nstatement according to the rules of the programming language being used. It also passes a number of arguments or\nparameters. Include a literal that describes the location of the programmed breakpoint as the first parameter so that the\nuser, especially the PL/I user, identifies the breakpoint easily.\nWhen control comes to the program location where the programmed breakpoint should occur, InterTest for CICS executes\nthe programmed breakpoint just like an automatic breakpoint, except that in the data portion of the display 16 bytes of the\nfirst three passed parameters are automatically displayed. In addition, a CORE command keyword is provided to display\nthe parameters.\nThe small Assembler programmed breakpoint load module, which is identical for all programming languages, must\nbe prepared by your systems programmer and assembled and link-edited into the proper language library so that it is\nautomatically included in your module as a result of the CALL. The program follows:\n PBP CSECT   \n     SR  15,15   \n     BR  14  \n     DC  C'PBPINTERTEST' \n     END PBP", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f927887ce64f-1", "text": "DC  C'PBPINTERTEST' \n     END PBP \n \nDeclare a Programmed Breakpoint in a PL/I Program\nA PL/I program with a programmed breakpoint must be coded to define the entry point as passing parameters in\nAssembler fashion, as shown next:\n DCL PBP ENTRY OPTIONS(ASSEMBLER);\n \nOnce this is done, code the calls in the usual manner.\nExample\n WRITE_RESPONSE:\n   RESPONSE = ERROR CODE;\n   CALL PBP ('WRITE_RESPONSE',RESPONSE,ADDR(REC_SIZE));\n \nAt this programmed breakpoint, the breakpoint display shows the following data areas:\n\u2022The characters WRITE_RESPONSE tell you which programmed breakpoint (if many was coded) is being executed\n\u2022The first 16 bytes of the field named RESPONSE\n\u2022The full word that contains the address of the field named REC_SIZE\nNOTE\nIf you do not include parameters in the CALL statement, a programmed breakpoint still occurs but no data is\ndisplayed.\n 1082", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4f42fd8ab0c8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDeclare a Programmed Breakpoint in a COBOL Program\nThe CALL statement that sets up a programmed breakpoint in a COBOL program is coded in the standard manner as\nfollows:\n WRITE-RESPONSE.\n   MOVE ERROR-CODE TO RESPONSE.\n   CALL 'PBP' USING RESPONSE.\n \nAt this programmed breakpoint, the breakpoint display shows the first 16 bytes of the field named RESPONSE.\nIf you do not include parameters in the CALL statement, a programmed breakpoint still occurs but data is not\nautomatically displayed.\nDeclare a Programmed Breakpoint in an Assembler Program\nIn Assembler you must use the CALL macro, coded so that the last parameter is marked as such, or coded without\nparameters. Because of the restrictions of the CALL macro, it is often practical not to code parameters. The breakpoint\ndisplay shows the location of the programmed breakpoint and the contents of the registers.\nIf you do not include parameters in the CALL statement, a programmed breakpoint still occurs but data is not\nautomatically displayed.\nRemove a Programmed Breakpoint\nOnce you code a programmed breakpoint CALL in a program, the breakpoint occurs every time execution reaches the\nprogrammed breakpoint's location during an interactive session. The only way to deactivate the programmed breakpoint is\nto replace the BALR 14,15 instruction in the program, which is contained in the CALL statement, by a NOPR 0. When the\ntask is waiting at breakpoint, do this easily by issuing the command:\n CORE=CURR=CHGX'0700'\n \nHowever, since this modifies the program's code, the programmed breakpoint will not occur again until the program is\nreloaded by CICS.\nAfter program testing is complete, the programmed breakpoint CALL statements should be removed for improved\nperformance.\nMonitoring CICS/FEPI Applications", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4f42fd8ab0c8-1", "text": "performance.\nMonitoring CICS/FEPI Applications\nThe Front-End Programming Interface (FEPI) provides terminal emulation using virtual terminals defined to a CICS region.\nThese virtual terminals, called nodes, communicate with back-end processes that run either in the same CICS region or\nin a remote region. Front-end processes, which are coded with EXEC CICS FEPI commands, communicate with both real\nand virtual terminals.\nInterTest for CICS lets both front-end and back-end processes be tested. However, the terminal IDs must be properly\nspecified when breakpoints are set.\nSet Monitoring and Breakpoints for a Front-End Process\nSet monitoring and breakpoints as usual when testing a front-end process only.\nSet Monitoring and Breakpoints for a Back-End Process\nTurn on monitoring as usual for a back-end process running in a local CICS region.\n 1083", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eba450a193f7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo set breakpoints for a back-end process running in a local region, specify both the terminal at which the process is\nrunning and the terminal to receive breakpoints, as follows:\n\u2022Term ID where breakpoints take effect: (F=)\nThe virtual terminal assigned by CICS. Specify either an actual virtual terminal name or .ANY if the terminal is\nassigned from a pool and its name is not known.\n\u2022Term ID that receives the breakpoints: (T=)\nThe real terminal to which breakpoints should be sent.\nIt is important that breakpoints  not be sent to a virtual terminal because this could disrupt the application dialog screen\nflow.\nIf the back-end process is running in a remote CICS region, turn on monitoring in the remote region and ensure that the\nterminal that receives breakpoints is a real terminal connected to the remote region.\nSet Breakpoints for Both Front-End and Back-End Processes\nTo set breakpoints for both front- and back-end processes that are running concurrently, follow the steps outlined in\nthe previous sections. However, make sure that  two real terminals are available for receiving breakpoint displays: one\nfor breakpoints from the front-end process, and one for breakpoints from the back-end process. For example, if both\nprocesses are running in the same CICS region, you might enter the following commands from TER1:\n CNTL=ON,PROG=FRONTEND,UBP=#1\n CNTL=ON,PROG=BACKEND,UBP=((#1),F=VIR1,T=TER2)\n \nBreakpoint displays for program FRONTEND are sent to TER1, the terminal at which the command was issued.\nBreakpoint displays for program BACKEND are sent to TER2.\nIf the back-end process is running in a remote CICS region, perform these steps:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eba450a193f7-1", "text": "If the back-end process is running in a remote CICS region, perform these steps:\n1.Set monitoring and breakpoints for the front-end  process in the local region.\n2.Set monitoring and breakpoints for the back-end  process in the remote region from any real terminal.\nTIMEOUT Values\nIf a TIMEOUT(seconds) parameter is specified on an EXEC CICS FEPI command when InterTest for CICS is monitoring\na back-end process, all breakpoint activity must be completed within the specified time. Otherwise, the front-end virtual\nterminal session times out and the back-end process could abend. To avoid this, it is strongly recommended that the FEPI\nTIMEOUT value be set to zero during testing. Change it to an appropriate value when testing is completed.\nInterTest for CICS with the IBM EDF (EXEC Debugging Facility)\nThe EDF facility, which is activated by the CEDF transaction and described in the IBM CICS/VS Application Programmer's\nGuide Command Level , does not interfere with EDF, except when EDF presents the EDF breakpoint display of the\nprogram being monitored by InterTest for CICS. EDF incorrectly indicates the location of the command since commands\nare issued by InterTest for CICS, not by the program.\nAdvantages of InterTest for CICS Over EDF\nInterTest for CICS offers many advantages over the EDF facility, including the following benefits:\n 1084", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "94f8511b35ed-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022The ability to set breakpoints anywhere in the program (not just at EXEC CICS commands).\n\u2022Data display/modification by symbolic names. This means the programmer does not need the most recent listing of the\ntested program, as long as the data names or paragraph names (labels in Assembler) remain the same.\n\u2022Monitoring with the ability to detect any illegal action of the program between CICS commands. CICS abends are\nintercepted by EDF, but damage might have occurred on the way to the abend, and EDF might not give any specifics\non the problem.\n\u2022The ability to declare an unconditional or conditional breakpoint at a specific location -- the EXEC CICS call at the point\nwhen the EXEC CICS call parameters are already formatted. At that time change the parameters (for example, by\nissuing the CORE=ARGnn command) before you let the command execute.\n\u2022The ability to set request breakpoints for a particular type of CICS command, regardless of where in the program\nit occurs, or for all EXEC CICS commands, or for all except some EXEC CICS commands. For example, with one\nspecification set breakpoints at all File Control commands or at all READ or WRITE commands.\nUsing InterTest for CICS with EDF\nIf you want to use InterTest for CICS with EDF, turn on EDF before you begin monitoring a program with InterTest for\nCICS. Moreover, when a monitored program is stopped at a request breakpoint for an EXEC CICS command, activate\nEDF by entering any character in the field marked EDF in the lower right corner of the Detailed Breakpoint display.\nWhen InterTest for CICS and EDF are being used on the same task, be aware of the following points:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "94f8511b35ed-1", "text": "\u2022If an InterTest for CICS breakpoint is set at an EXEC CICS command, the InterTest for CICS breakpoint occurs before\nthe command is passed to CICS.\n\u2022At the breakpoint, the programmer reviews and changes any parameters of the command before telling InterTest for\nCICS to continue with the task.\n\u2022InterTest for CICS checks the parameters and, if necessary, halts the task at an automatic breakpoint.\n\u2022If that does not happen, the command is passed by InterTest for CICS to CICS for execution; that is, to the EXEC\nInterface.\n\u2022Subsequently, EDF presents the before a command breakpoint. The EDF facility, however, is in control at that time and\nany changes by you during the EDF breakpoint cannot be checked by InterTest for CICS.\n\u2022Only after the command is executed, the EDF breakpoint display opens, and EDF is told to continue with the task can\nInterTest for CICS resume control and continue monitoring.\nCNTL Commands and Menus\nThe primary task of InterTest for CICS is to monitor programs so that it detects and prevents errors. The InterTest for CICS\nCNTL transaction performs all monitoring functions.\nNOTE\nThe CNTL Monitoring Command Builder menu topics are included here as a reference for InterTest for CICS\nusers familiar with this method of performing monitoring functions from previous releases.\nCNTL Capabilities\nUse the CNTL transaction to perform these functions:\n\u2022Monitoring\n\u2022Breakpoints\nMonitoring\nSet and remove monitoring for one or more programs, all the programs executed by a transaction, or all the programs\nexecuted from a terminal.\n 1085", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a02306457593-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBreakpoints\nSet and remove unconditional or conditional breakpoints.\nSet and remove request breakpoints prior to CICS commands, calls to DL/I or DB/2, and calls to database software.\nMonitoring Options\nWith the InterTest for CICS CNTL feature, you can:\n\u2022Set and remove statement tracing options for COBOL programs, including data monitoring\n\u2022Dynamically replace one or more CICS resources (programs, files, temporary storage, transient data queues) used by\na program\n\u2022Override default protection rules\n\u2022Set and remove special monitoring options, such as limiting the number of times a program is monitored or preventing\na program from updating a file\n\u2022Provide symbolic support for programs that consist of separately compiled modules brought together when the\nprogram is link-edited (composite support)\n\u2022Set and remove non-interactive monitoring sessions for a program executed by a transaction, or for all programs\nexecuted from a terminal\nStatus Display, Utility, and System Options\nWith the InterTest for CICS CNTL feature, you can:\n\u2022Display the status of monitored programs, transactions, or terminals\n\u2022Display the contents of InterTest for CICS tables and files\n\u2022Reset monitoring for a recompiled program\n\u2022Establish monitoring options for the entire system\nResume Task Execution\nWith the InterTest for CICS CNTL feature, you can resume execution of a task halted at a breakpoint.\nNOTE\nUse the CNTL menus and screens or CNTL commands to perform all of the functions listed in the previous two\nsections. Additional options, specified by commands, are available to perform more specialized functions.\nInitiate Monitoring\nInterTest for CICS provides many ways of initiating monitoring and performing other CNTL functions:\n\u2022Source listing facility\n\u2022ITST menus and fill-in screens\n\u2022CNTL menus and fill-in screens", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a02306457593-1", "text": "\u2022ITST menus and fill-in screens\n\u2022CNTL menus and fill-in screens\n\u2022CNTL commands\nWith the CNTL facility use one method exclusively or use the mix-and-match method -- even during one test session,\ndepending on your specific testing needs.\nExample\nUse the source listing facility to initiate monitoring and set breakpoints, the CNTL menus and screens to set special\noptions, and a single-line command to resume execution of a task.\nThe easiest way to turn on monitoring and set breakpoints for a single program is to use the source listing facility. For\na new or infrequent user, this method is strongly recommended. Turn on monitoring by pressing a PF key, and set a\n 1086", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7a460b8e2454-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nbreakpoint by entering a single keystroke directly on your program's source listing. For more information about this facility\nand what to do when your program halts at a breakpoint, see Source Listing Facility for InterTest.\nTo take advantage of the full range of InterTest for CICS monitoring capabilities, use the CNTL Monitoring Command\nBuilder menus and screens or enter CNTL commands. Nearly all the monitoring functions are implemented either way, so\nselect the method that suits you best.\nThe CNTL Monitoring Command Builder menus and screens make it easy for you to specify the necessary information\nwithout worrying about command syntax. All you have to do is select the function you want and enter the data -- InterTest\nfor CICS creates the right command for you. Online Help is available from every screen using PF1 to provide you with\nmore information.\nIf you prefer, enter single-line CNTL commands to specify monitoring functions. More experienced users often find it faster\nto enter commands directly.\nTo access online Help when entering single-line commands, type Help on a clear screen. InterTest for CICS displays the\nTransaction Codes screen. Press Enter  and InterTest for CICS displays the help facility master menu. Two main topics\n(program monitoring and breakpoints) and their associated subtopics provide information on CNTL commands.\nMonitor Command Building Menus and Screens\nThis section describes how to use the CNTL Monitoring Command Builder menus and screens to perform the following\nCNTL functions. The order in which CNTL functions are described corresponds to their order on the Function Selection\nMenu.\nFunction Selection Menu\nThe main menu for selecting CNTL functions.\nSetting and Removing Monitoring\nBegin and end monitoring for programs, transactions, or terminals.\nSetting and Removing Unconditional Breakpoints\nSet and remove unconditional breakpoints.\nSetting and Removing Conditional Breakpoints", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7a460b8e2454-1", "text": "Set and remove unconditional breakpoints.\nSetting and Removing Conditional Breakpoints\nSet and remove conditional breakpoints.\nSetting and Removing Request Breakpoints\nSet and remove request breakpoints before CICS commands, calls to DL/I, DB2, and SQL/DS, and calls to\ndatabase software.\nSetting and Removing Statement Trace Options\nSet and remove statement tracing and data monitoring for COBOL programs.\nSetting and Removing Replacement Options\nDynamically change CICS resources: programs, files, transient data queues, temporary storage.\nSetting and Removing Protection Options\nBypass InterTest for CICS rules that protect main storage, the CSA, and load modules.\nSetting and Removing Special Options\nModify monitoring rules (for example, prevent a program from updating a file, allow a program to branch to\nanother program, limit the number of times a program is monitored).\nSetting and Removing Composite Support\nProvide symbolic support for a program that consists of separately compiled modules.\nStatus Display\nDisplay the monitoring status of a program, transaction, or terminal.\nUtility Options\nDisplay the contents of InterTest for CICS tables and files, and reset monitoring for a recompiled program.\n 1087", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8232127a1aef-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSystem-Wide Options\nRequest monitoring options on a system-wide basis.\nResume Task Execution\nResume execution of a task stopped at a breakpoint.\nAccess the Monitoring Command Builder Main Menu\nTo display the Monitoring Command Builder main menu (the Function Selection Menu), enter CNTL  on a clear screen, or\nenter CNTL on the command line of any source listing, detailed breakpoint, or CORE screen.\nThe Function Selection Menu\nThe Function Selection screen is the main menu for the Monitoring Command Builder. This menu lists the different CNTL\nfunctions detailed later.\nIf you select this function: Also enter this:\n10 through 22 In second field, enter S or R to specify SET or REMOVE. If left\nblank, it defaults to S.\n10, 13, 16, 20, 21, 22, 24, or 30 Enter the program names, transaction codes, or terminal names.\nSpecify from one to six programs, one to nine transactions, or\none to nine terminals, but you cannot combine different types of\nentries. Specify .ALL to indicate all programs, transactions, or\nterminals. Also specify .OPTIONS in the Program Names field to\nset options for all programs. Optionally, specify a CICS user ID,\nsuch as MARY01, or .ANY to override the user ID default.\n11, 12, 14, 15,or 23 In the Program Names field, enter one program name. Optionally,\nspecify a CICS user ID, such as MARY01, or .ANY to override the\nuser ID default.\n31, 32, or 33 Do not specify program names, transaction codes, terminal\nnames, or a user ID value.\nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8232127a1aef-1", "text": "names, or a user ID value.\nNOTE\nIf a program is stopped at a breakpoint and you type CNTL  in the command line to access the Function\nSelection Menu, InterTest for CICS displays the name of the monitored entry (program, transaction, or terminal)\non this screen.\nWhen you have entered all the necessary information, press Enter . In most cases, a second screen opens. If you have\nspecified multiple programs, transactions, or terminals, the names of all the entries display on subsequent screens.\nWhen you set breakpoints, replacement, protection, special options, or composite support, you automatically set\nmonitoring for the programs, transactions or terminals that you specify. So, for example, it is not necessary to set\nmonitoring and set breakpoints; setting breakpoints accomplishes both functions.\nHowever, when you remove  breakpoints, replacement, protection, special options, or composite support, you do not\nremove monitoring for the programs, transactions, or terminals that you specify. Monitoring remains in effect until you\nexplicitly instruct InterTest for CICS to remove monitoring.\nGeneric Specification of Programs, Transactions, or Terminals\nWhen you set monitoring or monitoring options for a specific program, transaction, or terminal, InterTest for CICS creates\nan entry for that program, transaction, or terminal in the monitoring table. Also set monitoring or monitoring options\ngenerically by specifying asterisks, *, and plus signs, +, to replace characters in a program name, transaction code, or\nterminal name. These specifications are interpreted according to the rules for the CICS CEMT transaction.\n 1088", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "39e1f3db8be1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022An asterisk specifies any number of characters, including no characters. Specify more than one asterisk in a program\nname, transaction code, or terminal name. Do not, however, specify an asterisk by itself.\n\u2022A plus sign specifies just one character in a particular position. Specify more than one plus sign in a name or code. Do\nnot, however, specify a plus sign by itself.\n\u2022Combine asterisks and plus signs.\nExamples\nHere is how the following specifications are processed:\nABC*\nSpecifies all names or codes that begin with ABC, including ABC.\n*ABC\nSpecifies all names or codes that end with ABC, including ABC.\nAB*C\nSpecifies all names or codes that begin with AB and end with C with an unspecified number of characters in the\nmiddle.\nABC+\nSpecifies all four-character names or codes that begin with ABC followed by any one character.\n+ABC\nSpecifies all four-character names or codes that begin with any character followed by ABC.\nAB+C\nSpecifies all four-character names or codes that begin with AB followed by any one character and C.\nAB+C*\nSpecifies all names or codes that begin with AB followed by one character, C, and an unspecified number of\ncharacters.\nHierarchy Rules for Monitored Entries\nIt is important to know the priorities InterTest for CICS observes if more than one entry in the monitoring table applies to\nthe same program.\n\u2022A specific or generic program entry overrides a transaction entry, a terminal entry, and an .ALL specification\n\u2022A transaction entry overrides a terminal entry and an .ALL specification\n\u2022A terminal entry (specific or generic) overrides an .ALL specification\nExample\nSuppose you specify monitoring options for program ABC1 and different options for transaction TRN1. ABC1 executes", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "39e1f3db8be1-1", "text": "as part of that transaction. When ABC1 executes, the options specified for ABC1 override the options specified for TRN1.\nSimilarly, it is important to understand the priorities InterTest for CICS observes when a program, transaction, or terminal\nis specifically and generically declared for monitoring. A specific entry overrides a generic entry except when you request\nStatus Display. In this case, the generic specification takes precedence.\nSuppose you specify monitoring options for program ABC1 and different monitoring options for program ABC*. The\noptions specified for ABC* affect all programs whose names begin with ABC except for program ABC1 (and any other\nprograms beginning with ABC that have their own entries in the monitoring table). Monitoring for ABC1 is controlled by the\nspecific entry for that program. However, if you request a status display for program ABC*, you will get monitoring status\nreports for all programs that begin with ABC, including program ABC1 that has a separate monitoring table entry.\n 1089", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f7c0cafea544-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPF Keys\nExit from the Function Selection Menu by pressing a PF key. Most of these PF keys are also in effect on other Monitoring\nCommand Builder screens. The following bullets describe the function of each PF key.\nPF1 or 13\nInitiates the InterTest for CICS online help facility.\nPF2 or 14\nUnassigned\nPF3 or 15\nTerminates the Function Selection Menu screen and returns to the active breakpoint, if appropriate. Pressing\nClear does the same thing.\nPF4 or 16\nReturns to the source listing display facility.\nPF5 or 17\nUnassigned\nPF6 or 18\nUnassigned\nPF7\nUnassigned\nPF8\nDisplays your previous CNTL Monitoring Command Builder screen with the specified data.\nPF9 to end\nUnassigned\nMonitoring\nSet and remove monitoring for programs, transactions, or terminals directly from the Function Selection Menu.\nSpecify function 10, S or R, and the program names, transaction codes, or terminal names, and press Enter. For more\ninformation, see Function Selection Menu. This is the only screen you need to complete.\nYou can set a non-interactive monitoring session using CNTL options. For more information, see TFL Set Non-Interactive\nMonitoring.\nSet Monitoring\nWhen you set monitoring for a:\nProgram\nInterTest for CICS detects and prevents errors before  they occur. That means monitored programs will not abend\nor commit storage violations. InterTest for CICS monitors the program from whatever terminal it executes, even\nif it executes as part of a non-terminal owning task. Use the replacement, protection, or special options screen if\nyou want to restrict monitoring to a specific terminal.\nTransaction\nInterTest for CICS monitors all of the transaction's programs.\nTerminal", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f7c0cafea544-1", "text": "Transaction\nInterTest for CICS monitors all of the transaction's programs.\nTerminal\nInterTest for CICS monitors every program that executes at that terminal.\nNOTE\nInterTest for CICS will not monitor programs that begin with the prefix DFH (IBM CICS programs) or IN25\n(InterTest for CICS programs).\n 1090", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "881c8e63f522-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIf you set monitoring for a transaction or terminal, and a program executing as part of that transaction or at that terminal\nis stopped at an automatic breakpoint, InterTest for CICS automatically creates an individual entry in the monitoring\ntable for that program. This lets you set breakpoints and monitoring options specifically for that program. Similarly, if\nyou specify .ALL in the Program Names field on the Function Selection Menu or if you specify a generic program name,\nInterTest for CICS creates an individual monitoring table entry for any program monitored under that entry when it stops at\nan automatic breakpoint.\nSet the User ID for Monitoring\nMonitoring is sensitive to CICS user IDs.\nRemove Monitoring\nBefore you remove monitoring, you might want to produce a report of all InterTest for CICS monitoring activity to make\nsure other users are not currently testing the same programs. Press PF12  Status to produce a monitoring report.\nWhen you remove monitoring, you also remove all breakpoints and monitoring options specified for that program,\ntransaction, or terminal. A quick way of creating a new testing scenario for a program is to remove and then reset\nmonitoring with different breakpoints and options.\nNOTE\nRemember that you can also set monitoring by setting breakpoints, replacement, protection, special options, or\ncomposite support. However, if you remove breakpoints, options or composite support, monitoring remains in\neffect   for the specified programs until you specifically instruct InterTest for CICS to stop monitoring.\nUnconditional Breakpoints\nWhen you set unconditional breakpoints, InterTest for CICS halts the program at the specified locations. InterTest also\nautomatically monitors that program.\nTo set or remove unconditional breakpoints, specify function 11, S or R, and the program name on the Function Selection\nMenu, and press Enter. For more information, see The Function Selection Menu.\nSet Unconditional Breakpoints", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "881c8e63f522-1", "text": "Set Unconditional Breakpoints\nUse the Breakpoint Locations screen to set unconditional breakpoints.\nTo set breakpoints, enter the following information:\nSpecify up to nine breakpoint locations in fields.\nCOBOL\nFor COBOL program, specify a paragraph name or data name, a statement number, or the hexadecimal displacement\n(offset) from the beginning of the program.\nASSEMBLER\nFor an Assembler program, breakpoint locations are Assembler labels, datanames, or offsets.\nPL/I\nFor a PL/I program, breakpoint locations can be offsets or, if you have the PL/I symbolic option, PL/I labels or statement\nnumbers.\nFollow these rules when specifying information:\n 1091", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1f7b709ca2c4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022If you specify statement #1, InterTest for CICS sets a breakpoint at the first executable instruction in a COBOL\nProcedure Division, Assembler CSECT, or PL/I procedure.\n\u2022COBOL statements can contain more than one verb. In specifying statement numbers, indicate the verb at which\nthe breakpoint should occur. A statement number of nnn or nnn.0 indicates the first verb in the statement, nnn.1\nindicates the second verb, nnn.2 indicates the third verb, and so on. For example, a statement number entered as\n503.3 specifies a breakpoint at the fourth verb in statement number 503.\n\u2022If you specify a COBOL or Assembler data name, breakpoints are set at every reference to that data name.\n\u2022Enter an X in the All paragraph names field (COBOL) or All Assembler labels field to set breakpoints at all paragraph\nnames or all labels.\nOptional specifications:\n\u2022If you set a breakpoint within a loop, specify a value in the Enter 'n' to stop only every n'th time field to set how often\nthe program should be halted. For example, if you specify 3, the breakpoint occurs every third time the program\npasses through the loop.\n\u2022Specify the ID of the terminal where the program must be executing for breakpoints to take effect. If you leave this\nfield blank, it defaults to your current terminal. Enter .ANY to have breakpoints take effect at all terminals, even when\nthe program executes without a terminal. Enter .NO to have breakpoints take effect only when the program executes\nwithout a terminal.\n\u2022Specify the ID of the terminal to receive breakpoint displays. If you leave this field blank, it defaults to your current\nterminal. Enter .ANY to have breakpoint screens displayed at the terminal where the program is executing when", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1f7b709ca2c4-1", "text": "terminal. Enter .ANY to have breakpoint screens displayed at the terminal where the program is executing when\nbreakpoints occur.\n\u2022Specify the statement number of the indirect command that you want to invoke at the breakpoint you have set.\n\u2022Specify the user ID who must be executing the program for the breakpoint to take effect. Valid entries are .ANY or a\nspecific CICS user ID.\nWhen you complete entering all the necessary information, press Enter .\nExample\nThe following screen shows how to set unconditional breakpoints at four locations in the COBOL program COBDEMO.\nCA InterTest MONITORING COMMAND BUILDER  COBOL BREAKPOINT LOCATIONS   11 \n                                                                                \n    SET breakpoint locations for PROG=COBDEMO  in any of the following fields:  \n    (For qualification by nested program name, specify 'ProgramID:Label')\n                                                  \n   Para/Data return-transid________________      _______________________________ \n     Names: _______________________________      _______________________________ \n            _______________________________      _______________________________ \n  Statement                                        \n   Numbers: 1____    136__    174.2    _____    _____    _____    _____    _____ \n                                                                                \n   Offsets: _____    _____    _____    _____    _____    _____    _____    _____\n                                                                                \n            All paragraph names:  _                                             \n                                                                               \n           Enter 'n' to stop only every n'th time:                         ____ \n           Term ID (or .ANY or .NO) where breakpoints will take effect:    ____ \n           Term ID (or .ANY) that will receive the breakpoints:            ____ \n           Statement no. of indirect command(s) to be executed:         ________\n           user ID (or .ANY) who will execute the program              MARY01___ \nThe information in the previous screen causes breakpoints to occur at:\n 1092", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eca531978af6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Paragraph RETURN-TRANSID\n\u2022Statement 1 (the beginning of the Procedure Division)\n\u2022First verb in statement 136\n\u2022Third verb in statement 174\nBecause the user ID field specifies a single user and the terminal ID fields are left blank, the breakpoints take effect at any\nterminal under which User MARY01 is executing COBDEMO.\nRemove Unconditional Breakpoints\nIf you indicated that you want to remove unconditional breakpoints, the Remove Breakpoint Locations screen opens.\nCOBOL, PL/I, and Assembler versions of the Breakpoint Locations screen are available.\nTo remove a breakpoint, specify the information that you originally defined on the Set Breakpoint Locations screen, or\nenter its ID number on the bottom of the screen.\nThe ID number appears on the Detailed Breakpoint display. Press PF12 Status to request a status report for the program.\nThis report lists the ID of each breakpoint.\nNOTE\nTo remove all unconditional breakpoints from a program, enter .ALL in the Para/Data field, and press Enter .\nConditional Breakpoints\nWhen you set conditional breakpoints, InterTest for CICS halts the program at the specified locations only  if a condition is\nmet. Conditional breakpoints are very useful in isolating complex problems.\nTo set or remove conditional breakpoints, specify function 12, S  or R, and the program name on the Function Selection\nMenu, and press Enter. For more information, see The Function Selection Menu.\nSet Conditional Breakpoints\nFirst, InterTest for CICS displays the Conditional Locations screen.\nThis screen is similar to the screen used to specify unconditional breakpoints, and you should enter the information in the\nsame way. For more information, see Set Unconditional Breakpoints.\nA special feature lets you set a conditional breakpoint at  all instructions.\nTo set conditional breakpoints:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eca531978af6-1", "text": "A special feature lets you set a conditional breakpoint at  all instructions.\nTo set conditional breakpoints:\n1.Enter an x in the All Instructions field to request this option. If you request the All Instructions option and set a variable-\nchange breakpoint, the breakpoint takes effect whenever the value of the variable changes.\n2.Specify the breakpoint locations, and press Enter  to display the Conditional Breakpoint screen.\n3.Specify the condition that must be satisfied for the breakpoint to take effect on the Conditional Breakpoint screen.\nThere are two versions of the Conditional Breakpoint screen: a simplified version for COBOL users, and a detailed version\nfor PL/I and Assembler users and for those COBOL users who prefer this version.\nOn either version you, specify a condition in this format:\nleft side relational operator right side\n 1093", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b500c0ba9d68-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nVariable-Change Breakpoints\n\u2022COBOL and Assembler users set a conditional breakpoint to take effect whenever the value of a variable changes. To\ndo this, type x in the All Instructions field on the Conditional Locations screen.\n\u2022COBOL users must then specify the variable name on the Conditional Breakpoint screen.\n\u2022Assembler users must then specify the variable name on the Detailed Conditional Breakpoint screen, as discussed\npreviously in The Detailed Conditional Breakpoint screen.\nThe value entered in the Operator field determines if the breakpoint occurs whenever the value of the variable changes\n(NE) or only when the value increases, decreases, or does not change. Whenever you re-execute the program, the initial\nvalue of the variable is reset to its value at the beginning of program execution.\nLiteral Formats\nSpecify four types of literals for the right side of the comparison:\nCharacter\nSpecify character literals for comparisons with any field except a COBOL data name defined as COMP or\nCOMP-3. Enter the literal as C'character data', X'hexadecimal data' , or a combination of both. For example,\nC'ABC', X'0102', or C'ABC'X'0102'.\nPacked\nSpecify packed decimal literals for comparisons only with COBOL data names defined as COMP-3. Enter the\nliteral as P'number' . The number can be preceded by a minus sign. For example, P'123' or P'-123'.\nHalfword\nSpecify halfword literals for comparisons with COBOL data names defined as COMP with a length of four, as in\nS9(4) COMP. Enter the literal as H'number' . The number can be preceded by a minus sign. For example, H'12' or\nH'-12'.\nFullword", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b500c0ba9d68-1", "text": "H'-12'.\nFullword\nSpecify fullword literals for comparisons with COBOL data items defined as COMP with a length of eight, as in\nS9(8) COMP. Enter the literal as F'number' . The number can be preceded by a minus sign. For example, F'100'\nor F'-100'.\nFigurative Constants\nSpecify the following figurative constants for the right side of the comparison:\nValid Right Side\nSpecifications for the\nComparison\nZERO\nZEROS\nZEROESnumeric value 0 HIGH-VALUE\nHIGH-VALUEScharacter value X' FF'\nSPACE\nSPACESblank (X' 40' ) LOW-VALUE\nLOW-VALUEScharacter value X' 00'\nExample\nThe following sample screen shows how to set a conditional breakpoint in a COBOL program.\n           CA InterTest MONITORING COMMAND BUILDER  CONDITIONAL BREAKPOINT   \n                                                                              \n   Enter LEFT SIDE                                                       \n       Data Name tolen ________________________________________________________\n 1094", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5ba417ca5d12-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                                                                              \n      Enter OPERATOR (EQ, NE, GT, LT, GE, LE):  lt                               \n                                                                              \n   Enter RIGHT SIDE                                                           \n       Data Name ______________________________________________________________\n          OR                                                   \n       Literal 80______________________________________________________________\n                                                                               \n                                                                               \n                                                                             \n _ Enter  S  to Drop monitoring on a true condition                          \n                                                                             \n                                                                             \n                                                                             \n Press PF9 to go to complex conditional screen if necessary            \n                                                           \n\u2022The left side of the comparison specifies the data name TOLEN.\n\u2022The relational operator is LT (less than).\n\u2022The right side of the comparison specifies the literal 80.\nThis breakpoint takes effect only if the value in the data name TOLEN is less than 80. The breakpoint locations are all the\ninstructions, as previously specified on the Conditional Locations screen.\nRemove Conditional Breakpoints\nWhen you specify that you want to remove  conditional breakpoints, the Remove Conditional Locations screen opens.\nThe easiest way to remove a conditional breakpoint is from the Monitoring Status display. For more information, see\nMenus and Displays. To remove all conditional breakpoints from a program, enter .ALL in the Para/Data field, and press\nEnter.\nThe Detailed Conditional Breakpoint Screen\nWhen Assembler and PL/I users want to specify conditional breakpoints complete the Conditional Locations screen and\npress PF9, the screen opens. COBOL users access this screen by pressing PF9 from the COBOL Conditional Breakpoint\nscreen.\nSpecify the following values:\n\u2022The left side of the comparison must be an area of core. Enter information in  one of these four fields:\n\u2013Data name\n\u2013Register\n\u2013COBOL BLL cell\n\u2013Area identified by a CORE keyword\n\u2022The relational operator:\n 1095", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f08ecee1d118-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2013EQ for equal\n\u2013NE for not equal\n\u2013GT for greater than\n\u2013LT for less than\n\u2013GE for greater than or equal to\n\u2013LE for less than or equal to\n\u2022(Optional) The length of the left side or right side of the comparison. For more information, see Length of the\nComparison.\n\u2022The right side of the comparison, which is an area of core or a literal. Enter information in one of these five fields: a\ndata name, a register, a COBOL BLL cell, an area identified by a CORE keyword, or a literal. For more information,\nsee CORE Keywords and Literal Formats.\n\u2022(Optional) Adjusts a CORE location by specifying offsets (displacements). Each offset must be preceded by one of the\nfollowing operands:\n\u2013+\n\u2013-\n\u2013@ (indirect addressing below the 16-megabyte line) % (indirect addressing above the 16-megabyte line; XA\nsystems only)\n\u2013Literals cannot be modified by offsets.\nLength of the Comparison\nExplicitly define how many bytes of the left side or right side specification should be compared. Certain storage locations\nhave implicit lengths:\n\u2022A register or COBOL BLL cell has an implicit length of four bytes\n\u2022The storage locations referred to by the CORE keywords MXR, MXS, and TAL have implicit lengths of four bytes\n\u2022The implicit length of a COBOL data name is its field length as defined in the DMAP\n\u2022The length of a literal is the number of bytes it contains; any length specification is ignored\nDefine both left side and right side lengths for a packed decimal (COMP-3) comparison. For all other comparisons, define\nonly one length. If you define both lengths, the smaller length is used.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f08ecee1d118-1", "text": "only one length. If you define both lengths, the smaller length is used.\nThe maximum permissible length for the left side or right side is 16 bytes for packed decimal data and 255 bytes for all\nother data types.\nLiteral Formats\nFor more information about specifying literals, see Figurative Constants.\nCORE Keywords\nSpecify the following CORE keywords on the left side or right side of the comparison:\nCMAR\nFirst byte of the EXEC CICS Communications Area for the task\nCSA\nFirst byte of the CSA\nCURR\nNext Assembler instruction to be executed\nCWA\nFirst byte of the CWA\n 1096", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "869c5f818041-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCWK\nFirst byte of the COBOL program's Working-storage\nDSA\nFirst byte of the program's DSA\nITBE\nFirst byte of the next instruction to be executed\nLCL\nFirst byte of the COBOL program's local-storage\nMXR\nInterTest for CICS maximum CICS request counter (implicit length = 4)\nMXS\nInterTest for CICS maximum storage counter (implicit length = 4)\nOPFL\nFirst byte of the optional features List\nPGM=*\nFirst byte of the monitored program\nPREV\nLast Assembler instruction executed\nRnn\nA register ( nn is a decimal from 1 to 15) (implicit length = 4)\nTAL\nInterTest for CICS tally fullword (implicit length = 4)\nTERM=*\nFirst byte of the terminal table entry of the current terminal\nTGT\nFirst byte of the COBOL TGT for the monitored task\nTIOA\nFirst byte of the first TIOA of the task\nTWA\nFirst byte of the TWA of the monitored task\nRequest Breakpoints\nSet request breakpoints to halt a program prior to CICS commands and other program calls, such as calls to DL/I, DB2,\nor SQL/DS. Instruct InterTest for CICS to halt the program before every CICS command, or a type of CICS command,\nsuch as file control or program control commands. Specify that the program halts before specific commands, such as all\nREAD or WRITE commands. Once the program halts, Use all of the InterTest for CICS facilities to inspect and modify\nmain storage or auxiliary storage or to set additional options.\nTo set or remove request breakpoints:\n1.Specify function 13, S or R.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "869c5f818041-1", "text": "To set or remove request breakpoints:\n1.Specify function 13, S or R.\n2.Specify the program names, transaction codes, or terminal names on the Function Selection Menu, and press Enter.\nInterTest for CICS displays the Request Breakpoint Selection menu. Enter an x next to the options you want to select.\nYou can specify any of the following breakpoints:\nALL commands\nThe program halts prior to all CICS commands.\n 1097", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8e6047e167fe-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDL/I\nThe program halts prior to all DL/I calls.\nDB2\nThe program halts prior to all calls to DSNHLI (for DB2 users) or prior to all calls to ARIPRDI (for SQL/DS users).\nCALLS\nThe program is halted prior to calls to software that InterTest has been instructed to recognize at installation time.\nA second screen, where you specify the calls, displays.\nNOTE\nIf you select a type of CICS command, InterTest for CICS displays a second screen. For example, if you select\nFile Control, InterTest for CICS displays the File Control screen.\nNOTE\nPlace your cursor on a field and press F1 for a description of that field.\nWhen you have entered all necessary information, press Enter .\nTo remove requested breakpoints, use the Monitoring Status display. Alternatively, enter the information exactly as you\noriginally defined it.\nStatement Trace Options\nNOTE\nThese options are unrelated to the backtrace facility.\nSet Statement Trace options to save trace information for executed COBOL statements and to capture data values for\nthose statements. Remove the Statement Trace options to delete the trace data.\nTo set or remove Statement Trace options, follow these steps.\n1.Specify function 16, S or R.\n2.Specify the program names, transaction codes, or terminal names on the Function Selection Menu, and press  Enter .\nThe Statement Trace Options screen opens. For more information, see The Function Selection Menu.\nSpecify the following options on this screen. The equivalent option used in single-line commands is specified in\nparentheses.\nStatement tracing (TRC)\nInstructs InterTest for CICS to save trace information for every executed COBOL statement.\nData monitoring (DM)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8e6047e167fe-1", "text": "Data monitoring (DM)\nInstructs InterTest for CICS to capture data values for every executed COBOL statement. If data monitoring is\nselected, statement tracing is automatically activated. In addition, a specific terminal ID or user ID is required.\nTerm ID (or .ANY or .NO) where trace options will take effect\nSpecifies that the program be monitored and that Statement Trace options, if specified, take effect only when the\nprogram is executed at any terminal (.ANY), no terminal (.NO), or a specific terminal.\nUser ID (or .ANY) who will execute the program\nSpecifies that the program be monitored and that Statement Trace options, if specified, take effect only when the\nprogram is executed by any user (.ANY) or a specific user (a CICS user ID).\nRemove Statement Trace Options\nTo remove statement trace options, enter an x next to the options you want to remove. If you select statement tracing,\ndata monitoring is also removed. Enter the terminal ID and user ID information exactly as you originally defined it.\n 1098", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8b16b81a512a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReplacement Options\nSet replacement options to dynamically change the names of CICS resources (programs, files, transient data queues, and\ntemporary storage) specified in CICS CALLS by a monitored program. Remove the replacement options when you want\nthe program to use the resources defined in the program.\nSet Replacement Options\nWhen you specify replacement options for a transaction, the resources are replaced in all its programs. When you specify\nreplacement options for a terminal, the resources are replaced in all programs executing from that terminal.\nTo set or remove replacement options:\n1.Specify function 20, S or R,\n2.Specify the program names, transaction codes, or terminal names on the Function Selection Menu, and press  Enter .\nThe Replacement Options screen opens. For more information, see The Function Selection Menu.\nSpecify five options on this screen. The equivalent option used in single-line commands is specified in parentheses on the\nfollowing option list.\nReplace program name (RPC)\nAllows a program name to be replaced. Specify the original program name and the new name.\nReplace file name (RFC)\nAllows a file name to be replaced. Specify the original file name and the new name. The sample screen shown\npreviously specifies that program COBDEMO use file TFILE instead of PFILE.\nReplace TD queue name (RTD)\nAllows a transient data queue name to be replaced. Specify the original TD queue name and the new name.\nTS selection mask; TS replacement mask (RTS)\nAllows a temporary storage ID to be replaced. Specify the original temporary storage ID in the TS selection mask\nfield, and the new temporary storage ID in the TS replacement mask field. Specify both masks as eight bytes\nin either character (C'data') or hexadecimal (X'data') format. In the following example, STORAGE2 replaces", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8b16b81a512a-1", "text": "STORAGE1 in all temporary storage requests issued by the program.\nTS selection mask: C'STORAGE1'\nTS replacement mask: C'STORAGE2'\nLimit monitoring (TON)\nSpecifies that the program be monitored and that replacement options, if specified, take effect only when the\nprogram executes at the current terminal (*), a specific terminal (termid), or without a terminal (.NO).\nWhen you have specified the necessary information, press Enter.\nRemove Replacement Options\nTo remove a replacement option, specify the information exactly as you entered it. To remove all replacement options of a\nspecific type, enter .ALL  in the appropriate field.\nExample4\nTo remove all file replacement options, enter .ALL  in the Replace file name field.\nProtection Options\nThis section describes protection options.\n 1099", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b4ec732837fd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSet Protection Options\nSet options to override the InterTest for CICS default protection rules for modifying main storage, the CSA, and load\nmodules. Remove the protection options to reinstate the default protection rules.\nWARNING\nBecause the protection options can potentially damage your CICS system if misused, exercise caution in\nspecifying them. These options are password protected unless your site has removed this restriction.\nTo set or remove protection options follow these steps.\n1.Specify function  21, S or R .\n2.Specify the program name on the Function Selection Menu, and press Enter.\nThe Protection Options screen displays. For more information, see The Function Selection Menu.\nSpecify the following options on this screen. In the descriptions, the command syntax equivalent for each monitoring\noption is specified in parentheses.\nBypass storage protection (BYP)\nPermits a specified section of program code to modify any area of main storage, issue SVC instructions, or issue\nBALR, BASSM. or BASR 14,15 or 14,14 instructions.\n\u2022Specify the beginning and ending program addresses or program offsets. Specify addresses as six- to eight-\nhexadecimal digits, and offsets as one- to five-hexadecimal digits.\n\u2022If you specify .ANY in the From field and an address or offset in the To field, InterTest for CICS suspends\nmonitoring when any BALR, BASSM, or BASR 14,15 or 14,14 instruction passes control to the specified\nlocation. Monitoring resumes when the routine executed by the instruction returns control to the next byte after\nthe instruction.\n\u2022At a breakpoint, specify * in the From field and leave the To field blank to instruct InterTest for CICS to bypass\nthe current instruction.\nUnprotect CSA (CSA)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b4ec732837fd-1", "text": "the current instruction.\nUnprotect CSA (CSA)\nPermits a program to modify areas in the CSA. Specify the offset and the length in hexadecimal.\nUnprotect CWA (CWA)\nPermits a program to modify areas in the CWA. Specify the offset and the length in hexadecimal.\nUnprotect main storage area (LET)\nPermits a program to modify a designated area of storage. Specify the beginning address as six to eight\nhexadecimal digits. Specify the length of the area in hexadecimal.\nUnprotect load module (LET)\nPermits a program to modify a load module.\nProtect main storage area (PRO)\nPrevents a program from modifying a designated area of storage not protected by InterTest. Specify the beginning\naddress as six to eight hexadecimal digits. Specify the length of the area in hexadecimal.\nLimit monitoring (TON)\nSpecifies that the program be monitored and that the protection options, if specified, take effect only when the\nprogram executes at the current terminal (*), a specific terminal (termid), or without a terminal (.NO).\nRemove Protection Options\nTo remove protection options, enter the information exactly as you originally defined it. To remove all options of a specific\ntype, enter   .ALL  in the appropriate field.\nExample\nTo remove all bypass storage protection options, enter .ALL  in that field.\n 1100", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7357708a28fb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSpecial Options\nThis section discusses special options.\nSet Special Options\nSet special options to alter the InterTest for CICS standard monitoring procedures. Remove the special options to\nreinstate the default monitoring rules.\nTo set or remove special options, follow these steps.\n1.Specify function 22, S or R.\n2.Specify the program names, transaction codes, or terminal names on the Function Selection Menu, and press Enter .\nThe Special Options screen opens. For more information, see The Function Selection Menu.\nSpecify the following options on this screen. The equivalent option used in single-line commands is specified in\nparentheses.\nSource Listing Breakpoint (SLB)\nSpecifies that the Source Listing Breakpoint screen be displayed rather than the full breakpoint display screen.\nFor more information, see Source Listing Facility for InterTest.\nNo file updating (NUP)\nSpecifies that a monitored program not update any files. This option only affects VSAM and BDAM files;\ndatabases are unaffected.\nReentrancy check (RNT)\nPrevents a program from modifying its own code.\nFollow monitoring (FOL)\nInstructs InterTest for CICS to continue monitoring a program even if it branches directly to another program (wild\nbranch). All monitoring options remain in effect. Specify the following:\n\u2022ON when control passes to a program that does not have a PPT entry\n\u2022The name of the program when control passes to a program that has a PPT entry\n\u2022NOPPT instead of ON to reduce overhead when a program often branches to a program that does not have a\nPPT entry\n\u2022Note: Do not specify this option if control is passed to a program by a LINK or XCTL instruction. Such a\nprogram is monitored only if monitoring was specified for it.\nNumber of times to be monitored (MUS)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7357708a28fb-1", "text": "Number of times to be monitored (MUS)\nLimits the number of times a program should be monitored.\nLimit total size of CICS storage (MXS)\nLimits the amount of storage, including program storage, a program acquires.\nLimit total number of CICS requests (MXR)\nLimits the number of requests a transaction issues. This option is useful when a program is in a loop that includes\na CICS request.\nSetting for Structure Display Format (SDF)\nUse this option to override, by program, the global default setting. Specify the following:\n\u2022HEX to display data in hexadecimal / character format\n\u2022DATA to display data in Structure Display Format\nSet local automatic breakpoint (ABP)\nActivates the automatic breakpoint facility for a particular program, transaction, or terminal.\nSpecify the terminal to receive automatic breakpoint displays.\n 1101", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b3396da3ad21-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Asterisk (*) routes the display to the current terminal\n\u2022termid routes the display to a particular terminal\n\u2022.ANY routes the display to all terminals\n\u2022OFF instructs InterTest for CICS to abend the task instead of halting it at an automatic breakpoint\nNOTE\nThis option is useful when you do not want the breakpoint display routed to the terminal where the\nprogram is running, or when the display cannot be routed to that terminal (for example, a non-terminal\ntask or a task running on a non-3270 terminal). In those cases, specify the terminal to which breakpoint\ndisplays should be routed. The local automatic breakpoint option is also useful in a production\nenvironment when the global Automatic Breakpoint facility is disabled and you want to monitor a specific\nprogram, transaction, or terminal.\nLimit monitoring (TON)\nSpecifies that the program be monitored and that the special options, if specified, take effect only when the\nprogram executes at the current terminal (*), a specific terminal (termid), or without a terminal (.NO).\nRemove Special Option\nTo remove special options, enter an x next to the options you want to remove, or enter the information exactly as you\noriginally defined it.\nSet and Remove Composite Support\nThe InterTest for CICS composite support feature lets you take advantage of all of the InterTest for CICS capabilities\nwhen you test and debug composite modules. A  composite module is a load module defined in the PPT that consists\nof separately compiled or assembled parts brought together when the module is link-edited. The part of the composite\nmodule that receives control from CICS is referred to as the main  program ; the remaining parts are referred to as\nsubprograms . The main program and subprograms are written in the same or different languages.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b3396da3ad21-1", "text": "subprograms . The main program and subprograms are written in the same or different languages.\nComposite support lets you test and debug a subprogram as if it were a separate  program. This means you set\nbreakpoints and other monitoring options individually for any subprogram.\nInterTest for CICS provides   full symbolic support  for the main program and subprograms if you provide that information\nwhen the programs are compiled or assembled.\nFunction 23 on the CNTL Function Selection Menu is one method of accessing the Composite Support screen. An\nalternative method of accessing this screen is from the ITST monitoring menus.\nIndirect Commands\nThe InterTest for CICS indirect commands facility lets you define a set of commands that execute automatically or\nindirectly  at a predetermined location in a monitored COBOL or PL/I program. These commands are invoked from an\nunconditional, conditional, or request breakpoint.\nIn effect, indirect commands are executed at breakpoints within your program just as other InterTest for CICS line\ncommands issued from the Source Listing display, such as MOVE and GO, are used to alter the flow of your program's\nlogic. The difference is that indirect commands are executed automatically without issuing a breakpoint display. Once the\nindirect commands are performed, your program continues to execute normally.\nIndirect commands save you from having to recompile a program or manually correct an area of code every time it is\nencountered during a debugging session. With the indirect commands facility, you can:\n 1102", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3bc89c236166-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Change the flow of control in your program\n\u2022Test conditions based on specified variables\n\u2022Change the value of specified variables\n\u2022Create and execute commands as a group, like adding a new subroutine\n\u2022Automatically resume execution of your program at the same or different location\n\u2022Define abbreviations for variables with long names\nNOTE\nIndirect commands are not available for Assembler programs.\nNOTE\nIndirect commands are not supported in a CICSPlex environment and they are not saved in the MLOG when\nsession logging is turned on.\nWhen to Use Indirect Commands\nIndirect commands are used to correct the following sample program problems:\n\u2022A variable is not being initialized during processing. Using indirect commands initialize the variable every time the\nprogram is run and continue execution without recompiling.\n\u2022A new routine is needed in your program. Insert the code using indirect commands and continue executing your\nprogram without recompiling.\n\u2022A section of code is bad. To continue executing or testing without recompiling, write and invoke indirect commands to\ndirect InterTest for CICS to go around the bad source code or execute a new series of indirect command statements.\nStep Overview\nFor users familiar with the CNTL menus, use Function 24 of the CNTL Function Selection Menu to access the indirect\ncommands facility when you are coding the commands.\nStatus Display\nDetermine the monitoring status of one or more programs, transactions, or terminals by following these steps:\n1.Specify Function  30.\n2.Specify the program names, transaction codes, or terminal names on the Function Selection Menu, and press  Enter .\nIf you specify multiple programs, transactions, or terminals, InterTest for CICS displays the monitoring reports in the\norder in which you specified the entries.\nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3bc89c236166-1", "text": "order in which you specified the entries.\nNOTE\nThe status display accessed from the CNTL menu does not include the same formatting as the monitoring status\nreport discussed in other areas of this documentation.\nWARNING\nIt is advisable to determine the monitoring status of a program, transaction, or terminal before altering it.\nExample\nThe following screen shows a status report for the program COBDEMO.\n    CA InterTest for CICS  Activity Report, 11:39 a.m at terminal L905           \n     CICS Trace for InterTest internals is on.                                \n     No currently monitored tasks found.                                      \n   Automatic BreakPoint feature is globally active.                         \n   Automatic BreakPoint default terminal is not declared.                   \n 1103", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ff75824e3edf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n   CKPT  intrval=00:10 hh:mm                                               \n   CKPT  done at 11:37  a.m.\n   COBDEMO    Symbolic file is PROTDEM                                       \n               UBP   offset=  +01B44 id=56A7D208 at=#898                    \n                     from=L903 to=L903                                        \n               UBP   offset=  +016C2 id=B903CE24 at=#1                       \n                    from=L903 to=L903                                          \n               SLB   terminal is L903  Source Listing Breakpoints are off.   \n                     Listing view profile: Default.                           \n                    Singlestep no less than 002 statements.                  \n             * Entry not active                                               \n              * End of Report *                                           \n                                                                         \n---------------------------------------------------------------------------------\nPF1:Top   PF7:Up   PF8 or Enter:Down   PF3 or Clear:End   PF4:Refresh. Page 001\nThis report provides the following information:\n\u2022Automatic Breakpoint feature ...\nThe global ABP (Automatic Breakpoint) facility is active. This means monitored programs will receive breakpoint\ndisplays when an error triggers an automatic breakpoint.\n\u2022Automatic Breakpoint default ...\n\u2022There is no global ABP terminal.\n\u2022CKPT interval\nThe checkpoint recording facility is in effect. The interval between checkpoints is 30 minutes.\n\u2022CKPT done\nThe last checkpoint occurred at 9:45 a.m.\n\u2022COBDEMO\nThe next line identifies the program for which the status report was generated as COBDEMO.\n\u2022lines following COBDEMO\nThe rest of the report indicates the options currently active for COBDEMO. In this example, only Unconditional\nBreakpoints (UBP) are active for this program. For each breakpoint, the report provides the information shown in the\nfollowing table.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ff75824e3edf-1", "text": "following table.\n\u2013offset=\nThe breakpoint location is defined as a hexadecimal offset from the beginning of the program.\n\u2013id=hhhhhhhh\nThe breakpoint ID number assigned by InterTest for CICS.\n\u2013at=location\nThe symbolic location specified when the breakpoint was set. A number preceded by a # sign refers to a statement\nnumber, except for #1, which refers to the first executable instruction.\n\u2013from= termid\nThe ID of the terminal where the program must be executing for the breakpoint to take effect.\n\u2013to=termid\nThe ID of the terminal that will receive the breakpoint display.\nNote:  If you do not see the message, End of Report, the report is too long to fit on one screen. Press Enter to display\nmore of the report.\n\u2022*Entry not active*\nIndicates that InterTest for CICS is not currently monitoring the program.\nUtility Functions\nUse the utility functions to produce InterTest for CICS reports and to reset monitoring for a recompiled program.\n 1104", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8908a7079e5d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo select utility functions, specify Function 31 on the Function Selection Menu, and press Enter . The Utility Options\nscreen opens.\nSpecify the following functions on this screen. The equivalent function used in single-line commands is specified in\nparentheses.\nList InterTest tables (LIST)\nRequests a list of all the programs, transactions, and terminals that InterTest for CICS was instructed to monitor\nor not to monitor. The report also lists the programs InterTest for CICS will monitor as a result of the FOL special\noption.\nList programs in symbolic file (SYM)\nRequests a list of all the programs in the InterTest for CICS symbolic file. For each program, this report lists its\ndate and time of compilation, the number of records it occupies in the file, whether it can be purged, and whether\nit was compiled with the LISTER option.\nGlobal monitoring report (INQ)\nRequests a report of all InterTest for CICS monitoring activity.\nList one program in symbolic file (SYM)\nRequests information for one program in the InterTest for CICS symbolic file. It lists the date and time of\ncompilation, the number of records it occupies in the file, whether it can be purged, and whether it was compiled\nwith the LISTER option.\nNew program copy (NEW)\nResets symbolically specified breakpoints and other monitoring options for a recompiled program. Also resets the\nentry in the PPT Table to the program's new library address.\nNOTE\nThe reports produced by the options LIST, SYM, and INQ might be too long to fit on one screen. Press Enter to\ndisplay more of the report. To write a report to a transient data queue, enter the name of the TD queue.\nSet SystemWide Options", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8908a7079e5d-1", "text": "Set SystemWide Options\nSet certain options on a system-wide basis. Specify Function 32 on the Function Selection Menu, and press Enter. The\nSystem-Wide Options screen opens.\nSpecify the following options on this screen. Specify in parentheses the equivalent option used in single-line commands.\nEnter ON to set an option and OFF to remove it.\nAutomatic breakpoint (ABP)\nSets the automatic breakpoint facility for the entire system; the default. Breakpoint displays are routed to the\nterminal where the program is running. Specify a terminal ID to indicate where breakpoint displays should be\nrouted for non-terminal attached tasks and for tasks executing from non-3270 terminals.\nIf you specify OFF for the ABP option, you might want to use the Special Options screen (Function 22) to set the\nlocal automatic breakpoint option for one or more programs. The local automatic breakpoint option overrides the\nsystem automatic breakpoint option.\nGlobal logging (GLOG)\nRequests global logging of InterTest for CICS activity: most CNTL commands and all changes to main storage.\nSystem-wide monitoring (ALL)\nInstructs InterTest for CICS to monitor all application programs in the system, except those with the prefix DFH\n(IBM CICS programs) or IN25 ( InterTest for CICS programs).\nNOTE\nSpecify only one of the following two options at one time. To set both facilities, return to the Function\nSelection Menu and specify Function 32 again.\n 1105", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "49b361803170-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPurge breakpointed tasks (PURGE)\nInstructs InterTest for CICS to periodically purge tasks halted at a breakpoint for longer than the specified interval.\nThe first purge occurs when the option is specified. Subsequent purges occur at the end of the interval, specified\nin hours and minutes in this format hhmm. The minimum time interval is 20 minutes.\nCheckpoint InterTest (CKPT)\nInstructs the checkpoint recording facility to record periodically the status of InterTest for CICS monitoring so that\nyou can use the restart feature. The first checkpoint occurs when the option is specified. Subsequent checkpoints\noccur at the end of the interval, specified in hours and minutes in this format hhmm. The minimum time interval is\n10 minutes.\nNOTE\nThese options are password protected unless your site has removed this restriction.\nResume Task Execution\nWhen a task is halted at a breakpoint, request that execution of the task resume. Specify Function 33 on the Function\nSelection Menu and press Enter . For more information, see The Function Selection Menu.\nThe Monitoring Command Builder - Resume Task Execution screen displays. For detailed help on any of the fields on this\npanel, position your cursor in the field and press F1.\nExample\nThe following screen shows how to specify task resumption.\nThis screen specifies that the task:\n\u2022Resume at a new location: TASK-NUMBER-FOR-MSG.\n\u2022Execute three COBOL verbs before halting again.\nCA InterTest MONITORING COMMAND BUILDER  RESUME TASK EXECUTION     33\n                                                                               \n Press ENTER without options to resume execution of the breakpointed task  _____ \n        OR    enter one or more of the following options:                      \n To RESUME EXECUTION at a different location, enter ONE new location:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "49b361803170-1", "text": "To RESUME EXECUTION at a different location, enter ONE new location:          \n      COBOL paragraph, Assembler or PL/1 label:  tasknumberformsg____________ \n      COBOL or PL/1 statement number: _____      Offset: _____                 \n                                                                               \n To MOVE this breakpoint enter ONE new location,  OR  enter X to DISABLE it:   \n      COBOL paragraph, Assembler or PL/1 label:  _______________________________\n      COBOL or PL/1 statement number: _____      Offset: _____                 \n To AUTO STEP, enter #n for COBOL verbs or PL/1 STMTS or n for instrucs:   #3___\n with a n second WAIT between breakpoints:____\n to HALT at a CALL, enter XOR after n steps are reached:____ \n                                                                               \n To take a DUMP before continuing, enter a 1 to 4 digit dump code:          ____\n To ABEND transaction, enter dump code or XXXX if no dump is desired:       ____ \nCNTL Monitoring Commands and Options\nEnter single-line commands instead of using menus and screens. Entering commands directly is often faster and more\nefficient for experienced users. The InterTest for CICS CNTL transaction performs all monitoring functions. This topic\nteaches you which CNTL single-line commands you use to specify monitoring, monitoring options, and system-wide\n 1106", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5268fe0215db-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\noptions. For example, to set monitoring for the program COBDEMO when executed by the user ID BARNEY1, and also\nset a breakpoint at the beginning of the program, enter the following single command from CICS:\nCNTL=ON,PROG=COBDEMO,USR=BARNEY1,UBP=#1\nCNTL Commands at a Glance\nThe following table indicates the functions you specify with commands and, where appropriate, the equivalent selections\non the Primary Option menu, Breakpoint menu, and CNTL Function Selection Menu.\nCNTL Command Description Menu Path CNTL Function\nSTART, END Initializes and terminates\nInterTest for CICS.Not available Not available.\nRESTART Restarts InterTest for CICS. Not available Not available.\nON, OFF Sets and removes monitoring. Primary\n2.1, 2.2, 2.310\nON, OFF Sets and removes monitoring\noptions.Primary\n2.1, 2.2, 2.311 to 23\nOFFALL Removes ALL monitoring\noptions for ALL programs/\ntransactions/terminals set by a\nUserid or TerminalNot available Not available\nEXCL, INCL Excludes programs from\nmonitoring and ends program\nexclusion; applies to all CICS\nuser IDs.Not available Not available.\nGO Resumes task execution. Breakpoint 4 33\nGO Abends a task. Breakpoint 3 33\nINQ, LIST Produces InterTest for CICS\nreports.Type STATUS 30 and 31\nNEW Loads a new copy of a program. Primary\n2.1, 2.2, 2.331\nABP, GLOG, CKPT,PURGE Sets system-wide options. Primary 2.6 32\nEXEC Executes a module of CNTL\ncommands.Not available Not available.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5268fe0215db-1", "text": "EXEC Executes a module of CNTL\ncommands.Not available Not available.\nMLOG Records a monitoring session\nso that it can be repeated.Primary 2.7 Not available\nNOTE\nFor more information about specifying CNTL Monitoring Options, see CNTL Monitoring Options.\nCNTL Command propagation in a CICSPlex Environment\nFor CICSPlex environments using the InterTest for CICS CICSPLEX=YES installation option, all CNTL functions that are\ncheckpointed are propagated to all CICSPlex family members on startup (CNTL=START) or restart (CNTL=RESTART).\nThe following table summarizes which CNTL commands are propagated and which are not.\nCommands Propagated to All Family\nMembersCommands Not Propagated Comments\nCNTL=ABP\n 1107", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b281e80e13ee-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCNTL=ADD\nCNTL=CKPT\nCNTL=DUMP\nCNTL=END, {SCOPE=GLOBAL} Propagated if SCOPE=GLOBAL is\nspecified.\nCNTL=EXCL\nCNTL=FOL\nCNTL=GLOG\nCNTL=INCL\nCNTL=ITTRACE\nCNTL=NEW\nCNTL=OFF\nCNTL=ON\nCNTL=OFF,ALL\nCNTL=EXEC Commands in the module are propagated if\nthey are eligible for propagation.\nCNTL=GO\nCNTL=INQ\nCNTL=LIST\nCNTL=MENU\nCNTL=MLOG\nCNTL=PURGE\nCNTL=VRPT\nCNTL Command Syntax\nCNTL command syntax uses the following notational conventions:\n\u2022Uppercase words (such as CNTL) are InterTest for CICS keywords that must be entered exactly as shown\n\u2022Lowercase words (such as promid) represent user-supplied information and should be replaced with the appropriate\nentries.\n\u2022Information in brackets is optional and can be omitted\nThe following list contains the terms used in command syntax for which you must substitute the appropriate information.\npromid\nIdentifies one or more programs, transactions, or terminals. Use one of the following formats:\nPROG=program\n PROG=(prog1,...,prog9)\n TRAN=trancode\n TRAN=(tran1,...,tran9)\n TERM=terminal\n TERM=(term1,...,term9)\n PROG=.ALL                to specify the entire system\nNOTE\nAn * replaces promid for the monitoring table entry currently at a breakpoint at your terminal.\n 1108", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0dbd6e4db5ee-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nprogname\nIdentifies a program.\nlocn\nIdentifies a program location. Specify a location in one of the following ways:\n\u2022One- to five-digit hexadecimal displacement (offset) from the beginning of the program\n\u2022Six- or eight-digit hexadecimal address\n\u2022A COBOL paragraph name enclosed in single quotes\n\u2022A COBOL or PL/I statement number preceded by a # sign\n\u2022A PL/I or Assembler label enclosed in single quotes\noptions\nIndicates one or more CNTL monitoring options. Separate multiple options with commas.\nEnter CNTL commands directly on a clear screen or on the command line of a source listing, breakpoint, or CORE\ndisplay.\nGeneric Specification of promid\nSpecify asterisks, *, and plus signs, +, to replace characters in promid  in the following CNTL commands:\nCNTL=ON,... \nCNTL=OFF,... \nCNTL=EXCL,... \nCNTL=INCL,... \nCNTL=INQ,...\nNOTE\nAn asterisk, *, specifies any number of characters, including no characters.\nThese specifications are interpreted according to the rules for the CICS CEMT transaction.\nExamples\nTo specify all programs that start with ABC, including program name ABC, enter:\nPROG=ABC*\nTo specify all programs that end with ABC, including program name ABC, enter:\nPROG=*ABC\nTo specify all programs that start with AB and end with C and all those that could have an unspecified number of\ncharacters in the middle, enter:\nPROG=AB*C\nNOTE\nSpecifies more than one asterisk in a promid. Do not specify an asterisk by itself: PROG=* because it is invalid.\nTo specify all four-character program names that begin with ABC followed by any one character, enter:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0dbd6e4db5ee-1", "text": "To specify all four-character program names that begin with ABC followed by any one character, enter:\nPROG=ABC+\nNOTE\nA plus sign, +, specifies only one character in a particular position.\nTo specify all four-character program names that begin with any character followed by ABC, enter:\nPROG=+ABC\n 1109", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b00aea8e01b6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo specify all four-character program names that begin with AB followed by any one character and C, enter:\nPROG=AB+C\nNOTE\nSpecify more than one plus sign in a promid. Do not specify a plus sign by itself: PROG=+ because it is invalid.\nTo specify all programs that begin with AB followed by one character, C, and an unspecified number of characters, enter:\nPROG=AB+C*\nNOTE\nCombine asterisks and plus signs.\nHierarchy Rules for Monitored Entries\nIt is important to know the priorities InterTest for CICS observes if more than one entry in the monitoring table applies to\nthe same program.\n\u2022The PROG=.OPTIONS specification overrides all other specifications\n\u2022A program entry (specific or generic) overrides a transaction entry, a terminal entry, and an .ALL specification\n\u2022A transaction entry (specific or generic) overrides a terminal entry and an .ALL specification\n\u2022A terminal entry (specific or generic) overrides an .ALL specification\n\u2022A specific user ID overrides an .ANY specification\nExample\nSuppose you specify monitoring options for program ABC1 and different options for transaction TRN1. ABC1 executes as\npart of that transaction. When ABC1 executes, the options specified for ABC1 override the options specified for TRN1.\nSimilarly, it is important to understand the priorities InterTest for CICS observes when a program, transaction, or terminal\nis specifically and generically declared for monitoring. In this case, a specific entry overrides a generic entry except when\nyou issue the command CNTL=INQ,promid, where the generic specification takes precedence.\nExample\nSuppose you specify monitoring options for program ABC1 and different monitoring options for program ABC*. The\noptions specified for ABC* affect all programs whose names begin with ABC except for program ABC1 (and any other", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b00aea8e01b6-1", "text": "programs beginning with ABC that have their own entries in the monitoring table). Monitoring for ABC1 is controlled by the\nspecific entry for that program. However, if you specify CNTL=INQ,PROG=ABC*, you get monitoring status reports for all\nprograms that begin with ABC, including programs such as ABC1, which have separate monitoring table entries.\nInitialize and Terminate InterTest for CICS\nTo initialize InterTest for CICS, enter:\nCNTL=START\nTo terminate InterTest for CICS, enter:\nCNTL=END\nWARNING\nThis command terminates InterTest for CICS for all users and could be password protected.\nRestart InterTest for CICS\nUse the CNTL=RESTART command to restart InterTest for CICS. The command has the following syntax:\nCNTL=RESTART,TODAY=ONLY,NOWAIT\n 1110", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "10cf0cca24cf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe command has the following parameters:\nTODAY=ONLY\n(Optional) Specifies that InterTest for CICS only restarts if the checkpoint occurred on the same day\nNOWAIT\n(Optional) Suppresses displays of messages and makes the restart much faster\nWhen InterTest for CICS is restarted from a sequential terminal, it ignores all input records following the RESTART\ncommand until it finds a record with this command:\nCNTL=DUMMY\nThis terminates the CNTL transaction and permits the system to execute transactions from subsequent input records.\nHowever, if the restart is unsuccessful, the CNTL transaction terminates and all input records that follow the RESTART\ncommand are executed as usual by CICS.\nSet and Remove Monitoring\nTo set monitoring, enter:\nCNTL=ON,promid\nTo set monitoring for all programs and all users, enter:\nCNTL=ON,PROG=.ALL,USR=.ANY\nTo set monitoring for all programs executed by the user whose CICS user ID is BARNEY1, enter:\nCNTL=ON,PROG=.ALL,USR=BARNEY1\nTo remove monitoring, enter:\nCNTL=OFF,promid\nExamples\nTo turn on monitoring for program COBDEMO enter:\nCNTL=ON,PROG=cobdemo\nTo turn off monitoring for programs COBDEMO and PAYPROG, enter:\nCNTL=OFF,PROG=(cobdemo,payprog)\nAutomatic Creation of Monitoring Table Entries\nIf you set monitoring for a transaction or terminal and a program executing as part of that transaction or at that terminal\nis stopped at an automatic breakpoint, InterTest automatically creates an entry in the monitoring table for that program.\nThis enables you to set breakpoints and monitoring options for that individual program. Similarly, if you specified", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "10cf0cca24cf-1", "text": "This enables you to set breakpoints and monitoring options for that individual program. Similarly, if you specified\nCNTL=ON,PROG=.ALL or you specified a generic program name, InterTest for CICS creates an individual monitoring\ntable entry for any program monitored under that entry that InterTest for CICS stops at an automatic breakpoint.\nSet and Remove Monitoring Options\nTo set monitoring options, enter:\nCNTL=ON,promid,options  or   CNTL=ON*,options\nTo set system-wide default monitoring options, enter:\n 1111", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "10b3d3abbb5f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCNTL=ON,PROG=.OPTIONS,USR=.ANY,options\nOptions specified on a system-wide basis take effect for all programs InterTest for CICS monitors.\nNOTE\nSpecify only the following options on a system-wide basis: ABI, CSA, FOL, ICT, LET, MXR, MXS, NUP, PRO,\nRFC, RNT, RPC, RTD, RTS, SLB, STR, and TRC.\nTo remove monitoring options, enter:\nCNTL=OFF,promid,options OR CNTL=OFF*,options\nExamples\nTo set the Follow option for the task currently at a breakpoint at your terminal, enter:\nCNTL=ON*,FOL=ON\nTo set the No Update option for all monitored tasks, enter:\nCNTL=ON,PROG=.OPTIONS,NUP=ON\nTo remove the unconditional breakpoint at statement number 1 for program COBDEMO, enter:\nCNTL=OFF,PROG=cobdemo,UBP=#1\nSet and Remove ALL Monitoring Options Set by a User ID or Terminal\nTo remove ALL monitoring options set by a specific User ID or for a specific Terminal, enter:\nCNTL=OFF,ALL,USR=userid or CNTL=OFF,ALL,TTR=termid,FTR=termid\nTTR= and FTR= must specify the same terminal ID.\nUse this command with caution because it removes monitoring options for more than one program or transaction.\nThis command is also passed to the CNTL transaction as data on a CICS START command and could be used by an\ninstallation's AutoInstall exit when a terminal signs off to automatically remove all InterTest for CICS breakpoints set by the\nterminal or user ID.\nExclude Programs from Monitoring\nTo exclude a program from monitoring, enter:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "10b3d3abbb5f-1", "text": "terminal or user ID.\nExclude Programs from Monitoring\nTo exclude a program from monitoring, enter:\nCNTL=EXCL,promid\nTo remove the monitoring exclusion set by the CNTL=EXCL command, enter:\nCNTL=INCL,promid\nNOTE\nINCL and EXCL are not sensitive to the monitoring user ID.\nExamples\nTo exclude all of transaction PYRLs programs from monitoring, enter:\nCNTL=EXCL,TRAN=PYRL\nTo remove program PAYROLL1 from the exclusion list so it is again eligible for\nmonitoring, enter:\n 1112", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3a74fc71d2de-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCNTL=INCL,PROG=payroll1\nResume Task Execution\nTo resume task execution at a breakpoint, enter:\nCNTL=GO,TASK=taskid,C[,options]\ntaskid\nRepresents the number of the task at a breakpoint. Use the CNTL=INQ command to determine the taskid .\nC instructs InterTest for CICS to continue execution.\nTo resume execution of the task currently at a breakpoint at your terminal, enter:\nCNTL*C[,options]\nTo resume task execution after taking a transaction dump, enter:\nCNTL=GO,TASK=taskid,Ddddd[,options]\nDdddd, dddd\nSpecifies a four-character transaction dump code.\nSpecify the following options with the CNTL commands for resuming execution:\nAT=locn \nor\nAT=X\nGO=locn\nNOBREAK\nS=#nnn[,I=nn][,N=CALL/xxxx]orS=nnn[,I=nn][,N=CALL/xxxx]\nAT=locn moves the current breakpoint to a different location.\nAT=X disables the breakpoint.\nGO=locn specifies the location at which the task should resume execution. For more information, see GO=Element\nLimitation.\nNOBREAK resumes execution from the current statement ignoring all preset breakpoints and indirect commands until the\ntask either abends or runs to normal completion. Use the NOBREAK option on:\nCNTL*C\nor\nCNTL=GO, TASK=xxxxx, C\nS=#nnn[,I=nn][,N=CALL/xxxx]   instructs InterTest for CICS to halt program execution after  nnn COBOL verbs or PL/I\nstatements are executed.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3a74fc71d2de-1", "text": "statements are executed.\n\u2022S=nnn[,I=nn][,N=CALL/ xxxx] instructs InterTest for CICS to halt program execution after nnn machine instructions are\nexecuted.\n\u2022I=nn instructs InterTest for CICS to repeat the single-stepping after pausing for nn seconds\n\u2022N=CALL halts automatic single-stepping at a CALL or CICS commands\n\u2022N=xxxx halts automatic single-stepping after a specified number (1-9999) of steps\nNOTE\nS=1 is specified as S.\n 1113", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5f8162f63115-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nExamples\nTo specify that task 12345 resume at COBOL paragraph name TASK-NUMBER-FOR-MSG, enter:\nCNTL=GO,TASK=12345,C,GO=`task-number-for-msg'\nTo specify that the task currently at a breakpoint at your terminal resume at statement number 142 and that the program\nexecute five COBOL verbs or PL/I statements before being halted, enter:\nCNTL*C,GO=#142,S=#5\nTo specify that task 12345 resume execution after taking a dump and that the current breakpoint be disabled, enter:\nCNTL=GO,TASK=12345,Dhelp,AT=X\nThe transaction dump code is HELP.\nTo specify that task 777 resume execution at indirect command sequence number 10, enter:\nCNTL=GO,TASK=777,C,EXEC=0010\nGO= Element Limitation\nWhen changing the execution sequence of a high level program, especially COBOL or PL/I, you must take responsibility\nfor securing proper addressability of the data that will be processed in the piece of logic specified by GO= element.\nIn COBOL, before you force a branch (GO TO) to the routine using GO= element, the BLLs and their corresponding\nregisters must contain correct addresses. Accomplish this with CORE commands, especially the =SET element of the\nCORE command. Use symbolic names of BLL cells. The BLL cells are related to their data structures in the Data Division\nMap (DMAP) of the COBOL listing, while the related registers are found in the register assignment section of the memory\nmap.\nSERVICE RELOAD statements in the COBOL program are necessary to notify the COBOL compiler that, at a specific\ntime, the registers must be reloaded when the address of the base of a certain data structure changes. If you force", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5f8162f63115-1", "text": "a branch (GO TO) to the intended routine using the GO= element and, in the process, you cross the boundaries of\nSERVICE RELOAD, then it is necessary to set the addresses.\nIn PL/I, you not only must secure the proper addressability of data, but also remain within the same logical level (such as\nthe same DO block or called procedure). Going to another logical level requires going through all intermediate epilogues\nand prologues.\nAbend a Task Stopped at a Breakpoint\nTo abend a task with or without  a transaction dump, enter:\nCNTL=GO,TASK=taskid,Adddd[,options]\ntaskid\nRepresents the number of the task at a breakpoint. Use the CNTL=INQ command to determine the taskid.\nAdddd dddd\nSpecifies a four-character transaction dump code. Replace  dddd  with XXXX to abend the task without  a dump\nand disable exits.\nNOTE\nA dump code of XXXX is not allowed for tasks in a MRO session. Specify A by itself to abend the task without  a\ndump and enable the exits.\nSpecify the following options:\nAT=locn  or  AT=X\n 1114", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "40af54b5fbfe-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAT=locn moves the breakpoint to a different location\nAT=X disables the breakpoint\nExamples\nTo abend task number 54321 with a dump and a transaction dump code of DMP1, enter:\nCNTL=GO,TASK=54321,Admp1\nTo abend task number 54321 without a dump, enter:\nCNTL=GO,TASK=54321,AXXXX\nTo abend the current task with a dump and move the current breakpoint to statement number 128, enter:\nCNTL*Admp1,AT=#128\nTo abend the current task without a dump, enter:\nCNTL*AXXXX\nHow to Produce InterTest for CICS Reports\nTo produce a monitoring status report, enter:\nCNTL=INQ,promid[,TODEST=destid]\nTo produce a monitoring status report for the task currently at a breakpoint at your terminal, enter:\nCNTL?\nTo produce a system-wide monitoring report, enter:\nCNTL=INQ[,TODEST=destid]\nTo display the contents of InterTest for CICS monitor tables, enter:\nCNTL=LIST[,TODEST=destid]\nTo display the entire contents of the InterTest for CICS symbolic file, enter:\nCNTL=INQ,SYM=ALL[,TODEST=destid]\nTo display information for one program in the InterTest for CICS symbolic file, enter:\nCNTL=INQ,SYM=progname[,TODEST=destid]\ndestid\nRepresents the transient data destination. If omitted, the report displays on your terminal screen.\nExamples\nTo request a monitoring status report that displays on your terminal screen for program COBDEMO, enter:\nCNTL=INQ,PROG=cobdemo", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "40af54b5fbfe-1", "text": "CNTL=INQ,PROG=cobdemo\nTo request a monitoring status report for all programs that is routed to the CSSL transient data queue, enter:\nCNTL=INQ,TODEST=CSSL \nTo request a report listing information on all programs in the symbolic file that is routed to the CSSL transient data queue,\nenter:\n 1115", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "300a32d2651c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCNTL=INQ,SYM=ALL,TODEST=CSSL \nLoad a New Copy of a Program\nTo load a new copy of a program, reset symbolic breakpoints, and reset the entry in the PPT to the program's new library\naddress, enter:\nCNTL=NEW,PROG=progname\nNOTE\nThe specified program is declared for monitoring before any breakpoints are reset. Monitoring and breakpoints\nare reset for all user IDs. If you have breakpoints set for Statement #  or Offset , then you should first deactivate\nmonitoring for the program, issue the NEW copy, then reset your breakpoints to insure they are in sync with the\nnew program version.\nExample\nTo load a new copy of program COBDEMO.\nCNTL=NEW,PROG=COBDEMO \nSpecify optionally a SYM=.NOASK parameter. Doing so causes InterTest Symbolic File Date Checking module to bypass\nASKing the terminal operator to select a symbolic file member when a date or time mismatch is detected for a COBOL\nor PL/I module being NEW copied or when an Assembler module being new copied has more that one member in the\nsymbolic files.\nNOTE\nThis parameter should be used with  caution as it forces InterTest for CICS to use the first symbolic file member it\nfinds for a program being NEW copied when breakpoints are reset after the new module is copied.\nLog a Monitoring Session\nWhen you monitor a program, you can log, or record, the monitoring session and save it to PROTMLOG. You can then\nuse this file to repeat your monitoring session later.\nAll monitoring session commands are applied to the user ID and terminal that issue the commands.\nNOTE\nIndirect commands are not saved in the MLOG when session logging is turned on.\n\u2022To start recording a new monitoring session, enter:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "300a32d2651c-1", "text": "\u2022To start recording a new monitoring session, enter:\nCNTL=MLOG,START, name[,description ]\n\u2013name\nSpecifies a session name.\nLimits:  1 to 8 characters\n\u2013description\n(Optional) Describes the session.\nLimits:  0 to 35 characters\nWhen you issue the START command, the active recording session is indicated by a flashing REC on the Source\nListing Display screen.\n\u2022To stop recording and save the current session, enter:\nCNTL=MLOG,STOP\nWhen you issue the STOP command, the flashing REC disappears from the Source Listing Display screen.\n\u2022To cancel the current session and delete all entries that were recorded since the START command was issued, enter:\nCNTL=MLOG,CANCEL\n 1116", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "03c2b278f7b7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWhen you issue the CANCEL command, the flashing REC disappears from the Source Listing Display screen.\n\u2022To delete the entries from an existing session, enter:\nCNTL=MLOG,DELETE, name \n\u2022\u2013name\nSpecifies the session.\nLimits:  1 to 8 characters\n\u2022To load an existing session, enter:\nCNTL=MLOG,LOAD, name \n\u2013name\nSpecifies the session.\nLimits:  1 to 8 characters\nNOTE\nYou can only load saved sessions. Active sessions cannot be loaded.\nSet System-Wide Options\nTo activate the automatic breakpoint facility for the entire system, enter:\nCNTL=ABP,ON,termid\nBreakpoint displays are routed to the terminal where the program is running. Specify a terminal ID to indicate where\nbreakpoint displays should be routed for non-terminal attached tasks and for tasks executing from non-3270 terminals.\nNOTE\nThe delivered default is to activate the global automatic breakpoint facility when InterTest for CICS is initialized.\nTo deactivate the global automatic breakpoint facility, enter:\nCNTL=ABP,OFF\nIf you deactivate the global automatic breakpoint facility, set the local Automatic Breakpoint option for one or more\nprograms, transactions, or terminals. The local Automatic Breakpoint option overrides the system automatic breakpoint\nfacility.\nTo log all CNTL commands (except INQ and LIST) and all changes made to main storage, enter:\nCNTL=GLOG,ON\nTo de-activate global logging of InterTest for CICS commands, enter:\nCNTL=GLOG,OFF\nTo activate checkpointing so that the status of the InterTest for CICS monitoring is periodically monitored so that you can\nuse the restart feature, enter:\nCNTL=CKPT,INTRVAL=hhmm", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "03c2b278f7b7-1", "text": "use the restart feature, enter:\nCNTL=CKPT,INTRVAL=hhmm\nThe first checkpoint occurs when the option is specified. Subsequent checkpoints occur at the end of the interval,\nspecified in hours and minutes. The time interval must be at least ten minutes,\nTo terminate checkpointing, enter:\nCNTL=CKPT,OFF\nTo periodically purge all tasks waiting at a breakpoint, enter:\nCNTL=PURGE,INTRVAL=hhmm\n 1117", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "66d612451949-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe first purge occurs when the option is specified. Subsequent purges occur at the end of the interval, specified in hours\nand minutes. The time interval must be at least 20 minutes\nTo purge all tasks waiting at a breakpoint at once, enter:\nCNTL=PURGE,ALL=ONCE\nTo deactivate the purge facility, enter:\nCNTL=PURGE,OFF\nExample\nTo activate checkpointing with the first checkpoint occurring immediately and subsequent checkpoints occurring at 50\nminute intervals, enter:\nCNTL=CKPT,INTRVAL=0050\nExecute a Module of CNTL Commands\nAssemble modules containing CNTL commands by using the InterTest for CICS PROMMAC macros.\nNOTE\nFor more information about CNTL commands, see Start InterTest for CICS.\nAfter the product is activated, enter the following command to execute the commands in the module:\nCNTL=EXEC,MODULE=modulename\nNOTE\nThe CNTL=LIST and CNTL=INQ commands cannot be specified in the module.\nConstruct as many of these modules as you want. Each should have its own entry in the PPT.\nCNTL Monitoring Options\nThe following table describes the CNTL monitoring options and indicates the function to select from the Function Selection\nMenu to specify the same option.\nOption Description CNTL Menu Function\nABI Intercepts all CICS abends. Not available\nABP Sets local automatic breakpoint. Function 22\nBYP Bypasses storage protection, permit SVC,\nBALR 14,14 and BALR 14,15 instructions.Function 21\nCBP Sets or removes conditional breakpoints. Function 12\nCCV Sets or removes code coverage Not available\nCMD Sets or removes indirect command\nstatements for a program/terminal.Function 24", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "66d612451949-1", "text": "CMD Sets or removes indirect command\nstatements for a program/terminal.Function 24\nCSA Unprotects area in CSA. Function 21\nCWA Unprotects area in CWA. Function 21\nDM Sets or removes data monitoring Function 16\nFEP Identifies instructions that read certain main\nstorage areas.Not available\nFOL Continues monitoring after branch to\nanother program.Function 22\n 1118", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e26e95ab5cce-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nICT Instruction counter for preventing AICA\nabends.Not available\nKEP Keeps data area in a source listing Keep\nwindow.Not available\nLET Allows modification of storage or load\nmodule.Function 21\nLNK Sets composite support. Function 23\nLMD Specified the load module name of a\ncomposite module.Not available\nMON* Sets or removes monitoring on locations for\nsegmented monitoring.Function 14\nMUS Limits number of times a program is\nmonitored.Function 22\nMXR Limits number of CICS requests. Function 22\nMXS Limits storage usage. Function 22\nNOM* Sets or removes monitor off locations for\nsegmented monitoring.Function 15\nNRB Prevents a read buffer before a breakpoint\ndisplay.Not available\nNUP Prevents program from updating files. Function 22\nOVR Overrides errors that trigger an automatic\nbreakpoint.Not available\nPRO Protects storage from being modified. Function 21\nRBP Sets or removes request breakpoints. Function 13\nRFC Replaces file name. Function 20\nRNT Prevents program from modifying code. Function 22\nRPC Replaces program name. Function 20\nRTD Replaces transient data queue name. Function 20\nRTS Replaces temporary storage ID. Function 20\nSDF Structure Display Format Setting Function 22\nSLB Activates Source Listing Breakpoint display.Function 22\nSTR Saves CICS trace table. Not available\nTAL Counts how often instruction is executed\nwithin loop.Not available\nTER Changes the terminal ID. Not available\nTFL Sets a non-interactive monitoring session Not available\nTON Limits monitoring to single terminal. Functions 20,21,22\nTRC Sets or removes statement tracing Function 11\nUBP Sets or removes unconditional breakpoints. Function 11\nUSH Removes storage protection from SHARED\nstorage subpool area.Not available", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e26e95ab5cce-1", "text": "USH Removes storage protection from SHARED\nstorage subpool area.Not available\nUSR Sets monitoring for the CICS user ID\nspecified.All monitoring and most monitoring options\n 1119", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ef35db13cc4d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCNTL Monitoring Option Syntax\nTo set CNTL options, enter:\nCNTL=ON,promid,options  or  CNTL=ON*,options\nTo remove CNTL options, enter:\nCNTL=OFF,promid,options  or  CNTL=OFF*,options\nNOTE\nTo remove an option, specify it exactly as it was originally defined.\nTo remove an option that was specified more than once for a program, enter:\nCNTL=OFF,promid,option=.ALL\nThe .ALL specification is valid for the following options: BYP, CBP, CSA, KEP, LET, MON, NOM, PRO, RFC, RPC, RTD,\nRTS, and UBP.\nExamples\nTo instruct InterTest for CICS to limit the number of CICS requests made by program COBDEMO to 40, enter:\nCNTL=ON,PROG=cobdemo,MXR=40 \nTo instruct InterTest for CICS to stop limiting the number of CICS requests made by program COBDEMO for user ID\nBARNEY1, enter:\nCNTL=OFF,PROG=cobdemo,MXR=40,USR=BARNEY1\nTo instruct InterTest for CICS to remove all RFC options specified for program COBDEMO, enter:\nCNTL=OFF,PROG=cobdemo,RFC=.ALL \nMultiple Specifications of the Same Option\nMultiple specifications of the same option are in effect for a program, transaction, or terminal.\nExample\nSpecify the UBP option at various times to set unconditional breakpoints within a program. Each specification remains in\neffect until it is removed.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ef35db13cc4d-1", "text": "effect until it is removed.\nSpecify the following options more than once: BYP, CBP, CSA, DM, KEP, LET, MON, NOM, PRO, RFC, RPC, RTD,\nRTS, SLB, TRC, and UBP. For other options, only one specification is in effect at one time for a program, transaction, or\nterminal. The last specification is the one that InterTest for CICS recognizes.\nFor the following options, only one specification is in effect at a time: ABI, ABP, FOL, ICT, MUS, MXR, MXS, NUP, RNT,\nSTR, TAL, and TON.\nABI Intercept All CICS Abends\nThe ABI option intercepts CICS abends and produces automatic breakpoints with an error code and message explaining\nthe reason for the abend. Then select to continue execution (after, possibly, removing the error) or abend the task with the\nsame or different abend code. All abend codes are intercepted, except those generated into the IN25ABEN table by you.\nThe ABI option has three values: ON, OFF, and FORCE.\nABI=ON\n(Default)\n 1120", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9def34c332ad-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIntercepts all CICS abends and produces automatic breakpoints for programs or tasks that do not  have an active\nCICS HANDLE ABEND.\nABI=FORCE\nIntercepts CICS abends for programs or tasks that have an active CICS HANDLE ABEND command.\nABI=OFF\nCauses InterTest for CICS to STOP intercepting CICS ABENDS for the specified program.\nExamples\nCNTL=ON,PROG=ABC,ABI=ON\nCNTL=ON,PROG=ABC,ABI=OFF\nCNTL-ON,PROG=ABC,ABI=FORCE\nABP Local Automatic Breakpoint Option\nThe local  ABP option activates automatic breakpoints for a specified program, transaction, or terminal.\nTo set the local automatic breakpoint option, enter:\nABP=termid or ABP=*\ntermid\nSpecifies the ID of the terminal to which automatic breakpoint displays should be routed.\n*\nSpecifies that the current terminal should receive automatic breakpoint displays.\nThis option overrides the global  automatic breakpoint facility and is useful in a system where the global automatic\nbreakpoint facility is disabled.\nThe local ABP option is also useful when you do not want the breakpoint display routed to the terminal where the program\nis running, or when the display cannot be routed to that terminal (for example, a non-terminal task or a task running on a\nnon-3270 terminal). In these cases, specify the termid  of the terminal to which breakpoint displays should be routed.\nRemove the ABP option to deactivate automatic breakpoints for a specified program, transaction, or terminal. If a\nmonitoring violation occurs, InterTest for CICS abends the task instead of halting it at an automatic breakpoint.\nBYP Bypass Storage Protection", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9def34c332ad-1", "text": "BYP Bypass Storage Protection\nTo bypass storage protection and allow SVC and BALR, BASSM, BASR 14,15 and 14,14 instructions, enter:\nBYP=(offset1,offset2)\nor\nBYP=(addr1,addr2)\nSpecify the beginning and ending program locations either as offsets or addresses.\noffset\nSpecifies a one to five digit hexadecimal displacement from the beginning of the program.\naddr\nSpecifies a six- to eight-digit hexadecimal address.\nThis BYP specification defines a section of program code that is allowed to:\n\u2022Modify any area of storage\n\u2022Issue SVC instructions\n\u2022Issue BALR, BASSM, and BASR 14,15 and 14,14 instructions\n 1121", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e52843ade2a5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWARNING\nWARNING! Use this option with great care! Specify BYP only for a small section of code, such as a CALL\nstatement (that is, a BALR, BASSM, or BASR 14,15 or 14,14 instruction). In that case, monitoring is suspended\nuntil control returns to the instruction after the CALL statement. If control does not return, monitoring remains off\nfor the duration of the program's execution.\nThis BYP specification suspends monitoring when a BALR, BASSM, or BASR 14,15 or 14,14 instruction passes control\nto the specified location. It is useful when a monitored program calls a non-standard interface from several different\nlocations. Use the following specification to bypass storage protection when a BALR, BASSM, or BASR 14,15 or 14,14\ninstruction passes control:\nBYP=(.ANY,locn)\nlocn\nSpecifies a one- to five-digit hexadecimal displacement or a six- to eightdigit hexadecimal address.\nUse the following specification to bypass a current instruction at a breakpoint:\nBYP=*\nThis BYP specification instructs InterTest for CICS to allow the current instruction to modify storage or issue an SVC,\nBALR, BASSM, or BASR 14,15 or 14,14 instruction.\nNOTE\nSpecify this option with great care. It could be password protected.\nCBP Specify Conditional Breakpoints\nTo specify a conditional breakpoint, enter:\nCBP=locn,IF=condition\nA conditional breakpoint halts a program at a specified location only if a specified condition is met. For more information\nabout specifying the location and the condition, see Conditional Breakpoints.\nCCV Code Coverage\nThis option turns on code coverage for programs, transactions or terminals monitored in a non-interactive session. This", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e52843ade2a5-1", "text": "option can only be used together with the TFL option.\nTo turn on coverage, enter\nTFL=token,CCV=on\nExample\nTo turn on non-interactive monitoring and get a code coverage data for the program COBDEMO, enter\nCNTL=ON,PROG=COBDEMO,TFL=ABCDE,CCV=ON\nAfter the transaction is executed, the monitoring session for the specific program is terminated and an audit log\n(ABCDE.rpt) and code coverage data (ABCDE.ccv) are generated. The output files are in JSON format.\nFor more information about the token that is used for the TFL option, see TFL Set Non-Interactive Monitoring.\nCMD Set Indirect Command Statements\nTo set an indirect command statement for a particular program or terminal, enter:\nCMD=((number),F=termid),TEXT='command text'\n 1122", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "491519726670-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nnumber\nSpecifies the indirect command statement line number that will be assigned to the accompanying command text.\nF=termid\nSpecifies the terminal where the program for which the indirect commands are being set will execute from. This\nprovides multiple users with the potential for defining independent sets of indirect commands for each of their\ndebugging sessions. In addition, a single set of commands is shared by all users if F=.ANY is specified.\nNOTE\nIndirect commands defined under a specific or .NO terminal take precedence over any existing F=.ANY\ncommand set.\nTEXT\nSpecifies the actual indirect command text, which must be enclosed within single or double quotation marks. For\nmore information and command syntax, see Indirect Commands.\nCSA Unprotect an Area in the CSA\nTo unprotect an area in the CSA, enter:\nCSA=(offset,length)\noffset\nSpecifies a hexadecimal displacement from the beginning of the CSA.\nlength\nSpecifies the number of hexadecimal bytes in the CSA to be unprotected.\nThis option lets a program, transaction, or terminal modify areas in the CSA.\nWARNING\nSpecify this option with great care. It could be password protected.\nCWA Unprotect an Area in the CWA\nThis option lets a program, transaction, or terminal modify areas in the CWA.\nTo unprotect an area in the CWA, enter:\nCWA=(offset,length)\noffset\nSpecifies a hexadecimal displacement from the beginning of the CWA.\nlength\nSpecifies the number of hexadecimal bytes in the CWA to be unprotected.\nDM Data Monitoring Option\nThis option instructs InterTest for CICS to capture data values for every COBOL statement executed in the program or\ntransaction, or at a terminal. When data monitoring is set to ON, the statement tracing option (TRC) is forced on for the\nprogram, transaction, or terminal.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "491519726670-1", "text": "program, transaction, or terminal.\nTo set data monitoring for a particular program, transaction, or terminal, enter:\nDM=ON\nNOTE\nA specific terminal ID or user ID is required to set the data monitoring option. If one is not specified, the default\nwill be used.\n 1123", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "271f0ef18be9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFEP Set the FEP Option\nThe FEP option lets you find program instructions that read from one or more main storage areas specified in the\noption. The first format of the FEP option identifies main storage areas that a program might read. The second format\n(FEP=EX,...) prevents the program from reading all main storage areas except  the ones specified in the option and areas\nowned by the program.\nTo set the FEP option, enter:\nFEP=(addr,len)\nFEP=(EX,addr,len)\naddr\nIndicates six to eight digit hexadecimal address of the first byte of a main storage area.\nlen\nIndicates length of the area in hexadecimal.\nEX\nPrevents the program from reading all main storage areas except those specified in the option or owned by the\nprogram.\nFOL Continue Monitoring After a Branch to Another Program\nThis option instructs InterTest for CICS to monitor a program even after it branches directly to another program (wild\nbranch). All monitoring options remain in effect.\nSpecify breakpoints in the load module to which control is passed, but their locations might have to be specified as\nhexadecimal addresses.\nNOTE\nDo not specify this option if control is passed using a LINK or XCTL instruction.\n\u2022Use FOL=ON when control passes to a program that does not have a PPT entry.\n\u2022Use FOL=name when control passes to a program that has a PPT entry.\n\u2022Use FOL=NOPPT instead of ON to reduce overhead.\nTo continue monitoring after a branch, enter:\nFOL=ON \nor\nFOL=name \nor\nFOL=NOPPT\nICT Instruction Counter for Preventing AICA Abends\nThis command instructs InterTest for CICS to issue an EXEC CICS WAIT command each time the specified program", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "271f0ef18be9-1", "text": "executes nnnnn  instructions. Use this option to prevent incorrect AICA abends in high CPU-utilization programs where\noverhead was increased by the InterTest monitoring activity.\nTo set the instruction counter to prevent an AICA abend, enter:\nICT=nnnnn\nnnnnn\nSpecifies the number of instructions. Replace nnnnn  with a decimal number between 1 and 65,534.\n 1124", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "92d59e9cbb25-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nKEP Keep Data Areas in a Keep Window\nThe KEP= option lets you specify one storage area to be kept in a Keep window whenever the specified program displays\nor executes from the source listing facility. The Keep window is not available on a Detailed Breakpoint display.\nDisplay up to six items in a Keep window at a time. If you keep more than six items, InterTest for CICS initially displays\nthe first six items that you selected but allows scrolling to other items using the PF19 and PF20 keys. When an item is\nremoved from the window, another item is displayed. The KEP= option syntax allows only one request at a time. For each\nitem kept, InterTest for CICS displays a single line identifying the keep request, followed by the first 12 bytes of storage in\nboth hexadecimal and character format.\nTo keep data in a Keep window, enter:\nKEP=(request) \nKEP=((request),T=termid)\nrequest\nSpecifies one data area in CICS main storage to be displayed in a Keep window. Use CORE syntax to specify the\nrequested data area, but omit CORE=.\ntermid\nSpecifies the terminal that displays the requested area in a Keep window.\nT=.ANY\nSpecifies the data area that will display in a Keep window on any terminal that displays or executes the program\nusing LIST.\nLET Allow a Program to Modify Storage or a Load Module\nTo allow a program to modify storage, enter:\nLET=(address,length)\naddress\nSpecifies the starting address of the area of storage that is modified as six to eight hexadecimal digits.\nlength\nSpecifies, in hexadecimal, the number of bytes that are modified.\nThe storage area must lie entirely within the CICS Dynamic Storage Area.\nTo allow a program to modify a load module, enter:\nLET=progname\nprogname", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "92d59e9cbb25-1", "text": "To allow a program to modify a load module, enter:\nLET=progname\nprogname\nSpecifies the load module that is modified.\nNOTE\nSpecify this option with great care. It could be password protected.\nLNK Set Composite Support\nUse LNK options to set composite support for a composite module . A composite module consists of separately compiled\nor assembled parts brought together when the module is link-edited.\nThe part of the composite module that receives control from CICS is referred to as the main  program; the remaining parts\nare referred to as subprograms . These programs are written in the same or different languages.\nComposite support lets you test and debug a subprogram as if it were a separate program. Specify a separate LNK option\nfor the main program and for each subprogram you want to test separately.\n 1125", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8b8a8a92764f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIt is easier to set LNK options on the CNTL Composite Support screen than with single-line commands. Most of the\nnecessary information is supplied in an InterTest for CICS batch job step.\nTo set composite support for a composite module, enter:\nLNK=(composite module information)\nLMD Specify Load Module\nUse the LMD option to specify a particular composite load module name  when setting or changing the monitoring options\nfor its subprograms. For more information about the composite support, see Monitoring Menu Options.\nThis option applies for Composite Support  only. It is reasonable to use this option only if a subprogram exists in multiple\ncomposite modules.\nTo specify a load module, enter:\nLMD=lmdname\nlmdname\nSpecifies the load module name of a composite module.\nExample:\nAssume two composite modules COBDEML1 and COBDEML2 are being monitored. Both of the composite modules\ncontain a subprogram called ASBIN25.\nAn unconditional breakpoint at statement number 00098 of the subprogram ASBIN25 residing in the composite module\nCOBDEML2 is requested. Following CNTL command can be used:\nCNTL=ON,PROG=ASBIN25,UBP=00098,LMD=COBDEML2 \nMON Set Monitor ON Locations for Segmented Monitoring\nWARNING\nThe segmented monitoring options MON and NOM may cause unpredictable damage to the CICS system if not\nused properly. For more information about using MON and NOM, see Special Monitoring Situations. MON and\nNOM pertain to all users and are not user ID sensitive.\nNotes:\nMON is supported only in releases 5.1 and higher. MON options are not user ID sensitive and pertain to all users.\nTo set monitor on locations for segmented monitoring, enter:\nMON=locn", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8b8a8a92764f-1", "text": "To set monitor on locations for segmented monitoring, enter:\nMON=locn\nMON=(locn1,locn2,...,locn9)\nlocn\nSpecifies a program  location where InterTest for CICS starts or continues monitoring using the special\nsegmented monitoring method. The location must specify the op-code of a machine instruction that resides in\nnon-store-protected virtual storage.\nSpecify, in quotes, the location as a COBOL paragraph name or a PL/I or Assembler label; without quotes a COBOL or\nPL/I statement number (a decimal number preceded by a # sign), or a hexadecimal displacement from the beginning of\nthe program, or an address in main storage.\nMUS Limit the Number of Times a Program Is Monitored\nTo limit the number of times a program is monitored, enter:\n 1126", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "38bf7c73a31e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMUS=limit\nlimit\nSpecifies the number of times a program is monitored. Replace limit with a decimal number from 1 to 65,534.\nMXR Limit the Number of CICS Requests\nThe MXR option is useful when a program is in a loop that includes a CICS request and therefore will not time out.\nTo limit the number of CICS request, enter:\nMXR=nnnnnnn\nnnnnnnn\nSpecifies the number of CICS requests a program issues. Replace nnnnnnn  with a decimal number up to one\nmillion.\nMXS Limit Storage Usage\nTo limit storage usage, enter:\nMXS=nnnnnnn\nnnnnnnn\nSpecifies the amount of storage, including program storage that a program acquires. Replace nnnnnnn  with a\ndecimal number up to one million.\nNOM Set NO Monitor Locations for Segmented Monitoring\nWARNING\nThe segmented monitoring options MON and NOM might cause unpredictable damage to the CICS system if not\nused properly. For more information about using MON and NOM, see Special Monitoring Situations. MON and\nNOM pertain to all users and are not user ID -sensitive.\nNotes:\nNOM is supported in releases 5.1 and higher, only. NOM is not user ID sensitive and pertains to all users\nTo set no monitor locations for segmented monitoring, enter:\nNOM=locn\nNOM=(locn1,locn2,...,locn9)\n\u2022locn\nSpecifies a  program   location where InterTest for CICS stops monitoring using the special segmented monitoring\nmethod. The location must specify the op-code of a machine instruction that resides in non-store-protected virtual\nstorage.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "38bf7c73a31e-1", "text": "storage.\nSpecify the location as a COBOL paragraph name (in quotes), a PL/I or Assembler label (in quotes), a COBOL or PL/I\nstatement number (a decimal number preceded by a # sign), or a hexadecimal displacement from the beginning of the\nprogram. The location also specifies an address in main storage.\nNRB Prevent a Read Buffer Before a Breakpoint Display\nThe read buffer request lets InterTest for CICS restore the screen when you are finished with the breakpoint display.\nHowever, if the read buffer cannot be executed because the terminal or transmission network prevents it, you must issue\nthe NRB option to prevent the request.\nTo prevent InterTest from issuing a read buffer before displaying a breakpoint, enter:\n 1127", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f4304a42f5a0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNRB=ON\nNUP Prevent a Program from Updating CICS Files\nThe NUP option prevents a program from actually updating VSAM and BDAM CICS files. This option allows repeated\ntests of transactions without altering test records. The NUP option also prevents test programs from modifying production\nfiles.\nTo prevent a program from updating CICS files, enter:\nNUP=ON\nOVR Override Error Conditions That Trigger an ABP\nThe OVR option instructs InterTest for CICS to ignore error conditions that would otherwise trigger an automatic\nbreakpoint. For a list of error codes, see Examining Dumps.\nTo override an error that could trigger an ABP, enter:\nOVR=errcode\nor\nOVR=(errcode1,errcode2,...)\nerrcode\nSpecifies a hexadecimal InterTest for CICS error code.\nWARNING\nUse caution in specifying this option. Remember, it forces InterTest for CICS to ignore potentially dangerous\nconditions.\nPRO Protect Storage from Being Modified\nThe PRO option generates an automatic breakpoint whenever the monitored program attempts to modify the protected\narea. This is useful when you are trying to determine how an area of storage is being modified.\nSpecify the PRO option while a program is at a breakpoint if the storage location is different each time the program\nexecutes.\nTo protect storage from being modified, enter:\nPRO=(address,length)\naddress\nSpecifies the starting address of the protected storage area as six- to eight-hexadecimal digits.\nlength\nSpecifies, in hexadecimal, the number of protected bytes.\nRBP Specify Request Breakpoints\nThe RBP option lets you halt a program prior to all CICS commands, DL/I, DB2, or calls to software recognized by", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f4304a42f5a0-1", "text": "InterTest for CICS. This option also lets you halt a program prior to specific CICS commands, such as File Control or\nProgram Control commands. Most users will find it easier to use the CNTL Command Builder menus rather than the RBP\noption to specify request breakpoints.\nNOTE\nIf the F=term1 or T=term2 parameter is omitted, it defaults to the terminal that issued the RBP option.\nTo specify request breakpoints, use the following commands:\n 1128", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4f96158663af-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nRBP=request\nRBP=(request1,request2,...,request9)\nRBP=((request),F=term1,T=term2) \nRBP=((request1,...,request9),F=term1,T=term2)\nRBP=((request),F=term1,T=term2,L=loopnumber) \nRBP=((request1,...,request9),F=term1,T=term2,L=loopnumber)\n\u2022request\nSpecifies where the request breakpoint should occur:\n\u2013ALLCOM prior to all CICS commands\n\u2013ALLDLI prior to all DL/I calls\n\u2013ALLCAL prior to all calls to software InterTest for CICS has been instructed to recognize at installation time\n\u2013code  prior to the CICS commands represented by the code\nFor a list of valid codes, see the Help facility.\n\u2022term1\nSpecifies the terminal at which the program must be executing for the breakpoint to take effect. F=.ANY specifies that\nthe breakpoint take effect at all terminals -- even when the program executes without a terminal. F=.NO specifies that\nthe breakpoint take effect only when the program executes without a terminal.\n\u2022term2\nSpecifies the terminal to which the breakpoint display is sent. T=.ANY specifies that the breakpoint display be sent to\nthe terminal at which the program is executing.\n\u2022loopnumber\nSpecifies how often the program should be halted at the breakpoint.\nExample\nL=2 halts the program every other time it reaches the specified command; L=13 halts it every thirteenth time. If this\nparameter is omitted, the breakpoint occurs every time the program reaches the specified command. This parameter is\nespecially useful when a CICS command occurs within a loop; for example, during a browse.\nRFC Replace File Names", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4f96158663af-1", "text": "RFC Replace File Names\nThe RFC option dynamically substitutes one file name for another during program execution. This is useful when you want\nto use test files in a production environment, or when you want to use several different files to test a program.\nTo replace file names, enter:\nRFC=(file1,file2)\n\u2022file1\nSpecifies the file to be replaced.\n\u2022file2\nSpecifies the file that will replace file1.\nRNT Prevent a Program from Modifying Its Own Code\nThe RNT option lets you test a program for reentrancy by preventing the program from modifying its own code.\nTo prevent a program from modifying its own code, enter:\nRNT=ON\n 1129", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c37845520723-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nRPC Replace Program Names\nThe RPC option dynamically substitutes one program name for another in LOAD, LINK, and XCTL requests made by a\nmonitored program. This lets multiple copies of a program coexist in one system, provided each has its own PPT entry.\nUse the RPC option when you want to test a program using modules other than the ones coded in the program.\nTo replace program names, enter:\nRPC=(prog1,prog2)\nprog1\nSpecifies the program to be replaced.\nprog2\nSpecifies the program to replace prog1 .\nRTD Replace Transient Data Queue Names\nThe RTD option dynamically substitutes one transient data queue name for another during program execution so you can\ntest a program using transient data queues other than the ones coded in your program.\nTo replace transient data queue names, enter:\nRTD=(name1,name2)\nname1\nSpecifies the transient data queue name to be replaced.\nname2\nSpecifies the transient data queue name to replace name1 .\nRTS Replace Temporary Storage Identifications\nThe RTS option dynamically substitutes one temporary storage identification for another during program execution so you\ncan test a program using temporary storage identifications other than the ones coded in your program.\nTo replace temporary storage IDs, enter:\nRTS=(mask1,mask2)\nmask1\nSpecifies the temporary storage ID to be replaced.\nmask2\nSpecifies the temporary storage ID to replace mask1 .\nSpecify both masks as eight bytes in either character (C' data' ) or hexadecimal (X' data') format.\nSDF Structure Display Format Setting\nTo override, by program, the global default setting, enter:\nSDF=HEX or SDF=DATA\n\u2022HEX\nDisplays data in hexadecimal or character format.\n\u2022DATA\nDisplays data in Structure Display Format.\n 1130", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f6df06fdf892-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSLB Activate the Source Listing Breakpoint Facility\nThis option activates the Source Listing Breakpoint display for the specified terminal.\nTo activate the source listing breakpoint facility, enter:\nSLB=termid\nSLB=*\ntermid\nSpecifies the terminal to receive breakpoint displays.\n*\nSpecifies the terminal from which the option is issued.\nSTR Save the CICS Trace Table\nThe STR option instructs InterTest for CICS to preserve a copy of the CICS trace table when a program stops at a\nbreakpoint. Issue the command CORE=STRA to display the table. The most recent table entries display first; view earlier\nentries by scrolling through the display.\nTo save the CICS trace table, enter:\nSTR=ON\nTAL Count How Often an Instruction Is Executed\nThe TAL option counts the number of times a program reaches a specified location. This option is useful with a conditional\nbreakpoint because it lets you specify how often a program should be halted within a loop. Use the loopnumber  parameter\nwhen specifying an unconditional breakpoint to perform the same task.\nTo count the number of times an instruction executes, enter:\nTAL=locn\nlocn\nSpecifies a program  location as a COBOL paragraph name (in quotes), a PL/I or Assembler label (in quotes), a\nCOBOL or PL/I statement number (preceded by a # sign), or a hexadecimal displacement from the beginning of\nthe program.\nTER Change the Terminal ID\nThe TER option changes all occurrences of the old terminal ID to the new terminal ID whenever a terminal ID is specified\nfor an online option; for example, in a UBP option. This is useful when you have set terminal-specific options, and then\nneed to move to another terminal to continue testing.\nTo change the terminal ID, enter:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f6df06fdf892-1", "text": "need to move to another terminal to continue testing.\nTo change the terminal ID, enter:\nTER=(oldtrm,newtrm)\noldtrm\nSpecifies the old terminal ID.\nnewtrm\nSpecifies the new terminal ID.\nTFL Set Non-Interactive Monitoring\nThis option instructs InterTest for CICS to set a non-interactive monitoring session. This option disables automatic\nbreakpoints in monitored programs, transactions or terminals, and disables all breakpoint options. The non-interactive\nmonitoring session is set for a one-time occurrence only. Once the session is run, the monitoring is automatically disabled.\n 1131", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c4760f6ffa01-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nNon-Interactive monitoring is intended for collecting code coverage and/or trace data. This monitoring should\nbe used for transactions that complete successfully as not all the diagnostic data are available for failing\ntransactions during non-interactive processing.\nThis option accepts a token with a maximum of 8 characters as an input. The token must be unique for each monitoring\nsession, and is used to generate the report outputs of the non-interactive session. These outputs include an audit log\ndetailing the execution of the program, code coverage, and trace data. Use the CCV and TRC options to enable code\ncoverage and trace data creation.\nThe USSPATH specified under installation options for InterTest for CICS is used as a directory to save these files. If\nthe USSPATH is not specified correctly, this option is disregarded and error message CAIN4624 displays. For more\ninformation on USSPATH, see IN25OPTS Keywords.\nTo turn on non-interactive monitoring and produce an audit log, enter\nTFL=token\nThe audit log file generated from a non-interactive session will be in JSON format. This file contains a general report on\nmonitoring entries, time stamp, reason for termination of program execution and final values of general purpose registers.\nExample\nTo turn on non-interactive monitoring for program COBDEMO, enter\nCNTL=ON,PROG=COBDEMO,TFL=ABCDE\nAfter the transaction executes, the monitoring session for the specific program is terminated and an audit log (ABCDE.rpt)\nis generated.\nNOTE\nNon-interactive monitoring has precedence over normal (interactive) monitoring sessions.\nTON Limit Monitoring to One Terminal\nThe TON option instructs InterTest for CICS to monitor a program or transaction only when it executes at a specific\nterminal or without a terminal.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c4760f6ffa01-1", "text": "terminal or without a terminal.\nTo limit monitoring to a single terminal, enter:\nTON=termid \nor\nTON=*\nor\nTON=.NO\ntermid\nSpecifies the terminal the program must execute from to be monitored.\n*\nSpecifies that the program must execute at the current terminal to be monitored.\n.NO\nSpecifies that the program must execute without a terminal to be monitored.\n 1132", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aacf853af672-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTRC Statement Tracing Option\nThis option instructs InterTest for CICS to save trace information for every COBOL statement executed in the program or\ntransaction, or at a terminal.\nTo set statement tracing for a particular program, transaction, or terminal, enter:\nTRC=ON\nThis option is unrelated to the backtrace facility.\nIf this option is used together with the TFL option, a statement trace report is generated upon program execution.\nTFL=Token,TRC=ON\nThe file generated is in JSON format and includes the execution flow of the monitored program.\nExamples\nTo turn on non-interactive monitoring and get statement trace data for the program COBDEMO, enter\nCNTL=ON,PROG=COBDEMO,TFL=ABCDE,TRC=ON\nAfter the transaction executes, the monitoring session for the specific program is terminated and an audit log (ABCDE.rpt)\nand trace data (ABCDE.trc) are generated.\nFor more information about the token that is used for the TFL option, see TFL Set Non-Interactive Monitoring.\nUBP Specify Unconditional Breakpoints\nTo specify unconditional breakpoints, use the following commands:\nUBP=locn\nUBP=(locn1,locn2,...,locn9)\nUBP=((locn),F=term1,T=term2) \nUBP=((locn1,...,locn9),F=term1,T=term2)\nUBP=((locn),F=term1,T=term2,L=loopnumber) \nUBP=((locn1,...,locn9),F=term1,T=term2,L=loopnumber)\nubp=((ALLPAR),F=term1,T=term2,L=loopnumber)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aacf853af672-1", "text": "ubp=((ALLPAR),F=term1,T=term2,L=loopnumber) \nubp=((ALLLAB),F=term1,T=term2,L=loopnumber)\n\u2022locn\nSpecifies a program location as a COBOL paragraph name (in quotes), a PL/I or Assembler label (in quotes), a\nCOBOL or PL/I statement number (preceded by a # sign), or a hexadecimal displacement from the beginning of the\nprogram. locn also specifies an address in main storage.\nThe following operands specify the terminal at which the program must be executing for the breakpoint to take effect.\nF=.ANY\nSpecifies that the breakpoint take effect at all terminals, even when the program executes without a terminal.\nF=.NO\nSpecifies that the breakpoint take effect only when the program executes without a terminal.\nterm2\nSpecifies the terminal to which the breakpoint display is sent.\nT=.ANY\nSpecifies that the breakpoint display be sent to the terminal at which the program is executing.\nNOTE\nIf the F=term1 or T=term2 parameter is omitted, it defaults to the terminal that issued the UBP option.\n 1133", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c73757a5e6d3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nloopnumber\nSpecifies how often the program should halt when a breakpoint is within a loop.\nExample\nL=2 halts the program every other time it passes through the loop; L=3 halts it every third time. If this parameter is\nomitted, the breakpoint occurs every time the program reaches the location.\nALLPAR\nSpecifies that breakpoints take effect at all COBOL paragraph names.\nALLLAB\nSpecifies that breakpoints take effect at all Assembler labels.\nWhen you set unconditional breakpoints, InterTest for CICS halts the program at the specified locations.\nUSH Unprotect Shared Storage\nThe USH option removes storage protection from all main storage areas residing in the SHARED storage subpool.\nThis option lets a program change all CLASS=SHARED storage, and other storage areas in the SHARED subpool.\nFREEMAINs of these areas are permitted; however, the four-byte Storage Accounting Areas remain protected.\nTo unprotect shared storage, enter:\nUSH=ON\nThe TER option changes all occurrences of the old terminal ID to the new terminal ID whenever a terminal ID is specified\nfor an online option; for example, in a UBP option. This is useful when you have set terminal-specific options, and then\nneed to move to another terminal to continue testing.\nWARNING\nUse this option with extreme caution.\nUSR Limit Monitoring to a CICS User ID\nWhen security is active in the region and the IN25OPTS global installation option is set to DFLTUSR=SPECIFIC, a signed\non user's monitoring request defaults to using the requester's individual user ID (USR=userid). Otherwise, the default\nUSR= option is set to .ANY.\nMonitoring options set for a specific user ID have advantages. The From and To terminals automatically default to .ANY.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c73757a5e6d3-1", "text": "This means that you can switch terminals and continue to have monitoring, breakpoints, and options set for his user ID\ndirected to the new terminal.\nFor releases 5.4 and higher, to limit monitoring to a specific CICS user ID in a secure region, enter:\nUSR=userid\nuserid\nSpecifies CICS user ID.\nTo monitor all users of the promid , enter:\nUSR=.ANY\nAccessing Main Storage CORE\nCORE is the CICS transaction supplied with InterTest for CICS that gives you access to main storage areas both before\nand during a test session. Application programmers typically use CORE interactively to examine and modify areas\nof main storage while their program is stopped at a breakpoint. Use CORE also to examine and change (subject to\n 1134", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "927b8f203f34-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\npassword restriction) the contents of CICS tables and control blocks with or without a program at a breakpoint. CORE is\nindependent of the rest of InterTest for CICS and you can use it when the InterTest for CICS monitor is not active.\nThe Main Storage Facilities (CORE)\nUse CORE in the following ways:\n\u2022Source Listing Facility action characters:  Use a  d or m on the Source Listing Breakpoint screen to display or modify\nbreakpoint-related storage. For more information about this method, see Source Listing Facility for InterTest.\n\u2022Main Storage Menus:  Use Option 3 Main Storage  from the Primary Option menu to access the Main Storage menu\nfor CORE facilities. From a breakpoint, just type CORE  on the command line to go directly to the Main Storage menu.\n\u2022The Main Storage menu lets you access storage related to CICS system, task, and breakpoint areas without using any\ncommand syntax. (The menus build CORE commands for you.)\n\u2022CORE commands:  Once you become familiar with InterTest for CICS, use the CORE command formats and\nadvanced options. Enter CORE commands at the bottom of a CORE facility display, in the command line of any\nbreakpoint or Source Listing display, or directly from CICS.\nMain Storage Capabilities\nUsing Main Storage facilities of InterTest for CICS, you can do any of these functions:\n\u2022Display areas of CICS main storage\n\u2013Program-related areas such as data items or the COMMAREA\n\u2013Task-related areas such as the TCA or TWA\n\u2013System-related areas such as the CSA, CICS tables, or BMS maps\n\u2013Qualified, indexed, or subscripted COBOL data names\n\u2022Display a data structure in COBOL DMAP sequence, Assembler DSECT sequence, or CICS areas in DSECT\nsequence", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "927b8f203f34-1", "text": "sequence\n\u2022Modify areas of CICS main storage by\n\u2013Directly typing over the displayed data\n\u2013Filling in a pre-for matted MOVE command\n\u2013Moving data from one location to another\n\u2022Scan backward and forward through CICS main storage for specified data strings\n\u2022Load or delete a program load module\n\u2022Dynamically acquire CICS main storage\n\u2022Dump a specified area to the dump data set\n\u2022If you display a COBOL data item when your program is at a breakpoint, InterTest for CICS formats the field according\nto its definition and determines whether the field's current value is valid. For example, if you use CORE to display the\ncontents of a COMP-3 field that contains low-values such as binary zeros, InterTest for CICS automatically informs you\nthat the field contains invalid data. In addition, if the field is numeric, such as hexadecimal or packed decimal, InterTest\nfor CICS displays its decimal value.\nCORE Main Storage Displays\nThe CORE facility provides two storage display formats: structured and dump. When available, the structured format is the\ndefault.\nThe structured format  gives field names and displays storage field-by-field, which makes it easy to read and modify. The\nstructured format displays a COBOL data structure in DMAP sequence, an Assembler data structure in DSECT sequence,\nand common CICS areas in DSECT sequence. You do not have to know or remember field lengths to determine their\ncontents. The basic format of the structured display is:\nfield hexadecimal value character value\n 1135", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8d6e4aad8901-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBy contrast, the traditional  dump format  starts from a given point (which you specify) and is a continuous stream of\nvalues. You have to remember field lengths to know where one field stops and the next one starts.\nBoth formats provide similar functional capabilities, including:\nFull-screen edit\npermits you to dynamically modify displayed storage\nCORE command line\ndisplays the last CORE command executed. Change this command to any CORE or CNTL command.\nMessage line\nnotifies you of: invalid storage values, the values of numeric data, additional CORE requests queued for display,\nor if the requested storage area was not found.\nPF keys\nlet you scroll, switch the format displayed, access help, and return to a menu or breakpoint.\nThe Structured Format\nThere are two versions of the structured format:\n\u2022One for COBOL and PL/I\n\u2022One for Assembler and CICS data structures\nThe COBOL and PL/I Structured Display\nYou obtain a structured display by default when accessing main storage from:\n\u2022Source Listing Breakpoint screens\n\u2022Main Storage menus\nTo obtain a structured display when using CORE commands at the bottom of a current storage display, enter the\ncommand and press PF12 Structure .\nNOTE\nIf you request a storage display and a structured format is not available, the dump format and a message are\ndisplayed.\nThe following diagram shows the structured format for a COBOL data structure:\n      CA InterTest for CICS      - MAIN STORAGE UTILITY - Termid = U056     \n                                          \nStarting at Address =2370A140               Hexadecimal            Character   \n01 TASK-STRUCTURE                   |                            |  \n 02 TASK-CNTL                       | C3D5E3D3                   | CNTL", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8d6e4aad8901-1", "text": "02 TASK-PROTCPF                    | D7D9D6E3 C3D7C640          | PROTCPF      \n 02 TASK-PROTHLF                    | D7D9D6E3 C8D3C640          | PROTHLF      \n 02 TASK-SWITCH                     | 40                         |              \n 02 TASK-SWITCH2                    | F0F0                       | 00           \n 02 TASK-SWITCH3                    | 40                         |              \n 02 TASKNUM                         | 000000                     | ...          \n 02 TASKNUM-CHAR                    | 000000                     | ...          \n 02 TASK-TEXT                       |                            |              \n  03 TASK-ID-NO                     | 000F                       | ...         \n  03 FILLER                         | 40                         |             \n  03 TASK-MESG                      | E3C8C9E2 40C9E240 C140D4C5 | THIS IS A ME\n                                    | E2E2C1C7 C5404040          | SSAGE        \n  03 FILLER                         | 40                         |              \n 1136", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f9ef100cfe76-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  03 TASK-DATE                      |                            |              \n ------------------------------------------------------------------------------ \n  PF1 Help       2            3 End        4 Return     5            6 Dump     \n  PF7 Backward   8 Forward    9 Caps Off  10           11 Redisplay 12 SDF      \nCORE='TASK-STRUCTURE'      \nCAIN0467 AT LAST ENTRY IN STRUCTURE \nThe structured format displays COBOL data in DMAP sequence. The structure of a PL/I variable is presented similarly.\nEach field is discussed next.\n\u2022Starting Address  of the first item displayed.\n\u2022This is calculated from the contents of the BL and BLL cell and displacement for the requested data name.\n\u2022DMAP or SYM MAP\nData levels and names for the requested structure.\nA 77-level item is displayed individually; other structured displays begin with the requested data item and include any\nitems below it in the same 01 level.\n\u2022Hexadecimal display area\nGives the storage contents of each field named on the left. Each byte is displayed as two hexadecimal digits, with\nspaces inserted after every four bytes. Up to 12 bytes are displayed per line. Fields longer than 12 bytes have multiple\nlines of hexadecimal display. This area is unprotected and you can overtype it to dynamically modify the data values\ndisplayed.\nNote:  Data areas defined in the DMAP or SYM MAP with a length of zero (for example, 0F or 0C13) will not display.\n\u2022Character display area\nGives the character representation of each displayable byte for the field on the left. Hexadecimal 40s display\nas spaces; non-displayable bytes are indicated by periods. This area is unprotected and you can overtype it to\ndynamically modify the data values displayed.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f9ef100cfe76-1", "text": "dynamically modify the data values displayed.\n\u2022PF keys  are listed below the storage display. For more information about them, see Structured Displays.\n\u2022CORE command line\nDisplays the CORE command entered or generated from a Source Listing Breakpoint storage request or a CORE\nmenu. To request another structured display, modify the CORE command and press PF12. To request a dump format\nof a CORE display or to enter a CNTL command, modify the command and press Enter .\n\u2022Message line\nAlways check the message line on a CORE display. This message states that the end of the requested data structure\nhas been reached. (Page backward to display the beginning of a data structure or page forward when you are not\nat the end of the structure.) However, this message line also tells you if the requested area could not be found (the\ndisplay shows the last area pointed to by CORE or the CSA), or if a COBOL field or PL/I variable displayed from a\nbreakpoint contains valid data. An error message indicates when a field is invalid.\nThe Assembler and CICS Areas Structured Display\nYou obtain a structured display by default when accessing Assembler main storage from:\n\u2022Source Listing Breakpoint screens\n\u2022Main Storage menus\nTo get a structured display when executing a CORE command from an existing CORE display, type the command and\npress  PF12  instead of Enter.\nNOTE\nIf a structured format is not available for the requested area or data, the dump format and a message display.\nThe following diagram gives the structured format for Assembler and CICS areas. The fields are displayed in DSECT\nsequence.\n  CA InterTest for CICS       - MAIN STORAGE UTILITY - Termid = U056      \n 1137", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "301584eb6dec-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n   \nStarting at Address =  100CE8  Disp          HEXADECIMAL            CHARACTER   \nTASKNUM                         189 | 000000                     | ...          \nTSTEXT                          18C | 00000000 00000000 00000000 | ............\n                                    | 00000000 00000000 00000000 | ............\n                                    | 00000000 00000000          | ........     \nMSGNAME                         1AC | 00000000                   | ....         \nMSGLEN                          1B0 | 01D5                       | .N           \nRECRBA                          1B2 | 00000000 0000              | ......       \nRECPONT                         1B8 | 00000000                   | ....         \n                                1BC | 00                         | .            \nDMAP04AS                        1BC |                            |              \n                                1BC | 00000000 00000000 00000000 | ............\nRECOUT1L                        1C8 | 0000                       | ..           \nRECOUT1F                        1CA | 00                         | .            \nRECOUT1A                        1CA | 00                         | .            \nRECOUT1I                        1CB | 00                         | .            \nRECOUT1O                        1CB | 00000000 00000000 00000000 | ............\n ------------------------------------------------------------------------------ \n PF1 Help       2            3 End        4 Return     5            6 Dump      \n PF7 Backward   8 Forward    9 Caps Off  10           11 Redisplay 12 SDF       \n CORE='R13.TASKNUM' \n\u2022Starting ...\n\u2022Individual field names as defined in the DSECT.\n\u2022100CEB", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "301584eb6dec-1", "text": "\u2022Individual field names as defined in the DSECT.\n\u2022100CEB\nCICS address of each field.\n\u2022Disp\nDisplacement column is the field's relative hexadecimal displacement within the DSECT.\n\u2022Hexadecimal display area\nGives the storage contents of each field named on the left. Each byte is displayed as two hexadecimal digits with\nspaces inserted after every four bytes. Up to 16 bytes display per line. Fields longer than 16 bytes have multiple\nlines of hexadecimal display. This area is unprotected and you can overtype it to dynamically modify the data values\ndisplayed.\n\u2022Character display area\nGives the character representation of each displayable byte for the field on the left. Hexadecimal 40s display as\nspaces; non-displayable bytes are indicated by periods. Overtype this area to dynamically modify the data values\ndisplayed.\n\u2022PF keys\nListed below the storage display. For more information about them, see the Structured Displays sections in this article.\n\u2022CORE command line\nDisplays the CORE command entered or generated from a Source Listing Breakpoint storage request or a CORE\nmenu. To request another structured display, modify the CORE command and press PF12 . To request a dump format\nof a CORE display or to enter a CNTL command, modify the command and press Enter .\nUse Another Program\u2019s Data Definitions (USE Option)\nStructured display is normally used to format an application's storage area with its own data definitions. However, format\nany CICS storage area with any program's data definitions. To use another program's data definitions, add one of the\nfollowing specifications as the last element in a CORE command:\n=USE=progname.dataname \n 1138", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "062d026e7bf2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nor\n=USE=*.dataname\nprogname\nSpecifies the name of the program that contains the structured information.\ndataname\nSpecifies the name of the data item used as the starting point for the structured display.\n*\nSpecifies the program currently stopped at a breakpoint.\nExamples\nEach command is preceded by an explanation of how it works.\n\u2022To display the area pointed to by register 1 according to the data definition of COMAREA in the program stopped at a\nbreakpoint, enter:\nCORE@R1=USE=*.COMAREA\n\u2022To display the first FWA area according to the data definition of RECORD1, which is in the TESTMAST program, enter:\nCORE=FWA=USE=TESTMAST.RECORD1\nStructured Displays of DSECTs in PRINT OFF Areas\nTo get a structured display for a DSECT in a PRINT OFF area:\n1.Create an Assembler job containing your common DSECT layouts and use the InterTest for CICS post-processor step.\nTo save space in the InterTest for CICS Symbolic File:\n\u2013Do not specify the LISTER option.\n\u2013Do not link-edit the module.\n\u2013No PPT entry is necessary.\nThe module name must be unique in the InterTest for CICS symbolic file, or create one program containing all the\ncommon DSECTs and have them printed in the Assembler listing.\n2.To reference the module created in Step 1, add the following USE option to your CORE commands:\nCORE=USE=modulename\nThis command instructs CORE to use the named module instead of the program stopped at a breakpoint when\ninterpreting any symbolic names in the command.\nExample", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "062d026e7bf2-1", "text": "interpreting any symbolic names in the command.\nExample\nTo get a structured display of the USER TCA, which is the DFHTCADS DSECT whose address is in register 12 and is\nsaved in the module TESTMAST, enter:\nCORE='R12.DFHTCADS'=USE=TESTMAST\nStructured Displays of Common CICS Areas\nThe common CICS areas that display in a structured format (Assembler DSECT layout) depend on your InterTest for\nCICS installation. The default system areas available in a structured format are listed in the following CORE keywords:\nCLOT\nCICS Life-Of-Task Block (z/OS only)\nCSA\nCommon System Area\n 1139", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6bf0c3bf25e9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDCA\nDestination Control Area\nEIB\nEXEC Interface Block\nEIS\nEXEC Interface Structure\nOPFL\nOptional Features List\nRDIIN\nApplication Invocation Parameter List (z/OS only)\nSIT\nSystem Initialization Table\nSQLCA\nSQL Communication Area (z/OS only)\nTACB\nTransaction Abend Control Block\nTCA\nTransaction Control Area\nTCT\nTransaction Control Table\nNOTE\nTo add or subtract areas from the previous list, see CICS Interfaces and Compatibility.\nTo get a structured display of system areas, use the System Areas menu or enter a CORE  command, and press PF12 .\nStructured Displays PF Keys\nThe following list shows the PF keys and their associated functions:\nPF1 Help\nInitiates the InterTest for CICS online help facility.\nPF2\nUnassigned\nPF3 End\nExits the current menu or CORE display. If at a breakpoint, returns to the breakpoint display. Clear performs the\nsame function.\nPF4 Return\nReturns to the Primary Option menu or exits to CICS.\nPF5\nUnassigned\nPF6\nThis PF key lets the cursor be placed on a valid storage pointer within the hexadecimal display area and the\nstorage pointed to by the pointer will be displayed when this key is pressed. This is referred to as \u2017point and\nshoot\u2018 capability and allows for faster navigation through storage without having to key storage addresses on the\nCORE command line.\nPF7 Backward\nScrolls the current CORE display one page backward.\n 1140", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e014bb71ff9c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPF8 Forward\nScrolls the current CORE display one page forward.\nPF9 Caps Off or Caps On\nSets the mode of translation when changing data in the character area of the display. When Caps Off displays, all\ncharacter data on the line is translated to uppercase. When Caps On displays, all character data is accepted as\ntyped. To change from one mode to the other, simply press PF9.\nNote:  Translation to uppercase does not occur if an existing lowercase character on that line would be affected; a\nmessage is issued instead.\nPF10\nVaries according to what displays.\nPF11 Redisplay\nRedisplays the current screen with only the contents of storage being refreshed.\nPF12 Structure\nDisplays requested fields in a structured format.\nThe Dump Format\nThe dump format is similar to a transaction dump printout, with a hexadecimal display area on the left and a character\ndisplay area on the right. Obtain a dump format in the following ways:\n\u2022Use the Source Listing Breakpoint screen to display or modify a data item or area without  a structure such as object\ncode.\n\u2022Press Enter  when completing a CORE menu or executing a CORE command.\nThe following display shows the dump format display of the CICS CSA (Common System Area).\n   CA InterTest for CICS  - MAIN STORAGE UTILITY  Termid = X520  \n Offset                                                            Address Task\n +   0  00000000 00104FA8 001056F0 504CC492  * ......y....0&<Dk *  55EAE0  921\n +  10  00BA8000 004CEA90 00203004 9054A00C  * .....<.......... *  55EAF0", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e014bb71ff9c-1", "text": "+  20  0000001B 001FD48A 405499DA 4054D400  * ......M. .r. .M. *  55EB00  Page\n +  30  0054A9DA 001FD480 00203004 004EA410  * ..z...M......+u. *  55EB10  +000\n +  40  004CE800 0021F140 0010999C 0021F140  * .<Y...1 ..r...1  *  55EB20     \n +  50  1858387F 001FE6E0 03E80100 00000000  * ...\"..W..Y...... *  55EB30  CSA\n +  60  00683F03 00012C00 007F9308 000095BC  * .........\"l...n. *  55EB40     \n +  70  0000A000 00105800 00569000 0087362F  * .............g.. *  55EB50     \n +  80  00560190 E0FFFFBE 0000004B 00561438  * ................ *  55EB60     \n +  90  0000007B 00000000 00382030 D438C616  * ...#........M.F. *  55EB70     \n +  A0  00000000 001FE580 001FE240 001FE190  * ......V...S .... *  55EB80", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e014bb71ff9c-2", "text": "+  B0  001FE300 0055F1B8 0055F388 C500FF00  * ..T...1...3hE... *  55EB90     \n +  C0  000A0004 00000400 0055EEE0 00000000  * ................ *  55EBA0     \n +  D0  00000000 00000000 007F9308 00000000  * .........\"l..... *  55EBB0     \n +  E0  40558718 004CC010 004BF9C0 00551CB0  *  .g..<....9..... *  55EBC0     \n +  F0  00492556 004CEF30 004BA0B8 004AC100  * .....<.......cA. *  55EBD0     \n + 100  004AEE94 0049E10A 0048AF74 0047ABD0  * .c.m............ *  55EBE0     \n ______________________________________________________________________________           \n  PF1 Help       2            3 End        4 Return     5           6 Dump    \n  PF7 Backward   8 Forward    9 Caps Off  10           11          12 Structure\nOffset\nGives the hexadecimal displacement of the first byte of data on that line relative to the first byte of data on page\nnumber 0. Page number 0 is the first screen of a CORE display.\n 1141", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "64e76b93de24-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nHexadecimal display area\nShows each byte of data as two hexadecimal digits. Data is displayed 16 bytes per line, with spaces inserted\nafter every four bytes (eight hexadecimal digits). The maximum size of a single CORE display is 17 lines, or 272\n(hexadecimal 110) bytes of data.\nCharacter display area\nGives the character representation for each displayable byte. Hexadecimal 40s display as spaces; non-\ndisplayable bytes are indicated by periods. The columns of asterisks are not part of the data.\nAddress\nIndictates the CICS hexadecimal address of the first byte of the line.\nTask\nGives the task number of the breakpointed task for breakpoint-related storage displays. For task-related storage\ndisplays, gives the task number specified. (The default for task-related storage is also the task number of the\nbreakpointed task.)\nPage\nPage numbers are relative to the initial screen display. Paging forward with PF8  increases the page count; paging\nbackward with PF7 decreases the page count.\nThe area below the display area includes the following items:\n\u2022PF Key list.\n\u2022The command line in the Dump Format of CICS CSA displays the last CORE command entered or generated for the\ncurrent display. To request a structured format of the current CORE display, press PF12 . To request another CORE\ndisplay or to enter a CNTL command, modify the command and press Enter  (for a dump format or a CNTL command)\nor PF12  (for a structured format).\n\u2022The message line follows the command line and contains valuable information. Always read the message line on a\nCORE display.\n\u2022If InterTest for CICS could not locate a requested display area, the error message indicates that the requested area", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "64e76b93de24-1", "text": "was not found. When this occurs, InterTest for CICS displays the dump format of the last or default CORE pointer\nlocation. The default area is the CSA.\nSome messages can help you troubleshoot problems in storage.\nExample\nWhenever you are stopped at a breakpoint and request a COBOL storage display, InterTest for CICS automatically checks\nthat the fields in the display contain valid data (according to their definitions). An error message tells you which fields are\ninvalid and why.\nDump Display PF Keys\nThe following list explains what each PF key on the Dump Display does.\nPF1 Help\nInitiates the InterTest for CICS online help facility.\nPF2\nUnassigned\nPF3 End\nTerminates the current menu or CORE display. If at a breakpoint, returns to the breakpoint display. Clear performs\nthe same function.\nPF4 Return\nReturns to the Primary Option menu or exits to CICS.\nPF5\nUnassigned\n 1142", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "409a2e2bcb3c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPF6\nThis PF key lets the cursor be placed on a valid storage pointer within the hexadecimal display area and the\nstorage pointed to by the pointer will be displayed when this key is pressed. This is referred to as 'point and shoot'\ncapability and allows for faster navigation through storage without having to key storage addresses on the CORE\ncommand line.\nPF7 Backward\nScrolls the current CORE display one page backward.\nPF8 Forward\nScrolls the current CORE display one page forward.\nPF9 Caps Off or Caps On\nSets the mode of translation when changing data in the character area of the display. When Caps Off displays, all\ncharacter data on the line is translated to uppercase. When Caps On displays, all character data is accepted as\ntyped. To change from one mode to the other, simply press PF9.\nNote:  Translation to uppercase will not occur if an existing lowercase character on that line would be affected; a\nmessage is issued instead.\nPF10\nUnassigned\nPF11\nUnassigned\nPF12 Structure\nDisplays requested fields in a structured format.\nNOTE\nUse PF13 to PF24  to perform the same functions as PF1 to PF12 .\nAccess Storage from the Menus\nAccess the Main Storage (CORE) menus as follows:\n\u2022From a Source Listing breakpoint or display, enter CORE on the top command line and press Enter.\n\u2022From the Primary Option menu, enter Option 3 Main Storage .\nInterTest for CICS displays the Main Storage Menu.\nAfter completing a CORE menu, press Enter to get a structured display of main storage. From a structured display, press\nEnter if you want the dump format. For more information about  the two formats, see CORE Main Storage Displays.\nThe following table summarizes what you can do from each Main Storage menu.\nMain Storage Option Functions", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "409a2e2bcb3c-1", "text": "The following table summarizes what you can do from each Main Storage menu.\nMain Storage Option Functions\n1. System areas Display, change, or scan: CICS system areas (CSA, OPFL, TCT);\nindividual table entries in the TCT; CICS addresses.\nDisplay, load, or delete program load modules and BMS maps.\nChange functions can be password-protected\n2. Task areas Get storage for a task. Display, change, or scan storage for these\ntask-related CICS areas: CLOT, DWE, JCA, LLA, PLCB, PTA,\nSQLCA, SQLRCODE, RDIIN, SMX, STCA, TACB, TASKENT,\nTCA, TIOA, TSIOA, TWA, USER, XMTXN.\n 1143", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "57dc48b2d0d9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n3. Breakpoint areas Display, change, scan, or verify the following breakpoint-related\ndata: data items, registers, or program locations; special elements\n(includes Breakpoint Message, COBOL BLL cells, COMMAREA,\nFacility Control Area, COBOL TGT, Saved Screen Image, COBOL\nWorking-storage, COBOL Local-Storage, Exec Interface Block,\nTCT User Area); access the Complex data menu to display\nqualified, indexed, and subscripted COBOL data names when at a\nbreakpoint.\nNOTE\nUse additional keywords to access other areas. See the help file for an expanded list.\nPF Key Use at a CORE Menu\nTo access another CORE menu or exit from a CORE menu, use any of the PF keys listed in the following list.\nPF1 Help\nInitiates the InterTest for CICS online help facility.\nPF2\nUnassigned\nPF3 End *\nExits the CORE menu or display. When stopped at a breakpoint, use PF3 or Clear to restore the current\nbreakpoint display. You might need to use the key more than once.\nPF4 Return\nReturns to the Primary Option menu.\nPF5\nUnassigned\nPF6\nUnassigned\nPF7\nUnassigned\nPF8\nUnassigned\nPF9 Complex Data\nFrom the Breakpoint menu, displays the menu for viewing qualified, indexed, and subscripted COBOL data; from\nthe System and Task menus, PF9 is unassigned.\nPF10\nUnassigned\nPF11\nUnassigned\nPF12 Structure\nDisplays requested fields in a structured format.\nNOTE\nPF13 to PF24 perform the same functions as PF1 to PF12, respectively.\nBreakpoint-Related Areas Menu", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "57dc48b2d0d9-1", "text": "Breakpoint-Related Areas Menu\nWhen your task is stopped at a breakpoint, you can display, change, or scan storage relating to the current program or\ntask. From any breakpoint, enter CORE  on the command line. From the Main Storage menu, select 3 Breakpoint areas .\n 1144", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "753c2438c9b0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterTest for CICS responds by displaying one of three Breakpoint menus, depending on whether your program is written\nin COBOL, Assembler, or PL/I.\nUse this menu to do the following tasks:\n\u2022Display storage\n\u2022Dynamically modify storage\n\u2022Verify the contents of storage\n\u2022Search storage (scan) for a data string\nAll storage areas relate to your current task, which is indicated by the number in the upper-right corner of the screen.\nOvertype the task number to access storage relating to another task stopped at a breakpoint.\nDisplay Storage\nUse the COBOL name  or Special element field to specify the starting location (the first byte) of the area to display.\nNOTE\nTo display qualified, indexed, or subscripted COBOL data names, do not enter a COBOL name on this screen.\nInstead, press PF9 to access the CORE=Complex COBOL Data Names screen.\nCOBOL Name\nSpecify a COBOL variable, a data item, or a paragraph name. If you enter a COBOL paragraph name, InterTest for CICS\ndisplays the program code at that location.\nSpecial Element\nSpecify one of the CORE keywords highlighted on the screen to display a special element. Most special elements are\nfamiliar storage areas, such as the COMMAREA and COBOL WORKING-STORAGE. The SSCR (Saved screen image) is\na special InterTest for CICS area that lets you view the last screen displayed by your program before it was stopped at the\ncurrent breakpoint.\nAfter specifying a COBOL name or Special element, press Enter to obtain a structured display in COBOL DMAP\nsequence. To get a dump display, press Enter  a second time.\nExamples", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "753c2438c9b0-1", "text": "sequence. To get a dump display, press Enter  a second time.\nExamples\nTo display the contents of the data item TASKNUM in a structured format, specify the following, and press PF12 .\nCOBOL name: TASKNUM\nTo display the COBOL Working-Storage area for the task currently stopped at a breakpoint, specify the following, and\npress PF12  for a structured display.\nSpecial element: CWK\nTo display the EXEC Interface Block (EIB) in a COBOL DMAP sequence, specify the following, and press PF12 .\nSpecial element: EIB\nDisplay Qualified, Indexed, or Subscripted COBOL Data Names\nTo display qualified, indexed, or subscripted COBOL data names, press PF9  while you are viewing the Breakpoint-\nRelated Areas menu (CORE=Bkpt). InterTest for CICS displays the Complex COBOL Data Names screen. Parentheses\nand commas are not used in the COBOL Complex data menu.\nSpecify a data name, index, or subscript and press Enter.\n 1145", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ed4ed9ce3283-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNote: An alternative method of displaying complex data names is to use a d and the cursor on the Source Listing\nBreakpoint display. This method saves you from having to type long names. To get a Source Listing Breakpoint display,\npress PF4.\nNOTE\nYou cannot mix indexes and subscripts.\nExamples\nThese examples show how to complete the Complex COBOL Data Names menu.\n\u2022To display the subscripted item LEVEL-NAME (SUB-1, SUB-2) where the value of SUB-2 is 30, enter:\nData name: level-name \nOF Data name: \nIndex or subscript1: sub-1 \nIndex or subscript2: 30 \nIndex or subscript3:\n\u2022To display the indexed item TABLE-ITEM (INDX-1, INDX-2, INDX-3), enter:\nData name: table-item \nOF Data name: \nIndex or subscript1: indx-1 \nIndex or subscript2: indx-1\nIndex or subscript3: indx-3\nDynamically Modify Storage\nTo modify storage, use the MOVE line on the Breakpoint-Related Areas menu.\nThe following example gives TASKNUM a value of zero through the entries shown in the MOVE From and To fields.\nNOTE\nInterTest for CICS specifies the field\u2018s length and data type.\n   CA InterTest CORE COMMAND BUILDER  BREAKPOINTRELATED AREAS  (CORE=Bkpt)   \n                                                                                \nSpecify area to be displayed, changed or moved:              Task number: 00136 \n                                                                                \n  COBOL name: ______________________________                                    \n                                                                                \n  Special element: ________  (Enter highlighted keyword)           \n    SSCR Saved screen image   BMSG Breakpoint message       CMAR Commarea", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ed4ed9ce3283-1", "text": "SSCR Saved screen image   BMSG Breakpoint message       CMAR Commarea       \n    FCAR Facility cntl area   EIB  Exec interface block     TUAR TCT user area  \n    BLLS COBOL BLL CELLS      CWK  COBOL WORKING STORAGE    TGT  COBOL TGT \n    LCL  COBOL local storage  DSA  COBOL DSA     \n                                                                                \nSCAN VALUE: _________________________________________           DATA  FORMATS   \nSCAN RANGE: ______             B to scan backwards: _          \n                                                              | P' ' = Packed |\nTo VERIFY and/or CHANGE Data:                                 | X' ' = Hex    | \nExisting data: ______________________________________         | C' ' = Char   |\n     New data: ______________________________________          \n                                                                                \n\u2192  MOVE From zeros_______________________  To   tasknum_______________________\n                                                                               \n \n 1146", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ea1b5c23cbe8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n PF1 Help       2            3 End        4 Return     5            6           \n PF7            8            9 Complex   10           11           12    \nFor COBOL programmers, using this menu is the easiest way to modify storage because it requires no knowledge of data\nformats, hexadecimal values, or internal storage representations.\nDefine Literals\nThe previous screen shows how to move a literal keyword into the To field.\n\u2022Numeric literals are decimal strings of up to 18 digits, optionally preceded by a plus or minus sign.\n\u2022Non-numeric literals are any string of EBCDIC characters enclosed in single quotes.\n\u2022The character string cannot contain a quotation mark.\nTo specify a keyword in the From field, use any of these keywords listed with their actual values.\nZERO(S)\n0\nSPACE(S)\nOne or more blanks (X'40')\nHIGH-VALUE(S)\nOne or more occurrences of the hexadecimal string FF\nLOW-VALUE(S)\nOne or more occurrences of the hexadecimal string 00\nQUOTE(S)\nOne or more occurrences of the hexadecimal string 7D (the EBCDIC representation of a quotation mark)\nALL 'xx' or ALL nn fills the receiving field with a character string or a decimal digit.\nExamples\nThe following examples demonstrate how to fill a field with a literal.\n\u2022To fill the data item FLAG with high-values, enter:\nFrom  HIGH-VALUES      To  FLAG\n\u2022To fill COUNTER with low-values (binary zeros), enter:\nFrom  LOW-VALUES       To  COUNTER\n\u2022To move the three-byte character string ABC into the DEPT field, enter:\nFrom  'ABC'            To  DEPT\n\u2022To fill the field INITIALS with the character string SF, enter:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ea1b5c23cbe8-1", "text": "\u2022To fill the field INITIALS with the character string SF, enter:\nFrom  ALL 'SF'         To  INITIALS\nOther Ways of Changing Storage\nFull-screen edit provides an alternate method of changing storage. It enables you to change any displayed data by\novertyping the hexadecimal or character portions of displayed data with new data. Overwrite any number of displayed\nbytes whenever the bytes are contiguous or separate.\n 1147", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "657080cdd277-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Overtype hexadecimal display fields with the characters A-F and 0-9.\n\u2022Overtype character fields with any character.\n\u2022If you overtype the same data on both the hexadecimal and character display fields, the change made in the character\nfield is done first.\n\u2022When overtyping the character portion, the data is accepted as entered or converted to uppercase, depending on\nwhich mode the CORE transaction is in.\n\u2022Uppercase translation occurs when the PF9 key says Caps Off. No translation occurs when it says Caps On. To\nchange the mode, press the PF9 key before entering any data.\n\u2022If you enter commands together with changes, the changes are made before the commands are executed.\nUse Verify and Change Data\nAnother way of changing storage is to specify the starting byte of the area you want to change using the COBOL name or\nSpecial element field. Enter the new data in the New data field. It is a good idea, though not required, to enter the current\ndata in the Existing data field. If you do, CORE verifies the field contents before making the data change. If the verification\nfails, InterTest for CICS informs you, and the change is not made.\nSpecify existing and new data as follows: as a character string (C'...'), hexadecimal value (X'...'), packed data (P'value'),\na binary fullword (F'value'), or a binary halfword (H'value') where the value is a decimal number optionally preceded by a\nplus (+) or minus (-) sign. If no sign is specified, it defaults to +.\nExample\nThis example changes the CUST-NAME field.\n1.The entries on the following screen show how to change the contents of the CUST-NAME field from JIMMY to\nRONALD.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "657080cdd277-1", "text": "RONALD.\n     CA InterTest CORE COMMAND BUILDER - BREAKPOINT-RELATED AREAS  (CORE=Bkpt)  \n                                                                                \n Specify area to be displayed, changed or moved:             Task number: 00081\n                                                                                \n   COBOL name: CUST-NAME_____________________                                   \n                                                                                \n   Special element: ________   (Enter highlighted keyword)                      \n     SSCR Saved screen image   BMSG Breakpoint message       CMAR Commarea      \n     FCAR Facility cntl area   EIB  Exec interface block     TUAR TCT user area \n     BLLS COBOL BLL cells      CWK  COBOL working storage    TGT  COBOL TGT     \n     LCL  COBOL local storage  DSA  COBOL DSA                                   \n                                                                                \n SCAN VALUE: _________________________________________           DATA  FORMATS  \n SCAN RANGE: ______             B to scan backwards: _         ----------------\n                                                              | P' ' = Packed |\n To VERIFY and/or CHANGE Data:                                | X' ' = Hex    |\n Existing data: C'JIMMY'______________________________        | C' ' = Char   |\n      New data: C'RONALD'_____________________________        -----------------\n                                                                                \n MOVE From ______________________________    To   _____________________________\n                                                                                \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7            8            9 Complex   10           11           12  \n 1148", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c26406020160-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterTest for CICS performs the requested change only if it verifies that the current contents of CUST-NAME are\nJIMMY. If InterTest for CICS does not find JIMMY in CUST-NAME, it will not perform the change and displays a\nmessage to that effect.\n2.To change the contents of CUST-NAME to RONALD regardless of its current contents, enter nothing in the Existing\ndata field, and in the New data field enter:\nExisting Data:\nNew data: C'RONALD'\n3.To confirm the contents of CUST-NAME without changing them, enter nothing in the New data field, and in the Existing\ndata field enter:\nExisting data: C'JIMMY'\nNew Data:\n4.InterTest for CICS informs you whether the prescribed data was found in the designated field.\n5.Combine data formats in a single expression.\nExample\nTo specify New data as the character string KEY-CODE followed by two bytes of binary zeros, enter:\nExisting data:\nNew data: C'KEY-CODE'X'0000'\nSearch for Data\nThe Breakpoint-Related Areas menu also helps you search for data, as shown in the following screen.\nCA InterTest CORE COMMAND BUILDER  BREAKPOINTRELATED AREAS  (CORE=Bkpt)   \n                                                                               \n  Specify area to be displayed, changed or moved:            Task number: 00136 \n                                                           \n    COBOL name: TABLE1________________________                                \n                                                                              \n    Special element: ________  (Enter highlighted keyword)                    \n      SSCR Saved screen image   BMSG Breakpoint message     CMAR Commarea     \n      FCAR Facility cntl area   EIB  Exec interface block   TUAR TCT user area", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c26406020160-1", "text": "BLLS COBOL BLL CELLS      CWK  COBOL WORKING STORAGE  TGT  COBOL TGT    \n      LCL  COBOL local storage  DSA  COBOL DSA  \n                                                               \n  SCAN VALUE: C'STEVE F'_______________________________       DATA  FORMATS   \n  SCAN RANGE: 1000__             B to scan backwards:   \n                                                              | P' ' = Packed | \n  To VERIFY and/or CHANGE Data:                               | X' ' = Hex    | \n  Existing data: ______________________________________       | C' ' = Char   | \n       New data: ______________________________________        \n                                                                                \n  MOVE From ______________________________  To  _____________________________ \n                                                                               \n \n PF1 Help       2            3 End        4 Return     5            6          \n PF7            8            9 Complex   10           11       12  \nTo search for data, perform the following steps:\n1.Specify the starting address of the area to search by making an appropriate entry in the COBOL name or Special\nelement field.\n 1149", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d0fd132b792d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n2.Enter the data string for which you want to search (in field SCAN VALUE). Specify the data in character (C'character\nstring') or hexadecimal (X'hex data') format. Combined formats are allowed, such as:\nC`'KEY-CODE'X'FFFF'\n3.Specify the maximum number of bytes of storage you want searched (in field SCAN RANGE). Specify it in\nhexadecimal format or as a decimal number followed by the letter T.\n4.Search backward from the starting location, enter B in field B to scan backwards. If you leave this field blank, the\ndefault is to search forward.\nExample\nThe previous screen is set up to search for the character string STEVE F, beginning at the program location TABLE1, and\nsearching for 1000 hexadecimal bytes at most.\nAssembler Version of the Breakpoint Areas Menu\nAccess the CORE Breakpoint-Related Areas menu for an Assembler program stopped at a breakpoint. From any\nbreakpoint, enter CORE  on the command line. From the Main Storage menu, select 3 Breakpoint areas .\nUse the CORE=Bkpt Menu screen to display or change storage relating to the task currently stopped at a breakpoint. For\nmore information about any of the fields on this panel, position your cursor in the field and press F1.\nExamples\nTo display the program code at SCANLOOP, enter:\nAssembler Label: SCANLOOP\nTo display the area at displacement TIOADBA from the address in the register equated to TIOABAR, enter:\nAssembler base: TIOABAR    Assembler Label: TIOADBA\nTo display the contents of register 8, enter:\nRegister #: 8\nNOTE\nThe address of the Argument List must be in register 1.\nTo display the second argument in the program's Argument List, enter:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d0fd132b792d-1", "text": "To display the second argument in the program's Argument List, enter:\nArgument: 2\nPL/I Version of the Breakpoint Areas Menu\nAccess the CORE Breakpoint-Related Areas menu for a PL/I program stopped at a breakpoint by typing the command:\nCORE  on any Breakpoint display. From the Main Storage menu, select Option 3 Breakpoint areas to display the Core\nCommand Builder - Breakpoint Related Areas menu.\nUse this screen to display or change storage relating to the task currently stopped at a breakpoint. All fields operate the\nsame as for the CORE=Bkpt menu displayed for a COBOL program stopped at a breakpoint, except you enter a PL/I data\nname in the first field instead of a COBOL data name. For more information about this screen, see Breakpoint-Related\nAreas Menu. For more information about any of the fields on this panel, position your cursor in the field and press F1.\nSystem-Related Areas Menu\nTo display the System-Related Areas menu, enter CORE on a clear screen or from the command line of any source listing\ndisplay or breakpoint. This displays the Main Storage menu. Select option 1 System areas.\n 1150", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ea0fafa8afad-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse the System-Related Areas menu to display or change (subject to password protection) areas of storage relating to\nCICS. You can also load and delete program modules and search for data strings.\nDisplay System-Related Areas\nThe System-Related Areas menu lets you display the following, either from the beginning or from a specified offset or\nscan value:\n\u2022CICS area listed on the menu\n\u2022Any CICS hexadecimal address\n\u2022Single table entry\n\u2022Program load module or BMS map\nSpecify the area to display using one of the following entries:\nCICS AREA\nTo get an entire area or table, specify any CORE key area, such as CSA.\nADDRESS\nTo get a CICS address, specify one to eight hexadecimal digits.\nCICS TABLE entry\nTo get a single table entry, specify the entry next to the appropriate table.\nNOTE\nTo display the entire table, use the CICS AREA field.\nPROGRAM\nTo get a program load module, specify a program name.\nPROGRAM and M\nTo display a BMS MAP, specify the map name in the PROGRAM field, and specify M in the field to the right.\nAfter specifying the system areas for display, specify where to begin the display using the Optional offset and/or Scan\nfields.\nOptional offset\nSpecify a hexadecimal offset or sequence of offsets.\nEach offset must begin with either + (a positive hexadecimal displacement), - (a negative hexadecimal\ndisplacement), @ (an indirect address), or % (an indirect XA address). You can also calculate offsets. For\nexample: @32*4.\nScan Value and Range\nInterTest for CICS searches for the value you specify in the range of hexadecimal or decimal bytes you specify.\nTo get the requested display, press Enter  for a structured display. (Structured displays give field names and main storage", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ea0fafa8afad-1", "text": "contents in DSECT sequence.)\nFrom the structured display, press Enter  for a dump display. (Dump displays give main storage contents with 16\nhexadecimal and character bytes per line.)\nLoad or Delete Program Modules in Main Storage\nTo load a program into main storage, follow these steps.\n1.Type the program name in the CICS AREA field.\n2.Type L in the ENTER L to load, D to delete or M for map field.\n3.Press Enter  for a structured display.\n4.Press Enter  a second time for a dump display.\n 1151", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b9de4272d7bf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo display the program from other than the beginning after it is loaded, follow these steps.\n1.Specify an Optional Offset in the Optional offset field.\n2.Press Enter for a structured display.\n3.Press Enter a second time for a dump display.\nTo delete a program from main storage, follow these steps.\n1.Specify the program name in the To display PROGRAM field.\n2.Type D in the ENTER L to load, D to delete or M for map field.\n3.Press Enter to display the PPT for the program entry to be deleted.\n4.Follow the instructions to confirm the delete.\nChange and Search for Data\nThe change and search functions operate the same as on the Breakpoint-Related Areas menu. For example, the entries\nin the following screen move a value of hexadecimal 600 into the field located at an offset of (hexadecimal) 12 for the file\nPROTSYM.\nCA InterTest CORE COMMAND BUILDER - SYSTEM-RELATED AREAS  (CORE=Syst)    \n                                                                                \n Specify AREA, ADDRESS, TABLE or PROGRAM to be displayed or changed:            \n                                                                                \n   CICS AREA:  ________   CSA, TCT, SIT                  ADDRESS: ________\n                          CWA, DLP, OPFL, ABND                                  \n                                                                                \n   CICS TABLE entry:    PROTSYM_  TCT ____                                      \n                                                                                \n   To display PROGRAM:  ________   ENTER L to load, D to delete or M for map: _\n                                                                                \n Optional offset: +12_________________________________                          \n                                                                                \n Scan value: _________________________________________           Data  Formats  \n Scan range: ______             B to scan backwards: _        -----------------\n                                                              | P' ' = Packed |\n To VERIFY and/or CHANGE data:                                | X' ' = Hex    |", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b9de4272d7bf-1", "text": "To VERIFY and/or CHANGE data:                                | X' ' = Hex    |\n Existing data: ______________________________________        | C' ' = Char   |\n      New data: X'0600'______________________________         -----------------\n                                                                                \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7            8            9           10           11           12\nThe CORE Command Builder Task-Related Areas menu is used to view or modify areas relating to a particular task.\nTo view the menu, select Option 2 Task areas from the Main Storage menu. Use this menu to display, change, or scan\nstorage relating to a specified task for a task waiting at a breakpoint.\nCORE Commands and Advanced Options\nOnce you become proficient with the CORE command builder menu screens, enter CORE commands directly. The\ncommands are easy to learn after using the menus. All CORE commands created from the menus are presented on\nCORE displays as a self-teaching aid.\nExperienced users often find that entering commands is faster than using the menu screens. Enter CORE commands on\na clear screen, or on the command line of a Detailed or Source Listing Breakpoint display, or on any CORE display.\n 1152", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b53fc20b7d41-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe CORE commands are explained in the following sections with some advanced options that are intended only for\nexperienced InterTest for CICS users. If you are an inexperienced CORE user, skim the rest of these topics and reread\nthem when you are more familiar with CORE. For more information about using CORE commands in online help.\nDisplay Main Storage\nTo display storage starting at a specific location, enter the command:\nCORE=location\nSpecify the location as one of the following names:\n\u2022Symbolic name such as a COBOL paragraph name, COBOL data name, COBOL or PL/I statement number, or\nAssembler label that is defined in a program currently at a breakpoint\n\u2022CORE keyword (such as CMAR for the COMMAREA)\n\u2022Hexadecimal address\nTo display storage beginning at a displacement from a particular location, add or subtract the displacement using either of\nthese commands:\nCORE=location+displacement\nCORE=location-displacement\nTo display main storage beginning at a displacement from the area currently displayed, use either of the following\ncommands:\nCORE+displacement\nCORE-displacement\ndisplacement\nIndicates offset of the first byte of the area to be viewed from the first byte of the area currently displayed. The\ndisplacement number is hexadecimal, such as, 100, or decimal, such as, 256T. A number followed by the letter T,\nfor base ten, specifies a decimal number.\nExamples\nThe next examples show a number of CORE commands that are described in following sections:\n\u2022To display the COBOL Working-storage area, enter:\nCORE=CWK\n\u2022To display the data item EMPLOYEE-NUMBER enter the command shown next. The data item is a variable or fixed\nlength.\nCORE='EMPLOYEE-NUMBER'", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b53fc20b7d41-1", "text": "length.\nCORE='EMPLOYEE-NUMBER'\n\u2022To display main storage beginning hexadecimal 10 bytes (or 16 bytes) after the data location TABLE, enter:\nCORE='TABLE'+10\n\u2022To display main storage hexadecimal 100 bytes (or 256 bytes) after the start of the area currently on display, enter:\nCORE+100 or CORE+256T\n\u2022To display the storage area that is hexadecimal 100 bytes (or 256 bytes) before the area currently on display, enter:\nCORE-100 or CORE-256T\n\u2022To display (for Assembler programs) the area at displacement TIOATDL from the address in the register equated to\nTIOABAR, enter:\nCORE='TIOABAR.TIOATDL'\n\u2022To display the CUSTOMER-NUMBER as found in CUSTOMER-FILE-A, enter:\n 1153", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ee1f8afa1e2a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCORE='CUSTOMER-NUMBER OF CUSTOMER-FILE-A'\n\u2022To display the ZIP-CODE in a specific CITY for a specific CUSTOMER enter the command shown next.. Notice that\neach comma must be followed by a space.\nCORE='ZIP-CODE(NAME-IDX, CITY-IDX, ZIP-IDX)'\nThe following table summarizes how you enter locations and displacements in CORE commands. For more information,\nsee CORE Commands for PL/1 Symbolic Programs.\nCOBOL PL/I Assembler\nSymbolic Location 'data name'\n'paragraph name'\n#statement number\nCORE keyword'symbolname\u2018\n# statement number\nCORE keyword'regname.label\u2018 data\nlocation\n'label\u2018 - program location\nor register\nCORE keyword\nSymbolic Displacement 'paragraph name'\n#statement number'label\u2018\n# statement number'label\u2018\nAny Language\nNumeric Location 1- to 8-hexadecimal digits\n1- to 8-decimal digits followed by the letter T\nNumeric Displacement 1- to 6-hexadecimal digits\n1- to 8-decimal digits followed by the letter T\n(number1*number2) or (number1/number2)\nCICS Areas CORE keyword or keyword. fieldname\nElements of a CORE Command\nAn element of a CORE command is the minimum amount of symbols and text sufficient to instruct InterTest for CICS to\nperform a specific CORE function. Each CORE command must contain one complete element, although it can contain\nmore than one. A CORE command element begins with any one of the following symbols:\nEqual Sign (=)\nindicates that an absolute address (entered in hexadecimal), a symbolic address, or a CORE command function\nfollows.\nPlus Sign (+)\nadds the number of bytes specified after it to the address in the storage pointer. This advances the storage pointer", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ee1f8afa1e2a-1", "text": "forward.\nMinus Sign (-)\nsubtracts the number of bytes specified after it from the address in the storage pointer. This moves the storage\npointer backward.\nNOTE\nThe plus and minus signs must be followed by a displacement, specified symbolically, or as a number, a\nmultiplication, or a division.\nAt Sign (@)\nworks like the plus sign. However, after the address is advanced, it obtains the next address from the three right-\nmost bytes of the four bytes found at the current address. The result is indirect addressing. The at sign uses the\nlower 24 bits for addressing.\nPercent Sign (%)\nworks like the at sign, except it uses 31 bit (XA) addressing. It obtains the address from the four bytes of the\nfullword.\n 1154", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e55a5a576581-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nThe at and percent signs must be followed by a displacement specified symbolically, or as a number, a\nmultiplication, a division, or an absolute or symbolic address.\nComma (,)\nindicates that the following text is a further description of the previous element and not the beginning of a new\nelement.\nThere are many elements available to you that are described in subsequent topics. In addition, create new elements that\napply only to your site.\nNOTE\nFor more information about defining new elements by coding CORUCOM macros, see CICS Interfaces and\nCompatibility.\nStorage Pointer\nThe CORE transaction maintains a storage pointer that is adjusted as InterTest for CICS reads and interprets the CORE\ncommands you enter. Before the first input command is processed, this pointer is set to the address of the CICS Common\nSystem Area (CSA).\nAfter you enter a command and the first CORE display opens on your terminal, the storage pointer is set to the address of\nthe first displayed byte. This is the address of the storage pointer that the CORE transaction recognizes when it examines\nthe next command you enter. For example, the following sequence of commands locates the area named (symbolically)\nACCOUNT-NUMBER in the COBOL program whose task is presently waiting at breakpoint, and displays it. Then it adds\nfive to the address of the displayed area and produces another display that begins at the new address.\nCORE='ACCOUNT-NUMBER'\nCORE+5\nInterTest for CICS adjusts the storage pointer for every element found in your commands. InterTest for CICS reads each\ncommand from left to right and executes the first executable element it finds.\nExample\nThe following sequence of commands:\nCORE='CHARGE-ITEMS'\nCORE=SCAN404T,C'FRONT PANEL'\nCORE=CHGC'REAR PANEL'", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e55a5a576581-1", "text": "CORE=SCAN404T,C'FRONT PANEL'\nCORE=CHGC'REAR PANEL'\naccomplishes the same thing as the following single command:\nCORE='CHARGE-ITEMS'=SCAN404T,C'FRONT PANEL'=CHGC'REAR PANEL'\nBoth commands find the field named CHARGE-ITEMS in the program waiting at breakpoint, scan that storage area (which\nis 404 bytes long) for the characters FRONT PANEL, and change these bytes to contain the characters REAR PANEL\ninstead. (This is an example of using an equal sign to indicate the beginning of a new element.)\nThe CORE transaction protects itself against incorrect addresses and recovers from abends caused by store- or fetch-\nprotected addresses. It usually encounters these kinds of addresses during the search for the specified storage area,\nor if you have made a mistake in formulating the CORE command. If this type of error occurs, the message STORAGE\nACCESS ERROR displays.\n=WHERE directive\nThe =WHERE directive is optionally specified after the storage pointer. When this directive is specified, the CORE display\nidentifies what CICS subpool, control block, or program owns the storage.\nExample:\n 1155", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0c1ec99e3c1f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCORE=1234567=WHERE\nCORE Screen Scrolling Commands\nPF7 and PF8 let you scroll backward and forward one page at a time. However, it is possible to scroll forward or backward\nseveral pages at a time.\nTo scroll forward the specified number (1 to 999) of pages, enter:\nCORE=FWDnnn\nTo scroll backward the specified number (1 to 999) of pages, enter:\nCORE=BWDnnn\nExample\nThe command CORE=FWD5 causes CORE to display the storage area five pages ahead of the current area on\ndisplay. Each page is the size of one CORE display, which is hexadecimal 110 or decimal 272 bytes. So, the command\nCORE=FWD5 scrolls the display forward 5 x 272 = 1360 bytes.\nIndirect Addressing\nThe at sign (@) is used to signify indirect addressing in a CORE command. Indirect addressing uses an address stored in\na pointer  field to locate a field for display. The basic command formats used to perform indirect addressing follow.\nTo display main storage beginning with the address stored at the specified location, enter:\nCORE=location@0\nTo display main storage beginning with the address stored in the fullword located at the given displacement from the\nspecified location, enter:\nCORE=loc@disp\nNOTE\nA displacement following the at sign must be zero or positive. Negative displacements are not allowed.\nExamples\nThe following examples show how to use the at sign.\n\u2022Suppose INPUT-RECD-ADDR is the name of the BLL cell used to contain the address of an input record. To display\nthe input record when the COBOL program stops at a breakpoint, enter:\nCORE='INPUT-RECD-ADDR'@0\nThis command has the same effect as:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0c1ec99e3c1f-1", "text": "CORE='INPUT-RECD-ADDR'@0\nThis command has the same effect as:\nCORE='INPUT-RECORD'\n\u2013INPUT-RECORD\nIndicates the data structure addressed by the BLL cell named INPUT-RECD-ADDR.\n\u2022To display the first storage area on the task storage chain, enter:\nCORE=STCA@4\nSTCA\nIndicates CORE keyword for the System Task Control Area. CORE displays the storage area whose address is\nstored in the low-order three bytes of the fullword at STCA+4. The result is that CORE displays the first storage\narea on the task storage chain, which is stored at STCA+4. Pressing Enter repeats the CORE command, letting\nyou run through the entire chain.\n 1156", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5760cfd70dcd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nView Storage for a COBOL or PL/I Program at a Breakpoint\nUse names defined in a COBOL or PL/I program in CORE commands as follows:\n\u2022A COBOL data name, paragraph name, or PL/I symbol name must be in single quotes; qualify, index, or subscript a\nCOBOL data name\n\u2022A number sign (#) must directly precede a statement number\nNotes:\n\u2022If the same data name, such as CUSNAME, is defined more than once in a COBOL or PL/I program, reference\nparticular occurrences using the qualified data name.\n\u2022CORE displays as many bytes as are defined by a symbolic name unless the name is modified by a displacement.\nExample\nTo get a full CORE display (272 bytes of storage) beginning with the data location called CUSNAME, enter the command\nCORE='CUSNAME'+0, not just CORE='CUSNAME'.\n\u2022If you have a data name defined in arrays, specify it like this:\nCORE='NAME-1(X1, X2, X3)'\nExamples\nIn each of the following examples, the symbolic program addresses relate to the program currently stopped at a\nbreakpoint. For more information about using symbolic addresses for a program not stopped at a breakpoint, see Display\nProgram Code for a Program Not at a Breakpoint.\n\u2022To display the data field CUSTNAME in the program (COBOL) that is currently stopped at a breakpoint, enter:\nCORE='CUSTNAME'\n\u2022If you press PF12 , the COBOL structure in a DMAP-defined sequence is displayed. A COBOL structure is defined by\nlevel numbers.\nExample\nA structure is finished when a data item's level number is equal to or less than the level number of the first item in the\nstructure.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5760cfd70dcd-1", "text": "structure.\n\u2022To display the first executable instruction in the named COBOL paragraph of the program currently stopped at a\nbreakpoint, enter:\nCORE='900-END-RTN'\n\u2022To display the data field TASK_TEXT in the program (PL/I) that is currently stopped at a breakpoint, enter:\nCORE='TASK_TEXT'\n\u2022To display the code for the first executable instruction in statement 313 of the program currently stopped at a\nbreakpoint, enter:\nCORE=#313\n\u2022To display the code for the second verb in statement 313 of the COBOL program currently stopped at a breakpoint,\nenter:\nCORE=#313.1\nNOTE\nThe first verb is entered as CORE=#313.0.\n\u2022To display the code for the first executable instruction in the program currently stopped at a breakpoint, enter:\nCORE=#1\n\u2022To display the code for a qualified program name currently stopped at a breakpoint, enter:\nCORE='ACME300N:WS-VARIABLE-FLD'\n 1157", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3523a896bd62-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDisplay Qualified, Variable Length, Indexed, or Subscripted COBOL Data Names\nSpecify qualified, variable length, indexed, and subscripted COBOL data names as follows:\n\u2022To display non-uniquely defined COBOL data names, enter:\nCORE='NAME-1 OF NAME-2'\n\u2022Specify up to seven levels of indexing or subscripting.\n\u2013To display a variable length COBOL data item, such as a data item declared with an 'OCCURS X to Y times\ndepending on Z' clause, enter:\nCORE='DATA-NAME'\n\u2013To display an indexed or subscripted COBOL data item defined in arrays, enter:\nCORE='NAME(X1, X2, X3)'\n\u2022Follow these syntax rules:\n\u2013The data name must be enclosed in quotes.\n\u2013Specify up to seven levels of indexing or subscripting for a data item.\n\u2013Parentheses, ( ... ), indicate the beginning and end of indexing and subscripting.\n\u2013X1, X2, X3 are index names, subscript names or numeric subscript values. If more than one item is specified, a\ncomma and a blank must precede the next item.\n\u2013Do not mix indexing and subscripting in the same command.\nExample\nTo display a specific entry within a table, enter:\nCORE='TABLE(1, SUB-2)' \nTo display the CUSTOMER-NUMBER as found in CUSTOMER-FILE-C, enter:\nCORE='CUSTOMER-NUMBER OF CUSTOMER-FILE-C' \nTo display the ZIP-CODE in a specific CITY for a specific CUSTOMER, enter:\nCORE='ZIP-CODE(NAME-IDX, CITY-IDX, ZIP-IDX)'\nView Storage for an Assembler Program at a Breakpoint", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3523a896bd62-1", "text": "View Storage for an Assembler Program at a Breakpoint\nUse Assembler labels in a CORE command to symbolically address data locations, program locations, or registers as\nshown in the following items.\ndata locations\n'regname.label'\nprogram locations\n'label' (the label value must exceed 15)\nregisters\n'regname' (where the equated value is less than 16)\nExamples\nEach format is shown in the following examples, where the symbolic program addresses relate to the Assembler program\ncurrently stopped at a breakpoint.\n\u2022To display the area at a displacement of TIOADBA from the address in the register equated to TIOABAR, enter:\nCORE='TIOABAR.TIOADBA' \n\u2022Press PF12 to display an Assembler DSECT structure sequence.\n\u2022To display the program code starting at the label SCANLOC, enter:\n 1158", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "88907a07f00d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCORE='SCANLOC'\n\u2022To display the contents of the register equated to TIOABAR, enter:\nCORE='TIOABAR\nUse a Different Module for Assembler Structures\nWhen requesting an assembler structure display, you might encounter a not found condition for one of these reasons:\n\u2022The data area\u2019s DSECT was not printed in the Assembler output listing\n\u2022The requested DSECT is in an area preceded by a PRINT OFF instruction\nTo handle these occurrences, do the following things:\n\u2022Create an Assembler job containing your common DSECT layouts and use the InterTest for CICS post processor step\n\u2022Create one program that contains all of your DSECTS with the PRINT ON option\nThe following considerations are important:\n\u2022Do not specify a LISTER= option\n\u2022You do not have to link-edit the module\n\u2022You do not need a PPT Entry (in CICS) for this module\n\u2022The name of this module must be unique, and it must not be the same as any other module in the Symbolic File\nReference this module online by adding USE=xxxxxxxx to the CORE command. This additional option tells InterTest for\nCICS to access the named module (xxxxxxxx) instead of the program where InterTest for CICS is currently stopped.\n\u2022The data area\u2019s DSECT was not printed in the Assembler output listing\n\u2022The requested DSECT is in an area preceded by a PRINT OFF instruction\nTo handle these occurrences, do the following things:\n\u2022Create an Assembler job containing your common DSECT layouts and use the InterTest for CICS post processor step\n\u2022Create one program that contains all of your DSECTS with the PRINT ON option\nThe following considerations are important:\n\u2022Do not specify a LISTER= option\n\u2022You do not have to link-edit the module", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "88907a07f00d-1", "text": "\u2022Do not specify a LISTER= option\n\u2022You do not have to link-edit the module\n\u2022You do not need a PPT Entry (in CICS) for this module\n\u2022The name of this module must be unique, and it must not be the same as any other module in the Symbolic File\nReference this module online by adding USE=xxxxxxxx to the CORE command. This additional option tells InterTest for\nCICS to access the named module (xxxxxxxx) instead of the program where InterTest for CICS is currently stopped.\nExample\nThe command CORE='R12.DFHTCADS',USE=TESTMAST displays the structure for the USER TCA with the DFHTCAD\nDSECT. The address of the USER TCA is contained in register R12 with its DSECT structure saved in the Symbolic File\nrecords named TESTMAST. If R12 is not defined in your program, InterTest for CICS assumes you meant register 12.\n(The same assumption would be made for R0 through R15.) If the field name, such as DFHTCADS, has not been defined,\nInterTest for CICS searches for the default CICS structure for the field.\nCORE Commands For PL/I Symbolic Programs\nIf you have purchased the PL/I Symbolic Option and are currently stopped at a breakpoint, use CORE to view storage\nassociated with a symbolic PL/I program. The PL/I Symbolic CORE facilities work just like the COBOL Symbolic facilities\nof CORE, with the following differences:\n\u2022There are three PL/I symbolic formats for CORE commands:\n 1159", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e2b53a1ef28d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCORE='symbolname'\nThis command checks to see if the symbol is a label. If it is, the machine code at that location is displayed. If it is not,\nthe definition of the symbol in the most recently activated procedure or block is used to display the current value of the\nsymbol.\nNote:  The most recently activated block, containing a definition of the symbol, need not be the currently executing\nblock.\nCORE='blockname:symbolname'\nCORE='blockname:name1.name2.name3'\nThis command checks to see if the symbol is a label in the qualifying block. If the named block is active, the definition\nof the symbol in that block is used to display the current value of the symbol. If it is not, the blockname is checked to\nverify that it is on the active block chain.\nCORE='symbolname1 >symbolname2'\nThis command displays variables listed as based (*) in the PL/I Cross Reference, where:\n\u2013symbolname1 is assumed to be a pointer that points to an area to be mapped by symbolname2. If it is not a pointer,\nthen the address of symbolname1 is mapped by symbolname2.\n\u2013symbolname2 formats the data to be displayed. In the case of a structure, symbolname2 is assumed to be the\nbeginning of the area pointed to by symbolname1.\nCORE='name1.name2(name3,name4)'\nDisplay array item indicated by the resolution of variables name1 and name2. Up to 15 levels of qualification and\nsubscripting are supported.\n\u2022Controlled variables (CTL) are not supported.\n\u2022Symbolic CORE commands should not be used when a program is stopped at a PROC or BEGIN statement. The DSA", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e2b53a1ef28d-1", "text": "environment is not properly established by PL/I until the first executable statement in a block is actually executed. As\na result, CORE provides unpredictable results if you refer to a symbol that has not been allocated or freed (such as\nBASED variables that are allocated in the block).\n\u2022Like named variables are supported as follows:\n\u2013If two variables with the same name are declared in the same block/procedure, attempting to display these\nvariables with a CORE command requires qualification.\nCORE='name1.name2'\n\u2013If two variables with the same name are declared in different blocks/procedures, display them using the format:\nCORE='blockname:symbolname'\n\u2022Based variables are supported with an unlimited number of levels of basing.\nExample\nSee this sample in the following examples.\nPROC1:  ...;\n     DCL 1    A,\n              2 FIELDB  ...,\n                3 FIELDC ...;\n   SUBPROC:  ...;\n     DCL 1   A,\n             2 FIELDB  ...,\n               3 FIELDC ...;\n   END SUBPROC;\nTo display the variable FIELDB declared in PROC1, enter:\nCORE='PROC1:FIELDB'\nTo display the variable FIELDB declared in SUBPROC, enter:\n 1160", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c4dc018b70c0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCORE='SUBPROC:FIELDB'\nSee the following sample for the next example.\nDCL   Q PTR;\nDCL   R PTR;\nDCL   Z BASED(Q);\nTo display Z using R as the pointer, code the CORE command as follows:\nCORE='R >Z'\nDisplay Program Code for a Program Not at a Breakpoint\nWhen a symbolic name is used in a CORE command, CORE must know in which program the name or label is defined. If\nthe program is currently stopped at a breakpoint, CORE assumes that program will be displayed; otherwise, the following\ncommand format must be used:\nCORE=PGM=progname+symbolic name\nExample\nTo display the code generated in the COBOL paragraph named EDIT DATA in the resident program named ORDENTRY,\nwhich is not at a breakpoint, enter:\nCORE=PGM=ORDENTRY+'EDIT DATA'\nThis command adds the displacement of EDIT DATA to the address of the first byte of the program ORDENTRY and\ndisplays main storage starting at that address. If the program is not resident, specify the following command to load the\nprogram into storage:\nCORE=LOAD=progname\nBreakpoint Commands\nCertain CORE commands are applicable only when a task is stopped at a breakpoint. These commands let you do the\nfollowing tasks:\n\u2022Display storage areas whose contents are meaningful only when task execution halts at a breakpoint\n\u2022Display the screen as it existed before the breakpoint or restore the breakpoint display\n\u2022Dynamically acquire main storage\n\u2022Change the values of program data items using COBOL like MOVE commands\nDisplay Storage Related to a Task at a Breakpoint\nThe following list shows the commands used to display an area of main storage whose contents are meaningful only when\na task stops at a breakpoint.\nCORE=ARGnn", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c4dc018b70c0-1", "text": "a task stops at a breakpoint.\nCORE=ARGnn\nDisplays argument nn on the breakpointed program's argument list, where nn is a decimal number from 0 99. The\naddress of the argument list must be in register 1.\nCORE=BLLnn\nDisplays the BLL cell with relative number nn, where nn is a decimal number from 0 99. The first BLL cell is\nspecified in the CORE command as BLL1, the next as BLL2, and so on.\nCORE=BLLS\nDisplays the COBOL program's BLL cells.\n 1161", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fa23a338ac55-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCORE=BLXnn\nDisplays the BLX (external program storage) cell with relative number nn, where nn is a decimal number from 0\n99. The first BLX cell is specified in the CORE command as BLX0, the next as BLL1, and so on.\nCORE=BLXS\nDisplays the COBOL program's BLX (external program storage) cell pointers.\nCORE=CLOT\nDisplays the CICS Life Of Task block. This area exists only after the first SQL CALL in your program (z/OS only).\nCORE=CMAR\nDisplays the CICS EXEC Communication Area (DFHCOMMAREA) owned by the breakpointed command level\nCICS task.\nCORE=CURR\nDisplays the current instruction about to be executed when the task was halted at a breakpoint.\nCORE=CWK\nDisplays the breakpointed COBOL program's WORKING STORAGE.\nCORE=DSA\nDisplays the breakpointed program\u2019s Dynamic Storage Area.\nCORE=EIB\nDisplays the EXEC Interface Block owned by the breakpointed command level task.\nNote:  When using the Integrated CICS translator of Enterprise COBOL for z/OS, this command will not work\nunless the NOLINKAGE translator option or the ADATA compiler option is specified.\nCORE=EIS\nDisplays the EXEC Interface Structure owned by the breakpointed command level task.\nCORE=FCAR\nDisplays the Facility Control Area. This is the TCT entry for a terminal oriented task or the DCT entry for a task\ninitiated by a transient data trigger level.\nCORE=FLPT\nDisplays the 16 doublewords where floating point registers 0-15 were saved.\nCORE=ITBE\nDisplays the instruction that was to be executed when the task halted at the breakpoint.\nCORE=LCL\nDisplays the breakpointed COBOL program\u2019s LOCAL-STORAGE.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fa23a338ac55-1", "text": "CORE=LCL\nDisplays the breakpointed COBOL program\u2019s LOCAL-STORAGE.\nCORE=MXR\nDisplays the current value of the counter for CICS requests.\nCORE=MXS\nDisplays the current value of the counter for the amount of CICS storage acquired by the program.\nCORE=PREV\nDisplays the last executed Assembler instruction.\nCORE=PREVCORE=RDIIN\nDisplays the Application Invocation Parameter List. The task must have issued an SQL CALL for CORE=RDIIN to\nfunction (z/OS only).\nCORE=REGS\nDisplays the 16 fullwords where registers 0 15 are saved.\nCORE=Rnn\nDisplays the contents of register nn prior to the breakpoint.\n 1162", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "69f709748fa5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCORE=SQLCA\nDisplays the SQL Communications Area. This area contains data only after the first SQL call in your program (z/\nOS only).\nCORE=SQLRCODE\nFor z/OS only: Displays the contents of SQLCODE as a decimal number and converts this value into its\nassociated text message. Explanations of any SQL warning codes are also displayed.\nFor a DSNC abend, the failure code, the failing DB2 subcomponent identifier, and the subsystem termination\nreason code are displayed with explanations of the failure code and the subsystem identifier.\nCORE=SSCR\nDisplays the last CICS screen displayed by your program before it stopped at the current breakpoint.\nCORE=TAL\nDisplays the current value of the TALLY counter.\nCORE=TGT\nDisplays the COBOL program's Task Global Table.\nCORE=TIOA\nDisplays the first Terminal I/O Area chained to the breakpointed task.\nCORE=TUAR\nDisplays the saved user area in the terminal table (TCT) entry of the breakpointed task. Use this keyword only if\nSTUAR=YES was specified when InterTest for CICS was installed.\nCORE=VCTR\nDisplays the 32 quadwords where vector registers 0-31 were saved.\nCORE=WKAR\nDisplays the InterTest for CICS Work Area of the breakpointed task.\nDisplay Storage for an Inactive COBOL Program at a Breakpoint\nThe following list shows the command that can be used to display areas of main storage for both inactive and active\nCOBOL programs when at a breakpoint.\nCORE=BLLnn=program\nDisplays the BLL cell for the program specified on the command, where nn is a decimal number from 1 99. The\nfirst BLL cell is specified in the CORE command as BLL1, the next as BLL2, and so on.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "69f709748fa5-1", "text": "CORE=BLLS=program\nDisplays the COBOL program's BLL cell storage pointers.\nCORE=BLXnn=program\nDisplays the BLX (external program storage) cell for the program specified on the command, where nn is a\ndecimal number from 0 99. The first BLX cell is specified in the CORE command as BLX0, the next as BLX1, and\nso on.\nCORE=BLXS=program\nDisplays the BLX cells for the external storage for the program specified on the command.\nCORE=CWK=program\nDisplays the COBOL working storage for the program specified on the command.\nCORE=TGT=program\nDisplays the Task Global Table for the program specified on the command.\nRestore the Screen at a Breakpoint\nTo display the screen image as it existed prior to the breakpoint, enter:\n 1163", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "33618ee307ac-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCORE=SSCR\nTo return to the CORE command after displaying the screen image, press Clear .\nDynamically Acquire Main Storage at a Breakpoint\nTo dynamically acquire main storage when a program is at a breakpoint, enter:\nCORE=GETM,L=len,CL=type,INIT=xx\nL=len  is mandatory. The value of len is the same as the one entered with the parameter LENGTH(...) in a CICS GETMAIN\ncommand. It could be a hexadecimal value or a decimal followed by the letter T.\nCL=type  is optional and specifies the type of storage to be acquired. CL=USER acquires user class storage and\nCL=TERM acquires terminal class storage (TIOA). If this parameter is omitted, CL=USER is assumed.\nINIT=xx  is optional. The hexadecimal digits xx specify the character used to initialize the storage area. The default is\nbinary zeroes.\nThis command is equivalent to an EXEC CICS GETMAIN.\nWhen a CORE=GETM command executes, InterTest for CICS displays the acquired area beginning with its eight byte\nStorage Accounting Area (SAA). The address of the acquired area must be saved in a register where the program expects\nto find it.\nThe SET command is useful to load the address. Note that if the address is placed in a COBOL BLL cell, the address\nmust be adjusted up 8 bytes to point past the SAA. If a COBOL program has loaded the contents of the BLL cell into a\nregister, the register must also be loaded.\nExamples\nThe SET command is expressed as follows:\nCORE+8=SET=BLL1\nCORE=SET=REG6\nCORE=SET='SSA POINTER'\nCOBOL Like MOVE Command at a Breakpoint", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "33618ee307ac-1", "text": "CORE=SET='SSA POINTER'\nCOBOL Like MOVE Command at a Breakpoint\nThe MOVE command is valid for COBOL and PL/I programs stopped at a breakpoint.It has two formats:\n\u2022To move the contents of field 1 to field 2, enter:\nCORE=MOVE field 1 TO field 2\n\u2022To move a literal to a field, enter:\nCORE=MOVE literal TO field 2\n\u2022field 1\nNames the sending area.\n\u2022field 2\nNames the receiving area. Both fields must be defined in the program. Do not enclose either field name in quotes.\nQualify, index, or subscript either field.\n\u2022literal\nIndicates a fixed point numeric value, a string of EBCDIC characters, or a keyword, such as ZERO or SPACES.\n\u2022fixed point literal\nIndicates a string of up to 18 decimal digits with an optional leading plus, +, or minus sign, . (No sign defaults to +.)\nEmbedded decimal points are not allowed.\nSpecify any string of characters from one to 120 EBCDIC characters enclosed in quotes as a literal. A quotation mark\ncannot be part of the character string defining the literal.\n 1164", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5f8463519f1d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUse the following keywords as literals:\nZERO\nNumeric value 0\nSPACE\nOne or more blanks (X'40')\nHIGH-VALUE\nOne or more occurrences of X'FF'\nLOW-VALUE\nOne or more occurrences of X'00'\nQUOTE\nOne or more occurrences of the quotation mark (X'7D')\nNOTE\nAppend the letter S to any of the previous keywords without changing its meaning. For example, the command\nMOVE SPACES TO CUSTNAME is equivalent to MOVE SPACE TO CUSTNAME.\nTo repetitively fill a field with a particular character string or decimal digit, precede the literal with the keyword ALL followed\nby a space. For example, ALL 'XYZ' or ALL 9. The literal following ALL is any valid EBCDIC character string enclosed in\nquotes. If the literal following ALL is a numeric, it must be a single unsigned decimal digit.\nThe MOVE command handles only certain data types and makes any required conversions from one data type to another.\nThe conversions follow the examples specified in the IBM Full American National Standard COBOL Reference Manual .\nThe fields are checked for numeric content, as needed.\nA list of supported data types and the corresponding conversion rules follows:\nGROUP\nData is left justified with no conversion. This type of move is made if either the sending or receiving field has\ngroup data.\nDISPLAY\nData conversion is performed with left justification.\nDISPLAY NUMERIC\nData conversion is performed with right justification.\nCOMP-3\nData conversion is performed.\nCOMP\nData conversion is performed.\nALPHANUMERIC EDITED\nHandled as DISPLAY, but without editing.\nNUMERIC EDITED\nHandled as NUMERIC, but without editing.\nDisplay Task Owned Areas", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5f8463519f1d-1", "text": "NUMERIC EDITED\nHandled as NUMERIC, but without editing.\nDisplay Task Owned Areas\nTo display areas of storage that are related to a particular task, use the keywords in the following table. Unless you specify\notherwise, the areas displayed relate to the task that created the most recent breakpoint display.\nUse the command form:\nCORE=Area Displayed\nArea Displayed is one of the following CORE keywords:\n 1165", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eab048dfd67a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDWE\nTop Deferred Work Element\nJCA\nTop Journal Control Area\nLLA\nTop Load List Area\nPLCB\nProgram Logical Level Control Block\nPTA\nProgram Transaction Area Control Block\nSMX\nStorage Manager Transaction Control Block\nSTCA\nSystem portion of TCA\nTACB\nTop Task Abend Control Block\nTASKENT\nKernel Domain Task Definition Control Block\nTCA\nUser portion of TCA\nTWA\nTWA portion of TCA\nUSER\nTop USER class storage area\nXMTXN\nTransaction Manager Transaction Definition Control Block\nSet the Task Number in a CORE Command\nThe commands listed in the previous table display the task area relating to the task that most recently sent a breakpoint\ndisplay to the terminal screen. To display storage for a different task, you must enter a task number in the CORE\ncommand. The new task number remains in effect until you change it or a new breakpoint display is received at the\nterminal. The task number is in the upper right corner of CORE displays.\nTo specify the task number to be used by CORE in accessing task related areas, enter:\nCORE(task no)\nTo reset the task ID to the task currently waiting at a breakpoint, enter:\nCORE(*)\nUse this command if there is just one task currently at a breakpoint at the terminal.\nExamples\nThese examples show how to display storage for non breakpointed tasks.\n\u2022To display the top USER-class storage area for task 2145, enter:\nCORE(2145)=USER\n 1166", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2b89659eda08-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSubsequent task related commands refer to task 2145 until the task number is changed in a CORE command or until a\nnew breakpoint occurs.\n\u2022To display the user portion of the TCA for the task currently at a breakpoint, enter:\nCORE(*)=TCA\nDisplay Any CICS Control Area Structure in the Symbolic File\nUse the following command to display any CICS control area in the Symbolic File, and to display the structure of the first\nentry in a control area:\nCORE='CICS CONTROL AREA NAME'\nExamples\nThese examples demonstrate how to display entries located on the CSA.\n\u2022To display the structure at the first entry in a control area, enter:\nCORE=CSA\n\u2022To display the structure at a specific entry (CSADATFT) in the CSA, enter:\nCORE=CSA.CSADATFT\nDisplay System-Related Areas\nThe following CORE keywords display areas of main storage that contain system related information:\nABND\nKernel Error Data Block (CICS 3.2 and higher only)\nCSA\nCommon System Area\nCWA\nCommon Work Area\nDLP\nDL/I Interface Parameter List\nFCT\nFirst entry of the File Control Table\nFILE=filename\nFCT entry for the file specified by filename\nMAP=mapname\nDisplays a BMS Map\nMAP=name(mapset)\nDisplays a BMS Map belonging to the mapset\nOPFL\nOptional Features List of CICS\nPGM=progname\nArea occupied by the named program\nSIT\nCICS System Initialization Table\nTCT\nTerminal Control Table address list\n 1167", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "757561c50e5d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTERM=termid\nTCT entry for the terminal specified by termid\nTERM=*\nTCT entry of the terminal where CORE is currently executing\nChange the Contents of Main Storage\nUse the following commands to change the contents of main storage. However, use CORE menus to accomplish the\nsame functions.\nThe following commands move data into a specified storage area:\nMOVE\nUsed when a COBOL or PL/I program is stopped at a breakpoint. This command was previously described in\nCOBOL Like MOVE Command at a Breakpoint.\nCHG\nUsed to specify that data be moved into main storage at the current or specified main storage location.\nMOVEIN\nUsed to move data from one location in storage to another.\nSET\nUsed to load an address into the low order three bytes of a specified fullword.\nThe CHANGE Command (CHG)\nThe CHG command is used to move new data into main storage. The new data is specified in the command after the\nkeyword CHG in character, hexadecimal, packed, or binary format. This command has two formats:\n\u2022To move a data string into the main storage area that begins with the first byte of the current CORE display, enter:\nCORE=CHGdata\n\u2022To move data into main storage beginning at the specified location, enter:\nCORE=loc=CHGdata\nSpecify the data in a CHG command using any of the following formats:\n\u2022C'chardata' for character data\n\u2022X'hexdata' for hexadecimal data\n\u2022P'value' for packed decimal data\n\u2022F'value' for a binary fullword\n\u2022H'value' for a binary halfword preceded by a plus or minus sign\nReplace 'value' with a decimal number, optionally preceded by a plus (+) or minus ( ) sign.\nExamples", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "757561c50e5d-1", "text": "Examples\nTo place 123 in the first three bytes of storage on display, enter:\nCORE=CHGC'123'\nTo perform the same function as in Example 1, enter:\nCORE=CHGX'F1F2F3'\nTo place the characters 123 in the first three bytes of the data field ACCT NUM defined in the program currently stopped\nat a breakpoint, enter:\nCORE='ACCT NUM'=CHGC'123'\n 1168", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7320c0db6621-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo move the two byte packed decimal value of 100 into the first two bytes of the data field QUANTITY, enter:\nCORE='QUANTITY'=CHGP'100'\nWhen entering an apostrophe as part of character data, the apostrophe must be repeated.\nTo move the name O'HARA into the data area CUSNAME, specify:\nCORE='CUSNAME'=CHGC'O\"HARA'\nEnter any combination of hexadecimal and character data.\nTo change the value of RECKEY to the name SMITH followed by two bytes of binary zeroes, specify:\nCORE='RECKEY'=CHGC'SMITH'X'0000'\nBit Manipulation\nAppending OC, NC, or XC after the data string lets you perform one of the following logical operations to the contents of\nmain storage:\n\u2022OC to OR the data in the command to storage\n\u2022NC to AND the data in the command to storage\n\u2022XC to EXCLUSIVE OR the data in the command to storage\nExamples\nThe following examples demonstrate how to manipulate main storage bits.\n\u2022To set the high order bit of the first byte on the current CORE display to 1, enter:\nCORE=CHGX'80'OC\n\u2022To set the high order bit of the first byte on the current CORE display to 0, enter:\nCORE=CHGX'7F'NC\n\u2022To reverse all the bits of the first byte on the current CORE display, enter:\nCORE=CHGX'FF'XC\nVerify Storage Before a Change\nUse the VER command with a CHG command to prevent an incorrect change to storage. This command verifies that the\nspecified data is stored at the specified location. Specify the VER command as follows:\nCORE=loc=VERdata\nThe data in a VER command is specified using the following formats:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7320c0db6621-1", "text": "CORE=loc=VERdata\nThe data in a VER command is specified using the following formats:\nC'chardata'\ncharacter data\nX'hexdata'\nhexadecimal data\nExample\nVerify that the NAME field contains JIM before changing it to JAY. If JIM is not in the NAME field, the change command is\nrejected, enter:\nCORE='NAME'=VERC'JIM'=CHGC'JAY'\nMove Data with the MOVEIN Command\nThe MOVEIN command, which lets you move data, has two formats:\n 1169", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ec28054a8bcf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022To move data from the FROM location to the area currently displayed, enter:\nCORE=MOVEIN,L=len,FROM=location\n\u2022To move data from loc2 to loc1, enter:\nCORE=loc1=MOVEIN,L=len,FROM=loc2\nThe length parameter, L=len, specifies the number of bytes to be moved. The maximum value for len is decimal 256,\nspecified as 256T.\nExample\nTo move twenty (hexadecimal 14) bytes of data from NEWNAME into CUSTNUM, enter:\nCORE='CUSTNUM'=MOVEIN,L=14,FROM='NEWNAME'\nScroll an Address with the SET Command\nSpecify the SET command to set an address as follows:\nCORE=addr1=SET=addr2\nThe address specified by addr1 is placed into the three low order bytes of the fullword whose address is given by addr2.\nThe high order (left most) byte is filled with binary zeroes.\nExamples\nThese examples demonstrate how to use the SET command.\n\u2022To fill the fullword at F12DE8 with the data 00234ABC, enter:\nCORE=234ABC=SET=F12DE8\n\u2022To put the starting address of the program named PROGRM1 into the fullword that is at a displacement of 2C from the\nbeginning of the program named PROGRM2, enter:\nCORE=PGM=PROGRM1=SET=PGM=PROGRM2+2C\nScan Main Storage\nThe SCAN and SCAB commands search main storage for specified data. SCAN searches forward through storage, and\nSCAB searches backward. The command formats let you search from the current CORE display or from a specified\nlocation.\n\u2022To begin a search at the first byte of the current CORE display, enter:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ec28054a8bcf-1", "text": "location.\n\u2022To begin a search at the first byte of the current CORE display, enter:\nCORE=SCANrange,data\nor\nCORE=SCABrange,data\n\u2022To begin a search at the location specified as loc, enter:\nCORE=loc=SCANrange,data   \nor\nCORE=loc=SCABrange,data\nThe search terminates when the first occurrence of the specified data is found or the number of bytes specified in the\nrange have been scanned. Specify the range as a hexadecimal number or a decimal number followed by the letter T.\nExamples\nThese examples show how to search for and replace data in main storage.\n\u2022To search for the string STEVE beginning at the location TABLE1, enter:\nCORE='TABLE1'=SCAN1000T,C'STEVE'\n 1170", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f9dd73b287be-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe search for STEVE proceeds forward for a maximum of (decimal) 1000 bytes. If STEVE is not found a message\ndisplays.\n\u2022To search for STEVE starting at TABLE1, and to replace STEVE with the character string CHRIS, enter:\nCORE='TABLE1'=SCAN1000T,C'STEVE'=CHGC'CHRIS'\nNote:  This command only replaces the first occurrence of STEVE with CHRIS.\nLoad and Delete Programs or Displaying BMS Maps\nTo load and delete programs and to display BMS maps, use the CORE commands specified following.\n\u2022To load the named program or increase its current use count by 1, enter:\nCORE=LOAD=progname\n\u2022To inform CICS that the named program can be deleted or to decrease its current use count by 1, enter:\nCORE=DLTE=progname\n\u2022To display the named BMS map, enter:\nCORE=MAP=progname\nIf a program name contains any of the special characters, @, #, or $, you must enter the program name as C\u2019progname\u2019.\nFor example, to load the program named FIND#7 into main storage, enter:\nCORE=LOAD=C'FIND#7'\nDump Main Storage\nUse either of the two formats shown following to dump main storage. The dump is in the format of a partial CICS\ntransaction dump, and is written to the CICS dump data set.\n\u2022To create a dump of the area currently on display, enter:\nCORE=DUMP,L=len,ID=code\n\u2022To create a dump of the area beginning at the specified location, enter:\nCORE=loc=DUMP,L=len,ID=code\nL=len\nSpecifies the size of the dump. Specify as a hexadecimal number or a decimal number followed by a T. This", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f9dd73b287be-1", "text": "parameter is optional and, if omitted, defaults to the size of a CORE display.\nID=code\nSpecifies a dump code. If omitted, the default is CORE.\nFollowing the dump ID, include an optional message in the DUMP command. A blank must separate the message from\nthe command. The entire DUMP command and any messages are included in the dump.\nExample\nTo produce a dump of the storage area that was on the CORE display screen at the time the command was entered,\nenter:\nCORE=DUMP,ID=MY01 BAD ACCT NUMBER\nThe dump ID will be MY01, and the message BAD ACCT NUMBER displays in the dump.\nChain CORE Commands\nIn general, if you need to execute several CORE commands to achieve a desired result, chain the commands together\ninto one command. The format for chaining commands together is:\nCORE=command1=command2=...=commandn\n 1171", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "677c4b4479fc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThis is equivalent to sequentially executing the commands as follows:\nCORE=command1\nCORE=command2\nCORE=commandn\nExamples\nThe following examples demonstrate how to join CORE commands:\n\u2022To search the third storage area on the task's storage chain, enter:\nCORE=STCA@4@4@4=SCAN2000,C'RONALD'=MOVEIN,L=6,FROM=256ABC\nIf the character string RONALD is found within hexadecimal 2000 bytes, InterTest for CICS replaces it with whatever is\nat address 256ABC.\n\u2022To get a one hundred byte storage area for the task that is waiting at a breakpoint, and set the address of the first byte\n(after the eight byte long Storage Accounting Area) into the fullword at the address in register 6, enter:\nCORE=GETM,L=100T+8=SET=R6@0\nThe CALC Option\nWhen viewing a CORE display, overtype the TransID CORE with CALC to use the basic hexadecimal calculator function\nof InterTest for CICS. The CALC function displays the hexadecimal and equivalent decimal number for the given value\non the bottom line of the screen. The current CORE display is not affected. Return to the CORE transaction by replacing\nCALC with CORE.\nNOTE\nWhen using the CALC function, the letter T, for base ten, must follow decimal numbers.\nExamples\nThe following examples demonstrate how to display hexadecimal and decimal values of specified numbers.\n\u2022To display the hexadecimal value of 200 and the decimal value of 512 on the bottom line of the screen, enter:\nCALC=200\n\u2022To display the decimal value of 512 and the hexadecimal value of 200 on the bottom line of the screen, enter:\nCALC=512T", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "677c4b4479fc-1", "text": "CALC=512T\n\u2022To display the hexadecimal value of 202 and the decimal value of 514 on the bottom line of the screen, enter:\nCALC=0+(10*16T)+(16T*16T)+2\nConvert PL/I Statement Numbers into Displacements\nPL/I users who want to set breakpoints using hexadecimal offsets (displacements) need to use an offset calculated from\nthe beginning of the main control section. There are two ways to get such offsets:\n\u2022Use the offset given in the Assembler like listing provided by the source listing option of the PL/I compiler. However,\nthis listing is rather long.\n\u2022Use the offset listed in the Tables of Offsets and Statement Numbers portion of a PL/I listing for a statement. This offset\nis relative to the beginning of the machine code for the internal procedure. Then, calculate the offset relative to the\nmain control section using the following CORE command:\nCORE=PGM=pgmname;+'procname'+offset\n\u2022pgmname\nIndicates the PPT ID of a PL/I program module. It must be followed by a semicolon and a plus sign.\n\u2022procname\nIndicates the name of an internal PL/I procedure as listed in the Tables of Offsets.\n\u2022offset\nIndicates a hexadecimal offset for a statement as listed in the Tables of Offsets and Statement Numbers.\n 1172", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aad9ffcd928b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThis command accepts the offset for a statement as listed in the Tables of Offsets, and returns the hexadecimal value\nof the offset of that statement as counted from the beginning of the main control section. Use the returned value to set\na breakpoint or to request a CORE display of the program code at that location.\nExamples\nAn offset must be specified in the command. (Specify 0 as +0.)\nCORE=PGM=TESTPROG;+'EDIT INPUT'+10\nThe named program must reside in main storage. If it does not, use the following command to load it:\nCORE=LOAD=pgmname\nWhen you are finished, use the following command to remove the program from main storage:\nCORE=DLTE=pgmname\nCORE(NNNNN)=BMSG\nUse the CORE(NNNNN)=BMSG command to view a breakpoint display that is currently being displayed on another\nterminal. By replacing NNNNN with the task number of the breakpointed task, you can view the breakpoint display already\nshowing for that task, and you will be able to display and modify storage related to that task as if your terminal was the\nbreakpoint terminal. You will not be able to resume execution or abend the task at the breakpoint (this must be done from\nthe actual breakpoint terminal). Use the CNTL=DISC command from the command line to disconnect from the breakpoint\ndisplay.\nAccessing Auxiliary Storage FILE\nOption 4 Auxiliary Storage, from the Primary Option Menu, invokes the InterTest for CICS FILE transaction. This\nFILE transaction lets you display, add, change, and delete records in VSAM and BDAM files, DL/I, DB2, and SQL/DS\ndatabases, temporary storage, and transient data.\nThe FILE transaction is very useful when you want to update records or create test data. Use FILE at:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aad9ffcd928b-1", "text": "\u2022Any time, even when the rest of InterTest for CICS is inactive\n\u2022A breakpoint to inspect and modify data values and generate more test data\nThe changes you make to a file or database are always permanent, rather than dynamic, changes.\nFILE Capabilities\nUse FILE to perform the following functions. Each main function is an option on the Auxiliary Storage Menu.\nNOTE\nThe functions you perform depend on your security authorization.\n\u2022Files (VSAM and BDAM)\n\u2013View, add, update, and delete records\n\u2013Browse a file\n\u2013Search for data\n\u2013Mass insert records into a VSAM file\n\u2022DB2 and SQL/DS  Databases\n 1173", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b89a5c0aa2a3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2013View a table\n\u2013Update columns in a table\n\u2013Delete rows from a table\n\u2013Insert a row in a table\n\u2013Issue other SQL commands, including CREATE, ALTER, DROP, COMMENT ON, LABEL ON, GRANT, and\nREVOKE\n\u2022DL/I Databases\n\u2013Retrieve segments\n\u2013Add, update, and delete segments\n\u2022Transient Data\n\u2013Retrieve a transient data record\n\u2013Add a transient data record\n\u2013an intrapartition data queue\n\u2022Temporary Storage\n\u2013View or add a temporary storage record\n\u2013View or add a temporary storage queue record\n\u2013Search a temporary storage queue for data\n\u2013Purge a temporary storage queue\nIn addition to the previous listed functions, use FILE to perform tasks that would otherwise require specially written\nprograms.\nExample\nUse FILE to do the following tasks:\n\u2022Copy a record from one file to another\n\u2022Create test data from production files\nFILE performs these tasks because it retains retrieved record and segment data in its own WORK AREA.\nThe InterTest for CICS FILE transaction is comprehensive. It enables you to perform interactively any function that is\nsupported by CICS File Control and DL/I, and most DB2 functions. FILE uses CICS services exclusively; it does not use\nthe operating system's data access methods directly.\nRemote VSAM File and Temporary Storage Support\nUse FILE to access and update remote VSAM files and temporary storage. FILE supports the following files and storage:\n\u2022All VSAM file types\n\u2022Auxiliary and main temporary storage queues\n\u2022Temporary storage queue names of all valid lengths. If you are running CTS Version 1.3, queue names are up to 16\nbytes or 32-hexadecimal characters long.\nNo additional user input is required.\nNOTE\nBoth sites must be at InterTest for CICS r4.2 or higher.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b89a5c0aa2a3-1", "text": "NOTE\nBoth sites must be at InterTest for CICS r4.2 or higher.\nFILE Work Area\nFILE keeps record or segment data in its own work area when performing an I/O operation. An input operation , such as a\nREAD, places the requested data record or segment in FILE's work area and displays it on the screen.\nConsider the following operations when working with the FILE work area:\n 1174", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "542e0f76a8cc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022A successful input operation overwrites data currently in the work area.\n\u2022A successful output operation leaves all data in the work area intact. Reuse the contents of the work area for any\nnumber of consecutive output operations without having to reacquire the same data.\n\u2022Changing data in the work area does not affect the contents of the accessed data structure (file, database, temporary\nstorage, transient data) until a successful output operation is performed.\n\u2022The contents of the work area can exceed the display capacity of the terminal screen. Display any portion of the work\narea by entering the location in the LOC field or using PF keys. For more information about the LOC field, see Dump\nFormat.\nThe FILE Transaction and Menus\nThe tasks described here apply to any type of data organization. Tasks specific to a particular type of data organization\nare discussed in the appropriate section.\nAccess File Facilities\nUse the following methods to access the File facilities of InterTest for CICS.\n\u2022From CICS, enter the transaction code FILE .\n\u2022From the Primary Option Menu, select Option 4 Auxiliary Storage.\n\u2022From any Source Listing display, breakpoint, or CORE display, enter FILE  on the command line.\nThe Auxiliary Storage Menu opens.\nTo use the Auxiliary Storage menu, follow these steps:\n1.Use the Option field to select the auxiliary storage type you want to view.\n2.Optionally, enter one or more specific or generic names on the bottom fields of the menu. Generic names can include\nthe masking characters * and +. Use * to indicate a string of any length, + to indicate a single character.\n3.Press Enter  to display a selection list of the files and queues that meet your selection criteria.\nThe File Selection List", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "542e0f76a8cc-1", "text": "The File Selection List\nUse the File Selection list to select the specific file or queue you want to access. Type an s next to the File entry to select\nit for display.\nNOTE\nIn a list spanning multiple pages, use the command LOCATE filename  to position the display to the desired file.\nFor a list of the supported commands available from all InterTest for CICS Selection List displays and the standard PF Key\ndefinitions.\nInitial File Display\nThe Initial File Display screen has three distinct areas:\n\u2022The header area contains the following:\n\u2013Type of data organization (DATATYPE)\n\u2013Record or segment to be retrieved\n\u2013Format in which the data is to be displayed (FORMAT)\n\u2022Record display area\n\u2022Record information area displays the information about the file or PCB information for a DL/I database and functions\nthat can be performed, such as READ, BROWSE, and UPDATE etc against the FILE.\n 1175", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "054b512ab04a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nFILE uses different screens for accessing and displaying DB2 and SQL/DS databases. For more information,\nsee DB2 and SQL/DS Databases.\nSpecify a File or Database\nFollow this procedure to specify a file or a database:\n1.Enter a file ID in the FILEID field, or the DL/I database identifiers in the PSB and DBD fields. No specification is\nneeded for a DB2 or SQL/DS database.\n2.If the default value in the DATATYPE field is not correct for the type of data organization you want to access, use PF6\nto change it or replace the value with one of the following:\nFC for VSAM or BDAM files\nTS for Temporary Storage\nTD for Transient Data\nDL for DL/I databases\nDB for DB2 or SQL/DS databa\n3.If the display format is not suitable, press PF2 until the format you want is displayed, or replace the value in the\nFORMAT field with one of the following:\nD for Dump format\nC for Character format\nV for Vertical format\nS for Structured format\nEach of these formats is described in the sections that follow.\n4.If you do not want the display to start at the beginning of the record, change the value in the LOC field. Change this\nfield at any time during the session.\nExample\nTo view the data in the 150th byte of a record, specify 150 in the LOC field (95 for FORMAT= D) so byte 150 is the first\nbyte displayed.\nDump Format\nThe following screen shows a record displayed in dump format.\nOn this screen:\n\u2022The left side of the record displays the hexadecimal representation of each byte\n\u2022The right side is the character representation of each displayable byte; non-displayable bytes are shown as periods", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "054b512ab04a-1", "text": "DATATYPE= FC FILEID= INVNTRY  MODE=BROWSE  LOG=OFF TODEST=   PASSWORD=\n FUNC= NEXT SUBFUNC=      RETMETH=        ARGTYP=     SRCHTYP= \n MESSAGE= RECORD OBTAINED FOR VIEWING                                \n  RETNRCID=F0F0F0F0F0F0F0F0F0F5                                GELEN=\n     RCID=                                                                  \n     DATA=                                                     SIZE= 0050\n FORMAT= D 00112233 44556677 8899AABB CCDDEEFF  *0123456789ABCDEF*     \n LOC 0000  ........ ........ ........ ........  ................          \n   0000    F0F0F0F0 F0F0F0F0 F0F54040 40404040   0000000005    DSORG=VSKS\n   0010    F0F3F9F9 0407835C 40404040 40404040   0399....      RECFM=VB\n   0020    40404040 40404040 C1C2C340 C3D6D9D7        BC CORP  LRECL=0050\n   0030    F0F9F1F2 F8F74040 0000598C 40404040   091287  ....  BLKSIZE=0000\n   0040    D1D6C8D5 404040E2 D4C9E3C8 40404040   JOHN   SMITH  KEYPOS=0000\n   0050                                                        KEYLEN=0A\n 1176", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bd10ff77ada3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n   0060                                                        STRNO=01\n   0070                                                                        \n   0080                                                        READ  \n   0090                                                        BROWSE\n   00A0                                                              \n   00B0                                                                \n   00C0                                                                \n \n 1 Help       2 Format C   3 End        4 ENDB       5 NEXT    6 DataType DL\n 7 Page bwd   8 Page fwd   9 Caps Off  10 Top       11 Bottom   12         \nDump format has the following characteristics:\nRecord/segment display  -- 16 bytes per line; hexadecimal and character.\nNumeric information (such as, SIZE, LOC)  -- Hexadecimal.\nField entry  -- Hexadecimal or universal mode.\nPosition of first byte of data in record or segment  -- Location 0.\nLOC Field\nThe LOC field determines where the display starts. For example, if the LOC field specifies 002F, the first byte of data\ndisplayed is the 48th byte of the record.\nThe line numbers under the LOC field and the scale to the right of the FORMAT field help you determine the location of\nany byte of data. Each line number indicates the first byte of data in that line.\nTo locate a particular byte, follow these steps:\n1.Go to the correct line number.\n2.Go across to the correct position. For example, to locate the 48th byte of data (X'2F') in the record in the previous\nfigure, go to LOC line 0020.\n3.Go across to position FF. This byte contains a 'P' (X'D7'ss).\nCharacter Format\nThe following screen shows a record displayed in character format.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bd10ff77ada3-1", "text": "Character Format\nThe following screen shows a record displayed in character format.\n DATATYPE= FC FILEID= INVNTRY  MODE=BROWSELOG=OFF TODEST=      PASSWORD=  \n FUNC= NEXT SUBFUNC=      RETMETH=        ARGTYP=     SRCHTYP=                   \n MESSAGE= RECORD OBTAINED FOR VIEWING                                            \n  RETNRCID=0000000005                                          CHGELEN=\n     RCID=                                                                       \n     DATA=                                                     SIZE= 0080\n FORMAT= C 00000000011111111112222222222333333333344444444445         \n LOC 00001 12345678901234567890123456789012345678901234567890        \n           ..................................................  DSORG=VSKS\n  00001    0000000005      0399....               ABC CORP09   RECFM=VB\n  00051    1287  ....   JOHN   SMITH                           LRECL=0080\n  00101                                                        BLKSIZE=00000\n  00151                                                        KEYPOS=00001\n  00201                                                        KEYLEN=010\n  00251                                                        STRNO=001\n  00301                                                               \n  00351                                                        READ       \n 1177", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d0efa960971d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  00401                                                        BROWSE \n  00451                                                                       \n  00501                                                                 \n  00551                                                           \n \n 1 Help       2 Format V   3 End        4 ENDB    5 PREV   6 DataType DL\n 7 Page bwd   8 Page fwd   9 Caps Off  10 Top    11 Bottom 12  \nIn this screen, the record displays in horizontal lines containing up to 50 characters per line and non-displayable bytes are\nrepresented by periods.\nCharacter format has the following characteristics:\nRecord/segment display  -- 50 characters per line\nNumeric information (such as, SIZE, LOC)  -- decimal numbers\nField entry  -- character, decimal, or universal mode\nPosition of first byte of data in record or segment  -- LOCation 1\nThe LOC field determines where the display starts.\nExample\nIf the LOC field specifies 0065, the first byte of data displayed is the 65th byte of the record.\nThe line numbers under the LOC field and the vertically arranged scale to the right of the FORMAT and LOC fields help\nyou determine the position of any byte of data. Each line number indicates the first byte of data in that line.\nTo locate a particular byte, first go down to the correct line number, and then go across to the correct position.\nExample\nTo locate the 65th byte of data in the record in the previous figure, go down to LOC line 00051, and then across to position\n15. This byte contains a J.\nVertical Format\nThe following screen shows a record displayed in vertical format.\nDATATYPE= FC FILEID= INVNTRY  MODE=BROWSELOG=OFF TODEST=         PASSWORD=", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d0efa960971d-1", "text": "FUNC= NEXT SUBFUNC=      RETMETH=        ARGTYP=     SRCHTYP=                    \n MESSAGE=  RECORD OBTAINED FOR VIEWING                                    \n  RETNRCID=0000000005                                              CHGELEN=\n     RCID=                                                                        \n     DATA=                                                         SIZE= 0080\n FORMAT= V 00000000011111111112222222222333333333344444444445         \n LOC 00001 12345678901234567890123456789012345678901234567890          \n           ..................................................      DSORG=VSKS\n  00001    0000000005      0399....               ABC CORP09       RECFM=VB\n           FFFFFFFFFF444444FFFF00854444444444444444CCC4CDDDFF      LRECL=0080 \n           00000000050000000399473C00000000000000001230369709      BLKSIZE=00000\n                                                                   KEYPOS=00001\n  00051    1287  ....   JOHN   SMITH                               KEYLEN=010\n           FFFF4400584444DDCD444EDCEC4444                          STRNO=001\n           128700009C00001685000249380000                               \n                                                                   READ  \n  00101                                                            BROWSE \n \n 1178", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "65e1c627e172-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n \n \n 1 Help       2 Format D   3 End        4 ENDB       5 PREV       6 DataType DL\n 7 Page bwd   8 Page fwd   9 Caps Off  10 Top       11 Bottom    12\nIn vertical format, the data displays in groups of three lines similar to a DITTO output, with a blank line separating each\ngroup. Each line is represented as follows:\n\u2022Line 1 represents character format\n\u2022Line 2 represents hexadecimal values of the zone (high order) half-bytes\n\u2022Line 3 represents hexadecimal values of the digit (low order) half-bytes\nVertical format has the following characteristics:\nRecord/segment display  -- 50 bytes per line; hexadecimal and character\nNumeric data display (such as SIZE)  -- decimal numbers\nField entry  -- character, decimal, or universal mode\nPosition of first byte of data in record or segment  -- LOCation 1\nThe LOC field determines where the display begins.\nExample\nIf the LOC field specifies 00020, the first byte of data displayed is the 20th byte of the record.\nThe line numbers under the LOC field and the vertically arranged scale to the right of the FORMAT and LOC fields help\nyou determine the location of any byte of data. Each line number indicates the first byte of data in that line.\nTo locate a particular byte, first go down to the correct line number, and then go across to the correct position.\nExample\nTo locate the 20th byte of data in the record in the previous figure, go down to LOC line 00001, and then across to position\n20. This byte contains a '9' (X'F9').\nStructured Format", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "65e1c627e172-1", "text": "20. This byte contains a '9' (X'F9').\nStructured Format\nFILE displays file, transient data, and temporary storage records or DL/I segments field-by-field in structured format.\nCOBOL and PL/I structures use 01 level data names; Assembler structures use DSECT names.\nTo display a record or segment in structured format, you must identify the program containing the structure. Symbolic\ninformation for this program must be saved in the InterTest for CICS Symbolic File. Follow these steps to display a record\nor segment in structured format:\n1.If the FORMAT field does not contain S, press PF2 until FORMAT=S is displayed. The USE= field now opens after the\nFORMAT field.\n2.Identify the program and structure in the USE= field, as follows:\nUSE= symbolic -name .structure -name\nsymbolic-name\nIndicates the name of the program as defined in the Symbolic File.\nstructure-name\nIndicates the COBOL or PL/I 01 level name or the Assembler DSECT.\n3.Press Enter. InterTest for CICS displays the record in structured format.\nSample Records in Structured Format\nThe following screen shows a record in COBOL or PL/I structured format.\n 1179", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a8787bb7f247-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDATATYPE= FC FILEID= INVNTRY  MODE=      LOG=OFF TODEST=         PASSWORD= \n FUNC=      SUBFUNC=      RETMETH=        ARGTYP=     SRCHTYP= \n MESSAGE= RECORD OBTAINED FOR VIEWING \n  RETNRCID=F1D7D9D6E3E2E8D440000000000000000000000000000000        CHGELEN= \n     RCID= C'1' \n     DATA=                                                         SIZE= 02D8 \n FORMAT= S USE= PRODUCT.PRODREC \n LOC 0050           Name                      Hexadecimal            Character \n ----------------------------------------------------------------------------- \n 01 PRODREC                           |                            |\n  02 PRODUCTTYPE                      | D3                         | L\n  02 PRODUCTCODE                      | C2D4D5C8 40404040          | BMNH \n  02 PRODUCTDESCRIPTION               | E6D9C5D5 C3C8              | WRENCH  02 \nPRODUCTSITE                           | D1                         | J \n                                      |                            |\n                                      |                            |\n                                      |                            |\n                                      |                            |\n                                      |                            |\n                                      |                            |\n                                      |                            |\n -------------------------------------------------------------------------------- \n 1 Help       2 Format D   3 End        4 BEGB       5            6 DataType DL \n 7 Page bwd   8 Page fwd   9 Caps Off  10 Top       11 Bottom    12\nThe following screen shows a record in Assembler structured format.\n DATATYPE= FC FILEID= INVNTRY  MODE=      LOG=OFF TODEST=         PASSWORD=", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a8787bb7f247-1", "text": "FUNC=      SUBFUNC=      RETMETH=        ARGTYP=     SRCHTYP= \n MESSAGE=  \n  RETNRCID=D3C2D4D5C840404040404040404040404040404040404040        CHGELEN= \n     RCID= C'1' \n     DATA=                                                         SIZE= 0050 \n FORMAT= S USE= PRODUCT.PRODREC \n LOC 0000  Displacement               Hexadecimal                   Character \n------------------------------------------------------------------------------  \n PRODTYPE             0 | D3                                  | L \n PRODCODE             1 | C2D4D5C8 40404040                   | BMNH \n PRODDESC             9 | E6D9C5D5 C3C8                       | WRENCH\n PRODSITE            18 | D1                                  | J \n                        |                                     |\n                        |                                     |\n                        |                                     |\n                        |                                     |\n                        |                                     |\n                        |                                     |\n                        |                                     |\n ------------------------------------------------------------------------------ \n 1 Help       2 Format D   3 End        4 BEGB       5            6 DataType DL \n 7 Page bwd   8 Page fwd   9 Caps Off  10 Top       11 Bottom    12\n\u2022Both screens list the contents of each data name in both hexadecimal and character format.\n\u2022For Assembler DSECTs, the display also includes the displacement.\n\u2022Non-displayable bytes are represented by periods.\n 1180", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4109ebc4ab43-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nStructured format is very similar to dump format:\nRecord/segment display  -- For Assembler, 16 bytes per line; for COBOL or PL/I, 12 bytes per line in hexadecimal and\ncharacter\nNumeric information (such as, SIZE, LOC)  -- Hexadecimal\nField entry  -- Hexadecimal or universal mode\nPosition of first byte of data in record or segment  -- LOCation 0\nThe structure-name remains valid throughout the FILE session unless it is changed. This lets you shift display formats or\ndata types without re-entering the structure-name.\nSpecial Features\nThe following bullets describe special features:\n\u2022To change the symbolic-name or structure-name, overtype the command in the USE= field.\n\u2022The FILE or PCB information is not displayed. To see this information, switch to another display format.\n\u2022The structure is positioned at the data name whose offset is less than or equal to the LOC= value, except during\nscrolling.\nUse Structured Format When a Program Is at a Breakpoint\nWhen a program is stopped at a breakpoint, substitute an asterisk ( *) for the symbolic-name.\nExample\nIf program PAYROLL is stopped at a breakpoint and you enter:\nUSE=*.payrec\nInterTest for CICS uses the program named PAYROLL and the PAYREC structure.\nUse a Global Program Name\nYour site compiles a default dummy  COBOL or PL/I program containing all of the 01 level structures used at the site, or an\nAssembler program that contains all of the DSECTs. Symbolic information for this program must be stored in the InterTest\nfor CICS Symbolic File.\nThe symbolic name for this program is referenced in the FSYMP installation name. The default name is PROTFILE.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4109ebc4ab43-1", "text": "If a default global program was compiled or assembled, obtain a structured record format by entering the following\ncommand:\nUSE=structure-name\nThe symbolic-name defaults to the default dummy program name.\nFind a Data Name\nTo search the structure for a specific data name, enter the following command in the DATA= field:\nFIND=data-name\nNOTE\nThe FIND command is valid only when FORMAT=S.\ndata-name\nIndicates the data name to be displayed.\n 1181", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6ef0e140e11c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe search is applied to the beginning of a data name.\nExample\nFIND=A9 finds the field named A9-AREA, but not the field named AREA-A9.\nThe search begins with the data name after the starting point and continues until either a match is found or the search has\nwrapped around to the original starting point. A message signals a possible wraparound.\nUniversal Mode of Data Entry in the RCID, DATA, and SSA Fields\nUse the universal mode  of entering data in the RCID, DATA, and SSA fields when you are entering information that\ncontains both character and binary data (such as a VSAM key), or when it is inconvenient to change the display format.\nEnter data as follows:\nCharacter\nData. Specify C' (C and a single quote) before the character string and a ' (single quote) after it. Double any\napostrophes that display within the string.\nExample\nC'O''ALLEY''\nHexadecimal\nData. Specify X' (X and a single quote) before the data, and a ' (single quote) after it. The data must be an even\nnumber of hexadecimal characters.\nExample\nX'001F'\nNOTE\nSpecify an RCID up to 32-hexadecimal characters long.\nYou can also enter data that is both character and hexadecimal.\nExample\nC'1234'X'000F'\nAccess Files and Databases Protected by InterTest for CICS Passwords\nCertain files or DL/I databases could have been assigned InterTest for CICS passwords when InterTest for CICS was\ninstalled. A password prevents unauthorized viewing and updating. FILE only lets you access such a file or database if\nyou enter the correct password in the PASSWORD field. If you do not enter the correct password when one is required,\nFILE terminates.\nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6ef0e140e11c-1", "text": "FILE terminates.\nNOTE\nInterTest for CICS password protection decisions were made by the person who installed InterTest for CICS.\nLog FILE Session\nFILE's logging facility lets you record the input commands and output screens generated during a FILE session in\ncharacter format. The log is written to the transient data destination specified when InterTest for CICS was installed.\nTo see the name of the destination, follow these steps:\n1.On a clear screen, enter VRPT .\n2.Select option 02.\n3.The GLOG option indicates the name of the destination.\n 1182", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "40d57ed62b05-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo activate logging, enter:\nFUNC= LOG\nTo terminate logging, enter:\nFUNC= NLOG\nWhen logging is in effect, the LOG field contains LOG= ON and the FUNC=COPY function is disabled. When it is not in\neffect, the LOG field contains LOG= OFF.\nNOTE\nIf the AUDIT installation option was set at installation time, you cannot terminate logging.\nEnd a FILE Session\nTerminate FILE by pressing PF3  or the Clear key.\nPF Keys\nWhen you are using FILE, the PF keys perform the functions listed in the following table.\nPF Key Function\nPF1 Help initiates the InterTest for CICS online Help facility.\nPF2 Format C V D S changes the format displayed to Character,\nVertical, Dump, or Structured.\nPF3 End or Clear terminates the FILE facility.\nPF4 BEGB ENDB begins or ends a Browse for VSAM files specified for\nbrowse in the FILEID field.\nPF5 PREV NEXT displays the previous or next record in browse mode.\nPF6 DataType changes the DATATYPE to the code displayed next\nto the PF6 key: FC for File Control, DL for DL/I, TD for Transient\nData, TS for Temporary Storage, and DB for both DB2 and SQL/\nDS.\nPF7 Page Bwd scrolls the current display one page backward.\nPF8 Page Fwd scrolls the current display one page forward.\nPF9 Caps Off/Caps On sets the mode of translation when changing\ndata in the character area of the display. When Caps On displays,\nall character data is accepted as typed. When Caps Off is\ndisplays, all character data on the line is translated to uppercase.\nPress PF9 to change from one mode to the other.\nNote: Translation to uppercase will not occur if an existing", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "40d57ed62b05-1", "text": "Note: Translation to uppercase will not occur if an existing\nlowercase character would be affected; a message is issued\ninstead.\nPF10 Top scrolls the current display to the top of the work area.\nPF11 Bottom scrolls the current display to the last page of the work\narea.\nScroll Through a Record\nUse these PF keys to page forward and backward through a record, and to display the beginning or end of a record:\n 1183", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "782321cef8b5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022PF8 pages forward\n\u2022PF7 pages backward\n\u2022PF10 displays beginning of record\n\u2022PF11 displays end of record\nUse the LOC Field to Position the Display\nThe LOC field controls the position of the first displayed byte in the WORK AREA. The following table explains the values\nthat you enter in the LOC field to control the position of the first displayed byte.\nWARNING\nTo determine the location of any byte on the data display portion of the screen, add the number on the left end of\nthe line (the number under the LOC field) to the number above the byte in the data display header (to the right of\nthe FORMAT= field).\nLOC Position of Data\nHexadecimal value, relative to zero For FORMAT=D or S, indicates the relative displacement of the\nfirst displayed byte.\nDecimal value, relative to one For FORMAT=C or FORMAT=V, indicates the relative\ndisplacement of the first displayed byte.\n? and cursor is positioned in the record display area The cursor position becomes the first displayed byte when you\npress Enter. The LOC field reflects the hexadecimal or decimal\nposition, depending on the FORMAT= field.\nFWD or PF8 Advances the data display forward  one full page.\nBWD or PF7 Moves the data display backward one full page.\nTOP or PF10 Positions the display on the first byte.\nEND or PF11 Positions the display on the last page of data.\nThe Help Facility\nThe Help facility summarizes the steps required to perform FILE functions. Access the Help facility by pressing the PF1\nkey from any FILE screen.\nChange Data in the Work Area\nChange FILE work areas by overtyping the hexadecimal or character data displayed on the screen with new data. Any\nnumber of bytes can be overwritten with any uppercase or lowercase character.\nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "782321cef8b5-1", "text": "number of bytes can be overwritten with any uppercase or lowercase character.\nNOTE\nIf you overtype the same data in hexadecimal and character display fields, the hexadecimal change takes\nprecedence.\nYou can also replace record data with fill characters, data from CORE, or data from the saved WORK AREA.\nThe CHGE Function\nFollow this procedure when using the CHGE function:\n1.To change data in the WORK AREA, position the first byte (character) of the data that is to be changed so that it is the\nfirst byte of the FILE display. There are two ways to do this:\n 1184", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5c0776b395af-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2013Type the desired location in the LOC field, and press Enter.\n\u2013Type a question mark (?) in the LOC field, position the cursor at the appropriate location in the record, and press\nEnter.\nDelay pressing Enter until you complete Step 2.\n2.Fill in the FUNC= and DATA= fields as shown next:\nFUNC=CHGE\nDATA= new data\n3.Fill in the following optional  field, if it applies to your situation:\nCHGELEN =  length of the data to be change\nUse a hexadecimal number for FORMAT=D and a decimal number for all other FORMATs.\n4.Press Enter. The MESSAGE= field displays the following message and the displayed record shows the new data at\nthe proper location.\nxxx NUMBER OF BYTES CHANGED\nExample\nTo change four bytes at location 20 to the literal TEST, fill in the fields as shown next, and press Enter:\nFUNC=CHGE\nDATA=C'TEST'\nLOC=00020           (or 0013 for FORMAT=D)  \nFill Part of the Work Area with a Character String\nTo fill part of the WORK AREA with a character string, specify the following fields, and press Enter:\nFUNC=CHGE\nSUBFUNC=FILL\nCHGELEN= length of area to be change\nDATA= character string\nDOC= starting position\nExample\nTo move 30 spaces into locations 15 to 44, specify the following fields and press Enter:\nFUNC=CHGE\nSUBFUNC=FILL\nCHGELEN=0030        (or 001E for FORMAT=D)  \nDATA=C' '       (or X'40')  \nLOC=00015       (or 000E for FORMAT=D)  \nCopy Data from a Main Storage Location", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5c0776b395af-1", "text": "Copy Data from a Main Storage Location\nTo copy data from a main storage location into the WORK AREA, specify the following and press Enter:\nFUNC=CHGE\nSUBFUNC=CORE\nDATA= CORE command that determines the source address\nCHGELEN= length of area to be changed\nLOC= starting position\nExamples\n 1185", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8b0dc39094d5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe following examples demonstrate how to copy data from main storage.\n1.To copy 16 bytes from TWA+8 (at an InterTest for CICS breakpoint) into locations 48to 63 of the record, specify the\nfollowing, and press Enter:\nFUNC=CHGE\nSUBFUNC=CORE\nCHGELEN=0016        (or 0010 for FORMAT=D)  \nDATA=CORE=TWA+8\nLOC=00048       (or 002F for FORMAT=D)  \n2.Suppose you are stopped at a breakpoint in a COBOL program. You want to copy ten bytes of data from a field named\nSOC-SEC-NUMBER into locations 1 to 10 of the record. To do this, specify the following and press Enter:\nFUNC=CHGE\nSUBFUNC=CORE\nCHGELEN=0010            (or 000A for FORMAT=D)  \nDATA=CORE='SOC-SEC-NUMBER'\nLOC=00001           (or 0000 for FORMAT=D)  \nCopy Data from a Saved Work Area\nTo copy data from a saved work area into the current WORK AREA, specify the following, and press Enter:\nFUNC=CHGE\nSUBFUNC=FROM\nCHGELEN= length of the area to be changed\nDATA=FROMLOC= location of the data in the saved WORK AREA\nLOC= starting position\nSave Records and Display Work Areas\nSave a copy of the displayed record in a WORK AREA. This is useful when you want to create new records using an\nexisting record as a skeleton, or when you want to modify an existing record using data from a saved record.\nTo save the record currently displayed, enter:\nFUNC= SAVE\nA previously saved record area is destroyed.\nTo display the saved area, enter:\nFUNC= DISS", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8b0dc39094d5-1", "text": "To display the saved area, enter:\nFUNC= DISS\nTo display the active WORK AREA, enter:\nFUNC= DISW\nDump the Work Area\nWrite the work area to the CICS transaction dump file. To dump the WORK AREA, enter:\nFUNC= DUMP\nTODEST= a four character dump code\nYou can also enter an explanatory note in the MESSAGE field. The note displays in the dump.\nRecord a Copy of the Screen Display\nCopy the WORK AREA to a transient data queue. To copy the work area to a TD queue, enter:\n 1186", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "610803217112-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFUNC= COPY\nTODEST= a transient data queue ID\nYou can also enter an explanatory note in the MESSAGE field. The note is written with the work area.\nNOTE\nThis function is invalid when logging is in effect.\nCommon FILE Functions\nEnter the following FILE commands in the FUNC= field for all data types except DB2 and SQL/DS databases.\nCommand Function\nADDN Acquires a new work area for record insertion.\nADDU Uses an existing work area for record insertion.\nCHGE Changes data in the work area.\nCOPY Copies a work area to the transient data destination specified in\nthe TODEST field.\nDISS Displays the saved work area.\nDISW Displays the current work area.\nDUMP Dumps the work area using the dump code entered in the\nTODEST field.\nEND Ends the FILE session.\nHELP Accesses Help for FILE.\nLOG Logs all FILE transaction requests and responses.\nNLOG Terminates logging.\nSAVE Creates a copy of the current work area.\nSRCH Searches for the data string specified in the DATA field (not valid\nfor DL/I or transient data).\nVSAM Files\nThe FILE transaction performs any VSAM function allowed in your CICS system.\nNOTE\nYou can consult the IBM CICS/VS Application Programmer's Reference Manual  for information on using\nVSAM files. This manual helps you formulate your FILE requests correctly, and explains the meaning of many\nresponses you will receive from FILE.\nTo begin processing a VSAM file, first make sure you are viewing the correct screen. The DATATYPE= field should be set\nto FC. If not, press PF6 or enter:\nDATATYPE= FC\nThen enter:\nFILEID= file name\nThe other information you enter depends on the function you want to perform.\nIdentify the Record", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "610803217112-1", "text": "The other information you enter depends on the function you want to perform.\nIdentify the Record\nWhen you access a VSAM file for the first time, the record identification field is set as follows:\n 1187", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2bdedf42dc51-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nKSDS and ESDS   nulls   (X`00') \nRRDSone (X`01')\nNOTE\nData entered in the RCID field overrides these values.\nOccasionally, the last record identification for a file is needed as the first record identification for another file. To prevent\nthe RCID from being reset to nulls or to one, enter LAST  in the SUBFUNC field when you specify the new filename in the\nFILEID field. The LAST subfunction works only when a file is requested for the first time.\nFILE Screen Layout for VSAM Files\nThe following screen shows a blank header area on a FILE screen for VSAM files.\nExamples\nExamples of the complete screen, see Dump Format, Character Format, Vertical Format and Structured Format.\n DATATYPE= FC FILEID=          MODE=     LOG=     TODEST=         PASSWORD=\n FUNC=      SUBFUNC=      RETMETH=        ARGTYP=     SRCHTYP=       \n MESSAGE=                   \n  RETNRCID=                                                        CHGELEN=\n     RCID=                                                                        \n     DATA=                                                         SIZE=\n FORMAT= D 00112233 44556677 8899AABB CCDDEEFF  *0123456789ABCDEF*        \n LOC 0000  ........ ........ ........ ........  ................\n \n 1 Help       2 Format D   3 End        4 BEGB       5            6 DataType DL \n 7 Page bwd   8 Page fwd   9 Caps Off  10 Top       11 Bottom    12\nThe fields provide the following information:\nFields Function\nDATATYPE Identifies the type of data organization. This must be FC.\nFILEID Specifies the name of the VSAM file.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2bdedf42dc51-1", "text": "FILEID Specifies the name of the VSAM file.\nMODE Identifies the FILE operation such as browse, update, add, add in\nmass insertion. This field is blank if you are just viewing a record.\nLOG Specifies whether the FILE logging facility is on or off.\nTODEST Identifies a transient data destination (when a work area is copied)\nor a dump identification (when a work area is dumped).\nPASSWORD Must contain a four-character password if the file is protected.\nFUNC Specifies the FILE function. When this field contains a function\ncode, it is executed if you press Enter. In addition to common FILE\nfunctions, enter the following commands: BEGB, DEL, ENDB,\nGET, GETU, NEXT, PREV, PUT, REL.\nSUBFUNC Modifies a FUNC specification.\nRETMETH Identifies the RCID field (BDAM files only).\nARGTYP No longer required.\nSRCHTYP Specifies how RCID information is processed (KSDS files only).\n 1188", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3328a8363925-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMESSAGE Contains FILE messages. Also specify messages here when\nFUNC=COPY or FUNC=DUMP.\nRETNRCID Contains the record key of the retrieved record.\nCHGELEN Specifies the number of bytes changed in the work area when\nFUNC=CHGE.\nRCID Identifies the record to be processed.\nDATA Contains data needed to perform certain FILE functions.\nSIZE Specifies the record size or the number of records to be searched.\nFORMAT Specifies the format in which the record is displayed.\nUSE Specifies the program and structure for structured format.\nLOC Specifies a location within a record.\nSome fields are used only for certain tasks. The discussion of each FILE function indicates which fields must be specified.\nWhen a record displays, its FILE information is in the lower-right portion of the screen. This information includes the\nfollowing:\n\u2022DSORG(data organization)\n\u2022RECFM(record format)\n\u2022LRECL (record length)\n\u2022BLKSIZE (blocksize)\n\u2022KEYPOS (key position)\n\u2022KEYLEN (key length)\n\u2022STRNO (string number)\nBeneath the FILE information is a list of the functions you can perform, such as READ, ADD, UPDATE, BROWSE,\nDELETE.\nFILE Functions for VSAM Records\nThe following FILE functions are discussed in this section:\n\u2022Viewing a VSAM record\n\u2022Browsing a VSAM file\n\u2022Searching for a data string\n\u2022Updating a VSAM record\n\u2022Adding a VSAM record\n\u2022Mass insertion into a VSAM file\n\u2022Copying a VSAM record from one file to another\n\u2022Deleting VSAM records\nView a VSAM Record\nTo view a VSAM record, specify the READ operation on the FILE definition.\n1.Enter the following required information for all VSAM files:\nFUNC= GET\nRCID= key", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3328a8363925-1", "text": "FUNC= GET\nRCID= key\n\u2013For a KSDS  file, the key is a full or generic key, depending on the optional SRCHTYP field. Specify the key in\nhexadecimal or character format or a combination of both.\n\u2013For an ESDS file, the key is a four-byte hexadecimal number representing the relative byte address (RBA).\n 1189", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e917c718dd95-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2013For an RRDS file, the key is a four-byte hexadecimal number representing the relative record number.\n2.Enter the following optional information for a KSDS file:\nSRCHTYP= FKEQ/FKGE/GKEQ/GKGE\n\u2013If you specify SRCHTYP=FKEQ, enter the full key in the RCID field. FILE retrieves the specified record. This is the\ndefault.\n\u2013If you specify SRCHTYP=FKGE, enter the full key in the RCID field. FILE retrieves the specified record or the\nrecord with the next higher key.\n\u2013If you specify SRCHTYP=GKEQ, enter a generic (partial) key in the RCID field. FILE retrieves the first record\nwhose key matches the generic key.\n\u2013If you specify SRCHTYP=GKGE, enter a generic (partial) key in the RCID field. FILE retrieves the first record\nwhose key matches the generic key or the next higher key.\n3.Press Enter. FILE displays the requested record.\nBrowse a VSAM File\nTo browse a VSAM file, specify the BROWSE operation on the FILE definition.\n1.Enter the following required information for all VSAM files (or press PF4):\nFUNC= BEGB\nAlso specify a key in the RCID field to begin to browse from a specified record.\n\u2013For a KSDS file, this key can be a full or generic key, depending on the SRCHTYP field.\n\u2013For an ESDS file, you must also specify ARGTYP= RBA or ARGTYP= XRBA.\n2.Enter the following optional information for a KSDS file:\nSRCHTYP= FKGE/FKEQ/GKGE/GKEQ", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e917c718dd95-1", "text": "SRCHTYP= FKGE/FKEQ/GKGE/GKEQ\n\u2013If you specify SRCHTYP=FKGE, enter the full key in the RCID field. The browse starts at the record with that key or\nthe next higher key. This is the default.\n\u2013If you specify SRCHTYP=FKEQ, enter the full key in the RCID field. The browse starts at this record.\n\u2013If you specify SRCHTYP=GKGE, enter a generic (partial) key in the RCID field. The browse starts at the first record\nwhose key matches the generic key or the next higher key.\n\u2013If you specify SRCHTYP=GKEQ, enter a generic (partial) key in the RCID field. The browse starts at the first record\nwhose key matches the generic key.\n3.Press Enter. FILE displays the first retrieved record. The FUNC field is preset to NEXT.\n\u2013To view the records in ascending sequence, press Enter.\n\u2013To view the records in descending sequence, enter FUNC=PREV, and then repeatedly press Enter to display the\nrecords in descending sequence. Use the PREV function only if the browse is initiated with SRCHTYP=FKEQ.\n\u2013Use both NEXT and PREV during the same browse operation. Use PF5 to change descending and ascending\nsequence.\n4.Terminate the browse by pressing PF4, specifying FUNC=ENDB, or specifying one of these functions: GET, GETU,\nADD, or ADDU.\nExample\nTo view the record with the key 'REC001' and the next record, and then to terminate the browse, follow these steps:\n1.Specify the following (or press PF4):\nFUNC= BEGB\nRCID= C`REC001'\n2.Press Enter to display the record with a key of REC001.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e917c718dd95-2", "text": "2.Press Enter to display the record with a key of REC001.\n3.Press Enter to display the next record.\n4.Press PF4 to end the browse.\n 1190", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c32aeebb7746-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSearch for a Data String\nTo search for a data string, specify the BROWSE operation on the FILE definition.\n1.Specify the following required information:\nFUNC= SRCH\nRCID= id of record where search should begin\nDATA= data string to be located\nLOC a number or the keyword ANY\nIf a number is entered in the LOC field, FILE looks for the data string only at the specified location. If ANY is entered,\nFILE searches the entire record for the specified data string.\n2.To search more than one record, enter the number of records that you want to search in the SIZE field.\n3.Specify the following optional information for a KSDS file:\nSRCHTYP= FKGE/FKEQ/GKEQ/GKGE\n\u2013If you specify SRCHTYP=FKGE, enter the full key in the RCID field. The search starts with the specified record or\nthe record with the next higher key. This is the default.\n\u2013If you specify SRCHTYP=FKEQ, enter the full key in the RCID field. The search starts with the specified record.\n\u2013If you specify SRCHTYP=GKEQ, enter a generic (partial) key in the RCID field. The search starts with the first\nrecord whose key matches the generic key.\n\u2013If you specify SRCHTYP=GKGE, enter a generic (partial) key in the RCID field. The search starts with the first\nrecord whose key matches the generic key or the next higher key.\n4.Press Enter. If FILE finds the requested data string, it displays the record in which it is found, starting with the\nrequested string. The RETNRCID field displays the ID of the record and the LOC field displays the record position at\nwhich the data was found.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c32aeebb7746-1", "text": "which the data was found.\nIf the data is not found, the message DATA NOT FOUND opens.\nExample\nTo scan up to ten records in the file ACCTS looking for the data string TEST in record positions 20-23, and to begin the\nsearch with the record whose ID is NEWREC001, specify the following:\nFILEID= ACCTS\nFUNC= SRCH\nRCID= C`NEWREC001'\nDATA= C`TEST'\nLOC 00020       (or 0013 for FORMAT=D)  \nSIZE= 0010      (or 000A for FORMAT=D)  \nPress Enter to display the data.\nUpdate a VSAM Record\nTo update a record, specify the UPDATE operation on the FILE definition.\n1.Retrieve the record you want to update, and then enter the appropriate command:\nFUNC= GETU\nRCID= key       (for all VSAM files)    \nFUNC= GET\nRCID= key       (for KSDS files only)   \n2.Press Enter, or browse the file.\n3.Change any portion of the record, except a KSDS key. For more information, see Change Data in the Work Area.\n4.After you have made all the changes, specify the following, and then press Enter:\nFUNC= PUT\nSIZE= new record size\n 1191", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "59c4f3cfb4c8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSpecify the SIZE field only when changing the size of a variable length record.\n5.FILE rewrites the updated record.\nAdd a VSAM Record\nTo add a record, specify the ADD operation on the FILE definition.\n1.Specify the following required information:\nFUNC= ADDN  (to obtain a new work area) \nor\nFUNC=ADDU   (to use the data in the current work area)  \nPress Enter to get the work area to be used for the new record. FILE displays the maximum record length in the SIZE\nfield and ADD in the MODE field.\n2.Specify the following optional information:\nFUNC=CHGE\nSUBFUNC=FILL\nDATA=data string\nPress Enter.\n\u2013For FUNC=ADDN, the data string fills the new work area.\n\u2013For FUNC=ADDU, the data string fills the extended portion of the work area.\n3.Change the data in the work area to meet your requirements. For more information, see Change Data in the Work\nArea. \n4.To write the updated record, enter the following required information:\nFUNC= PUT\nRCID= record id\nSIZE= record length\nFor a KSDS file, the record ID overlays the key portion of the record.\nNOTE\nSpecify the SIZE field only when adding a variable length record. Press Enter. FILE redisplays the new\nrecord and displays the message RECORD ADDED.\n5.If you decide not to add this record, specify FUNC= REL. FILE continues to display the record and displays the\nmessage FWA HAS BEEN RELEASED.\nMass Insertion into a VSAM File\nFollow the same procedure for adding a single record.\n1.Specify FUNC=ADDN, or FUNC=ADDU and SUBFUNC=MASS. Optionally specify the DATA= data string field.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "59c4f3cfb4c8-1", "text": "2.Make your changes and write the new record. Repeat the procedure of making changes and writing the new record\nuntil you have added all the records.\n3.Enter FUNC= REL to terminate the mass insertion operation.\nExample\n1.Specify the following, and then press Enter:\nFILEID= ACCTS \nFUNC= ADDN \nSUBFUNC= MASS \n2.Specify the following, and then press Enter:\nFUNC= CHGE SUB\nFUNC= FILL DATA= C' ' \n3.Specify the following, and then press Enter:\n 1192", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1b7b55f3ffb1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFUNC= PUT \nRCID= C'NEWREC004' \n4.Specify the following, and then press Enter:\nFUNC= PUT \nRCID= C'NEWREC005'\n5.Specify the following, and then press Enter:\nFUNC= PUT\nRCID= C`NEWREC008' \n6.Specify the following, and then press Enter:\nFUNC= REL \nCopy a VSAM Record from One File to Another\nTo copy a record from one file to a second file, specify the READ function for the first file and the ADD function for the\nsecond file.\n1.To retrieve the record you want to copy, specify the following, and then press Enter or browse the file:\nFILEID= file ID of source file\nFUNC= GET\nRCID= key\n2.After FILE displays the record, specify the following, and then press Enter:\nFILEID= file ID of destination file\nFUNC= ADDU\n3.Make any necessary changes, then specify the following, and press Enter:\nFUNC= PUT\nRCID= key\nSIZE= record length\nNote: Specify the SIZE field only when adding a variable length record.\nFILE redisplays the record and displays the message RECORD ADDED.\nRepeat Steps 1 through 3 to copy additional records.\nNOTE\nIf the LRECLs of the two files differ, the LRECL of the destination file determines the size of the record. The\nrecord is either truncated or padded with binary zeros to meet that length.\nExample\nTo copy a record with the key 'REC050' from the ACCTS file to the TEST file, follow these steps:\n1.Specify the following, and then press Enter to display the record:\nFILEID= ACCTS \nFUNC= GET RCID= C'REC050", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1b7b55f3ffb1-1", "text": "FILEID= ACCTS \nFUNC= GET RCID= C'REC050\n2.Specify the following, and then press Enter:\nFILEID= TEST \nFUNC= ADDU\n3.Specify the following, and then press Enter:\nFUNC= PUT\nRCID= C'REC001'\nDelete VSAM Records\nTo delete a record, follow these steps:\n1.Specify the DELETE operation on the FILE definition.\n 1193", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c8ce78e0a62b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n2.Specify the following required information:\nFUNC= DEL\nTo delete a single record, follow these steps:\n1.Specify the following:\nRCID= full record key\n2.Press Enter.\nTo delete all records having a generic (partial) key (KSDS files only), follow these steps:\n1.Specify the following:\nRCID= generic key\nSRCHTYP= GKEQ \nARGTYP= KEY\n2.Press  Enter .\nNotes:\n\u2022FILE deletes all the records whose keys match the generic key unless BACKUPTYPE DYNAMIC is specified for the\nFILE definition because CICS does not permit generic key deletion for FILE defined with this option\n\u2022If a single record is deleted, FILE displays it with the message RECORD DELETED.\n\u2022If you specify SRCHTYP=GKEQ, FILE displays the first record deleted. The message field specifies the number of\ndeleted records xxx RECORDS DELETED.\nExamples\n1.To delete the record NEWREC001 from the ACCTS file, specify the following, and then press Enter:\nFILEID= ACCTS\nFUNC= DEL\nRCID= C`NEWREC001'\n2.To delete all records whose keys start with the character string NEWREC from the ACCTS file, specify the following,\nand then press Enter:\nFILEID= ACCTS\nFUNC= DEL\nSRCHTYP= GKEQ\nRCID= C`NEWREC'\nARGTYP= KEY\nDeleting a Record with a Large Key\nTo delete a record whose key is larger than the RCID field, perform these steps:\nTo retrieve the record or browse the file, follow these steps.\n1.Specify the following:\nFUNC= GET\nSRCHTYP= GKGE\nRCID= generic key\nARGTYP= KEY", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c8ce78e0a62b-1", "text": "SRCHTYP= GKGE\nRCID= generic key\nARGTYP= KEY\n2.Press  Enter .\nTo delete the record, follow these steps.\n1.Specify the following:\nFUNC= PUT\nSUBFUNC= DEL\n 1194", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b9817f0b9ee9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n2.Press Enter .\nFILE deletes the record and displays the message RECORD DELETED.\nWork with DL/I Databases\nFILE lets you access any DL/I database to which it has been given access.\nTo start working with a DL/I database follow these steps.\n1.Initiate the FILE transaction and get the DL/I entry screen.\n2.Press PF6 or specify the following:\nDATATYPE= DL\n3.Then enter:\nPSB= PSB name\nDBD= DBD name\nNO= DBD entry number\nOther information you enter depends on the function you want to perform.\nNOTE\nFor more information about using DL/I databases, see  IBM's DL/I DOS/VS Application Programming Reference\nManual  or the IMS/VS Application Programming for CICS/VS Users Manual.\nFILE Screen Layout for DL/I Databases\nThe following screen shows the FILE screen layout for DL/I databases.\nDATATYPE= DL FUNC=      PSB=          DBD=          NO 01 SUBFUNC=      PS=     \n SSA=                                                                           \n                                                                                \n                                                                   TODEST=      \nMESSAGE=                                                           CHGLEN=      \n    DATA=                                                          SIZE= 0000   \nFORMAT= D 00112233 44556677 8899AABB CCDDEEFF  *0123456789ABCDEF*  LOG=ON       \nLOC 0000  ........ ........ ........ ........   ................                \n                                                                  STAT=         \n                                                                  NAME=         \n                                                                  LEVL=         \n                                                                  POPT=         \n                                                                  KFBL=        \n                                                                  KEY FEEDBACK  \n                                                                  *          *  \n                                                                  *          *  \n                                                                  *          *  \n                                                                  *          *  \n                                                                  *          *  \n                                                                  *          *  \n-------------------------------------------------------------------------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b9817f0b9ee9-1", "text": "*          *  \n                                                                  *          *  \n------------------------------------------------------------------------------- \n1 Help       2 Format C   3 End        4 BEGB       5            6 DataType FC  \n7 Page bwd   8 Page fwd   9 Caps Off  10 Top       11 Bottom    12\n 1195", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5fb537bc7f78-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe following table describes each field's function.\nField Function\nDATATYPE Specifies the type of data organization. For DL/I databases, it is\nDL.\nFUNC Specifies the FILE function. When this field contains a function\ncode, it is executed if you press Enter. In addition to common FILE\nfunctions, enter the following commands: DLET, GHN, GHU, GN,\nGNHP, GNP, GU, ISRT, REPL.\nPSB Specifies the PSB name, which you can change any time using\nFILE.\nDBD Specifies the DBD name, which you can change any time using\nFILE.\nNO Specifies which DBD entry to use when there is more than one\nDBD with the same name in the PSB. The default is 01.\nSUBFUNC Modifies a FUNC specification.\nPS If the DBD is password protected, enter a four-character\npassword.\nSSA Specifies required segment search arguments. For more\ninformation, see the SSA Formats.\nTODEST Identifies a transient data destination (when a work area is copied)\nor a dump identification (when a work area is dumped).\nMESSAGE Contains FILE messages. Also specify messages here when\nFUNC=COPY or FUNC=DUMP.\nCHGELEN Specifies the number of bytes changed in the work area when\nFUNC=CHGE.\nDATA Contains data needed to perform certain FILE functions.\nSIZE Specifies the size of the segment.\nFORMAT Specifies the format in which the segment is displayed.\nUSE Specifies the program and structure for structured format.\nLOG Specifies whether FILE's logging facility is on or off.\nLOC Specifies a location within a segment.\nReturned PCB information appears in the lower-right screen area:\nSTAT -- DL/I status code returned by PSB\nNAME  -- Name of retrieved segment\nLEVL  -- Level number of segment", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5fb537bc7f78-1", "text": "NAME  -- Name of retrieved segment\nLEVL  -- Level number of segment\nPOPT  -- DL/I processing options\nKFBL  -- Length of key feedback area\nKEY FEEDBACK  -- Displays key feedback area\nSome fields are applicable only to certain functions. The discussion of each FILE function indicates which fields must be\nspecified.\n 1196", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7bbb94e7f460-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSpecifying the SIZE Field\nUse the SIZE field to specify a storage area large enough to contain the segment to be retrieved or added. If this field\nis blank or contains zeros, FILE uses the default value specified in the DL1SIZE option when InterTest for CICS was\ninstalled. To check the default value:\n1.On a clear screen, enter VRPT .\n2.Select option 02.\n3.The DL1SIZE option contains the default SIZE value.\nIf you need to change the default value, contact the systems programmer who maintains InterTest for CICS.\nFILE Functions for DL/I Databases\nThe following topics are discussed in this section:\n\u2022SSA formats\n\u2022Viewing a DL/I segment\n\u2022Updating a DL/I segment\n\u2022Adding a DL/I segment\n\u2022Copying a DL/I segment\n\u2022Deleting a DL/I segment\nSSA Formats\nSSA specifications follow standard DL/I conventions. Information entered in the SSA field must conform to the following\nformat:\nsegname qual keyname ro keyarg\nsegname\nIndicates the segment name, from one to eight characters long. If the segment name is less than eight characters,\nit must be followed by a blank.\nqual\nIndicates a blank, left parenthesis, (, or asterisk, *.\n\u2022Blanks specify an unqualified SSA.\n\u2022A left parenthesis, (, specifies a qualified SSA. If used, right\nparenthesis, ), must follow the keyarg  data.\n\u2022An asterisk, *, specifies that command codes are present. In this case, either a blank (for an unqualified\nSSA) or a left parenthesis (for a qualified SSA) must follow the last command code. FILE does not validate\ncommand codes. This is handled by DL/I.\nkeyname", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7bbb94e7f460-1", "text": "command codes. This is handled by DL/I.\nkeyname\nIndicates the key name, from one to eight characters long. If it is less than eight characters long, it must be\nfollowed by one blank.\nro\nIndicates a relational operator. It can be any of the standard relational operators used in DL/I. It must be two bytes\nlong and must immediately follow either the last character in the keyname (if the keyname is eight characters\nlong), or the blank terminating the keyname (if the keyname is less than eight characters long).\nIf you use a one-character sign rather than two letters to specify the relational operator (such as = instead of EQ), you\nmust specify a blank before or after the sign.\n 1197", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fcfd3aee447d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nkeyarg\nIndicates the argument for the key name. Enter the keyarg as either character or hexadecimal data, or as a\ncombination of both, in one of the following ways:\n\u2022C'data' for character data\n\u2022X'data' for hexadecimal data\n\u2022data for treated as character data\nNOTE\nIf your keyarg  data contains any of these special characters, ), &, |, *, or + you must use the X'data'\nformat to enter it.\n\u2022Create compound conditions by using & or | signs to join multiple keyname ro keyarg specifications.\nNOTE\nIf you specify more than one SSA, you must insert a blank and SSA= before each subsequent SSA.\nExamples\nIn the following examples of SSA specifications, b indicates a blank.\n1.The following specification indicates an unqualified SSA:\nSSA= SEGTWObb\nThe two blanks are necessary, because the segment name is less than eight characters, and an unqualified SSA is\nindicated.\n2.The following specifications indicate a qualified SSA:\nSSA= EMPLOYEE(NAMEb=bSMITH)\nSSA= EMPLOYEE(NAMEbEQSMITH)\n3.The following specification indicates an unqualified SSA with the command code L:\nSSA= CARSb*Lb\n4.The following specification indicates a qualified SSA with a compound condition:\nSSA= EMPLOYEE(NAMEb=bSMITH&CODEbLTX'FFF0')\nView a DL/I Segment\nFollow this procedure to view a DL/I segment:\n1.Specify the following required information:\nFUNC= a DL/I get function\nSIZE= size of DL/I segment\n2.Enter the following optional information:\nSSA= the SSAs needed to retrieve the requested segment", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fcfd3aee447d-1", "text": "2.Enter the following optional information:\nSSA= the SSAs needed to retrieve the requested segment\n3.Press  Enter . The returned PCB information is displayed in the lower-right portion of the FILE screen. If the call is\nsuccessful, the segment also displays.\nExamples\n1.To retrieve the first root segment, which is 975 bytes long, specify the following, and then press Enter:\nFUNC= GU\nSIZE= 975       (or 3CF for FORMAT= D)  \n2.To sequentially process a database whose longest segment is 2000 bytes, specify the following, and then press Enter\nfor each segment:\nFUNC= GN\nSIZE= 2000      (or 7D0 for FORMAT= D)  \n 1198", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "843212dc4407-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n3.To retrieve an EMPLOYEE segment, which is 100 bytes long, specify the following, and then press Enter. (Its key is\nADAMS, and its parent is a SKILL segment with a key of ARTIST.)\nFUNC= GU\nSIZE= 100       (or 64 for FORMAT= D)   \nSSA= SKILL (SKILCODE= ARTIST) SSA=EMPLOYEE(NAME = ADAMS)\nUpdate a DL/I Segment\nFollow this procedure to update a DL/I segment:\n1.Specify the following required information:\nFUNC= GHU, GHN, or GHNP\n2.Enter the following optional information:\nSIZE= size of DL/I segment\nSSA= the SSAs needed to retrieve the requested segment\n3.Press Enter . The returned PCB information is displayed in the lower-right portion of the FILE screen. If the call is\nsuccessful, the segment is also displayed. The STAT field indicates if the call is successful. Make your changes to the\ndisplayed segment. For more information, see Change Data in the Work Area.\n4.To rewrite the updated segment, specify the following:\nFUNC= REPL\n5.Press Enter .\nThe returned PCB information is displayed.\nExample\nTo retrieve, change, and replace a SKILL segment whose key is ARTIST and whose length is 100 bytes, follow these\nsteps:\n1.Specify the following, and then press Enter :\nFUNC= GHU\nSIZE= 100           (or 64 for FORMAT= D)   \nSSA= SKILL   (SKILCODE= ARTIST)\n2.Change the segment.\n3.Specify the following :\nFUNC= REPL\n4.Press Enter .\nAdding a DL/I Segment\nFollow this procedure to add a DL/I segment:\n1.Specify the following required information:\nFUNC= ADDN", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "843212dc4407-1", "text": "1.Specify the following required information:\nFUNC= ADDN\nSIZE= size of the DL/I segment\n2.Enter the following optional information:\nDATA= data string to initialize the new segment\n3.Press Enter  to display the work area for the new segment. FILE displays the message WORK AREA OBTAINED.\n4.Change the displayed segment. For more information, see Change Data in the Work Area.\n5.To write the new segment, enter the following required information, and then press Enter :\nFUNC= ISRT\nSSA= SSAs necessary to insert segment into proper\n     position in database\n 1199", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "870a2c312554-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe returned PCB information is displayed in the lower-right portion of the screen. The segment is added if the call is\nsuccessful.\nExample\nTo add a new 100 byte SKILL segment whose key is ENGINEER, follow these steps:\n1.Specify the following, and then press Enter:\nFUNC= ADDN \nSIZE= 100\n2.Change the segment.\n3.Specify the following :\nFUNC= ISRT\nSSA= SKILL (SKILCODE= ENGINEER)\n4.Press  Enter .\nCopy a DL/I Segment\nCopy a DL/I segment from one database to another.\n1.To retrieve the segment you want to copy, specify the following, and then press Enter:\nFUNC= a DL/I get function\nPSB and DBD of source database\nSIZE= size of the DL/I segment\n2.Enter the following optional information, and then press Enter :\nSSA= SSAs needed to retrieve the requested segmentFILE displays the segment.\n3.Specify the following, and then press  Enter :\nFUNC= ADDU\nPSB and/or DBD of destination database\nSIZE= size of the DL/I segment\n4.Make any necessary changes.\n5.Specify the following, and then press Enter :\nFUNC= ISRT\nSSA= SSAs necessary to insert segment into proper\n     position in database\nThe segment is copied if the call is successful.\nExample\nTo copy a SKILL segment whose key is ARTIST and whose length is 100 bytes from one database to another, follow\nthese steps:\n1. Specify the following, and then press  Enter :\nFUNC= GU \nPSB= OLDBASE \nDBD= DBD0025 \nSIZE= 100              (or 64 for FORMAT= D)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "870a2c312554-1", "text": "SIZE= 100              (or 64 for FORMAT= D) \nSSA= SKILL (SKILCODE= ARTIST)\n2. Specify the following, and then press Enter :\nFUNC= ADDU \nPSB= NEWBASE \nDBD= DBD0010 \n 1200", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "472be4c4acf9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSIZE= 100              (or 64 for FORMAT= D)\n3. Specify the following, and then press Enter :\nFUNC= ISRT \nSSA= SKILL (SKILCODE= ARTIST)\nDelete DL/I Segments\nFollow this procedure to delete a DL/I segment:\nNOTE\nTo avoid damage to the integrity of the database, take the same precautions that you take when you program in\nDL/I.\n1.Enter the following required information:\nFUNC= GHU, GHN, or GHNP\nSIZE= size of the DL/I segment\n2.Enter the following optional information:\nSSA= the SSAs needed to retrieve the requested segment\n3.Press Enter . The returned PCB information is displayed in the lower-right area of the FILE screen. If the call is\nsuccessful, the segment is also displayed. The STAT field indicates if the call is successful.\n4.To delete the retrieved segment, enter:\n5.FUNC= DLET\n6.Press Enter . The returned PCB information is displayed.\nExample\nTo delete the SKILL segment whose key is ARTIST, follow these steps:\n1.Specify the following:\nFUNC= GHU SSA= SKILL (SKILCODE= ARTIST)\n2.Press Enter .\n3.Specify the following:\nFUNC= DLET\n4.Press Enter .\nDB2 and SQL/DS Databases\nFILE lets you access DB2 or SQL/DS databases to which it has access.\nNOTE\nFor more information, see IBM's DB2 Application Programming and SQL Guide.\nAccess the DB2 Facility\nTo start working with a DB2 database, select one of the following options:\n\u2022From a clear CICS screen, enter FILE .\n\u2022On the file display, change the data type to DB.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "472be4c4acf9-1", "text": "\u2022On the file display, change the data type to DB.\n\u2022From a clear CICS screen, enter ITST .\n\u2022On the Auxiliary Storage Menu, select Option 4.\n\u2022On the resulting menu, select Option 2, DB Database.\nThe File DB2 Facility screen displays.\n 1201", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4096720b7606-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSQL Commands\nEnter Structured Query Language (SQL) commands to perform DB2 or SQL/DS functions. FILE accepts the following\nSQL commands, subject to user authorization: SELECT, UPDATE, DELETE, INSERT, CREATE, ALTER, DROP, LABEL\nON, GRANT, REVOKE, and COMMENT ON.\nNOTE\nFor more information, see IBM's DB2 Application Programming and SQL Guide.\nObserve the following rules in entering SQL commands:\n\u2022Begin the command in column one.\n\u2022Enter only one command at a time.\n\u2022A command can exceed several lines. If the command does not fit in the allowed space, press PF4 to obtain a larger\ninput area. The command remains in the large input area for redisplay (using PF4), modification, and execution.\nScroll Through the DB2 and SQL/DS Table Display\nFILE displays DB2 and SQL/DS table data horizontally in columns and vertically in rows.\n\u2022The columns represent the fields in the database\n\u2022The rows represent the records for each member in the table\nThe following screen shows an SQL table data display.\n CA InterTest for CICS - File DB2 Facility                               \n EXEC SQL                        # Cols 012   Max Loc 00141   Loc 00001 Page 001  \n SELECT * FROM DSN8210.EMP                                                 \n                                                                                  \n 1-------2-------------3---------4----------------5----------6----------7------\n  EMPNO  | FIRSTNME    | MIDINIT | LASTNAME       | WORKDEPT | *PHONENO | *HIRE  \n --------+-------------+---------+----------------+----------+----------+-----+   \n  000210 | WILLIAM     | T       | JONES          | D11      | 0942     | 1979", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4096720b7606-1", "text": "000220 | JENNIFER    | K       | LUTZ           | D11      | 0672     | 1968 \n  000070 | EVA         | D       | PULASKI        | D21      | 7831     | 1980 \n  000230 | JAMES       | J       | JEFFERSON      | D21      | 4265     | 1966 \n  000240 | SALVATORE   | M       | MARINO         | D21      | 3780     | 1979 \n  000250 | DANIEL      | S       | SMITH          | D21      | 0961     | 1969 \n  000260 | SYBIL       | V       | JOHNSON        | D21      | 8953     | 1975 \n  000270 | MARIA       | L       | PEREZ          | D21      | 9001     | 1980 \n  000050 | JOHN        | B       | GEYER          | E01      | 6789     | 1949 \n  000090 | EILEEN      | W       | HENDERSON      | E11      | 5498     | 1970 \n  000280 | ETHEL       | R       | SCHNEIDER      | E11      | 8997     | 1967 \n  000290 | JOHN        | R       | PARKER         | E11      | 4502     | 1980 \n  000300 | PHILIP      | X       | SMITH          | E11      | 2095     | 1972", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4096720b7606-2", "text": "1 Help       2 CMND list 3 END       4 Large CMND  5 Log On     6 DataType FC    \n 7 Page bwd   8 Page fwd  9 Page 1   10 Scrl. -->  11 Scrl. <-- 12 Structure\nIn the previous screen, the column headings (EMPNO, FIRSTNME, MIDINIT, and so on) represent all fields in the table. A\nheading preceded by an asterisk indicates that the field contains null characters (for example, *PHONENO).\nThe vertical rows represent the members in the table. In this example, each member contains information for a different\nemployee. If all the rows cannot display on one screen, press PF8 to page down through the table. Press PF7 to page up\nagain.\nFILE provides the following information above the screen display:\n 1202", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eaf438b6a9c3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n# Rows  -- specifies the total number of rows in the display. FILE displays this field only if you page down to the end of the\ntable.\nCols  -- specifies the number of columns defined in the table.\nMax Loc  -- specifies the horizontal width of the screen display.\nLoc -- specifies the position of the leftmost character on display.\nPage  -- specifies the page you are currently viewing.\nDisplay Additional Columns\nIf all the columns cannot display at one time, shift the display in one of the following ways:\n\u2022Tab to the line that separates the displayed columns and press Enter . The position indicated by the cursor becomes\nthe first position on your screen.\n\u2022Place the cursor under any character in the column heading and press  Enter . The position indicated by the cursor\nbecomes the first position on your screen.\n\u2022Change the value in the Loc field by entering #nn (clear any remaining numbers), and press Enter .\nExample\nIf you enter #10 in the Loc field, the display starts with the first character in column 10.\n\u2022Change the value in the Loc field and press Enter.E\nExample\nIf you enter 50 in the Loc field, the display starts with the 50th character.\n\u2022Press PF11 to shift the display 80 characters to the left. Pressing  PF10  shifts the display back 80 characters to the\nright.\nExample\nIn the previous display, the Loc field indicates that the display begins with position 1; the Max Loc field indicates that the\nentire table display is 141 characters wide. To see the remaining columns, you must scroll the display. If you tab the cursor\nto the line preceding HIREDATE and press Enter , FILE displays the following screen:\n        CA InterTest for CICS  - File DB2 Facility        \u00ee", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eaf438b6a9c3-1", "text": "CA InterTest for CICS  - File DB2 Facility        \u00ee         \n EXEC SQL  # Rows 00032          # Cols 012   Max Loc 00141   Loc 00075 Page 002  \n SELECT * FROM DSN8210.EMP                                                      \n                                                                                  \n 7------------8---------9---------10---11-----------12------\n |*HIREDATE |*JOBCODE |*EDUCLVL |*SEX |*BRTHDATE   |*SALARY |               \n +----------+---------+---------+-----+----------+----------+\n | 19790411 | 52      | 17      | M   | 19530223 | 18270.00 |             \n | 19680829 | 55      | 18      | F   | 19480319 | 29840.00 |             \n | 19800930 | 56      | 16      | F   | 19530526 | 36170.00 |             \n | 19661121 | 53      | 14      | M   | 19350530 | 22180.00 |             \n | 19791205 | 55      | 17      | M   | 19540331 | 28760.00 |             \n | 19691030 | 52      | 15      | M   | 19391112 | 19180.00 |             \n | 19750911 | 52      | 16      | F   | 19361005 | 17250.00 |             \n | 19800930 | 55      | 15      | F   | 19530526 | 27380.00 |             \n | 19490817 | 58      | 16      | M   | 19250915 | 40175.00 |", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eaf438b6a9c3-2", "text": "| 19700815 | 55      | 16      | F   | 19410515 | 29750.00 |             \n | 19670324 | 54      | 17      | F   | 19360328 | 26250.00 |             \n | 19800530 | 42      | 12      | M   | 19460709 | 15340.00 |             \n 1203", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "104fd55add1c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n | 19720619 | 48      | 14      | M   | 19361027 | 17750.00 |             \n | 19640912 | 43      | 12      | F   | 19310421 | 15900.00 |             \n _______________________________________________________________________________  \n 1 Help       2 CMND list 3 END       4 Large CMND  5 Log On      6 DataType FC    \n 7 Page bwd   8 Page fwd  9 Page 1    10 Scrl. -->  11 Scrl. <-- 12 Structure\nNow you can view the other columns in the table.\nNOTE\nThe Loc field now indicates that the display begins with position 75.\nView a Structured Display\nTo see a structured display of the data table columns, press PF12 . The structured display lists each column from the\nData Table display in left-to-right column order. The following screen shows the structured display of the columns in the\nprevious screen.\n      CA InterTest for CICS   - File DB2 Facility            \nEXEC SQL                                                   Loc 00001           \nSELECT * FROM DEVMPL.EMP\n-------------------------------------------------------------------------\nCOL | COLUMN NAME                    | DATATYPE  | LENGTH | CODE | NULL |\n----+--------------------------------+-----------+--------+------+------+\n  1 | EMPNO                          | Char      |      6 |  452 |   No |\n  2 | FIRSTNME                       | Char  Var |     12 |  448 |   No |\n  3 | MIDINIT                        | Char      |      1 |  452 |   No |\n  4 | LASTNAME                       | Char  Var |     15 |  448 |   No |", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "104fd55add1c-1", "text": "5 | WORKDEPT                       | Char      |      3 |  453 |  Yes |\n  6 | PHONENO                        | Char      |      4 |  453 |  Yes |  \n  7 | HIREDATE                       | Date Type |     10 |  385 |  Yes |  \n  8 | JOB                            | Char      |      8 |  453 |  Yes |  \n  9 | EDLEVEL                        | Integer S |      2 |  501 |  Yes | \n 10 | SEX                            | Char      |      1 |  453 |  Yes | \n 11 | BIRTHDATE                      | Date Type |     10 |  385 |  Yes | \n 12 | SALARY                         | Decimal   |   9. 2 |  485 |  Yes | \n 13 | BONUS                          | Decimal   |   9. 2 |  485 |  Yes | \n 14 | COMM                           | Decimal   |   9. 2 |  485 |  Yes |\n______________________________________________________________________________\n1 Help       2 CMND list 3 END       4 Large CMND  5 Log On     6 DataType FC\n7            8           9          10            11           12 Data Table\nEach row of the Structured Display gives the following information about a column on the Data Table display:\n\u2022Relative (left-to-right) column number\n\u2022Name\n\u2022Data type (such as character and integer)\n\u2022Length\n\u2022Data type code\n\u2022Whether the field contains null characters\nPress PF12  to redisplay the table display.\nSelect the starting column before redisplaying the Data Table in one of the following ways:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "104fd55add1c-2", "text": "Select the starting column before redisplaying the Data Table in one of the following ways:\n\u2022Change the value in the LOC field to indicate a starting display position. To do this, enter nn, clear any remaining LOC\nfield numbers, and press PF12 .\n 1204", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f58ed550a9c2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nExample\nIf you enter 22 in the LOC field, the display starts at position 22.\n\u2022Change the value in the LOC  field to indicate a starting column number. To do this, enter #nn, clear any remaining LOC\nfield numbers, and press PF12 .\nExample\nIf you enter #9 in the LOC field, the display starts with the first character in column 9.\nPF Keys\nThe PF keys perform the functions shown in the following table when you are using SQL.\nPF Key Function\nPF1 Help initiates the InterTest for CICS online Help facility.\nPF2 CMND List displays a list of the last six commands entered. You\ncan re-execute or modify these commands.\nPF3 END or Clear terminates the FILE facility.\nPF4 Large CMND extends the command input area.\nPF5 Log On/Off toggles between logging on/logging off when the\nAUDIT option is N.\nPF6 Datatype FC changes the DATATYPE to FC (File Control).\nPF7 Page Bwd scrolls the current display one page backward. The key\nsetting indicates First Page when you are viewing the first page of\nthe display.\nPF8 Page Fwd scrolls the current display one page forward. The key\nsetting indicates Last Page when you are viewing the last page of\nthe display.\nPF9 Page 1 returns to the first page of the table data display.\nPF10 ==> scrolls the current display 80 characters to the right.\nPF11 <== scrolls the current display 80 characters to the left.\nPF12 Structure toggles between structured column definitions and table\ndata displays.\nThe legends next to the PF keys show as needed. For example, if the table display contains more rows and columns than", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f58ed550a9c2-1", "text": "are shown on one screen, the legends next to PF7 through PF11 display. If the table display is shown on one screen, the\nlegends for these PF keys do not display.\nIf you are on the first screen and page backward (PF7), the legend changes from Page bwd  to First Page  and is\nhighlighted. Similarly, if you try to page forward past the last row, the legend for PF8 changes from Page fwd  to a\nhighlighted Last page .\nFILE Functions for DB2 and SQL/DS Databases\nThis section shows how to perform the following functions:\n\u2022Select columns of data from a table\n\u2022Update a column of data in a table\n\u2022Delete a row from a table\n\u2022Insert a row into a table\n\u2022Confirm changes\n 1205", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cd2d7e5a3676-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nYou also might be able to perform other functions depending on your security authorization.\nSelect Columns of Data\nUse the SELECT command to display one column, many columns, or all columns in a table. The SELECT command also\nlets you set conditions to determine whether or not a column is displayed.\nExample\nTo view all columns in a table, specify the following, and then press Enter :\nSELECT * FROM DSN8130.TEMPL\nFILE\nDisplays all of the data in the table.\nUpdate a Column\nThe UPDATE command lets you update a column. Set conditions to determine when the update should be performed.\nExample\nTo change the WORKDEPT column for an employee, specify the following, and then press Enter :\nUPDATE DSN8130.TEMPL SET WORKDEPT = `A15' WHERE EMPNO = `000010'\nThis command instructs FILE to change the WORKDEPT column in table DSN8130.TEMPL for the employee whose\nEMPNO is 000010.\nBefore performing the update, you are asked to confirm the change. For more information, see Confirm Changes.\nDelete a Row\nUse the DELETE command to delete a row or several rows of data. Set conditions to determine when the deletion should\nbe performed.\nExample\nTo delete a department from a table, specify the following, and then press Enter :\nDELETE FROM DSN8130.TEMPL WHERE WORKDEPT = 'D11' \nThis command instructs FILE to delete from table DSN8130.TEMPL all rows in which the WORKDEPT is D11.\nBefore performing the deletion, FILE displays a second screen indicating how many rows will be deleted and asking you\nto confirm the deletion. Enter C to confirm the deletion or R to cancel it. If you enter C, FILE performs the deletion and\ninforms you that the command was successfully executed.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cd2d7e5a3676-1", "text": "informs you that the command was successfully executed.\nInsert a Row\nThe INSERT command lets you insert an entire row of data. First specify the column names, and then specify the values\nto insert into each column. Set conditions to determine when the insertion should be performed.\n\u2022Insert only one row of data at a time.\n\u2022You must specify data for each column in the table, except for columns that contain nulls, which are identified by\nasterisks.\nExample\nTo insert employee data into a table, specify the following, and then press Enter :\n 1206", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aba468f40982-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nINSERT INTO DSN8130.TEMPL \n(EMPNO,FIRSTNME,MIDINIT,LASTNAME,WORKDEPT,SALARY)\nVALUES(`010200',`JAMES',`S',`NEWMAN',`D11',27500)\nFILE inserts a row into table DSN8130.TEMPL. This row contains six columns of information for employee James S.\nNewman.\nBefore performing the insertion, FILE displays a second screen asking you to confirm or cancel the insertion. Enter C to\nconfirm or R to cancel the insertion.\nConfirm Changes\nWhen you instruct FILE to update a column, or delete or insert a row, the File DB2 Facility screen displays.\nSpecify one of the following values:\n\u2022Enter C to confirm that the change is to be executed.\nFILE executes the change and indicates that the command has been successfully executed.\n\u2022Enter R to cancel the change.\nRedisplay SQL Commands\nTo redisplay the last six commands you have entered, press PF2.\nDo one of the following to select any command to re-execute or modify:\n\u2022Enter x in the field to the left of a command to execute it\n\u2022Enter m to modify a command\nNOTE\nIf you do not enter any data, any PF key returns you to either the table data display or structured display.\nView the CICS Attachment Facility (z/OS Users Only)\nThe Resource Control Table (RCT), or CICS DB2 attachment facility, contains the information required for CICS to\nestablish its connection to DB2. The FILE transaction's DB2 facility lets you view information and statistics on each entry\nin the active RCT.\nThe display format is presented as if the RCT existed as a DB2 table. This display is similar to the information provided by", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aba468f40982-1", "text": "the IBM-supplied DSNC DISP STAT command, but provides more complete and easily accessed information.\nThe following table summarizes the differences between the InterTest for CICS DSNCRCT Display and the CICS DSNC\nDisplay.\nInterTest for CICS DSNCRCT Display CICS DSNC Display\nGives all RCT transactions Gives only the first transaction in a group\nUser transactions appear in alphabetical order Transactions in RCT order\nShows the Authorization ID Does not show the Authorization ID\nTo display the RCT, enter the keyword DSNCRCT in the DB2 command area. InterTest for CICS redisplays the keyword\nas SELECT * FROM DSNCRCT for compatibility with other DB2 data table displays; however, SELECT command clauses\nare not supported with DSNCRCT.\nThe InterTest for CICS RCT display includes 15 columns of information, requiring three panels for display. To scroll to the\nnext or previous panel of columns, press PF11 or PF10. To see a Structured Display of the columns, press PF12 .\nThe following screen shows the initial RCT display showing columns 1 to 8.\n 1207", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "46b11dc0bebb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n     CA InterTest for CICS  - File DB2 Facility          \nEXEC SQL                        # Cols 015   Max Loc 00190   Loc 00001 Page 001 \nSELECT * FROM DSNCRCT3                                                          \n                                                                                \n1---------2------------3------------4-------5-------6---------7--------8-------   \n Tran Id  |  *Plan Id  |  *Auth Id  | Auths | Calls | Commits | Aborts | Waits|\n----------+------------+------------+-------+-------+---------+--------+------+    \n DSNC     |            |            |     0 |     0 |       0 |      0 |     0|\n POOL     |  DSN8CC21  |            |     0 |     0 |       0 |      0 |     0|\n CNTL     |  FILE21    |  INTRTST   |     0 |     0 |       0 |      0 |     0|\n CORE     |  FILE21    |  INTRTST   |     0 |     0 |       0 |      0 |     0|\n DB2A     |  ASMSQL    |  DEVMPL    |     0 |     0 |       0 |      0 |     0|\n DB2C     |  COBSQL    |  DEVMPL    |     0 |     0 |       0 |      0 |     0|\n DB2P     |  PLISQL    |  DEVMPL    |     0 |     0 |       0 |      0 |     0|", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "46b11dc0bebb-1", "text": "D8CS     |  DSN8CC21  |            |     0 |     0 |       0 |      0 |     0|\n D8PP     |  DSN8CQ21  |            |     0 |     0 |       0 |      0 |     0|\n D8PS     |  DSN8CP21  |            |     0 |     0 |       0 |      0 |     0|\n D8PT     |  DSN8CH21  |            |     0 |     0 |       0 |      0 |     0|\n D8PU     |  DSN8CH21  |            |     0 |     0 |       0 |      0 |     0|\n FILE     |  FILE21    |  INTRTST   |     0 |     0 |       0 |      0 |     0|\n HELP     |  FILE21    |  INTRTST   |     0 |     0 |       0 |      0 |     0|\n_______________________________________________________________________________ \n1 Help       2 CMND list 3 END       4 Large CMND  5 Log On     6 DataType FC   \n7 Page bwd   8 Page fwd  9 Page 1   10 Scrl.  ->  11 Scrl. <-   12 Structure \nThe second panel shows all the DB2 thread statistics, which are kept in the RCT.\nThe third panel contains two columns that deal with dynamic plan selection.\nFollowing are descriptions for the columns on all three panels.\nTran ID -- Lists all CICS transactions that issue SQL calls. The first two entries are system transactions; the rest are user", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "46b11dc0bebb-2", "text": "transactions listed in alphabetical order. The system transactions are defined next.\n\u2022DSNC is the command processor transaction; it does not have an associated plan.\n\u2022POOL defines threads that are shared by some or all of the CICS transactions. These threads are allocated to\ntransactions only for a CICS unit of work. Consider them short-term threads. Any RCT entry that is specified to\noverflow to the pool can use them.\nPlan ID  -- Indicates the plan name associated with the transaction.\nAuth ID  -- Indicates the authorization identification concatenated to the table name when the associated transaction is\nused to access a data table.\nAuths  -- Indicates the number of authorizations (sign-on invocations) for transactions associated with this entry.\nCalls  -- Indicates the number of SQL calls issued by transactions associated with this entry.\nCommits  -- Indicates the number of sync points issued for transactions associated with this entry.\nAborts  -- Indicates the number of sync point rollbacks and abends issued for transactions associated with this entry.\nWaits -- Indicates the number of times that all available threads for this entry were busy and the associated transactions\nhad to either wait or be diverted to the pool.\nMax Thread  -- Indicates the maximum number of threads the attachment facility should be prepared to connect for this\ntransaction group.\n 1208", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c3fab1eaa673-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMax Act Thread  -- Indicates the maximum number of threads the attachment facility should allow to be connected for this\ntransaction, group, or pool before requests must either wait or be diverted to the pool.\nHigh Thread  -- Indicates the maximum number of threads required by transactions associated with this entry since the\nconnection was started. This number includes transactions forced to wait on a thread or diverted to the pool.\nCurr Thread Lvl  -- Indicates the current number of threads associated with this entry at this time.\nThread Subtask  -- Indicates the maximum number of z/OS subtasks or threads that should be started when the\nattachment facility is started.\nExit Prog ID  -- Indicates the name of the exit program, which dynamically allocates the plan name for transactions\nassociated with this entry.\nDym User Area  -- Displays the contents of the fullword in the RCT entry reserved for dynamic exit program use.\nNOTE\nThe RCT statistics are kept on an entry basis, not on a transaction basis. This means that all transactions in a\ngroup (sharing the same Plan ID) will have the same statistics.\nBDAM Files\nThe FILE transaction performs any BDAM function allowed in your CICS system.\nNOTE\nYou might want to consult the IBM CICS/VS Application Programmer's Reference Manual  for information on\nusing BDAM files. This manual helps you formulate your requests correctly and explains the meaning of many\nresponses you receive from FILE. check reference ?\nTo begin processing a BDAM file, first make sure you are viewing the correct screen. From the Auxiliary Storage Menu,\nselect option 1 Files.\nThe DATATYPE= field should be set to FC. If not, press PF6 or Enter :\nDATATYPE=FC\nThen enter:\nFILEID= file name\nThe other information you enter depends on the function you want to perform.\nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c3fab1eaa673-1", "text": "The other information you enter depends on the function you want to perform.\nNOTE\nUndefined record type files are not supported.\nFILE Screen Layout for BDAM Files\nThe following screen shows a blank header area on a FILE screen for BDAM files. For examples of the complete screen,\nsee Dump Format, Character Format, Vertical Format, and Structured Format.\nDATATYPE= FC FILEID=          MODE=     LOG=     TODEST=         PASSWORD=       \n FUNC=      SUBFUNC=      RETMETH=        ARGTYP=     SRCHTYP=                    \n MESSAGE=                                                                         \n  RETNRCID=                                                        CHGELEN=       \n     RCID=                                                                        \n     DATA=                                                         SIZE=          \n FORMAT= D 00112233 44556677 8899AABB CCDDEEFF  *0123456789ABCDEF*                \n 1209", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "62fbdfa426fc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n LOC 0000  ........ ........ ........ ........  ................\nField Function\nDATATYPE Identifies the type of data organization. This must be FC.\nFILEID Specifies the name of the BDAM file.\nMODE Identifies the FILE operation, such as browse, update, add, add in\nmass insertion. This field is blank if you are viewing  a record.\nLOG Specifies whether FILE's logging facility is on or off.\nTODEST Identifies a transient data destination (when a work area is copied)\nor a dump identification (when a work area is dumped).\nPASSWORD Must contain a four-character password if the file is password\nprotected.\nFUNC Specifies the FILE function. When this field contains a function\ncode, it is executed if you press Enter. In addition to common FILE\nfunctions, enter the following commands: BEGB, DEL, ENDB,\nGET, GETU, NEXT, PREV, PUT, REL.\nSUBFUNC Modifies a FUNC specification.\nRETMETH Identifies the RCID field (BDAM files only).\nARGTYP Must contain RBA or XRBA when working with ESDS files.\nSRCHTYP Specifies how RCID information is processed (KSDS files only).\nMESSAGE Contains FILE messages. Also specify messages here when\nFUNC=COPY or FUNC=DUMP.\nRETNRCID Contains the record key of the retrieved record.\nCHGELEN Specifies the number of bytes changed in the work area when\nFUNC=CHGE.\nRCID Identifies the record to be processed.\nDATA Contains data needed to perform certain FILE functions.\nSIZE Specifies the record size or the number of records to be searched.\nFORMAT Specifies the format in which the record is displayed.\nUSE Specifies the program and structure for structured format.\nLOC Specifies a location within a record.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "62fbdfa426fc-1", "text": "USE Specifies the program and structure for structured format.\nLOC Specifies a location within a record.\nSome fields are used only for certain tasks. The discussion of each FILE function indicates which fields must be specified.\nWhen a record displays, its FILE information is on the lower-right portion of the screen. This information includes the\nfollowing:\n\u2022DSORG (data organization)\n\u2022RECFM (record format)\n\u2022LRECL (record length)\n\u2022BLKSIZE (blocksize)\n\u2022KEYPOS (key position)\n\u2022KEYLEN (key length)\n\u2022STRNO (string number)\nBeneath this information is a list of the functions you can perform, including READ, ADD, UPDATE, BROWSE, DELETE.\n 1210", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4b7af74263ba-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFILE Functions for BDAM Records\nThe following FILE functions are discussed in this section:\n\u2022Viewing a BDAM record\n\u2022Browsing a BDAM file\n\u2022Searching for a data string\n\u2022Updating a BDAM record\n\u2022Adding a new BDAM record\nView a BDAM Record\nTo view a record, specify the READ operation on the FILE definition.\n1. Enter the following information:\nFUNC=GET\nRCID=record identification\nand, if appropriate, specify the following optional  fields:\nRETMETH=KEY     (Use if RCID contains a deblocking key) \nRETMETH=RELREC  (Use if RCID contains a deblocking relative record number)  \n2. Press Enter . The following information appears on the FILE screen:\nThe MESSAGE= field shows the following message RECORD OBTAINED FOR VIEWING\n\u2022The MODE= field becomes blank\n\u2022The RETNRCID= field contains the returned record's identification\n\u2022The SIZE= field gives the size of the data in the record, which is the size of the work area\n\u2022The data is displayed, beginning with the byte indicated in the LOC= field\nExample\nTo view a BDAM record that is the sixth record on track 3 in the file BDAMFIL, follow this procedure.\n1.Enter the following:\nFILEID=BDAMFIL\nFUNC=GET\nRCID=X'000306'\n2.Press Enter.\nBrowse a BDAM File\nTo browse a file, specify the BROWSE operation on the FILE definition.\n1.Press PF4 or complete the FUNC= field as shown next:\nFUNC=BEGB\nand, if appropriate, complete the following optional  fields:\nRCID= record identification where browse begins", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4b7af74263ba-1", "text": "RCID= record identification where browse begins\nRETMETH=KEY       (Use if RCID contains a deblocking key)\nRETMETH=RELREC    (Use if RCID contains a deblocking relative record number)\n2.Press  Enter . The first record displays and the following information is on the FILE screen:\n\u2013The MESSAGE= field shows the message BROWSE BEGUN\n\u2013The MODE= field indicates BROWSE\n\u2013The FUNC= field contains the function NEXT\n 1211", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8394081aaa4c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n3.To view the records in ascending  sequence, complete the FUNC= field as shown following, and then press Enter :\nFUNC=NEXT\nThe FILE display screen shows the next sequential record.\nNOTE\nYou cannot browse a BDAM file in descending sequence.\nTo interrupt a browse operation to do something else, such as scroll the display, you must erase the FUNC=\nfield.\n4.There are two ways to terminate a browse operation: explicitly and implicitly.\n\u2013To terminate a browse explicitly , press  PF4  or specify the following, and press Enter :\nFUNC=ENDB\nThe following information is on the FILE screen:\n\u2022The MESSAGE= field shows the message BROWSE TERMINATED\n\u2022The MODE= field becomes blank\n\u2013To terminate a browse implicitly , specify one of the following entries and press Enter :\nFUNC=GET\nFUNC=GETU\nFUNC=ADDN\nFUNC=ADDU\nThe information on the FILE screen reflects the function you selected.\nSearch for a Data String\nThis function is valid only for files with the browse capability. Check the lower-right corner of the FILE screen for the\nproperties of the file before attempting to use this function.\n1.Complete the following fields as shown next:\nFUNC= SRCH\nRCID= record id of first record to be searched\nDATA= search argument\nLOC= position in the record to search\nor\nLOC=ANY\n\u2013LOC= position  instructs FILE to look for the search argument only at the specified position.\n\u2013LOC=ANY instructs FILE to look for the search argument in the entire record.\nIn addition, there is an optional  field:\nSIZE= number of records to be searched (default=1)\n2.Press Enter . If a match is found, the record displays, and the following information is on the FILE screen:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8394081aaa4c-1", "text": "\u2013The MESSAGE= field shows the message DATA HAS BEEN LOCATED.\n\u2013The RETNRCID= field contains the returned record's identification.\n\u2013The LOC= field contains the location of the found data.\n\u2013If no match is found, the MESSAGE= field shows the message DATA NOT FOUND.\nUpdate a BDAM Record\nTo update a record, specify the UPDATE operation on the FILE definition.\n1.Complete the following fields:\nFUNC=GETU\nRCID= record identification\n 1212", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b00df88a9343-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nand, if appropriate, the following optional  field:\nRETMETH=KEY       (if RCID contains a deblocking key)\nRETMETH=RELREC    (if RCID contains a deblocking relative record number)               \nNOTE\nYou can update any record that was obtained by a GET, BEGB, NEXT, or PREV function. If you already have\na record, go to Step 3.\n2.Press  Enter , and the following information appears on the FILE screen:\n\u2013The MESSAGE= field shows the message RECORD OBTAINED FOR UPDATE\n\u2013The MODE= field indicates UPDATE\n\u2013The RETNRCID= field contains the returned record's identification\n\u2013The SIZE= field gives the size of the data in the record (the size of the work area)\n\u2013The data displays, beginning with the byte indicated in the LOC= field\n3.Make any necessary changes to the displayed record's data. However, the record will not change until you perform\nStep 4 and rewrite the updated record. To rewrite the updated record, complete the following fields, and then press\nEnter :\nFUNC=PUT\nRCID= record identification\nand, if appropriate, the following optional  field:\nSIZE= size of record's data   (required for variable length)    \nThe following information appears on the FILE screen:\n\u2013The MESSAGE= field shows the message RECORD UPDATED.\n\u2013The MODE= field becomes blank.\n\u2013The data in the work area continues to display.\n4.If you change your mind and decide not to update the record at this time, complete the FUNC= field as shown next,\nand press Enter :\nFUNC=REL\nThe following information appears on the FILE screen:\n\u2013The MESSAGE= field shows the message FWA HAS BEEN RELEASED.\n\u2013The MODE= field becomes blank.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b00df88a9343-1", "text": "\u2013The MODE= field becomes blank.\n\u2013The data in the work area continues to display.\nAdd a New BDAM Record\nTo add a record, specify the ADD operation on the FILE definition.\nNOTE\nBefore reading this section, consult the BDAM Data Sets section of the File Control Section  in the IBM CICS/VS\nApplication Programmer's Reference Manual .\n1.Complete one of the following fields:\nFUNC=ADDN      (to obtain a new work area)  \nFUNC=ADDU      (to use the data in the existing work area)  \nComplete the following optional  field, if appropriate:\nDATA= characters\n\u2013If you enter FUNC=ADDN, the characters you type in the DATA= field are those that will fill the work area.\n\u2013If you enter FUNC=ADDU, the characters you type in the DATA= field will fill the newly obtained data space (the\nnew work area might be larger than the present one for a variable-length file).\n2.Press Enter . The following information displays on the FILE screen:\n 1213", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eb9a2feea77f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2013The MESSAGE= field shows the message WORK AREA OBTAINED.\n\u2013The MODE= field indicates ADD.\n\u2013The SIZE= field gives the size of the work area (the size is the maximum permitted for this particular file).\n\u2013The obtained work area displays, beginning with the byte indicated in the LOC= field.\n3.Make any necessary changes to the newly obtained work area.\n4.To write the newly added record, complete the following fields as follows:\nFUNC=PUT\nRCID= record identification\nand, if appropriate, the following optional  field:\nSIZE= size of record's data  (required for variable length)\nPress Enter . The following information appears on the FILE screen:\n\u2013The MESSAGE= field shows the message RECORD ADDED.\n\u2013The MODE= field becomes blank.\n\u2013The data in the work area continues to display.\n5.If you change your mind and decide not to add any records at this time, complete the FUNC= field as shown following,\nand press Enter :\nFUNC=REL\nThe following information appears on the FILE screen:\n\u2013The MESSAGE= field shows the message FWA HAS BEEN RELEASED.\n\u2013The MODE= field becomes blank.\n\u2013The data in the work area continues to display.\nTemporary Storage\nThe FILE transaction performs any temporary storage function allowed in your CICS system.\nTo begin processing temporary storage, first make sure you are viewing the correct screen. From the Auxiliary Storage\nMenu, select option 5 TS Queues. The DATATYPE= field should be set for TS. If not, press PF6 or enter:\nDATATYPE=TS\nThe other information you enter depends on the function you want to perform.\nFILE Screen Layout for Temporary Storage\nThe following screen shows a blank header area on a FILE screen for temporary storage. For examples of the complete", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eb9a2feea77f-1", "text": "screen, see Dump Format, Character Format, Vertical Format and Structured Format.\n DATATYPE= TS                       LOG=OFF     TODEST=              \n FUNC=      SUBFUNC=      STORFAC=                                   \n MESSAGE=                                                                         \n     RCID=                                                        CHGELEN=       \n     DATA=                                                         SIZE=0000      \n FORMAT= D 00112233 44556677 8899AABB CCDDEEFF  *0123456789ABCDEF*                \n LOC 0000  ........ ........ ........ ........  ................                \n \n \n-------------------------------------------------------------------------------  \n 1 Help       2 Format C   3 End        4            5            6 DataType FC \n 7 Page bwd   8 Page fwd   9 Caps Off  10 Top       11 Bottom    12\n 1214", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4d1d1608b063-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe fields provide the following information:\nField Function\nDATATYPE Identifies the type of data organization. This must be TS.\nLOG Specifies whether FILE's logging facility is on or off.\nTODEST Identifies a transient data destination (when a work area is copied)\nor a dump identification (when a work area is dumped).\nFUNC Specifies the FILE function. When this field contains a function\ncode, it is executed if you press Enter . In addition to common FILE\nfunctions, enter the following commands: GET, GETQ, PURG,\nPUT, PUTQ, REL.\nSUBFUNC Modifies a FUNC specification.\nSTORFAC When writing a record (FUNC=PUT or PUTQ), specifies the type\nof storage: AUX (auxiliary) or MAIN.\nENTRY Specifies the relative position of a record in a temporary storage\nqueue. Required for FUNC=GETQ, PUTQ, and SRCH.\nMESSAGE Contains FILE messages. Also specify messages here when\nFUNC=COPY or FUNC=DUMP.\nCHGELEN Specifies the number of bytes changed in the work area when\nFUNC=CHGE.\nRCID Identifies the record or queue to be processed.\nDATA Contains data needed to perform certain FILE functions.\nSIZE Specifies the record size or the number of records to be searched.\nFORMAT Specifies the format in which the record is displayed.\nUSE Specifies the program and structure for structured format.\nLOC Specifies a location within a record.\nSome fields are used only for certain tasks. The discussion of each FILE function indicates which fields must be specified.\nFILE Functions for Temporary Storage\nThe following FILE functions are discussed in this section:\n\u2022Viewing a temporary storage queue record\n\u2022Adding a new temporary storage queue record\n\u2022Purging a temporary storage queue\n\u2022Searching a temporary storage queue for a data string", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4d1d1608b063-1", "text": "\u2022Purging a temporary storage queue\n\u2022Searching a temporary storage queue for a data string\nViewing a Temporary Storage Queue Record\nFollow this procedure to view a temporary storage queue record:\n1.Complete the following fields:\nFUNC=GETQ\nRCID= temporary storage queue identification\nENTRY= record's relative position in the queue  (default=1)\n2.Press Enter. The record's data is displayed on the FILE screen with the following information:\n\u2013The MESSAGE= field shows the message TS QUEUE RECORD RETRIEVED.\n\u2013The SIZE= field gives the size of the retrieved record's data.\n 1215", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2a0ead2a72d0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAdd a New Temporary Storage Queue Record\nFollow this procedure to add a temporary storage queue record:\n1.Specify one of the following:\nFUNC=ADDN   (to obtain a new work area) \nFUNC=ADDU   (to use the data in the existing work area) \nThen complete the SIZE= field as shown next:\nSIZE= size of data area\nIn addition, complete the following optional  field, if appropriate:\nDATA= characters\n\u2013If you enter FUNC=ADDN, the characters you type in the DATA= field will fill the work area.\n\u2013If you enter FUNC=ADDU, the characters you type in the DATA= field will fill the newly obtained data space (if the\nnew work area is larger than the present one).\n2.Press Enter . The following information displays on the FILE screen:\n\u2013The MESSAGE= field shows the message WORK AREA OBTAINED.\n\u2013The SIZE= field gives the size of the work area (the size will be the maximum permitted).\n\u2013The obtained work area is displayed, beginning with the byte indicated in the LOC= field.\n3.Make any necessary changes to the newly obtained work area.\n4.To write the newly added record, complete the following fields:\nFUNC=PUTQ\nENTRY= record's relative position in queue\nRCID= temporary storage identification\nSIZE= size of data in the record\nand, if appropriate, the following two optional  fields:\nSUBFUNC= REPL   (to replace an existing record) \nSTORFAC=AUX\nor\nSTORFAC=MAIN\n\u2013Use STORFAC=AUX to place the record on a direct access storage device. This is the default.\n\u2013Use STORFAC=MAIN to place the record in main storage.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2a0ead2a72d0-1", "text": "\u2013Use STORFAC=MAIN to place the record in main storage.\n5.Press Enter . The following information displays on the FILE screen:\n\u2013Without SUBFUNC=REPL, the MESSAGE= field shows the message TS QUEUE RECORD WRITTEN.\n\u2013With SUBFUNC=REPL, the MESSAGE= field shows the message TS QUEUE RECORD WRITTEN AND\nREPLACED.\n\u2013The SIZE= field gives the size of the work area.\n\u2013The work area displays, beginning with the byte indicated in the LOC=field.\nExamples\nYou want to add a new 100-byte record to a temporary storage queue called TEMPSTO1, which resides in auxiliary\nstorage. This record is to be the last record in the queue.\nSpecify the following, and then press  Enter :\nFUNC=ADDN \nRCID=C'TEMPSTO1'\nSIZE= 100 or 64         (for FORMAT=D)  \nMake changes to the work area.\nSpecify the following, and then press  Enter :\n 1216", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "18bcce57ff96-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFUNC=PUTQ \nRCID=C'TEMPSTO1'\nTo replace record 5 in a temporary storage queue named TEMPSTO2, which resides in main storage, using the work area\nfrom Example 1:\nSpecify the following, and then press Enter :\nFUNC=ADDU\nMake changes to the work area.\nSpecify the following, and then press  Enter :\nFUNC=PUTQ \nENTRY=05 \nRCID=C'TEMPSTO2' \nSUBFUNC=REPL \nSIZE= 100 or 64     (for FORMAT=D)  \nSTORFAC=MAIN\nPurge a Temporary Storage Queue\nFollow this procedure to purge a temporary storage queue:\n1.Complete the following fields:\nFUNC=PURG\nRCID= temporary storage queue identification\n2.Press Enter . The following information is on the FILE screen:\n\u2013The MESSAGE= field shows the message   xxx RECORDS DELETED.\n\u2013The SIZE= field gives the size of the work area.\n\u2013The work area displays, beginning with the byte indicated in the LOC= field.\nSearch a Temporary Storage Queue for a Data String\nFollow this procedure to search a temporary storage queue for a data string.\n1.Complete the following fields:\nFUNC=SRCH\nENTRY= relative record position to start search\nRCID= temporary storage queue identification\nDATA= search argument\nLOC= position in record to search for the data string\nor\nLOC=ANY     (to search the entire record for the data string)   \nIn addition, complete the following optional  field:\nSIZE= number of records to search       (default=1) \n2.Press Enter . If a match is found, the record containing the data displays, starting at the location where the data was", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "18bcce57ff96-1", "text": "found. The following information also appears on the FILE screen:\n\u2013The MESSAGE= field shows the message DATA HAS BEEN LOCATED.\n\u2013If no match is found, the MESSAGE= field shows the message DATA NOT FOUND.\n\u2013The ENTRY= field contains the returned record's relative position in the queue.\n\u2013The LOC= field contains the location of the found data.\n 1217", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7c7a68056f31-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nExample\nTo scan ten records in the temporary storage queue named TEMPSTO1 starting at the third record for the data string\nTEST, if that data is in location 20 in the record, specify the following, and then press Enter :\nFUNC=SRCH\nENTRY=03\nRCID=C'TEMPSTO1'\nDATA=C'TEST'\nLOC=00020 OR 0013       (for FORMAT=D)  \nSIZE=0010 OR 000A       (for FORMAT=D)  \nTransient Data\nThe FILE transaction performs any transient data function allowed in your CICS system.\nTo begin processing transient data, first make sure you are viewing the correct screen. From the Auxiliary Storage Menu,\nselect option 5 TD Queues. The DATATYPE= field should be set at TD. If not, press PF6 or Enter :\nDATATYPE=TD\nThe other information you enter depends on the function you want to perform.\nFILE Screen Layout for Transient Data\nThe next screen shows a blank header area on a FILE screen for temporary storage. For examples of the complete\nscreen, see Dump Format, Character Format, Vertical Format and Structured Format.\n DATATYPE= TD                       LOG=OFF     TODEST=              \n FUNC=      SUBFUNC=     \n \n                                   \n MESSAGE=                                                         CHGELEN=      \n     DATA=                                                         SIZE=0000    \n FORMAT= D 00112233 44556677 8899AABB CCDDEEFF  *0123456789ABCDEF*              \n LOC 0000  ........ ........ ........ ........  ................                \n \n \n \n ------------------------------------------------------------------------------ \n 1 Help       2 Format C   3 End        4            5            6 DataType FC", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7c7a68056f31-1", "text": "7 Page bwd   8 Page fwd   9 Caps Off  10 Top       11 Bottom    12 \nThe fields provide the following information:\nField Function\nDATATYPE Identifies the type of data organization. This must be TD.\nDESTID Specifies the name of the transient data, as defined in the DCT.\nLOG Specifies whether FILE's logging facility is on or off.\nTODEST Identifies a transient data destination (when a work area is copied)\nor a dump identification (when a work area is dumped).\nFUNC Specifies the FILE function. When this field contains a function\ncode, it is executed if you press Enter. In addition to common FILE\nfunctions, enter the following commands: GET, PUT.\nSUBFUNC Modifies a FUNC specification.\n 1218", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cb5de2c0466d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMESSAGE Contains FILE messages. Also specify messages here when\nFUNC=COPY or FUNC=DUMP.\nCHGELEN Specifies the number of bytes changed in the work area when\nFUNC=CHGE.\nRCID Identifies the record or queue to be processed.\nDATA Contains data needed to perform certain FILE functions.\nSIZE Specifies the record size or the number of records to be searched.\nFORMAT Specifies the format in which the record is displayed.\nUSE Specifies the program and structure for structured format.\nLOC Specifies a location within a record.\nSome fields are used only for certain tasks. The discussion of each FILE function indicates which fields must be specified.\nFILE Functions for Transient Data Records\nThe following FILE functions are discussed in this section:\n\u2022Retrieving a transient data record\n\u2022Adding a new transient data record\n\u2022Purging intrapartition data\nNOTE\nIf you are running CTS Version 1.3 and higher, 16-byte and 32-hexadecimal character TS queue names are\nsupported.\nRetrieve a Transient Data Record\nNOTE\nWhen you retrieve a record from an intrapartition transient data destination, the retrieved record disappears from\nthat queue.\n1.To retrieve a transient data record, complete the following fields:\nFUNC=GET\nDESTID= transient data destination\nYou are advised to enter the DESTID= field before entering the FUNC= field when you begin working with a particular\ndestination. If only the DESTID= is entered, the properties of the transient data queue are shown for your verification.\nThis can, for example, help you avoid entering a FUNC=GET for an extrapartition destination that is now open for\noutput.\n2.Press Enter . The record you are retrieving opens on the FILE screen. The following information also displays:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cb5de2c0466d-1", "text": "\u2013The MESSAGE= field shows the message TD RECORD OBTAINED.\n\u2013The SIZE= field gives the length of the data.\nAdd a New Transient Data Record\nFollow this procedure to add a new transient data record:\n1.Complete the FUNC= and DESTID= fields, and then complete the SIZE= field:\nDESTID= transient data destination\nFUNC=ADDN     (to obtain a new work area)   \nor\nFUNC=ADDU     (to use the data in the existing work area)   \nSIZE= size of the data area Note: The SIZE cannot be higher than permitted for the destination.\n 1219", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0000e7e1f957-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIn addition, you can complete the following optional  field if appropriate:\nDATA= characters\n\u2013If you enter FUNC=ADDN, the characters you type in the DATA= field will fill the work area.\n\u2013If you enter FUNC=ADDU, the characters you type in the DATA= field will fill the newly obtained data space (if the\nnew work area is larger than the present one).\nYou are advised to enter the DESTID= field before entering the FUNC= field when you begin working with a particular\ndestination. If only the DESTID= is entered, the properties of the transient data queue are shown for your verification.\nThis can, for example, help you avoid entering a FUNC=ADDU for an extrapartition destination that is now open for\ninput.\n2.Press Enter . The following information is on the FILE screen:\n\u2013The MESSAGE= field shows the message WORK AREA OBTAINED.\n\u2013The SIZE= field gives the size of the work area (the size is the maximum permitted).\nThe obtained work area is displayed, beginning with the byte indicated in the LOC= field.\n3.Make any necessary changes to the newly obtained work area. To write the newly added record, complete the\nfollowing fields:\nFUNC=PUT\nDESTID= transient data destination\nand, if appropriate, the following optional  field:\nSIZE= size of the record         (if smaller than work area)\n4.Press Enter .\nThe MESSAGE= field on the FILE screen shows the message TD RECORD WRITTEN.\nExamples\nTo add a new 100-byte record (with most of its fields blank) to the transient data destination CSSL:\nSpecify the following, and then press Enter :\nFUNC=ADDN \nDESTID=CSSL\nDATA=C' '", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0000e7e1f957-1", "text": "FUNC=ADDN \nDESTID=CSSL\nDATA=C' ' \nSIZE= 100   or   64     (for FORMAT=D)  \nMake changes to the work area.\nSpecify the following, and then press Enter :\nFUNC=PUT\nDESTID=CSSL\nTo add another new record to the transient data destination in Example 1, using the work area from Example 1:\nSpecify the following, and then press Enter :\nFUNC=ADDU\nMake changes to the work area.\nSpecify the following, and then press Enter :\nFUNC=PUT\nDESTID=CSSL\n 1220", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ca7764260eff-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPurge Intrapartition Data\nFollow this procedure to purge intrapartition data:\n1.Complete the following fields:\nFUNC=PURG\nDESTID= transient data destination\nYou are advised to enter the DESTID= field before entering the FUNC= field when you begin working with a particular\ndestination. If only the DESTID= is entered, the properties of the transient data queue are shown for your verification.\nThis can, for example, help you avoid entering a FUNC=PURG for an extrapartition destination.\n2.Press Enter . This purges the data. The MESSAGE= field on the FILE screen displays the message DESTINATION\nPURGED.\nUsing InterTest for CICS with DB2 and SQL/DS Programs\nThis article explains how to use InterTest for CICS to test CICS/DB2 and SQL/DS application programs. The topics are\nintended primarily for system programmers and database administrators.\nPreliminary Steps\nBefore you can monitor a DB2 program, make sure that the following tasks have been completed:\n1.InterTest for CICS was installed with DB2 support. Check with your system programmer if you are not sure.\n2.The application program was compiled or assembled with symbolic support.\n3.The CICS/DB2 attach facility (z/OS) is active.\nCheck for DB2 Support\nInterTest for CICS should have been installed with DB2 support if you are going to monitor DB2 application programs.\nTo ensure that DB2 support was installed, follow these steps:\n1.Run the DB2DEMO program by invoking the DEMD transaction.\n2.Press PF2 when the welcome screen displays.\n3.Press Enter to perform SQL select from SYSIBM.SYSTABLES.\nCompile or Assemble Programs with Symbolic Support", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ca7764260eff-1", "text": "Compile or Assemble Programs with Symbolic Support\nTo test DB2 programs thoroughly, they should be compiled or assembled with symbolic support, and the program's Cross-\nReference should be saved in the InterTest for CICS Symbolic File.\nCheck That the Attach Facility or Resource Adapter Is Active\nYou must ensure that the CICS/DB2 Attach facility is active in the CICS region in which you are testing DB2 programs.\nTo test whether the attach facility is active, follow these steps:\n1.Type FILE on a clear screen.\n2.Change the DATATYPE to DB and press Enter .\nIf the attach facility is active, InterTest for CICS displays the following message:\nCAIN1701\nENTER THE SQL COMMAND TO BE EXECUTED.\nIf the attach facility is not  active, InterTest for CICS displays the following message:\n 1221", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "289c899557ea-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN1712\nDSNC NOT ACTIVE OR DB2 NOT AVAILABLE.\nIf the Resource Adapter is active, it displays the following message:\nARI0401I\nSQL/DS ONLINE RESOURCE ADAPTER IS ALREADY ACTIVE IN THIS PARTITION.\nIf the Resource Adapter is not  active when SQL/DS is in multi-partition mode, the following messages display:\nARI0418A\nSQL/DS IS NOT READY. RETRY THE ENABLE TRANSACTION CIRB AFTER SQL/DS STARTS.\nARI0413I\nRESOURCE ADAPTER ARI0OLRM IS DISABLED.\nIf the Resource Adapter is active in the non-CICS partition but not  yet active in the CICS partition, the following\nmessages display:\nARI407E\nERROR ATTEMPTING TO EXEC SQL.\nARI407E\nSQLCODE = -560 SQLERRD1 = -180 SQLERRD2 = 0.\nARI413I\nRESOURCE MANAGER ARI0OLRM IS DISABLED.\nIf the CICS DB2 Attach Facility Is Not Active\nIf the attach facility is not  active and you execute a DB2 program, the transaction fails with an AEY9 abend code. If you\nare monitoring the program with InterTest for CICS and you do not have a Handle Condition for this error, your program is\nhalted at an automatic breakpoint at a call to DB2 (CALL 'DSHNLI') or SQL (CALL 'ARIPRDI'). In this case, follow these\nsteps:\n1.Call your system programmer or console operator and request that the CICS/DB2 attach facility be started.\n2.Continue program execution by re-executing the call. In COBOL, this means paging back to the statement prior to the\ncall:\nPERFORM SQL-INITIAL UNTIL SQL-INIT-DONE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "289c899557ea-1", "text": "call:\nPERFORM SQL-INITIAL UNTIL SQL-INIT-DONE\n3.Type G to the left of this statement and press PF5.\nHalt Programs Before and After Each SQL Request\nTo test DB2 programs, halt the program before and after each SQL request.\n\u2022Halting the program before  each SQL request lets you check that all fields in the request have been initialized correctly\n\u2022Halting the program after  each SQL request lets you view the data returned to your program and the SQL return codes\nHalt a Program Before Each SQL Request\nTo halt a program before each SQL request, use the InterTest for CICS request breakpoint capability:\n1.Access the Request Breakpoint Selection menu. For more information, see Using Breakpoints.\n2.Type X in the DB2 field at the top of the menu. Press Enter .\nThis instructs InterTest for CICS to set a breakpoint prior to each application  call to DB2.\n 1222", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aa88468c6031-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022For DB2, this occurs at the call to DSNHLI.\n\u2022For SQL, this occurs at the call to ARIPRDI.\nWhen the program halts at the request breakpoint, you can inspect the values of fields.\nHalt a Program after an SQL Request\nWhen a program halts at a request breakpoint, you can execute the SQL request and stop the program again.\n\u2022For COBOL or PL/I programs, press PF10 , which executes one COBOL verb or one PL/I statement\n\u2022For Assembler programs, press PF10  twice to execute two instructions\nWhen the program is halted after the call, you can inspect the values of fields again and analyze the SQL return codes.\nInspect Host Variables\nWhen you are stopped at a breakpoint, inspect the values of data fields. SQL terminology refers to the fields used in SQL\nrequests as host variables. Host variables are used to do the following tasks:\n\u2022Supply a value to an SQL request\n\u2022Receive a value from an SQL request\nA typical SQL request has the following format:\nEXEC SQL\n    SELECT  column names    \n    INTO    host variables  \n    FROM    table name  \n    WHERE   column names/host variables \nEND-EXEC\nExample:\n\u2022The INTO clause of the SELECT statement specifies host variables.\n\u2022The WHERE clause of the SELECT statement uses host variables to qualify the request for data.\nIn a typical COBOL program:\n\u2022All the host variables used to receive data for column values named in an INTO clause are grouped together in a\nsingle structure designated by a 01-level field name\n\u2022All the host variables used to qualify the data request in a WHERE clause are grouped together in a single structure\n\u2022All the host variables used for null indicators are grouped together in a single structure\nNotes:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aa88468c6031-1", "text": "\u2022All the host variables used for null indicators are grouped together in a single structure\nNotes:\n\u2022When your program is halted at a breakpoint before  an SQL request, check the null indicators and host variables used\nin the WHERE clause\n\u2022When your program is halted after  an SQL request, check the host variables specified in the INTO clause\nDisplay Host Variables\n   CA InterTest for CICS    - MAIN STORAGE UTILITY  Termid = LXD6 \n Starting at Address =  140D9C                Hexadecimal            Character \n  \n 01 DCLEMP                           |                             |\n  02 EMPNO                           |  F0F0F0F0 F1F0              | 000010 \n  02 FIRSTNME                        |                             |\n 1223", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e4ce5f62d77f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n   03 FIRSTNMELEN                    |  0009                       | .. \n   03 FIRSTNMETEXT                   |  C3C8D9C9 E2E3C9D5 C5000000 | CHRISTINE..\n  02 MIDINIT                         |  C1                         | A \n  02 LASTNAME                        |                             |\n   03 LASTNAMELEN                    |  0004                       | .. \n   03 LASTNAMETEXT                   |  C8C1C1E2 00000000 00000000 | HAAS.......\n                                     |  000000                     | ...\n  02 WORKDEPT                        |  C1F0F0                     | A00 \n  02 PHONENO                         |  F3F9F7F8                   | 3978\n  02 HIREDATE                        |  F1F9F6F5 60F0F160 F0F1     | 19650101 \n  02 JOB                             |  D7D9C5E2 40404040          | PRES \n  02 EDLEVEL                         |  0012                       | .. \n  02 SEX                             |  C6                         | F \n   \n PF1 Help       2            3 End        4 Return     5            6           \n PF7 Backward   8 Forward    9 Caps Off  10           11 Redisplay 12 Structure \n CORE='DCLEMP' \nFor DB2 Users\nIf you use the DCLGEN function to generate DB2 table declarations, the COBOL 01-level field name is a concatenation of\nthe characters DCL and the table name, as shown in the previous example.\nSQL Return Codes", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e4ce5f62d77f-1", "text": "the characters DCL and the table name, as shown in the previous example.\nSQL Return Codes\nThe SQL communication area (SQLCA) is a structure of variables that is updated after each SQL statement executes. An\napplication program that contains executable SQL statements must provide an SQLCA to let DB2 communicate with the\nprogram.\nNOTE\nThe IBM manual DB2 Application Programmer Guide  provides information on the SQLCA.\nWhen DB2 processes an SQL statement, it places a return code in the SQLCODE field of the SQLCA that indicates the\nsuccess or failure of the SQL request:\n\u2022If the return code is zero, the SQL request was processed. DB2 did not detect an error or an exceptional condition.\n\u2022If the return code is a negative  number, DB2 detected an error.\n\u2022If the return code is a positive  number, DB2 detected an exceptional but valid condition.\nNote: Sometimes a zero return code does not indicate a successful execution. You should always check the SQLWARN\nfield to ensure that it is blank, which indicates successful execution. If the field is not blank, a warning condition exists.\nCheck the other warning indicators to determine the specific condition.\nExample\nIf a value was truncated the SQLCODE will be zero, but the SQLWARN1 field indicates truncation.\nBecause the SQLCA contains valuable diagnostic information, it is a good idea to check its contents after each SQL\nrequest.\nHow to Handle SQL Error Codes\nTwo techniques are commonly used by programmers to handle SQL error return codes after each SQL request:\n\u2022Check the SQLCODE data field immediately after each SQL request\n\u2022Branch to a common error handling routine\n 1224", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7a815ab77a0a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nChecking   the SQLCODE immediately tells you which request produced the error so you can create an error message\nreflecting that request. However, this method might not be efficient if you have many similar routines throughout your\nprogram -- one for each SQL request. Moreover, if you discover a logic error in such an error handling routine, you must\ncorrect the error in all the routines throughout the program.\nBranching   to a common error handling routine results in a smaller program and simplifies the task of debugging the\nroutine. However, you might not be able to determine which SQL request caused the error unless you pass an indicator to\nthe error routine, which is then reflected in the generated error message.\nUsers who want to check the SQLCODE field in the SQLCA after each SQL request should set unconditional breakpoints\nat each occurrence of SQLCODE. For more information about setting breakpoints at each occurrence of a data field,\nsee Using Breakpoints. Your program must be compiled or assembled symbolically with the option to produce a Cross-\nReference listing.\nUsers who branch to a common error handling routine should set request breakpoints at all DB2 calls and then single-\nstep through the breakpoint, as described in the Halt Programs Before and After Each SQL Request. This technique does\nnot require that programs be compiled or assembled symbolically.\nIn either case, keep SQLCODE in the Keep window so its value can be checked easily. For more information about the\nKeep window, see Breakpoint Activities.\nDisplay the SQLCODE\nOnce your program halts at a breakpoint, the Keep window displays the hexadecimal contents of SQLCODE. To display\nthe SQL return code in decimal format, follow these steps:\n1.Type D to the left of SQLCODE in the Keep window.\n2.Press Enter .\nIf you have not kept SQLCODE in the Keep window, follow these steps:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7a815ab77a0a-1", "text": "If you have not kept SQLCODE in the Keep window, follow these steps:\n1.Type D to the left of the statement where you are stopped.\n2.Position the cursor under the data field SQLCODE .\n3.Press Enter .\nInterTest for CICS displays a CORE structured display of SQLCODE and the following message:\nCORE053 VALUE OF FIELD is = +/- nnn\nnnn\nIndicates the SQL return code.\nDB2 return codes can have many meanings and subcodes. The IBM's DB2 Messages and Codes manual explains the\nreturn codes.\nYou can convert this value into a text message by overkeying the CORE='SQLCODE' command at the bottom of the\nSQLCODE display with the following command and pressing Enter:\nCORE=SQLRCODE\nYou can access the SQLCODE text message display from the breakpoint screen by entering CORE=SQLRCODE  on the\ncommand line, if the command line displays.\nInterTest for CICS converts the decimal value to a text message. In addition, if there are any warning codes in the SQLCA,\nInterTest for CICS displays each of them along with its meaning. The following is a sample SQLRCODE display.\nCA InterTest for CICS    - MAIN STORAGE UTILITY  Termid = LXD6 \n 1225", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d3ebfd9a3cd1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n  \n  \n DSNT408I SQLCODE = 204\n  \n          ERROR:  ADM.DEPT IS AN UNDEFINED NAME\n \n  \n  \n ------------------------------------------------------------------------- \n    \n PFKEYS 1 Help     2           3 End       4 Return      5            6        \n        7          8           9          10            11           12 \n  CORE=SQLRCODE\nDB2 messages often contain tokens that are replaced at execution time. The message in the previous example the token\nname is replaced by the actual name that is undefined -- in this case, ADM.DEPT.\nWithout InterTest for CICS, tokens are often hard to interpret. They are returned in the SQLERRM field of the SQLCA, and\nif there are multiple tokens, appear sequentially in the order in which they appear in the message text, separated by X'FF'.\nInterTest for CICS inserts tokens in the correct places in the message text, as shown in the previous figure, which makes\nthe DB2 messages much easier to understand.\nDisplay All the Fields in the SQLCA\nTo view all the fields in the SQLCA after an SQL request, overtype the CORE command at the bottom of the display with\none of the following, and press PF12 :\nCORE='SQLCA'        (COBOL and PL/I)    \nCORE='Rn.SQLCA'         (Assembler) \nn\nIndicates the register used to reference the SQLCA.\nInterTest for CICS displays all the fields in the SQLCA in structured format as defined in the program.\nAnother method for viewing the SQLCA fields is to type the following command and press PF12 :\nCORE=SQLCA\nInterTest for CICS displays the SQLCA fields using Assembler language field names.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d3ebfd9a3cd1-1", "text": "InterTest for CICS displays the SQLCA fields using Assembler language field names.\nBoth methods should produce the same results, but the second method is available for programs not compiled or\nassembled symbolically.\nNote: Neither command is valid until after an SQL request is issued.\nAdvanced Debugging Techniques\nFor specialized debugging tasks, you can instruct InterTest for CICS to halt your program at DB2 calls other than an SQL\napplication request. However, halting programs at these calls usually does not produce much useful information and might\ncreate problems.\nTo halt a program before   selected DB2 calls, use the InterTest for CICS request breakpoint capability, and follow these\nsteps:\n1.Access the Request Breakpoint Selection menu. For more information, see Using Breakpoints.\n2.Enter X to the left of the CALLs field at the top of the menu. Press Enter .\n 1226", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2d5b73fa5cb2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterTest for CICS displays the Request Breakpoint Selection menu for calls.\nFor DB2 this menu contains three relevant entries.\nDSNHLI, DSNHADDR, and DSNTIAR.\nDSNHLI\nThe call generated for all SQL application requests. To halt the program at these calls, set request breakpoints\nat all DB2 calls on the first Request Breakpoint Selection menu as described in Halt Programs Before and After\nEach SQL Request.\nDSNHADDR\nThe call made to the SQL-INITIAL routine that is inserted by the DB2 preprocessor in the COBOL Procedure\nDivision to initialize the parameter lists needed for an SQL call.\nThe DB2 preprocessor generates structures identified at the 01-level by SQL-PLIST n in COBOL Working-storage.\nThere is one structure for each EXEC SQL command in the program. The SQL-PLIST ns are parameter lists\npassed to DB2 at each SQL request. The values in the parameter lists are updated at application program\ninitialization using a DSNHADDR call. The SQL-INITIAL routine makes one call to DSNHADDR for each EXEC\nSQL command. Usually, setting a breakpoint at each DSNHADDR call will not produce much useful information.\nDSNTIAR\nThe call made to the IBM-provided DB2 subroutine that converts an SQL return code to a text message. The\nsubroutine is approximately 32 KB in size and must be statically linked with your program. According to IBM,\ncalling DSNTIAR dynamically from a CICS application program causes problems because of the GETMAINs\nissued by DSNTIAR.\nUnless your application program needs the SQL return code text message, there is no need to set breakpoints at\nDSNTIAR calls. Instead, use the SQLRCODE command explained in Handle SQL Return Codes.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2d5b73fa5cb2-1", "text": "DSNC Abends\nA DSNC abend means the CICS attach facility detected an internal error and has abnormally terminated a DB2 internal\ntask or a user connected task. The CICS attach facility first writes a SNAP dump to the SYS1.DUMP nn data set. Then,\ndepending on the type of error, the CICS attach facility either:\n\u2022Terminates the user transaction by issuing an EXEC CICS ABEND with DSNC as the abend code. In this case, the\napplication's SQLCA remains set to low values.\n\u2022Lets the transaction continue, but produces a dump by issuing EXEC CICS DUMP with DSNC as the abend code. In\nthis case, a return code is placed in the application's SQLCA.\nIn the first case described previously, you cannot handle the DSNC abend in your program's EXEC HANDLE ABEND\nroutine because control does not come back to it. EDF captures the DSNC abend, but its halt screen provides little useful\ninformation.\nInterTest for CICS intercepts a DSNC transaction abend and produces an automatic breakpoint, as follows.\n     CA INTERTEST for CICS    - PROTDEM FILE SOURCE LISTING BREAKPOINT \n Command ===>   \n Program= COBSQL   Option #       Stmt #                             Margin= 01 \n                                        Search= \n \n  \n    01414*****ENDEXEC. \n    01415     PERFORM SQLINITIAL UNTIL SQLINITDONE \n  A   ==>     CALL 'DSNHLI' USING SQLPLIST6. \n      ==> \n 1227", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bd565152a106-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n      ==> CICS abend intercepted. Abend code = DSNC, after an external CALL. \n      ==> \n      ==>      Press PF1 for a detailed description. \n      ==> \n    01417 \n    01418 \n _  01419     IF SQLCODE = 530 \n _  01420        MOVE 'INVALID WORK DEPARTMENT ' TO ERRMSGO \n _  01421        MOVE 1                          TO WDEPTL\n _  01422        MOVE DFHBMBRY                   TO WDEPTA\n _  01423        GO TO SENDRTN. \n    01424    \n                    \nIf CICS terminated the transaction, you cannot continue processing it because the registers were destroyed.\nInterTest for CICS provides several CORE commands to help you determine the cause of the problem online without\nwaiting for the DB2 SNAP dump.\nThe CICS Life of Task Control Block (CLOT)\nAccording to the DB2 Problem Determination Guide , first locate the CICS Life of Task (CLOT) control block. The reason\nfor the error can be determined by the codes in the CLOTCFLG field of the control block included in the dump.\nTo display the CLOT, type the following command and press PF12 :\nCORE=CLOT\nNext, the DB2 Problem Determination Guide recommends that you inspect the CLOTCFLG field. You can page forward to\ndisplay this field or type the following command and press  PF12 :\nCORE=CLOT.CLOTCFLG\nReason and Abend Codes--Inspecting and Interpreting\nIf the thread subtask abended (CLOTCFLG=18), the reason code is contained in the CLOTWRK1 field and the abend", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bd565152a106-1", "text": "code is contained in the CLOTWRK2 field. Both abend reason codes and subsystem termination reason codes have the\nfollowing format:\nX'00ccxxxx'\nX'00'\nSpecifies the high-order byte\nX'cc'\nSpecifies the hexadecimal sub-component identifier\nX'xxxx'\nSpecifies the hexadecimal reason code\nTo display this information on a single diagnostic screen, type the following command and press Enter :\nCORE=SQLRCODE\nA sample diagnostic InterTest for CICS display follows.\n 1228", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2d1fc3817d19-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n     CA InterTest for CICS   - MAIN STORAGE UTILITY  Termid = LXD6 \n  \n  \n Transaction DB2C, Program COBSQL   has terminated with an DSNC abend. \n  \n          The reason code for this failure is:          18 \n              The thread subtask has abended; see subtask dump. \n  \n  \n          The failing DB2 subcomponent identifier is: 00E7 \n              Relational data system. \n  \n          The subsystem termination reason code is:   000D \n  \n Refer to the IBM DATABASE 2 Messages and Codes, Part 4. Reason Codes, \n for detailed information. \n  \n  \n  \n -----------------------------------------------------------------------  \n PFKEYS 1 Help     2           3 End       4 Return      5            6  \n        7          8           9          10            11           12 \n  CORE=SQLRCODE    \nNOTE\nFor an explanation of the codes, see the DB2 Messages and Codes manual.check reference\nInspect the Application Invocation Parameter List (RDIIN)\nIn some cases, the DB2 Problem Determination Guide suggests that you inspect the Application Invocation Parameter\nList (RDIIN) in the DB2 SNAP dump for further information. If this control block exists in your CICS DSNC dump, you can\nview it online by typing the following command and pressing PF12 :\nCORE=RDIIN\nView the CICS DB2 Attachment Facility\nDefine the CICS/DB2 connection and control characteristics using the CICS Resource Definition Online (RDO). You\ncan still assemble macro resource control tables (RCTs) for migration to the DFHCSD file only. The DSNCRCT macro is", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2d1fc3817d19-1", "text": "shipped with CICS to allow migration of RCT tables to the CSD.\nNOTE\nFor more information about DSNCRCT, see the CICS Resource Definition Guide .\nThe RCT or DB2 attachment facility contains the information required for CICS to establish its connection to DB2. The\nFILE transaction's DB2 facility lets you view information and statistics on each entry in the active RCT. The display format\nis presented as if the RCT existed as a DB2 table. This display is similar to the information provided by the IBM-supplied\nDSNC DISP STAT command, providing complete and easily accessed information.\nTo display the RCT, type the keyword DSNCRCT in the DB2 command area.\n 1229", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5bc02a0f4c5e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAnalyzing Dumps Symbolically SymDump  for CICS Option\nWhat Is SymDump  for CICS Option?\nWhen you test a program with InterTest for CICS, your program does not usually produce a dump because InterTest\nfor CICS monitors the program and halts it at an automatic breakpoint before the program abends. Then you can take\nadvantage of InterTest for CICS's powerful diagnostic tools to find the problem, correct the error and continue testing.\nIdeally, you might use InterTest for CICS to monitor every program and catch every error. However, in real world\nsituations, that is not possible, due to the overhead involved or because you may not want to monitor security programs or\nprograms using non -standard code.\nTherefore, although InterTest for CICS greatly reduces the number of dumps, dumps will still occur, especially in\nproduction. Even a thoroughly debugged program can abend because of bad data, scheduling errors, invalid parameters,\nand many other factors beyond programmer control.\nSymDump  for CICS Option, which stands for symbolic dump facility, is a powerful online tool designed to handle dumps. It\nlets you do the following tasks:\n\u2022Analyze dumps symbolically, this is especially valuable for shooting bugs in your production system where you might\nnot want InterTest for CICS breakpoint displays\n\u2022Manage your dump data set so you can selectively retain, view, and print the dumps you need, and discard the ones\nyou do not need.\nSymbolic Dump Analysis\nProblems that cause dumps are a fact in both production and test systems. SymDump  Option lets you analyze and\nsolve these problems online , without having to access and read traditional hexadecimal format dumps. Your source\nlisting displays at the instruction that triggered the abend, simply as if InterTest for CICS had stopped the program at an", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5bc02a0f4c5e-1", "text": "automatic breakpoint.\nWith SymDump  Option you can do the following tasks:\n\u2022Use the powerful functions of InterTest for CICS to find and correct errors by:\n\u2013Displaying program variables symbolically\n\u2013Viewing the program listing and compiler output\n\u2013Setting breakpoints for subsequent testing\n\u2013Using CORE and FILE to inspect and modify main and auxiliary storage\n\u2022Take advantage of special SymDump  Option capabilities to:\n\u2013Pinpoint the abending instruction and its operands\n\u2013Display the formatted trace table\n\u2013View the source statement responsible for the abend\n\u2013List the programs and files used by the task\n\u2013View the contents of the PSW and registers at the abend\nYou can use SymDump  Option in any region -- regardless of where the abend occurred. For example, you can debug\na production dump in your test region. Therefore, it is not necessary to run InterTest for CICS in production to take\nadvantage of SymDump  Option. You can even debug a dump produced in a remote data center at another site.\nYou can instruct SymDump  Option to refer to the symbolics you want, if multiple symbolic versions of the program exist.\nThis is especially helpful if there are many versions of a particular program. Even if InterTest for CICS does not have\nsymbolic information for the program, SymDump  Option still provides a formatted display of the CICS system areas, with\nhexadecimal and character representations of each field so you can debug with or without symbolics.\n 1230", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "97af6c1fc47d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nManage Dumps\nSymDump  Option also lets you control which CICS dumps to save, discard, and print. It has its own dump data set,\nwhich is separate from the CICS dump data set. You can even route dumps to both data sets. It is easy to manage the\nSymDump  Option data set because you can do the following tasks:\nList\nLists all dumps. You will know immediately when each dump was created and which transaction and program\nproduced it. You can quickly select the dumps you want to view online.\nDelete\nspecific dumps. You can delete the dumps you do not want and keep the ones you need. As a result, you avoid\nthose situations where CICS stops writing dumps because the dump data set is filled.\nHold\nspecific dumps. You can specify which dumps you want to retain for future use.\nPrint\nspecific dumps. It is no longer necessary to print the entire dump data set to get printouts of selected dumps. You\ncan even print an index of all the dumps in the dump data set.\nHow SymDump  Option Works with Your CICS Dump Data Set\nSymDump  Option contains only application dumps; system dumps are still written to your CICS dump data set. When the\nSymDump  Option is installed, your system programmers can specify which dumps they do not want written to either the\nSymDump  Option or the CICS dump data set to save DASD space. For example, they can exclude all AKCT abends.\nInterTest for CICS automatically deletes old dumps from the SymDump  Option data set when space is needed for new\nones. However, you determine how frequently dumps are deleted. You can also specify that certain dumps be held so", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "97af6c1fc47d-1", "text": "they are not deleted. If the SymDump  Option data set becomes full (that is, full of dumps that cannot be deleted), new\ndumps are written to your CICS dump data set instead of to the SymDump  Option data set.\nFor more information, see CICS Abend Analysis.\nBreakpoint Displays for NonSymbolic Programs\nA non-symbolic breakpoint screen appears for all non-symbolic programs. In addition, it appears if your COBOL or PL/\nI program was compiled without the InterTest for CICS post-processor. For more information, consult your systems\nprogrammer.\nUnconditional Breakpoint\nThe following panel shows a sample non-symbolic breakpoint screen for an unconditional breakpoint:\n CNTL=GO,TASK=00063,C             at +00BB0           pgm=COBDEMO ,addr=24510BD0\n UBP: F=U056,T=U056 Unconditional breakpoint.                                \n Mon.as COBDEMO            Pgm COBDEMO  Trx DEMC Fac U056 Trm     in.....out  \n Task 00063 at +00BB0             TIOA none                      +00A90  +00B16\n DSA 23708B88  TGT 23709D60   CWK 2370A058                       +00B06  +00B16\n BLLS:  0 001000D0  1 00000000  2 00001000  3 00002000            00002  times \n        4 00003000  5 00004000  6 00000000  7 00000000           +00B06  +00B24\n        8 00000000  9 00000000                                   +00B36  +00BA4", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "97af6c1fc47d-2", "text": "+00BA8  curr. \nNEXT MVC   X'B0'(4,R8),8(R7)                  AT +00BB0                  \nPREV OI    X'84'(RD),X'01'                    AT +00BAC                  \n        Press ENTER to execute the default command on line 1,                \n 1231", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3eb7467de1d4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n        OVERTYPE it, or use any of the following PF KEYS:                    \n 1 Help  2         3 Source  4         5 Resume     6 Menu                 \n 7       8         9 1 Inst 10        11 Backtrace 12 Status                   \n Addr and content of relevant area:                                            \n23708C0C 21        \u2020             \nCNTL=GO...\nDefault CNTL command and location information. For an automatic breakpoint, the default command abends\nthe task. For all other breakpoints, the default is to continue task execution. The command can be modified or\novertyped with any other InterTest for CICS command.\nat +00BB0\nDisplacement of the instruction about to be executed follows the command on the top line.\npgm...\nName of the program that was stopped by InterTest for CICS follows the displacement.\n,addr...\nAddress of the instruction that triggered the breakpoint.\nNote: InterTest for CICS stopped the program before this instruction was executed.\nUBP\nType of breakpoint: automatic (ABP), unconditional (UBP), conditional (CBP), request (RBP), or single-stepping\n(SBP). In most cases, there is a one or two line message explaining exactly why the breakpoint occurred.\nMon.as\nName of the monitoring table entry.\nPgm\nProgram name (Pgm), transaction code (Trx), and CICS facility (Fac) associated with the task; in this case,\nterminal (Trm) U056.\nTask\nTask number and displacement of the instruction about to be executed.\nTIOA\nAddress of the first TIOA on the chain of such areas allocated to the task. To display the area, issue the command\nCORE=TIOA.\nCWK", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3eb7467de1d4-1", "text": "CORE=TIOA.\nCWK\nAddresses of the areas containing the copy of COBOL DSA, TGT, Working-Storage, and Local-Storage for this\ntask. If the program does not contain a DSA   or Local-Storage, the fields are left blank. To display the area, issue\nthe appropriate CORE command (for example, CORE=CWK).\nBLLS:\nCOBOL BLL cells or general registers 0-15 for Assembler or PL/I programs.\n++00BA8\nBacktrace of the starting (IN) and ending (OUT) displacements or addresses of the most recently executed pieces\nof code. Every break in the sequential execution of the program results in a new entry. A loop counter tells how\nmany times the piece of code above it was executed. The entry curr. stands for current location.\nAT +00BB0\nMachine code and offset (or absolute address) of the instruction that triggered the breakpoint.\nAT +00BAC\nMachine code and offset (or absolute address) of the last instruction executed.\n1 Help \u2026\nProgram function keys for immediate access to InterTest for CICS facilities.\n 1232", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c0a754fba901-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n23708C0C ...\nAddress and representation (in both character and hexadecimal form) of the area of main storage that would have\nbeen modified by the next instruction.\nAutomatic Breakpoint\nThe following panel shows a non-symbolic breakpoint screen for an automatic breakpoint:\n CNTL=GO,TASK=00077,A             at +007A4          pgm=PL1DEMO ,addr=24517864\n 37 ABP: ASRA abend in user code------ data exception.                           \n  Mon.as PL1DEMO         Pgm PL1DEMO  Trx DEMP Fac U056 Trm       in.....out     \nTask 00077 at +007A4             TIOA none                      +00000  +00000 \nDSA 23703F40                                                    +00022  +00038 \nREGS: 0 FFFFF0F0  1 23704340  2 23704890  3 245170FC            +00014  +00020 \n      4 23704256  5 2451A3F8  6 2451B6F0  7 23704230            +0003C  +00358 \n      8 23704228  9 23704890 10 23AA4B27 11 00000000            +003CA  +00478 \n     12 2370BC20 13 23703F40 14 A4517754 15 00000000 CC= 0      +00480  +004B0 \nNEXT ZAP   X'A28'(4,RD),X'2F1'(3,RD)         AT +007A4          +004B8  +004C6", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c0a754fba901-1", "text": "PREV STH   R0,0(,R1)                          AT +007A0         +004CE  +00584 \n        Press ENTER to execute the default command on line 1,   +051B8  +00584 \n        OVERTYPE it, or use any of the following PF KEYS:       +00586  +005D4 \n 1 Help  2         3 Source  4         5 Resume     6 Menu      +051B8  +005D4 \n 7       8         9 1 Inst 10        11 Backtrace 12 Status    +005D6  +005E4 \n Addr and content of relevant area:                             +005EC  +00662 \n 23704968 00000000                                              +051B8  +00662 \n                                                                +00664  +00692 \n                                                                +051B8  +00692 \n                                                                +00694  +00694 \n                                                                +00794  curr.     \nCTNL=...\nDefault CNTL command and location information. For an automatic breakpoint, the default command abends\nthe task. For all other breakpoints, the default is to continue task execution. The command can be modified or\novertyped with any other InterTest for CICS command.\nDisplacement\nof the instruction about to be executed follows the command on the top line.\nName\nof the program that was stopped by InterTest for CICS follows the displacement.\nAddress\nof the instruction that triggered the breakpoint.\nNote: InterTest for CICS stopped the program before this instruction was executed.\n37 ABP\nType of breakpoint: automatic (ABP), unconditional (UBP), conditional (CBP), request (RBP), or single-stepping", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c0a754fba901-2", "text": "(SBP). In most cases, there is a one or two line message explaining exactly why the breakpoint occurred.\nMon.as ...\nName of the monitoring table entry  that caused the current monitoring to be in effect.\nTask ...\nTask number and displacement of the instruction about to be executed.\n 1233", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a39e99ab2b82-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPgm ...\nProgram name (Pgm), transaction code (Trx), and CICS facility (Fac) associated with the task; in this case,\nterminal (Trm) U056.\nRegs:\nCOBOL BLL cells or general registers 0-15 for Assembler or PL/I programs.\nCC=0\nCondition Code. The value of the condition code is the value that was saved when the breakpoint occurred.\nNEXT ZAP ...\nNext and previous instructions. This line indicates the next instruction to execute and the instruction that was\nexecuted previously.\nAddr and content of relevant area:\nAddress and representation (in both character and hexadecimal form) of the area of main storage that would have\nbeen modified by the next instruction.\nBacktrace\nEach pair of entries describes the boundaries of a piece of the program that executed sequentially.\nDefault CNTL Command\nIn the previous screen, the following dispatch command displayed in this field:\nCNTL=GO,TASK=00077,A\nThis command is used to continue a program's execution from a breakpoint.\nYou can enter any appropriate InterTest for CICS command in this field. To modify this command, overtype it.\nLocation Information\nIn the previous screen, the following location information is displayed:\nat +007A4 pgm= PL1DEMO,   addr=24517864\nThis tells you that a program named PL1DEMO is stopped at displacement 7A4. This is the displacement of the\ninstruction that is about to be executed (check the program's listing to identify the instruction).\nReason for the Breakpoint\nThe type of breakpoint and the reason for it are described in the previous screen by the following message:\n37 ABP: ASRA abend in user code- data exception.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a39e99ab2b82-1", "text": "37 ABP: ASRA abend in user code- data exception.\n\u2022The letters ABP indicate automatic breakpoint, and the number 37 is the error code.\n\u2022The remainder of the line explains what the error code means. In this case, a data exception interrupt was set in\nmotion by the monitored program. Ordinarily, this would cause a CICS abend with the code ASRA, but InterTest for\nCICS averted the abend with this breakpoint.\nExamples\nThe following examples show other reasons for a breakpoint.\nThe following message indicates that an unconditional breakpoint  (UBP)  with the identification 02 occurred because the\nuser requested it at the COBOL paragraph named  999-Abend.\n 1234", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "02378caf37c3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n02 UBP: At='999-abend' Unconditional breakpoint.\nThe following message indicates that an unconditional breakpoint with the identification 07 was requested by the user at\nthe second verb of COBOL statement number 374. The following is another version of the previous message:\n07 UBP: At=#374.1 Unconditional breakpoint.\nIf the user requests the unconditional breakpoint by address or displacement, the following message appears:\n09 UBP: F=.ANY,T=V015 Unconditional breakpoint.\nF=.ANY\nMeans that the user requested an unconditional breakpoint to occur on any terminal (or for a task that has no\nterminal). The parameter T=V015 means that the breakpoint display will be sent to terminal V015.\nIf the user requests single-stepping (SBP), the following message appears:\nAT SBP: Single-stepping breakpoint.\nIf the user set a request breakpoint (RBP), a message similar to the following one appears:\nRBP: Request bkpt; CICS macro is: ...............\nIf the user requests a programmed breakpoint (PBP), the following message appears:\n00 PBP: Programmed breakpoint.\nMonitor Table Entry\nThe name of the entry in the InterTest for CICS Monitoring Table that caused the current monitoring effort is always\ndisplayed. In the previous screen it was:\nMon.as PL1DEMO\nThis tells you that the program is being monitored under (MONitored AS) the entry declared explicitly for the program\nnamed PL1DEMO. It is important to know the Monitoring Table entry because the available online options are attached to\nthat entry.\nNOTE\nAs the tested task continues execution, part of it might be monitored under one Monitoring Table entry and part\nunder another entry, depending on how you formulated the request.\nExamples", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "02378caf37c3-1", "text": "under another entry, depending on how you formulated the request.\nExamples\nIf you were to request that this program be monitored only when it is run from a particular terminal, or if the online TON=\noption were declared, the following message would appear:\nMon.as PL1DEMO for U056\nIn this case, monitoring only takes place when the program named PL1DEMO is executed from the terminal named U056.\nIf the program was declared for monitoring under a transaction name (implicitly) rather than its program name, the\nfollowing message would appear, indicating that the entry in the Monitoring Table is transaction (TRX), DEMP.\n 1235", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "310746424cf3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMon.as DEMP TRX\nIf the program was declared for monitoring under a terminal name (implicitly), the following message would appear,\nindicating that the entry in the Monitoring Table is terminal (TRM), U056.\nMon.as U056 TRM\nProgram, Transaction, and CICS Facility\nThe names of the program, transaction, and CICS facility appear in the center of the third line from the top on the\nbreakpoint screen. In the previous example, the following information is displayed:\nPgm PL1DEMO Trx DEMP Fac U056 Trm\n\u2022This tells you that the name of the program being monitored is PL1DEMO, that the transaction (Trx) is executing a\nprogram named DEMP, and that the CICS facility that generated this task is the terminal (Trm) named U056.\n\u2022For tasks created automatically by the trigger-level facility of a transient data, the FAC field names the Destination\nControl Table (DCT) entry.\nExample\nFAC GCOS DCT names the GCOS destination in the DCT.\n\u2022For tasks that do not own a terminal or a DCT entry, the FAC field displays the content of the TCAFCAAA field of the\nTask Control Area (TCA).\nTask Identification Number and Address\nThe fourth line from the top of the breakpoint screen gives the task identification number and the address of the Terminal\nStorage Area. In the previous example, this information is expressed as follows:\nTask 00077 at +007A4      TIOA none\n\u2022The parameter 00077 indicates the number of the task that was put into the breakpoint state by InterTest for CICS.\n\u2022The parameter at +007A4 repeats the address of the instruction that is about to be executed.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "310746424cf3-1", "text": "\u2022The parameter TIOA None gives the address of the first terminal Storage Area (the Terminal Input/Output Area)\non the chain of areas allocated for the task at breakpoint. You can display the first TIOA by issuing the command\nCORE=TIOA.\nProgram Storage Areas\nThe fifth line from the top of the breakpoint screen gives the address of various program storage areas, depending on\nthe language of the program. For COBOL programs the line displays the address of the DSA (Dynamic Storage Area) if\nthe program was compiled using COBOL for MVS, COBOL for OS/390, or COBOL for z/OS, the address of the TGT, the\naddress of Working-Storage, and the address of Local-Storage, if applicable.\n 1236", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7a71f12b39b3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022The DSA address shown is the address of the Dynamic Storage Area for the current iteration of the program. To\ndisplay the area, enter the command: CORE=DSA .\n\u2022The TGT address shown is the address of the storage area that contains the copy of the COBOL Task Global Table for\nthis task. To display the area, enter the command: CORE=TGT .\n\u2022The CWK address shown is the address of the storage area that contains the copy of the COBOL WORKING-\nSTORAGE for this task. To display the area, enter the command: CORE=CWK .\n\u2022The LCL address shown is the address of LOCAL-STORAGE for the current iteration of the COBOL program. To\ndisplay the area, enter the command CORE=LCL .\n\u2022For PL/I programs, the line displays the address of the program's DSA, while for Assembler programs, it displays the\naddress of the program's work area.\nBLL Cells (COBOL) or General Registers (NonCOBOL)\nFor COBOL programs, this area of the display shows the contents of up to 16 BLL cells used by the task at the time of\nthe breakpoint. Each displayed fullword is preceded by a number, from 0 to 15, relative to the number of the first BLL cell\nactually used in the program.\nThe monitored program might be using a different number of BLL cells, but all can be displayed by issuing the proper\nCORE command. This can best be done using the symbolic names of the BLL cells.\nExample\nIn the first example, the following BLL display is shown:\nBLLs: 0 001000D0 1 00000000 2 00001000 3 00002000", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7a71f12b39b3-1", "text": "4 00003000 5 00004000 6 00000000 7 00000000\n 8 00000000 9 00000000   \nThe BLL cell with the relative number 1, which in command level programs contains the address of the DFHCOMMAREA,\nshows the null value.\nGeneral Registers\nFor Assembler or PL/I programs, this area displays the contents of registers 0 to 15. The following example shows the 16\nconsecutive fullwords that InterTest for CICS used to save registers 0 to 15 at the time of the breakpoint.\nExample\nRegister 0 contains the value of -3856, and registers 11 and 15 contain the null value.\nREGS: 0 FFFFF0F0  1 23704340 2 23704890 3 245170FC\n 4 23704256  5 2451A3F8 6 2451B6F0 7 23704230\n 8 23704228 9 23704890 10 23AA4B27 11 00000000\n 12 2370BC20 13 23703F40 14 A4517754 15 00000000\nCC= 0\nCondition Code\nThe condition code appears to the right of the last line of the REGS: display, and is identified by the letters CC. The value\nof the condition code is the value that was saved at the time of breakpoint. For an interpretation of the condition code,\nconsult the IBM System/370 Reference Card. In the previous example, the condition code is 0.\n 1237", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "590dc6372c18-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNext and Previous Instructions\nThe line directly below the last line of the BLLS or REGS area indicates the next instruction to be executed and the\ninstruction that was executed previously. In the previous illustration, the following lines appears:\nNEXT ZAP   X'A28'(4,RD),X'2F1'(3,RD)        AT +007A4 \nPREV STH   R0,0(,R1)                        AT +007A0\n\u2022In the field marked Next, the Assembler instruction that was scheduled to be executed next when the breakpoint\noccurred is displayed. In this example, the instruction is a ZAP. The first operand is located at displacement A28 from\nthe value in register D for a length of 4, while the second operand is located at displacement 2F1 from the value in\nregister D for a length of 3.\nFollowing the instruction, on the same line, at +007A4 gives the displacement of the instruction in the program (7A4).\nIf the instruction resides outside the program, the address of the instruction is given instead, expressed as eight-\nhexadecimal digits.\n\u2022In the field marked Prev, the Assembler instruction that was executed just before the breakpoint occurred is displayed.\nIn this example, the instruction is a STH. The first operand value is in register 0, while the second operand location is\nat displacement 0 from the value in register 1\nTo the right of the instruction, on the same line, at +007A0 is the displacement of the instruction in the program (7A0).\nIf the instruction resides outside the program, the address of the instruction is given instead, expressed as eight\nhexadecimal digits.\nData Display Area", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "590dc6372c18-1", "text": "hexadecimal digits.\nData Display Area\nThe data display area is under the next and previous instruction line. In the previous example, it appears as:\n23704968 00000000\nThis example shows only four bytes. However, when a larger data field is involved, the portion of the display can occupy\nthe entire lower left corner of the breakpoint screen.\nThis area varies according to the type of breakpoint that occurred:\nAutomatic Breakpoint\nWhen possible, in the case of an automatic breakpoint, InterTest for CICS shows the area that would have been\naffected if the breakpoint had not occurred. This example shows the receiving field of the next instruction to be\nexecuted.\nUnconditional and Single-Stepping Breakpoints\nFor these types of breakpoints, InterTest for CICS shows the area that was affected by the previously executed\ninstruction, where applicable.\nRequest Breakpoint\nInterTest for CICS does not show the data display area for request breakpoints.\nProgrammed Breakpoint\nFor a programmed breakpoint, InterTest for CICS shows the area designated by the programmer in the CALL\nPBP statement that caused the breakpoint to occur.\nThe format of the data display area is similar to the CORE transaction screen. Each line presents up to 16 bytes in\nboth hexadecimal and character format. On each line, the address of the first byte in that line is shown (for example,\n23704968), followed by the same contents in character format between asterisks, where non-displayable values are\nshown as periods.\n 1238", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "628572217cc4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBacktrace Display\nThe backtrace display has two vertical columns under the heading in.....out on the right side of the breakpoint screen.\nEach pair of entries describes the boundaries of a piece of the program that executed sequentially. That is, they were\nexecuted in the same order as the machine instructions that reside in the main memory.\nThe backtrace display is dynamic. The most recently executed piece of code appears as the bottom line of the backtrace\ndisplay, and the oldest piece of code executed is the top line. As the execution of the program progresses, new lines are\nadded at the bottom and dropped from the top.\nThe following screen repeats the backtrace display shown in the previous example.\n     in.....    out\n  \n      +00000  +00000\n      +00022  +00038\n      +00014  +00020\n      +0003C  +00358\n      +003CA  +00478\n      +00480  +004B0\n      +004B8  +004C6\n      +004CE  +00584\n      +051B8  +00584\n      +00586  +005D4\n      +051B8  +005D4\n      +005D6  +005E4\n      +005EC  +00662\n      +051B8  +00662\n      +00586  +005D4\n      +051B8  +005D4\n      +005D6  +005E4\n      +005EC  +00662\n      +051B8  +00662\n      +00664  +00692\n      +00586  +005D4\n      +051B8  +00692\n      +00694  +00694\n      +00794  curr.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "628572217cc4-1", "text": "+00694  +00694\n      +00794  curr.     \nIn the previous example:\n\u2022The letters curr. stand for current location. The current location is also shown in the first line of the breakpoint screen\n(+00794 curr is the most recently executed piece of code).\n\u2022The # character precedes each statement number.\n\u2022Displacements or addresses are given for lines whose statement numbers could not be found. The displacements are\npreceded by a plus sign, +, and the addresses are expressed as six-hexadecimal digits.\nThe backtrace display reveals a number of facts about the way the monitored program behaved:\n\u2022The bottom line, for example, shows that from +00794 to curr (+007A4) the program executed sequentially.\n\u2022Before this happened -- as the fourth line from the bottom shows -- the program executed its instructions sequentially\n(from +00664 to +00692), but then +00692 passed control to the +051B8, which returned control back to +00692. Most\nlikely, this means that at +00692 the program issued a CICS command.\nIn this manner, you can trace, with great precision, the execution of the program from any point in its logic all the way up\nto the breakpoint. \n 1239", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b8066ed10ec2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNotes:\n\u2022If one of the pieces of code executed a loop, the number of times the loop was executed appears as a decimal number\nunder the appropriate line in the backtrace display.\n\u2022If the  ,GO= element of the InterTest for CICS dispatch command was requested, the change in the logic flow is shown\nin the backtrace display just as if the program executed a branch or a GO TO command.\n\u2022At the beginning of the execution of a COBOL program, a number of lines of the backtrace display only indicate the\nexecution of the COBOL initialization routines. The first statement number shown is the one from which the first branch\ninstruction was executed. This limitation should not pose a problem, since the execution of the Procedure Division\nbegan from the first coded statement.\nExamining Dumps\nTwo kinds of abends,  or abnormal terminations, are of interest to InterTest for CICS users:\n\u2022Abends in CICS during execution of a transaction\nWhen this happens, you must examine the transaction dump associated with the abend to find any InterTest for CICS\nWork Areas (also known as InterTest for CICS Diagnostic Areas). The presence of such an area is a sure indication\nof InterTest for CICS monitoring. Only in this area can you find certain data about the program, such as the values of\nregisters, that you will need to know.\n\u2022Abends in InterTest for CICS transactions (CNTL, CORE, FILE, ITST, LIST, SYMD)\nTo understand why these transactions abend, you need to know how they work in CICS:\n\u2013CNTL and CORE transactions, when necessary, follow the chain of active CICS tasks and the chain of suspended", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b8066ed10ec2-1", "text": "CICS tasks to locate the task whose data is to be displayed, and any other tasks to which the CNTL command\ncould apply. If a chain is damaged, these transactions will abend. Yet, the CICS system might be able to function for\nsome time with these chains damaged, as long as the CICS software does not have to scan all the chains.\n\u2013CORE and FILE transactions are conversational, and can be defined so that they will abend if you take too long to\nrespond with the next command.\n\u2013FILE transaction is simply a generalized application program, and it can abend in situations where the parameters\nyou submit could not be checked sufficiently before the CICS command was issued. In most instances, InterTest for\nCICS does not attempt to check for the same things that the CICS software checks for, because such a duplication\nof effort would significantly increase the size of the InterTest for CICS software; even if those conditions were\ndiscovered by the InterTest for CICS programs, InterTest for CICS would have to issue the abend.\nCICS Abend Codes\nInterTest for CICS issues the following error codes when error conditions are discovered:\nCORE\nIs the same as the transaction code of the CORE transaction at your site. It means that the CORE transaction\nintercepted a CICS abend that makes it impossible to continue the transaction.\nINHA\nIndicates that a program (usually a user program) has corrupted an InterTest for CICS storage area so that\nInterTest for CICS cannot continue processing. Check the CICS statistics to see if any storage violations occurred.\nIf you find any, see which program caused the violation. This would be a program not being monitored by InterTest\nfor CICS.\nINTE\nIndicates that an automatic breakpoint cannot be executed because:\n\u2022The InterTest for CICS automatic breakpoint facility is disabled.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b8066ed10ec2-2", "text": "\u2022The InterTest for CICS automatic breakpoint facility is disabled.\n\u2022There is no terminal on which to show the breakpoint display.\n\u2022The terminal designated to receive the breakpoint display is not a 3270-type CRT (or compatible model).\n 1240", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c26db240eb38-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nINTP\nIndicates that a PLI LE program was linked without CEESTART as its first CSECT and InterTest abends the task\nwith an INTP abend code.\nKERN\nIndicates that the task at a breakpoint could not recover from an abend. If you know the reason (for example, you\nabended the task), ignore this code; otherwise, contact Broadcom support.\nNATI\nIndicates that a breakpoint display is being directed to a terminal that does not have the Automatic Task Initiation\n(ATI) capability. If the status of the terminal is either transceive or receive (preferably, transceive), the terminal has\nthe ATI capability. You can adjust the status by the CEMT service transaction.\nABP and INTE Abend Error Codes\nThe InterTest for CICS Diagnostic Area is printed as one of the user class storage areas in the INTE abend dump. It\ncontains the error code as the first two characters of message XX INTE ABEND..., which can be found at the beginning of\nthe area. The codes and their messages are shown in the following table. These two-character hexadecimal codes appear\nin the Inquiry Repor t, which can be obtained by pressing PF3 from the Breakpoint Display, or by entering CNTL=INQ.\nCode Description\n01 Assembler only; an EX machine instruction issued upon an EX\ninstruction.\n02 An invalid machine instruction code. Note no override by OVR\noption.\n03 This machine instruction not permitted under CICS; for example,\nan SVC.\n04 A privileged machine instruction, illegal under CICS.\n05 An operating system GETMAIN request, as opposed to a CICS\nGETMAIN.\n06 The storage area about to be affected is, entirely or in part,", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c26db240eb38-1", "text": "GETMAIN.\n06 The storage area about to be affected is, entirely or in part,\noutside of the storage that is legally available to this CICS\napplication.\n07 The storage area about to be affected resides outside of the CICS\nregion.\n08 The named program module cannot be found in the program table\n(PPT), its PPT entry is disabled, or it is unavailable to this CICS\napplication.\n09 The program module about to be deleted already has a zero\ncurrent use count.\n0A The Transient Data or Temporary Storage area is incorrectly\nspecified.\n0B This Terminal Control request incorrectly specifies the TIOA\naddress.\n0C The storage area specified for this CICS request does not belong\nto this task or is not a CICS storage area.\n0D InterTest for CICS logic error. Contact Broadcom Support  for\nassistance.\n0E This FREEMAIN request is illegal or specifies a wrong storage\narea address.\n 1241", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "49338f5ad2b7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n0F With this task about to terminate, one or more RELOAD=YES\nprogram modules still do not have their main storage areas\nFREEMAINed.\n10 Possible incorrect length of a temporary storage or transient data\nrecord.\n11 A wild branch or direct machine instruction branch outside of the\nprogram module was detected. If not a mistake, apply the FOL\noption and continue.\n12 Macro level coding only; this CICS macro specifies incorrect\nstorage area.\n13 A GETMAIN request with FLENGTH for more than 65504 bytes\ncan be issued only when the program is in AMODE=31.\n14 An attempt to modify this load module, which is considered\nreentrant, either explicitly (RNT=ON option) or as PL/I or COBOL\nII.\n16 A GETMAIN for 0 bytes of storage has been detected.\n17 Macro level coding only; incorrect length field in a variable-length\nrecord.\n18 Macro level coding only; the DFHFC macro does not specify an\nFWA.\n19 Macro level coding only; the DFHFC macro does not specify the\nstorage area of CLASS=FILE.\n21 InterTest for CICS ordered to continue a task from a breakpoint at\nan incorrect location.\n23 The total number of CICS requests this program issued while\nmonitored in this task exceeded the value specified in the MXR\noption.\n24 The total size of main storage this task is using just exceeded the\nvalue specified in the MXS option.\n25 CICS abend intercepted, but not immediately after the last CICS\nrequest (either macro or command) or another outside CALL\nrecognized by InterTest for CICS.\n26 CICS abend intercepted while a CICS macro was in progress.\n27 CICS abend intercepted while an EXEC CICS command in\nprogress.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "49338f5ad2b7-1", "text": "27 CICS abend intercepted while an EXEC CICS command in\nprogress.\n28 CICS abend intercepted while a CALL outside the program, such\nas a Database request, recognized by InterTest for CICS, was in\nprogress.\n29 EXEC CICS RETURN with TRANSID issued from other than the\ntask's top logical level.\n2C An abend occurred while processing an IN25UEXI routine.\n2D A program check occurred in IN25PGM2.\n34 A protection exception program check caused an ASRA abend\nintercept.\n35 An addressing exception program check caused an ASRA abend\nintercept.\n36 A specification exception program check caused an ASRA abend\nintercept.\n 1242", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "548286ba6a3a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n37 A data exception (invalid packed numeric data format) caused an\nASRA abend intercept.\n38 A fixed point overflow program check caused an ASRA abend\nintercept.\n39 A fixed point divide program check caused an ASRA abend\nintercept.\n3A A decimal overflow program check caused an ASRA abend\nintercept.\n3B A decimal divide program check caused an ASRA abend\nintercept.\n3C An exponent overflow program check caused an ASRA abend\nintercept.\n3D An exponent underflow program check caused an ASRA abend\nintercept.\n3E A significance program check caused an ASRA abend intercept.\n3F A floating point divide program check caused an ASRA abend\nintercept.\nCC The storage area about to be affected by this EXEC CICS\ncommand resides, all or in part, outside the CICS main storage\nlegally available to this application program. The area could have\nbeen specified as INTO ( ), SET ( ) or one of the LENGTHs.\nEntries in the CICS Trace Table\nThe CICS Trace table contains special entries and internal processing entries.\nSpecial Entries\nInterTest for CICS writes special entries into the CICS Trace Table to assist you in your analysis efforts. These entries\nappear in the Trace Table when it is found in a dump, and when it is displayed with a CORE=STRA command (at a\nbreakpoint) or the CORE=TRT command.\nIn the CICS formatted dump, these special entries are identified as follows:\n USER 195.\n \nUnlike the regular CICS-written entries, the InterTest for CICS entries provide displacements, which are the same\ndisplacements you can find in the listing of the program. InterTest for CICS writes these entries into the Trace Table, in", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "548286ba6a3a-1", "text": "addition to those issued by the monitored program and the CICS software, when the monitored program is about to:\n\u2022Issue a CICS request (command).\n\u2022Be stopped at an InterTest for CICS breakpoint or resume execution after an InterTest for CICS breakpoint.\n\u2022Execute an instruction for which InterTest for CICS disregards a presumed error condition because of an OVR\n(Override) option in effect.\n\u2022Issue a DL/I request.\n\u2022Issue a CICS request (command) and the active online NUP= option will affect the request.\n\u2022Issue a call to software defined in the InterTest for CICS IN25UEXI table.\nThe entries issued for these cases consist of two fields, which are described next.\n\u2022Field A contains the displacement of the request (or the breakpoint) from the beginning of the program, expressed as\nfour hexadecimal digits. If the request was made outside the program, this field contains the address instead.\n\u2022Field B contains the following bytes:\n 1243", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "077fa8f8ce42-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2013At a CICS command, bytes 0 to 3 contain four hexadecimal digits that specify the command code (such as, 0204 for\na handle condition).\n\u2013At a breakpoint, bytes 0 to 2 contain the code indicating the type of breakpoint (ABP = automatic breakpoint, UBP =\nunconditional breakpoint, and so on) and byte 3 contains either a B (for Before the breakpoint) or an A (for After the\nbreakpoint).\n\u2013At each override condition, bytes 0 to 2 contain the characters OVR and byte 3 contains the hexadecimal error\nrode. (The OVR option cancels the Automatic Breakpoint display.)\n\u2013At a DL/I request, bytes 0 to 1 contain the characters DL.\n\u2013At an NUP-affected request, bytes 0 to 2 contain the characters NUP (the online NUP= option prevents updates to\nfiles).\n\u2013At a call to InterTest for CICS-recognized software, bytes 0 to 1 contain the characters US and bytes 2 to 3 contain\nthe numeric identifier from the IN25UEXI table.\nInterTest for CICS also writes four entries into the Extents Trace Table when the monitored program is about to pass\ncontrol directly to another program (by a branch instruction and not by a CICS command) and the online FOL= option is\nin effect. These entries are as follows:\n\u2022In field A, the first entry contains the displacement that passes control. In field B, it contains the characters FROM.\n\u2022In fields A and B, the second entry contains the name of the program that passes control.\n\u2022In field A, the third entry contains the displacement that obtains control. In field B, it contains the characters INTO.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "077fa8f8ce42-1", "text": "\u2022In fields A and B, the fourth entry contains the name of the program that obtains control.\nWhen monitoring is dropped because of a BYP option or a request by an IN25UEXI routine, field B contains DROP.\nInternal Processing Entries\nCICS trace table entries for InterTest for CICS internal processing do not appear unless you request them. Normally, you\ndo not want them when you are analyzing your application's processing; the InterTest for CICS program entries might\nconceal your application program entries.\nTo place the InterTest for CICS program entries on the CICS Trace Table, issue the command:\n CNTL=ITTRACE,ON\n \nTo remove the entries, issue the command:\n CNTL=ITTRACE,OFF\n \nTo place the InterTest for CICS common user interface entries on the CICS trace table and log the TCP/IP message\npackets to the MSGUSR DD issue the following command:\n ICDB TRACE_ON\n \nTo remove the entries, issue the command:\n ICDB TRACE_OFF\n \nNote the following:\n\u2022Turn on the ITTRACE before creating a dump for Broadcom Support .\n\u2022These commands have no effect on the CICS Trace Table entries normally made by the monitored program or the\nspecial entries made by InterTest for CICS, which is previously discussed.\n 1244", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2748e5c761e9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUsing the FOL= Option\nNOTE\nAlthough the FOL= option can still be used, it was replaced by Source Listing and CNTL facilities to dynamically\ncalled programs. It is often difficult to debug software that does not follow CICS standards. To use InterTest for\nCICS on such software, you must request the online FOL= option, which enables InterTest for CICS to monitor\na program even when that program passes control to an unknown address (for example, an address that is not\npart of CICS or another interface supported by InterTest for CICS).\nFor more information about how to set and remove the FOL= option, see CNTL Commands and Menus. These topics\nprovide additional background information on how the FOL= option is actually used by the InterTest for CICS system.\nFind the Program Entry\nWhen the FOL= option is in force and the control of the CPU is about to leave the code of the monitored program,\nInterTest for CICS attempts to find out the following:\n\u2022What program is about to receive control\n\u2022What options, such as breakpoints, apply to that program\nInterTest for CICS does this by trying to find the CICS Program entry belonging to the program that is about to receive\ncontrol. If InterTest for CICS can locate this entry, it is possible for InterTest for CICS to use displacements that apply to\nthe beginning of the new program rather than displacements that apply to the old program.\nIf the CICS program entry is found, InterTest for CICS does the following:\n\u2022InterTest for CICS makes four special entries in the CICS Trace Table to indicate which program passed control and\nfrom where it passed control, and which program received control and from where.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2748e5c761e9-1", "text": "from where it passed control, and which program received control and from where.\n\u2022InterTest for CICS begins to show data pertaining to the new program in the breakpoint display. For example, any\ndisplacements in the backtrace portion of the breakpoint screen are calculated relative to the program that just\nreceived control. You also see a short message in the backtrace display to indicate which program passed control\ndirectly to the current one.\nThe CICS program entry is only found if the target program is located or if it resides in main storage. If the program is not\npermanently resident, it is considered only if its current use count is at least one. In addition, InterTest for CICS will not be\nable to find the program entry if control is being passed to a piece of code that does not reside in a storage area used for\nmanaging CICS programs.\nFind the Monitoring Table Entry\nIf the new CICS program entry is found, InterTest for CICS also tries to find the InterTest Monitoring Table entry that\nbelongs to the program that got control directly. This lets the new CICS program assume all options, such as breakpoints,\nthat were declared for the program that is about to receive control.\nIf found, the new InterTest Monitoring Table entry is assumed to be together with all the options associated with this entry.\nHowever, InterTest for CICS carries the FOL= option over such a Monitoring Table switch so that the FOL= option remains\nactive for the remainder of the monitoring effort, even though the Monitoring Table entry that is now in control might not\nhave a FOL= option declared. This means that any options, such as breakpoints, that you want to see applied to the\nprogram that is receiving control can be declared for the Monitoring Table entry associated with the program.\nMoreover, you can declare these options in the most convenient way; for example, breakpoints can be declared by", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2748e5c761e9-2", "text": "displacements, and the UBP= and BYP= options can be declared for displacements and for addresses. The addresses\nensure that if InterTest for CICS cannot find the CICS program and InterTest Monitoring Table entries, it continues\nmonitoring under the Monitoring Table entry of the program that passed control.\nWARNING\nInterTest for CICS disregards the Exclusion Table during the search for the new Monitoring Table entry because\nmonitoring cannot be interrupted at the place of the wild branch. Before InterTest for CICS can interrupt\n 1245", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a45bc1290cce-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nmonitoring, it has to know where control is returned so that later it can resume monitoring. However, the location\nto which control is returned depends on the design of the monitored program, and InterTest for CICS cannot\npredict that. This is why monitoring cannot be interrupted on a wild branch.\nMonitoring Restrictions\nThis article discusses the monitoring restrictions that apply to InterTest for CICS.\nProgram Control Restrictions\nFor InterTest for CICS to be able to monitor a program, it must receive control from the CICS EXECUTE\nINTERFACE PROGRAM (DFHEIP). During startup InterTest for CICS enables the global user exit points XPCFTCH\nand XDUREQ provided by IBM. These points allow a program to assume control of another program during an EXEC\nCICS LINK, an EXEC CICS XCTL, or abend processing. To verify the status of these exits, use the IGLU transaction.\nIf a program is eligible for monitoring by InterTest for CICS, monitoring can begin only if one of the following conditions is\nsatisfied:\n\u2022The program to be monitored is the first program to participate in a transaction. In other words, the program was\nnamed in the CICS Transaction Resource definition.\n\u2022The program to be monitored received control from another program through an EXEC CICS LINK or EXEC CICS\nXCTL.\n\u2022The program to be monitored received control from another program through a direct branch instruction. In addition,\nthe program that passed control must be monitored by InterTest for CICS, and must have the online FOL=option\nactive. For more information, see CNTL Commands and Menus .\n\u2022The program to be monitored received control from another COBOL program using a dynamic call.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a45bc1290cce-1", "text": "\u2022The program to be monitored received control from another COBOL program using a dynamic call.\n\u2022The program to be monitored received control as the abend exit routine. In other words, the program (or part of it), was\nnamed in an EXEC CICS HANDLE ABEND command, executed prior to the abend.\nIf a non-monitored   program passes control to another program directly through a branch instruction rather than an\nEXEC CICS LINK or EXEC CICS XCTL command, monitoring is not set in motion. This is true even though the program\nthat is receiving control is declared in the InterTest for CICS monitoring table. In order to cause monitoring to start in\nthis situation, segmented monitoring may be used or the program issuing the direct branch must be monitored with the\nFOL=option declared. For more information, see the FOL= keyword of the IN25OPTS macro.\nTransaction Definition Restrictions\nThe following CICS transaction definition restrictions apply to all monitored programs:\n\u2022InterTest for CICS program monitoring will not work properly when the Transaction PROFILE Definition specifies\n\u2018ONEWTE(YES)\u2019.\n\u2022Two-terminal testing must be used to monitor programs whose Transaction PROFILE Definition specifies\n'MSGJRNL(INPUT|OUTPUT|INOUT)'.\n\u2022Transactions that will be monitored by InterTest for CICS should not have a DTIMOUT value specified with\nSPURGE=YES. You must specify either SPURGE=NO or DTIMOUT=NO in the Transaction Definition because\nInterTest suspends transactions at a breakpoint. This causes CICS to purge the transaction if SPURGE=YES and the\ntransaction exceeds the DTIMOUT value.\nExecution Restrictions\nAs InterTest for CICS executes the instructions of the monitored program, it must be able to recognize the following\nrequests:\n\u2022Any CICS service requests. This is to prevent InterTest for CICS from monitoring the CICS software.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a45bc1290cce-2", "text": "\u2022Any other means the monitored program could use to pass control to other parts of the application.\n 1246", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "71850ecb06f3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterTest for CICS recognizes CICS service requests if the commands are coded into the monitored program. However,\nit might not recognize calls to the system if the statements that prepare the service request are coded and arranged\ndifferently than as generated by the CICS command translator.\nSpecial Circumstances\nYou should be aware of the following special circumstances:\n\u2022InterTest for CICS will not monitor a program whose name begins with the characters DFH or IN25 unless that\nprogram is specifically declared for monitoring by its program name. Such a program cannot be monitored by\ndeclaring a transaction or terminal for monitoring, or even by declaring the entire application system: InterTest for CICS\nautomatically assumes this program belongs to the CICS system software.\n\u2022You must prevent InterTest for CICS from monitoring certain programs that run under CICS, such as TRUE's, GLUE's,\nand any user replaceable system components (such as DFHPEP). Use the CNTL=EXCL command to exempt these\nprograms from monitoring. You can identify the program, transactions, and terminals to be exempted by giving their full\nidentifications or by using generic identifications. However, it is best to follow the procedure that we recommend and\nalways explicitly declare programs for monitoring by using a CNTL=ON, PROG=... command or by specifying specific\nprograms in the menu system.\n\u2022InterTest for CICS suppresses breakpoints between an EXEC CICS POST and EXEC CICS WAIT EVENT, WAIT\nEXTERNAL, WAIT CONVID, or WAITCICS. When the EXEC CICS WAIT is encountered, breakpoint processing\nresumes. Starting the InterTest for CICS internal VTAT transaction, when a breakpoint is encountered, would freemain\nthe ECB set by the EXEC CICS POST causing the EXEC CICS WAIT to hang waiting on the ECB. Therefore, InterTest", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "71850ecb06f3-1", "text": "for CICS suppresses any type of breakpoint set between the POST and WAIT allowing the application program to\ncontinue normally.\nSYSVIEW  Integration\nThe InterTest CICS Integration with SYSVIEW  Performance Management enables SYSVIEW  to detect application debug\nactivity in an executing CICS Transaction. The detection of debug activity helps you avoid adverse actions by SYSVIEW\nthat are based on the transaction being in a debugging session.\nWhen an application debugger is active during an ongoing execution of a CICS transaction, the transaction might reach\nthreshold goals resulting in the cancellation of the transaction. SYSVIEW  active transactions provide a Debug column\nthat indicates that a debugger has been active for a specific transaction. The column DEBUG  helps determine which\ntransactions are behaving outside of threshold norms due to debugger monitoring activity.\nThe following image is an example of a SYSVIEW screen with the Debug column:\nSYSVIEW 16.0 CA31 ---------------------------- CTASKS, CICS Active Tasks ---------------------------- 01/28/21\n 22:00:37\nCommand ====>                                                                                         Scroll\n *===> PAGE\nGSVX005I Beginning of data columns ---------------------------------------------------- Lvl 2 Row 1-16/16 Col\n 1-119/691\nFormats DEFAULT EIB GLOBAL STORAGE                                                                           \n          \nJobname CICS700V ASID 0059 Jobid JOB33097 CICS 5.3 Mode REGION                                               \n          \n                 Current High Limit AtLimit          CPU Paging IORate TranRate                              \n          \nMax Tasks              3    4    20       0  Job   0.01%  4.483  0.117    0.083                              \n          \nShort On Storage    none                                                                                     \n          \n 1247", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "310ef504eb4e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n-----------------------------------------------------------------------------------------------------------------------\nCmd    Jobname  A Tran   Task# Program  Term WaitType WaitName Debug   CPUTime Lifetime WaitTime ExecTime \n RunTime    \n______ CICS700V   CISR      31 DFHISRRP      IS_INPUT IS_PROCQ         0.000346 13:05:45                     \n          \n______ .          CISM      33 DFHISRSP      IS_SCHED IS_SCHDQ         0.000363 13:05:45                     \n          \n______ .          CISP      34 DFHISPHP                                0.025995 13:05:45                     \n          \n______ .          CEPM       5 DFHEPSY       EPECQEMT EPSUSPND         0.000059 13:05:47                     \n          \n______ .          CSSY       7 DFHAPATT      ICEXPIRY DFHAPTIX         0.002035 13:05:47                     \n          \n______ .          CSTP       9 DFHZCSTP      TCP_NORM DFHZDSP          1.288292 13:05:47                     \n          \n______ .          CSSY       6 DFHAPATT      ICMIDNTE DFHAPTIM         0.000846 13:05:47                     \n          \n______ .          CMPE       4 DFHMPDE       MPDQEMW  MPSUSPND         0.000657 13:05:47                     \n          \n______ .          CSHQ      28 DFHSHSY       SHSYSTEM                  0.007312 13:05:45", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "310ef504eb4e-1", "text": "______ .          CHCK      35 DFHHCHK       ICWAIT                    0.034595 13:05:45                     \n          \n______ .          CISE      32 DFHISEMP      IS_ERROR IS_ERROQ         0.000357 13:05:45                     \n          \n______ .          CEPF      23 DFHECDF       ECDFQEMW ECSUSPND         0.000025 13:05:47                     \n          \n______ .          CSNE      36 DFHZNAC       ZC       DFHZNAC1         0.001216 13:05:45                     \n          \n______ .          ISER      49 IN70SERV      EKCWAIT  SINGLE           0.002021 13:03:45 25.31301         \n 13:03:45    \n______ .          DEMC     105 COBDEMO  E001 ZCIOWAIT DFHZARQ1 DEBUG   0.001221 1.620147 1.618705         \n 1.620108    \n______ .          GSVI      46 GSVCGSVI      USERWAIT GSVIREQS         0.183954 13:03:54                     \n          \n***************************************************** End of Data\n *****************************************************\nThis integration includes the following benefits:\n\u2022The SYSVIEW  dynamic thresholding option, Threshold-Task-Dynamic-AppDebug(=YES), lets you check for the\npresence of an Application Debugger, and bypasses transaction cancelations that result form triggered threshold rules.\n\u2022The dynamic thresholding option eliminates the need to change the threshold rules each time a debugger is active in a\ntightly monitored CICS region.\nAccess CTASKS", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "310ef504eb4e-2", "text": "tightly monitored CICS region.\nAccess CTASKS\nYou can access SYSVIEW  CTASKS through SYSVIEW  Plug-in for Zowe CLI, or through SYSVIEW  ISPF screens.\nZOWE CLI\nTo locate specific fields, use the fields command as shown in the following example:\nzowe sysview display \u201cACTIVITY;ASID CICSJOB1;CTASKS;\u201d -fields Jobname Tran Program Debug\nSYSVIEW  ISPF Screens\nSet your CICS job to the current ASID and enter CTASKS command.\n 1248", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "34077209ba3e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nDebugging activities are also available in the Transaction history which includes a message Application\ndebugging was active for transaction .\nThis capability, included in PTF SO15873 , is supported in InterTest for CICS-V11, and SYSVIEW  -V16.\nCICS Abend Analysis\nSymDump  for CICS improves your ability to analyze and resolve application program problems.\nIdeally, you could monitor every program and catch every error with a product like InterTest for CICS. Realistically, this is\nnot possible either because of overhead or because you may not want to monitor security programs or programs using\nnonstandard code. As a result, dumps occur -- especially in production where even a thoroughly debugged program\nabends because of bad data, scheduling errors, invalid parameters, and many other factors beyond programmer control.\nWith SymDump  for CICS, you can do the following actions:\n\u2022View captured dumps using the SymDump  for CICS SYMD Transaction or the Eclipse-based Graphical User Interface\n(Eclipse UI).\n\u2022Analyze dumps symbolically to resolve application dumps that occur in production and test systems. You can then\nsolve these problems easily online using the Source Listing Dump Analysis screen. When examining a dump using this\nscreen, your source listing displays at the instruction that triggered the abend. For more information about performing\nsymbolic dump analysis and using the Source Listing Dump Analysis screen, see Working with Dumps.\n\u2022Locate problems easily when you do not have a symbolic dump. Use the SymDump  for CICS Abend Analysis display\nto avoid having to analyze hexadecimal dumps. This display pinpoints the instruction that caused the abend, explains\nthe nature of the abend, and gives you simple and quick access to the instruction and its operands in main storage.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "34077209ba3e-1", "text": "\u2022Immediately resolve CICS production problems from any region; for example, debug production abends from your test\nregion. With SymDump  for CICS you can analyze the dump online to resolve the problem promptly, without  using a\nmonitoring facility. For more information, see Production Strategies .\n\u2022Easily display a wide range of data about your dump through formatted and main storage displays.\n\u2022Manage your dump data set so you can selectively retain, view, and print the dumps you need, and discard the ones\nyou do not.\n\u2022Reference your program's symbolic listing easily. SymDump  for CICS lets you maintain multiple symbolic listings\nfor a program and decide how much of the listing to keep on the symbolic file. SymDump  for CICS symbolic file\nmanagement saves valuable disk space since the listings are compressed.\n\u2022Capture and review the CICS Internal Trace table.\nThe following restrictions apply:\n\u2022View only dumps captured under the same CICS release.\n\u2022View only dumps captured by the same version of SymDump  for CICS.\n\u2022Stopping and starting SymDump  for CICS loads a new copy of IN25COLD. (A NEWCOPY cannot be performed for\nIN25COLD).\nBecause SymDump  for CICS and InterTest for CICS are completely integrated, you can access any InterTest for CICS\nfunction from within SymDump  for CICS. For example, while using SymDump  for CICS to analyze a dump you can access\nInterTest for CICS to set breakpoints whenever the need arises.\nCORE Keywords\nSymDump  for CICS supports the following CORE keywords:\nABND DLP PROG=* TCT\nBLL DSA REG TERM\n 1249", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dedc57d18445-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBLLS EIB REGS TGT\nBLX EIS RSA TUAR\nBLXS EISTG SCAB TWA\nBWD FIND= SCAN USE=\nCLOT L= SQLCA WKAR\nCMAR LCL SQLRCODE USER\nCSA OPFL SSCR WHERE\nCURR PGM STCA\nCWA PGM=* TCA\nCWK PROG TACB\nSymDump  for CICS does not support the following CORE keywords, but InterTest for CICS does. To look at any of these\nCICS storage areas, access them through InterTest for CICS.\nARG EMSG JCA PPT\nBMSG END LLA PREV\nCHG FAKE LOAD PROM\nDCT FCT MAP= SET=\nDELETE FILE MOVEIN SIT\nDEST FINDTRAN MXR SSCR\nDLTE HLST MXS TAL\nDSA IUSER OPTS TRAN\nDUMP IF= PCT TRUE\nDWE ITBE PEAPX VER\nMenus\nMenus let you access all SymDump  for CICS functions easily.\nTo access the SymDump  for CICS menus use one of the following methods:\n\u2022From CICS, enter the transaction ID SYMD  from a clear CICS screen. The SymDump  for CICS Primary Option menu\nappears.\n\u2022You can also access the SymDump  for CICS Primary Option menu from the InterTest for CICS Primary Option menu\nby selecting option 5 Dump Analysis .\nThe following sample screen is the SymDump  for CICS Primary Option Menu:\n----------------  CA SymDump for CICS   PRIMARY OPTION MENU -----------------\n OPTION  ===>                                                                 \n1 Analysis           - Display/select captured CICS dumps/traces          \n2 Tracing            - Capture CICS internal trace for analysis", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dedc57d18445-1", "text": "2 Tracing            - Capture CICS internal trace for analysis           \n3 Configuration      - Display/modify CA-SymDump initialization parameters\n4 Start              - Start dump capture facility                        \n5 Stop               - Stop dump capture facility                         \n6 Source             - Display/select program source files/listings    \n7 Status/Maintenance  -  Product status and maintenance functions\n 1250", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5c6d871fddbe-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n8 What's new?        - Display information about CA SymDump for CICS\nX Exit               - Terminate CA-SymDump menu processing               \n \n PF1 Help       2            3 End        4 Return     5            6         \n PF7            8            9           10           11           12         \nFrom the Primary Option menu, you can access all SymDump  for CICS functions. A brief summary of each option follows.\n1 Analysis\nSpecifies selection criteria for the dumps and traces you want to access.\n2 Tracing\nCaptures the CICS Internal Trace table and writes it to the PROTDMP file.\n3 Configuration\nSets or updates parameters for capturing dumps.\n4 Start\nStarts the dump capture facility.\n5 Stop\nStops the dump capture facility.\n6 Source\nSelects program source files and listings for display.\n7 Status/Maintenance\nStatus\nProvides online displays of SymDump  for CICS product components, including the genlevel, global\ninstallation options, and what maintenance has been applied.\nMaintenance\nAllows a help administrator to maintain the optional user help file entries of user-defined abend codes and\ndescriptions.\n8 What's New\nDisplays online help topics listing the new features for this release.\nX Exit\nExits menu processing.\nYou can bypass this menu and go directly to one of the SymDump  for CICS options by entering SYMD x , where x is the\noption number listed on the Primary Option menu. For example, enter SYMD 1 from a clear CICS screen to go directly to\nthe Analysis screen.\nNOTE\nFrom InterTest for CICS menus , enter 5.x from the InterTest for CICS Primary Option menu command line,", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5c6d871fddbe-1", "text": "where x is the option number listed on the SymDump  for CICS Primary Option menu. You can also quickly exit\nany menu by using =X.\nStandard PF Keys\nPF key assignments are standard across all SymDump  for CICS menus. The following is a list of the standard PF key\nassignments.\nPF1 Help\nDisplays a Help menu relating to the current screen.\n 1251", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0c2a17c7787d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPF2\nUnassigned.\nPF3 End\n(End or Clear) Terminates the current screen.\nPF4 Profile\nDisplays the Source Listing Profile screen where you can set values for your current session.\nPF6 Menu\nDisplays the Primary Option menu.\nPF7 Backward\nScrolls backward one page unless the setting was changed on the Profile.\nPF8 Forward\nScrolls forward one page unless the setting was changed on the Profile.\nPF9, PF10, PF11\nUnassigned.\nCapturing Dumps\nThe dump capture facility runs under the CICS Global User Exit facility and must be started before it can begin capturing\nCICS Transaction abend.\nThis article describes how to use SymDump  for CICS to capture dumps.\nContents:\nConfigure a Dump Capture\nThe SymDump  for CICS Configuration menu lets the systems programmer set or update parameters for capturing dumps.\nConfiguration parameter defaults are specified when you define the PROTDMP file using IN25INIT. Access to these\nfunctions may be restricted at your site.\nNOTE\nIf you update the configuration parameter, you must restart SymDump  for CICS for the new parameters to take\neffect. For more information, see Activate Your Product.\nAccess the Configuration Menu\nYou can access the Configuration menu using one of the following methods:\n\u2022Select option 3 Configuration  on the SymDump  for CICS Primary Option menu\n\u2022Type SYMD 3 from a clear CICS screen\nThe Configuration menu appears.\n           CA SymDump for CICS  - Configuration              \n COMMAND ===>                                                                  \n CASD6960  CA SymDump for CICS is active                                       \n Overtype the parameters you want to change, then press ENTER                  \n Suppress AP0001 dumps:          Y (Y,N)    Messages to operator:       N (Y,N)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0c2a17c7787d-1", "text": "Suppress transaction dumps:     N (Y,N)    Capture EXEC CICS dumps:    Y (Y,N)\n Automatic purge of dumps:       Y (Y,N)    Dump only current program:  N (Y,N)\n Automatic purge hold days:      7 (0-99)   Dump select start date: 06/01/2000 \n Dynamic purge of oldest dump:   N (Y,N)               (CURRDATE or MM/DD/YYYY)\n Suppress duplicate dumps:       Y (Y,N)                                       \n 1252", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bff78225842f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n Duplicate dump limit:           3 (0-999)                                     \n Enter abend codes to be EXCLUDED:    '*' is generic character                 \n ____             ____             ____             ____           ____        \n ____             ____             ____             ____           ____        \n ____             ____             ____             ____           ____        \n ____             ____             ____             ____           ____        \n \n PF1 Help       2            3 End        4            5            6          \n PF7            8            9           10           11           12          \nNote: A message at the top of the screen indicates whether SymDump  for CICS dump capture is active.\nAfter entering values for the configuration parameters, press Enter. SymDump  for CICS prompts you to press Enter to\nconfirm the parameter update request or to press PF3 to cancel the updates.\nConfiguration Parameters\nThe following configuration parameter descriptions contain the format and valid values for each entry.\nSuppress AP0001 Dumps\nSpecifies whether to suppress full AP0001 SVC dumps for ASRA and ASRB abends.\nEnter Y or N\nNOTE\nIf you specify N, dumping conforms to the specifications defined for your CICS system.\nDefault: Y\nSuppress Transaction Dumps\nSpecifies whether to write a transaction dump to the CICS dump data set.\nEnter Y or N\nDefault: Y\nAutomatic Purge of Dump\nSpecifies whether to automatically purge dumps during SymDump  for CICS startup. Purging qualification is\ndetermined by age as set in the field Automatic Purge Hold Days.\nNOTE\nDumps with a HOLD indicator (set from the Dump/Trace Selection screen) are not purged.\nEnter Y or N;\nDefault: Y\nAutomatic Purge Hold Days", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bff78225842f-1", "text": "Enter Y or N;\nDefault: Y\nAutomatic Purge Hold Days\nIf Automatic Purge of Dumps is set to Y, specify the number of days to retain nonheld dumps before they are\npurged.\nSpecify 0 days to purge all dumps without a HOLD indicator at SymDump  for CICS startup.\nLimits: Enter a number from 0 to 99, inclusive\nDefault: 1\nDynamic Purge of Oldest Dump\nSpecifies whether to allow SymDump  for CICS to dynamically purge nonheld dumps during dump capture on a\nFIFO basis. Dynamic purging only occurs when there is insufficient space to hold the dump being captured, and\ndeletes no more dumps than required to get space for the new dump. Automatic Purge Hold Days is ignored for\ndynamic purges.\nEnter Y or N\nDefault: N\n 1253", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "06c2f689f06d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSuppress Duplicate Dumps\nSpecifies whether duplicate dump suppression is in effect. A dump is considered to be a duplicate when an abend\nhas a matching program or offset with a previously captured dump.\nEnter Y or N\nIf set to Y, dumps are suppressed after the Duplicate Dump Limit is reached.\nDefault: N\nNOTE\nIf the dumps that are suppressed by this parameter match the criteria specified in the IN25CAPT\nCapture List then those dumps are captured. The status of the dump changes to Force/Capt.\nDuplicate Dump Limit\nSpecifies the maximum number of duplicate dumps to capture for a given occurrence of program or offset.\nNOTE\nThis parameter is recognized only when Suppress Duplicate Dumps is set to Y.\nEnter a number from 0 to 999, inclusive\nDefault: 1\nNOTE\nIf the dumps that are suppressed by this parameter match the criteria specified in the IN25CAPT\nCapture List then those dumps are captured. The status of the dump changes to Force/Capt.\nMessages to Operator\nSpecifies whether to write SymDump  for CICS informational messages to the console when dump or trace\nrequests are intercepted by SymDump  for CICS.\nEnter Y or N\nDefault: Y\nCapture EXEC CICS Dumps\nSpecifies whether SymDump  for CICS should capture transaction dumps produced by EXEC CICS DUMP\ncommands.\nEnter Y or N\nDefault: Y\nDump Only Current Program\nSpecifies whether the dump should include just the active program or all linked and loaded programs.\nEnter Y or N\nDefault: Y\nDump Select Start Date\nSpecifies the date dump selection starts.\nEnter a date in the format mm/dd/yyyy or specify CURRDATE for the current date.\nDefault: CURRDATE (current date)\nEnter Abend Codes to be Excluded", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "06c2f689f06d-1", "text": "Default: CURRDATE (current date)\nEnter Abend Codes to be Excluded\nEnter the abend codes for which symbolic dumps should not be written to the SymDump  for CICS data set or\nCICS dump data set.\nEnter any CICS dump or abend code in the format xxxx. You can use an asterisk to represent a generic character;\nfor example, USR* excludes all dump and abend codes beginning with USR.\nDefault: None\nNOTE\nIf the dumps that are suppressed by this parameter match the criteria specified in the IN25CAPT\nCapture List then those dumps are captured. The status of the dump changes to Force/Capt.\n 1254", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ea6ae4f671e4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nStart and Stop a Dump Capture\nUsers can view dumps or traces online even if SymDump  for CICS dump capture has not been started. However,\nSymDump  for CICS cannot write or capture dumps or traces unless the dump capture facility is active.\nNOTE\nAccess to these functions may be restricted at your site.\nStart the Dump Capture Facility\nTo start the SymDump  for CICS dump capture facility, do one of the following actions:\n\u2022Select option 4 Start on the SymDump  for CICS Primary Option menu\n\u2022Type SYMD 4  from a clear CICS screen\nNOTE\nSites can choose to initiate SymDump  for CICS dump capture automatically at CICS startup. For more\ninformation, see Start and Stop Dump Capture Facility.\nStop the Dump Capture Facility\nTo stop the SymDump  for CICS dump capture facility, do one of the following actions:\n\u2022Select option 5 Stop  on the SymDump  for CICS Primary Option menu\n\u2022Type SYMD 5  from a clear CICS screen\n Working with Dumps\nThis article explains how to select the dumps with which to work, use the Dump/Trace Selection List, view dumps and\ntheir information, and how to delete, hold, and release dumps.\nSpecify Selection Criteria\nAfter the dumps are captured, you must specify the SymDump  for CICS data set and other selection criteria to select the\ndumps and traces with which you want to work. You do so using the Dump/Trace Analysis screen.\nSelect Dumps and Traces\nYou can use the following procedure to select dumps and traces with which to work.\nFollow these steps:\n1.Access the Dump/Trace Analysis screen.\n2.Select option 1 Analysis  on the Primary Option menu.\nThe Dump/Trace Analysis screen appears.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ea6ae4f671e4-1", "text": "The Dump/Trace Analysis screen appears.\n--------- CA SymDump for CICS  DUMP/TRACE ANALYSIS  -----------\n COMMAND ===>                                                        \n   Type captured dump/trace selection criteria, then press ENTER.  \n   Dump File ID PROTDMP_          (*+), Required     \n   CICS applid  ________  (*+)\n   User ID  . . _                 (*+)_______                        \n   Program  . .                   (*+)________                       \n   Transaction                    (*+)____                          \n   Dump code  .  (*+)                    ___                       \n   Terminal . . ____                                                 \n   Start date . 01/01/1998        mm/dd/yyyy                          \n 1255", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7a88f3982355-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n   Start time . 00                hh                                  \n   End date . . 04/23/2000        mm/dd/yyyy                          \n   End time . . 24                hh                                  \n   (*+) Wildcard characters are allowed\n                                                                      \n PF1 Help       2            3 End        4 Return     5            6 \n PF7            8            9           10           11           12 \n3.Specify the information as necessary. Press Enter to continue, or press PF3 to exit this screen and return to the\nPrimary Option menu without processing the specifications.\nDump and Trace Analysis Fields\nUse the following fields or sections available on the Dump/Trace Analysis screen to select the dumps and traces with\nwhich you want to work:\nDump File ID\nEnter an explicit or masked name for the SymDump  for CICS dump data sets from which you want to select\ndumps.\nA value for this field is required; all other fields are optional.\nLimits:  The Dump File ID name must be 1- to 7-alphanumeric characters in length. It must match the FILE name\nfor the dump data set or include wildcard characters that broaden the search for the dump file FILE name.\nValid wildcard characters are * and +.\n\u2022Use * for a string of any length\n\u2022Use + for a single character\n\u2022Example: DU* searches all dump file names whose file name starts with DU, and DU++++P searches all\ndump file names whose file name starts with DU and whose seventh character is a P.\nDefault:  The SymDump  for CICS dump data set name for your CICS region.\nCICS Applid\nSpecify the applid of the CICS region from which dumps are selected if the dump data set contains dumps from\nmore than one region.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7a88f3982355-1", "text": "more than one region.\nEnter any valid CICS applid from 1 to 8 alphanumeric characters in length Wildcard characters * and + are\npermitted.\nDefault:  None\nUser ID\nSpecify the user ID to select dumps produced by a specific user ID.\nEnter any valid user ID from 1- to 8-alphanumeric characters in length. Wildcard characters * and + are permitted.\nDefault:  None\nProgram Name\nSpecify a program name to select dumps produced only by that program.\nEnter a name from 1- to 8-alphanumeric characters in length. Wildcard characters * and + are permitted.\nDefault:  None\nTransaction\nSpecify a transaction ID to select dumps produced only by that transaction.\nEnter a value in the format  xxxx . Wildcard characters * and + are permitted.\nDefault:  None\nDump Code\nSpecify the dump code to select dumps with a specific code.\nEnter any CICS dump or abend code in the format xxxx. Wildcard characters * and + are permitted.\nDefault:  None\n 1256", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "17b601216245-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTermid\nSpecify the terminal ID to select dumps for transactions running at a specific terminal.\nEnter any valid terminal ID in the format xxxx. A generic character is  not permitted.\nDefault:  None\nStart Date\nSpecify the month, day, and year from which SymDump  for CICS should begin selecting dumps.\nEnter a date in the format mm/dd/yyyy .\nDefault:  Set by the configuration parameter Dump Select Start Date.\nStart Time\nSpecify the hour from which SymDump  for CICS should begin selecting dumps.\nEnter a time in the format hh.\nLimits: Valid values are 00 to 24 (a 24-hour clock is assumed).\nDefault:  0; set by the configuration parameter Dump Select Start Date.\nEnd Date\nSpecify the month, day, and year at which SymDump  for CICS should stop listing dumps.\nEnter a date in the format  mm/dd/yyyy.\nDefault:  The current date.\nEnd Time\nSpecify the hour at which SymDump  for CICS should stop listing dumps.\nEnter a time in the format hh.\nLimits: Valid values are 00 to 24 (a 24-hour clock is assumed).\nDefault:  0\nNOTE\nLeave the default values for the Start Date, Start Time, End Date, and End Time parameters to list only\nthose dumps generated on the current  day. Use the EOF key to blank out the default values to list all\ndumps in the data set.\nSpecify Criteria for Dump Selection\nThe following sample shows how to specify criteria for dump selection. According to the specifications shown, SymDump\nfor CICS lists only those dumps in file PROTDMP that were generated from 8 a.m. on March 22, 2000, through 5 p.m. on\nthe same day.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "17b601216245-1", "text": "the same day.\n--------------  CA SymDump for CICS DUMP/TRACE ANALYSIS  -----------------\n COMMAND ===>                                                   \n \n   Type captured dump/trace selection criteria, then press ENTER.  \n \n   Dump File ID PROTDMP_ (*+), required\n   CICS applid  ________ (*+)\n   User ID  . .                   (*+)________                        \n   Program  . .                   (*+)________                          \n   Transaction                    (*+)____                            \n   Dump code  . __                (*+)__                              \n   Terminal . . ____                                                \n   Start date . 03/22/2000        mm/dd/yyyy                       \n   Start time . 08                hh                               \n   End date . . 03/22/2000        mm/dd/yyyy                      \n   End time . . 17                hh                                \n   (*+) Wildcard characters are allowed\n PF1 Help       2            3 End        4 Return     5            6 \n 1257", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aa9950b96fe1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n PF7            8            9           10           11           12 \nSelect Dumps from Another CICS Region\nIf the region whose dumps you want to access has its own SymDump  for CICS dump data set.\nAccess Dumps\nTo access dumps in a region that has separate dump data sets\n1.Change the default dump file name on the Dump/Trace Analysis screen to the dump file name of the region for which\nyou want to access dumps. Your CICS region must have an FCT entry and the necessary startup JCL for that file.\n2.Set the CICS applid to the applid of the CICS region for which you want to access dumps or leave it blank.\nSymDump  for CICS generates a list of only those dumps from the specified dump file that meet the other selection\ncriteria you specified on the Dump/Trace Analysis screen. Files on the specified dump file that are not dumps are\nexcluded from the generated selection list.\nAccess Shared Dump Data Sets\nTo access shared dump data sets (where two regions write dumps to the same data set)\n1.On the Dump/Trace Analysis screen, do not change the default dump file name.\n2.Change the CICS applid to the applid of the CICS region for which you want to access dumps.\nNote: Two CICS regions can write dumps to the same data set only  if they are not active at the same time.\nDump/Trace Selection List\nAfter you specify the criteria for dump selection on the Dump/Trace Analysis screen, SymDump  for CICS lists the dumps\nthat meet your criteria on the Dump/Trace Selection screen. From this list, you can select dumps to view online, delete,\nhold for future use, or release from a previously specified hold.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aa9950b96fe1-1", "text": "hold for future use, or release from a previously specified hold.\nNote: If the dump or trace you are looking for does not appear on the Dump/Trace Selection screen, check your selection\ncriteria on the Dump/Trace Analysis screen. Since only dumps and traces that meet your selection criteria appear on the\nDump/Trace Selection screen, you may need to change your selection criteria.\nCollapse and Expand Branches\nThe selection list on the Dump/Trace Selection screen is an expandable, collapsible tree structure, similar to InterTest for\nCICS Monitoring Status report. Each dump file that met your selection criteria is a branch on the tree. There are several\nways to collapse and expand branches.\nTo collapse or expand branches use one of the following methods:\nFrom the command line:\n\u2022Type collapse or expand on the command line to collapse or expand all of the branches in the display tree.\n\u2022Using PF keys:\n\u2013Press PF5 to collapse all of the branches in the display tree.\n\u2013Press PF6 to expand all of the branches in the display tree.\nFor individual dump files:\n\u2022Type a plus sign (+) next to a dump file name that has a + indicator next to it to expand that branch.\n\u2022Type a minus sign (-) next to a dump file name that has a - indicator next to it to collapse the branch.\nAfter typing the plus or minus sign, press Enter.\n 1258", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1d4f79078bd2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nExample Dump/Trace Selection List (Collapsed View)\nThe following sample screen shows that two dump files met the selection criteria entered with a mask of PROTD* on the\nDump/Trace Analysis screen. Each dump file is a branch on the tree.\n --------------- CA SymDump for CICS DUMP/TRACE SELECTION ----------------\n COMMAND ===>                                                                  \n \n   Type S select,  D delete, H hold, R release, I history                       \n \n     Dumpfile  Tran  Program   Offset  Abend       Created        # Dups  Status\n _ + PROTDMP   DEC2  COB2DEMO  001188  ASRA  07/22/2000 12:48:49       2       \n _ + PROTDM2   TCB   FINDTCB   0001FE  ASRA  07/15/2000 09:23:46               \n   *** End of data ***                                                         \n \n \n \n PF1 Help       2            3 End        4 Return     5 Collapse   6 Expand   \n PF7 Backward   8 Forward    9           10           11           12         \nExample Dump/Trace Selection List (Expanded View)\nThe expanded view follows. It lists all of the dumps that met the Dump/Trace Analysis screen selection criteria grouped by\ndump file name.\n--------------- CA SymDump for CICS DUMP/TRACE SELECTION  ----------------\n COMMAND ===>                                                                  \n \n   Type S select,  D delete, H hold, R release, I history                       \n \n    Dumpfile  Tran  Program   Offset  Abend       Created        # Dups  Status", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1d4f79078bd2-1", "text": "Dumpfile  Tran  Program   Offset  Abend       Created        # Dups  Status\n _ - PROTDMP   DEMC  COBDEML   000812  ASRA  07/22/2000 12:50:20       2\n _   |-        DEMC  COBDEML   000812  ASRA  07/22/2000 12:50:08       2       \n _   |-        DEC2  COB2DEMO  001188  ASRA  07/22/2000 12:48:49       2       \n _   |-        DEC2  COB2DEMO  001188  ASRA  07/22/2000 12:48:40       2       \n _   |-        DEMC  COBDEMO   001B86  ASRA  07/22/2000 12:48:16       5       \n _   |-        DEMC  COBDEMO   001B86  ASRA  07/22/2000 12:48:07       5       \n _   |-        DEMC  COBDEMO   001B86  ASRA  07/22/2000 12:47:47       5       \n _ + PROTDM2   TCB   FINDTCB   0001FE  ASRA  07/15/2000 09:23:46               \n   *** End of data ***                                                         \n .                                                                            \n .\n .\n PF1 Help       2            3 End        4 Return     5 Collapse   6 Expand   \n PF7 Backward   8 Forward    9           10           11           12         \nThe expanded listing shows the following information for each dump:\nDumpfile", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1d4f79078bd2-2", "text": "The expanded listing shows the following information for each dump:\nDumpfile\nSpecifies the file ID of the dump data set.\nTran\nIdentifies the transaction that produced the dump, or *Duplicate* if the listing represents a duplicate abend of the\nprior listing.\n 1259", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9255d9a1ce19-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nProgram\nIdentifies the program that produced the dump, or if SYMT was used to capture the CICS Interval Trace Table, the\nprogram that produced the trace .\nOffset\nSpecifies the program offset that triggered the abend.\nAbend\nIdentifies the abend code when the dump was produced.\nCreated\nSpecifies the d ate and time when the dump was produced.\n# Dups\nSpecifies the total number of duplicate dumps detected for this abend entry. This number can be greater than the\nduplicates listed on the dump file if duplicate dump suppression is set to yes.\nStatus\nSpecifies the status of the dump; for example, whether it has been selected, deleted, placed on hold, or released.\nThis column is blank if you have not specified an option for the dump.\nList Order and Navigation\nWithin a dump file, the dumps are sorted by creation date and time with the most recent dump listed first and the oldest\ndump listed last.\nPress PF8 to page forward through the list; press PF7 to page backward.\nTo scroll up or down a specific number of lines, enter UP xx or DOWN xx from the Command line. For example, DOWN 10\nscrolls to the tenth listing on the display.\nYou can resort the sequence of the dump tree or list by specifying the SORT command on the command line. The syntax\nof the SORT command is:\nSORT {DUMPFILE|TRAN|PROGRAM|OFFSET|ABEND|CREATED} {A|D}\nIf you do not specify the third parameter, the default sequence is ascending. If you do not specify any parameters with the\nSORT command, the dump list is sorted by its default sort sequence, which is ascending by DUMPFILE and descending\nsequence by CREATED.\nView Duplicate Abends", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9255d9a1ce19-1", "text": "sequence by CREATED.\nView Duplicate Abends\nSymDump  for CICS identifies duplicate abends on the selection list in the # Dups column. Duplicate dumps show the\nsame entries on the selection list, except for the creation date and time. For duplicate dumps, the most recent dump is\nlisted first and the oldest dump is listed last.\n\u2022The first dump listed on the PROTDMP dump file was produced by the DEC2 transaction. An abend occurred in\nprogram COB2DEMO at offset 001188, producing an ASRA abend code. The abend occurred on July 22, 2000 at\n12:48:49. This dump is being held; in other words, it cannot be deleted until released.\n\u2022The second dump shows the same information as the first dump other than the creation time. The same transaction,\nprogram, and offset produced the ASRA, just eight seconds earlier on the same day, July 22, 2000.\nThe following selection list shows the information discussed previously.\nDumpfile  Tran  Program   Offset  Abend       Created        # Dups  Status\nPROTDMP   DEC2  COB2DEMO  001188  ASRA  07/22/2000 12:48:49       2  *HOLD*\n          DEC2  COB2DEMO  001188  ASRA  07/22/2000 12:40:40       2       \n 1260", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a3949f74cb82-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDump Options\nYou can specify the dump options from the Dump/Trace Selection screen to view, delete, hold, or release dumps or view\nthe status.\nFollow these steps:\n1.Open the Dump/Trace Selection screen.\n2.Specify one of the following options:\nNOTE\nYou can specify an option for more than one dump.\n3.Do one of the following tasks after specifying your options:\n\u2013Press Enter to process the options. The Status column shows the options you specified.\n\u2013Press PF3 to return to the Dump/Trace Analysis screen. The information you previously entered on that screen is\nretained.\n\u2013Press PF4 to return to the Primary Option menu.\nExample Specify Options for Dumps\nThis example shows that:\n\u2022The two dumps from the DEMP transaction are being held for later use. These dumps will not be deleted even if the\nSymDump  for CICS data set becomes full or they become eligible for deletion by the automatic purge option\n\u2022The latest dump for the ASRA produced by transaction DEMC, program COBDEMO, is viewed online\n\u2022The two duplicate dumps for the COBDEMO ASRA are deleted after the delete requests are confirmed\n--------- CA SymDump for CICS DUMP/TRACE SELECTION  --------------\n COMMAND ===>                                                          \n \n   Type S select,  D delete, H hold, R release, I history                       \n                                                                                \n     Dumpfile Applid   Tran Program  Offset Abend  Created         Dups Status  \n _   |-        DEMC  COBDEMO   001B86  4544  07/25/2000 15:56:59        \n h   |-        DEMP  PL1DEMO   002CBC  AEIL  07/23/2000 11:46:34", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a3949f74cb82-1", "text": "h   |-        DEMP  PL1DEMO   001A6E  ASRA  07/22/2000 12:49:16       2 \n _   |-        DEMP  PL1DEMO   001A6E  ASRA  07/22/2000 12:49:01       2\n s   |-        DEMC  COBDEMO   001B86  ASRA  07/22/2000 12:48:16       5\n d   |-        DEMC  COBDEMO   001B86  ASRA  07/22/2000 12:48:07       5\n d   |-        DEMC  COBDEMO   001B86  ASRA  07/22/2000 12:47:47       5\n .\n .\n .\nExample Review the Status of Dumps in the Duplicate Suppression History Panel\nYou can specify option I from the Dump/Trace Selection screen to review the status of dumps on the Duplicate\nSuppression History panel. This panel indicates the status of duplicates for a selected dump, whether the duplicate dumps\nwere suppressed or captured.\nFollow these steps:\n1.Open the Dump/Trace Selection screen.\n2.Specify option I for any dump and press Enter.\nNOTE\nYou can specify the option for more than one dump.\n 1261", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "760180ffa1a0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                 CA SymDump for CICS DUMP/TRACE SELECTION         \n COMMAND ===>                                                                   \n                                                                                \n   Type S select,  D delete, H hold, R release, I history                       \n                                                                                \n     Dumpfile Applid   Tran Program  Offset Abend  Created         Dups Status  \n _ - PROTDMP  A11ICICX SYMD *TRACE*         SYMT 12/07/12 13:49:32              \n _ - |-       A11ICICX DE39 C390DEMO 001196 APCT 12/07/12 09:05:40    3         \n _ - |-       A11ICICX DE39 C390DEMO 001196 APCT 12/07/12 09:05:37    3         \n _ - |-       A11ICICX DE39 C390DEMO 001196 APCT 12/07/12 09:05:30    3         \n _ - |-       A11ICICX DE37 C370DEMO 0010EC APCT 12/07/12 09:05:27    3         \n _ - |-       A11ICICX DE37 C370DEMO 0010EC APCT 12/07/12 09:05:24    3         \n _ - |-       A11ICICX DE37 C370DEMO 0010EC APCT 12/07/12 09:05:21    3         \n i - |-       A11ICICX DEMV CMVSDEMO 00118E APCT 12/07/12 09:05:10    3", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "760180ffa1a0-1", "text": "_ - |-       A11ICICX DEMT ASMDEMO  0001BE ASRA 12/07/12 09:05:05    3         \n _ - |-       A11ICICX DEMT ASMDEMO  0001BE ASRA 12/07/12 09:05:00    3         \n _ - |-       A11ICICX DEMT ASMDEMO  0001BE ASRA 12/07/12 09:04:57    3         \n _ - |-       A11ICICX DEMC COBDEMO  001294 ASRA 12/07/12 09:04:35    4 * *SLCT*\n _ - |-       A11ICICX DEMC COBDEMO  001294 ASRA 12/07/12 09:04:27    4         \n _ - |-       A11ICICX DEMC COBDEMO  001294 ASRA 12/07/12 09:04:22    4         \n _ - |-       A11ICICX DEMC COBDEMO  001294 ASRA 12/07/12 09:04:18    4         \n                                                                                \n PF1 Help       2            3 End        4 Return     5 Collapse   6 Expand    \n PF7 Backward   8 Forward    9           10           11           12  \nThe Duplicate Suppression History panel opens.\nThe following example shows that the selected dump has three duplicates but only a single entry is available from the\nlist.\n             CA SymDump for CICS Duplicate Suppression History     \n COMMAND ===>                                                                   \n                                                                                \n          Dumpfile   Tran  Program   Offset  Abend #Dups", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "760180ffa1a0-2", "text": "Dumpfile   Tran  Program   Offset  Abend #Dups                        \n          PROTDMP    DEMV  CMVSDEMO  00118E  APCT    3                          \n                                                                                \n          APPLID   USER     TASK  TERM      CREATED      STATUS                 \n          A11ICICX CICSUSER 00067 U056 12/12/07 09:05:17 SUPPRESSED             \n          A11ICICX CICSUSER 00066 U056 12/12/07 09:05:15 SUPPRESSED             \n          A11ICICX CICSUSER 00065 U056 12/12/07 09:05:10 CAPTURED               \n          *** End of data ***                                                   \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7 Backward   8 Forward    9           10           11           12  \n 1262", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b6364b001071-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe previous example shows that dumps were suppressed after the first dump was captured, because the duplicate\nlimit was set to 1.\n3.Review the status column.\nSuppressed\nIndicates that the selected dump has been suppressed.\nCaptured\nIndicates that the selected dump has been captured.\nForce Captured\nIndicates that the selected dump has been force captured due to Dump Suppression Override list.\n4.Press PF3 to return to the Dump/Trace Analysis screen or press PF4 to return to the Primary Option menu.\nReview the Status of Forced/Captured Dumps\nYou can also review the status of dumps that were not suppressed on the Duplicate Suppression History panel.\nFollow these steps:\n1.Open the Dump/Trace Selection screen.\n2.Specify option I for any dump and press Enter.\nNOTE\nYou can specify the option for more than one dump.\n                CA SymDump for CICS DUMP/TRACE SELECTION         \n COMMAND ===>                                                                   \n                                                                                \n   Type S select,  D delete, H hold, R release, I history                       \n                                                                                \n     Dumpfile Applid   Tran Program  Offset Abend  Created         Dups Status  \n _ - PROTDMP  A11ICICX SYMD *TRACE*         SYMT 12/07/12 13:49:32              \n _ - |-       A11ICICX DE39 C390DEMO 001196 APCT 12/07/12 09:05:40    3         \n _ - |-       A11ICICX DE39 C390DEMO 001196 APCT 12/07/12 09:05:37    3", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b6364b001071-1", "text": "_ - |-       A11ICICX DE39 C390DEMO 001196 APCT 12/07/12 09:05:30    3         \n _ - |-       A11ICICX DE37 C370DEMO 0010EC APCT 12/07/12 09:05:27    3         \n _ - |-       A11ICICX DE37 C370DEMO 0010EC APCT 12/07/12 09:05:24    3         \n _ - |-       A11ICICX DE37 C370DEMO 0010EC APCT 12/07/12 09:05:21    3         \n _ - |-       A11ICICX DEMV CMVSDEMO 00118E APCT 12/07/12 09:05:10    3         \n _ - |-       A11ICICX DEMT ASMDEMO  0001BE ASRA 12/07/12 09:05:05    3         \n _ - |-       A11ICICX DEMT ASMDEMO  0001BE ASRA 12/07/12 09:05:00    3         \n _ - |-       A11ICICX DEMT ASMDEMO  0001BE ASRA 12/07/12 09:04:57    3         \n i - |-       A11ICICX DEMC COBDEMO  001294 ASRA 12/07/12 09:04:35    4         \n _ - |-       A11ICICX DEMC COBDEMO  001294 ASRA 12/07/12 09:04:27    4", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b6364b001071-2", "text": "_ - |-       A11ICICX DEMC COBDEMO  001294 ASRA 12/07/12 09:04:22    4         \n _ - |-       A11ICICX DEMC COBDEMO  001294 ASRA 12/07/12 09:04:18    4         \n                                                                                \n PF1 Help       2            3 End        4 Return     5 Collapse   6 Expand    \n PF7 Backward   8 Forward    9           10           11           12    \nThe Duplicate Suppression History panel opens.\nIn the following example, the selected dump has four entries in the list, because four duplicate dumps were captured\nfor this abend.\n             CA SymDump for CICS Duplicate Suppression History     \n COMMAND ===>                                                                   \n                                                                                \n 1263", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "809a718da2e0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n          Dumpfile   Tran  Program   Offset  Abend #Dups                        \n          PROTDMP    DEMC  COBDEMO   001294  ASRA    4                          \n                                                                                \n          APPLID   USER     TASK  TERM      CREATED      STATUS                 \n          A11ICICX CICSUSER 00053 U056 12/12/07 09:04:35 FORCE/CAPT             \n          A11ICICX CICSUSER 00052 U056 12/12/07 09:04:27 FORCE/CAPT             \n          A11ICICX CICSUSER 00051 U056 12/12/07 09:04:22 FORCE/CAPT             \n          A11ICICX CICSUSER 00050 U056 12/12/07 09:04:18 FORCE/CAPT             \n          *** End of data ***                                                   \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7 Backward   8 Forward    9           10           11           12         \n3.Review the status column.\nReview the status column. The Duplicate Suppression History panel in the previous example shows dumps that\nwere captured for all four occurrences of this abend. This is because the abend matches the criteria specified in the\nIN25CAPT Capture List. Only dumps captured and match the IN25CAPT Capture List are indicated by the status,\nForce/Capt.\n4.Press PF3 to return to the Dump/Trace Analysis screen or press PF4 to return to the Primary Option menu.\nSymbolic Listings", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "809a718da2e0-1", "text": "Symbolic Listings\nMultiple symbolic listings can exist for an abending program. It is important to use the symbolic listing that matches the\nprogram captured in the dump -- get the correct symbolic listing.\n\u2022For COBOL and PL/I programs that are link-edited immediately after the command-level stub, SymDump  for CICS\nautomatically  finds the matching symbolic listing, if one exists. SymDump  for CICS searches through all of your\nsymbolic files (defined in the IN25OPTS module) to find the program listing whose date and time match the date and\ntime of the load module for which the dump was generated.\n\u2022For Assembler programs, and for those COBOL and PL/I programs for which SymDump  for CICS cannot find a\nmatching listing, SymDump  for CICS displays the following Symbolic Version List.\n------------- CA SymDump for CICS  - Symbolic Version List ---------------\n COMMAND ===>\n Program = ASMDEMO        Load Module  Date/Time = 00/00/0000 00:00:00           \n    File ID    Date        Time    Language     Comments                        \n  _ PROTSYM  03/01/2000  11.12.59  ASM        LATEST VERSION                    \n  _ OLDSYM   11/12/1999  10.29.31  ASM                                          \n \n \n        S - Select which Symbolic file to use                                    \n-------------------------------------------------------------------------------\n  PFKEYS:  1 Help      2           3 No file   4           5           6         \n           7           8           9          10          11          12         \nThe Symbolic Version List lists all symbolic files containing listings for the program you are debugging.\n 1264", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "96300a2ed5ae-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nYou can select a list using the following procedure.\nFollow these steps:\n1.Type S to the left of the symbolic file containing the listing you want to use and press Enter. SymDump  for CICS\ndisplays the Display Selection menu using the listing you identified when you examined the program listing online.\n2.Press PF3, if none of the versions are correct. SymDump  for CICS displays the Display Selection menu and informs\nyou that symbolic information is not available for this program.\nNote: SymDump  for CICS displays the Symbolic Version List even if it finds only one symbolic listing. If you know the\nlisting does not match your program version, you can debug without symbolics.\nYou can also recompile or reassemble the program with the appropriate post-processor program to get an up-to-date\nsymbolic listing before examining the dump.\nView a Dump and Its Information\nWith SymDump  for CICS, information about a dump is available quickly and easily.\nView a Dump Online\nTo view a dump online, take the following steps:\n1.Locate the dump on the Dump/Trace Selection screen.\nNote: If the dump does not appear in the list, you may need to specify different selection criteria on the Dump/Trace\nAnalysis screen. For more information, see Specifying Selection Criteria.\n2.Type S to the left of the dump you want to view.\n3.Press Enter. The Display Selection menu displays for the dump you selected. A sample menu is shown next.\nNOTE\nOccasionally you may need to locate the correct symbolic listing for the dump you selected. If this is\nnecessary, see Symbolic Support for more information.\n----------------- CA SymDump for  CICS DISPLAY SELECTION -------------------\n COMMAND ===>                                                                 \n   Type + to expand or - to collapse display groups below,", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "96300a2ed5ae-1", "text": "COMMAND ===>                                                                 \n   Type + to expand or - to collapse display groups below,                     \n          or S to select a display.                                           \n   Prog: COBDEMO    Code: ASRA    Tran: DEMC   Appl: A01IC9NE   Date: 04/19/00 \n   User: CICSUSER   Task: 00042   Term: 2068   Node: A60L2068   Time: 16:19:36 \n     Display                Description                                        \n _ - Formatted Displays     Analysis, source, abend help, last screen...      \n _   |-Analysis             Analysis of abending instruction and operands      \n _   |-Source               Source code at the point of the abend              \n _   |-Abend help           Abend code description and probable cause\n _   |-Last screen          Last 3270 screen image sent to the terminal        \n _   |-Program call trace   Display program call sequence and registers        \n _   |-Trace                Complete or filtered CICS trace table entries      \n _   |-Register contents    Program register contents selection display      \n _   |-Programs referenced  List of programs referenced by the transaction     \n   * |-Files accessed       List of files referenced by the transaction        \n _   |-Transaction          Transaction definition attributes display          \n                                                                              \n PF1 Help       2            3 End        4 Return     5 Collapse   6 Expand   \n PF7 Backward   8 Forward    9           10           11           12       \n4.Type S to the left of the display name that you want to see on the Display Selection menu, as shown in the following\nsample screen.\n 1265", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "27d308023639-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nEntering an S next to a display category name has no effect. In the following example, Formatted Displays is\na display category name.\n----------------- CA SymDump for CICS DISPLAY SELECTION -------------------\n COMMAND ===>                                                                  \n \n   Type + to expand or - to collapse display groups below,                     \n \n          or S to select a display.                                           \n   Prog: COBDEMO    Code: ASRA    Tran: DEMC   Appl: A01IC9NE   Date: 04/19/96 \n   User: CICSUSER   Task: 00042   Term: 2068   Node: A60L2068   Time: 16:19:36 \n                                                                      More:   +\n     Display                Description                                        \n _ - Formatted Displays     Analysis, source, abend help, last screen...      \n _  |-Analysis              Analysis of abending instruction and operands      \n s  |-Source                Source code at the point of the abend              \n _  |-Abend help            Abend code description and probable cause          \n .\n .\n .\n5.Press Enter. The screen that appears depends on the item you selected on the menu.\nView Multiple Dumps\nIf you selected more than one dump for viewing on the Dump/Trace Selection screen, SymDump  for CICS displays each\ndump, beginning with the most recent one.\nTo see all of the dumps you selected, follow these steps:\n1.Press PF3 from the Display Selection menu after you view all of the areas you want to see for the first dump.\nSymDump  for CICS redisplays the Display Selection menu with information for the second dump you specified on the\nDump/Trace Selection screen.\n2.Analyze the second dump.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "27d308023639-1", "text": "Dump/Trace Selection screen.\n2.Analyze the second dump.\nRepeat these steps to view the rest of the dumps you selected on the Dump/Trace Selection screen.\nDisplay Selection Menu\nThe Display Selection menu contains information about the dump you selected from the Dump/Trace Selection screen.\nThe following is a sample Display Selection Menu.\n----------------- CA SymDump for CICS DISPLAY SELECTION-------------------\n        COMMAND ===> [A]                                                               \n   Type + to expand or - to collapse display groups below,                     \n          or S to select a display.                                           \n        [B] Prog: COBDEMO    Code: ASRA    Tran: DEMC   Appl: A01IC9NE   Date: 04/19/00 \n   User: CICSUSER   Task: 00042   Term: 2068   Node: A60L2068   Time: 16:19:36 \n                                                                      More:   +\n        [C]  Display                Description                                        \n _ - Formatted Displays     Analysis, source, abend help, last screen...      \n _   |-Analysis             Analysis of abending instruction and operands      \n _   |-Source               Source code at the point of the abend              \n _   |-Abend help           Abend code description and probable cause\n _   |-Last screen          Last 3270 screen image sent to the terminal        \n 1266", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "94d92d1211e5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n _   |-Program call trace   Display program call sequence and registers        \n _   |-Trace                Complete or filtered CICS trace table entries      \n _   |-Register contents    Program register contents selection display\n _   |-Programs referenced  List of programs referenced by the transaction     \n   * |-Files accessed       List of files referenced by the transaction        \n _   |-Transaction          Transaction definition attributes display          \n        [D]                                                                             \n PF1 Help       2            3 End        4 Return     5 Collapse   6 Expand   \n PF7 Backward   8 Forward    9           10           11           12          \nThe Display Selection menu is divided into four basic sections:\n[A]\nA command line supporting the commands assigned to PF keys.\n[B]\nAn informational section containing details about the dump, from program name and abend code to the user ID,\napplid, terminal, and task. Field definitions are provided in online help (PF1).\n[C]\nA display tree from which you can access detailed informational displays that provides data about the dump and\nthe error. The detailed informational displays are grouped into the following categories: Formatted Displays, Task\nAreas, Database Areas, Language Areas, and CICS System Areas.\nNOTE\nAn asterisk (*) next to an item or a group name means that the particular display or group of displays is\nunavailable for the program. For instance, if the abended program does not reference any files, the Files\nAccessed display in the Formatted Displays group shows an asterisk to indicate its unavailability\n[D]\nA section showing the PF key assignments for this screen.\nDisplay Tree\nThe display tree in the Display Selection menu is an intuitive way to access all of the information you need to debug your", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "94d92d1211e5-1", "text": "problem. The display tree is a hierarchical list of available displays. The displays are arranged in the following categories:\nFormatted Displays\nIntelligently formatted displays of the dump contents. Displays include analysis, source, abend help, program call\ntrace, registers, last CICS screen, files accessed, and programs, transactions, and terminals referenced.\nTask Areas\nCORE displays for areas like the Commarea, the EXEC Interface Block, and the Transaction Work Area.\nNote: When using the integrated CICS translator of Enterprise COBOL for z/OS, the CORE=EIB command will\nnot work unless the NOLINKAGE translator option or the ADATA compiler option is specified.\nLanguage Areas\nCORE displays for areas like COBOL working storage and COBOL BLL cells.\nDatabase Areas\nCORE displays for DB2 and DL/I.\nCICS System Areas\nCORE displays for areas like the Common System Area and the Common Work Area.\n 1267", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "25c6e5217af4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nEach category contains a set of screens for displaying different types of information. The following is a list of the screens\nin each category. Each category and the screens it contains are explained later in these topics.\nFormatted Displays Task Areas Database Areas Language Areas CICS System Areas\nAbend analysis Commarea CLOT BLLs CSA\nSource listing dump\nanalysisEIB N/A BLXs CWA\nAbend help Segmented storage RDIIN CWK OPFL\nLast screen TWA SQLCA TGT TCT\nProgram call trace TUAR SQLRCODE EISTG N/A\nFormatted trace table STCA LASTSQL DSA N/A\nRegister contents TCA N/A N/A N/A\nPrograms referenced TACB DLP N/A N/A\nFiles accessed TCTTE N/a N/A N/A\nTransaction summary TIOA CTA N/A N/A\nTerminal summary User storage DGB N/A N/A\nTask-Bridge-CBTS Program ISB N/A N/A\nN/A EIS PCBL N/A N/A\nN/A CURR (abending\ninstructionPST N/A N/A\nN/A RIE RSB N/A N/A\nN/A TIE SCD N/A N/A\nN/A N/A UIB N/A N/A\nScroll Through the Tree\nWhen the Display Selection menu initially appears, the Formatted Displays group is expanded while the other groups are\ncollapsed. You must scroll down (PF8) to see the collapsed groups.\nWhen expanded, the items beneath the group in the hierarchy are displayed. A group is expanded when there is a minus\nsign (-) to the left of the group name and a tree structure is displayed below the group.\nIf categories are expanded, there may be more information that can be displayed on one screen. If the word More appears", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "25c6e5217af4-1", "text": "in the upper-right corner of the display tree, there is more information than is shown. A plus sign next to the word More\nindicates that scrolling forward (PF8) shows additional items. A minus sign indicates that scrolling backward (PF7) shows\nadditional items. If there is more information in both directions, both a plus and minus sign display. If there is no additional\ninformation in either direction, the word More does not appear.\nWhen collapsed , the items beneath the group in the hierarchy are hidden. A group is collapsed when there is a plus sign\n(+) to the left of the group name.\nFor more information about expanding and collapsing tree items, see Collapse and Expand Branches.\nAll Display Selection menu items listed in uppercase (such as EIB, TACB, and CSA) identify CORE keywords. When you\nare viewing an InterTest for CICS Main Storage display for one area, you can bypass the SymDump  for CICS menus and\nswitch to another area using the following command syntax:\nCORE=keyword\nOvertype the keyword in the CORE=keyword command on the bottom of the InterTest for CICS Main Storage Display and\npress Enter. For more information about using CORE commands, see Accessing Main Storage CORE.\n 1268", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "de900ff70f4d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nYou must have InterTest for CICS installed to use this feature.\nFormatted Displays Category\nThe Formatted Displays category contains different formatted displays that you can access from the Display Selection\nmenu. These displays include the following:\n\u2022Abend Analysis\n\u2022Source Listing Dump Analysis\n\u2022Abend Help\n\u2022Last Screen Image\n\u2022Program Call Trace\n\u2022Formatted Trace Table\n\u2022Register Contents\n\u2022Referenced Programs\n\u2022Files Accessed (by Abending Transaction)\n\u2022Transaction summary\n\u2022Terminal summary\nAbend Analysis Screen\nThe Abend Analysis Screen provides additional information about the abending instruction and its operands.\nFollow these steps:\n1.Select Analysis  under the Formatted Display category on the Display Selection menu. The Abend Analysis screen\nappears.\n--------------  CA SymDump for CICS   ABEND ANALYSIS  -----------------------\n COMMAND ===>                                                                  \n   Type S to display main storage at the data location address.               \n            [A] Prog: COB2DEMO   Code: ASRA    Tran: DEC2   Appl: A01IC9NE   Date: 07/22/2006\n   User: CICSUSER   Task: 00225   Term: 2068   Node: A60L2068   Time: 12:48:40 \n                                                                      More:   + [B] Data Type            \n Location   Value                                      \n   Abended by                       Operating system                           \n   Abend type                       Program check, data exception (0C7)        \n   Abend in CSECT                   COB2DEMO + 00001140                        \n   AMODE, EXECKEY                   31, USER                                   \n   PSW at time of abend             079D0000 000DD78C 00060007 05ED3000", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "de900ff70f4d-1", "text": "_ Abending instruction  069F0188   FA20A2C895E1                               [C]                        \n    AP    X'2C8'(3,R10),X'5E1'(1,R9)                 \n                                    Add decimal instruction                    \n _ Operand 1 storage     069CA5D8   000000                                     \n                                    Invalid packed decimal data                [D] BLW=0000 Offset=02C8   \n                    \n _ Operand 2 storage     069EF6E5   1C                                         \n PF1 Help       2 Refresh    3 End        4 Return     5            6          \n PF7 Backward   8 Forward    9           10           11           12       \nThe Abend Analysis screen is divided into the following major sections:\n[A]\nIdentifies the dump you selected.\n 1269", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9ab8285e0104-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n[B]\nIndicates whether the program was abended by CICS, an application or the operating system, the abend type,\nand the addressing mode, execution key, and program status word (PSW) values at the time of the abend.\n[C]\nProvides details of the instruction and operands in the abending statement. Type an S next to the data type and\npress Enter to view that item in CORE. For more information, see Accessing Main Storage CORE.\n[D]\nFor COBOL/II and IBM COBOL programs, gives Base Locator (BL) cell references to the operand. The following\ninformation identifies the BL cell references by type.\nBL \u2014 Type Locator For\nBLA \u2014 Alphanumeric temporaries\nBLF \u2014 File entries\nBLK \u2014 Local storage\nBLL \u2014 Linkage Section\nBLO \u2014 Object class data\nBLV \u2014 Variably located data\nBLW \u2014 Working Storage\nBLX \u2014 External data name\nIXD \u2014 DSA index values\nIXT \u2014 TGT index values\nPress PF3 to return to the Display Selection menu.\nSource Listing Dump Analysis Screen\nThe Source Listing Dump Analysis screen allows you to view the abending statement in the context of the source code.\nTo display the Source Listing Dump Analysis screen\n1.Select Source  under the Formatted Display category on the Display Selection menu. The following sample screen\nshows that the ASRA abend that resulted from an improperly initialized field, TASKNUM.\n     CA InterTest for CICS - PROTSYM FILE SOURCE LISTING DUMP ANALYSIS         \nCOMMAND ===>                                                       \nProgram= COBDEMO  Option #       Stmt #        Displacement=        Margin= 01 \n                                        Search=                                \n-------------------------------------------------------------------------------\n _ 00895 CONTINUE-TASK.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9ab8285e0104-1", "text": "Search=                                \n-------------------------------------------------------------------------------\n _ 00895 CONTINUE-TASK.                                                       \n   00896**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED                          \n A   ==>     ADD +1 TO TASKNUM.                                               \n     ==>                                                                       \n     ==> CODE: ASRA                                                            \n     ==>                                                                       \n     ==>      Press PF1 for a detailed description.                           \n     ==>                                                                       \n _ 00898     IF TASKNUM = 1                                                    \n _ 00899         MOVE 'DMAPASR'  TO MAPNAME.                                  \n _ 00900     IF TASKNUM = 2                                                    \n _ 00901         MOVE 'DMAPSUM'  TO MAPNAME.                                  \n _ 00902     IF TASKNUM GREATER 2                                              \n _ 00903         GO TO SEND-END-MSG.                                          \n _ 00904     GO TO REWRITE-TSQ.                                               \n _ 00905 REWRITE-TSQ.                                                         \n   00906*EXEC CICS WRITEQ TS                                                   \n   00907*          REWRITE               \n 1270", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a04151519f6b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n2.From the Source Listing Dump Analysis screen you can:\n\u2013Press PF1 for more information about the cause of the abend.\n\u2013Scroll through the source listing and compiler output using PF7  or PF8.\n\u2013Display the value of data fields, using the line command d and moving the cursor under the data item.\n\u2013Press PF3 to return to the Display Selection menu.\n\u2013Enter one of the following commands on the command line:\nCommand \u2014  Description\nHELP \u2014 Invoke the Help facility\nEND \u2014 Return to the previous display/menu screen\nPROFILE \u2014 Display the source listing Profile screen\nBWD \u2014 Scroll backward\nFWD \u2014 Scroll forward\nCORE \u2014 Display CORE menu\nRESETBKP\u2014  Reposition breakpointed task at the breakpoint\nBTRACE \u2014 Invoke the backtrace facility\nIf you have InterTest for CICS, you can also enter the following commands. These commands are valid only when\nInterTest for CICS is also installed at your site and the global installation option is defined as SYMDINT=YES. To check its\nvalue, use ITST Option 7.1.2 from InterTest for CICS.\nCommand Description\nMONITOR \u2014 Set monitoring for the listed program\nMENU \u2014 Display the InterTest for CICS Primary Option menu\nCNTL \u2014 Display CNTL Command menu\n=x.y.z \u2014 Fast path to InterTest for CICS Primary Option menu X.Y.Z\nFILE \u2014 Invoke the InterTest for CICS FILE facility\nITST \u2014 Display the InterTest for CICS Primary Option menu\nSTATUS \u2014 Display the status of the listed program\nSTATUS ALL \u2014 Display the status of all monitored programs\nAbend Help Screen\nThe Abend Help screen displays help for a specific abend code. In most cases, the help screen gives a probable cause\nand recommends what you can do to handle the error.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a04151519f6b-1", "text": "and recommends what you can do to handle the error.\nTo invoke the online help facility, select Abend Help  under the Formatted Display category on the Display Selection\nmenu.\nThe following is a sample Abend Help Display for an ASRA abend.\n    CA InterTest for CICS- INTERACTIVE HELP FACILITY -\nTUTORIAL: Automatic Breakpoint:  Error code 37.\n \n Error code 37:  ASRA (0C7)  - Data exception.\n \n A data exception is recognized when either the sign or digit codes of operands\n in the decimal machine instruction are invalid.\n \n WHAT YOU CAN DO:   Use CORE to display the fields in question and then modify\n them with the CORE facility. Then use the resume task facilities to re-execute\n the instruction.\n \n The usual cause is that a data field had not been initialized to a valid\n packed decimal (COBOL: COMP-3) value, or the value was not properly edited\n before the move into the field. This kind of error is also likely to happen if\n 1271", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "246ce929f26b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n the same main storage location is defined as two or more fields, and not all\n of these are specified for packed-decimal (COMP-3) arithmetic.\n                                                                          (end)\n ------------------------------------------------------------------------------\n ENTER N FOR NEXT PAGE, P FOR PRECEDING PAGE, F FOR FIRST PAGE, OR -\n M FOR RETURN TO PREVIOUS MENU,  CLEAR TO EXIT, OR MESSAGE NUMBER. ==> M \nNOTE\nThe prompts on the bottom of the Help screen refer to navigating within the Help facility. For example, entering\nM returns you to the previous Help menu, not the previous SymDump  for CICS menu.\nPress Clear  or PF3 to exit the Help facility and return to the previous SymDump  for CICS menu.\nNOTE\nA local systems administrator can create and maintain help file entries for user-defined abend codes. These\nuser-provided help entries take precedence over system-provided help entries. The search hierarchy used for an\nAbend Help Display is as follows:\n1.User-provided help for the abend code and program name.\n2.User-provided help for the abend code.\n3.System-provided help for the abend code.\n4.If none of the above, a message indicates help is not available.\nLast Screen Image\nTo display the last 3270 screen image sent to the terminal by the abended application, follow these steps:\n1.Select Last Screen under the Formatted Display category on the Display Selection menu. The following screen is the\nlast screen sent by the program COBDEMO before it abended.\n ******************************************************************************\n *****                     Welcome to the CA                              *****\n *****                 CA InterTest Demo Session                          *****\n *****                                                                    *****\n *****              Before proceeding, please have on hand the            *****\n *****              guide which accompanies the Demo Session.             *****\n *****                                                                    *****", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "246ce929f26b-1", "text": "*****              guide which accompanies the Demo Session.             *****\n *****                                                                    *****\n *****     Please make sure that the program COBDEMO is monitored by      *****\n *****      CA InterTest. This program will abend if it is not monitored  *****\n *****                                                                    *****\n *****     To turn the monitor on, press CLEAR and follow the steps       *****\n *****     outlined in the documentation.                                 *****\n *****                                                                    *****\n *****     If the monitor is already on, press ENTER to begin the         *****\n *****     Basic Demo Session or PF2 to go to the Options Menu.           *****\n ******************************************************************************\n2.Press PF3 to return to the Display Selection menu.\nProgram Call Trace\nThe Call Trace tells you how the transaction got to where the abend occurred. This is especially useful when\ntroubleshooting an abend for a long-running transaction or a composite module. This screen contains a complete program\ncall history of the transaction that abended.\nTo display the Program Call Trace Summary, Select Program Call Trace under the Formatted Display category on the\nDisplay Selection menu.\n 1272", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1cb3bb41ada6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe summary provides the following information for each call:\nCaller details\nThe program making the call. Details include the program name, CSECT of the call, return offset, and caller-\nprogram language.\nCall type\nIndicates the type of call. Types include a CICS link, a static call, a dynamic call, last command executed, or\nunknown.\nCalled details\nThe program being called. Details include the program name, CSECT, and offset.\nThe Call Trace Summary lists calls in chronological order:\n\u2022The top entry lists the first program in the call chain\n\u2022The bottom entry is the current program\nA sample Program Call Trace Summary follows. Detailed field definitions are available from online help (PF1).\n             CA SymDump for CICS  PROGRAM CALL TRACE SUMMARY      A11CIQA5 \n COMMAND ===>                                                                   \n                                                                                \n   Type S for program source I for program details  R for registers at call     \n        C for Channel/Container display                                         \n   Prog: COB2DEML   Code: ASRA    Tran: DEC2   Appl: A11CIQA5   Date: 06/16/11  \n   User: CICSUSER   Task: 00120   Term: U005   Node: A55TU005   Time: 13:10:06  \n                                                                                \n   ------- Caller (FIFO sequence) -------                                       \n   Program   Csect     Return  Language    Call Type                            \n _ COB2DEMO  COB2DEMO  002AA8  COBOL       Linked to                            \n _ COB2DEML  COB2DEML  0002B4  COBOL       Stat call                            \n _ COB2DEML  ACO2IN25  0000E2  COBOL       CURR PGM", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1cb3bb41ada6-1", "text": "*** End of data ***                                                          \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n                                                                                \n PF1 Help       2            3 End        4 Return     5            6           \n PF7 Backward   8 Forward    9           10           11           12      \nRead the Program Call Trace\nThe previous example shows the call trace for an ASRA abend in the program COBDEML. Reading this trace from the\nbottom up gives us the call history of DEC2 leading up to the ASRA abend:\n\u2022The first line indicates CICS passed control to the COBOL program COB2DEMO for transaction DEC2. The first call\nwas an EXEC CICS LINK to COB2DEML at the beginning of CSECT COB2DEML (offset 00000). The call return offset\nis 002BEC in COB2DEMO.\n\u2022The middle line indicates COB2DEML, also a COBOL program, executed a static call to a subroutine (ACO2IN25). The\ncall return offset is 0002B4 in COB2DEML.\n 1273", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7ed062a2b58d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nView Source and Data at Each Stage of the CALL\nTo view source and data at each stage of the CALL, follow these steps:\n1.Type an S to the left of a Caller Program entry from the Program Call Trace Summary display to view the caller\nprogram's source codes at the time of the call.\nIf the source for the given program is available, a source listing appears. While in the source listing, display variables\nfor the program may be displayed.\nIf the source is not available, registers at the time of the call are displayed instead of source code.\n2.Type an I to the left of a Caller Program entry to display details about the program such as the load library from which\nit came.\n3.Type a C to the left of the Caller Program entry to display Channel and Container data for this program. (This option is\nvalid only on CICS systems which support Channels and Containers).\nThe following is a sample Channel/Container Storage screen:\n------------  CA SymDump for CICS    CHANNEL/CONTAINER STORAGE  -------------\n COMMAND ===>\n   Type S to display main storage.\n   Prog: TESTCB59   Code: DUMT    Tran: CB59   Appl: A31IC9NP   Date: 04/25/2006\n   User: CICSUSER   Task: 00064   Term: U017   Node: ________   Time: 15:17:25\n   Channel          Container     Curr CPGID Length    Character Data\n _ LNK0CHAN-00      LNK3CONT-01      x 00037 0000106 * 3 1ST LINK03 PUT 00064 *\n _ LNK0CHAN-00      LNK2CONT-01      x 00037 0000106 * 2 1ST LINK02 PUT 00064 *", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7ed062a2b58d-1", "text": "_ LNK0CHAN-00      LNK1CONT-01      x 00037 0000106 * 1 1ST LINK01 PUT 00064 *\n _ LNK0CHAN-00      LNK0CONT-00      x 00037 0000106 * 2 1ST LINK02 RWR 00064 *\n   *** End of data ***\n \n \n \n PF1 Help       2            3 End        4 Return     5            6\n PF7 Backward   8 Forward    9           10           11           12PFKEYS\n4.Type an S next to the channel you want to display. The MAIN STORAGE UTILITY screen appears.\n       CA InterTest for CICS - MAIN STORAGE UTILITY - Termid = U017\nOffset                                                            Address  Task\n+   0  F340F1E2 E340D3C9 D5D2F0F3 40D7E4E3  * 3 1ST LINK03 PUT * 239F6748    64\n+  10  40F0F0F0 F6F4C3D6 D4D7E4E3 C5D940C1  *  00064COMPUTER A * 239F6758\n+  20  E2E2D6C3 C9C1E3C5 E26B40C9 D5C34040  * SSOCIATES, INC   * 239F6768  Page\n+  30  40404040 40404040 40404040 40404040  *                  * 239F6778  +000\n+  40  40404040 40404040 40404040 40404040  *                  * 239F6788", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7ed062a2b58d-2", "text": "+  50  40404040 40404040 40404040 40404040  *                  * 239F6798\n+  60  40404040 4040C8C1 D9E3C6C9 C5D3C440  *       HARTFIELD  * 239F67A8\n+  70  C5E7C5C3 E4E3C9E5 C540D7C1 D9D24040  * EXECUTIVE PARK   * 239F67B8\n+  80  40404040 40404040 40404040 40404040  *                  * 239F67C8\n+  90  40404040 40404040 40404040 40404040  *                  * 239F67D8\n+  A0  40404040 40404040 40404040 40404040  *                  * 239F67E8\n+  B0  40404040 4040C5C1 E2E340E6 C9D5C4E2  *       EAST WINDS * 239F67F8\n+  C0  D6D96B40 C3E34B40 F0F6F0F8 F8404040  * OR, CT. 06088    * 239F6808\n+  D0  40404040 40404040 40404040 40404040  *                  * 239F6818\n+  E0  40404040 40404040 40404040 40404040  *                  * 239F6828", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7ed062a2b58d-3", "text": "+  F0  40404040 40404040 40404040 40404040  *                  * 239F6838\n+ 100  40404040 4040                        *                  * 239F6848\n ------------------------------------------------------------------------------\n PF1 Help       2            3 End        4 Return     5            6 Dump\n PF7 Backward   8 Forward    9 Caps Off  10           11           12 Structure\n 1274", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "490e9e093ec8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n CORE=239F6748\n CASD6509 Abended task CSCB storage (END OF BLOCK)\nView Inactive Programs\nYou can view inactive programs in the Program Call Trace Summary screen.\nFollow these steps:\n1.Select an active program.\nThe program listing for the active program is displayed.\n2.Issue the CORE=CWK***** command, where ***** is the inactive program name, and press Enter.\nThe working storage for the inactive program is displayed.\nThe following are the PFKEYS PF key assignments for this screen:\nPF7 and PF8\nScrolls through the working storage variables\nPF12\nToggles between hexadecimal format and characters\nFormatted Trace Table\nThe Formatted Trace Table screen enables you to view complete or filtered CICS trace table entries for the dump. You\ncan display trace entries in Abbreviated (default), Short, or Full mode. The presentation of the trace is identical for traces\nthat are within a transaction dump, or those captured using the SYMT trace capture facility.\nThe trace display starts with the first line of the captured trace. You are able to quickly navigate to where you want to in\nthe trace by using the filter and command line features.\nTo display the Formatted Trace Table, select Trace under the Formatted Display category on the Display Selection menu.\nThe trace entries are formatted using DFHTUXX0, for the corresponding release of CICS. For help in interpreting the trace\nentries, see the appropriate IBM documentation.\nNOTE\nA pre-requisite for formatting the CICS trace table is that a Trace Formatting region needs to be active and\nconnected you your CICS region from which you are viewing the dump.  For more information see Activate Your\nProduct.\nThe following sample screen shows the SymDump  for CICS Trace, in Abbreviated Mode:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "490e9e093ec8-1", "text": "The following sample screen shows the SymDump  for CICS Trace, in Abbreviated Mode:\n--------------  CA SymDump for CICS    FORMATTED TRACE TABLE  -------------- \nCOMMAND ===>                                             MODE: A SCROLL: PAGE                         \n000047 00031 QR    PG 0901 PGPG  ENTRY INITIAL_LINK          ASMDEMO \n000048 00031 QR    LD 0001 LDLD  ENTRY ACQUIRE_PROGRAM       200E0AF8  \n000049 00031 QR    LD 0002 LDLD  EXIT  ACQUIRE_PROGRAM/OK  A0D11230,20D11230,2C88,0,REUSABLE,ESDSA,OLD_COPY  \n             \n000050 00031 QR    AP 1940 APLI  ENTRY START_PROGRAM         ASMDEMO,CEDF,FULLAPI,EXEC,NO,200431C0,00000000 ,\n 00000000,1,NO\n000051 00031 QR    SM 0C01 SMMG  ENTRY GETMAIN               367,YES,00,TASK                                 \n             \n000052 00031 QR    SM 0C02 SMMG  EXIT  GETMAIN/OK            00140478  \n000053 00031 QR    AP 00E1 EIP   ENTRY HANDLE-CONDITION                                \n 0004,00140488 ...h,08000204 ....  \n000054 00031 QR    PG 0700 PGHM  ENTRY SET_CONDITIONS       \n 20D13BCD,20D13BCA,001404F4,00140488,ASSEMBLER,80,AMODE31     \n000055 00031 QR    PG 0701 PGHM  EXIT  SET_CONDITIONS/OK     0       \n 1275", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c9888df1da95-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n000056 00031 QR    AP 00E1 EIP   EXIT  HANDLE-CONDITION      OK                         \n 00F4,00000000 ....,00000204 .... \n000057 00031 QR    AP 00E1 EIP   ENTRY READQ-TS                                         \n 0004,00140488 ...h,08000A04 .... \n000058 00031 QR    TS 0C01 TSMB  ENTRY MATCH                 DEMAU052 \n000059 00031 QR    TS 0C02 TSMB  EXIT  MATCH/OK              ,,,DEMAU052,,00000000,,ANY,NO,NO                \n             \n000060 00031 QR    TS 0201 TSQR  ENTRY READ_INTO             DEMAU052,00140610 , 00000000 , 00000024,1,EXEC  \n             \n000061 00031 QR    TS 0202 TSQR  EXIT  READ_INTO/OK          00140610 , 00000024 , 00000024,1,NO             \n             \n000062 00031 QR    AP 00E1 EIP   EXIT  READQ-TS              OK                         \n 00F4,00000000 ....,00000A04 .... \n000063 00031 QR    AP 1942 APLI  *EXC* Program-Check        \n START_PROGRAM,ASMDEMO,CEDF,FULLAPI,EXEC,NO,200431C0,00000000 , 000000\n000064 00031 QR    AP 0790 SRP   *EXC* PROGRAM_CHECK                                                         \n             \n000065 00031 QR    DS 0010 DSBR  ENTRY INQUIRE_TASK", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c9888df1da95-1", "text": "000066 00031 QR    DS 0011 DSBR  EXIT  INQUIRE_TASK/OK       ESSENTIAL_YES                                   \n             \n000067 00031 QR    DS 0002 DSAT  ENTRY CHANGE_MODE           QR                                              \n             \n                                                                                                             \n             \nPF1 Help       2            3 End         4 Mask      5 Repeat     6 Return On                               \n             \nPF7 Backward   8 Forward    9 All Trace  10 Left     11 Right     12 Retrieve   \nPFKEYS PF key assignments for the trace display follow.\n* PF1/PF13\nInvoke SymDump  for CICS HELP facility for this function\n* PF2/PF14\nNo function.\n* PF3/PF15\nEnd the Formatted Trace Display. Of special note here, is that when selecting a trace from within a transaction\ndump, that all trace filters, highlights, and overrides will remain in effect until the dump selection is left completely.\nMerely leaving the trace selection does not reset these values. For traces captured using the SYMT trace capture\nfacility, all filters, highlights, and overrides are reset when the trace is left.\n* PF4/PF16\nDisplay the current Filter Selection Mask.\n* PF5/PF17\nRepeat Find Command.\n* PF6/PF18\nToggle to turn Return Entry display off or on.\n* PF7/PF19\nPage back by scroll amount.\n* PF8/PF20\nPage forward by scroll amount.\n 1276", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d438bab1a857-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n* PF9/PF21\nToggle to turn filtering on/off.\n* PF10/PF22\nScroll left by scroll amount.\n* PF11/PF23\nScroll right by scroll amount.\n* PF12/PF24\nRetrieve previously entered commands.\nCommand Line: (Top of screen)\nM or MODE A\nDisplay trace in abbreviated mode.\nS\nDisplay trace in short mode if available.\nF\nDisplay trace in full mode.\nO\nDisplay only trace entries that have line overrides.\nH\nDisplay only trace entries that are highlighted.\nF or FIND string\nFind the next occurrence of a string in the trace (string may be in single or double quotes).\nFirst\nFinds the first occurrence of the string.\nNext\nFinds the next occurrence.\nCommand Line: (Top of screen continued)\nLast\nFinds the last occurrence.\nPrev\nFinds the previous occurrence.\nF or FIND HILITE\nFind the next occurrence of a highlighted entry (sub operands first, next, and so on, same as normal find).\nH or HIGHLIGHT string\nHighlight all occurrences of a string.\nTOP\nPositions trace display to beginning of displayed entries.\nBOT\nPositions trace display to the end of the displayed entries.\nL number\nPositions trace to a specific line number.\nR or Reset O\nReset all line overrides.\n 1277", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5ffcf47b2a59-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nR or Reset H\nReset all highlighted entries to normal intensity.\nN (number)\nWith PF7, PF8, PF10, PF11 scrolling by the specified number of lines.\nLine Entry Commands: (Left side of screen)\nA\nEntry always displays as abbreviated.\nS\nEntry always displays as short if available.\nF\nEntry always displays as full.\nH\nEntry always displays as highlighted.\nRH\nHighlight status of entry is reset to normal intensity.\nRO\nMode override is reset to default mode.\nMode Setting: (Top of screen on right)\nA\nDisplay entire trace in Abbreviated Mode.\nS\nDisplay entire trace in Short Mode (if available).\nF\nDisplay entire trace in Full Mode.\nH\nDisplay only entries that are set to Highlight status.\nO\nDisplay only entries that are set to Override status.\nScroll Setting: (Top of screen on right)\nP or Page\nScrolling is one page at a time.\nAny valid numeric\nScrolling is for the specified number.\nFilter Selection\nFilter Selection provides the SymDump  for CICS Formatted Trace Facility user with the ability to quickly display only\nselected entries within a trace, making an overwhelming array of entries manageable. Use the following PF keys to control\nthe display:\n\u2022PF4 from the Trace display displays the mask display, and allows you to modify the mask to suit your specific needs.\nTrace entries that match your filter criteria are displayed for your review, all others are hidden! When displaying the\nFilter Selection Mask using PF4, you are still within the Trace display you were in when you pressed PF4.\n\u2022PF3 or PF9 returns to where you were. If Filter Selection is in effect the new Filter values are used.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5ffcf47b2a59-1", "text": "The following sample screen shows the SymDump  for CICS Trace, in Abbreviated Mode:\n 1278", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a7cc0501f681-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n--------------  CA SymDump for CICS    FORMATTED TRACE TABLE  --------------                                 \n                   \nCOMMAND ===>                                             MODE: A SCROLL: PAGE                                \n                     \n000047 00031 QR    PG 0901 PGPG  ENTRY INITIAL_LINK          ASMDEMO                                         \n                     \n000048 00031 QR    LD 0001 LDLD  ENTRY ACQUIRE_PROGRAM       200E0AF8                                        \n                     \n000049 00031 QR    LD 0002 LDLD  EXIT  ACQUIRE_PROGRAM/OK    A0D11230,20D11230,2C88,0,REUSABLE,ESDSA,OLD_COPY\n                     \n000050 00031 QR    AP 1940 APLI  ENTRY START_PROGRAM         ASMDEMO,CEDF,FULLAPI,EXEC,NO,200431C0,00000000 ,\n 00000000,1,NO       \n000051 00031 QR    SM 0C01 SMMG  ENTRY GETMAIN               367,YES,00,TASK                                 \n                     \n000052 00031 QR    SM 0C02 SMMG  EXIT  GETMAIN/OK            00140478                                        \n                     \n000053 00031 QR    AP 00E1 EIP   ENTRY HANDLE-CONDITION                                 \n 0004,00140488 ...h,08000204 ....         \n000054 00031 QR    PG 0700 PGHM  ENTRY SET_CONDITIONS       \n 20D13BCD,20D13BCA,001404F4,00140488,ASSEMBLER,80,AMODE31             \n000055 00031 QR    PG 0701 PGHM  EXIT  SET_CONDITIONS/OK     0", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a7cc0501f681-1", "text": "000056 00031 QR    AP 00E1 EIP   EXIT  HANDLE-CONDITION      OK                         \n 00F4,00000000 ....,00000204 ....         \n000057 00031 QR    AP 00E1 EIP   ENTRY READQ-TS                                         \n 0004,00140488 ...h,08000A04 ....         \n000058 00031 QR    TS 0C01 TSMB  ENTRY MATCH                 DEMAU052                                        \n                     \n000059 00031 QR    TS 0C02 TSMB  EXIT  MATCH/OK              ,,,DEMAU052,,00000000,,ANY,NO,NO                \n                     \n000060 00031 QR    TS 0201 TSQR  ENTRY READ_INTO             DEMAU052,00140610 , 00000000 , 00000024,1,EXEC  \n                     \n000061 00031 QR    TS 0202 TSQR  EXIT  READ_INTO/OK          00140610 , 00000024 , 00000024,1,NO             \n                     \n000062 00031 QR    AP 00E1 EIP   EXIT  READQ-TS              OK                         \n 00F4,00000000 ....,00000A04 ....         \n000063 00031 QR    AP 1942 APLI  *EXC* Program-Check        \n START_PROGRAM,ASMDEMO,CEDF,FULLAPI,EXEC,NO,200431C0,00000000 , 000000\n000064 00031 QR    AP 0790 SRP   *EXC* PROGRAM_CHECK                                                         \n                     \n000065 00031 QR    DS 0010 DSBR  ENTRY INQUIRE_TASK", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a7cc0501f681-2", "text": "000066 00031 QR    DS 0011 DSBR  EXIT  INQUIRE_TASK/OK       ESSENTIAL_YES                                   \n                     \n000067 00031 QR    DS 0002 DSAT  ENTRY CHANGE_MODE           QR                                              \n                     \n                                                                                                             \n                     \nPF1 Help       2            3 End         4 Mask      5 Repeat     6 Return On                               \n                     \nPF7 Backward   8 Forward    9 All Trace  10 Left     11 Right     12 Retrieve  \n 1279", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e5f183d4533d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWARNING\nIf you enter a space on the first character of the task number, the filter entry is ignored. This allows you to quickly\ndeactivate and activate entries.\nYou can repeat any given filter entry by entering R(n) in column 1 of any given filter entry. Multiple filter entries are\ncumulative.\nPFKEYS PF key assignments for the MASK display follow.\n* PF1/PF13\nInvoke SymDump  for CICS HELP facility for this function.\n* PF2/PF14\nNo function.\n* PF3/PF15\nExit mask display.\n* PF4/PF16\nNo function.\n* PF5/PF17\nNo function.\n* PF6/PF18\nNo function.\n* PF7/PF19\nNo function.\n* PF8/PF20\nNo function.\n* PF9/PF21\nToggle to turn filtering on or off and exit mask display.\n* PF10/PF22\nNo function.\n* PF11/PF23\nNo function.\n* PF12/PF24\nNo function.\nTo use the SymDump  for CICS Trace effectively, you need to understand the order in which the display screen is built.\nThis is done as follows:\n1.Format starts with the current line number the display is positioned on.\n2.The Mode and Line overrides are applied.\n3.The Filter Criteria are applied, if filtering (PF9) is turned on.\n4.Any line commands such as the FIND, are then applied to the results of the previous steps.\nThe significance of this is that if you are trying to filter on a string that only shows up if the trace MODE is set to FULL,", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e5f183d4533d-1", "text": "and you have the MODE set to ABBREVIATED, your filter will fail  and no entries display. In a similar fashion, if you enter\na FIND on a string that is contained only in entries that are excluded by your filter, you will not get a hit on your find  even\nthough you know that entries in the trace contain that string! Paying close attention to these issues help ensure your\nsuccess with the trace.\n 1280", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6f1792e4afa0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nRegister Contents\nDisplay Program Registers\nFollow these steps:\n1.Select Register Contents under the Formatted Display category on the Display Selection menu. The following is a\nsample Register Contents screen.\n------------------ CA SymDump for CICS REGISTER CONTENTS  -----------------\n COMMAND ===>                                                                  \n   Type S to display main storage pointed to by the register.                 \n   Prog: COBDEMO    Code: ASRA    Tran: DEMC   Appl: A01IC9NE   Date: 04/26/96 \n   User: CICSUSER   Task: 00082   Term: 2068   Node: A60L2068   Time: 09:50:13 \n                                                                      More:   +\n   Register  Contents           Description                                    \n   *PR 0     00000002           Invalid address, not captured in dump          \n _ GPR 1     00378786           Abending program's storage                     \n _ GPR 2     00378712           Abending program's storage                     \n _ GPR 3     00377C6C           Abending program's storage                     \n s GPR 4     00368050           Execute interface user area (EIUS) storage     \n   *PR 5     00004000           Invalid address, not captured in dump          \n _ GPR 6     00368548           USER24 storage area                            \n _ GPR 7     003693DF           USER24 storage area                            \n _ GPR 8     003693E0           USER24 storage area                            \n _ GPR 9     00379C56           Abending program's storage                     \n _ GPR 10    00376C48           Abending program's storage                     \n _ GPR 11    00376C48           Abending program's storage", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6f1792e4afa0-1", "text": "_ GPR 11    00376C48           Abending program's storage                     \n PF1 Help       2            3 End        4 Return     5            6          \n PF7 Backward   8 Forward    9           10           11           12         \n2.Type an s next to the register whose contents you want to view in main storage, and press Enter. A screen similar to\nthe following appears.\n              CA InterTest - MAIN STORAGE UTILITY - Termid = X508              \nOffset                                                            Address  Task\n+   0  0018B0D0 00000000 00190C98 00000000  * ...}.......q.... *   18B050    82\n+  10  00000000 00190C98 800848E0 000DA848  * .......q......y. *   18B060      \n+  20  80045570 0018B050 80045570 85C79C30  * .......&....eG.. *   18B070  Page\n+  30  05BEE9F0 05C7AC2F 05C7BC2E 05C7CC2D  * ..Z0.G...G...G.. *   18B080  +000\n+  40  00045980 00190008 000DBF0A 05EC006C  * ...............% *   18B090      \n+  50  00055680 00000000 00000000 0018B050  * ...............& *   18B0A0", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6f1792e4afa0-2", "text": "+  60  0018B054 00000000 00000000           * ............    *   18B0B0      \n \n \n \n ------------------------------------------------------------------------------\n PF1 Help       2            3 End        4 Return     5            6          \n PF7 Backward   8 Forward    9 Caps Off  10           11           12 Structure\n CORE=0018B050                                                                 \n CASD6509 ABENDED TASK EIUS STORAGE (END OF BLOCK)                      \nDisplay Floating Point or Vector Registers\nIn the SymDump  for CICS Register Contents screen, press PF8 to display vector and floating point registers.\nThe following screen appears:\n 1281", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "99d09ed6d95a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n                     CA SymDump for CICS REGISTER CONTENTS            \nCOMMAND ===>\n \n   Type S to display main storage pointed to by the register.\n \n   Prog: SYMCIC06   Code: ASRA    Tran: RHS6   Appl: U11ICIXD   Date: 01/26/17\n   User: CICSUSER   Task: 00094   Term: U006   Node: A55TU006   Time: 03:31:11\n                                                                       More: - +\n   Register  Contents           Description\n   *PR 12    00000000_0079B000  Storage area not captured in the dump\n_ GPR 13    00000000_001008A0  Assembler Execute Interface (DFHEISTG) storage\n_ GPR 14    00000000_B8714674  Abending program's storage\n_ GPR 15    00000000_001008A0  Assembler Execute Interface (DFHEISTG) storage\n \n   FPCR      10203040           Floating Point Control Register\n \n   VR 0      01000100_00000000_00000000_00000000  Vector Register\n   VR 1      01010101_00000000_00000000_00000000  Vector Register\n   VR 2      01020102_00000000_00000000_00000000  Vector Register\n   VR 3      01030103_00000000_00000000_00000000  Vector Register\n   VR 4      01040104_00000000_00000000_00000000  Vector Register\n \n PF1 Help       2            3 End        4 Return     5            6", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "99d09ed6d95a-1", "text": "PF1 Help       2            3 End        4 Return     5            6\nPF7 Backward   8 Forward    9           10           11           12\nNOTE\nVector registers from 0 to 15 overlap with the floating-point registers. When vector registers are active, only\n128-bit vector registers are displayed. Floating-point registers are the first 8 bytes of the corresponding vector\nregister.\nPrograms Referenced\nTo display a list of programs referenced by the abended transaction and various attributes of these programs, select\nPrograms Referenced under the Formatted Display category on the Display Selection menu. The following sample\nPrograms Referenced screen uses the Assembler demo program, ASMDEMO.\n-------- CA SymDump for CICS  PROGRAMS REFERENCED  ----------------\n COMMAND ===>                                                                  \n   Type + to expand or - to collapse program entries below,                    \n          or S to display the program's machine code.                         \n  Prog: ASMDEMO    Code: ASRA    Tran: DEMA   Appl: A01IC9NE   Date: 06/12/2006\n  User: CICSUSER   Task: 00046   Term: 2069   Node: A60L2069   Time: 13:01:50 \n                                                                      More:   +\n     Program   Description                Attributes                           \n _ - ASMDEMO   DFHRPL DSNAME  . . : AD1DEV.INTERT.DEMO.LOAD                    \n               DFHRPL data set volume . : OSI003                               \n               Load point, entry point  : 00369000, 00369028                   \n               Language, compile date . : Assembler                            \n               Program length . . . . . : 11408    Bytes (decimal)             \n               Load from link pack  . . : NO                                   \n               Initial execution key  . : USER", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "99d09ed6d95a-2", "text": "Initial execution key  . : USER                                 \n               Initial AMODE, RMODE . . : 24, 24                               \n               Data location  . . . . . : Below 16M line                       \n 1282", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "42ae8a7d59c6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n               Status . . . . . . . . . : ENABLED                              \n               Reload . . . . . . . . . : NO                                   \n                                                                               \n PF1 Help       2            3 End        4 Return     5 Collapse   6 Expand   \n PF7 Backward   8 Forward    9           10           11           12          \nCollapse and Expanding Entries\nJust as with the Display Selection menu's display tree, the program entries on this screen can be collapsed or expanded:\n\u2022Expanding a program entry displays the attributes of that program\n\u2022Collapsing an entry hides the attributes and displays only the program name\nFor more information about collapsing and expanding entries, see Collapse and Expand Branches.\nExamine the Program in Main Storage\nType an s in the field to the left of a program name and press  Enter to display the program in main storage.\nFiles Accessed\nTo see the files accessed by the abended transaction, select Files Accessed under the Formatted Display category on\nthe Display Selection menu. The following is a Files Accessed sample screen.\n---------------- CA SymDump for CICS  FILES ACCESSED  ---------------------\n COMMAND ===>                                                                  \n   Type + to expand or - to collapse file entries below,                       \n          or S to display the last record accessed from file.                 \n  Prog: IN25DATE   Code: FILS    Tran: SYMD   Appl: A01IC9NE   Date: 05/10/2006\n  User: CICSUSER   Task: 00793   Term: 2069   Node: A60L2069   Time: 10:34:56 \n     File      Description                Attributes                           \n _ + PROTDMP   Access method, type  . . : VSAM, RRDS", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "42ae8a7d59c6-1", "text": "_ + PROTDMP   Access method, type  . . : VSAM, RRDS                           \n _ + PROTWSD   Access method, type  . . : VSAM, RRDS                           \n _ + PROTINT   Access method, type  . . : VSAM, RRDS                           \n _ + PROTSYM   Access method, type  . . : VSAM, RRDS                           \n _ + PROTTST   Access method, type  . . : VSAM, RRDS                           \n _ + PROTFS1   Access method, type  . . : VSAM                                 \n _ + PROTDP2   Access method, type  . . : VSAM                                 \n   *** End of data ***                                                         \n                                                                               \n PF1 Help       2            3 End        4 Return     5 Collapse   6 Expand   \n PF7 Backward   8 Forward    9           10           11           12        \nCollapse and Expand Entries\nJust like the branches on the Dump/Trace Selection List display tree, the file entries on this display can be collapsed or\nexpanded:\n\u2022Expanding a file entry displays the attributes of that file\n\u2022Collapsing an entry hides the attributes and displays only the file name\nFor more information about collapsing and expanding entries, see Collapse and Expand Branches.\nAn expanded file shows more information than will fit on a single screen. Use PF7 and PF8 to scroll through the file\ninformation. The following Files Accessed screen is a composite showing all of the data available for a file.\n------------------ CA SymDump for CICS    FILES ACCESSED, --------------------\n 1283", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "69d31d4d0192-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n COMMAND ===>                                                                  \n   Type + to expand or - to collapse file entries below,                       \n          or S to display the last record accessed from file.                 \n  Prog: IN25DATE   Code: FILS    Tran: SYMD   Appl: A01IC9NE   Date: 05/10/2006\n  User: CICSUSER   Task: 00793   Term: 2069   Node: A60L2069   Time: 10:34:56 \n                                                                      More:   +\n     File      Description                Attributes                           \n _ - PROTDMP   Access method, type  . . : VSAM, RRDS                           \n               AD1DEV.C9NEC410.PROTDMP                                         \n               Disposition  . . . . . . : Share                                \n               Status . . . . . . . . . : Open, Enabled                        \n               Access options . . . . . : Add, Browse, Delete, Read, Update    \n               Object type  . . . . . . : Base cluster                         \n               LSR pool ID  . . . . . . : 1                                    \n               Key length, offset . . . :                                      \n               Record format  . . . . . : Fixed, Blocked                       \n               Remote name, system  . . :                                      \n               Recoverable  . . . . . . : NO                                   \n               Maximum record length  . : 4089                                 \n               Empty dataset  . . . . . : NO                                   \n               Number of strings  . . . : 3                                    \n               Fwd recoverable  . . . . : NO                                   \n               Journal number . . . . . :                                      \n               Add requests . . . . . . : 0                                    \n               Browse requests  . . . . : 332", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "69d31d4d0192-1", "text": "Browse requests  . . . . : 332                                  \n               Delete requests  . . . . : 0                                    \n               Read update requests . . : 1                                    \n               Read only requests . . . : 14                                   \n               Remote delete requests . : 0                                    \n               Update requests  . . . . : 1                                    \n               Highest string waits . . : 0                                    \n               Total string waits . . . : 0                                    \n               Vsam EXCPs (data)  . . . : 348                                  \n               Vsam EXCPs (index) . . . : 0                                    \n                                                                               \n PF1 Help       2            3 End        4 Return     5 Collapse   6 Expand   \n PF7 Backward   8 Forward    9           10           11           12   \nTransaction Summary\nThe Transaction Summary screen provides the attribute definitions for the abended transaction.\nFollow these steps:\n1.Select Transaction under the Formatted Display category on the Display Selection menu. A sample Transaction\nSummary screen is shown next.\n ------- CA SymDump for CICS  TRANSACTION SUMMARY ------------------\nCOMMAND ===>                                                                  \n   Prog: COBDEMO    Code: ASRA    Tran: DEMC   Appl: A01IC9NE   Date: 04/26/96 \n   User: CICSUSER   Task: 00082   Term: 2068   Node: A60L2068   Time: 09:50:13 \n                                                                      More:   +\n   Description                  Attributes                                     \n   Backout status . . . . . . : Wait                                           \n   Command security active  . : No                                             \n 1284", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9b2a3b5d7848-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n   Deadlock timeout (seconds) :                                                \n   Execution status . . . . . : Enabled                                        \n   Initial program  . . . . . : COBDEMO                                        \n   Isolate user key storage . : Yes                                            \n   Priority (1-255) . . . . . : 1                                              \n   Profile name . . . . . . . : COBDEMO                                        \n   Purgeable during stall . . : No                                             \n   Read timeout (seconds) . . :                                                \n   Remote name  . . . . . . . :                                                \n   Remote system  . . . . . . :                                                \n   Resource security active . : No                                             \n   Routing type . . . . . . . : Static                                         \n                                                                               \n PF1 Help       2            3 End        4 Return     5            6          \n PF7 Backward   8 Forward    9           10           11           12        \n2.Use PF7 and PF8 to scroll through the list.\nTerminal Summary\nThe Terminal Summary screen lists the attributes for the terminal on which the transaction was run.\nFollow these steps:\n1.Select Terminal under the Formatted Display category on the Display Selection menu. The following is a sample\nTerminal Summary screen.\n---------------- CA SymDump for CICS  TERMINAL SUMMARY  ---------------------\n COMMAND ===>                                                                  \n   Prog: COBDEMO    Code: ASRA    Tran: DEMC   Appl: A01IC9NE   Date: 04/26/96 \n   User: CICSUSER   Task: 00082   Term: 2068   Node: A60L2068   Time: 09:50:13 \n                                                                      More:   +\n   Description                  Attributes                                     \n   Access method  . . . . . . : VTAM", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9b2a3b5d7848-1", "text": "Description                  Attributes                                     \n   Access method  . . . . . . : VTAM                                           \n   Acquired status  . . . . . : ACQUIRED                                       \n   Alternate page height  . . : 24                                             \n   Alternate page width . . . : 80                                             \n   Alternate printer  . . . . :                                                \n   Alternate printcopy feature: NOALTPRTCOPY                                   \n   Alternate screen height  . : 0                                              \n   Alternate screen width . . : 0                                              \n   Map set suffix . . . . . . :                                                \n   APL keyboard status  . . . : NOAPLKYBD                                      \n   APL text feature . . . . . : NOAPLTEXT                                      \n   ASCII datastream type  . . : NOTAPPLIC                                      \n   ATI status . . . . . . . . : ATI                                            \n   Audible alarm status . . . : AUDALARM                                       \n                                                                               \n PF1 Help       2            3 End        4 Return     5            6          \n PF7 Backward   8 Forward    9           10           11           12          \n2.Use PF7 and PF8 to scroll through the list.\nTask Areas\nThe various task area displays show the respective task area in main storage. The following list briefly explains the\ncontents of the task area displays and what they show.\n 1285", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f66f47923aab-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Commarea Last CICS communications area\n\u2022EIB EXEC Interface Block\n\u2022Segmented Storage All the EXEC DUMP segmented storage areas\n\u2022TWA Transaction work area\n\u2022TUAR Terminal control table entry user area\n\u2022STCA Task control system area\n\u2022TCA Task control user area\n\u2022TACB Task abend control block\n\u2022TCTTE Terminal control table entry\n\u2022User Storage User storage areas\n\u2022Program Abending program's storage in dump format\n\u2022EIS EXEC interface structure\n\u2022CURR Instruction that caused the abend\n\u2022RIE Request Interface Element\n\u2022TIE DL/I Transaction Interface Element\nNOTE\nWhen using the integrated CICS translator of Enterprise COBOL for z/OS, the CORE=EIB command will not\nwork unless the NOLINKAGE translator option or the ADATA compiler option is specified.\nLanguage Areas\nThe various language area displays show the respective language area in main storage. The following list briefly explains\nthe contents of the language area displays and what they show.\nBLLs\nCOBOL BLL cells\nBLXs\nCOBOL BLX cells\nCWK\nCOBOL working storage\nTGT\nCOBOL task global table\nLCL\nCOBOL local storage\nDSA\nCOBOL or PL/I dynamic storage area\nEISTG\nAssembler EXEC interface storage area\nDatabase Areas\nThe various database area displays show the respective database area in main storage. The following list briefly explains\nthe contents of the database area displays and what they show.\nCLOT\nDB2 CICS life-of-task block\nRDIIN\nDB2 RDS input parameter list\n 1286", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2db83d0ff8e9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSQLCA\nDB2 SQL communication area\nSCLRCODE\nDB2 SQL return code\nDLP\nDL/I interface parameter list\nCTA\nDL/I DBCTL Control Transaction Area\nDGB\nDL/I DBCLT Global Block\nISB\nDL/I Interface Scheduling Block\nPCBL\nDL/I Program Communication Block List\nPST\nDL/I Program Specification Table\nRSB\nDL/I Remote Scheduling Block\nSCD\nDL/I System Content Directory\nUIB\nDL/I User Interface Block\nCICS System Areas\nThe various CICS system area displays show the respective CICS system area in main storage. The following list briefly\nexplains the contents of the CICS system area displays.\nCSA\nCommon system area\nCWA\nCommon work area\nOPFL\nOptional features list\nTCT\nTerminal control table\nDelete Dumps\nTo delete dumps follow these steps, follow these steps:\nNOTE\nYou can only delete dumps in the SymDump  for CICS PROTDMP data set.\n1.Generate a list of dumps by completing the Dump/Trace Analysis screen. For more information about displaying and\ncompleting this screen, see Specifying Selection Criteria.\n2.Type a D next to the dumps that you want to delete on the Dump/Trace Selection screen and Press Enter. You will be\nasked to confirm that these are the dumps that you want to delete.\n3.Press Enter to perform the deletion.\n 1287", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "90c745fc8f1d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nHold and Release Dumps\nHolding a dump prevents it from being deleted until you specifically release it. This section explains how to hold and\nrelease dumps.\nTo hold dumps, follow these steps:\n1.Generate a list of dumps by completing the Dump/Trace Analysis screen. For more information about  displaying and\ncompleting this screen, see Specifying Selection Criteria.\n2.Type an H next to the dumps you want to hold on the Dump/Trace Selection screen.\n3.Press Enter to put the dumps on hold.\nTo release dumps that are being held, follow these steps:\n1.Generate a list of dumps by completing the Dump/Trace Analysis screen. For more information about displaying and\ncompleting this screen, see Specifying Selection Criteria.\n2.Type an R next to the dumps you want to release, on the Dump/Trace Selection screen.\n3.Press  Enter to release the dumps.\nSource Listing Facility for SymDump\nYou can use the SymDump  for CICS Source Listing facility to do the following:\n\u2022Prepare your programs for further testing and debugging\n\u2022Display your source\n\u2022Search for data\n\u2022Adjust the display area and set the scrolling amount\n\u2022Display nested programs and search through them\n\u2022Display storage for our program or program data-names and variables.\nTo access InterTest for CICS functions, switch to InterTest for CICS to use the function, and then return to SymDump  for\nCICS when you are finished.\nPrepare Your Program for Symbolic Viewing\nTo prepare a program for viewing during dump analysis, follow these steps:\n1.Modify the compile or assemble JCL to include a post-processor step. For Source Listing viewing, the LISTER\nparameter of the post-processor is required. For more information about how to modify your JCL, see Symbolic\nSupport.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "90c745fc8f1d-1", "text": "Support.\n2.Modify the JCL.\n3.Recompile or reassemble the program. This puts the program's listing in the symbolic file.\nSource Selection List\nTo display the Source menu\n1.Select Option 6 Source from the SymDump  for CICS Primary Option menu. The Source menu appears.\n----------------- CA SymDump for CICS  SOURCE MENU  ------------------------\n OPTION  ===>                                                                  \n    Select a member list type, specifying optional criteria below.            \n    1  Source listings    - Display/select program source listings             \n    2  Symbolic files     - Display/select program source SYMBOLIC files       \n    Type specific or generic program/file name(s):                             \n       (Valid mask characters are  *  and/or  +)                               \n 1288", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8ba3e00f692c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    c*______ ________ ________ ________ ________ ________ ________ ________    \n \n PF1 Help       2            3 End        4 Return     5            6          \n PF7            8            9           10           11           12          \nFrom this menu you can display either a:\n\u2013Listing or a list of listings by typing 1 on the Option line.\n\u2013Symbolic file or a list of Symbolic files by typing  2 on the Option line. You can then select a Symbolic file to display\nthe Program Listings for that file.\n2.Specify either the listing name or the Symbolic File name in the unlabeled text fields to enter additional criteria. You\ncan use masks to filter the selection list for items matching the filter criteria:\n\u2013Use * in place of a string of any length. For example, c* filters for all listings beginning with the letter c.\n\u2013Use + for a single character. For example, a mask of COBD++O filters for any seven-letter item that begins with the\nletters COBD, has an O in the last position, and has any valid character in the fifth and sixth positions. For instance,\nCOBDEMO, COBDXXO, and COBDABO all meet the mask criteria, but COBDEML or COBDEM do not.\n\u2013Leave the fields blank to display all symbolic files or listings.\n3.Press Enter after you specify a listing, file, or mask. The Source Listing Selection menu appears.\nThe Source Listing Selection menu shows all of the files or listings that meet the criteria you specified on the Source\nmenu. The following is a sample Source Listing Selection menu screen.\n-------------- CA SymDump for CICS  SOURCE LISTING SELECTION  ---------------\n COMMAND ===>", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8ba3e00f692c-1", "text": "-------------- CA SymDump for CICS  SOURCE LISTING SELECTION  ---------------\n COMMAND ===>                                                                  \n   Name     File        Created      Size  Attributes                          \n _ CICSCOBA PRTSYM1  09/20/94 16:38    29  COBOL II, no purge                  \n _ CICSCOBB PRTSYM1  09/20/94 16:13    21  COBOL II, no purge                  \n _ COBDEML  PROTSYM  07/07/94 09:32    17  COBOL, no purge, composite          \n _ COBDEMO  PROTSYM  07/07/94 09:25    70  COBOL, no purge                     \n _ COB2DEML PROTSYM  07/07/94 09:33    25  COBOL II, no purge, composite       \n _ COB2DEMO PROTSYM  07/21/94 10:34   158  COBOL II, no purge                  \n _ COB2DMLX PRTSYM1  09/21/94 16:10    26  COBOL II, no purge, composite       \n _ COB2INSP PRTSYM1  02/01/94 09:11   155  COBOL II, no purge                  \n _ COB2IN25 PROTSYM  07/07/94 09:31    11  COBOL II, no purge                  \n _ COB2XCTL PRTSYM1  09/22/94 13:38   159  COBOL II, no purge", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8ba3e00f692c-2", "text": "_ CSBIN25  PROTSYM  07/07/94 09:29     8  COBOL, no purge                     \n _ C370DEML PROTSYM  07/07/94 09:33    27  COBOL/370, no purge, composite      \n _ C370DEMO PROTDGG  12/12/94 12:51   161  COBOL/370, no purge                 \n _ C370DEMO PROTWSD  12/12/94 12:51   161  COBOL/370, no purge                 \n _ C370DEMO PROTSYM  07/21/94 16:35   161  COBOL/370, no purge                 \n _ C370IN25 PROTSYM  07/07/94 09:32    12  COBOL/370, no purge                 \n   *** End of data ***                                                         \n                                                                               \n PF1 Help       2 Refresh    3 End        4 Return     5            6          \n PF7 Backward   8 Forward    9           10           11           12          \n4.Type an S next to the file or listing you want and press Enter to display that file or listing in the Source Listing Display.\nThe following is a sample Source Listing Display screen containing a COBOL source listing.\n         CA InterTest - PROTDEM FILE SOURCE LISTING DISPLAY              \n1 COMMAND ==>                                                                  \n Program= COBDEMO  Option #       Stmt #                             Margin= 01\n Nested=                                Search=                               \n2 OPTS 1 Proc div  2 Work-stor 3 Link sect 4 D-map      5 Clst/Pmap More:   +", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8ba3e00f692c-3", "text": "6 Data xref 7 Proc xref 8 Err msgs  9 Srch fwd  10 Srch bwd             \n 1289", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "144f48ab90dd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n3 PFKS 1 Help      2           3 End       4 Profile    5            6 Menu    \n       7 Backward  8 Forward   9 Next Wnd  10          11           12     \n ------------------------------------------------------------------------------\n       _ 00001 ID DIVISION.                                                    \n       _ 00002 PROGRAM-ID. COBDEMO.                                            \n       _ 00003 ENVIRONMENT DIVISION.                                           \n      4  00004 DATA DIVISION.                                                  \n       _ 00005 WORKING-STORAGE SECTION.                                        \n       _ 00006 77  S999-FIELD1             PIC S9(3).                          \n5     _  00007 77  S999-FIELD2             PIC S9(3)       VALUE +50.          \n       _ 00008 77  999-FIELD1              PIC 9(3).                           \n       _ 00009 77  999-FIELD2              PIC 9(3)        VALUE 50.           \n       _ 00010 77  FIRST-SCREEN-LEN        PIC S9(4) COMP  VALUE +1696.        \n       _ 00011 77  MSG-SCREEN-LEN          PIC S9(4) COMP  VALUE +1040.        \n       _ 00012 77  THIRD-SCREEN-LEN        PIC S9(4) COMP  VALUE +960.         \n       _ 00013 77  FOURTH-SCREEN-LEN       PIC S9(4) COMP  VALUE +1761.        \n       _ 00014 77  ERROR-SCREEN-LEN        PIC S9(4) COMP  VALUE +960.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "144f48ab90dd-1", "text": "00015*77  COMMAREA-LEN            PIC S9(4) COMP  VALUE +39.          \nThe Source Listing Display screen is divided into five major sections. The sections and the fields they contain are\nexplained next:\n1\n\u2014 This section contains fields in which you can enter commands and information. The following list describes\neach field in this section.\nCOMMAND ===>\nEnter a transaction, transaction-based command, or a Source Listing Display command.\nProgram=\nChanges the program whose code is displayed.\nOption #\nEnter an option listed on OPTS lines by number.\nStmt #\nDisplays a specific statement.\nNested=\nIndicates the displayed COBOL nested program or the program to be searched. This field is empty if the\nprogram does not contain any nested programs.\nMargin=\nAdjusts the display margins to view code past column 80.\nSearch=\nSearches for a data name or string.\n2\n\u2014 The OPTS section lists entries for the Option # field. The numbers in the following table are used in the Option\n# field to display specific sections of the source listing or to search for data. Using these options makes it easy to\nlocate specific sections of your program.\nFor COBOL and PL/I programs, all of the OPTS labels cannot display at once.\n1.Tab to More + and\n2.Press Enter to view OPTS 5 to the end.\n3.Tab to More - and\n 1290", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f70dd6617e72-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n4.Press Enter to view OPTS 1 to 10.\nOption COBOL PL/I Assembler\n1 * Procedure Division Data Cross Reference First CSECT\n2 * Working-Storage Aggregate Length Table -\n3 * Linkage Section Storage Requirements -\n4 Data Division Map Static Storage Map -\n5 CLIST/Pmap Variable Storage Map Macro and Copy Source\nCatalog for high level output\n6 Data Cross Reference Table of Offsets Data Cross Reference\n7 Procedure Cross Reference Generated Code (Assembler-\nlike)Literals Cross Reference\n8 Error Messages Error Messages Error Messages\n9 Search Forward Search Forward Search Forward\n10 Search Backward Search Backward Search Backward\n13 Local-Storage Procedure Cross Reference -\n14 - Labels Cross Reference -\nNOTE\n* These options can be used with NESTED= entries to request a display of these sections for a specific nested\nprogram.\nIf you have InterTest for CICS, you can also use the following options:\nOption COBOL PL/I Assembler\n11 Indirect Commands Indirect Commands  \n12 Conditional Breakpoint Options Unconditional/Conditional\nBreakpointUnconditional/Conditional\nBreakpoint Options\nNOTE\nThe sections available for display depend on which version of the post-processor LISTER parameter was used\nto compile or assemble the program. For more information, see Adding Symbolic Information.\n3\n\u2014 The PFKS section lists the PF key functions that are available for this screen.\n4\n\u2014 Column 1 (represented by the underscore _) of each line is reserved for entering single-letter commands.\nIf you have InterTest for CICS, this column is also reserved for breakpoint-related functions. When a breakpoint\ntakes effect during execution, it is identified in column 1 with one of the following letters:\nA\nAutomatic ( InterTest for CICS generated)\nU", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f70dd6617e72-1", "text": "A\nAutomatic ( InterTest for CICS generated)\nU\nUnconditio nal (stops before  selected item)\n)\nUnconditional (stops after selected item)\nC\nConditional\n 1291", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "400e9bad9da2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nV\nVariable-change (COBOL and Assembler)\nR\nRequest\n5\n\u2014 This section displays the source code from the program named in the Program= field. The numbers at the\nleft side of each line are the COBOL or PL/I statement numbers from the compiled listing or the Assembler\nhexadecimal location number from the assembled listing.\nNOTE\nThe display screen's format varies by terminal type. For 132-column terminals, lines of code display as\nis and can be viewed in full. For 80-column terminals, the compiler output is automatically reformatted\nso that most of the code is viewed in columns 1 to 80. To view code beyond column 80, change the\ndisplay margins.\nHow You Adjust the Margins\nBecause certain compiler output (particularly Assembler and Optimizer/II  output) extends beyond 80 columns, you may\nneed to adjust the display margins to view more of your program's Source Listing.\nWhen you adjust the margins, the statement or location numbers stay on the screen as the rest of the display shifts left or\nright. A plus sign (+) in the line above the display area indicates the column where shifting begins.\nTo adjust the output display to view portions of the listing to the right of column 80:\n1.Enter the position number of the desired left margin in the Margin= field. Valid entries are 1 through 50.\n2.Press Enter. The screen displays the output beginning at the position specified.\nNOTE\nIf there is no output beyond column 80, SymDump  for CICS redisplays columns 1 through 80 regardless of\nthe position number you specified.\nLIST Command -- Position the Display\nWhen you initiate the Source Listing facility, you can easily name the program and position the display at any statement\nnumber with a single command:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "400e9bad9da2-1", "text": "number with a single command:\nLIST=progname,#nnnnn\nprogname\nIndicates the name of the program you want to view.\n#\nIs required.\nnnnnn\nIndicates the statement number from 1 to 99999.\nNOTE\nIf the requested statement number is greater than the number of statements in the listing, the greatest number is\ndisplayed.\nAssembler Programs\nWhen you initiate the Source Listing facility you can position the Assembler display at a specific offset location in a\nCSECT. Use the command form:\n 1292", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "adc55b365099-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nLIST=progname,offset\nprogname\nIndicates the name of the program you want to view.\noffset\nIndicates a one- to six-hexadecimal number from 0 to FFFFFF.\nFor example, to position the Source Listing display of program COBDEMO with statement 99 highlighted near the top of\nthe display area enter:\nLIST=COBDEMO,#99\nTo position the Source Listing display of program ASMDEMO with offset 0007E8 highlighted near the top of the display\narea enter:\nLIST=ASMDEMO,7E8\nYou can position the display area to include more data, source listing, or storage items using the following options:\nOption #\nDisplays a specific section, choose an Option # from the OPTS.\nStatement #\nDisplays a particular statement, enter the statement number from 1 to 9999 in the Statement # field and press\nEnter.\nNested=\nDisplay a particular nested program, enter the program name in the Nested = field and press Enter.\nSearch=\nDisplays the code defining a particular data item in Working-storage, Local-Storage, or the Linkage section, enter\nthe data name in the Search = field and press Enter. To display the code surrounding a particular paragraph or\nlabel, enter the paragraph name or label name in the Search = field and press Enter .\nDisplacement=\nDisplay the listing at a specific displacement in an Assembler program, enter the displacement from 0 to FFFFFF\nin the Displacement= field.\nIssue Commands\nThe Command line on the Source Listing Display is always available regardless of what view options are currently in use.\nYou can use the Command line to enter a transaction, a transaction-based line command (such as a CORE command),\nand the Source Listing Display commands.\nABI Command", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "adc55b365099-1", "text": "and the Source Listing Display commands.\nABI Command\nTurns interception of CICS abends on and off.\nBOTTOM Command\nPositions the listing at the end of the source code within the complete online listing.\nThe short form is BOT; no PF key is assigned\n 1293", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dfe3f532e824-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBPO Command\nJumps to the Breakpoint Options build screen when setting a breakpoint.\nNOTE\nYou must have InterTest for CICS installed to use this feature.\nBTRACE Command\nDisplays the CICS Command Back Trace Table. This table is built from the EXEC CICS Trace entries found in the CICS\nTrace Table when the dump is captured.\nBWD Command\nScrolls backward. The scroll amount is set on the Source Listing Profile.\nThe assigned PF key is PF7.\nCNTL Command\nDisplays the CNTL Command menu. CNTL is only valid if the InterTest for CICS global installation option SYMDINT is set\nto YES. To check the value of SYMDINT, use ITST Option 7.1.2 from InterTest for CICS.\nNo PF key is assigned.\nCS Command\nResets the Source Listing display to Abending (Current) Statement.\nCORE Command\nDisplays the Main Storage menu. Select an option to view a main storage (CORE) display.\nNo PF key is assigned.\nDOWN Command\nShifts the listing down a specific number of lines.\nEND Command\nReturns to the prior display or menu.\nThe assigned PF key is PF3.\nFILE Command\nDisplays the Auxiliary Storage menu. Select an option to view a file or queue. FILE is only valid if the InterTest for CICS\nglobal installation option SYMDINT is set to YES. To check the value of SYMDINT, use ITST Option 7.1.2 from InterTest\nfor CICS.\nNo PF key is assigned.\nFIND Command\nLocates the specified string. Use the syntax shown next.\nFIND string  [NEXT | PREV]\n 1294", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2ed92ed46a07-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nstring\nReplace with any group of letters or numbers up to 31 characters long. If string  contains a blank, you must\nenclose string  in apostrophes. If string  contains an apostrophe ('), you must enclose string  in quotes (\").\nNEXT\nLocates the next occurrence of string . (Pressing Enter performs the same action.)\nPREV\nLocates the previous occurrence of string .\nThe short form is F; no PF key is assigned.\nFS Command\nPositions listing at a specific line number. Use the syntax shown next.\nFS line-number\nline-number\nReplace with any line number.\nNo PF key is assigned.\nFO Command\nPositions listing at a specific hexadecimal offset. Use the syntax shown next.\nFO hex-offset\nhex-offset\nReplace with any offset within an Assembler program.\nNo PF key is assigned.\nFP Command\nPositions listing at a specific paragraph, procedure, or label. Use the syntax shown following.\nFP label\nlabel\nReplace with any valid label up to 31 characters long. Valid labels include data names, CSECTs, procedures, and\nparagraph names.\nNo PF key is assigned.\nFWD Command\nScrolls forward the amount indicated on the Source Listing Profile.\nThe assigned PF key is PF8.\nHELP Command\nDisplays help for the Source Listing facility.\nThe assigned PF key is PF1.\n 1295", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6047e664c168-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nITST Command\nDisplays the ITST Primary Option menu. ITST is only valid if the InterTest for CICS global installation option SYMDINT is\nset to YES. To check the value of SYMDINT, use ITST Option 7.1.2 from InterTest for CICS.\nPF Key:  See MENU\nIC Command\nDisplays the Indirect Commands Build screen.\nNOTE\nYou must have InterTest for CICS installed to use this feature.\nLEFT Command\nShifts the listing left a specific number of characters\nLOCATE Command\nFinds a label, line number, offset, or special area. Use the syntax shown next; select one operand from the list.\nLOCATE label\n       line-number\n       hex-offset\n       .xx\nlabel\nReplace with any valid label up to 31 characters long. Valid labels include data names, CSECTs, procedures, and\nparagraph names. A COBOL paragraph name consisting of all numbers is not a valid label.\nline-number\nReplace with any line number.\nhex-offset\nReplace with an offset from an assembler program. Offsets are indicated by a leading + character.\n.xx\nReplace with the appropriate special indicator. Special indicators are language-dependent. Select one from the\nappropriate list.\nFor COBOL, select an indicator from the following list:\nSpecial Indicator Meaning\n.PD \u2014 Procedure Division\n.WS \u2014 Working Storage Section\n.LC \u2014 Local-Storage Section\n.LS \u2014 Linkage Section\n.DM \u2014 DMPA\n.PM \u2014 COBOL/VS PMAP/CLIST\n.CL \u2014 COBOL/VS PMAP/CLIST\n.OF \u2014 COBOL II OFFSET/LIST\n.LI \u2014 COBOL II OFFSET/LIST\n 1296", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "05fa3f7faccb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n.DX \u2014 Data Cross-Reference\n.PX \u2014 Procedure Cross-Reference\n.EM \u2014 Error Messages\nFor PL/I, select an indicator from the following values:\nSpecial Indicator Meaning\n.AG \u2014 Aggregate List\n.SR \u2014 Storage Registers\n.SS \u2014 Status Storage\n.VS \u2014 Variable Storage\n.OF \u2014 Offsets\n.GC \u2014 Generated Code\n.PX \u2014 Procedure Cross-Reference\n.LX \u2014 Label Cross-Reference\n.DX \u2014 Data Cross-Reference\n.EM \u2014 Error Messages\nFor Assembler, select an indicator from the following values:\nSpecial Indicator Meaning\n.C1 \u2014 First CSECT\n.1C \u2014 First CSECT\n.MC \u2014 Macro Catalog\n.XR \u2014 Cross-Reference\n.LI \u2014 Literals\n.EM \u2014 Error Messages\nThe short form is LOC or L; no PF key is assigned.\nMARGIN Command\nShifts the listing to a specific margin position\nMENU Command\nDisplays the high-level menu. When not at a breakpoint, it is the ITST Primary Option Menu; when at a breakpoint, it is the\nBreakpoint Primary Option Menu. MENU is only valid if the InterTest for CICS global installation option SYMDINT is set to\nYES. To check the value of SYMDINT, use ITST Option 7.1.2 from InterTest for CICS.\nThe assigned PF key is PF6.\nMONITOR Command\nSets monitoring for the current program using the CICS user ID displayed on the Profile. MONITOR is only valid if the\nInterTest for CICS global installation option SYMDINT is set to YES. To check the value of SYMDINT, use ITST Option\n7.1.2 from InterTest for CICS.\n 1297", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3223aeaaa872-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe assigned PF key is PF5.\nOFFALL Command\nTurns off all breakpoints set by Userid or Terminal.\nNOTE\nYou must have InterTest for CICS installed to use this feature.\nPROFILE Command\nDisplays the Source Listing Profile, where you can change settings for the current session.\nThe assigned PF key is PF4.\nRIGHT Command\nShifts the listing right a specific number of characters\nSTATUS Command\nDisplay the Monitoring Status report (Option 2.4 on the InterTest Primary Option menu) for the current program. You can\nremove monitoring, breakpoints, and options directly from the Status display. STATUS is only valid if the InterTest for CICS\nglobal installation option SYMDINT is set to YES. To check the value of SYMDINT, use ITST Option 7.1.2 from InterTest\nfor CICS.\nThe assigned PF key is PF12.\nSTATUS ALL Command\nDisplays the Monitoring Status report for all programs, transactions, and terminals InterTest for CICS is monitoring in the\nregion. STATUS ALL is only valid if the InterTest for CICS global installation option SYMDINT is set to YES. To check the\nvalue of SYMDINT, use ITST Option 7.1.2 from InterTest for CICS.\nThere is no assigned PF key.\nTOP Command\nPositions the listing at the beginning of the source code in the complete online listing.\nThere is no assigned PF key.\nUP Command\nShifts the listing up a specific number of lines.\n=.x.y.z Command\nFastpath to InterTest for CICS Primary Menu Option x.y.z.\nNOTE\nYou must have InterTest for CICS installed to use this feature.\nAction-Characters Supported from a Source Listing Display\nEntering a single character on your source listing can perform the following function:\nd", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3223aeaaa872-1", "text": "Entering a single character on your source listing can perform the following function:\nd\nDisplays program or variable storage at a breakpoint.\n 1298", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c068c74473bc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nEnter the d function next to a statement that references or defines the variable you want to display. If the statement\nreferences the variable, you must also position the cursor under the variable name before pressing Enter.\nHow You Search for Data\nFrom the Source Listing Display screen, you can define, search for, and display any character string (such as a data item,\nlabel, or paragraph name). This is a quick way to go to different areas in a listing.\nDisplay a Data Item Definition\nTo display a data item definition\n1.Enter a data item name up to 31 characters in the Search= field.\n2.Press Enter to begin the search. The data item and its definition are highlighted when found.\nSearch for a Data Item\nTo search for a data item\n1.Enter up to 31 characters in the Search=  field.\n2.Specify the search direction in the Option # field. (Option # 9 is Search Forward; Option # 10 is Search Backward.)\n3.Press Enter to begin the search.\nFor COBOL nested programs, the current nested program (indicated in the NESTED= field) is searched first for the\nspecified data item. If the data item is not found in the indicated program, then the main program and other nested\nprograms for the item are searched.\nNOTE\nIt is not necessary to enter the entire data item, label, or paragraph name. You can enter the first few characters\nto begin your search. For example, if you wanted to search for TASKNUM, you could enter TASK, TASKN, and\nso on, in the Search= field.\nScroll Forward and Backward\nPF7 and PF8 scroll the compiler output backward and forward, respectively. The default scroll amount is one page.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c068c74473bc-1", "text": "However, you can change the scroll amount on the Source Listing Profile screen. For more information, see Set the Scroll\nAmount. \nChange the Program\nAt any time during testing, you can change the program with which you are working.\nTo change the program displayed\n1.Enter the desired program name in the Program= field.\n2.Press Enter to display the listing from the beginning of the program, or use the Option #, Statement #, or Search=\nfields to select another point of initial display before pressing Enter.\nInfo Area\nThe info area is located at the top of the Source Listing Display screen under the Search field. The info area displays\nvarious windows depending on the value in the Display window field in the Source Listing Profile.\nTo change the information displayed in the info area, change the value in the Display window field.\nFollow these steps:\n1.On the Source Listing screen, either type profile  in the command line and press Enter , or press PF4.\n 1299", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "49c4858a3a85-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe Profile screen appears.\n2.Specify the desired value in the Display window field, and press Enter .\nThe info area displays the information that you requested.\nNotes:\n\u2022Alternatively, type 20-24 in the Option # field to display the required window.\n\u2022Press PF9 to switch between the windows in order. PF9 does not switch between the windows when the Backtrace\nFacility is active.\nThe Display window field has the following values:\nN (None)\nDisables the info area so that you are able to see more of the source code.\nT (Titles)\nDisplays the Title window in the info area. The Title window shows the title and header lines of your Source Listing\nDisplay, including the option and PF key descriptions. T is the default value for the Display window field unless\nchanged during the product installation.\nR (Registers)\nDisplays the Register window in the info area. The Register window shows the registers and attributes of your\nprogram.\nK (Keep)\nDisplays the Keep window in the info area. The Keep window shows your program data items.\nP (Program)\nDisplays the Program window in the info area. The Program window displays the load module name and the\nsymbolic file information.\nRegister Window\nThe Register window allows you to display and modify the contents of registers, and view an area where a register points\nto.\nThe following screen shows the Register window:\n   CA InterTest for CICS  - PROTSYM FILE  ABEND DETECTED BREAKPOINT             \nCOMMAND ===>                                                                        \nProgram= COBDEMO  Option #       Stmt #                                             \n                                        Search=                                     \n------------------------------------------------------------------------------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "49c4858a3a85-1", "text": "Search=                                     \n------------------------------------------------------------------------------------\n R0-R7  3520A424 35209220 00100100 3520B5C8 3520A540 350F79E0 350F7998 B5200108     \n R8-R15 3520A5C8 3520A2C0 3651B15C 3651B904 3651B11C 352090D0 B651C242 00000000     \n Cond. Code = 0   Amode = 31   ExecKey = USER   TransIsolate = YES                  \n------------------------------------------------------------------------------------\n _ 000412 CONTINUE-TASK.                                                            \n   000413**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED                              \n A    ==>     ADD +1 TO TASKNUM.                                                    \n...\nThe Register window contains the following fields:\n\u2022R0-R7\n\u2022R8-R15\nDisplays the contents of registers at the current statement of the program.\n\u2022Cond. Code\n 1300", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eb31e513765b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIndicates the current condition code.\n\u2022Amode\nDisplays the current addressing mode of the program.\n\u2022ExecKey\nDisplays the ExecKey for the current program if the CICS Storage Protection Option is active, depending on the option\nspecified in the program definition.\n\u2022TransIsolate\nDisplays the transaction isolation option of the current task if the CICS Transaction Isolation Option is active.\n\u2022To modify the program registers, overtype the displayed contents with the desired value, and press Enter .\n\u2022To view the area pointed to by a register, overtype the first displayed character of the register with either an at sign (@)\nfor a 24-bit address, or with a percent sign (%) for a 31-bit address, and press Enter .\nProgram Window\nThe Program window displays the name of the load module that you analyze.\nThe following screen shows the Program window:\n   CA InterTest for CICS  - PROTSYM FILE  SOURCE LISTING DISPLAY                \nCOMMAND ===>                                                                        \nProgram= CSBIN25  Option #       Stmt #                                             \n                                        Search=                                     \n Load module= COBDEML                                                               \n Symbolic file: PROTSYM  Timestamp: 2014-05-27 05:05 Language: IBMCOB 4.2           \n---------+--------------------------------------------------------------------------\n _ 000023 PROCEDURE DIVISION USING COMM-TEXT.                                       \n _ 000024     MOVE ZERO TO DIVCT.                                                   \n...\nThe Symbolic file, Timestamp, and Language fields provide information about the subprogram specified in the Program\nfield, not the load composite module in the Load module field.\nSet the Scroll Amount\nThe scroll amount determines how much more of your source listing displays each time you press PF7 or PF8.\nTo set the scroll amount for scrolling backward and forward (PF7 and PF8)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eb31e513765b-1", "text": "To set the scroll amount for scrolling backward and forward (PF7 and PF8)\n1.Type profile  on the command line and press Enter, or press PF4 from a Source Listing screen to display the Profile\nscreen.\n2.Overtype the current PF7/8 Amount= entry with one of the following:\nPAGE\nThe size (number of lines) of the display area on the Source Listing Display.\nHALF\nHalf the size of the display area.\nnnnn\nAny number of lines from 1 to 9999.\nSTOP\nGo to the next or previous breakpoint in the program.\nNOTE\nSetting the Scroll Amount to STOP is an excellent way to review all breakpoints set in your program if\nyou have InterTest for CICS installed.\n 1301", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cd9ef050491d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n3.Press Enter. The change takes effect immediately and returns to the Source Listing Display screen.\nDisplay and Search Through Nested Programs\nSymDump  for CICS provides support for COBOL II nested programs when the COBOL nested programs are recompiled\nwith the COBOL II post-compiler provided with SymDump  for CICS.\nCOBOL II nested programs allow non-unique paragraph and data names to be defined across nested programs.\nTherefore, SymDump  for CICS can support qualified names  for COBOL programs. A qualified name consists of\na one- to 30-byte COBOL program name, a colon, and a one- to 30-byte paragraph or data name. For example,\nprogram1:datanam1 is a qualified name. Qualified names ensuring that the correct version of datanam1 (which can be\ndefined in multiple programs) displays.\nWhen SymDump  for CICS displays the source code for a nested program, the Nested= field displays below the Program=\nfield. The Nested= field is 30 bytes long and indicates the name of the nested program for the currently displayed source\ncode. If you are using the Source Listing facility to display a COBOL nested program and you press PF8 to scroll through\nthe entire source code of the program, the Nested= field changes each time the source code for a different nested\nprogram displays.\nThe names of all nested programs within a specific COBOL program are listed at the end of the Procedure Name Cross\nReference section (Option  # 7).\n              CA InterTest for CICS - PROTDEM FILE SOURCE LISTING DISPLAY              \nCOMMAND ===>                                                                   \nProgram= ACME2000 Option #       Stmt #                             Margin= 01 \n Nested=                                Search=", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cd9ef050491d-1", "text": "Nested=                                Search=                                \nOPTS 1 Proc div  2 Work-stor 3 Link sect 4 D-map      5 Clst/Pmap More:   +    \n     6 Data xref 7 Proc xref 8 Err msgs  9 Srch fwd  10 Srch bwd                \nPFKS 1 Help      2           3 End       4 Profile    5 Monitor    6 Menu      \n     7 Backward  8 Forward   9 Next Wnd 10           11           12 Status    \n---------+---------------------------------------------------------------------\n _ DEFINED      PROCEDURE NAMES         REFERENCES                             \n _   122 3000-REGISTER-HANDLER          P107                                   \n _   131 4000-FORCE-ABEND               P108                                   \n _   139 5000-HANDLE-ROUTINE            D129                                   \n _   152 9000-RETURN                    P109                                   \n _   168 9999-GOBACK                                                           \n _   227 9999-GOBACK                    P221                                   \n DEFINED   CROSS-REFERENCE OF PROGRAMS     REFERENCES                          \nEXTERNAL   ACME200A . . . . . . . . . . . 120                                 \n     171   ACME200N . . . . . . . . . . . 229 114                             \n       2   ACME2000 . . . . . . . . . . . 230                                 \nEXTERNAL   ACME2001 . . . . . . . . . . . 117                                 \nEXTERNAL   DFHEI1 . . . . . . . . . . . . 127 137 147 160 166                 \nNESTED PROGRAM MAP                                                             \nPROGRAM ATTRIBUTE CODES (RIGHTMOST COLUMN) HAVE THE FOLLOWING MEANINGS:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cd9ef050491d-2", "text": "PROGRAM ATTRIBUTE CODES (RIGHTMOST COLUMN) HAVE THE FOLLOWING MEANINGS:     \nThe Nested= field also indicates the nested program that Option # 1, 2, and 3 apply to, and the nested program that\nSymDump  for CICS searches first for any data name or paragraph name that you specify in the Search= field. If a\nparagraph name or data name is not found in the specified nested program, SymDump  for CICS then searches the main\nprogram.\nFor example, if Option # 2 and Nested=program2 are specified, the Working Storage section for nested program\nprogram2 is displayed. Also, if Nested=program3 and Search=datanam1 are specified, nested program program3 is\nsearched first for datanam1; if datanam1 is not found, the main program is searched for datanam1.\n 1302", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "78fe1b1418ea-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nExit the Source Listing Facility\nTo exit the Source Listing facility, type END  on the Command line and press Enter.\nInterTest for CICS users can exit the menus using =X.\nBatch Utility\nBatch utility IN25DMPU provides maintenance and reporting functions for your SymDump  for CICS VSAM repository\n(PROTDMP file).\nThese topics detail the required JCL and command syntax used to execute the batch utility.\nCommand Syntax\nYou enter commands one per line in the SYSIN file using the command syntax described in this section.\nA valid command consists of a keyword followed by an argument or expression generally specified in the following format:\nkeyword argument operator value\nNotes:\n\u2022operator  and value  are not always required.\n\u2022The OPT command keyword requires a slightly different syntax that is described later in this topic.\nThe following are examples of valid commands:\nDSN TEST.SYMDUMP.PROTDMP\nLIST ALL\nDELETE AGE GT 30\nOPT PURGE Y\nSupported Keywords\nThe supported command keywords follow:\nCOPY\nCopies selected dumps from the secondary repository (ODSN) to the primary repository (DSN). You must specify\nboth DSN and ODSN keywords prior to using the COPY keyword.\nDELETE\nDeletes selected dumps from the primary repository (DSN). You must specify the DSN keyword before using the\nDELETE keyword.\nDSN\nDefines the dsname for the primary repository. You must specify this prior to using any other commands.\nLIST\nProvides a list of dumps contained within the primary repository that fulfill required selection criteria; this keyword\nalso provides PROTDMP file statistics.\nLOCK\nLocks the selected dumps in the primary repository (DSN) to prevent deletion. You must specify a DSN keyword\nprior to using the LOCK keyword.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "78fe1b1418ea-1", "text": "prior to using the LOCK keyword.\nNote:  This command is equivalent to the H line command on the Dump/Trace Selection screen.\n 1303", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "27413ffe375c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nODSN\nDefines the dsname for the secondary repository. You must specify this keyword prior to using the COPY\ncommand.\nOPT\nOverrides an option value in the primary repository (DSN). Valid options and their values are described later in\nthis topic.\nUNLOCK\nUnlocks selected dumps in the primary repository (DSN) that lets you delete or modify them. You must specify the\nDSN keyword prior to using the LOCK keyword.\nNote:  This command is equivalent to the R line command on the Dump/Trace Selection screen.\nArguments\nFollowing are the descriptions for all the valid arguments. Some command keywords only accept a subset of these\narguments.\nAGE\nSelects dumps by the number of days since they were created.\nFor example:\nLIST AGE EQ 10\nDELETE AGE GT 35\nALL\nSelects all dumps.\nFor example:\nLIST ALL\nUNLOCK ALL\nCODE\nSelects dumps by the abend code.\nFor example:\nLOCK CODE EQ ATNI\nDELETE CODE EQ ASRA\nDATE\nSelects dumps by their created date in the format of MM/DD/YYYY.\nFor example:\nLIST DATE EQ 11/20/2007\nDELETE DATE GT 11/18/2007\nLOCK\nSelects dumps that are locked in hold status that prevents them from being deleted.\nFor example:\nLIST LOCK\nPGM\nSelects dumps by the name of the abending program.\nFor example:\nLIST PGM EQ ASMDEMO\nDELETE PGM EQ COB2DEMO\nTERM\nSelects dumps by the name of the terminal where the abending transaction began.\nFor example:\nLIST TERM EQ U008\n 1304", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "35422a896869-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDELETE TERM GE U010\nTRAN\nSelects dumps by the name of the abending transaction.\nFor example:\nLIST TRAN RANGE DEMA DEMP\nDELETE TRAN EQ DEMC\nOperators\nThe valid operators are as follows:\nEQ\nSelects dumps if the value of the argument is equal to the value specified.\nNE\nSelects dumps if the value of the argument is not equal to the value specified.\nGE\nSelects dumps if the value of the argument is greater than or equal to the value specified.\nGT\nSelects dumps if the value of the argument is greater than the value specified.\nLE\nSelects dumps if the value of the argument is less than or equal to the value specified.\nLT\nSelects dumps if the value of the argument is less than the value specified.\nRANGE\nSelects dumps if the value of the argument is between the two values specified.\nOption Arguments for the OPT Command Keyword\nThe valid arguments for the OPT command are as follows:\nALL\nDisplays the current settings of all options from SymDump for CICS.\nFor example:\nOPT ALL\nSUPPRESSA\nSuppresses AP0001 dumps. Specify whether full AP0001 SVC dumps should be suppressed for the ASRA and\nASRB abends. If you specify N, dumps conform to the specifications defined for your CICS system.\nFor example:\nOPT SUPPRESSA Y\nOPT SUPPRESSA N\nSUPPRESSC\nSuppresses CICS transaction dumps. Specify if a transaction dump should be written to the CICS dump data set.\nFor example:\nOPT SUPPRESSC Y\nOPT SUPPRESSC N\nPURGE\nPurges dumps automatically. Specify if automatic purging of dumps should occur during startup of SymDump  for", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "35422a896869-1", "text": "CICS. Qualification for purging is determined by age (number of days to hold dumps), or the HOLD indicator set\non the Selection List menu.\n 1305", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a9a9aa89059c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFor example:\nOPT PURGE Y\nOPT PURGE N\nMESSAGES\nMessages to the operator. Specify if informational messages should be written to the console when SymDump  for\nCICS intercepts dump or trace requests.\nFor example:\nOPT MESSAGES Y\nOPT MESSAGES N\nCAPTUREX\nCaptures EXEC CICS dumps. Specify if transaction dumps produced by EXEC CICS DUMP commands should\nbe captured by SymDump .\nFor example:\nOPT CAPTUREX Y\nOPT CAPTUREX N\nDUMPCURR\nDumps only the current program. Specify if the dump should include just the active program or all linked and\nloaded programs.\nFor example:\nOPT DUMPCURR Y\nOPT DUMPCURR N\nDYNAPURGE\nDynamic purge of dumps. Specify if dynamic purging of dumps should occur during dump capture for non-\nheld dumps on a FIFO basis. Dynamic purging occurs only when space to hold the dump being captured is\ninadequate; dynamic purging deletes only enough dumps to make space for the new dump. HOLD days are\nignored for dynamic purge.\nFor example:\nOPT DYNAPURGE Y\nOPT DYNAPURGE N\nPREVABEND\nUse Prev Abend code. Specify if the original abend code is presented when a Handle Abend command is issued.\nThe Handle Abend routine usually issues an EXEC CICS Abend or Dump command which masks the original\nproblem. A 'Y' in this option causes the original dump to be formatted. In order to set PREVABEND to 'Y', the\nCAPTUREX parameter must also be set to 'Y'.\nFor example:\nOPT PREVABEND Y\nOPT PREVABEND N\nHOLD", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a9a9aa89059c-1", "text": "For example:\nOPT PREVABEND Y\nOPT PREVABEND N\nHOLD\nNumber of days to hold dumps. Specify the number of days non-held dumps are retained.\nFor example:\nOPT HOLD 20\nSELECT\nDumps select start date. Specify the date that dump selection starts.\nFor example:\nOPT SELECT CURRDATE\nOPT SELECT 01/01/2007\n 1306", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ea281b09d87c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSUPPRESSD\nSuppresses duplicate transaction dumps. Specify if duplicate dump suppression is in effect. A dump is considered\na duplicate when an abend has a matching program/offset with a previously captured dump.\nFor example:\nOPT SUPPRESSD Y\nOPT SUPPRESSD N\nSUPPRESSL\nDuplicates dump suppression limit. Specify the maximum number of duplicate dumps captured for a given\noccurrence of program/offset. This parameter is recognized only when SUPPRESSD=Y is also specified.\nFor example:\nOPT SUPPRESSL 158\nEXCLUDE ADD\nCauses the specified abend code to be added to the exclusion list to prevent dumps from being created for this\ntype of abend.\nFor example:\nOPT EXCLUDE ADD ASRA\nEXCLUDE DEL\nCauses the specified abend code to be removed from the exclusion list to allow dumps to be created for this type\nof abend.\nFor example:\nOPT EXCLUDE DEL ASRA\nJCL\nThis area describes the JCL used to run batch utility and DD statements.\nSYSIN\nContains commands for batch utility, specified one per line. Blank lines are ignored. Any line containing an\nasterisk \"*\" as the first non-blank character is treated as a comment.\nSYSPRINT\nContains the output report from the batch utility.\nPARM='TEST'\nIf specified, the batch utility only validates input commands.\nExample JCL:\n//UTIL EXEC PGM=IN25DMPU,PARM='TEST'                                    \n//STEPLIB DD DISP=SHR,DSN=CAI.CAVHLOAD                 \n//SYSPRINT DD SYSOUT=*                                    \n//SYSIN  DD *                                           \n    DSN CA.TEST.PROTDMP \n    LIST ALL                   \n* --- COMMENT ---", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ea281b09d87c-1", "text": "DSN CA.TEST.PROTDMP \n    LIST ALL                   \n* --- COMMENT ---              \n    LIST DATE EQ 11/20/2007    \n    OPT ALL\n/*   \nExample output in SYSPRINT:\n DSN CA.TEST.PROTDMP                                                     \n                                                                                \n LIST ALL                                                                       \n                                                                                \n 1307", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "459a72861051-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n File Statistics for CA.TEST.PROTDMP                                     \n                                                                                \n 265 total records, 199 records used, 66 records free in 2 blocks               \n 63 continuous records in largest block                                         \n Record size is 8,185                                                           \n                                                                                \n CICS       DATE         TIME      ABEND   PROGRAM   TRANSID TERMID  STATUS     \n--------------------------------------------------------------------------------\n A31IC9N8   11/19/2007   10.00.23   ASRA   ASMDEMO    DEMA   U035               \n A31IC9N8   11/19/2007   10.00.30   ASRA   PL1DEMO    DEMP   U035               \n A31IC9N8   11/19/2007   10.00.40   ASRA   COBDEMO    DEMC   U035               \n A31IC9N8   11/19/2007   10.00.44   ASRA   ASMDEMO    DEMA   U035               \n A31IC9N8   11/19/2007   10.01.00   ASRA   ASMDEMO    DEMA   U035               \n A31IC9N8   11/20/2007   09.12.04   ASRA   COBDEMO    DEMC   U032               \n A31IC9N8   11/20/2007   09.12.14   ASRA   PL1DEMO    DEMP   U032               \n LIST DATE EQ 11202007                                                          \n                                                                            \n File Statistics for CA.TEST.PROTDMP                                     \n                                                                               \n 265 total records, 199 records used, 66 records free in 2 blocks               \n 63 continuous records in largest block", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "459a72861051-1", "text": "63 continuous records in largest block                                         \n Record size is 8,185                                                           \n                                                                                \n CICS       DATE         TIME      ABEND   PROGRAM   TRANSID TERMID  STATUS     \n--------------------------------------------------------------------------------\n A31IC9N8   11/20/2007   09.12.04   ASRA   COBDEMO    DEMC   U032               \n A31IC9N8   11/20/2007   09.12.14   ASRA   PL1DEMO    DEMP   U032               \nOPT ALL                                    \nSuppress AP0001 dumps:        Y (Y,N)  Messages to operator:      Y (Y,N)\nSuppress transaction dumps:   Y (Y,N)  Capture exec cics dumps:   Y (Y,N)\nAutomatic purge of dumps:     N (Y,N)  Use previous abend code:   Y (Y,N)\nAutomatic purge hold days:   39 (0-99) Dump only current program: Y (Y,N)\nDynamic purge of oldest dump: N (Y,N)  Dump select start date: 13/06/2005)\nSuppress duplicate dumps:     Y (Y,N)  (CURRDATE or MM/DD/YYYY)      \nDuplicate dump limit:       016 (1-999)                   \n                                       \nEnter abend codes to be excluded:  '*' is generic character         \n....       ATNI       ASRA       ATND      ....    \n....       AZTQ       AZCT       ATCV      ....   \nPrinting Dumps\nThe SymDump  for CICS batch print facility (IN##PDMP where ## indicates a two digit number that represents the CICS\nrelease) lets you specify criteria to determine which dumps to print, just as you specify criteria to select dumps for the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "459a72861051-2", "text": "SymDump  for CICS Selection List. Dumps printed using IN##PDMP contain most of the storage areas and summary\ninformation that appears when an actual CICS transaction dump is printed using the CICS DFHDUP utility program.\nSample JCL for program IN##PDMP can be found in CAI.CAVHJCL member SYMPDMP.  Customize this member using\nthe instructions provided at the top.\n 1308", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aaef22184af7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nIn an exceptional situation when IN##PDMP does not provide the information you require, take a CICS\ntransaction dump and format it using the CICS DFHDUP utility program.\nPRINT and INDEX Commands\nUse the following format to specify the PRINT command in the SYSIN data set to request printouts of the dumps that meet\nthe criteria specified by the parameters:\n PRINT parameters\n \nUse the following format to specify the INDEX command in the SYSIN data set to request a list of the dumps that meet the\ncriteria specified by the parameters:\n INDEX parameters\n \nObserve the following rules:\n\u2022Specify the PRINT or INDEX command in any column.\n\u2022You can specify multiple PRINT and INDEX commands; however, enter each specification on a new line.\n\u2022Specify at least one parameter for the PRINT command. Specify the INDEX command without parameters to print the\ncomplete index of the SymDump  for CICS data set.\n\u2022Separate parameters with commas.\n\u2022You can enter parameters on multiple lines. To continue a command specification, end the line with a comma and\nbegin the continuation in any column on the next line.\n\u2022To include a comment, leave one blank space after the last parameter on a line, and then specify the comment.\nNOTE\nIf the INDEX command is specified without parameters, a comment is not allowed.\n\u2022A JCL DD statement must identify the SymDump  for CICS data set from which the dumps are to be selected.\nNOTE\nA sample job stream follows the description of the command parameters.\nThe following list defines the parameters for the PRINT and INDEX commands.\nParameter Description Format Default\nFROMDATE= The beginning date from which\ndumps are selected; if omitted,\nall dates usedmmddyyyy None\nFROMTIME= The beginning time from which\ndumps are selectedhhmmss 000000", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aaef22184af7-1", "text": "FROMTIME= The beginning time from which\ndumps are selectedhhmmss 000000\nTODATE= The ending date up to which\ndumps are selectedmmddyyyy Current system date\nTOTIME= The ending time up to which\ndumps are selectedhhmmss 235959\nCICS= The applid of the CICS region\nfrom which dumps are selectedapplid None\nDUMP= The dump code for which\ndumps are selectedxxxx None\n 1309", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a65bf186493e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPROGRAM= The program name for which\ndumps are selectedxxxxxxxx Nnoe\nTRANSID= The transaction ID for which\ndumps are selectedxxxx None\nTERMID The terminal ID for which dumps\nare selectedxxxx None\nUSERID The CICS userid for which\ndumps are selectedxxxxxxxx None\nALL All dumps are printed ALL None\nNote:  Be aware of these considerations when specifying parameters:\n\u2022You cannot specify the ALL parameter with any other parameter.\n\u2022For the FROMTIME and TOTIME parameters to limit the dumps that are printed, they must be specified with the\nFROMDATE parameter. If the TODATE parameter is omitted, it defaults to the current day.\nJob Stream to Print Dumps and Source Listing\nThe following sample job stream prints selected dumps for program COBDEMO and uses InterTest for CICS to print the\nprogram's source listing. The first step prints the requested dumps and the index of the dump data set; the second step\nprints the saved listing for program COBDEMO.\nNOTE\nThe SymDump  for CICS load library must be the first library in STEPLIB.\n //YOURNAME      JOB YOURJOBINFO \n //*Step 1 prints dumps for COBDEMO and lists all dumps in the data set\n //STEP1    EXEC PGM=IN##PDMP,REGION=4M           ## = CICS release eg. 66,67...\n //STEPLIB  DD  DSN=CAI.CAVHLOAD,DISP=SHR         CA SymDump for CICS load library\n //         DD  DSN=your.CICS.LOADLIB,DISP=SHR    CICS load library\n //PROTDMP  DD  DSN=SYMDUMP.PROTDMP,DISP=SHR      CA SymDump for CICS data set", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a65bf186493e-1", "text": "//DFHDMPDS DD  DSN=&SYMDFILE,DISP=(,PASS),UNIT=SYSDA,\n //             DCB=(RECFM=VB,LRECL=4092,BLKSIZE=4096),\n //             SPACE=(CYL,(3,1))\n //DFHPRINT DD  SYSOUT=*\n //SYSPRINT DD  SYSOUT=*\n //REPORT   DD  SYSOUT=*                          Output data set\n //SYSIN    DD  DUMMY,DCB=BLKSIZE=80\n //DFHTINDX DD  SYSOUT=*\n //SYMSYSIN DD  *\n PRINT FROMDATE=03012014,TODATE=03042014,PROGRAM=COBDEMO   Print specifications \n INDEX                                                     Index specifications\n /*\n //*Step 2 prints the program listing for COBDEMO\n //STEP2    EXEC    PGM=IN25UTIL\n //STEPLIB  DD  DSN=CAI.CAVHLOAD,DISP=SHR      CA InterTest load library\n //SYSUDUMP DD  SYSOUT=*\n //MESSAGE  DD  SYSOUT=*\n //OUTPUT   DD  SYSOUT=*,                         Output data set\n //             DCB=(RECFM=FBA,LRECL=121,BLKSIZE=2420)\n //PROTSYM  DD  DSN=INTRTST.PROTSYM,DISP=SHR\n //CARDS    DD  *\n PRINT=COBDEMO\n 1310", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d370dd0a24a9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n /*\n //\n \nIn the previous example:\n\u2022The PROTDMP DD statement names the SymDump  for CICS data set\n\u2022The REPORT DD statement names the data set to which the dumps are to be written\n\u2022The PRINT parameters specify that all dumps be printed that were generated from 3/1/2014 to 3/4/2014 for program\nCOBDEMO\n\u2022The INDEX command specifies that a complete index of the dump data set be printed because there are no\nparameters to limit the listing\n\u2022The OUTPUT DD statement identifies the data set to which the COBDEMO listing will be written\nSample Index of a CICS Data Set\nThe following example shows a sample index of all of the dumps in the PROTDMP dump data set.\n REPORT IN64PDMP            C A   S Y M D U M P                  DATE:03/05/2014\n                                                                 TIME:  14:57:18\n                          D U M P   F I L E   I N D E X          PAGE:         1\n   FILE      CICS     DATE       TIME      ABEND    PROGRAM    TRANSID    TERMID\n -------------------------------------------------------------------------------\n  PROTDMP     C2AG   03/05/2014  16:29:03    ATCH     INVNTRY     INVT      E066 \n  PROTDMP     C2AG   03/05/2014  14:54:16    ASRA     COBDEMO     DEMC      E058  \n  PROTDMP     C2AG   03/05/2014  13:55:28    ASRA     COBDEMO     DEMC      E098", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d370dd0a24a9-1", "text": "PROTDMP     C2AG   03/05/2014  13:05:23    AEIL     COBDEMO     DEMC      E058  \n  PROTDMP     C2AG   03/05/2014  12:07:44    USR1     PAYROLL     PYRL      E125 \n  PROTDMP     C2AG   03/05/2014  10:14:21    USR2     PL1DEMO     DEMP      E008  \n  PROTDMP     C2AG   03/05/2014  09:29:08    ASRA     ASMDEMO     DEMA      E139  \n  PROTDMP     C2AG   03/03/2014  18:13:12    AEIL     FEDTAX      FTAX      E127  \n  PROTDMP     C2AG   03/03/2014  16:04:02    ASRA     SALESTOT    SLST      E244\n \nFor each dump, SymDump  for CICS provides the following information:\nCICS\nCICS region where the dump was produced.\nDate\nDate the dump was produced.\nTime\nTime the dump was produced.\nAbend\nCode identifying the type of dump.\nProgram\nProgram that produced the dump.\nTransid\nTransaction that produced the dump.\nTermid\nTerminal ID that produced the dump.\n 1311", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "62b9bbcbadf7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nProduction Strategies\nThis article describes how to debug production dumps in:\n\u2022Your production region with symbolic support\n\u2022Your test region with symbolic support\n\u2022Your production or test region without symbolic support\nYou will also learn how to capture the CICS Internal Trace to analyze program flow and performance problems in either\ntest or production regions.\nAll these scenarios assume that there is only one production region and one test region. However, you can expand the\nexamples to include multiple production and test regions.\nSymbolic Support\nTo take full advantage of SymDump  for CICS, you need an up-to-date symbolic listing of the application programs that\nexecute in your test or production CICS regions. When you are ready to move a program from test to production, ensure\nyou save its symbolic listing so it is available if the program needs further debugging.\nTo get an up-to-date symbolic listing of the application programs that execute in your test or production CICS regions:\n1.Move the listing to a separate production symbolic file.\n2.Use the IN25UTIL batch program to unload the listing from the test symbolic file to an intermediate data se\n3.Reload it to the production symbolic file. For more information, see Maintaining a PROTSYM File.\nThe examples in the following areas detail transaction dump analysis with symbolic support and assume that there are:\n\u2022Multiple symbolic files (For information on defining and maintaining multiple files, see Allocate Files.\n\u2022Up-to-date symbolic listings of production programs\nYou might have several different versions of a program and, consequently, several different symbolic listings on various\nsymbolic files.\n\u2022For COBOL and COBOL II programs, SymDump  for CICS automatically finds the right symbolic listing for the program\nversion you are debugging, if it exists", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "62b9bbcbadf7-1", "text": "version you are debugging, if it exists\n\u2022For PL/I and Assembler programs, and for COBOL and COBOL II programs that do not have matching listings,\nSymDump  for CICS displays all of the symbolic files containing listings for the program so you can select the one you\nwant\nIf you do not have an up-to-date symbolic listing for the program, you can get symbolics by recompiling or reassembling\nthe program with the appropriate post-processor program after the dump is generated, but before you examine it online.\nFor more information, see Symbolic Support .\nHow You Analyze Production Transaction Dumps\nThis example assumes that you want to analyze production transaction dumps in your production region with symbolic\nsupport. We recommend this method because you can take advantage of the full power of SymDump  for CICS by using\nthe symbolic program feature to quickly analyze and resolve abends.\nWhen a production program abends, you can use all of the SymDump  for CICS options to examine the dump. Because\nthe current symbolic listing is available, you can inspect the instruction that triggered the abend, examine the contents of\ndata items, and scroll through the abending program listing.\nWith InterTest for CICS available in production, you can also set the following:\n\u2022Monitoring from SymDump  for CICS and re-execute the program\n\u2022Breakpoints or other InterTest for CICS options before re-executing the program\n 1312", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ac5e0eb0d7ef-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNow when the program abends, you can inspect the statement backtrace table to determine the program's logic flow. After\nInterTest for CICS halts the program at a breakpoint, you can do the following:\n\u2022More easily determine the cause of the error\n\u2022Fix it dynamically\n\u2022Continue program execution to make sure the program completes as expected\nHow You Analyze Production Dumps from Your Test Regions\nThis scenario assumes that you want to analyze production dumps in your test region with symbolic support. You may\nprefer this method if you want to take advantage of the combined symbolic capabilities of SymDump  for CICS without\nrunning the SymDump  for CICS dump analysis component in production.\nTo analyze production dumps from your test regions, you need to meet the following requirements:\n\u2022Have read access to the production symbolic file and SymDump  for the CICS dump data set from a test region\n\u2022Have running the complete version of SymDump  for CICS in test region\n\u2022Ensure that the SymDump  for CICS application that executes in production only captures the transaction dumps in the\nproduction region\n\u2022Ensure that the SymDump  for CICS in the test region captures its own transaction dumps, but can display the dumps\ncaptured by both production and test regions\n\u2022Have loaded the CICS file definitions in the test region that reference the production symbolic file and the SymDump\nfor CICS dump data set (see Define CICS File Entries)\nDefine CICS File Entries\nEach region for which you want SymDump  for CICS to capture dumps needs its own SymDump  for CICS dump data set.\nRegions can share a dump data set only if they are not active at the same time.\nEach region must have a FILE definition for its own SymDump  for CICS dump data set. If you want to analyze production", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ac5e0eb0d7ef-1", "text": "dumps in test regions, your test region requires extra FILE definitions for any production symbolic files and dump data\nsets you want to access. The following lists detail how these entries can be defined.\nProduction Region FCT name DSNAME\nProduction Dump Data Set: PROTDMP SYMDUMP.PROD.FILE\nProduction Symbolic File: PROTSYM .PROD.SYMBOLIC\nTest Region FCT name DSNAME\nTest Dump Data Set: PROTDMP SYMDUMP.TEST.FILE\nTest Symbolic File: PROTSYM TEST.SYMBOLIC\nAdditional FILE Definitions DMPPROD SYMDUMP.PROD.FILE\nSYMPROD .PROD.SYMBOLIC\n\u2022The DMPPROD FILE definition in test references the SymDump  for CICS production dump data set.\n\u2022The SYMPROD FILE definition in test references the production symbolic file.\nNote: The symbolic file ddnames must also be defined in the IN25OPTS module of the CICS region that references them.\nAccess Production Dumps\nFollow these steps:\n1.Enter SYMD  from your test region. SymDump  for CICS displays the Primary Option menu.\n2.Select option 1 Analysis on the Primary Option menu to display the SymDump  for CICS Dump/Trace Analysis screen.\nThe Dump/Trace Analysis screen lets you select dumps from the SymDump  for CICS data set.\n 1313", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0e43eb3bc800-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n-----------  CA SymDump for CICS PRIMARY OPTION MENU  ---------------------\n OPTION  ===>                                                                  \n1 Analysis           - Display/select captured CICS dumps/traces          \n2 Tracing            - Capture CICS internal trace for analysis           \n3 Configuration      - Display/modify CA SymDump initialization parameters\n4 Start              - Start dump capture facility                        \n5 Stop               - Stop dump capture facility                         \n6 Source             - Display/select program source files/listings         \n7 Status/Maintenance  -  Product status and maintenance functions\n8 What's new?        - Display information about CA SymDump for CICS\nX Exit               - Terminate CA SymDump for CICS menu processing           \n \n \n                       CA SymDump for CICS V10.0\n             Copyright \u00a9 2016 CA.  All rights reserved. \n                                                                               \n PF1 Help       2            3 End        4 Return     5            6          \n PF7            8            9           10           11           12      \nNOTE\nThe Dump File ID parameter, by default, references the SymDump  for CICS dump data set for the current\nCICS region.\n------------  CA SymDump for CICS DUMP/TRACE ANALYSIS  --------------------\n COMMAND ===>                                                                  \n   Type captured dump/trace selection criteria, then press ENTER.             \n   Dump File ID PROTDMP_          (Required, mask characters '*' and/or '+'    \n   CICS applid  ________          VTAM specific application ID                 \n   User ID  . . ________                                                       \n   Program  . . ________                                                       \n   Transaction  ____                                                           \n   Dump code  . ____                                                           \n   Terminal . . ____                                                           \n   Start date . 01/01/1999        mm/dd/yyyy                                   \n   Start time . 00                he", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0e43eb3bc800-1", "text": "Start time . 00                he                                           \n   End date . . 04/23/2006        mm/dd/yyyy                                   \n   End time . . 24                he                                           \n                                                                               \n PF1 Help       2            3 End        4 Return     5            6          \n PF7            8            9           10           11           12          \n3.To access dumps from the production dump data set, overtype the Dump File ID name with the test region's FILE\ndefinition for the production dump data set. For example, overtype PROTDMP with DMPPROD as shown in the\nfollowing screen.\n-----------  CA SymDump for CICS DUMP/TRACE ANALYSIS  ---------------------\n COMMAND ===>                                                                  \n   Type captured dump/trace selection criteria, then press ENTER.             \n   Dump File ID DMPPROD_          Required, mask characters '*' and/or '+'    \n   CICS applid  ________          VTAM specific application ID                 \n   User ID  . . ________                                                       \n   Program  . . ________                                                       \n   Transaction  ____                                                           \n   Dump code  . ____                                                           \n   Terminal . . ____                                                           \n 1314", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "93b65bab4d41-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n   Start date . 01/01/2003        mm/dd/yyyy                                   \n   Start time . 00                he                                           \n   End date . . 04/23/2006        mm/dd/yyyy                                   \n   End time . . 24                he                                           \n \n PF1 Help       2            3 End        4 Return     5            6          \n PF7            8            9           10           11           12    \nSymDump  for CICS lists all the dumps from DMPPROD (the production dump data set) meeting the other selection\ncriteria specified on this menu.\nNow you can analyze the production dump in your test region using all of the symbolic capabilities of SymDump  for CICS.\nIf you need to do further debugging on the abending program and you also have InterTest for CICS installed, you can go\nback to the production region and set appropriate breakpoints.\nAnalyze Dumps Without Symbolic Support\nThis scenario assumes that you want to analyze production dumps without symbolic support. You may prefer this method\nif you do not want to maintain symbolic listings of production programs, but want to use the powerful SymDump  for CICS\nnon-symbolic online capabilities.\nTo debug in production, you need the following:\n\u2022The complete version of SymDump  for CICS\n\u2022An up-to-date hardcopy program listing\nTo analyze the dump in your test region, see How You Analyze Production Dumps from Your Test Regions. You will\nneed all of the requirements outlined there except the symbolic listings of your production programs. Follow the steps for\ndefining FILE definitions and accessing production dumps described in that scenario.\nAnalyze the Problem\nWhen a production program abends, all of the SymDump  for CICS options except the ability to examine the abending", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "93b65bab4d41-1", "text": "programs source listing are available to help you resolve the problem. Using SymDump  for CICS is much easier than\ndeciphering a hexadecimal dump because you can:\n\u2022Display all formatted dump areas except for the source listing entry to identify where the abend occurred. The displays\nidentify the instruction, displacement, register contents, and storage values at the abend. Most of the time, the dump\nanalysis also identifies the cause of the abend. Use your hardcopy listing to determine how to fix the problem.\n\u2022Examine formatted CICS areas; for example, system and user TCA, CSA, TCTTE, and so on. You do not have to\ncompute offsets because these areas are formatted by data name.\n\u2022Display the formatted trace table, beginning with the first entry for the abended task. SymDump  for CICS trace table\noptions let you list:\n\u2013Entries for all tasks or just the abended task\n\u2013All entries or just EIP entries\n\u2013Entries in text or hexadecimal format\nIf you need more help, you can move the program back to the test region and monitor it there with InterTest for CICS.\nCapture the CICS Internal Trace Table\nWith SymDump  for CICS, you can capture and review the CICS Internal Trace Table at any time. The SymDump  for CICS\nonline formatted trace utility captures an image of the CICS Internal Trace Table, and can replace the AUX TRACE facility\nfor debugging system performance problems in many cases.\n 1315", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e00b5aabb2b8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBefore you capture and review your trace, complete the following:\n1.Ensure that you have sufficient space on your PROTDMP file. The larger the CICS Internal Trace Table, the more\nspace you need.\n2.Expand your extended DSA allocation to accommodate the size of the trace you will review. You will need additional\nDSA of approximately twice the size of the CICS Internal Trace Table for each trace being viewed.\n3.Expand the size of your CICS Internal Trace Table so you will not lose entries you may be trying to capture when the\ntable wraps. To do this, use the CICS CETR transaction or modify the size of the CICS Internal Trace Table using the\nSIT TRTABSZ parameter.\nOnce you complete these steps, execute the transaction you want to trace. When you reach a point where enough trace\nentries exist, you have two methods available for capturing the trace with SymDump  for CICS.\nCapture the CICS Internal Trace Table from the Primary Option Menu\nFollow these steps:\n1.Display the SymDump  for CICS Primary Option menu by entering the SYMD transaction identifier from CICS.\nYou can also select option 5 Dump Analysis  from the InterTest for CICS Primary Option menu.\n-----------  CA SymDump for CICS PRIMARY OPTION MENU  ---------------------\n OPTION  ===>                                                                  \n1 Analysis           - Display/select captured CICS dumps/traces          \n2 Tracing            - Capture CICS internal trace for analysis           \n3 Configuration      - Display/modify CA SymDump initialization parameters\n4 Start              - Start dump capture facility                        \n5 Stop               - Stop dump capture facility                         \n6 Source             - Display/select program source files/listings         \n7 Status/Maintenance  -  Product status and maintenance functions\n8 What's new?        - Display information about CA SymDump for CICS", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e00b5aabb2b8-1", "text": "8 What's new?        - Display information about CA SymDump for CICS\nX Exit               - Terminate CA SymDump for CICS menu processing           \n \n \n                          \n \n \n                                                                        \n PF1 Help       2            3 End        4 Return     5            6          \n PF7            8            9           10           11           12       \n2.Select option 4 Start to start the SymDump  for CICS dump capture facility.\n3.Select option 2 Tracing to capture the trace table and write it to the PROTDMP file.\n4.Select option 1 Analysis to select the captured trace for display.\n5.On the Dump/Trace Analysis screen, enter *trace*  in the Program field to limit your selection criteria to traces.\nAll traces appear on the Dump/Selection List screen with the keyword *TRACE* in the Program field.\n6.Select your trace by creation time and SymDump  for CICS displays the Formatted Trace Table display.\nCapture the CICS Internal Trace Table from CICS\nTo capture the CICS Internal Trace table from CICS\n1.Execute the SYMT  transaction from CICS. SymDump  for CICS writes the complete CICS Internal Trace out to the\nPROTDMP file.\n2.To select your trace for analysis, execute the SYMD  transaction.\nYou can invoke SymDump  for CICS from the InterTest for CICS Primary Option menu.\n3.Select option 1 Analysis to select the captured trace for display.\n 1316", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eb132b857b71-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n4.On the Dump/Trace Analysis screen, enter *trace*  in the Program field to limit your selection criteria to traces.\nAll traces display on the Dump/Selection List screen with the keyword *TRACE* in the Program field.\n5.Select your trace by creation time and SymDump  for CICS displays the Formatted Trace Table display.\nExample How to Use the Trace Capturing Option\nThe following is an example of how to use the trace capturing option.\nTo use the trace capturing option\n1.Use the CETR transaction to ensure that the trace table is large enough and will not wrap. 1000 KB should be enough\nfor this example. On heavily used systems, higher values may be appropriate.\n2.Execute the Assembler demo program, DEMA . You should see a Welcome to the InterTest Demo Session welcome\nscreen.\n\u2013If you see this screen, proceed to Step 3.\n\u2013If you do not, then the DEMA test transaction abended on a previous step, and you need to clean out the temp\nstorage record left over from this abend by using the CECI transaction.\n\u2022Type CECI DELETEQ TS QUEUE(Demotte) to replace the value with your current terminal ID.\n\u2022Run the DEMA transaction again.\n3.Allow the DEMA transaction to abend.\n4.Type SYMT  from CICS or select option  2 Tracing from the SymDump  for CICS Primary Option menu. The following\nmessage appears:\nCASD6375 CICS internal trace has been captured by SymDump  for CICS.\nNOTE\nIf you receive the following message, start the SymDump  for CICS dump capture facility by selecting option 4\nStart  from the SymDump  for CICS Primary Option menu.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eb132b857b71-1", "text": "Start  from the SymDump  for CICS Primary Option menu.\nCASD6377 CA SymDump for CICS not started, trace capture not performed\n5.Press Clear , type SYMD , and press Enter to display the Primary Option menu, if you captured the table with the SYMT\ntransaction.\n6.Select option 1 Analysis . SymDump  for CICS displays the Dump/Trace Analysis menu.\n7.Specify appropriate options on the Dump/Trace Analysis menu, as shown in the following sample screen, and press\nEnter.\n8.Use the Program entry *trace*  to limit the selection to traces only. The other information shown on the following screen\nis for illustration only. You need to substitute your specific dump file name and date and time information.\n-----------  CA SymDump for CICS DUMP/TRACE ANALYSIS  ---------------------\n COMMAND ===>                                                                  \n \n   Type captured dump/trace selection criteria, then press ENTER.             \n \n   Dump File ID PROTDMP_          Required, mask characters '*' and/or '+'    \n   CICS applid  ________          VTAM specific application ID                 \n   User ID  . . ________                                                       \n   Program  . . *trace*_                                                       \n   Transaction  ____                                                           \n   Dump code  . ____                                                           \n   Terminal . . ____                                                           \n   Start date . 07/24/2006        mm/dd/yyyy                                   \n   Start time . 00                he                                           \n   End date . . 07/24/2006        mm/dd/yyyy                                   \n   End time . . 24                he                \n 1317", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3551f2804810-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n9.Select the trace entry. Notice traces are captured under the SYMD transaction with the program name *TRACE* and\nan abend code of SYMT.\n-----------  CA SymDump for CICS DUMP/TRACE SELECTION  --------------------\n COMMAND ===>                                                                  \n \n   Type S select,  D delete, H hold, R release, I history                       \n \n     Dumpfile  Tran  Program   Offset  Abend       Created        # Dups  Status\n s - PROTDMP   SYMD  *TRACE*           SYMT  07/24/2006 11:00:10               \n   *** End of data ***                                                         \nBefore selecting and viewing a TRACE captured with SymDump  for CICS, the TRACE FORMAT REGION must have\nbeen started. For more information, see Activate Your Product.\nSymDump  for CICS displays the trace in a Formatted Trace Table.\n--------------  CA SymDump for CICS   FORMATTED TRACE TABLE  --------------                               \nCOMMAND ===>                                             MODE: A SCROLL: PAGE                               \n000001 00028 QR    TR 0202 TRSR  EXIT  SET_INTERNAL_TABLE_SIZE/OK                                            \n   \n000002 00028 QR    AP 00E1 EIP   EXIT  SET-TRACEDEST         OK                         \n 00F4,00000000 ....,00007804 ....\n000003 00028 QR    AP 00E1 EIP   ENTRY HANDLE-CONDITION                                  0004,2004E018 ..\n\\.,08000204 ....\n000004 00028 QR    PG 0700 PGHM  ENTRY SET_CONDITIONS        1FEFE789,1FEFE786                               \n  \n000005 00028 QR    PG 0701 PGHM  EXIT  SET_CONDITIONS/OK     0", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3551f2804810-1", "text": "000006 00028 QR    AP 00E1 EIP   EXIT  HANDLE-CONDITION      OK                         \n 00F4,00000000 ....,00000204 .... \n000007 00028 QR    AP 00E1 EIP   ENTRY INQUIRE-TRACEDEST                                 0004,2004E018 ..\n\\.,08007802 .... \n000008 00028 QR    TR 0201 TRSR  ENTRY INQUIRE_INTERNAL_TRACE                                                \n    \n000009 00028 QR    TR 0202 TRSR  EXIT  INQUIRE_INTERNAL_TRACE/OK STARTED,1F4                                 \n  \n000010 00028 QR    AP 00E1 EIP   EXIT  INQUIRE-TRACEDEST     OK                         \n 00F4,00000000 ....,00007802 ....   000011\n00028 QR    AP 00E1 EIP   ENTRY INQUIRE-TRACEFLAG                                 0004,2004E018 ..\n\\.,08007812 .... \n000012 00028 QR    KE 0201 KEDD  ENTRY INQUIRE_GLOBAL_TRACE                                                  \n    \n000013 00028 QR    KE 0202 KEDD  EXIT  INQUIRE_GLOBAL_TRACE/OK ON                                            \n  \n000014 00028 QR    AP 00E1 EIP   EXIT  INQUIRE-TRACEFLAG     OK                         \n 00F4,00000000 ....,00007812 .... \n000015 00028 QR    AP 00E1 EIP   ENTRY INQUIRE-TRACEFLAG                                 0004,2004E018 ..\n\\.,08007812 .... \n000016 00028 QR    AP 00E1 EIP   EXIT  INQUIRE-TRACEFLAG     OK                         \n 00F4,00000000 ....,00007812 ....", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3551f2804810-2", "text": "00F4,00000000 ....,00007812 .... \n000017 00028 QR    AP 00E1 EIP   ENTRY INQUIRE-TRACEDEST                                 0004,2004E018 ..\n\\.,08007802 .... \n000018 00028 QR    TR 0201 TRSR  ENTRY INQUIRE_INTERNAL_TRACE                                                \n   \n \n 1318", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1e6983584674-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n000020 00028 QR    AP 00E1 EIP   EXIT  INQUIRE-TRACEDEST     OK                         \n 00F4,00000000 ....,00007802 .... \n000021 00028 QR    AP 00E1 EIP   ENTRY INQUIRE-TRACEDEST                                 0004,2004E018 ..\n\\.,08007802 ....  \n                                                                                                             \n    \nPF1 Help       2            3 End         4 Mask      5 Repeat     6 Return On                               \n   \nPF7 Backward   8 Forward    9 All Trace  10 Left     11 Right     12 Retrieve                  \n10. Type the FIND DEMA on the Command line, and then press Enter. SymDump  for CICS displays the following screen.\n--------------  CA SymDump for CICS   FORMATTED TRACE TABLE  --------------                                  \nCOMMAND ===>                                             MODE: A SCROLL: PAGE                                \n  \nCASD6247 DEMA found in entry 001396                                                                           \n001396 TCP   QR    XM 1101 XMAT  ENTRY ATTACH                DEMA,0,T,NO,YES,TERMINAL,2005F930 , 02400000    \n  \n001397 TCP   QR    XM 0401 XMLD  ENTRY LOCATE_AND_LOCK_TRANDEF DEMA,YES                                      \n  \n001398 TCP   QR    DD 0301 DDLO  ENTRY LOCATE                1F500040,2153A38C,TXD,DEMA                       \n001399 TCP   QR    DD 0302 DDLO  EXIT  LOCATE/OK             200F9AB0 , D7000000", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1e6983584674-1", "text": "001400 TCP   QR    XM 0402 XMLD  EXIT  LOCATE_AND_LOCK_TRANDEF/OK 200FBAC0 , 000000B9,DEMA                   \n   \n001401 TCP   QR    DS 0002 DSAT  ENTRY ATTACH                1F509DF8,0,1,NON_SYSTEM,1F509DF8 , 0000030C     \n  \n001402 TCP   QR    DS 0003 DSAT  EXIT  ATTACH/OK             03840009                                       \n001403 TCP   QR    XM 1102 XMAT  EXIT  ATTACH/OK             1F509DF8 , 0000030C,0000030C                    \n  \n001404 TCP   QR    AP FD91 ZATT  EXIT  ATTACH                                                                 \n001405 TCP   QR    AP 4D00 CQCQ  ENTRY MERGE_CIB_QUEUES                                                     \n001406 TCP   QR    AP 4D01 CQCQ  EXIT  MERGE_CIB_QUEUES/OK                                                  \n001407 TCP   QR    AP 4D00 CQCQ  ENTRY GET_CIB                                                               \n  \n001408 TCP   QR    AP 4D01 CQCQ  EXIT  GET_CIB/EXCEPTION     CIB_QUEUE_EMPTY,00000000,00000000               \n          \n001409 TCP   QR    DS 0004 DSSR  ENTRY WAIT_OLDW             TCP_NORM,00059DD0,CSTP,NO,IDLE,DFHZDSP          \n          \n001410 XM    QR    DS 0012 DSKE  ENTRY TASK_REPLY            1FFEC780,1F4BF380                               \n           \n001411 XM    QR    XM 1305 XMTA  ENTRY TASK_REPLY            1F509DF8,03840009,03840009", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1e6983584674-2", "text": "001412 XM    QR    SM 0F01 SMAR  ENTRY ALLOCATE_TRANSACTION_STG BELOW,USER,YES,NO,NO                         \n         \n001413 XM    QR    SM 0F02 SMAR  EXIT  ALLOCATE_TRANSACTION_STG/OK                                           \n           \n001414 XM    QR    PG 0801 PGXM  ENTRY INITIALIZE_TRANSACTION                                                \n            \n001415 XM    QR    PG 0802 PGXM  EXIT  INITIALIZE_TRANSACTION/OK                                             \n            \n001416 XM    QR    AP 0590 APXM  ENTRY INIT_XM_CLIENT        YES                                             \n           \n                                                                                                             \n         \n 1319", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ff9dba41ee1b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPF1 Help       2            3 End         4 Mask      5 Repeat     6 Return On                               \n         \nPF7 Backward   8 Forward    9 All Trace  10 Left     11 Right     12 Retrieve   \n11. Press PF4,  and specify a filter mask to display entries for task 00031 only.\n--------------  CA SymDump for CICS   FORMATTED TRACE TABLE  --        \n TASK  TCB   DM ID   MOD   TYPE OR DATA                                        \n 00031 *     *  *    *     *                                                   \n                                                                               \n \n \n \n \n \n PF1 Help       2            3 End         4           5            6         \n PF7            8            9 All Trace  10          11           12         \n12. Press PF3 to activate the filter. The following screen appears.\n--------------  CA SymDump for CICS   FORMATTED TRACE TABLE  -------------\n COMMAND ===>                                             MODE: A SCROLL: PAGE \n 001698 00031 QR    AP EA00 TMP   ENTRY LOCATE                PFT,DFHCICST     \n 001699 00031 QR    AP EA01 TMP   EXIT  LOCATE                PFT,DFHCICST,1F5ACB20,NORMAL          \n 001700 00031 QR    AP 0591 APXM  EXIT  INIT_XM_CLIENT/OK                     \n 001701 00031 QR    AP 1790 TFXM  ENTRY INIT_XM_CLIENT        2005F930 , 02400000       \n 001702 00031 QR    XM 1001 XMIQ  ENTRY SET_TRANSACTION       TERMINAL,2005F930", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ff9dba41ee1b-1", "text": "001703 00031 QR    XM 1002 XMIQ  EXIT  SET_TRANSACTION/OK                   \n 001704 00031 QR    AP 1791 TFXM  EXIT  INIT_XM_CLIENT/OK     00000000,00000000,YES,NO   \n 001705 00031 QR    US 0401 USXM  ENTRY INIT_TRANSACTION_USER 00000000,YES  \n 001706 00031 QR    XS 0401 XSXM  ENTRY ADD_TRANSACTION_SECURITY 00000000 , 00000000  \n 001707 00031 QR    XS 0402 XSXM  EXIT  ADD_TRANSACTION_SECURITY/OK         \n 001708 00031 QR    US 0402 USXM  EXIT  INIT_TRANSACTION_USER/OK 1F52409F , 1F526090,0  \n 001709 00031 QR    DS 0002 DSAT  ENTRY SET_PRIORITY          1             \n 001710 00031 QR    DS 0003 DSAT  EXIT  SET_PRIORITY/OK                     \n 001711 00031 QR    KE 0201 KEDD  ENTRY INQUIRE_ANCHOR        0000002C      \n 001712 00031 QR    KE 0202 KEDD  EXIT  INQUIRE_ANCHOR/OK     1F58A000       \n 001713 00031 QR    KE 0201 KEDD  ENTRY INQUIRE_ANCHOR        00000010      \n 001714 00031 QR    KE 0202 KEDD  EXIT  INQUIRE_ANCHOR/OK     800513B0                    001715 00031 QR   \n DP 0900 DPXM  ENTRY\nINIT_XM_CLIENT", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ff9dba41ee1b-2", "text": "DP 0900 DPXM  ENTRY\nINIT_XM_CLIENT                          \n 001716 00031 QR    SM 0301 SMGF  ENTRY GETMAIN               2156950C , 00000060,NO,00,DPTA        \n 001717 00031 QR    SM 0302 SMGF  EXIT  GETMAIN/OK            2002C0F0        \n 001718 00031 QR    DP 0901 DPXM  EXIT  INIT_XM_CLIENT/OK                    \n                                                                             \n PF1 Help       2            3 End         4 Mask      5 Repeat     6 Return On\n PF7 Backward   8 Forward    9 All Trace  10 Left     11 Right     12 Retrieve\n13. Type the FIND command f *exc to identify the first exception record as shown in Step 13.\n14. Press Enter to find the first exception record. SymDump  for CICS displays the following.\n--------------  CA SymDump for CICS   FORMATTED TRACE TABLE  --------                    \n COMMAND ===>                                             MODE: A SCROLL: PAGE                               \n                      \n 1320", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "70775ec03789-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n CASD6247 *EXC found in entry 001760                                                                         \n                      \n 001760 00031 QR    AP 1942 APLI  *EXC* Program-Check        \n START_PROGRAM,ASMDEMO,CEDF,FULLAPI,EXEC,NO,200C70D0,00000000 , 000000\n 001761 00031 QR    AP 0790 SRP   *EXC* PROGRAM_CHECK                                                        \n                      \n 001762 00031 QR    DS 0010 DSBR  ENTRY INQUIRE_TASK                                                         \n                      \n 001763 00031 QR    DS 0011 DSBR  EXIT  INQUIRE_TASK/OK       ESSENTIAL_YES                                  \n                      \n 001764 00031 QR    DS 0002 DSAT  ENTRY CHANGE_MODE           QR                                             \n                      \n 001765 00031 QR    DS 0003 DSAT  EXIT  CHANGE_MODE/OK        1F503030 , 00000001                            \n                      \n 001766 00031 QR    PG 0500 PGIS  ENTRY INQUIRE_CURRENT_PROGRAM                                              \n                      \n 001767 00031 QR    PG 0501 PGIS  EXIT  INQUIRE_CURRENT_PROGRAM/OK 2C88,20D00A20,ASMDEMO                     \n                      \n 001768 00031 QR    AP 0781 SRP   *EXC* ABEND_ASRA            ASMDEMO,0000019C,CICS                          \n                      \n 001769 00031 QR    ME 0301 MEME  ENTRY SEND_MESSAGE          1,AP0001,0005D370 , 00000008,0005D378 ,\n 00000004,0005D368 , 00000008", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "70775ec03789-1", "text": "00000004,0005D368 , 00000008 \n 001770 00031 QR    SM 0301 SMGF  ENTRY GETMAIN               1F44A0D4 , 00000018,1000,YES,KESTACKS          \n                      \n 001771 00031 QR    SM 0302 SMGF  EXIT  GETMAIN/OK            0004A000                                       \n                      \n 001772 00031 QR    KE 0101 KETI  ENTRY INQ_LOCAL_DATETIME_DECIMAL                                           \n                      \n 001773 00031 QR    KE 0102 KETI  EXIT  INQ_LOCAL_DATETIME_DECIMAL/OK 11172004,143250,063745,MMDDYYYY        \n                      \n 001774 00031 QR    KE 0401 KEGD  ENTRY INQUIRE_KERNEL                                                       \n                      \n 001775 00031 QR    KE 0402 KEGD  EXIT  INQUIRE_KERNEL/OK     A11IC9N3,CICS                                  \n                      \n 001776 00031 QR    ME 0312 MEME  EVENT ISSUE-MVS-GETMAIN                                                    \n                      \n 001777 00031 QR    ME 0313 MEME  EVENT MVS-GETMAIN-COMPLETE                                                 \n                      \n 001778 00031 QR    ME FF45 MEWS  *EXC* SYMREC-ERROR                                                         \n                      \n 001779 00031 QR    ME FF00 SUWT  ENTRY SEND_DIRECT           2000292B , 00000002,20002B0C ,\n 00000001,DFHAP0001 A11IC9N3           \n 001780 00031 QR    ME FF02 SUWT  EVENT BEFORE-MVS-WTO", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "70775ec03789-2", "text": "PF1 Help       2            3 End         4 Mask      5 Repeat     6 Return On                              \n                      \n PF7 Backward   8 Forward    9 All Trace  10 Left     11 Right     12 Retrieve\n15. Specify TOP in the command line, as shown in Step 15, and press Enter to position the display at the beginning of the\ntrace.\n16. Press PF4 and specify a filter selection mask to show only EIP entries for task 00031 as shown next.\n 1321", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ed894f8b7751-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n--------------  CA SymDump for CICS   FORMATTED TRACE TABLE              \n TASK  TCB   DM ID   MOD   TYPE OR DATA                                    \n 00031 *     *  *    EIP   *                                                   \n                                                                              \n \n \n \n \n PF1 Help       2            3 End         4           5            6        \n PF7            8            9 All Trace  10          11           12          \n17. Press PF3 to activate the filter selection mask.\n--------------  CA SymDump for CICS   FORMATTED TRACE TABLE  --------------                                  \n                  \n COMMAND ===>                                             MODE: A SCROLL: PAGE                               \n                      \n 001750 00031 QR    AP 00E1 EIP   ENTRY HANDLE-CONDITION                                 \n 0004,00140488 ...h,08000204 ....         \n 001753 00031 QR    AP 00E1 EIP   EXIT  HANDLE-CONDITION      OK                         \n 00F4,00000000 ....,00000204 ....         \n 001754 00031 QR    AP 00E1 EIP   ENTRY READQ-TS                                         \n 0004,00140488 ...h,08000A04 ....         \n 001759 00031 QR    AP 00E1 EIP   EXIT  READQ-TS              OK                         \n 00F4,00000000 ....,00000A04 ....         \n 001824 00031 QR    AP 00E1 EIP   ENTRY ADDRESS                                          \n 0004,1F264270 ....,08000202 ...      *\n 001825 00031 QR    AP 00E1 EIP   EXIT  ADDRESS               OK                         \n 00F4,00000000 ....,00000202 ....", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ed894f8b7751-1", "text": "00F4,00000000 ....,00000202 ....         \n 001826 00031 QR    AP 00E1 EIP   ENTRY INQUIRE-SYSTEM                                   \n 0004,1F264270 ....,08005402 ....         \n 001833 00031 QR    AP 00E1 EIP   EXIT  INQUIRE-SYSTEM        OK                         \n 00F4,00000000 ....,00005402 ....         \n 001834 00031 QR    AP 00E1 EIP   ENTRY LOAD                                             \n 0004,1F264270 ....,08000E06 ....         \n 001864 00031 QR    AP 00E1 EIP   ENTRY RETURN                                           \n 0004,20100018 ....,08000E08 ....         \n 001952 00031 QR    AP 00E1 EIP   EXIT  LOAD                  OK                         \n 00F4,00000000 ....,00000E06 ....         \n 001953 00031 QR    AP 00E1 EIP   ENTRY GETMAIN                                          \n 0004,1F264270 ....,08000C02 ....         \n 001956 00031 QR    AP 00E1 EIP   EXIT  GETMAIN               OK                         \n 00F4,00000000 ....,00000C02 ....         \n 001957 00031 QR    AP 00E1 EIP   ENTRY LOAD                                             \n 0004,1F264270 ....,08000E06 ....\n 001964 00031 QR    AP 00E1 EIP   EXIT  LOAD                  OK                         \n 00F4,00000000 ....,00000E06 ....         \n 001965 00031 QR    AP 00E1 EIP   ENTRY GETMAIN", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ed894f8b7751-2", "text": "001965 00031 QR    AP 00E1 EIP   ENTRY GETMAIN                                          \n 0004,1F264270 ....,08000C02 ....         \n 001968 00031 QR    AP 00E1 EIP   EXIT  GETMAIN               OK                         \n 00F4,00000000 ....,00000C02 ....         \n 001969 00031 QR    AP 00E1 EIP   ENTRY GETMAIN                                          \n 0004,1F264270 ....,08000C02 ....         \n 1322", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7fb011091bf6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 001972 00031 QR    AP 00E1 EIP   EXIT  GETMAIN               OK                         \n 00F4,00000000 ....,00000C02 ....         \n 001973 00031 QR    AP 00E1 EIP   ENTRY PUSH                                             \n 0004,1F264270 ....,0800020C ....         \n 001978 00031 QR    AP 00E1 EIP   EXIT  PUSH                  OK                         \n 00F4,00000000 ....,0000020C ....         \n                                                                                                             \n                      \n PF1 Help       2            3 End         4 Mask      5 Repeat     6 Return On                              \n                      \n PF7 Backward   8 Forward    9 All Trace  10 Left     11 Right     12 Retrieve  \n18. Press  PF9  to turn off filtering and to display all the entries at this point. As shown in the following screen, there was a\nREADQ for QID DEMAG001 followed by a Program Check in program ASMDEMO.\n19. Press PF6 to show the Program name for all programs that made trace entries. You can see that ASMDEMO issued\nthe READQ request.\n--------------  CA SymDump for CICS   FORMATTED TRACE TABLE  --------------          \n \n COMMAND ===>                                             MODE: A SCROLL: PAGE                               \n                      \n 001750 00031 QR    AP 00E1 EIP   ENTRY HANDLE-CONDITION                                 \n 0004,00140488 ...h,08000 ASMDEMO +000000A0\n 001751 00031 QR    PG 0700 PGHM  ENTRY SET_CONDITIONS", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7fb011091bf6-1", "text": "001751 00031 QR    PG 0700 PGHM  ENTRY SET_CONDITIONS       \n 20D033BD,20D033BA,001404F4,00140488,ASSEMBLER,80,AMO DFHEEI  +00000328\n 001752 00031 QR    PG 0701 PGHM  EXIT  SET_CONDITIONS/OK     0                                              \n      DFHEEI  +00000328\n 001753 00031 QR    AP 00E1 EIP   EXIT  HANDLE-CONDITION      OK                         \n 00F4,00000000 ....,00000 DFHEEI  +00000328\n 001754 00031 QR    AP 00E1 EIP   ENTRY READQ-TS                                         \n 0004,00140488 ...h,08000 ASMDEMO +000000CC\n 001755 00031 QR    TS 0C01 TSMB  ENTRY MATCH                 DEMAU010                                       \n      DFHEITS +00000292\n 001756 00031 QR    TS 0C02 TSMB  EXIT  MATCH/OK              ,,,DEMAU010,,00000000,,ANY,NO,NO               \n      DFHEITS +00000292\n 001757 00031 QR    TS 0201 TSQR  ENTRY READ_INTO             DEMAU010,00140610 , 00000000 , 00000024,1,EXEC \n      DFHEITS +0000097A\n 001758 00031 QR    TS 0202 TSQR  EXIT  READ_INTO/OK          00140610 , 00000024 , 00000024,1,NO            \n      DFHEITS +0000097A\n 001759 00031 QR    AP 00E1 EIP   EXIT  READQ-TS              OK", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7fb011091bf6-2", "text": "00F4,00000000 ....,00000 DFHAIP  +000008C2\n 001760 00031 QR    AP 1942 APLI  *EXC* Program-Check        \n START_PROGRAM,ASMDEMO,CEDF,FULLAPI,EXEC,NO,200C70D0, DFHPGDM +0000C618\n 001761 00031 QR    AP 0790 SRP   *EXC* PROGRAM_CHECK                                                        \n      DFHSRP  +0000050E\n 001762 00031 QR    DS 0010 DSBR  ENTRY INQUIRE_TASK                                                         \n      DFHSRP  +00002F08\n 001763 00031 QR    DS 0011 DSBR  EXIT  INQUIRE_TASK/OK       ESSENTIAL_YES                                  \n      DFHSRP  +00002F08\n 001764 00031 QR    DS 0002 DSAT  ENTRY CHANGE_MODE           QR                                             \n      DFHSRP  +00002F54\n 001765 00031 QR    DS 0003 DSAT  EXIT  CHANGE_MODE/OK        1F503030 , 00000001                            \n      DFHSRP  +00002F54\n 1323", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9a114cd380b7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 001766 00031 QR    PG 0500 PGIS  ENTRY INQUIRE_CURRENT_PROGRAM                                              \n      DFHSRP  +000026DA\n 001767 00031 QR    PG 0501 PGIS  EXIT  INQUIRE_CURRENT_PROGRAM/OK 2C88,20D00A20,ASMDEMO                     \n      DFHSRP  +000026DA\n 001768 00031 QR    AP 0781 SRP   *EXC* ABEND_ASRA            ASMDEMO,0000019C,CICS                          \n      DFHSRP  +0000050E\n 001769 00031 QR    ME 0301 MEME  ENTRY SEND_MESSAGE          1,AP0001,0005D370 , 00000008,0005D378 ,\n 00000004,000 DFHSRP  +00003C72\n 001770 00031 QR    SM 0301 SMGF  ENTRY GETMAIN               1F44A0D4 , 00000018,1000,YES,KESTACKS          \n      DFHSIP  +00054454\n                                                                                                             \n                      \n PF1 Help       2            3 End         4 Mask      5 Repeat     6 Return Off                             \n                      \n PF7 Backward   8 Forward    9 Filter     10 Left     11 Right     12 Retrieve\n20. Type HILITE ASMDEMO  to highlight all entries containing ASMDEMO.\n21. Type F HILITE FIRST   to locate the first HIGHLIGHTED entry in the trace.\n--------------  CA SymDump for CICS   FORMATTED TRACE TABLE  --------------                                  \n                  \n COMMAND ===>                                             MODE: A SCROLL: PAGE                               \n                      \n CASD6247 HILITE found in entry 001456", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9a114cd380b7-1", "text": "CASD6247 HILITE found in entry 001456                                                                       \n                      \n 001456 00030 QR    AP 1791 TFXM  EXIT  BIND_XM_CLIENT/OK     YES,ASMDEMO,YES                                \n      DFHSIP  +0003F7A6\n 001457 00030 QR    AP 0590 APXM  ENTRY RMI_START_OF_TASK                                                    \n      DFHSIP  +0003F83E\n 001458 00030 QR    AP 2520 ERM   ENTRY CALL-TRUES-FOR-TASK-START                                            \n      DFHAPXM +00000BAA\n 001459 00030 QR    SM 0301 SMGF  ENTRY GETMAIN               1F44A0D4 , 00000018,1000,YES,KESTACKS          \n      DFHCSA  +00001894\n 001460 00030 QR    SM 0302 SMGF  EXIT  GETMAIN/OK            0004A000                                       \n      DFHCSA  +00001894\n 001461 00030 QR    AP F000 XCP   ENTRY ENQ                                                                  \n      DFHERM  +00004B3A\n 001462 00030 QR    NQ 0301 NQED  ENTRY ENQUEUE               1F551200,0005D094 , 00000004,YES,UOW,..-.      \n      DFHKCP  +000003D0\n 001463 00030 QR    NQ 0302 NQED  EXIT  ENQUEUE/OK            NO                                             \n      DFHKCP  +000003D0\n 001464 00030 QR    AP F001 XCP   EXIT  ENQ                                                                  \n      DFHERM  +00004B3A", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9a114cd380b7-2", "text": "DFHERM  +00004B3A\n 001465 00030 QR    SM 0201 SMAD  ENTRY ADD_SUBPOOL           80,8,0,IN25STRU,DOMAIN,FIXED,NO,BELOW,YES      \n      DFHERM  +00004C4E\n 001466 00030 QR    CC 2010 CCCC  ENTRY GET                   20001851 , 00000000 , 00000010,SMSUBPOL,IN25STRU\n     DFHSIP  +000E8922\n 001467 00030 QR    DS 0004 DSSR  ENTRY WAIT_MVS              CCVSAMWT,1F2C14C0,NO,IO,ASYNRESP               \n      DFHSIP  +0006C760\n 001468 00030 QR    DS 0005 DSSR  EXIT  WAIT_MVS/OK                                                          \n      DFHSIP  +0006C760\n 001469 00030 QR    CC 2050 CCCC  EXIT  GET/EXCEPTION         RECORD_NOT_FOUND,20001851 , 00000000 , 00000010\n      DFHSIP  +000E8922\n 1324", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bd035523e4d1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 001470 00030 QR    LM 0003 LMLM  ENTRY ADD_LOCK              SUBPOOL                                        \n      DFHSIP  +000E9C06\n 001471 00030 QR    LM 0004 LMLM  EXIT  ADD_LOCK/OK           1F495448                                       \n      DFHSIP  +000E9C06\n 001472 00030 QR    LM 0003 LMLM  ENTRY UNLOCK                1F495448,EXCLUSIVE                             \n      DFHSIP  +000E9C52\n 001473 00030 QR    LM 0004 LMLM  EXIT  UNLOCK/OK                                                            \n      DFHSIP  +000E9C52\n 001474 00030 QR    SM 0202 SMAD  EXIT  ADD_SUBPOOL/OK        1F484C14 , 0000013D                            \n      DFHERM  +00004C4E\n 001475 00030 QR    AP F000 XCP   ENTRY DEQ                                                                  \n      DFHERM  +00004C96\n 001476 00030 QR    NQ 0301 NQED  ENTRY DEQUEUE               1F551200,0005D094 , 00000004,UOW,..-.          \n      DFHKCP  +00000546\n                                                                                                             \n                      \n PF1 Help       2            3 End         4 Mask      5 Repeat     6 Return Off                             \n                      \n PF7 Backward   8 Forward    9 Filter     10 Left     11 Right     12 Retrieve  \n22. Type TOP on the command line and press Enter to reposition the trace.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bd035523e4d1-1", "text": "22. Type TOP on the command line and press Enter to reposition the trace.\n23. Press PF4 and specify a filter selection mask to show only READQ entries for task 00031as shown next.\n--------------  CA SymDump for CICS   FORMATTED TRACE TABLE  -           \n TASK  TCB   DM ID   MOD   TYPE OR DATA                                        \n 00031 *     *  *    EIP   READQ                                              \n \n \n \n \n                                                                              \n PF1 Help       2            3 End         4           5            6         \n PF7            8            9 All Trace  10          11           12  \n24. Press PF9 to activate the filter.\n--------------  CA SymDump for CICS   FORMATTED TRACE TABLE  --------------                                  \n                  \n COMMAND ===>                                             MODE: A SCROLL: PAGE                               \n                      \n CASD6229 Bottom of data                                                                                     \n                      \n 001754 00031 QR    AP 00E1 EIP   ENTRY READQ-TS                                         \n 0004,00140488 ...h,08000 ASMDEMO +000000CC\n 001759 00031 QR    AP 00E1 EIP   EXIT  READQ-TS              OK                         \n 00F4,00000000 ....,00000 DFHAIP  +000008C2\n                                                                                       \n \n \n \n PF1 Help       2            3 End         4 Mask      5 Repeat     6 Return Off                             \n                      \n PF7 Backward   8 Forward    9 All Trace  10 Left     11 Right     12 Retrieve \n 1325", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1e9914328be4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n25. Press  PF9  to turn off the filter.\n--------------  CA SymDump for CICS   FORMATTED TRACE TABLE  --------------                                  \n                  \nCOMMAND ===>                                             MODE: A SCROLL: PAGE                                \n                     \n001754 00031 QR    AP 00E1 EIP   ENTRY READQ-TS                                         \n 0004,00140488 ...h,08000 ASMDEMO +000000CC\n001755 00031 QR    TS 0C01 TSMB  ENTRY MATCH                 DEMAU010                                        \n     DFHEITS +00000292\n001756 00031 QR    TS 0C02 TSMB  EXIT  MATCH/OK              ,,,DEMAU010,,00000000,,ANY,NO,NO                \n     DFHEITS +00000292\n001757 00031 QR    TS 0201 TSQR  ENTRY READ_INTO             DEMAU010,00140610 , 00000000 , 00000024,1,EXEC  \n     DFHEITS +0000097A\n001758 00031 QR    TS 0202 TSQR  EXIT  READ_INTO/OK          00140610 , 00000024 , 00000024,1,NO             \n     DFHEITS +0000097A\n001759 00031 QR    AP 00E1 EIP   EXIT  READQ-TS              OK                         \n 00F4,00000000 ....,00000 DFHAIP  +000008C2\n001760 00031 QR    AP 1942 APLI  *EXC* Program-Check        \n START_PROGRAM,ASMDEMO,CEDF,FULLAPI,EXEC,NO,200C70D0, DFHPGDM +0000C618", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1e9914328be4-1", "text": "001761 00031 QR    AP 0790 SRP   *EXC* PROGRAM_CHECK                                                         \n     DFHSRP  +0000050E\n001762 00031 QR    DS 0010 DSBR  ENTRY INQUIRE_TASK                                                          \n     DFHSRP  +00002F08\n001763 00031 QR    DS 0011 DSBR  EXIT  INQUIRE_TASK/OK       ESSENTIAL_YES                                   \n     DFHSRP  +00002F08\n001764 00031 QR    DS 0002 DSAT  ENTRY CHANGE_MODE           QR                                              \n     DFHSRP  +00002F54\n001765 00031 QR    DS 0003 DSAT  EXIT  CHANGE_MODE/OK        1F503030 , 00000001                             \n     DFHSRP  +00002F54\n001766 00031 QR    PG 0500 PGIS  ENTRY INQUIRE_CURRENT_PROGRAM                                               \n     DFHSRP  +000026DA\n001767 00031 QR    PG 0501 PGIS  EXIT  INQUIRE_CURRENT_PROGRAM/OK 2C88,20D00A20,ASMDEMO                      \n     DFHSRP  +000026DA\n001768 00031 QR    AP 0781 SRP   *EXC* ABEND_ASRA            ASMDEMO,0000019C,CICS                           \n     DFHSRP  +0000050E\n001769 00031 QR    ME 0301 MEME  ENTRY SEND_MESSAGE          1,AP0001,0005D370 , 00000008,0005D378 ,\n 00000004,000 DFHSRP  +00003C72", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1e9914328be4-2", "text": "00000004,000 DFHSRP  +00003C72\n001770 00031 QR    SM 0301 SMGF  ENTRY GETMAIN               1F44A0D4 , 00000018,1000,YES,KESTACKS           \n     DFHSIP  +00054454\n001771 00031 QR    SM 0302 SMGF  EXIT  GETMAIN/OK            0004A000                                        \n     DFHSIP  +00054454\n001772 00031 QR    KE 0101 KETI  ENTRY INQ_LOCAL_DATETIME_DECIMAL                                            \n     DFHSIP  +000821F4\n001773 00031 QR    KE 0102 KETI  EXIT  INQ_LOCAL_DATETIME_DECIMAL/OK 11172004,143250,063745,MMDDYYYY         \n     DFHSIP  +000821F4\n001774 00031 QR    KE 0401 KEGD  ENTRY INQUIRE_KERNEL                                                        \n     DFHSIP  +000822D6\n \nPF1 Help       2            3 End         4 Mask      5 Repeat     6 Return Off                              \n                     \nPF7 Backward   8 Forward    9 Filter     10 Left     11 Right     12 Retrieve\n26. Type L 1750  to position the trace to line 1750 and press Enter.\n 1326", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0dc32c68842d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n--------------  CA SymDump for CICS   FORMATTED TRACE TABLE  --------------                                  \n                  \n COMMAND ===>                                             MODE: A SCROLL: PAGE                               \n                      \n 001750 00031 QR    AP 00E1 EIP   ENTRY HANDLE-CONDITION                                 \n 0004,00140488 ...h,08000 ASMDEMO +000000A0\n 001751 00031 QR    PG 0700 PGHM  ENTRY SET_CONDITIONS       \n 20D033BD,20D033BA,001404F4,00140488,ASSEMBLER,80,AMO DFHEEI  +00000328\n 001752 00031 QR    PG 0701 PGHM  EXIT  SET_CONDITIONS/OK     0                                              \n      DFHEEI  +00000328\n 001753 00031 QR    AP 00E1 EIP   EXIT  HANDLE-CONDITION      OK                         \n 00F4,00000000 ....,00000 DFHEEI  +00000328\n 001754 00031 QR    AP 00E1 EIP   ENTRY READQ-TS                                         \n 0004,00140488 ...h,08000 ASMDEMO +000000CC\n 001755 00031 QR    TS 0C01 TSMB  ENTRY MATCH                 DEMAU010                                       \n      DFHEITS +00000292\n 001756 00031 QR    TS 0C02 TSMB  EXIT  MATCH/OK              ,,,DEMAU010,,00000000,,ANY,NO,NO               \n      DFHEITS +00000292\n 001757 00031 QR    TS 0201 TSQR  ENTRY READ_INTO             DEMAU010,00140610 , 00000000 , 00000024,1,EXEC", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0dc32c68842d-1", "text": "DFHEITS +0000097A\n 001758 00031 QR    TS 0202 TSQR  EXIT  READ_INTO/OK          00140610 , 00000024 , 00000024,1,NO            \n      DFHEITS +0000097A\n 001759 00031 QR    AP 00E1 EIP   EXIT  READQ-TS              OK                         \n 00F4,00000000 ....,00000 DFHAIP  +000008C2\n 001760 00031 QR    AP 1942 APLI  *EXC* Program-Check        \n START_PROGRAM,ASMDEMO,CEDF,FULLAPI,EXEC,NO,200C70D0, DFHPGDM +0000C618\n 001761 00031 QR    AP 0790 SRP   *EXC* PROGRAM_CHECK                                                        \n      DFHSRP  +0000050E\n 001762 00031 QR    DS 0010 DSBR  ENTRY INQUIRE_TASK                                                         \n      DFHSRP  +00002F08\n 001763 00031 QR    DS 0011 DSBR  EXIT  INQUIRE_TASK/OK       ESSENTIAL_YES                                  \n      DFHSRP  +00002F08\n 001764 00031 QR    DS 0002 DSAT  ENTRY CHANGE_MODE           QR                                             \n      DFHSRP  +00002F54\n 001765 00031 QR    DS 0003 DSAT  EXIT  CHANGE_MODE/OK        1F503030 , 00000001                            \n      DFHSRP  +00002F54\n 001766 00031 QR    PG 0500 PGIS  ENTRY INQUIRE_CURRENT_PROGRAM                                              \n      DFHSRP  +000026DA", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0dc32c68842d-2", "text": "DFHSRP  +000026DA\n 001767 00031 QR    PG 0501 PGIS  EXIT  INQUIRE_CURRENT_PROGRAM/OK 2C88,20D00A20,ASMDEMO                     \n      DFHSRP  +000026DA\n 001768 00031 QR    AP 0781 SRP   *EXC* ABEND_ASRA            ASMDEMO,0000019C,CICS                          \n      DFHSRP  +0000050E\n 001769 00031 QR    ME 0301 MEME  ENTRY SEND_MESSAGE          1,AP0001,0005D370 , 00000008,0005D378 ,\n 00000004,000 DFHSRP  +00003C72\n 001770 00031 QR    SM 0301 SMGF  ENTRY GETMAIN               1F44A0D4 , 00000018,1000,YES,KESTACKS          \n      DFHSIP  +00054454\n                                                                                                             \n                      \n PF1 Help       2            3 End         4 Mask      5 Repeat     6 Return Off                             \n             \n PF7 Backward   8 Forward    9 Filter     10 Left     11 Right     12 Retrieve\n 1327", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "33d72c5568b9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n27. Type MODE S  on the command line to change the mode of the trace to short. Now you can see the times that entries\nwere made.\n--------------  CA SymDump for CICS   FORMATTED TRACE TABLE  --------------                                  \n                  \n COMMAND ===>                                             MODE: S SCROLL: PAGE                               \n                      \n 001750 00031 QR    AP 00E1 EIP   ENTRY HANDLE-CONDITION                     REQ(0004) FIELD-A(00140488 ...h)\n FIEL ASMDEMO +000000A0\n                                                                                    RET-A0D00AE8\n 14:32:50.8825789560 00.0000021406 =\n 001751 00031 QR    PG 0700 PGHM  ENTRY SET_CONDITIONS IDENTIFIERS(20D033BD) LABELS_FLAGS(20D033BA)\n LABELS(001404F DFHEEI  +00000328\n                                        (00140488) LANGUAGE(ASSEMBLER) CURRENT_EXECUTION_KEY(80)\n AMODE(AMODE31)                    \n                                                                                    RET-9FC19028\n 14:32:50.8825832685 00.0000043125 =\n 001752 00031 QR    PG 0701 PGHM  EXIT  SET_CONDITIONS/OK FASTPATH_FLAGS(0)         RET-9FC19028\n 14:32:50.88258664 DFHEEI  +00000328\n 001753 00031 QR    AP 00E1 EIP   EXIT  HANDLE-CONDITION OK                  REQ(00F4) FIELD-A(00000000 ....)\n FIEL DFHEEI  +00000328\n                                                                                    RET-9FC19028\n 14:32:50.8825877060 00.0000010625 =", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "33d72c5568b9-1", "text": "14:32:50.8825877060 00.0000010625 =\n 001754 00031 QR    AP 00E1 EIP   ENTRY READQ-TS                             REQ(0004) FIELD-A(00140488 ...h)\n FIEL ASMDEMO +000000CC\n                                                                                    RET-A0D00B14\n 14:32:50.8825885185 00.0000008125 =\n 001755 00031 QR    TS 0C01 TSMB  ENTRY MATCH QUEUE_NAME(DEMAU010)                  RET-9F92D9E2\n 14:32:50.88259261 DFHEITS +00000292\n 001756 00031 QR    TS 0C02 TSMB  EXIT  MATCH/OK TSMODEL_NAME() PREFIX() REMOTE_PREFIX() REMOTE_NAME(DEMAU010)\n POO DFHEITS +00000292\n                                        (00000000) SYSID() MAIN(ANY) RECOVERABLE(NO) SECURITY(NO)            \n                      \n                                                                                    RET-9F92D9E2\n 14:32:50.8825972685 00.0000046562 =\n 001757 00031 QR    TS 0201 TSQR  ENTRY READ_INTO QUEUE_NAME(DEMAU010) ITEM_BUFFER(00140610 , 00000000 ,\n 00000024) DFHEITS +0000097A\n                                        (EXEC)                                      RET-9F92E0CA\n 14:32:50.8825997373 00.0000024687 =\n 001758 00031 QR    TS 0202 TSQR  EXIT  READ_INTO/OK ITEM_BUFFER(00140610 , 00000024 , 00000024)\n TOTAL_ITEMS(1) FM DFHEITS +0000097A", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "33d72c5568b9-2", "text": "TOTAL_ITEMS(1) FM DFHEITS +0000097A\n                                                                                    RET-9F92E0CA\n 14:32:50.8826042685 00.0000045312 =\n 001759 00031 QR    AP 00E1 EIP   EXIT  READQ-TS OK                          REQ(00F4) FIELD-A(00000000 ....)\n FIEL DFHAIP  +000008C2\n                                                                                    RET-800828C2\n 14:32:50.8826051904 00.0000009218 =\n 001760 00031 QR    AP 1942 APLI  *EXC* Program-Check   FUNCTION(START_PROGRAM) PROGRAM(ASMDEMO)\n CEDF_STATUS(CEDF) DFHPGDM +0000C618\n                                                                                                             \n              \n PF1 Help       2            3 End         4 Mask      5 Repeat     6 Return Off                             \n         \n 1328", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ab56d7568795-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n PF7 Backward   8 Forward    9 Filter     10 Left     11 Right     12 Retrieve  \n28. Tab to the MODE field to the right of the command line. Type F to place the trace into FULL mode and press Enter.\n--------------  CA SymDump for CICS   FORMATTED TRACE TABLE  --------------                                  \n                  \n COMMAND ===>                                             MODE: F SCROLL: PAGE                               \n                      \n 001750 AP 00E1 EIP ENTRY HANDLE-CONDITION                    REQ(0004) FIELD-A(00140488 ...h) FIELD-\nB(08000204 .. ASMDEMO +000000A0\n        TASK-00031 KE_NUM-0039 TCB-QR   /007AAD08 RET-A0D00AE8 TIME-14:32:50.8825789560 INTERVAL-00.0000021406\n        =001750=     \n 001751 PG 0700 PGHM  ENTRY - FUNCTION(SET_CONDITIONS) IDENTIFIERS(20D033BD) LABELS_FLAGS(20D033BA)\n LABELS(001404F DFHEEI  +00000328\n             (00140488) LANGUAGE(ASSEMBLER) CURRENT_EXECUTION_KEY(80) AMODE(AMODE31)                         \n                      \n        TASK-00031 KE_NUM-0039 TCB-QR   /007AAD08 RET-9FC19028 TIME-14:32:50.8825832685 INTERVAL-00.0000043125\n        =001751=     \n          1-0000  00500000 0000009A 00000000 00000000  BC782200 00000000 01000100 20D033BD \n *.&...........................}..*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ab56d7568795-1", "text": "*.&...........................}..*     \n            0020  20D033BA 00E10478 0005D3A0 00000012  001404F4 00140488 01807F30 0005D5A4 \n *.}........L........4...h..\"...Nu*     \n            0040  20D033B8 001404F0 20000F02 01404040                                       *.}.....0.....   \n                *     \n 001752 PG 0701 PGHM  EXIT  - FUNCTION(SET_CONDITIONS) RESPONSE(OK) FASTPATH_FLAGS(0)                        \n      DFHEEI  +00000328\n        TASK-00031 KE_NUM-0039 TCB-QR   /007AAD08 RET-9FC19028 TIME-14:32:50.8825866435 INTERVAL-00.0000033750\n        =001752=     \n          1-0000  00500000 0000009A 00000000 00000000  BC782200 00000000 01000100 20D033BD \n *.&...........................}..*     \n            0020  20D033BA 00E10478 0005D3A0 00000012  001404F4 00140488 01807F30 0005D5A4 \n *.}........L........4...h..\"...Nu*     \n            0040  20D033B8 00140000 20000F02 01404040                                       *.}...........   \n                *", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ab56d7568795-2", "text": "*     \n \n        TASK-00031 KE_NUM-0039 TCB-QR   /007AAD08 RET-9FC19028 TIME-14:32:50.8825877060 INTERVAL-00.0000010625\n        =001753=     \n 001754 AP 00E1 EIP ENTRY READQ-TS                            REQ(0004) FIELD-A(00140488 ...h) FIELD-\nB(08000A04 .. ASMDEMO +000000CC\n        TASK-00031 KE_NUM-0039 TCB-QR   /007AAD08 RET-A0D00B14 TIME-14:32:50.8825885185 INTERVAL-00.0000008125\n        =001754=     \n 001755 TS 0C01 TSMB  ENTRY - FUNCTION(MATCH) QUEUE_NAME(DEMAU010)                                           \n      DFHEITS +00000292\n        TASK-00031 KE_NUM-0039 TCB-QR   /007AAD08 RET-9F92D9E2 TIME-14:32:50.8825926123 INTERVAL-00.0000040937\n        =001755=     \n          1-0000  00800000 0000016F 00000000 00000000  BFF70000 00000000 05000000 00000000 \n *.......?.........7..............*     \n            0020  00000000 C4C5D4C1 E4F0F1F0 40404040  40404040 00000000 00000000 00000000  *....DEMAU010    \n    ............*     \n                                                                                                             \n                      \n PF1 Help       2            3 End         4 Mask      5 Repeat     6 Return Off", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ab56d7568795-3", "text": "PF7 Backward   8 Forward    9 Filter     10 Left     11 Right     12 Retrieve  \n 1329", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "27b3d36d4f88-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n29. Tab to the Mode field and type A to place the trace back into ABBREVIATED mode and press Enter.\n--------------  CA SymDump for CICS   FORMATTED TRACE TABLE  --------------                                  \n                  \n COMMAND ===>                                             MODE: A SCROLL: PAGE                               \n                      \n 001750 00031 QR    AP 00E1 EIP   ENTRY HANDLE-CONDITION                                 \n 0004,00140488 ...h,08000 ASMDEMO +000000A0\n 001751 00031 QR    PG 0700 PGHM  ENTRY SET_CONDITIONS       \n 20D033BD,20D033BA,001404F4,00140488,ASSEMBLER,80,AMO DFHEEI  +00000328\n 001752 00031 QR    PG 0701 PGHM  EXIT  SET_CONDITIONS/OK     0                                              \n      DFHEEI  +00000328\n 001753 00031 QR    AP 00E1 EIP   EXIT  HANDLE-CONDITION      OK                         \n 00F4,00000000 ....,00000 DFHEEI  +00000328\n 001754 00031 QR    AP 00E1 EIP   ENTRY READQ-TS                                         \n 0004,00140488 ...h,08000 ASMDEMO +000000CC\n 001755 00031 QR    TS 0C01 TSMB  ENTRY MATCH                 DEMAU010                                       \n      DFHEITS +00000292\n 001756 00031 QR    TS 0C02 TSMB  EXIT  MATCH/OK              ,,,DEMAU010,,00000000,,ANY,NO,NO               \n      DFHEITS +00000292", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "27b3d36d4f88-1", "text": "DFHEITS +00000292\n 001757 00031 QR    TS 0201 TSQR  ENTRY READ_INTO             DEMAU010,00140610 , 00000000 , 00000024,1,EXEC \n      DFHEITS +0000097A\n 001758 00031 QR    TS 0202 TSQR  EXIT  READ_INTO/OK          00140610 , 00000024 , 00000024,1,NO            \n      DFHEITS +0000097A\n 001759 00031 QR    AP 00E1 EIP   EXIT  READQ-TS              OK                         \n 00F4,00000000 ....,00000 DFHAIP  +000008C2\n 001760 00031 QR    AP 1942 APLI  *EXC* Program-Check        \n START_PROGRAM,ASMDEMO,CEDF,FULLAPI,EXEC,NO,200C70D0, DFHPGDM +0000C618\n 001761 00031 QR    AP 0790 SRP   *EXC* PROGRAM_CHECK                                                        \n      DFHSRP  +0000050E\n 001762 00031 QR    DS 0010 DSBR  ENTRY INQUIRE_TASK                                                         \n      DFHSRP  +00002F08\n 001763 00031 QR    DS 0011 DSBR  EXIT  INQUIRE_TASK/OK       ESSENTIAL_YES                                  \n      DFHSRP  +00002F08\n 001764 00031 QR    DS 0002 DSAT  ENTRY CHANGE_MODE           QR                                             \n      DFHSRP  +00002F54\n 001765 00031 QR    DS 0003 DSAT  EXIT  CHANGE_MODE/OK        1F503030 , 00000001", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "27b3d36d4f88-2", "text": "DFHSRP  +00002F54\n 001766 00031 QR    PG 0500 PGIS  ENTRY INQUIRE_CURRENT_PROGRAM                                              \n      DFHSRP  +000026DA\n 001767 00031 QR    PG 0501 PGIS  EXIT  INQUIRE_CURRENT_PROGRAM/OK 2C88,20D00A20,ASMDEMO                     \n      DFHSRP  +000026DA\n 001768 00031 QR    AP 0781 SRP   *EXC* ABEND_ASRA            ASMDEMO,0000019C,CICS                          \n      DFHSRP  +0000050E\n 001769 00031 QR    ME 0301 MEME  ENTRY SEND_MESSAGE          1,AP0001,0005D370 , 00000008,0005D378 ,\n 00000004,000 DFHSRP  +00003C72\n 001770 00031 QR    SM 0301 SMGF  ENTRY GETMAIN               1F44A0D4 , 00000018,1000,YES,KESTACKS          \n      DFHSIP  +00054454\n                                                                                                             \n                      \n PF1 Help       2            3 End         4 Mask      5 Repeat     6 Return Off                             \n                      \n PF7 Backward   8 Forward    9 Filter     10 Left     11 Right     12 Retrieve \n 1330", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "037ec413621e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n30. Type L 1760  on the command line to position the trace to line 1760 and press Enter.\n--------------  CA SymDump for CICS   FORMATTED TRACE TABLE  --------------                                  \n                  \n COMMAND ===>                                             MODE: A SCROLL: PAGE                               \n                      \n 001760 00031 QR    AP 1942 APLI  *EXC* Program-Check        \n START_PROGRAM,ASMDEMO,CEDF,FULLAPI,EXEC,NO,200C70D0, DFHPGDM +0000C618\n 001761 00031 QR    AP 0790 SRP   *EXC* PROGRAM_CHECK                                                        \n      DFHSRP  +0000050E\n 001762 00031 QR    DS 0010 DSBR  ENTRY INQUIRE_TASK                                                         \n      DFHSRP  +00002F08\n 001763 00031 QR    DS 0011 DSBR  EXIT  INQUIRE_TASK/OK       ESSENTIAL_YES                                  \n      DFHSRP  +00002F08\n 001764 00031 QR    DS 0002 DSAT  ENTRY CHANGE_MODE           QR                                             \n      DFHSRP  +00002F54\n 001765 00031 QR    DS 0003 DSAT  EXIT  CHANGE_MODE/OK        1F503030 , 00000001                            \n      DFHSRP  +00002F54\n 001766 00031 QR    PG 0500 PGIS  ENTRY INQUIRE_CURRENT_PROGRAM                                              \n      DFHSRP  +000026DA\n 001767 00031 QR    PG 0501 PGIS  EXIT  INQUIRE_CURRENT_PROGRAM/OK 2C88,20D00A20,ASMDEMO                     \n      DFHSRP  +000026DA", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "037ec413621e-1", "text": "DFHSRP  +000026DA\n 001768 00031 QR    AP 0781 SRP   *EXC* ABEND_ASRA            ASMDEMO,0000019C,CICS                          \n      DFHSRP  +0000050E\n 001769 00031 QR    ME 0301 MEME  ENTRY SEND_MESSAGE          1,AP0001,0005D370 , 00000008,0005D378 ,\n 00000004,000 DFHSRP  +00003C72\n 001770 00031 QR    SM 0301 SMGF  ENTRY GETMAIN               1F44A0D4 , 00000018,1000,YES,KESTACKS          \n      DFHSIP  +00054454\n 001771 00031 QR    SM 0302 SMGF  EXIT  GETMAIN/OK            0004A000                                       \n      DFHSIP  +00054454\n 001772 00031 QR    KE 0101 KETI  ENTRY INQ_LOCAL_DATETIME_DECIMAL                                           \n      DFHSIP  +000821F4\n 001773 00031 QR    KE 0102 KETI  EXIT  INQ_LOCAL_DATETIME_DECIMAL/OK 11172004,143250,063745,MMDDYYYY        \n      DFHSIP  +000821F4\n 001774 00031 QR    KE 0401 KEGD  ENTRY INQUIRE_KERNEL                                                       \n      DFHSIP  +000822D6\n 001775 00031 QR    KE 0402 KEGD  EXIT  INQUIRE_KERNEL/OK     A11IC9N3,CICS                                  \n      DFHSIP  +000822D6\n 001776 00031 QR    ME 0312 MEME  EVENT ISSUE-MVS-GETMAIN", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "037ec413621e-2", "text": "DFHSRP  +00003C72\n 001777 00031 QR    ME 0313 MEME  EVENT MVS-GETMAIN-COMPLETE                                                 \n      DFHSRP  +00003C72\n 001778 00031 QR    ME FF45 MEWS  *EXC* SYMREC-ERROR                                                         \n      DFHSIP  +0007D68C\n 001779 00031 QR    ME FF00 SUWT  ENTRY SEND_DIRECT           2000292B , 00000002,20002B0C ,\n 00000001,DFHAP0001 A1 DFHSIP  +000875C8\n 001780 00031 QR    ME FF02 SUWT  EVENT BEFORE-MVS-WTO                                                       \n      DFHSIP  +000875C8\n                                                                                                             \n                      \n PF1 Help       2            3 End         4 Mask      5 Repeat     6 Return Off                             \n                      \n PF7 Backward   8 Forward    9 Filter     10 Left     11 Right     12 Retrieve\n 1331", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "07ddef965f39-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n31. Tab to line 001760 on the left of the screen, and type F to override this line only to FULL mode, and press Enter.\n--------------  CA SymDump for CICS   FORMATTED TRACE TABLE  --------------                                  \n                  \n COMMAND ===>                                             MODE: A SCROLL: PAGE                               \n                      \n 001760 AP 1942 APLI  *EXC* - Program-Check   FUNCTION(START_PROGRAM) PROGRAM(ASMDEMO) CEDF_STATUS(CEDF)\n EXECUTION DFHPGDM +0000C618\n             ENVIRONMENT_TYPE(EXEC) SYNCONRETURN(NO) LANGUAGE_BLOCK(200C70D0) COMMAREA(00000000 , 00000000)\n LINK_LEVEL(1)          \n             SYSEIB_REQUEST(NO)                                                                              \n                      \n        TASK-00031 KE_NUM-0039 TCB-QR   /007AAD08 RET-9F794B08 TIME-14:32:50.8915181123 INTERVAL-00.0089289218\n        =001760=     \n          1-0000  01A00000 000000DA 00000000 00000000  B81B4EA0 00000000 02000100 C1E2D4C4 \n *..................+.........ASMD*     \n            0020  C5D4D640 200E0AF8 0000007C 200E0AF8  9F13A501 01D00202 20D00A20 200C70D0 \n *EMO ...8...@...8..v..}...}.....}*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "07ddef965f39-1", "text": "*EMO ...8...@...8..v..}...}.....}*     \n            0040  00002C88 00000000 00000000 00000000  00000000 00013202 00029620 80095E5A \n *...h......................o...;!*     \n            0060  0005D388 00000000 20020E00 00000400  02FEC780 00007000 00008258 92FF7EC4 \n *..Lh..............G.......b.k.=D*     \n            0080  20001678 00095D68 20000990 00000000  E100C5D9 00000000 00000000 00000000 \n *......)...........ER............*     \n            00A0  80000000 0004D030 20000C60 0014005C  80096778 A0051850 0009677E 0004D030 \n *......}....-...*.......&...=..}.*     \n            00C0  1FFEC780 00095B72 00000000 00000000  000888C2 20000C60 000888D4 00000000  *..G...\n$...........hB...-..hM....*     \n            00E0  00099620 00000000 800513B0 00000001  1F4BF380 80097464 00000000 20001308 \n *..o...............3.............*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "07ddef965f39-2", "text": "*..o...............3.............*     \n            0100  000888C2 0014005C 1F5460A0 20000C60  20000E00 0004C030 00083284 00099620 \n *..hB...*..-....-......{....d..o.*     \n            0120  80095E5A 0005D388 0005D080 0004C030  800513B0 00000048 200FBAC0 000000B9  *..;!..Lh..}...\n{............{....*     \n            0140  BC229A0D C4377F4C 1A11E4E2 C9D3C4C1  F0F14BC1 F5F5E3E4 F0F1F022 9A0DC437 \n *....D.\"<..USILDA01.A55TU010...D.*     \n            0160  7F000100 20000F28 00000000 00000000  D8D9D8D9 00000000 00000000 00000000 \n *\"...............QRQR............*     \n            0180  00000001 00000001 00000000 00000000  00000000 00000000 00000000 01800080 \n *................................*     \n          2-0000  F0C3F761 C1D2C5C1 018400C7 0000FFFF  C4C6C8C1 D7D3C9F1 1F8C43C0 1F4BF380  *0C7/", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "07ddef965f39-3", "text": "AKEA.d.G....DFHAPLI1...{..3.*     \n            0020  0005D080 1FFEC780 00000001 00000000  FF850007 00000000 078D0000 A0D00BBC \n *..}...G..........e...........}..*     \n            0040  00060007 00000000 A0D00BBC 80000000  20D00B36 001404F0 A0D00A48 A0D01A48 \n *.........}.......}.....0.}...}..*     \n            0060  A0D02A48 000001D5 00000232 A0D03A48  00000000 00000000 20001760 001400D0 \n *.}.....N.....}.............-...}*     \n                                                                                                             \n                      \n PF1 Help       2            3 End         4 Mask      5 Repeat     6 Return Off                             \n                      \n PF7 Backward   8 Forward    9 Filter     10 Left     11 Right     12 Retrieve \n 1332", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4f5a1e0dbf68-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n32. Type RESET OVERRIDES to reset all overrides.\n--------------  CA SymDump for CICS FORMATTED TRACE TABLE  --------------                                    \n                \n COMMAND ===>                                             MODE: A SCROLL: PAGE                               \n                      \n 001760 00031 QR    AP 1942 APLI  *EXC* Program-Check        \n START_PROGRAM,ASMDEMO,CEDF,FULLAPI,EXEC,NO,200C70D0, DFHPGDM +0000C618\n 001761 00031 QR    AP 0790 SRP   *EXC* PROGRAM_CHECK                                                        \n      DFHSRP  +0000050E\n 001762 00031 QR    DS 0010 DSBR  ENTRY INQUIRE_TASK                                                         \n      DFHSRP  +00002F08\n 001763 00031 QR    DS 0011 DSBR  EXIT  INQUIRE_TASK/OK       ESSENTIAL_YES                                  \n      DFHSRP  +00002F08\n 001764 00031 QR    DS 0002 DSAT  ENTRY CHANGE_MODE           QR                                             \n      DFHSRP  +00002F54\n 001765 00031 QR    DS 0003 DSAT  EXIT  CHANGE_MODE/OK        1F503030 , 00000001                            \n      DFHSRP  +00002F54\n 001766 00031 QR    PG 0500 PGIS  ENTRY INQUIRE_CURRENT_PROGRAM                                              \n      DFHSRP  +000026DA\n 001767 00031 QR    PG 0501 PGIS  EXIT  INQUIRE_CURRENT_PROGRAM/OK 2C88,20D00A20,ASMDEMO                     \n      DFHSRP  +000026DA", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4f5a1e0dbf68-1", "text": "DFHSRP  +000026DA\n 001768 00031 QR    AP 0781 SRP   *EXC* ABEND_ASRA            ASMDEMO,0000019C,CICS                          \n      DFHSRP  +0000050E\n 001769 00031 QR    ME 0301 MEME  ENTRY SEND_MESSAGE          1,AP0001,0005D370 , 00000008,0005D378 ,\n 00000004,000 DFHSRP  +00003C72\n 001770 00031 QR    SM 0301 SMGF  ENTRY GETMAIN               1F44A0D4 , 00000018,1000,YES,KESTACKS          \n      DFHSIP  +00054454\n 001771 00031 QR    SM 0302 SMGF  EXIT  GETMAIN/OK            0004A000                                       \n      DFHSIP  +00054454\n 001772 00031 QR    KE 0101 KETI  ENTRY INQ_LOCAL_DATETIME_DECIMAL                                           \n      DFHSIP  +000821F4\n 001773 00031 QR    KE 0102 KETI  EXIT  INQ_LOCAL_DATETIME_DECIMAL/OK 11172004,143250,063745,MMDDYYYY        \n      DFHSIP  +000821F4\n 001774 00031 QR    KE 0401 KEGD  ENTRY INQUIRE_KERNEL                                                       \n      DFHSIP  +000822D6\n 001775 00031 QR    KE 0402 KEGD  EXIT  INQUIRE_KERNEL/OK     A11IC9N3,CICS                                  \n      DFHSIP  +000822D6\n 001776 00031 QR    ME 0312 MEME  EVENT ISSUE-MVS-GETMAIN", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4f5a1e0dbf68-2", "text": "DFHSRP  +00003C72\n 001777 00031 QR    ME 0313 MEME  EVENT MVS-GETMAIN-COMPLETE                                                 \n      DFHSRP  +00003C72\n 001778 00031 QR    ME FF45 MEWS  *EXC* SYMREC-ERROR                                                         \n      DFHSIP  +0007D68C\n 001779 00031 QR    ME FF00 SUWT  ENTRY SEND_DIRECT           2000292B , 00000002,20002B0C ,\n 00000001,DFHAP0001 A1 DFHSIP  +000875C8\n 001780 00031 QR    ME FF02 SUWT  EVENT BEFORE-MVS-WTO                                                       \n      DFHSIP  +000875C8\n                                                                                                             \n               \n PF1 Help       2            3 End         4 Mask      5 Repeat     6 Return Off                       \n PF7 Backward   8 Forward    9 Filter     10 Left     11 Right     12 Retrieve\n33. Type RESET HILITE  to reset all HILIGHTS.\n 1333", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d78174c109bf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n34. Press  PF3  End Trace to exit the Formatted Trace Table facility. Use PF3 again to exit the menus.\nUsing InterTest for CICS to Find Errors\nIf you also have InterTest for CICS, you can use it to locate errors. This article explains how to locate errors using\nInterTest for CICS.\nThe example here lets you find and correct the error without re-executing the program. However, sometimes you will want\nto monitor the program with InterTest for CICS to learn more about what caused the error. You can turn monitoring on\ndirectly from the Source Listing Dump Analysis screen by entering MONITOR in the command line or pressing PF5. You\ncan also set breakpoints or other monitoring options from this display, and then all you have to do is exit from SymDump\nfor CICS and re-execute the transaction.\nWhen InterTest for CICS halts the program at an automatic breakpoint or at a breakpoint you set, you can use the full\npower of InterTest for CICS to debug the program. For example, you can:\n\u2022Examine the backtrace to determine the logic flow up to that point\n\u2022Dynamically correct the problem and resume execution\nWith both SymDump  for CICS and InterTest for CICS, you have all the tools you need to find and correct a problem.\nView the Breakpoint at the Triggering Source Statement\nInterTest for CICS makes it easy to find the error that caused the abend. This example shows you how to use InterTest for\nCICS facilities while viewing a dump.\nTo see the InterTest for CICS breakpoint at the source statement that triggered the abend, select the Source display from\nthe Display Selection screen (see View a Dump and Its Information). The following screen appears:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d78174c109bf-1", "text": "the Display Selection screen (see View a Dump and Its Information). The following screen appears:\n                    CA InterTest - SOURCE LISTING DUMP ANALYSIS\nCOMMAND ===>\nProgram= COBDEMO  Option #       Stmt #                             Margin= 01 \n                                        Search=                                \n-------------------------------------------------------------------------------\n _ 00880 CONTINUE-TASK.\n   00881**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED\n A   ==>     ADD +1 TO TASKNUM.\n     ==>\n     ==> ABEND/DUMP CODE: ASRA\n     ==>\n     ==>      Press PF1 for a detailed description.\n     ==>\n _ 00883     IF TASKNUM = 1\n .\n .\n .\nThe A to the left of statement 882 indicates that the abend occurred at this statement. The ASRA was caused by\nimproperly formatted data. Because the statement ADD +1 TO TASKNUM triggered the abend, TASKNUM most likely\ncontains invalid data.\nRedisplay the Abend\nEven though a task abended, SymDump  for CICS lets you redisplay the abend that caused the dump at a breakpoint so\nyou can use InterTest for CICS to discover the reason for the abend.\n 1334", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4272a6ff0143-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo redisplay the abend that caused the dump at a breakpoint\n1.Display the contents of TASKNUM by entering a d to the left of statement 882.\n2.Place the cursor under any character in TASKNUM, and press Enter. The following InterTest for CICS screen appears.\nThe structured CORE display reveals that TASKNUM contains binary zeros instead of a valid packed decimal value.\n              CA InterTest - MAIN STORAGE UTILITY - Termid = E024\nStarting at Address =  1461A4                Hexadecimal            Character\n                                           \n 02 TASKNUM                           000000                       ...\n 02 TASK-TEXT\n  03 TASK-ID-NO                       000F                         ..\n  03 FILLER                           40\n  03 TASK-MESG                        E3C8C9E2 40C9E240 C140D4C5   THIS IS A ME\n                                      E2E2C1C7 C5404040            SSAGE\n  03 FILLER                           40\n  03 TASK-DATE\n   04 TASK-MM                         F0F9                         09\n   04 TASK-SL1                        61                           /\n   04 TASK-DD                         F1F5                         15\n   04 TASK-SL2                        61                           /\n   04 TASK-YY                         F9F3                         93\n ______________________________________________________________________________\n  PF1 Help       2            3 End        4 Return     5            6          \n  PF7 Backward   8 Forward    9 Caps Off  10           11 Redisplay 12 Structure\n CORE='TASKNUM'\n CORE052 FIELD DOES NOT CONTAIN A VALID PACKED DECIMAL (COMP-3) VALUE\nYou can go one step further and see where TASKNUM was defined in your program.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4272a6ff0143-1", "text": "You can go one step further and see where TASKNUM was defined in your program.\n3.Press Clear  to return to the Source Listing Dump Analysis screen.\nLocate Where TASKNUM Was Initialized\nTo see where TASKNUM was initialized, enter TASKNUM in the Search= field and press Enter. This instructs InterTest for\nCICS to display the source statement defining TASKNUM. The following screen appears.\n                    CA InterTest - SOURCE LISTING DUMP ANALYSIS\nCOMMAND ===>\nProgram= COBDEMO  Option #       Stmt #                             Margin= 01 \n                                        Search=                                \n-------------------------------------------------------------------------------\n   00445     03 TASK-SWITCH2          PIC 99.\n   00446     03 TASK-SWITCH3          PIC X.\n   00447     03 TASKNUM               PIC S9(5)  COMP-3.\n   00448     03 TASK-TEXT.\n .\n .\n .\nInterTest for CICS highlights statement number 447 in Working Storage, which defines TASKNUM as a COMP-3 field.\nNotice that the VALUE clause needed to initialize TASKNUM is missing. Because TASKNUM never initialized, it does not\ncontain a valid packed decimal value. When the program tries to add one to this field, a data exception occurs.\nUsing InterTest for CICS to determine the cause of the abend makes it easy to correct the error. For example, in this case\nyou could initialize TASKNUM either by adding VALUE +0 to statement 447 or by coding the statement MOVE ZEROS TO\nTASKNUM in the Procedure Division. Then recompile the program.\n 1335", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fbcd19099dd4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUsing the CICS REST API\nUse the SymDump CICS REST API Application Programming Interface (API) to perform the following actions:\n\u2022Display a report list\n\u2022Retrieve a report with index\n\u2022Lock a report\n\u2022Unlock a report\n\u2022Display PROTDMP Options\n\u2022Delete a report\nFor instructions to install the SymDump REST API, see Install Testing Tools Server and REST API.\nExample Use Cases\nAs a developer or DevOps admin, you can use the SymDump CICS REST API for the following actions:\nReports\nDisplays a list of ABEND reports\nFull Dump with index\nRetrieves an ABEND analysis report with an index\nLOCK\nLocks an ABEND report to prevent accidental deletion\nUNLOCK\nUnlocks an ABEND report to allow deletion\nDELETE\nDeletes an ABEND report\nOPTIONS\nDisplays the PROTDMP installation options\nAuthentication\nREST API communication is secured through the HTTP or HTTPS protocol. The REST API server authenticates using the\nBasic authentication type, and the mainframe username and password.\nTroubleshoot Errors\nFor errors that occur during request processing, the API returns an HTTP status code to the calling client. An error is\nindicated by a 4nn code or a 5nn code. For example:\nStatus: 400 Bad Request.\nIn addition, some errors might include a JSON object/response that contains a message that describes the error. Use this\ninformation to diagnose the error.\nCA SymDump Rest API\nPlease refer to the online format for OpenAPI content.\nCICS REST API: Reports\nUse the SymDump CICS REST API reports endpoint to display a report list.\n 1336", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fd95aaa182b6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nHTTP Method and URI Path\nThe SymDump CICS REST API URI path for the Reports endpoint has the following format:\nGET   http://host:port/symdump/api/v1/cics/protdmp/{protdmp}/reports\nWhere:\nhost\nSpecifies the address of the server that runs the REST API\nport\nSpecifies the port of the server that runs the REST API\nPROTDMP\nSpecifies the dump repository data set name\nHeaders\nAuthorization: Basic Auth with mainframe username and password\nExample:  Retrieve a report list.\nGET GET /symdump/api/v1/cics/protdmp/CAI.PROTDMP/reports\nREST API Response and Return Codes\nExpected Response\nOn completion, the service returns an HTTP response. This response includes a status code that indicates whether the\nrequest completed. The status code 200 OK  indicates success.\nExample:\n{\n  \"data\": [\n    {\n      \"abend\": \"string\",\n      \"date\": \"string\",\n      \"jobName\": \"string\",\n      \"key\": \"string\",\n      \"lock\": \"string\",\n      \"offset\": \"string\",\n      \"program\": \"string\",\n      \"stepName\": \"string\",\n      \"system\": \"string\",\n      \"time\": \"string\",\n      \"userID\": \"string\"\n    }\n  ],\n  \"messages\": [\n    {\n      \"messageContent\": \"string\",\n      \"messageNumber\": \"string\",\n      \"messageType\": \"string\"\n    }\n  ],\n  \"metadata\": [\n    {\n      \"messageTime\": \"string\",\n 1337", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4b86e89ace99-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n      \"messageVersion\": \"string\",\n      \"serviceName\": \"string\",\n      \"sessionID\": \"string\"\n    }\n  ]\n}\nCICS REST API: Full Dump with Index\nUse the SymDump CICS REST API full dump with index endpoint to retrieve a report.\nHTTP Method and URI Path\nThe SymDump CICS REST API URI path for the full dump with index endpoint has the following format:\nGET   http://host:port/symdump/api/v1/cics/protdmp/{protdmp}/reports/{key}/full-dump-with-index\nWhere:\nhost\nSpecifies the address of the server that runs the REST API\nport\nSpecifies the port of the server that runs the REST API\nPROTDMP\nSpecifies the dump repository data set name\nKey\nReport key used to locate a particular report from the report list\nHeaders\nAuthorization: Basic Auth with mainframe username and password\nExample:  Retrieve a report\nGET/symdump/api/v1/cics/protdmp/CAI.PROTDMP /reports/{key}/full-dump-with-index\nREST API Response and Return Codes\nExpected Response\nOn completion, the service returns an HTTP response. The response includes a status code that indicates whether the\nrequest completed. The status code 200 OK  indicates success.\nExample:\nExample001:\n{\n  \"data\": \"string\",\n  \"dump\": {\n    \"abend\": \"string\",\n    \"date\": \"string\",\n    \"jobName\": \"string\",\n    \"key\": \"string\",\n    \"lock\": \"string\",\n    \"offset\": \"string\",\n    \"program\": \"string\",\n    \"stepName\": \"string\",\n 1338", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "34c83dfc62d9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    \"system\": \"string\",\n    \"time\": \"string\",\n    \"userID\": \"string\"\n  },\n  \"index\": [\n    {\n      \"children\": [\n        \"string\"\n      ],\n      \"description\": \"string\",\n      \"lineNo\": \"string\"\n    }\n  ],\n  \"messages\": [\n    {\n      \"messageContent\": \"string\",\n      \"messageNumber\": \"string\",\n      \"messageType\": \"string\"\n    }\n  ],\n  \"metadata\": [\n    {\n      \"messageTime\": \"string\",\n      \"messageVersion\": \"string\",\n      \"serviceName\": \"string\",\n      \"sessionID\": \"string\"\n    }\n  ]\n}\nCICS REST API: Lock\nUse the SymDump CICS REST API Lock endpoint to lock a report.\nHTTP Method and URI Path\nThe SymDump CICS REST API URI path for the Lock endpoint has the following format:\nPOST   http://host:port/symdump/api/v1/cics/protdmp/{protdmp}/reports/{key}/lock\nWhere:\nhost\nSpecifies the address of the server that runs the REST API\nport\nSpecifies the port of the server that runs the REST API\nPROTDMP\nSpecifies the dump repository data set name\nKey\nReport key used to locate a particular report from the report list\nHeaders\nAuthorization: Basic Auth with mainframe username and password\n 1339", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "393d00b5d7ef-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nExample:  Lock a report:\nPOST /symdump/api/v1/cics/protdmp/CAI.PROTDMP /reports/{key}/lock\nREST API Response and Return Codes\nExpected Response\nOn completion, the service returns an HTTP response. The response includes a status code that indicates whether the\nrequest completed. The status code 200 OK  indicates success.\nExample:\n{\n  \"dump\": {\n    \"abend\": \"string\",\n    \"date\": \"string\",\n    \"jobName\": \"string\",\n    \"key\": \"string\",\n    \"lock\": \"string\",\n    \"offset\": \"string\",\n    \"program\": \"string\",\n    \"stepName\": \"string\",\n    \"system\": \"string\",\n    \"time\": \"string\",\n    \"userID\": \"string\"\n  },\n  \"messages\": [\n    {\n      \"messageContent\": \"string\",\n      \"messageNumber\": \"string\",\n      \"messageType\": \"string\"\n    }\n  ],\n  \"metadata\": [\n    {\n      \"messageTime\": \"string\",\n      \"messageVersion\": \"string\",\n      \"serviceName\": \"string\",\n      \"sessionID\": \"string\"\n    }\n  ]\n}\n}\nCICS REST API: Unlock\nUse the SymDump CICS REST API Unlock endpoint to unlock a report.\nHTTP Method and URI Path\nThe SymDump CICS REST API URI path for the Unlock endpoint has the following format:\nPOST   http://host:port/symdump/api/v1/cics/protdmp/{protdmp}/reports/{key}/unlock\nWhere:\n 1340", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ca8ddea17c6e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nhost\nSpecifies the address of the server that runs the REST API\nport\nSpecifies the port of the server that runs the REST API\nPROTDMP\nSpecifies the dump repository data set name\nKey\nReport key used to locate a particular report from the report list\nHeaders\nAuthorization: Basic Auth with mainframe username and password\nExample:  Unlock a report:\nPOST /symdump/api/v1/cics/protdmp/CAI.PROTDMP/reports/{key}/unlock\nREST API Response and Return Codes\nExpected Response\nOn completion, the service returns an HTTP response. The response includes a status code that indicates whether the\nrequest completed. The status code 200 OK  indicates success.\nExample:\n \n{\n  \"dump\": {\n    \"abend\": \"string\",\n    \"date\": \"string\",\n    \"jobName\": \"string\",\n    \"key\": \"string\",\n    \"lock\": \"string\",\n    \"offset\": \"string\",\n    \"program\": \"string\",\n    \"stepName\": \"string\",\n    \"system\": \"string\",\n    \"time\": \"string\",\n    \"userID\": \"string\"\n  },\n  \"messages\": [\n    {\n      \"messageContent\": \"string\",\n      \"messageNumber\": \"string\",\n      \"messageType\": \"string\"\n    }\n  ],\n  \"metadata\": [\n    {\n      \"messageTime\": \"string\",\n      \"messageVersion\": \"string\",\n      \"serviceName\": \"string\",\n      \"sessionID\": \"string\"\n 1341", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7e5a1e0fce10-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n    }\n  ]\n}\nCICS REST API: Delete\nUse the SymDump  CICS REST API delete endpoint to delete a report.\nHTTP Method and URI Path\nThe SymDump  CICS REST API URI path for the delete endpoint has the following format:\nDELETE   http://host:port/symdump/api/v1/cics/protdmp/{protdmp}/reports/{key} \nWhere:\nhost\nSpecifies the address of the server that runs the REST API\nport\nSpecifies the port of the server that runs the REST API\nPROTDMP\nSpecifies the dump repository data set name\nKey\nReport key used to locate a specific report from the report list\nHeaders\nAuthorization: Basic Auth with mainframe username and password\nExample:  Delete a report\nDELETE /symdump/api/v1/cics/protdmp/CAI.PROTDMP/reports/{key}\nREST API Response and Return Codes\nExpected Response\nExample:\n{\n  \"dump\": {\n    \"abend\": \"string\",\n    \"date\": \"string\",\n    \"jobName\": \"string\",\n    \"key\": \"string\",\n    \"lock\": \"string\",\n    \"offset\": \"string\",\n    \"program\": \"string\",\n    \"stepName\": \"string\",\n    \"system\": \"string\",\n    \"time\": \"string\",\n    \"userID\": \"string\"\n  },\n  \"messages\": [\n    {\n      \"messageContent\": \"string\",\n 1342", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "003dae9667d8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n      \"messageNumber\": \"string\",\n      \"messageType\": \"string\"\n    }\n  ],\n  \"metadata\": [\n    {\n      \"messageTime\": \"string\",\n      \"messageVersion\": \"string\",\n      \"serviceName\": \"string\",\n      \"sessionID\": \"string\"\n    }\n  ]\n}\nCICS REST API: Options\nUse the SymDump  CICS REST API options endpoint to display PROTDMP installation options.\nHTTP Method and URI Path\nThe SymDump  CICS REST API URI path for the options endpoint has the following format:\nGET  http://host:port/symdump/api/v1/cics/protdmp/{protdmp}/options\nWhere:\nhost\nSpecifies the address of the server that runs the REST API\nport\nSpecifies the port of the server that runs the REST API\nHeaders\nAuthorization: Basic Auth with mainframe username and password\nExample:  Display installation options:\nPOST /symdump/api/v1/cics/protdmp/{protdmp}/options\nREST API Response and Return Codes\nExpected Response\nOn completion, the service returns an HTTP response. The response includes a status code that indicates whether the\nrequest completed. The status code 200 OK  indicates success.\nExample:\n   {\n   \"data\":\"string\",\n   \"messages\":[\n      {\n         \"messageContent\":\"string\",\n         \"messageNumber\":\"string\",\n         \"messageType\":\"string\"\n      }\n   ],\n 1343", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0d17269a4465-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n   \"metadata\":[\n      {\n         \"messageTime\":\"string\",\n         \"messageVersion\":\"string\",\n         \"serviceName\":\"string\",\n         \"sessionID\":\"string\"\n      }\n   ]\n}\nDWARF\nNOTE\nDWARF symbolic support is under incremental development. Not all features available for PROTSYM\nprocessing are currently available for DWARF symbolic support. For more information on the limitations, see\nDWARF Incremental Release State.\nDWARF is a format of source-level debugging information which is stored within an object file in the target program.\nInterTest for CICS supports DWARF debugging as an alternative to PROTSYM for COBOL 5 and above. DWARF\nsymbolic data is stored inside the target program object, and also read straight from the program object. When you use\nDWARF debugging, it is not necessary to create a PROTSYM file.\nDWARF symbolic data increases the size of the program object, but does not use more storage when you load the\nprogram object.\nThe user experience using DWARF debugging on InterTest for CICS is designed to be largely similar to using PROTSYM.\nLimitations\nUnlike PROTSYM, DWARF debugging data is displayed as a copy of the source, rather than a listing, so some listing\nfunctionality is not available. For more information on the limitations, see Source Listing Facility for InterTest.\nThe following Source Listing sections are not available with DWARF debugging:\n\u2022Data Division Map\n\u2022CLIST/Pmap\n\u2022Data Name XREF\n\u2022Procedure Cross Reference\n\u2022Error Messages\nNOTE\nDebugging using DWARF is only supported for COBOL programs in InterTest for CICS.\nUsage Considerations", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0d17269a4465-1", "text": "Usage Considerations\n\u2022The extended source code is part of the program object. Anyone with access to the program object has access to the\nsource code of the program. Consult your security policies before using DWARF.\n\u2022DWARF data increases the size of the program object. Ensure that load libraries have enough allocated space.\n\u2022Ensure you turn on DWARF symbolic support in the product. It is turned off by default. For more information, see\nSYMBOLIC  in the IN25OPTS keywords.\nThere is no fundamental difference between using symbolics from PROTSYM or DWARF. For a practical walkthrough\ndemo, refer to COBOL Basic Demo Session for DWARF.\n 1344", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d11a0413aeff-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAdvantages of DWARF over PROTSYM\n\u2022Because the DWARF extended source information is part of the load module itself, there is no mismatch between the\nlisting and load module.\n\u2022When you use DWARF, you do not need to maintain a separate symbolic repository (PROTSYM file).\nGenerate the DWARF Information\nYou generate the DWARF information by specifying the COBOL compiler option TEST(SOURCE). For more information,\nrefer to the IBM Enterprise COBOL documentation.\nA sample JCL is available in the member CABADWCJ, in the CAI.CAVHPROC data set.\nNOTE\nIt is currently not possible to save the DWARF data into a separate binary file.\nRequired COBOL Options\nThe following compiler options are required to load symbolic information for COBOL programs into the DWARF file:\nOPT(0)\nProduces breakpoints synchronized with the source.\nNOTE\nWhen a COBOL program is OPTIMIZED, the optimization adds or modifies the generated code, and it\nmight not be synchronized with the related source statements in the listing. Therefore the breakpoints\nmight be stopped in an unexpected location.\nTEST(SOURCE)\nGenerates the DWARF debugging information including the expanded source code.\nDWARF Lister Screen\nWith PROTSYM, symbolic information for individual programs is stored as separate PROTSYM entries in a PROTSYM\nfile. With DWARF, symbolic information is stored inside the program object. One program object can contain DWARF\nsymbolic information for multiple programs that are bound together using binder. Therefore, to retrieve DWARF symbolic\ninformation, ensure that you provide both the program object (load module) and program (COBOL PROGRAM-ID) names.\nExample: Source Listing Display", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d11a0413aeff-1", "text": "Example: Source Listing Display\nCA InterTest for CICS - *DWARF* FILE  SOURCE LISTING DISPLAY               \nCOMMAND ===>                                                                  \nProgram= CSBIN25  Option #       Stmt #                           Margin= 07                                  \n                                              Search=                                \nLoad module= COBDEML                                                          \nSymbolic file: *DWARF*  Timestamp: MATCH  Language: IBM COBOL  5.2.0         \n-------------------------------------------------------------------------------\nWhere:\nLoad module=\nSpecifies the name of the program object where the symbolic information is stored.\nProgram=\nSpecifies the COBOL PROGRAM-ID of the program you want to use.\nTo switch to another program in the scope of the same program object, change the Program= field only. To switch to\nanother program in a different program object, change the Load module= field.\n 1345", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7153b4b8f6fa-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nExample: Open expanded source for COBDEML (in the COBDEML program object)\nThe command LIST=COBDEML produces the following:\nCA InterTest for CICS - *DWARF* FILE  SOURCE LISTING DISPLAY               \nCOMMAND ===>                                                                  \nProgram= COBDEML  Option #       Stmt #                             Margin= 07                                \n                                            Search=                                \nLoad module= COBDEML                                                          \nSymbolic file: *DWARF*  Timestamp: MATCH  Language: IBM COBOL  5.2.0         \n-------------------------------------------------------------------------------   \n000001  ID DIVISION.                                                        \n000002  PROGRAM-ID. COBDEML.                                             \nExample: Display CSBIN25 in the same program object.\nChange the Program= field to CSBIN25:\nCA InterTest for CICS - *DWARF* FILE  SOURCE LISTING DISPLAY               \nCOMMAND ===>                                                                  \nProgram= CSBIN25  Option #       Stmt #                            Margin= 07                                 \n                                                 Search=                                 \nLoad module= COBDEML                                                          \nSymbolic file: *DWARF*  Timestamp: MATCH  Language: IBM COBOL  5.2.0         \n-------------------------------------------------------------------------------   \n000001  ID DIVISION.                                                       \n000002  PROGRAM-ID. COBDEML.                                             \nResult:\nCA InterTest for CICS - *DWARF* FILE  SOURCE LISTING DISPLAY               \nCOMMAND ===>                                                                  \nProgram= CSBIN25  Option #       Stmt #                           Margin= 07                                  \n                                            Search=                                \nLoad module= COBDEML                                                          \nSymbolic file: *DWARF*  Timestamp: MATCH  Language: IBM COBOL  5.2.0         \n-------------------------------------------------------------------------------   \n000001  ID DIVISION.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7153b4b8f6fa-1", "text": "-------------------------------------------------------------------------------   \n000001  ID DIVISION.                                                        \n000002  PROGRAM-ID. CSBIN25.                                             \nExample: Display expanded source for COBDEMO (in the COBDEMO program object)\nChange the Load module= field to COBDEMO:\nCA InterTest for CICS - *DWARF* FILE  SOURCE LISTING DISPLAY               \nCOMMAND ===>                                                                  \nProgram= CSBIN25  Option #       Stmt #                           Margin= 07                                  \n                                               Search=                                 \nLoad module= COBDEMO                                                          \nSymbolic file: *DWARF*  Timestamp: MATCH  Language: IBM COBOL  5.2.0         \n-------------------------------------------------------------------------------   \n000001  ID DIVISION.                                                       \n000002  PROGRAM-ID. CSBIN25.                                             \nResult:\nCA InterTest for CICS - *DWARF* FILE  SOURCE LISTING DISPLAY               \nCOMMAND ===>                                                                  \n 1346", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "50b6857c5171-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nProgram= COBDEMO  Option #       Stmt #                           Margin= 07                                  \n                                               Search=                                \nLoad module= COBDEMO                                                          \nSymbolic file: *DWARF*  Timestamp: MATCH  Language: IBM COBOL  5.2.0         \n-------------------------------------------------------------------------------   \n000001  ID DIVISION.                                                          \n000002  PROGRAM-ID. COBDEMO.                                                \nCOBOL Basic Demo Session for DWARF\nSymbolic Version Processing\nDuring automatic breakpoint processing, if a program has no previously selected symbolic file, InterTest matches the date/\ntime of the load module to a symbolic file.\nEnsure that the value of the SYMBOLIC option in IN25OPTS is set to enable DWARF symbolic data. For more information\nsee IN25OPTS Keywords. If the symbolic version list pops up, select *DWARF* as in the example below:\nCA InterTest for CICS - SYMBOLIC VERSION LIST                                                                 \n   Program = COBDEMO     Load Module Date/Time =  01/10/2018 07:24:21              \nLoadlib = your.program.loadlib                      Volume = volser                                           \n                                   \nFile ID     Date       Time    Language     Comments                          \nS *DWARF*  01/10/2018  07.24.21  IBM COBOL  DATE/TIME MATCH \n_ PROTSYM  01/10/2018  07.24.21  IBMCOB 52  LATEST VERSION \n_ PROTSYM  01/02/2018  11.14.03  IBMCOB 52\n.\n.\n.         \n         S - Select which Symbolic file to use                                  \n-------------------------------------------------------------------------------", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "50b6857c5171-1", "text": ".\n.         \n         S - Select which Symbolic file to use                                  \n------------------------------------------------------------------------------- \nPFKEYS:  1 Help      2           3 No file   4           5           6\n         7 Backward  8 Forward   9          10          11          12\nNOTE\nOnce a symbolic file is selected for a program, InterTest continues to use the selected file and bypasses\nsubsequent date/time matching until all declared breakpoints and monitoring options are removed for the\nprogram, or until a CNTL=NEW, PROG=program command is executed.\nDemo Session Objectives\nThis demo session teaches you how to do the following:\n\u2022Select a source listing for a program from the ITST menus\n\u2022Inform InterTest that you want to test a program (set monitoring)\n\u2022Respond to the information provided when a program error is detected\n\u2022Examine the value of a data item\n\u2022Dynamically change the value of a data item\n\u2022Halt program execution at any point (set breakpoints)\n\u2022Resume program execution\n 1347", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "62d498147b18-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBefore You Start\nEnsure that the COBOL test program COBDEMO is compiled with the compiler option TEST(SOURCE). A sample\ncompilation procedure, CABADWCJ, is described in Installation Verification.\nDemo Session Scenario\nThe InterTest basic demo session takes you through the following scenario:\n1.You use the ITST menus to select and view the source listing of the sample program to be executed. A sample IBM\nEnterprise COBOL program named COBDEMO is provided for you to use.\n2.You set monitoring for the sample program and view the status display of your monitoring request.\n3.You exit the ITST menus and initiate COBDEMO by specifying the DEMC transaction.\n4.InterTest for CICS intercepts and prevents an ASRA abend in COBDEMO. InterTest halts COBDEMO at an ADD\nstatement and displays a diagnostic message informing you that the problem was caused by improperly formatted\ndata.\n5.You examine the current value of TASKNUM, the receiving field in the ADD statement which you suspect might be the\ncause of the problem. You find that TASKNUM does not contain a valid packed decimal number.\n6.You move a packed decimal zero into TASKNUM to correct the error.\n7.You set a breakpoint to halt COBDEMO at another statement. This step is purely instructional and has nothing to do\nwith correcting the ASRA.\n8.You resume program execution. InterTest halts the program at the breakpoint you set in Step 7. You can see that when\nthe ADD statement executed, the value of TASKNUM changed.\n9.You clean up by removing the breakpoint you set. You then resume program execution and COBDEMO runs to\ncompletion.\nSelect the Source Program from the ITST Menus", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "62d498147b18-1", "text": "completion.\nSelect the Source Program from the ITST Menus\nTo begin your session, select the source listing of the COBDEMO demonstration program from the ITST Primary Option\nMenu.\nFollow these steps:\n1.Sign on to CICS.\n2.Type ITST on a clear screen.\n3.Press Enter.\nThe InterTest for CICS Primary Option Menu displays.\nCA InterTest for CICS PRIMARY OPTION MENU     \nOPTION  ===>     \n1  Source             - Display/select program source files/listings            \n2  Monitoring         - Display/modify CA InterTest monitoring/activity         \n3  Main storage       - Display/modify CICS storage areas                       \n4  Auxiliary storage  - Display/access databases/files/queues                   \n5  Dump analysis      - Invoke CA SymDump CICS dump/trace capture facility      \n6  Product help       - Invoke CA InterTest product help facility               \n7  Status/Maintenance - Product status and maintenance functions                \n8  What's new?        - Display information about CA InterTest for CICS     \nX  Exit               - Terminate menu processing                                                            \n                                                                                                             \n                                                                                                             \n                                                                                                             \n                                                                                                             \n           \n 1348", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0eaf09edeff2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPF1 Help       2            3 End        4 Return     5            6          \nPF7            8            9           10           11           12        \nThe PF keys have conventional assignments for ISPF-like navigation:\nPF1 (Help)\nAccesses online help\nPF3 (End)\nDisplays the previous panel\nPF4 (Return)\nReturns to the top-level menu\nNext, open the source listing of the program you want to debug.\nFollow these steps:\n1.Type 1 in the Option field.\n2.Press Enter.The InterTest Source Menu opens.\n                 CA InterTest for CICS  SOURCE MENU  \nOPTION  ===> 1                                                                   \nSelect a member list type, specifying optional criteria below.               \n1  Source listings    - Display\n/select program source listings                \n2  Symbolic files     - Display\n/select program source SYMBOLIC files          \nType specific or generic program/file name(s):                                   \n(Valid mask characters are  *  and/or  +)                                  \ncobdemo_ ________ ________ ________ ________ ________ ________ ________   \n3.To search for program listings, type 1 in the Option field\n4.Tab to the first entry field for file/program names\n5.Enter\ncobdemo\nThe Source Listing Selection screen lists all program Source Listings with the name COBDEMO.\n                CA InterTest for CICS SOURCE LISTING \nSELECTION                \nCOMMAND \n===>                                                                                                      \n           \n   Type S to select a source listing.                                                                     \n                                                    \nName     File         Created       Size \nAttributes                         \ns COBDEMO  *DWARF*  01/02/2018 07:27 ----- IBMCOB 6.1", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0eaf09edeff2-1", "text": "_ COBDEMO  NDVRSYM  01/02/2018 07:27   145 IBMCOB 6.1                         \n_ COBDEMO  NDVRSYM  08/04/2015 10:29   134 IBMCOB 4.2                           \n*** End of data ***                                                                                       \n                                              \nPF1 Help       2 Refresh    3 End        4 Return     5            6          \nPF7 Backward   8 Forward    9           10           11           12 \n6.Type S in the field to the left of the program name on the line where *DWARF* is specified in the File column.\n 1349", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9c5f052ea83e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n7.Press Enter.\nNOTE\nIf the list does not contain the name of the previously indicated demo program, it might be because the user\nwho installed InterTest changed the name of the InterTest sample programs available to you. To find the\ncorrect names, check with that user.\n   CA InterTest for CICS - *DWARF* FILE  SOURCE LISTING DISPLAY\nCOMMAND ===>\nProgram= COBDEMO  Option #       Stmt #                             Margin= \n07                                        Search=                                \n-------------------------------------------------------------------------------           \n000001 ID DIVISION.                                                                 \n000002 PROGRAM-ID. COBDEMO.                                                         \n000003 ENVIRONMENT DIVISION.                                                        \n000004 DATA DIVISION.                                                           \n_ 000005 WORKING-STORAGE SECTION.                                                \n_ 000006 77  S999-FIELD1             PIC S9(3).                                   \n_ 000007 77  S999-FIELD2             PIC S9(3)       VALUE +50.                   \n_ 000008 77  999-FIELD1              PIC 9(3).                                    \n_ 000009 77  999-FIELD2              PIC 9(3)        VALUE 50.                    \n_ 000010 77  COMMAREA-LEN            PIC S9(4) COMP  VALUE +59.                   \n_ 000011 77  LINK-COMMAREA-LEN       PIC S9(4) COMP  VALUE +59.                   \n_ 000012 77  TSQ-LEN                 PIC S9(4) COMP  VALUE +59.                   \n_ 000013 77  REC-LEN                 PIC S9(4) COMP.                              \n_ 000014 77  NUM-CHOICES             PIC S9(4) COMP  VALUE +7.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9c5f052ea83e-1", "text": "_ 000015 77  SUB                     PIC S9(4) COMP.                        \nThe top half of the display identifies the program and provides fields for entering:\n\u2022Commands\n\u2022Options\n\u2022Statement numbers\n\u2022Search criteria\nDepending on your session defaults, it might also display PF key assignments and available options. These are omitted\nfrom the Source Listing displays in this article for clarity.\nThe bottom half of the display contains the source listing.\nNOTE\nThe statement numbers on your screen may not match those shown in the illustrations. This will not hinder you\nfrom performing the test session.\nView the Source Listing Profile\nThe Source Listing Profile lists the PF keys, options and current environment settings relating to the Source Listing\ndisplay.\nTo open the Source Listing Profile for the current session, enter the command PROFILE or press the PF4 key.\n   CA InterTest for CICS - *DWARF* FILE  SOURCE LISTING PROFILE\nCOMMAND ===>\nProgram= COBDEMO  Option #       Stmt #                            Margin= 07                                 \n                                           Search=\n 1350", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "34227f106a4d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nOPTS 1 Proc div  2 Work-stor 3 Link sect  4            5          More: +      6           7           8      \n      9 Srch fwd  10 Srch bwd\nPFKS 1 Help      2 SDF       3 End        4 Auto prms  5 Monitor    6 Menu     \n     7 Backward  8 Forward   9 Next Wnd  10           11           12 Status\n-------------------------------------------------------------------------------\nDisplay window   = T         N (None), T (Titles), R (Registers),\n                             K (Keep), P (Program)\nPF7/8 amount     = PAGE      PAGE, HALF, STOP, or a number from 1 to 9999\nStep Timing      = BEFORE    Stop  Before  or  After  the next verb  is executed\nStepping amount  = 001       The number of verbs   to execute\nAuto-stepping    = OFF       ON to activate; press PF4 to change values\nSource List BKPT = ON        OFF to use the detailed breakpoint display\nFrom terminal ID = U002      Terminal ID where the program will execute\nBKPT terminal ID = U002      Terminal ID to receive the breakpoint displays\nUser ID          = .ANY      User ID who will execute this program\nAutoKeep Display = ON        OFF to deactivate\nCode Counting    = OFF       ON to activate Code Coverage\nSDF              = DATA      HEX  for Hexadecimal Format           \nNOTE\nEnsure that the AutoKeep Display feature is activated for this demo session. For further instructions, see Source\nListing Facility for InterTest.\nSet Monitoring\nThe next step is to instruct InterTest to monitor COBDEMO. As part of monitoring a CICS command-level program such", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "34227f106a4d-1", "text": "as COBDEMO, InterTest automatically prevents all CICS abends during execution. How this works is shown later on when\nInterTest prevents COBDEMO from abending because of an ASRA.\nTo begin monitoring the demo program, navigate to the Source Listing Profile or Source Listing Display, and enter the\nMONITOR command or press PF5. The screen momentarily flashes as the request is processed. The Source Listing\nDisplay screen then reappears.\nView Monitoring Status\nTo verify that the program is being monitored, open the Monitoring Status screen to verify that the program is correct, then\nexit to CICS using the fastpath entry.\nFollow these steps:\n1.Enter STATUS on the command line and press enter.\nThe Monitoring Status screen opens and shows the monitoring entry for the current program only.\n                    CA InterTest for CICS MONITORING STATUS           \nCOMMAND ===>   \nType + to expand or - collapse option levels displayed below,\n          or R to remove option(s).\n     Option     Description                Attributes\n_ - COBDEMO    Program monitor entry      IBMCOB 5.2\n_ - |-.ANY     User monitoring options    Active\n       |        Symbolic listing file      *DWARF*\n_     |-SLB    Source listing breakpoints U002\n                *** End of data ***\n                                              \nPF1 Help       2 Refresh    3 End        4 Return     5 Collapse   6 Expand     \nPF7 Backward   8 Forward    9           10           11           12         \n 1351", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "334d7488c32e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nIf the Status display does not display, ensure you set monitoring correctly. Press PF3 to return to the Source\nListing display, and then type MONITOR on the command line or press PF5 to set monitoring. Check the\nstatus again before you continue.\n2.Once you verify that the monitoring entry is for the correct program, press PF3 to return to the Source Listing.\n3.Type =X in the Source Listing Command field and press Enter.\nThe ITST menu processing opens\n4.To exit to CICS, enter the command =X from the Source Selection menu.\nStart Program Execution\nNow you are ready to begin to test COBDEMO.\nFollow these steps:\n1.Clear the CICS display\n2.Type DEMC and press enterA welcome screen appears\n3.Press enterThe welcome screen closes, and COBDEMO resumes execution.\nDetect and Prevent an Abend\nThe next screen you see is not displayed by the COBOL demo. It is a diagnostic screen, called a breakpoint display,\nwhich displays when InterTest detects an error:\n   CA InterTest for CICS - *DWARF* FILE  ABEND DETECTED BREAKPOINT\nCOMMAND ===>\nProgram= COBDEMO  Option #       Stmt #                            Margin= 07                                 \n                                          Search=\n-------------------------------------------------------------------------------\n _____ TASKNUM                         | ?00000.\n---------+---------------------------------------------------------------------\n _ 000410  CONTINUE-TASK.   000411 **** TASKNUM *NOTE* FIELD MUST BE INITIALIZED A   ==>       ADD +1 TO\n TASKNUM.     ==>    ==> ASRA ABEND (0C7) detected and prevented. Caused by invalid decimal     ==> arithmetic\n data format.  \n    ==>    ==>      Press PF1 for a detailed description.  \n    ==> _ 000413      IF TASKNUM = 1", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "334d7488c32e-1", "text": "==> _ 000413      IF TASKNUM = 1\n _ 000414          MOVE 'DMAPASR'  TO MAPNAME.\n _ 000415      IF TASKNUM = 2\n _ 000416          MOVE 'DMAPSUM'  TO MAPNAME.\n _ 000417      IF TASKNUM GREATER 2\n _ 000418          GO TO SEND-END-MSG.\n _ 000419      GO TO REWRITE-TSQ.\n _ 000420  REWRITE-TSQ.                                                         \nNote that InterTest highlights an ADD instruction and displays a message below it.\nExecution of that ADD instruction triggered an ASRA abend. InterTest prevented the abend and then displays the above\ndiagnostic screen.\nThe point at which InterTest stops the execution of a program is called a breakpoint. A program can be halted at a\nbreakpoint automatically, or you can set up InterTest to halt the program at a specific, user-defined breakpoint. The A to\nthe left of the ADD statement indicates that the program was halted at an automatic breakpoint, not a previously defined\none.\n 1352", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "70774e4dc7c0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe highlighted message indicates that the problem was caused by improperly formatted data. Since ADD+1 TO\nTASKNUM triggered the breakpoint, it is likely that TASKNUM contains improperly formatted data.\nDetermine the Cause of the Error\nTo determine the cause of the error, examine the current value stored in TASKNUM (i.e. its value prior to the execution of\nthe ADD statement that triggered the ASRA) and confirm that the value is in valid arithmetic format.\nInterTest for CICS displays the current value of TASKNUM in the above screenshot. In this case, TASKNUM is displayed\nin this specially formatted Keep window under the Search= field. On the left is the name of the data item; on the right\nis the datatype appropriate display format. The question mark at the beginning of the field indicates that it contains an\nunexpected value for its datatype.\nUp to six data items are displayed at a time within the scrollable Keep window. This feature lets you see how the values of\ndata items change as your program executes. The Keep window remains on screen until you remove all data items from\nit. For more information on the Keep window, see COBOL Debugging Programs.\nNow take a look at the contents of TASKNUM. It does not contain a valid packed decimal value. Instead, it contains low-\nvalues (binary zeros). COBOL does not allow you to add a value to a field without initializing it.\nDynamically change the value in TASKNUM\nNow that we identified and confirmed the cause of the problem, we can fix it.\nFollow these steps:\n1.To modify the value of TASKNUM, type M to the left of TASKNUM in the keep window.\n   CA InterTest for CICS - *DWARF* FILE  ABEND DETECTED BREAKPOINT\nCOMMAND ===>", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "70774e4dc7c0-1", "text": "COMMAND ===>\nProgram= COBDEMO  Option #       Stmt #                            Margin= 07                             \n           Search=\n-------------------------------------------------------------------------------\n M____ TASKNUM                         | ?00000.\n---------+---------------------------------------------------------------------\n_ 000410  CONTINUE-TASK.\n  000411 **** TASKNUM *NOTE* FIELD MUST BE INITIALIZED\n      A    ==>       ADD +1 TO TASKNUM.                                                                   \n                            \n2.Press Enter.\nInterTest for CICS generates a fill-in-the-blanks MOVE statement.\n3.Type zeros in the MOVE field\n   CA InterTest for CICS - *DWARF* FILE  ABEND DETECTED BREAKPOINT\nCOMMAND ===>                                                                    \nProgram= COBDEMO  Option #       Stmt #                             Margin= 07                            \n              Search=                                 \n-------------------------------------------------------------------------------\n  _____ TASKNUM                         | ?00000.                                \n---------+---------------------------------------------------------------------\n MOVE zeros____________________________________________________________            \n   \n     to                                                                                  \n       TASKNUM                                                                    \nOvertype Underscores with a Data-Name, Figurative Constant,\n 1353", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cf6fcb41c40b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAlphanumeric Literal, or Numeric Literal                                       \nNOTE\nYou do not have to know the type of data (binary, packed etc.) or the length of TASKNUM. The InterTest\nCOBOL-like MOVE statement automatically takes care of that for you.\n4.Press Enter\nInterTest for CICS executes the MOVE statement. As a result, TASKNUM now contains a packed decimal zero.\nInterTest also displays a main storage display that shows the new value of TASKNUM:\n       CA InterTest for CICS   - MAIN STORAGE UTILITY - Termid = U002     \nStarting at Address =2080A138         Structure Display Format\n02 TASKNUM                         |  00000.                    |               \n02 TASKNUM-CHAR                    | ...                        |               \n02 TASK-TEXT                       |                            |                \n03 TASK-ID-NO                      |  000.                      |                \n03 FILLER                          |                            |                \n03 TASK-MESG                       | THIS IS A MESSAGE          |                                         \n   03 FILLER                          |                            |               \n03 TASK-DATE                       |                            |                 \n04 TASK-MM                         | 12                         |                 \n04 TASK-SL1                        | /                          |                 \n04 TASK-DD                         | 25                         |                 \n04 TASK-SL2                        | /                          |                 \n04 TASK-YY                         | 99                         |               \n------------------------------------------------------------------------------  \nPF1 Help       2            3 End        4 Return     5            6 Dump       \nPF7 Backward   8 Forward    9 Caps Off  10           11 Redisplay 12 Structure  \nCORE=MOVE ZEROS TO TASKNUM                                                      \nCAIN0201 RECEIVING FIELD has been changed as shown                           \nTIP", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cf6fcb41c40b-1", "text": "CAIN0201 RECEIVING FIELD has been changed as shown                           \nTIP\nTo change the contents of a field, you can overtype the desired bytes in the Keep window or on the main\nstorage display. Overtyping is, of course, faster than using an InterTest-generated MOVE statement.\nHowever, with the MOVE statement you do not have to know the internal representation of the data. InterTest\nautomatically takes care of the details for you.\n5.To return to the program listing so that we can continue to test COBDEMO, press Clear\nInterTest for CICS redisplays the breakpoint screen without the explanation of the abend. Note the new value of\nTASKNUM in the Keep window.\nCOBOL Control Program Execution\nNow that the value in TASKNUM is properly initialized, the next step might be to continue testing by resuming program\nexecution. However, this is a good opportunity to learn about another important InterTest feature - the ability to control\nprogram execution by setting breakpoints.\nHow to Stop Your Program by Setting Breakpoints\nOne of the problems with traditional testing methods is that you have little or no control over program processing. You\ninitiate the task, and the program either runs to completion or abends.\nWith InterTest, you can control program execution in several ways. For example, you can set breakpoints anywhere in\nyour program. The three types of breakpoints you can set are unconditional, conditional and variable-change.\n 1354", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "315458b74590-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022When you set an unconditional  breakpoint at a statement, the program stops just before or just after the statement is\nexecuted. (Depending on the type of unconditional breakpoint that you set.)\n\u2022When you set a conditional  breakpoint at a statement, the program stops only if a condition you specified is met -- such\nas a counter equaling or exceeding some value. You can also set a conditional breakpoint to stop at any instruction\nwhen the condition you specified is met.\n\u2022When you set a variable-change  breakpoint, the program stops at any instruction if the value of the variable you\nspecify has changed. This is a special type of conditional breakpoint.\nWhat You Can Do When Your Program is Stopped\nOnce a program is stopped, you can use the InterTest testing and debugging facilities to perform the following tasks:\n\u2022Examine the source listing\n\u2022Examine and modify main and auxiliary storage to detect and correct errors\n\u2022Set and remove breakpoints\n\u2022Keep data items in a Keep window to observe changes in their values\n\u2022Abend your task with or without a dump\n\u2022Execute the program in single-step mode; that is, the program executes one verb and then stops.\nCOBOL Set Unconditional Breakpoints\nThe next step in this demo is to set an unconditional breakpoint. You can set unconditional breakpoints directly on\nthe Source Listing screen. Enter U or ) to the left of each statement where you want the application to halt program\nexecution. The U sets a breakpoint that stops before  the instruction is executed. The ) sets a breakpoint that stops after\nthe instruction is executed.\nSet a breakpoint at the statement IF TASKNUM GREATER 2\nFollow these steps:\n1.Type U to the left of the statement number on the IF TASKNUM GREATER 2 line:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "315458b74590-1", "text": "CA InterTest for CICS - *DWARF* FILE  ABEND DETECTED BREAKPOINTCOMMAND ===>\nProgram= COBDEMO  Option #       Stmt #                            Margin= 07                             \n                                            Search=\n-------------------------------------------------------------------------------\n _____ TASKNUM                         |  00000.\n---------+---------------------------------------------------------------------\n_ 000410  CONTINUE-TASK.  \n  000411 **** TASKNUM *NOTE* FIELD MUST BE INITIALIZED A   ==>       ADD +1 TO TASKNUM. _ 000413      IF\n TASKNUM = 1\n_ 000414          MOVE 'DMAPASR'  TO MAPNAME.\n_ 000415      IF TASKNUM = 2\n_ 000416          MOVE 'DMAPSUM'  TO MAPNAME.\n U 000417      IF TASKNUM GREATER 2   \n2.Press Enter\n3.Type the GO command on the command line or press PF5 to continue execution from where the program is currently\nstopped (at the statement ADD +1 TO TASKNUM).\nInterTest for CICS resumes program execution and continues until it reaches the breakpoint you just set. InterTest\nhalts the program before that statement is executed and displays the following screen:\n   CA InterTest for CICS - *DWARF* FILE  UNCOND  BEFORE BREAKPOINT\nCOMMAND ===>Program= COBDEMO  Option #       Stmt #                            Margin= 07                 \n                       Search=\n-------------------------------------------------------------------------------\n_____ TASKNUM                         | +00001.\n 1355", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5716549f02f2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n---------+---------------------------------------------------------------------\n_ 000415      IF TASKNUM = 2\n_ 000416          MOVE 'DMAPSUM'  TO MAPNAME. U 000417      IF TASKNUM GREATER 2  \n_ 000418          GO TO SEND-END-MSG. ...\nNote the U to the left of the highlighted statement. It identifies the breakpoint as an unconditional \"before\" breakpoint.\nFor an \"after\" breakpoint, the application displays a ). For an automatic, conditional, variable-change, or request\nbreakpoint, the application displays an A, C, V , or R, respectively.\nThe value of TASKNUM is now 1, because the ADD +1 TO TASKNUM statement executed successfully.\nWhen you are stopped at a breakpoint, you can perform the following tasks:\n\u2022Scroll or search through your source listing\n\u2022Examine and modify main and auxiliary storage\n\u2022Add a data item to the Keep window using the K line command\n\u2022Set and remove breakpoints\n\u2022Abend your task (with or without a dump)\nWhen debugging your own programs, you typically perform one or more of these activities, which are described in detail\nin the next article. However, COBDEMO does not have any more errors, so the next step is the final step in the demo\nsession.\nNext, remove the unconditional breakpoint you just set so COBDEMO will not stop unnecessarily at this statement when it\nis re-executed.\nRemove Breakpoints from the Status Display\nFollow these steps:\n1.Type STATUS on the command line.\n2.Press Enter.\nInterTest for CICS displays the Monitoring Status screen:\n                    CA InterTest for CICS MONITORING STATUS            \nCOMMAND ===>   Type + to expand or - collapse option levels displayed below,\n               or R to remove option(s).", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5716549f02f2-1", "text": "or R to remove option(s).\n     Option     Description                Attributes\n_ - COBDEMO    Program monitor entry      IBMCOB 5.2\n_ - |-.ANY     User monitoring options    Active\n       |        Waiting at breakpoint      Task 00101, UBP since 06:39 a.m.\n       |        Symbolic listing file      *DWARF*_\n -   |-UBP    Unconditional breakpoint   #417 \n      |        Option ID                  6CF0FC3E\n      |        From, to terminals         U002, U002\n_     |-SLB    Source listing breakpoints U002\n                *** End of data ***                                            \nPF1 Help       2 Refresh    3 End        4 Return     5 Collapse   6 Expand   \nPF7 Backward   8 Forward    9           10           11           12        \n3.Type R to the left of the unconditional breakpoint (UBP).\n4.Press Enter.\nAn asterisk displays next to the breakpoint, indicating that a command is processed.\n5.Press PF2 to refresh the screen.\nThe unconditional breakpoint is no longer displayed.\n6.Press PF3 to return to the Source Listing Breakpoint screen.\n 1356", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "168c5648b388-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nResume Program Execution\nFollow these steps:\n1.Press PF5 to continue program execution.\nInterTest for CICS resumes program execution. COBDEMO displays a screen confirming that you have successfully\ncorrected the ASRA.\n2.Press Enter.\nCOBDEMO displays the following screen:\n**********************************************************************\n****                                                              ****    \n****             CA InterTest Demo Session                        ****    \n****                                                              ****    \n**********************************************************************\n        \nYou have completed the sample CA InterTest test session.\nAs part of this session, you:                                      \n                * displayed program source code and compiler output online\n                * displayed and modified main storage         \n                * controlled program execution                                   \n       This is just a fraction of CA InterTest's capabilities. You can also: \n                * display or modify any CICS file, or DL/1, DB2, or SQL/DS database\n                * set and remove many kinds of monitoring options\n                  \n                  Press ENTER or CLEAR to complete the termination.               \n3.To complete this part of the sample test session, press Clear or Enter to clear your screen.\nWhat You Have Learned\nThis demo session has taught you the basics of using InterTest to test a program.\nYou learned how to perform the following tasks:\nSelect a source program for display\nGo to ITST Menu Option 1.1. Select a program from the list.\nSet monitoring for a program\nUse the MONITOR command or PF5 from Source Listing.\nView a Monitoring Status display\nUse the STATUS command or PF12 from Source Listing.\nInterpret the information the application provides when it detects an error\nView the Automatic Breakpoint and press PF1 for help.\nExamine the value of a data item in a Keep window\nView the data in the AutoKeep Display window.\nModify main storage", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "168c5648b388-1", "text": "View the data in the AutoKeep Display window.\nModify main storage\nOvertype the value in the Keep Window or type D to the left of a variable. Place the cursor under the variable and\npress Enter for a CORE Main Storage display. On the CORE screen, overtype the values and press Enter.\nSet an uncondition\nal \"before\" breakpoint\nType U to the left of an instruction and press Enter.\nRemove a breakpoint from the Monitoring Status display\nUse PF12 to view Monitoring Status. Type R next to a UBP and press Enter.\n 1357", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "747173e757c3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nRemove a breakpoint from the Source Listing Display\nOn Source Listing, overtype U with X and press Enter.\nResume program execution\nUse the RESUME command or PF5.\nDWARF FAQ\nThis page contains frequently asked questions regarding DWARF and its integration into InterTest.\nHow long has DWARF been available?\nDWARF was developed by Brian Russell, Ph.D., at Bell Labs in 1988. IBM introduced DWARF support for COBOL 5 in\n2013.\nIs there DWARF support in both InterTest Batch and InterTest for CICS?\nCurrently, the InterTest INC05 enables the DWARF functionality only in the InterTest for CICS base product.\nDoes this mean I can eliminate all my Symbolic Files when I adopt InterTest with DWARF?\nYes, after you recompile all your program sources written in COBOL v5 using the TEST(SOURCE) compiler option.\nHow do you recommend we approach converting to DWARF?\nYou can adopt a gradual approach and use both DWARF and PROTSYM at the same time. The SYMBOLIC\nInterTest global option in IN25OPTS can be used to adjust your preferences so you can transition to using DWARF only.\nHow will a developer know if they require a symbolic file or not when they start a DEBUG session?  Is it obvious\nto them?\nIt depends on the SYMBOLIC option you set, and whether you have an available PROTSYM, DWARF data, or any\ncombination. The monitoring status displays either a *DWARF* label or the name of a PROTSYM depending on the\nselected SYMBOLIC option.\nHow do I report a DWARF issue?", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "747173e757c3-1", "text": "selected SYMBOLIC option.\nHow do I report a DWARF issue?\nOpen a regular support ticket through https://support.broadcom.com/  and indicate that it is related to DWARF.\nDoes the TEST(SOURCE) compiler option cause any performance issues, such as the compile step running\nlonger or the load module take up more space in my load libraries?\nNo significant compilation delays should occur. The extended source code is attached to the load module during\ncompilation and will increase the load module footprint on the disk. The source is part of the NOLOAD section so it does\nnot increase the footprint in the memory when loaded.\nCan I debug a composite program with mixed symbolics?\nA composite load module consists of multiple subprograms linked together. You can debug composite subprograms\nusing DWARF. There is however a limitation when it comes to mixed symbolic support. You cannot use DWARF for one\nsubprogram and PROTSYM for another subprogram in the same composite module. You need to either use DWARF or\nPROTSYM for all subprograms within a single composite module. However, you can use DWARF for one load module\nand PROTSYM for a different one.\nAm I limited to use DWARF or PROTSYM only?\nYou can use both. Your preference can be set using the SYMBOLIC InterTest global option in IN25OPTS. The global\noption is applied to one CICS region. You have 7 options which vary from \u201cPROTSYM only\u201d, to \u201calways ask\u201d, to \u201cDWARF\nonly\u201d.\nDoes SymDump have support for DWARF?\n 1358", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "117bacff0691-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDWARF support was introduced only for InterTest for CICS. SymDump does not have DWARF support.\nHow does DWARF affect my compile listings stored in Endevor ?\nThere is no impact at all. The only change to your compile listing is the presence of the TEST(SOURCE) option in the list\nof used compile options.\nIs Dynamic Symbolic Support affected by DWARF?\nDynamic Symbolic Support automatically retrieves listings from Endevor  and stores them in the PROTSYM if the\ncorresponding listing is not found in the PROTSYM. In essence, Dynamic Symbolic Support is just an extension for\nPROTSYM. DWARF does not affect it in any way and you can still use both DWARF and PROTSYM depending on your\npreference.\nDoes the InterTest Eclipse plugin have support for DWARF?\nDWARF support is a recently integrated feature in InterTest, and is currently only supported from the classic CICS\ninteractive UI.\nUsing the Eclipse UI\nThis section describes how to use the Eclipse UI to debug CICS and batch applications. Use the Eclipse UI and this\ndocument to walk through the process and procedures that follow.\n  \nTIP\nTip: This section contains tutorial instructions that step you through debugging a program with the Eclipse UI.\nWhen you see instructions that prompt you to make specific changes a debug session, use the information as\nan example, or complete the tutorial by following the steps as instructed. The tutorial uses the default InterTest\nfor CICS library names. \nTo perform the steps in this tutorial, you must know the following information. If you do not already know this information,\nor if the default demo program names were changed during installation, contact your InterTest administrator.\n From your IBM installation  \n\u2022User ID", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "117bacff0691-1", "text": "From your IBM installation  \n\u2022User ID\n\u2022z/OS host name\n From InterTest \n\u2022Path to the file containing Testing Tools server settings to be imported. If the application was installed properly, you\nhave a set of servers that are properly configured for your site.\n\u2022InterTest for CICS PROTSYM data set names\n For the CICS demo sessions, you also need the following information:  \n\u2022CICS host name\n\u2022Path to the file containing InterTest server settings to be imported\nSynchronized Processing\nThe application searches the symbolic files for the programs that you specify to be monitored for testing and tries to match\na symbolic file with the same date and time as that of the load module. If a match is not found, the Select Symbolic dialog\nopens. If this dialog appears, do one of the following:\n 1359", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "42a55939623b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Select the version that you want the mainframe debugger to use and click Use.\n\u2022If you do not want to monitor the file, select Do Not Monitor.\n\u2022For batch applications, you can click Abend Stop to end the debugging session.\nUse this feature to maintain synchronized processing at all times.\nOnline Help\nInterTest provides extensive online documentation and context-sensitive help. You can request online help anytime while\nusing InterTest by clicking the Help menu and selecting the following options as needed.\nHelp Contents\nOpens an external Help browser window and displays a top-level link to the InterTest online documentation, which\nyou can expand to display subsets of the documentation.\nSearch\nActivates the InterTest online Help view and displays the Search panel in which you can enter text that you want\nto search for. Click Go to display all topics on the online documentation in which the search text appears.\nDynamic Help\nDisplays the help data as it is dynamically displayed to reflect the context of the view that is in focus. For example,\nwhen the focus is on Breakpoints, Dynamic Help will only display those topics relevant to breakpoints.\nNote : The dynamic help feature is not supported in the Program Listing area pop-up menus, window controls\nsuch as menu items or buttons, or toolbar buttons.\nCheat Sheets\nOpens pages to guide you through some of the processes. Each cheat sheet is designed to help you complete a\nspecific task, and lists the sequence of steps required to help you achieve that goal.\nKey Assist\nOpens the Key Assist window where you can see shortcut key combinations.\nUpdate InterTest\nOpens the Install/Update dialog from which you will be able to install updates of the currently installed features, or\nnew features.\nAbout InterTest\nDisplays the About InterTest dialog, which provides information on the software release number, plug-in details,\nand configuration details.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "42a55939623b-1", "text": "and configuration details.\nF1 Support\nYou can access online Help for most (but not all) window controls by placing the focus on the dialog or control and\npressing F1.\nIf the control is located in the InterTest main window, the Help view is activated automatically and a keyword search\ntargeting text in the online documentation related to the control is performed. When the search is complete, links to topics\nrelated to the keyword search are displayed in the Help panel.\nIf the control is located on a dialog started by InterTest, an external Help window is activated. The same keyword search is\nperformed and links to topics related to the keyword search are displayed in the Help panel.\nDynamic Help\nWhen the InterTest Help view is active in InterTest as you make each view active, the help data displayed is dynamically\nupdated to mirror the view that is in focus.\n 1360", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "35ea563d0954-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nVisual Debugger\nThe Visual Debugger provides a visual representation of a running CICS COBOL transaction or COBOL batch program.\nUsing this, you can view the trace data that is represented by the graph structure to become better oriented with the\nexecution flow.\nDemo Source Programs\nInterTest for CICS installs demo programs to use for this tutorial that are designed for use with the InterTest for CICS\nEclipse UI tutorial. Use the compile procedures created during installation to compile a demo program, populate the\nPROTSYM, and link the program.\nNOTE\n The default names for the demo programs for each type of application may have been changed by your\nInterTest for CICS administrator during installation.\nCICS Demo Source Programs\nThe demo CICS source programs are as follows:\n Name of Program   Language Type  Transid \nCOBDEMO Enterprise COBOL DEMC\nDB2DEMO Enterprise COBOL DEMD\nPLIDEMO PL/I DEMP\nASMDEMO Assembler DEMA\nBatch Demo Source Programs\nThe demo source programs for batch applications are as follows:\n Type of Program  Name of Program  \nAssembler CAMRASM\nCOBOL CAMRCOBB\nPL/I CAMRPLI\nUnderstanding Your Workspace\nMain Window\nThe InterTest and SymDump  Eclipse UI contains a group of views that provide all the functions you need to debug your\nprograms.\nA view is a visual component within the application window. It is typically used to navigate a hierarchy of information or\ndisplay properties for a program listing, which displays the program being debugged. Modifications made in a view are\ngenerally done with dialogs. A perspective is a collection of views that pertain to a single product.\nThe following illustration shows the main window in the InterTest perspective with several views open.\n 1361", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "149bd58e267b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUsually, only one instance of a particular type of view may exist within the main window. Views can appear by themselves\nor stacked with other views in a tabbed notebook. To activate one of these views, click the appropriate tab. Only one view\nis active at one time, with the exception of the Program Listing area, where several imported program listing files can be\nopen at one time. The listings behave like sub-views that are grouped together (or stacked) in the Program Listing area.\nYou can change the default window layout by opening views, closing views, or docking views in different positions.\nToolbars\nThere are two kinds of toolbars in the InterTest and SymDump  Eclipse UI:\n\u2022Main toolbar\n\u2022View toolbar\nThe main toolbar  is displayed at the top of the main window directly beneath the menu bar. The contents of this toolbar\nchange based on the active view. You can find explanations of all the buttons on the toolbar in the online help.\nThere are also individual view toolbars , which appear in the title bar of a view. Actions in a view's toolbar apply only to the\nview in which they appear. The following example shows the Bookmarks view toolbar:\n 1362", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4c0dd4c42409-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nSome view toolbars include a Menu button, shown as an inverted triangle, that contain actions for the view.\nPerspectives\nThe Eclipse UI has one perspective for InterTest and another for SymDump . You can switch from one product to the other\nwithout closing the Eclipse UI, but you must always have at least one perspective open. \nTo open a perspective, select Window, Show perspectives. When the Open Perspective dialog appears, click the\nperspective that you want to open. The main window updates to show the perspective that you selected..\nViews\nThe InterTest and SymDump  Eclipse UI supports the following types of views:\nAuto Data\nDisplays variables and their contents at a particular breakpoint.\nBookmarks\nDisplays all anchors (bookmarks) placed on a specific line of code.\nBreakpoints\nDisplays all breakpoints (enabled and disabled) that are set in the vertical ruler of the Program Listing area.\nCall Trace\nDisplays a list of the called subprograms in a load module based on the current breakpoint. This is a CICS only\nview.\nConsole\nDisplays read-only standard output messages from InterTest.\nError Log\nDisplays all warnings and errors generated by the common user interface. This is used by Broadcom Support  and\nyou can export this log when reporting an error.\nHelp\nDisplays the related help topics for the highlighted view.\nInterTest Debug\nDisplays the monitored and unmonitored programs.\nOutline\nDisplays an outline of the program that is currently open in the Program Listing area and lists the structural\nelements.\nProperties\nDisplays a list of attributes, if any, related to another active view. Not all views have information to display in this\nview.\nRegister Data\nKeeps track of general register values during a debugging session for Assembler programs.\nServers", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4c0dd4c42409-1", "text": "Keeps track of general register values during a debugging session for Assembler programs.\nServers\nDisplays the servers that have been defined for InterTest to communicate with the mainframe.\nSession Data\nKeeps track of session-related information during a debugging session for CICS programs.\n 1363", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1ce5f3c5214c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nStatement Trace\nDisplays a trace of previously executed statements.\nTasks\nDisplays the tasks available for the currently active program.\nWatch Data\nKeeps track of variables and other program-related information during a debugging session.\nUse views to navigate a hierarchy of information (such as variable values), show breakpoints, bookmarks, console output,\nand various other activities.\nThe application saves any changes you make in a view across instances of the Eclipse UI.\nTo open a view, select Window, Show views, and then click the view that you want to open. The selected view opens in\nthe main window.\nTo close a view, click on the X on the view's tab.\nYou can perform the following actions with the buttons on the Bookmark's toolbar, as described in the following table:\nButton Description\nConfigures the settings for the program name\nShows the position in the program listing where the breakpoint is\nset\nConfigures a selected breakpoint\nDeletes a selected breakpoint.\nAdds a global breakpoint\nMinimizes the view.\nMaximizes the view.\nDebugging with the Eclipse UI\nThis article describes how to use the Eclipse UI to debug a program.\n 1364", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d674e8095ad4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFigure 1: Debug-EclipseUI\nConnect to a Server\nBefore you begin debugging a program, you must connect to a server. You can import server setting and you can add new\nserver connections to the Eclipse UI.\n 1365", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bf463f402792-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nImport Broadcom  Testing Tools Server Settings\nConnect to a Testing Tools server before, start a debugging session. The GUI component runs on Windows and the\ndebugging session runs on z/OS. This server provides the communication between the Eclipse UI and the mainframe\nplatform.\nYou may need to import the Testing Tools server settings the first time you start the Eclipse UI component or whenever\nyour InterTest administrator updates any of the server settings.\nIf the application was installed properly, you have a set of servers that are properly configured for your site.\nFollow these steps:\n1.Start the InterTest Eclipse UI.\nThe InterTest main window opens.\n2.Click File, Import.\nThe Import dialog opens.\n3.Click Next.\nThe Import Server Settings dialog opens.\n4.Type or browse for the file path to the file containing the server settings. Obtain this information from your InterTest\nadministrator.\n5.Click Finish.\nYou are connected to the specified server.\nAdd a New Server Connection\nIf you have not already established a connection to the server that you want to use, you can add a server connection\nusing the Eclipse UI. You must have the host and port details of the server to which you want to connect.\nFollow these steps:\n1.Select InterTest, Add New Server.\nThe New Server Connection  dialog opens.\n2.Enter the details for the new server connection.\nThe following field values are required to create a new server connection:\nName\nSpecifies the name of the server connection. You can use uppercase and lowercase alphanumeric characters,\nand embedded spaces when entering a value in this field.\nTIP\nFor the purposes of this tutorial, specify the name Basic Demo in this field.\nHost\nSpecifies the z/OS host name assigned by your installation. This is the host name used for TSO or CICS logon.\nPort", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bf463f402792-1", "text": "Port\nSpecifies the TCP/IP port number of the server. If there is a default port number displayed, verify it is correct. The\nport number is updated in the Preferences dialog.\n\u2022For a CICS region -- This field must be the port number configured in the CICS region.\n\u2022For a Testing Tools server -- This field must be the port number that is configured for the Testing Tools server\nrunning on z/OS UNIX System Services (USS).\nUse as Default Server\nSpecifies that this server is selected when you access the Batch Link Queue or Schedule Table.\n(Optional) User ID\nSpecifies the user ID for logging on to a z/OS system. Enter your user ID in this field.\n 1366", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "703d65cbe3ea-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n(Optional) Save Password\nSpecifies whether you want to save the password. If you save the password, the application preloads the saved\npassword into the Logon dialog whenever you are prompted to enter your user ID and password. Until the\npassword is deliberately reset or a logon fails, you are prompted for a user ID and password only when you first\nuse a server. Check this box to save your password.\n3.Click Finish.\nThe new server is created and added to the list of servers in the Servers view. The Servers view shows the details of\nthe new server.\nCheck the Server Status\nThe Server view displays the status of the servers you are connected to so that you can see if the server is active.\nFollow these steps:\n1.Click Window, Show Views, Servers, on the InterTest main window toolbar if the Servers view is not already visible.\nThe Servers view opens, displaying the name of the server and its status.\nThe server has one of the following statuses:\nAvailable\nThe GUI is connected to a mainframe server that is running.\nNot Available\nThe GUI failed to connect to the server and is not running. The reason for the failure is noted next to the server\nstatus.\n2.If the Status column is blank, click the Refresh Server button\non the Servers view toolbar.\nThe system may take several seconds to respond.\n3.If the status remains blank or Not Available, contact your InterTest administrator.\nCreate a Project\nAfter you are connected to a Broadcom  Testing Tools server, create a project in which to debug your program.\nFollow these steps:\n1.Click the Create Project  button\non the InterTest main window toolbar.\nThe New CICS Project dialog opens or New Batch Project dialog opens, depending on the demo session.\n2.Specify a name for your project in the Project Name  field.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "703d65cbe3ea-1", "text": "2.Specify a name for your project in the Project Name  field.\nTIP\nTip: Specify Basic Demo  in the Project Name field for the Eclipse UI tutorial. The rest of this procedure uses\nthis demo value.\n3.Check the Use default location  box if it is not already checked.\n4.Select Basic Demo  from the InterTest Server drop-down list.\n5.For CICS applications, insert your CICS Application ID .\nNote:  Do not select Import files once project is created .\n6.Click Finish .\nThe InterTest Debug view displays your project name, project type, the server name, the status indicator, and two\nempty folders: Monitored, and Unmonitored.\n 1367", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "209c63707a4c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nConfigure the Debug Settings\nBefore you execute a program, set the debug settings for your project. The debug settings dialog is different for CICS and\nbatch applications. This dialog is also displayed when you start the program execution.\nConfigure Debug Settings for CICS Applications\nFollow these steps:\n1.Right-click the project name on the InterTest Debug view, and select Configure Session Debug Settings.\nThe InterTest Debug Settings dialog opens.\n2.Ensure that the following fields are completed:\nInterTest Server\nDisplays the Testing Tools server name.\nCICS Region\nDisplays the CICS region name.\n3.Click Finish.\nThe debug settings are configured.\nConfigure Debug Settings for Batch Applications\nTIP\nThe specific values in this procedure apply to the demo program tutorial.\nFollow these steps:\n1.Click the project name on the InterTest Debug view, right-click, and select Configure Session Debug Settings.\nThe InterTest Debug Settings dialog opens with the main tab in view.\n2.Click the InterTest Server drop-down list, and select Basic Demo.\n3.Select the PROTSYM tab.\n4.Click Add, and add CAI.PROTSYM as the PROTSYM data set name, or the data set name provided by your InterTest\nadministrator, in the Add Dataset Name dialog. Click OK.\nThe data set name appears in the PROTSYM Datasets area.\n5.Click the JCL Settings tab.\nThe InterTest Debug Settings dialog opens.\n6.Complete the following fields:\nInterTest Server\nDisplays Basic Demo. If Basic Demo is not showing, select it in the box.\nConversion JCL Dataset(Member Name)\nDescribes the mainframe data set name and member name. Type CAI.CAVHJCL(DEMOJCL) or a data set name\nprovided by your InterTest administrator.\nDataset Type", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "209c63707a4c-1", "text": "provided by your InterTest administrator.\nDataset Type\nDescribes the type of data set. Select IBM PDS, or the data set type appropriate to the one provided by your\nInterTest administrator.\nJob Step Name\nDescribes the name of the job step. Type Step1 .\nPROCLIB List\nLeave empty.\nConverted/Submit JCL Dataset(Member Name)\nDescribes the output data set where the converted JCL resides. Type HLQ.MYJCL(BATCHDMO), where HLQ is\nthe high level qualifier you choose, or any allocated PDS.\n 1368", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "db1fd1e6191c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n7.Click the Convert JCL button.\nThe converted JCL is placed in HLQ.MYJCL(BATCHDMO).\n8.After the JCL conversion is complete, click the Edit JCL button to edit the converted JCL.\nThe Edit JCL dialog opens.\n9.Make the following changes to the Edit JCL dialog:\n\u2013Change the job card to conform with your installation standards.\n\u2013Change PROFILE=YOURID to PROFILE=(your TSO User ID).\nThe following illustration shows the edited JCL:\n10.Make sure the data set you are editing is not being used in TSO or Roscoe .\n11.Click OK.\nThe Edit JCL dialog closes and you return to the InterTest Debug Settings dialog.\n12.Click Finish.\nYou receive a message indicating that the file has been saved successfully. Click OK. You return to the InterTest main\nwindow.\n 1369", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a274abda76f9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSelect the Source Program to Monitor\nAfter configuring your session, specify the program that you want to monitor. As part of monitoring a program, the\napplication automatically prevents all abends during execution.\nFollow these steps:\n1.Verify that the program to be debugged has been compiled and post-processed into the PROTSYM files.\n2.Click the InterTest Debug view so that it is the active view.\n3.Click the project name on the InterTest Debug view.\nThe project name is highlighted.\n4.Click the Import PROTSYM Files button\non\nthe InterTest main window toolbar.\nThe Import PROTSYM Files dialog opens.\n5.Enter the following information:\nInterTest Server\nDefines the Testing Tools server. For the tutorial, select Basic Demo.\nPROTSYM Data Set\nDefines the fully qualified data set name of the PROTSYM VSAM file.\nType CAI.PROTSYM, or substitute CAI.PROTSYM with the DSN provided by your InterTest administrator.\nIf you receive an error about failure to retrieve a member list, check with your InterTest administrator.\nNote : You may be prompted to log on to your mainframe TSO here, if you have not already done so.\n6.Click List Members.\nThe table is populated with the programs in the data set you chose.\n 1370", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ed6044cb6667-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n7.Scroll down through the table until you reach the program that you want to use. Select the program by checking the\nbox next to it.\n8.If the Into folder box is empty, click the Browse button, and select the Basic Demo folder to import the program into.\nThe name Basic Demo appears in the Into folder box.\nNOTE\nThe InterTest administrator may have changed the name of the sample programs when installing the\napplication. If you do not see the name of the demo program that you want to use, check with your InterTest\nfor CICS administrator to find out the correct name.\n9.Ensure that the two check boxes in the Options section are selected.\n10.Click Finish.\nThe demo program displays in the InterTest Debug view in the Monitored Programs folder.\n11.Double-click the demo program name on the InterTest Debug view.\nThe program listing displays in the Program Listing area, with an outline of the program in the Outline view.\n 1371", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d52840ac281b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nHow to Use the Outline View\nThe Outline view displays an outline of the program that is currently active in the Program Listing area and lists the\nstructural elements. This makes it easier to display any section of your program. The contents of the Outline view are\nspecific to the active program listing. The Outline view contains a top level node for each action.\n\u2022To expand a node, click the plus sign (+) next to the text.\n\u2022To collapse a node, click the minus sign (-) next to the text.\nNOTE\nSelecting a variable or label name repositions the program listing to the line containing the name. If the\nlocation is collapsed, the area is automatically expanded.\nView Monitoring Status\nThe InterTest Debug view lists the programs in a tree that identifies them as monitored or unmonitored. You can view the\nprograms under these categories by clicking the plus (+) to expand the Monitored and Unmonitored nodes.\nStart Program Execution\nThe process to start the program execution is different for batch and CICS applications. Follow one of these procedures to\nbegin debugging your program.\nFor Batch Applications\nFollow these steps:\n1.Select the program that you want to monitor under the Monitored node in the Debug view.\n2.Click the green bug button\non the toolbar.\nThe batch job is submitted and the initial intercept is displayed.\n3.Click the green arrow button to allow the program to run.\nThe program will run until it encounters an abend.\nFor CICS Applications\nFollow these steps:\n1.Under the Monitored node on the InterTest Debug view, select the program that you want to monitor and click the\ngreen bug button\non the toolbar.\nThe InterTest Debug Settings dialog opens.\n2.Ensure that the debug settings are defined as you want them.\n3.Click Connect.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d52840ac281b-1", "text": "2.Ensure that the debug settings are defined as you want them.\n3.Click Connect.\nInterTest notifies InterTest for CICS that your program is ready for debugging .\n4.Go to the mainframe CICS display (green screen), and type in the transaction identifier of the demo program.\n5.Press Enter.\nThe Welcome screen appears.\n6.Press Enter on this CICS mainframe screen.\nThe demo program begins execution. Your CICS session will indicate that it is in xSystem state:\n 1372", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b7cbfbcdb95c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n1.Return to the InterTest Eclipse UI to continue with your debugging session. Notice that the InterTest Debug view now\ndisplays the debug status as Debugging.\nAnalyze Abends\nWhen a program encounters an error during execution, an abend occurs. See Abend Analysis with the Eclipse UI for more\ninformation about addressing abends that occur during program execution.\nResume Program Execution\nResume the program execution after evaluating and resolving an error that the program identified or after the program has\nstopped at a breakpoint.\nFollow these steps:\n1.Click the Step Once button\non the InterTest Debug view toolbar to continue testing by resuming program execution.\n2.Program execution stops at the next statement. The debug status in the InterTest Debug view indicates that the\nprogram is at a single-step breakpoint and that shows the value that you updated in resolving the previous abend.\nThe following example shows the results of this step for the CICS COBOL demo.\n 1373", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2a4ba27227e2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n3.Click the Resume Debugging button\non the InterTest Debug view toolbar.\nThe demo program halts at the unconditional breakpoint you set previously in this tutorial. The InterTest Debug view\nwindow updates to reflect the reason for the stop\n4.Click the Resume Debugging button again.\nThe program continues until no further abends, breakpoints, or bookmarks are encountered.\n5.When the program completes, do one of the following actions to end the debugging session.\n\u2013For batch applications, the demo program displays the Debugging dialog to indicate that the program is complete.\nClick OK to terminate the debugging session. The tutorial is finished.\n\u2013For CICS applications, the mainframe CICS screen displays the END DEMO SESSION screen. Press Clear or\nEnter on the mainframe CICS screen to end the CICS debugging session and then complete the next two steps.\n6.In the Eclipse UI, click the Cancel Debug Session button\non the InterTest Debug view toolbar.\nThe Cancel Debug Session dialog opens.\n7.Click the Disconnect and Remove Breakpoints button, and then click Finish to terminate the connection with the\nserver.\nThe debugging status now shows Debugging Inactive in the InterTest Debug view.\nAbend Analysis with the Eclipse UI\nWhen a program encounters an error during execution, an abend occurs and stops the program. This article describes\nhow to identify and fix the cause of an abend before resuming the program execution.\nAt the abend, the following events occur:\n\u2022The appropriate program listing causing the error is activated (if the program was not displayed earlier).\n\u2022The program positions itself at the statement causing the error.\nWhen the program stops, we say that it halts the program at a breakpoint. This is done automatically when an abend\noccurs, or the application halts a program at a breakpoint that you have previously set.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2a4ba27227e2-1", "text": "occurs, or the application halts a program at a breakpoint that you have previously set.\n 1374", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dc2faac5198b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWhen an abend occurs:\n\u2022A small blue arrow appears in the ruler to the left of the line causing the error, and the line is highlighted.\n\u2022The status in the InterTest Debug view now displays a diagnostic message. This message explains that the error was\ncaused by improperly formatted data.\nTIP\nIn the tutorial, the demo program detects an error at the ADD instruction. Execution of that ADD instruction\ntriggers an abend.\nOnce a program is stopped, you can use the InterTest testing and debugging facilities to do the following tasks. When\ndebugging your own programs, you will typically perform one or more of these activities.\n\u2022Examine the source listing.\n\u2022Examine and modify main and auxiliary storage (memory) to detect and correct errors.\n\u2022Set and remove breakpoints and bookmarks.\n\u2022Examine a program's statement trace.\n\u2022Keep data items in a watch view to observe changes in their values.\n\u2022Abend your task with or without a dump.\n\u2022Go around a problem by resuming program execution from a location other than the one at which the program is\ncurrently stopped.\n\u2022Execute the program in single-step mode; that is, the program executes one verb and then stops.\nDetermine the Cause of an Error\nUse the Auto Data view to see the values of the variables that are associated with a statement. Use the Watch Data view\nto see the value of data items that you want to watch.\nExample:\nIn this example, an Assembler program has encountered an error at the TASKNUM statement. The value of TASKNUM\nis displayed as an expression (%R13+189) in the Auto Data view. The left column shows the base + displacement for\nthe name of the data item. In the columns to the right are the field's display value. Assembler programs show as Memory", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dc2faac5198b-1", "text": "Expression, and hex value at that offset.\nLook at the contents of TASKNUM. Confirm that the value stored in TASKNUM is not a valid packed decimal value by\nexamining its current value in the Auto Data view; that is, its value prior to the execution of the AP statement that triggered\nthe ASRA. Instead, it contains low-values (binary zeros - the three highlighted bytes). Assembler does not allow you to\nadd a packed decimal value (=P\u20191\u2019) to a field initialized with low values.\nChange the Value in TASKNUM for COBOL and PL/I Applications\nYou have identified and confirmed the cause of the problem. Now you want to fix it.\n 1375", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "edebd13ba49d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFollow these steps:\n1.Right-click the variable TASKNUM in the Auto Data view. Click Change Value.\nThe Data View Value dialog opens.\n2.Select the Display value button.\n3.Change the value of TASKNUM displayed in the box to a numeric zero (type a numeric zero).\nNOTE\nYou do not have to know the type of data (binary, packed, and so on) or the length of TASKNUM. You can\nchange the contents of a field by overtyping the desired bytes.\n4.Click OK.\nTASKNUM now contains a packed decimal zero.\nChange the Value in TASKNUM for Assembler Applications\nFollow these steps:\n1.Right-click one of the following variables in the Auto Data view\n\u2013%R13+189 - for CICS applications\n\u2013%R13+634 - for batch applications\n2.Click Memory Dump.\nThe Memory Dump dialog opens and displays the memory address for TASKNUM in the Address column. To the right\nunder offset +0 the hex value displays, to the far right is the character value. The first three bytes (highlighted yellow)\nare the value of TASKNUM.\n3.Click the Variables button, type TASKNUM, and click the Fetch button.\nThe Memory Dump dialog opens, and the three bytes of TASKNUM display.\n4.Overtype 000000 with 00000C, and press Enter.\n5.Click Close.\nThe Auto Data view now displays TASKNUM with a packed decimal zero.\n 1376", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0c670fffd953-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBreakpoints\nA breakpoint is an intentional stopping or pausing place in a program, put in place for debugging purposes.\nWhen you open or activate a program listing in the Program Listing area, the breakpoints added to that program are\nmarked with a blue circle icon. When the mouse hovers over a blue circle, the following details of a breakpoint are\ndisplayed:\n\u2022Breakpoint type\n\u2022Program name\n\u2022Statement number (in square brackets)\n\u2022Source code text\nThere are six types of breakpoints.\nAutomatic\nThe program stops because InterTest for CICS detected and prevented an error. When a program is stopped at an\nautomatic breakpoint, you can either correct the error or go around it. You set all other breakpoints.\nConditional\nThe program stops at the location you specify if a condition is met. Optionally, conditional breakpoints can be set\nto stop at any instruction if a condition is met.\nRequest\nThe program stops at every CICS command or macro, at certain CICS commands or macros, or at calls to PL/I,\nDB2, or software.\nSingle-step\nThe program stops after executing one or more verbs.\nUnconditional\nThe program stops at the location you specify, just before the statement is executed.\nVariable Change\nThe program stops at any location if the value of a specified variable has changed. This is a special type of\nconditional breakpoint.\nExample:\nIn this example, execution stops just before the statement Add +1 to TaskNum is executed. A blue arrow points to that\nstatement. This illustration displays the information when the mouse hovers over a blue circle.\n 1377", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "74fcfe4edbf6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWhen to Use Breakpoints\nYou can set breakpoints at any time -- before you execute the program and when the program is stopped. Although where\nyou decide to set breakpoints depends on the specifics of your program, you might want to set breakpoints in the following\nplaces:\n\u2022At the beginning of the Procedure Division, so when the program executes you can set additional breakpoints\n\u2022At paragraph names, so you can examine the contents of variables at the start of sections\n\u2022Before a call, so you can dynamically control the program path\n\u2022At each location named in an EXEC CICS HANDLE CONDITION, so you can verify error handling\nSet Unconditional Breakpoints\nAt an unconditional breakpoint, the program stops at the location you specify, just before the statement is executed. Let\nus see how to set a breakpoint at the following IF statement. You set unconditional breakpoints directly on the Program\nListing area.\nFollow these steps:\n1.Click the demo COBOL program listing on the Program Listing area, so its name is highlighted in its tab.\n2.Press <Ctrl> + F on your keyboard.\nThe Find/Replace dialog opens.\n3.Type If Tasknum Greater 2 in the Find box, and click Find.\nThe demo program positions itself so that the line you searched for appears in the program listing.\n 1378", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "affd05c0d638-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n4.Right-click the ruler to the left of the line you have selected (statement 484), and select Add Breakpoint.\n 1379", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b8412ce69573-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nA blue circle appears to the left of the ruler, and a blue mark appears in the right-side vertical ruler. By default, the Add\nBreakpoint dialog adds an unconditional breakpoint if the listing line is within the Procedure Division, and a variable\nchange breakpoint if the line is within the Data Division.\nNote : You cannot add a breakpoint in a comment line or outside the source code section.\nChange Breakpoints - CICS\nThe process for changing breakpoints is different for CICS and batch applications. The following procedure describes how\nto change a breakpoint in a CICS application.\nFollow these steps:\n1.Right-click the blue circle to the left of the line that contains the unconditional breakpoint that you want to change, or\ndouble-click the breakpoint in the Breakpoints view, and select Configure Breakpoint in the dialog.\nThe Update Line Breakpoint dialog opens.\n2.Select Conditional breakpoint under Breakpoint Type.\nThe other fields become active.\n3.Click the Variable List button, and select TASKNUM from the Variable List.\n4.Click the Literals button and change the literal value to the new value where you want the breakpoint.\nThe following illustration displays the finished dialog showing a conditional variable at TASKNUM=x'00003c'.\n 1380", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "edf16034d515-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n5.Click Finish.\nThe dialog closes and the breakpoint displays in the Breakpoints view as a conditional breakpoint.\n6.Repeat steps 1 through 5, and make statements 480 and 482 unconditional breakpoints.\n7.Change the breakpoint at statement 484 back to an unconditional breakpoint.\nChange Breakpoints\nThe following procedure describes how to change breakpoints in batch applications.\nFollow these steps:\n1.Right-click the blue circle to the left of the line where you have set an unconditional breakpoint, and select Configure\nBreakpoint in the dialog.\nThe Update Line Breakpoint dialog opens.\n 1381", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c4120ca0281d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n2.Click the Conditional breakpoint option button.\n3.Change the fields as follows:\nLeft Side  - LOOP-OUT\nOperator  - GT - Greater Than\nRight Side  - x'00'\nNote : Character literals do not need to be prefixed with a C. The system automatically recognizes them as characters.\nThus, 2 is treated as F2, whereas hex literals must be prefixed with an X.\n4.Click Finish.\nThe dialog closes and the breakpoint displays in the Breakpoints view as a conditional breakpoint.\nHow to Delete Breakpoints\nAs you continue testing and debugging it is good practice to delete breakpoints you no longer need, so that the program\nwill not stop unnecessarily.\nIt is easier to delete individual or multiple breakpoints from the Breakpoints view when you have a number set throughout\na large program and you do not want to search through the source listing for them.\nYou can delete breakpoints in the following ways.\nHover the mouse on the vertical ruler to the left of the statement whose breakpoint you want to delete, right-click, and\nselect Delete Breakpoint. The blue circle disappears, and there is no longer a breakpoint at this line.\n\u2022Select the breakpoint from the list of breakpoints in the Breakpoints view, right-click, and select Delete Breakpoint. You\ncan also use the <Del> (Delete) key. Do not delete the unconditional breakpoint set at statement 484.\n 1382", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0895bab5758e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nYou can use the Eclipse UI delete several breakpoints at one time, follow these steps:\nClick the first breakpoint on the Breakpoints view, hold down the Shift key, then click the last breakpoint you want to\ndelete.\nThe breakpoints you select are highlighted.\n\u2022Right-click and select Delete Breakpoint.\nThe breakpoints you select are deleted from the Breakpoints view and the program listing.\nBookmarks\nBookmarks help you to navigate quickly in the source code by marking individual locations. You can add and delete\nbookmarks as needed.\nThe Bookmarks view displays all bookmarks placed on a specific line of the program listing. The bookmarks appear in a\ntable format that provides a description of each bookmark, the name of the program where the bookmarks are located,\nfolder (path), and line number (location) in the Program Listing area.\nExample\nThe following illustration displays a sample Bookmarks view, showing three bookmarks in the C370DEMO program:\nNote : This view is not displayed unless you open the view by selecting Window, Show Views, Bookmarks on the InterTest\nmain menu.\nAdd Bookmarks\nYou can add bookmarks to your program to help you navigate quickly through the program.\nFollow these steps:\n1.Double-click the demo program on the InterTest Debug view.\nThe program listing displays in the Program Listing area.\n2.Select the statement where you want to insert the bookmark.\nThe listing is positioned at the line which includes the selected item.\n3.Right-click the shaded vertical ruler on the left side of the listing view, and select Add Bookmark.\nThe Add Bookmark  dialog opens, with the contents of the listing statement displayed in the Enter Bookmark Name\nfield.\n4.Edit the name (description) for the bookmark and click OK.\nA new bookmark is set at the selected statement. This is indicated by a small rectangle\nappearing", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0895bab5758e-1", "text": "A new bookmark is set at the selected statement. This is indicated by a small rectangle\nappearing\nnext to the scroll bar. The Bookmarks view displays the details of the new bookmark.\nIn the Bookmarks view, after you add a bookmark, you can double-click the bookmark to open the program listing, if not\nalready opened. The listing is positioned at the statement specified in the bookmark and highlights the statement.\n 1383", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "313c7da19cd1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nHow to Remove Bookmarks\nOnce you have created and used bookmarks, it is a good idea to delete them, so you do not clutter up your program or\nthe Bookmarks view.\nSelect the line of code that contains a bookmark, and perform one of the following steps:\n\u2022From the program listing left-hand ruler, right-click your mouse, and select Remove Bookmark from the pop-up menu.\n\u2022From the Bookmarks view, highlight the bookmark and click the Delete button (the red X) on the Bookmarks view\ntoolbar, or use the Delete key on your keyboard.\nThe bookmark is removed from the Bookmarks view and the program.\nVisual Debugger\nThe Visual Debugger is a visual representation of a running CICS COBOL transaction or COBOL batch program. View the\ntrace data that is represented by the graph structure to become better oriented with the execution flow.  \nGetting Started with Visual Debugger\nDisplays instructions on how to add the visual debugger view and how to configure CICS COBOL or batch programs for\nvisualization. \nVisual Debugger Key Features:\nStatement Trace Visualization\nSee the transfers of the control between monitored programs and the paragraphs.\nDynamic Graph Update\nProceed through the breakpoints and view dynamic updates to the graph.\nNavigate Execution Flow History\nNavigate through the history of the Execution Flow.\nLink with Editor\nUse the graph elements to easily locate the corresponding programs, paragraphs, and control transfers in the\nCOBOL source code.\nZoom and Pan\nZoom and pan the graph to focus on an area of interest.\nSave and Load Session Data\nSave debugging session data and analyze it later or forward it by email.\n \nGetting Started with Visual Debugger\nThe latest version of the Eclipse plug-in is required to run the InterTest Visual Debugger. The Visual Debugger view is the\ndefault part of InterTest perspective.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "313c7da19cd1-1", "text": "default part of InterTest perspective. \nIf you have hidden the Visual Debbuger view and want to show again, go to Window | Show View | Other .\nTo customize your visualization\n1.Expand the InterTest node and choose Visual Debugger.\n2.Click OK. \n 1384", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b4fec29c7506-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n3.Adjust the size and the position of a new view according to your\npreferences.\n4.Enable the 'statement trace' option in order to get the data that you need for the visualization during debugging.\n 1385", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3ded973b8d93-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nBatch project: Ensure that the Statement Trace and Notify at End of Task options are checked in the debug\nsettings.\nCICS project:  \nEnsure that the corresponding checkboxes are checked in the program settings of each monitored program.\n 1386", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3ca212320fee-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n5.Submit a job for debugging (Batch project) or connect to a CICS region and run a CICS transaction.\nThe graph appears once you start getting statement trace information.\nThe graph is dynamically updated until you hit a breakpoint or the execution finishes.\nStatement Trace Visualization\nThe visual debugger graph represents a traced execution flow. There are two visualization levels:\n\u2022Programs Level \n\u2022Paragraphs Level\n 1387", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aae3837dc903-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPrograms Level\nOn the programs level, each node represents a monitored program that was or is currently being executed. The executed\nprogram is marked with a blue border.\nThe arrows represent transfers of controls between the programs. The number on an arrow shows how many times the\ncontrol was passed from the program (represented by the arrow source node) to the program (represented by the arrow\ntarget node).\nRight click on an arrow to access the context menu that displays up to 3 of the last transfers. Click the context menu item\nthat represents the transfer to position your cursor in the editor of the statement that immediately precedes the transfer.\nDouble click any program node to switch the paragraphs level. You are also able to switch to the paragraphs level from\nthe context menu.\n 1388", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8e4e147ed93b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nParagraphs Level\nThe paragraph level nodes represent the executed paragraphs or the paragraphs in the middle of execution of the\nprogram. It also visualizes other monitored programs the control was transferred to or from during the execution. The\nprograms nodes have a darker background that allows for easier identification.\nFor example, DEMOGDAT is a program and GET-DATE is a paragraph.\nNavigation\nYou can use the breadcrumb navigation on the top of the Visual Debugger view.\nBoth at program and paragraph levels you can find the node representing currently executed programs or paragraphs.\nClick the Focus on Current Statement icon to locate the node.\nNavigate between the graphs using the arrows.\n 1389", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "88414257a28f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nVisualization of an Entry Point\nThe node that represents the first program executed in the debugging session is marked with a flag.\nWhen the first executed program is visualized on the paragraphs level, the first paragraph executed in the debugging\nsession is also marked with the flag.\nDynamic Graph Update\nThe graph is updated dynamically when the new debugging data is received.  When you hit a breakpoint, you  always\nreceive new data. \nThe layout is automatically adjusted during the addition of a new node or arrow.\nExample:  Place two breakpoints at the statements 000028 and 000034 in the DEMOMAIN program:\n000020 START-OF-PGM.\n000021 MOVE 'THIS IS MESSAGE FROM DEMOMAIN' TO MSG-TEXT.\n000022 PERFORM GET-DATE THRU GET-DATE-EX 3 TIMES. \n000023 PERFORM GET-NEW-INVOICES.\n000024 PERFORM PROC-INVOICE UNTIL INV-CNT = 0. \n000025 GO TO BATCH-RETURN. \n000026\n000027 GET-DATE.\n000028 CALL 'DEMOGDAT'. \n000029\n000030 GET-DATE-CONV.\n000031 CALL 'DEMOCDAT'. \n000032\n000033 GET-DATE-EX.\n000034 EXIT.\nExample Image Breakpoint at 000028:\nThe Visual Debugger view appears when the execution stops at the first breakpoint:\n 1390", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "47023864aced-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nThe GET-DATE paragraph is shown because statement 000028 CALL 'DEMOGDAT' belongs to this specific\nparagraph.\nExample Image Breakpoint at 000034:\nAt the second breakpoint, the graph view is updated.\n 1391", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "610160e66a48-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nGenerally the positions of the nodes are not determined and can differ every time the graph is redrawn. \nNavigate Execution Flow History\nNavigate through the execution flow history to analyze code behavior with ease.\nThe footer of the graph view displays a slider with the total number of statements executed since the debugging session\nwas started. This number is located in between the history slider and the zoom slide bar.\n 1392", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a78b4502ba3b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nClick and drag the slider back along the timeline to control which part of the statement trace is visualized. This\nfunctionality allows you to play back every event that has taken place since the beginning of the debugging session. This\nplayback is useful if you want to see what was executed after a specific statement, step-by-step, without time-consuming\ninspection of the statement trace.\nThe nodes that represent the latest statements disappear in the flow the further you go back in history.\nAdditionally, the history slider affects:\n\u2022The numbers on the arrows reflect how many times a transition of control occur between two corresponding programs\nor paragraphs.\n\u2022The context menu that appears when you right-click on an arrow, and shows up to three of the most recent transfers of\ncontrol.\n\u2022Annotations which appear in the editor when you click on an arrow and mark all the statements after the transfer of\ncontrol occurs.\nLink with Editor\nLink with Editor is the feature that allows you to link Visual Debugger graph elements with the source editor. Link with\nEditor enables the usage of Visual Debugger graph elements for switching between the code sections. Link with Editor\nfunctionality works in both directions and  allows to position the graph based on where the cursor is placed in the editor.\nBy default, the Link with Editor feature is turned on. To toggle it, you can use the corresponding toolbar button in the view.\nEnabling Link with Editor leads to the following behavior.\n 1393", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "98e0cd985c70-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNavigate in the Editor using Graph Elements\n1.Selecting a node that represents a program positions the cursor to the beginning of that program. The corresponding\ntab in the editor automatically opens and becomes active.\n2.Selecting a node that represents a paragraph positions the cursor to the beginning of that paragraph. The tab in the\neditor, which corresponds to the program with that paragraph, automatically opens and becomes active.\n3.Selecting an edge between programs A and B positions the cursor to the line in the program A, where the last\ntransition of the control to the program B occurred. This also applies to paragraphs level.\n 1394", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c710e997b87e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNavigate through the Graph using the Cursor\n1.Placing the cursor on any line will highlight the corresponding node (program or paragraph, depending on the current\nlevel of the graph) and position it at the center of the Visual Debugger view.\nPrograms Level:\nParagraphs Level:\n 1395", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a9ba466c1c22-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n2.Clicking on the Position at the breakpoint will have the same effect as manual placing of the cursor on the\ncorresponding line.\nZoom and Pan\nIn order to better view a graph that expands across the given user interface space, you can either click and drag desired\nnodes away from overlapping clusters, or zoom in on a specific area. You can pan the graph within the view.\n 1396", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "40ad5e215857-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nZoom In and Out\nYou can zoom in and out within the view to focus on a specific area of the graph by using the control in the bottom right\ncorner.\nPan the Graph\nIf you have a larger graph that expands outside of the given view, you can use panning to manipulate the image.\nNode Dragging\nYou can drag a specific node to provide an unobstructed view of node content.\nNOTE\nAny changes to manual node arrangement will not be saved.\n \n \n 1397", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fd41e17813bf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSave and Load Session Data\nYou are able to easily store trace data from a session that you are currently debugging into a .trace file. You can load data\nwithout the need to re-run the debugging session or connect to a mainframe.\nSave a Debugging Session\nTo save a debugging session, follow these steps:\n1.Right click and select Save debugging session. Alternatively, you can press S while the Visual Debugger View is\nactive. \nYour debugging session is saved in a .trace file inside your workspace. \nThe save trace dialog appears. \n 1398", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ac72b374c74d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n2.Specify the name of the trace file in the field and click OK.\nYour debugging session is saved.\nLoad a Debugging Session\nTo load a debugging session, follow these steps: \n1.Right click to load a debugging session. Alternatively, you can press L while the View is active.\n 1399", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "286111eee251-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n 1400", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5077b38bb2eb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n2.Select the session you want to load from the Trace Resource Selection window and click\nOK.\nNOTE\nThe projects currently being debugged are not listed.\n 1401", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a9de299db193-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe graph is redrawn to represent the loaded debugging\nsession.\nNOTE\nGenerally the positions of the nodes are not determined and can differ every time the graph is redrawn.\n 1402", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "522f2986e0d3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIntegrating\nIntegrate InterTest and SymDump with other solutions to extend the capabilities of the product and to expand the range of\nuse cases.\nInterTest and SymDump features the following integrations:\nSymbolic Support\nUse source code information from application programs to enhance and simplify the use of Broadcom Application\nQuality and Testing Tools products for z/OS.\nDebugger for Mainframe extension for VS Code\nA Visual Studio Code extension that provides a modern debugging experience for CICS and Batch programs\nwritten in COBOL.\nAbend Analyzer for Mainframe extension for VS Code\nA Visual Studio Code extension that allows you to view Abend reports in a modern IDE interface.\nSymbolic Support\nThis section is a reference for programmers who use the symbolic support features of Broadcom  Application Quality and\nTesting Tools.\nWhat is Symbolic Support?\nThe term symbolic support  refers to the use of source code information from application programs to enhance and simplify\nthe use of Broadcom  Application Quality and Testing Tools products for z/OS.\nSome of these products include:\n\u2022InterTest Batch\n\u2022InterTest for CICS\n\u2022Optimizer/II  /II\n\u2022SymDump  Batch\n\u2022SymDump  for CICS\nThese products provide application programmers with the critical tools that are needed to improve productivity\nthroughout the application life cycle. Symbolic support makes these products easier to learn and use by using terms that\nprogrammers recognize and understand from their own source code.\nFor example, using symbolic support with an interactive debugger like InterTest Batch lets programmers perform\nthe following actions:\n\u2022Enter breakpoint commands right on the source listing display.\n\u2022Stop execution at every label in a program.\n\u2022Automatically display the values of referenced variables at each statement.\n\u2022Easily display the value of any program variable.\n\u2022Set conditional breakpoints based on variable values.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "522f2986e0d3-1", "text": "\u2022Set conditional breakpoints based on variable values.\n\u2022View a trace of all previously executed source statements.\nSymbolic support eliminates the need to manually locate variables in storage, compute program offsets for source\nstatements, or determine which statements were executing. You do not need to keep program listings open while\ndebugging. These activities are done for you automatically when you use symbolic support with the Broadcom  Application\nQuality and Testing Tools products for z/OS.\n 1403", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8bc3e833a6d7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nHow Does Symbolic Support Work?\nWhen your application programs are compiled or assembled, symbolic information about the program is written to various\nreports in the output listing. A program that is called a postprocessor reads the output listing, collects the symbolic\ninformation, and stores it in a symbolic repository that is called a PROTSYM.\nUsing the listing postprocessors to collect symbolic information does not alter your program in any way. The listing that is\nproduced by your compiler or assembler is used only as input. Your object module is not altered. Only the PROTSYM is\nupdated.\nAfter the symbolic information is stored in the PROTSYM, you can access the information by the Broadcom  Application\nQuality and Testing Tools products to provide symbolic support for your application.\nNOTE\nInterTest for CICS also supports DWARF as a debugging format for COBOL 5 and above. DWARF debugging\ndata is stored in the target program rather than in a PROTSYM file. For more information, see DWARF.\nSymbolic Support for Optimized Applications\nBroadcom  Application Quality and Testing Tools support programs that are optimized by the COBOL compiler OPTIMIZE\noption or by Optimizer/II  or Optimizer/II . However, debugging and post-mortem analysis of these programs can sometimes\nresult in unexpected behavior.\nNOTE\nThe PL/I compilers are optimizing compilers.\nOften as part of the optimization process, a compiler relocates individual instructions, statements, or even entire\nparagraphs so that the optimized program runs more efficiently. This means that some or all of the instructions that\nare generated for a given statement might be moved to another statement, or that some or all of the statements in a\nparagraph might be moved to another paragraph. When this type of optimization occurs, the resulting object program and", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8bc3e833a6d7-1", "text": "paragraph might be moved to another paragraph. When this type of optimization occurs, the resulting object program and\ncorresponding listing may not accurately represent the relationship between the source statements and their generated\nobject code, or even between a paragraph label and the statements contained within the paragraph. As a result, there\nmay be times when the breakpoint intercept does not occur, or when the wrong sequence of statements appears to be\nexecuted while single-stepping, or when the abending object code does not correspond to the correct source statement.\nThere may also be times when the debugger appears to highlight the wrong statement at a breakpoint intercept or the\ndump analysis identifies the wrong statement as the abending source statement.\nThese unexpected displays do not indicate that a program is being executed incorrectly or that an abend is being\nincorrectly analyzed. These displays simply indicate that the debugger or dump analyzer sometimes cannot accurately\nidentify exactly which object code corresponds to which source statement, or which statement is contained within which\nparagraph.\nThe Broadcom  Application Quality and Testing Tools products use the information in the compiler-generated procedure\nmap or in the offset report to establish the program offset for each statement and label in the program. During execution\nor abend processing, the debugger or abend analyzer recognizes the start of the new statement or label by matching the\nprogram offset of the currently executing instruction with the PROTSYM information that is obtained from the compiler\nlisting. Therefore, the accuracy with which the debugger or abend analyzer can represent a breakpoint or other intercept\nor the abending statement is only as good as the information in the compiler listing.\nInaccuracies may include, but will not be limited to:\n\u2022Incorrect execution when using the SKIP, GO stmt# or CS stmt# commands\n\u2022Failure to stop at a breakpoint at a paragraph label or statement\n\u2022Unexpected or out of sequence highlighting of statements when single-stepping", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8bc3e833a6d7-2", "text": "\u2022Unexpected or out of sequence highlighting of statements when single-stepping\n\u2022Incorrect identification of the statement which contains the abending object code\n 1404", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a06a5952523b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAlso, application abends may result from the use of the SKIP, GO stmt# or CS stmt# commands because the optimized\nobject code may have register requirements that do not support changes to the flow of control. These commands should\nbe avoided when debugging an optimized program.\nFor the best debugging results, avoid using optimization when possible in your testing environment. Production\napplications may be compiled with optimization, and debugging these applications as they exist without recompiling is\nsupported. However, under these circumstances you may experience some of the previously listed inaccuracies.\nNOTE\nFor more information about debugging optimized COBOL and the OPTIMIZE option, see COBOL OPTIMIZE\nCompiler Option .\nSupported Compilers and Assemblers\nSymbolic information is currently supported for programs that are compiled or assembled by the following IBM products:\n\u2022OS/VS COBOL\n\u2022OS PL/I\n\u2022VS COBOL II\n\u2022AD/CYCLE COBOL/370\n\u2022COBOL for MVS\n\u2022COBOL for VM\n\u2022Enterprise COBOL for z/OS\n\u2022Visual Age PL/I\n\u2022PL/I for MVS and VM\n\u2022Enterprise PL/I for z/OS\n\u2022High Level Assembler for MVS and VM and VSE\n\u2022Assembler H\nConsiderations for Using the Integrated Preprocessors\nThe integrated CICS translator and integrated SQL coprocessor of Enterprise COBOL for z/OS are fully supported by\nthe postprocessor. It is important to note however, that duplicate statement numbers for those statements generated\nby the integrated preprocessors are not saved in the PROTSYM. The Broadcom  Application Quality and Testing Tools\nproducts required this modification to the saved listing. In addition, the compiler LIST option is required to correctly load\nthe symbolic information into the PROTSYM file.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a06a5952523b-1", "text": "the symbolic information into the PROTSYM file.\nThe postprocessor also supports the integrated CICS and SQL preprocessors of PL/I for z/OS. However, programs that\ncontain EXEC SQL INCLUDE statements for user-defined members still require a separate precompile step. (EXEC SQL\nINCLUDE statements for SQLCA and SQLDA are supported when using the integrated SQL preprocessor.) Note that\nthat duplicate statement numbers for those statements generated by the integrated preprocessors are not saved in the\nPROTSYM. The Broadcom  Application Quality and Testing Tools products required this modification to the saved listing.\nThe integrated INCLUDE and MACRO preprocessors of PL/I for z/OS are not supported. A separate precompile step is\nrequired when incorporating external files into your program.\nPROTSYM File\nThe PROTSYM file is a VSAM relative record data set (RRDS) with an upper limit of 4,112,640 data records of 2 KB each.\nThe PROTSYM file can store symbolic information for up to 147,000 application programs at one time.\nThe PROTSYM file is defined by IDCAMS and must be initialized by program IN25UTIL before you can add symbolic\ninformation.\nMember CAVHPROT in CAI.CAVHJCL contains sample JCL that you can use to allocate and initialize a PROTSYM file.\n 1405", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a9bb3955c066-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nThe PROTSYM file cannot reside in the LSR pool.\nSharing PROTSYM Files\nYour PROTSYM files can be shared between Broadcom  products and across multiple systems and environments. A\nsingle PROTSYM file contains symbolic information for both CICS and batch programs.\nUse RESERVE and DEQ macros when updating the PROTSYM file to allow sharing of the file between regions and\nsystems. The resource major name that is used in the RESERVE and DEQ macros is INTERTST. If your installation uses\na service that converts RESERVEs into cross-system ENQs, define the major name INTERTST to the service.\nDepending on your needs, you can maintain more than one PROTSYM file at your installation. All Broadcom  Application\nQuality and Testing Tools products support the use of multiple PROTSYM files.\nLoading Symbolic Information\nBy modifying the JCL procedures used to compile or assemble your applications, you can automatically update the\nsymbolic information in your PROTSYM file every time a program is rebuilt. This update is the easiest way to help ensure\nthat the symbolic information in your PROTSYM file matches the executable for every program. We recommend this\nmethod to maintain symbolic information.\nAlternatively, you can save the listings from your compiles or assemblies and can load the symbolic information later as\nneeded. If you choose this method, you can load symbolic information into your PROTSYM file using a separate batch\njob. Broadcom  provides batch utilities that let you load one or more program listings residing in partitioned data sets (PDS\nor PDSE), Librarian , Panvalet , or Endevor  format.\nSome of the Broadcom  Application Quality and Testing Tools products provide additional online functionality for viewing\nand maintaining PROTSYM files. For more information about the online utilities for any Broadcom  product, see the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a9bb3955c066-1", "text": "documentation for that product.\nCreating a PROTSYM File\nCAVHPROT\nMember CAVHPROT in CAI.CAVHJCL contains sample JCL for defining and initializing a PROTSYM file. The\nINITIALIZE, UPDATE, DELETE, PURGE, and RELOAD functions are protected by a password or external security.\nThe default password is 12345678. To modify the password or enable external security, run the member CAVHCONF\nin CAI.CAVHJCL with a modified version of member CAVHCONF in CAI.CAVHMAC as input before you create your\nPROTSYM files. You can specify external security or password protection, but not both.\nNOTE\nIf you are installing one of the Broadcom  Testing and Fault Management products, be sure to follow the\ninstructions for creating the PROTSYM file in Configuring for the product you are installing. Some products may\nprovide custom JCL members that have been tailored for use with the product.\nCAVHPROT contains the following two steps:\n\u2022Step 1 (DEFSYM) -- Invokes IDCAMS to define the PROTSYM file.\n\u2022Step 2 (LOAD) -- Invokes IN25UTIL to initialize each of the PROTSYM records.\nThe following JCL for member CAVHPROT shows these two steps:\n //CAVHPROT JOB\n //DEFSYM   EXEC PGM=IDCAMS,REGION=1024K                          \n//SYSPRINT DD SYSOUT=*                                           \n//SYSIN    DD *                                                  \n   DELETE $PROTSYM$ CLUSTER PURGE                                \n 1406", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "86d1016b630c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n   SET MAXCC=0                                                   \n   DEFINE CLUSTER (NAME($PROTSYM$)          -   \n                   REC($RECS$)                  -   \n                   CISZ(2048)            /* DO NOT CHANGE */        -   \n                   VOLUME($SYMVOL$)             -   \n                   RECSZ(2040 2040)             -   \n                   SHR(4 4)                 -   \n                   NUMBERED)                    -   \n          DATA (NAME($PROTSYM$.DATA))                            \n/*                                                               \n//LOAD     EXEC PGM=IN25UTIL,REGION=2048K                        \n//STEPLIB  DD DSN=$LOADLIB$,DISP=SHR                             \n//MESSAGE  DD SYSOUT=*                                           \n//PROTSYM  DD DSN=$PROTSYM$,DISP=SHR                             \n//CARDS    DD *                                                  \nPASSWORD=$PASSWORD$                                               \nINITIALIZE   \nREPORT       \n/*           \n// \n \nMake the following substitutions in member CAVHPROT:\n$PROTSYM$\nThe fully-qualified name of your new PROTSYM library.\n$SYMVOL$\nThe volume on which the PROTSYM resides.\n$RECS$\nThe primary space allocation in records. (See Notes 1 and 2.)\n$PASSWORD$\nThe one- to eight-character PROTSYM update password for your installation, from CAVHCONF. (See Note 3.)If\nexternal security for the symbolic component is enabled in CAVHCONF, this keyword is not required and will be\nignored if it is specified.\n$LOADLIB$\nThe product target library.\nSubmit the JCL to allocate and initialize a new PROTSYM file.\n1.Do not allocate any secondary space.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "86d1016b630c-1", "text": "1.Do not allocate any secondary space.\n2.The space required depends on many factors including the size of your programs, the number of variables and labels,\nthe average length of their names, and the LISTER options used for loading symbolic information. We recommend\nan initial allocation of 10,000 records. You can allocate new PROTSYM files as needed, and expand and reorganize\nexisting files.\n3.If you have not altered the installation default, specify PASSWORD=12345678.\n4.The PROTSYM share parameters must be SHR(4,4).\n5.To allow multiple program version support, include the MAXPGMVER=parameter.\nNOTE\nFor more information about the MAXPGMVER parameter, see Maintaining a PROTSYM File.\n 1407", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9d6665ff1586-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAdding Symbolic Information\nYou can add symbolic information to your PROTSYM files using the following postprocessors:\nIN25SYMC\nLoads symbolic information for programs compiled using:\n\u2022OS/VS COBOL version 2.3 plus PTF8 or higher\n\u2022Optimizer/II\nIN25COB2\nLoads symbolic information for programs compiled using:\n\u2022Enterprise COBOL for z/OS\n\u2022IBM COBOL for VM\n\u2022IBM COBOL for MVS and VM\n\u2022AD/CYCLE COBOL/370\n\u2022VS COBOL II\n\u2022Optimizer/II\nIN25SYMP\nLoads symbolic information for programs compiled using:\n\u2022Enterprise PL/I for z/OS\n\u2022IBM PL/I for MVS and VM\n\u2022Visual Age PL/I\n\u2022OS PL/I\nIN25SYMA\nLoads symbolic information for programs compiled using:\n\u2022High level Assembler for MVS and VM and VSE\n\u2022Assembler H\nIN25LINK\nReads IBM linkage editor output to collect and load subroutine mapping information for composite load modules.\nIN25SYMD\nLoads multiple COBOL, C, PL/I, and Assembler listings residing in PDS, PDSE, Librarian , Panvalet , or Endevor\nformat.\nIN25SYMC\nUse program IN25SYMC to load symbolic information for programs compiled using OS/VS COBOL or Optimizer/II .\nYou can execute IN25SYMC as a standalone batch job to load a single COBOL listing that has been previously saved to\na permanent file, or add it to your existing OS/VS COBOL or Optimizer/II  JCL procedure. The method you select depends\nentirely on the procedures at your own installation. Both methods are described in this article.\nIN25SYMC JCL", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9d6665ff1586-1", "text": "IN25SYMC JCL\nThe following table describes the DD statements used by IN25SYMC:\nDDname Description\nSTEPLIB The load library containing IN25SYMC.\n 1408", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3c1af8dd59e5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nINPUT The listing that was written to SYSPRINT by the OS/VS COBOL\ncompiler, or by Optimizer/II , during compilation.\nOUTPUT All or part of the original compiler listing is written to this file,\ndepending on your request.\nMESSAGE Any messages produced by IN25SYMC during postprocessing are\nwritten here.\nPROTSYM The file to which the symbolic information is written.\nCARDS The input control statements that define the request.\nNOTE\nIf you are adding a new step for IN25SYMC to a JCL procedure, use program IN25PARM to write your input\ncontrol statements to the CARDS file.\nIN25SYMC Options\nOptions are passed to IN25SYMC using a parameter statement in the CARDS DD. Specify the parameter statement as an\nin-stream control card, or when using a JCL procedure, generate it using program IN25PARM.\nThe following JCL shows these options:\n //IN25PARM EXEC PGM=IN25PARM,PARM='parameter statement'\n //STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD\n //CARDS    DD DISP=(,PASS),DSN=&&CARDS,UNIT=SYSDA,SPACE=(TRK,(1,1))\n \nParameter statements in the CARDS DD must begin in column 1.\nThe program name is the only required field on the parameter statement. This positional parameter defines the name\nthat is used to store the symbolic information in the PROTSYM file. This name is used by the Broadcom  Application\nQuality and Testing Tools products to locate the symbolic information and is displayed when listing the contents of your\nPROTSYM.\nIn most cases, this name should be the same as the PROGRAM-ID. However, when loading symbolic information for use", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3c1af8dd59e5-1", "text": "with InterTest for CICS, you must specify the name of the CICS program definition, or when using composite support,\nspecify the monitor name.\nThe following example shows an in-stream parameter statement that you can use to save symbolic information using the\nname ORDEDIT:\n //CARDS  DD *\n ORDEDIT\n /*\n \nControlling Printed Output with the CUTPRINT Option\nBecause you can load symbolic information from a permanent data set or a temporary listing file, you can also print all or\npart of the listing generated by the compiler.\nAppend the CUTPRINT option to your parameter statement to control printing of the compiler listing as follows:\n,CUTPRINT=ALL\nDo not print any of the compiler listing.\n,CUTPRINT=MAP\nPrint the listing up to, but not including, the Data Division Map report.\n 1409", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0998e4bd0fe0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n,CUTPRINT=REF\nPrint the listing up to, but not including, the cross reference of data names.\nThe following sample parameter statement saves symbolic information for program ORDEDIT and prints only the source\ncode section of the compiler listing:\n //CARDS   DD *\n ORDEDIT,CUTPRINT=MAP\n /*\n \nNOTE\nSpecify the CUTPRINT parameter only when you do not want all or part of your listing printed. The entire listing\nis printed if this parameter is omitted.\nSaving Your Listing for Online Display with the LISTER Option\nAppend the LISTER option to your parameter statement to control which portion of your source listing is saved to the\nPROTSYM file as follows:\n,LISTER=ALL\nSaves the entire OS/VS COBOL listing.\n,LISTER=MAP\nSaves the OS/VS COBOL listing up to, but not including, the Data Division Map report.\n,LISTER=REF\nSaves the OS/VS COBOL listing up to, but not including, the cross reference of data names.\nThe following sample parameter statement saves symbolic information for program ORDEDIT, does not print any of the\nlisting, and saves the listing up to, but not including, the Data Division Map report to the PROTSYM file:\n //CARDS DD  *\n ORDEDIT,CUTPRINT=ALL,LISTER=MAP\n /*\n \nNOTE\n\u2022If the LISTER parameter is omitted, no listing is saved in the symbolic file.\n\u2022The LISTER parameter is required for use with Optimizer/II , SymDump  Batch, and InterTest Batch.\n\u2022To reduce overhead and save space in your PROTSYM file, we recommend that you specify LISTER=MAP\nwhen executing IN25SYMC.\nSetting Data as Nonpurgeable", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0998e4bd0fe0-1", "text": "when executing IN25SYMC.\nSetting Data as Nonpurgeable\nYou can mark any saved symbolic data for this program as nonpurgeable. If a program's data is marked as nonpurgeable,\nthe data is not removed from the PROTSYM when deleting programs using a purge interval batch run. However, you can\ndelete the data by program name. For instructions on deleting data from the symbolic file, see Maintaining a PROTSYM\nFile.\nTo mark data as nonpurgeable, add the NOPURGE option to your parameter statement as the last option.\nThe following sample parameter statement saves symbolic information for program ORDEDIT, prints the entire listing,\nsaves the entire listing in the PROTSYM file, and does not let symbolic data be removed from the symbolic file by a purge\ninterval batch run.\n //CARDS DD  *\n ORDEDIT,LISTER=ALL,NOPURGE\n 1410", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1a590490ce3f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n /*\n \nRequired OS/VS COBOL Options\nThe following compiler options are required to load symbolic information for OS/VS COBOL programs into the PROTSYM\nfile:\nOption Description\nCLIST or PMAP Produces a condensed Procedure Division map or full Assembler\nProcedure Division map.\nDMAP Produces a Data Division map.\nNONUM Suppresses compiler-generated line numbers.\nSXREF Produces a cross-reference of data and paragraph names.\nVERB Produces a report of verb names.\nThe following compiler options are required to load symbolic information for a program compiled using Optimizer/II  into the\nPROTSYM file:\nOption Description\nDMAP or MDMAP Produces a Data Division map or merged Data Division map.\nMLIST Produces a merged Procedure Division map.\nNONUM Suppresses compiler-generated line numbers.\nXREF Produces a cross-reference of data and paragraph names.\nTo use symbolic references in OS/VS COBOL, you must declare at least one data item in working storage.\nExecuting IN25SYMC as a Standalone Program\nMember CAVHSYMC in CAI.CAVHPROC contains sample JCL for executing postprocessor IN25SYMC as a standalone\nbatch job. Use this member to load symbolic information from previously saved OS/VS COBOL listings.\n //CAVHSYMC PROC PROTSYM=CAI.PROTSYM,\n //             NAME=XXXXXXXX,                                \n //             LISTLIB=USER.LISTLIB, \n //             MEMBER=XXXXXXXX,                          \n //             LISTER=ALL,                                      \n //             CUTPRINT=ALL                                     \n //*                                                             \n //IN25PARM EXEC PGM=IN25PARM,REGION=512K,", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1a590490ce3f-1", "text": "//IN25PARM EXEC PGM=IN25PARM,REGION=512K,                       \n //             PARM='&MEMBER,LISTER=&LISTER,CUTPRINT=&CUTPRINT' \n //STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD                           \n //CARDS    DD DSN=&&CARDS,DISP=(,PASS),                         \n //            UNIT=SYSDA,SPACE=(TRK,(1,1))                      \n //*                                                             \n //IN25SYMC EXEC PGM=IN25SYMC,REGION=2M                          \n //STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD                           \n //PROTSYM  DD DISP=SHR,DSN=&PROTSYM                             \n //INPUT    DD DISP=SHR,DSN=&LISTLIB(&MEMBER)                    \n //CARDS    DD DSN=&&CARDS,DISP=(OLD,DELETE)                     \n //OUTPUT   DD SYSOUT=*,DCB=(LRECL=121,BLKSIZE=2440,RECFM=FBA)        \n 1411", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e42b5c963514-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n //MESSAGE  DD SYSOUT=*                                               \n //                                                                   \n \nYou can override the following procedure variables:\nVariable Description\nPROTSYM Specifies the name of the symbolic file being updated.\nNAME Specifies the name that is used to store the symbolic information\nin the PROTSYM file. This name is used by the Broadcom\nApplication Quality and Testing Tools products to locate the\nsymbolic information and is displayed when listing the contents of\nyour PROTSYM.\nIn most cases, this name should be the same as the PROGRAM-\nID. However, when loading symbolic information for use with\nInterTest for CICS, specify the name of the CICS program\ndefinition, or for composite support, specify the monitor name.\nLISTLIB Specifies the name of the partitioned data set containing the listing\nfrom the OS/VS COBOL compiler or Optimizer/II .\nMEMBER Specifies the name of the member in the listing library that\ncontains the compiler listing for the program being added.\nLISTER Specifies how much of the listing to write to the OUTPUT file.\nCUTPRINT Specifies how much of the listing to write to the OUTPUT file.\nAdding IN25SYMC to Your OS/VS COBOL Procedure\nTo automatically update the symbolic information in your PROTSYM file whenever a OS/VS COBOL program is compiled,\nyou can add a postprocessor step directly to the JCL procedure that you use to compile your programs. These same\nsteps also apply to your Optimizer/II  procedure.\nFollow these steps to update your existing compile procedure:\n1.Ensure that your compile step specifies all of the required OS/VS COBOL options.\n2.Change the DD statement so that a temporary disk file is created for your listing, if the SYSPRINT output from your\ncompile step is written to SYSOUT.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e42b5c963514-1", "text": "compile step is written to SYSOUT.\n3.Add a new IN25PARM step following your compile step to generate the parameter statement for the postprocessor.\n4.Add a new IN25SYMC step to postprocess the listing from the compile step. The INPUT DD on this step refers to the\nsame file as the SYSPRINT DD from the compile step.\n5.Add a new IEBGENER step to print the compiler listing only if the compiler detects errors.\nThe following example shows modifications to a compile procedure:\n //COB      EXEC PGM=IKFCBL00,REGION=4M,  \n //  PARM='SOURCE,DMAP,SXREF,PMAP,VERB,NONUM,&OPTIONS'    <= 1  \n  \n      (Your existing DD statements for OS/VS COBOL)\n  \n //SYSPRINT DD DSN=&&LST,DISP=(NEW,PASS),                 <= 2\n //            UNIT=SYSDA,SPACE=(CYL,(1,2))    \n //*\n //*   GENERATE THE PARAMETER STATEMENT FOR IN25SYMC\n //*\n //CARDS   EXEC PGM=IN25PARM,REGION=1M,COND=(4,LT),       <= 3              \n //   PARM='&MEMBER,LISTER=ALL'                             \n 1412", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e94dbb9f7279-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR                                     \n //CARDS    DD DSN=&&CARDS,DISP=(NEW,PASS),                             \n //            UNIT=SYSDA,SPACE=(TRK,(1,1))                               \n //*\n //*    POST-PROCESS THE COMPILER LISTING\n //*\n //SYM      EXEC PGM=IN25SYMC,REGION=4M,COND=(4,LT)       <= 4              \n //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR                                     \n //PROTSYM  DD DSN=USER.PROTSYM,DISP=SHR                                    \n //OUTPUT   DD SYSOUT=*,\n //            DCB=(LRECL=121,BLKSIZE=2420,RECFM=FBA)          \n //INPUT    DD DSN=&&LST,DISP=(OLD,PASS)                      (See Note 1)\n //CARDS    DD DSN=&&CARDS,DISP=(OLD,DELETE)                  (See Note 2)\n //MESSAGE  DD SYSOUT=*                                                 \n //*\n //PRINT    EXEC PGM=IEBGENER,COND=(5,GT,COB)         <= 5   \n //SYSUT1   DD DSN=&&LST,DISP=(OLD,DELETE)                              \n //SYSUT2   DD SYSOUT=*                                                 \n //SYSPRINT DD DUMMY                                                    \n //SYSIN    DD DUMMY                                                    \n \nNOTE\n\u2022If the SYSPRINT DD on your compile step refers to a permanent data set, the INPUT DD for IN25SYMC\nmust point to the same data set.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e94dbb9f7279-1", "text": "must point to the same data set.\n\u2022If you prefer to pass your parameter statement as an override in the invoking JCL, delete the CARDS step,\ndelete this DD statement, and add SYM.CARDS DD to your invoking JCL member.\nIN25COB2\nUse program IN25COB2 to load symbolic information for programs compiled using any of the following products:\n\u2022Enterprise COBOL for z/OS\n\u2022IBM COBOL for VM\n\u2022IBM COBOL for MVS and VM\n\u2022AD/CYCLE COBOL/370\n\u2022VS COBOL II\n\u2022Optimizer/II\nNOTE\nIn this article, the term COBOL refers to any of the COBOL dialects supported by the IBM compilers listed\npreviously.\nExecute IN25COB2 as a standalone batch job to load a single COBOL listing that has been previously saved to a\npermanent file, or add it to your existing COBOL or Optimizer/II  JCL procedure. The method you select depends entirely\non the procedures at your own installation. Both methods are described in this article.\n 1413", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ff660819650b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIN25COB2 JCL\nThe following table describes the DD statements used by IN25COB2:\nDDname Description\nSTEPLIB The load library containing IN25COB2.\nINPUT The listing that was written to SYSPRINT by the COBOL compiler,\nor by Optimizer/II , during compilation.\nOUTPUT All or part of the original compiler listing is written to this file,\ndepending on your request.\nMESSAGE All messages produced by IN25COB2 during post processing are\nwritten to this file.\nPROTSYM The file to which the symbolic information is written.\nCARDS The input control statements that define the request.\nNOTE\nIf you are adding a new step for IN25COB2 to a JCL procedure, use program IN25PARM to write your input\ncontrol statements to the CARDS file.\nIN25COB2 Options\nOptions are passed to IN25COB2 using a parameter statement in the CARDS DD. Specify the parameter statement as an\nin-stream control card, or when using a JCL procedure, generate it using program IN25PARM as follows:\n //IN25PARM EXEC PGM=IN25PARM,PARM='parameter statement'\n //STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD\n //CARDS    DD DISP=(,PASS),DSN=&&CARDS,UNIT=SYSDA,SPACE=(TRK,(1,1))\n \nParameter statements in the CARDS DD must begin in column 1.\nThe program name is the only required field on the parameter statement. This positional parameter defines the name\nthat is used to store the symbolic information in the PROTSYM file. This name is used by the Broadcom  Application", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ff660819650b-1", "text": "Quality and Testing Tools products to locate the symbolic information and is displayed when listing the contents of your\nPROTSYM.\nIn most cases, this name should be the same as the PROGRAM-ID. However, when loading symbolic information for use\nwith InterTest for CICS, you must specify the name of the CICS program definition, or when using composite support,\nspecify the monitor name.\nThe following example shows an in-stream parameter statement that can be used to save symbolic information using the\nname ORDEDIT:\n //CARDS  DD *\n ORDEDIT\n /*\n \nControlling Printed Output with the CUTPRINT Option\nBecause you can load symbolic information from a permanent data set or a temporary listing file, you can also print all or\npart of the listing generated by the compiler.\nAppend the CUTPRINT option to your parameter statement to control printing of the compiler listing as follows:\n 1414", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "55a997d9e60d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n,CUTPRINT=ALL\nDo not print any of the compiler listing.\n,CUTPRINT=MAP\nPrint the listing up to, but not including, the Data Division Map report.\n,CUTPRINT=REF\nPrint the listing up to, but not including, the cross reference of data names.\nThe following sample parameter statement saves symbolic information for program ORDEDIT and prints only the source\ncode section of the compiler listing:\n //CARDS   DD *\n ORDEDIT,CUTPRINT=REF\n /*\n \nNOTE\nSpecify the CUTPRINT parameter only when you do not want all or part of your listing printed. The entire listing\nis printed if this parameter is omitted.\nSaving Your Listing for Online Display with the LISTER Option\nAppend the LISTER option to your parameter statement to control which portion of your source listing is saved to the\nPROTSYM file, as follows:\n,LISTER=ALL\nSaves the entire COBOL listing.\n,LISTER=MAP\nSaves the COBOL listing up to, but not including, the Data Division map report.\n,LISTER=REF\nSaves the COBOL listing up to, but not including, the cross reference of data names.\nThe following sample parameter statement saves symbolic information for program ORDEDIT, does not print any of the\nlisting, and saves the listing up to, but not including, the Data Division map report to the PROTSYM file:\n //CARDS DD  *\n ORDEDIT,CUTPRINT=ALL,LISTER=MAP\n /*\n \nNOTE\n\u2022If the LISTER parameter is omitted, no listing is saved in the symbolic file.\n\u2022The LISTER parameter is required for use with Optimizer/II , SymDump  Batch, and InterTest Batch.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "55a997d9e60d-1", "text": "\u2022To reduce overhead and save space in your PROTSYM file, we recommend that you specify LISTER=MAP\nwhen executing IN25COB2 unless compiling with Optimizer/II, which requires LISTER=MMAP.\nSetting Data as Nonpurgeable\nYou can mark any saved symbolic data for this program as nonpurgeable. If a program's data is marked as nonpurgeable,\nthe data is not removed from the PROTSYM when deleting programs using a purge interval batch run. However, you can\ndelete the data by program name. See Maintaining a PROTSYM File for instructions on deleting data from the symbolic\nfile.\nTo mark data as nonpurgeable, add the NOPURGE option to your parameter statement as the last option.\n 1415", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b95889107395-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe following sample parameter statement saves symbolic information for program ORDEDIT, prints the entire listing,\nsaves the entire listing in the PROTSYM file, and does not let symbolic data be removed from the symbolic file by a purge\ninterval batch run.\n //CARDS DD  *\n ORDEDIT,LISTER=ALL,NOPURGE\n /*\n \nRequired COBOL Options\nThe following compiler options are required to load symbolic information for COBOL programs into the PROTSYM or\nDWARF file:\nOption Description\nMAP Produces a Data Division map.\nNONUMBER Suppresses compiler-generated line numbers.\nOFFSET or LIST* Produces a condensed Procedure map or full Assembler\nProcedure map.\nXREF Produces a cross-reference of data and procedure names.\nNOPT or OPT(0)** Produces breakpoints synchronized with source.\nNOSTGOPT Prevents the compiler from discarding unreferenced data items.\nThe NOSTGOPT option is only valid for COBOL 5.1 and above.\nTEST(SOURCE) (DWARF only) Generates the DWARF debugging information\nincluding the expanded source code.\n* The LIST option is required when using the integrated CICS translator or integrated SQL coprocessor of COBOL for z/\nOS.\n** When a COBOL program is OPTIMIZED, your breakpoints may not get stopped exactly where you think they should\nbecause the optimization is adding or modifying the generated code, and it may not be synchronized with the related\nsource statements in the listing.\nThe following compiler options are required to load symbolic information for a program compiled using Optimizer/II  into the\nPROTSYM file:\nOption Description\nINTERTST Required only when optimizing programs that are monitored using\nInterTest for CICS.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b95889107395-1", "text": "INTERTST Required only when optimizing programs that are monitored using\nInterTest for CICS.\nMAP or MMAP Produces a Data Division map or merged Data Division map.\nMMAP Required when optimizing programs that are monitored using\nInterTest for CICS.\nMOFFSET Produces a merged Procedure map.\nNONUM Suppresses compiler-generated line numbers.\nXREF Produces a cross-reference of data and paragraph names.\nNOTE\nIf you are using Optimizer/II  r7 or higher, you can use the SYM compile-time option to automatically load\nsymbolic information into your PROTSYM file during optimization. When using the SYM option, add a\nPROTSYM DD statement to your compile/optimize step. No additional option requirements exist when using this\nmethod.\n 1416", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4281479f491f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTo use symbolic references in COBOL, you must declare at least one data item in working storage.\nExecuting IN25COB2 as a Standalone Program\nMember CAVHCOB2 in CAI.CAVHPROC contains sample JCL for executing postprocessor IN25COB2 as a standalone\nbatch job. Use this member to load symbolic information from previously saved COBOL listings.\n //CAVHCOB2 PROC PROTSYM=CAI.PROTSYM,\n //             NAME=XXXXXXXX,                                \n //             LISTLIB=USER.LISTLIB, \n //             MEMBER=XXXXXXXX,                          \n //             LISTER=ALL,                                      \n //             CUTPRINT=ALL                                     \n //*                                                             \n //IN25PARM EXEC PGM=IN25PARM,REGION=512K,                       \n //             PARM='&MEMBER,LISTER=&LISTER,CUTPRINT=&CUTPRINT' \n //STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD                           \n //CARDS    DD DSN=&&CARDS,DISP=(,PASS),                         \n //            UNIT=SYSDA,SPACE=(TRK,(1,1))                      \n //*                                                             \n //IN25COB2 EXEC PGM=IN25COB2,REGION=2M                          \n //STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD                           \n //PROTSYM  DD DISP=SHR,DSN=&PROTSYM                             \n //INPUT    DD DISP=SHR,DSN=&LISTLIB(&MEMBER)                    \n //CARDS    DD DSN=&&CARDS,DISP=(OLD,DELETE)", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4281479f491f-1", "text": "//CARDS    DD DSN=&&CARDS,DISP=(OLD,DELETE)                     \n //OUTPUT   DD SYSOUT=*,DCB=(LRECL=133,BLKSIZE=3990,RECFM=FBA)        \n //MESSAGE  DD SYSOUT=*                                               \n //                                                                   \n \nYou can override the following procedure variables:\nVariable Description\nPROTSYM Specifies the name of the symbolic file being updated.\nNAME Specifies the name that is used to store the symbolic information\nin the PROTSYM file. This name is used by the Broadcom\nApplication Quality and Testing Tools products to locate the\nsymbolic information and is displayed when listing the contents of\nyour PROTSYM.\nIn most cases, this name should be the same as the PROGRAM-\nID. However, when loading symbolic information for use with\nInterTest for CICS, specify the name of the CICS program\ndefinition, or for composite support, specify the monitor name.\nLISTLIB Specifies the name of the partitioned data set containing the listing\nfrom the COBOL II compiler or Optimizer/II .\nMEMBER Specifies the name of the member in the listing library that\ncontains the compiler listing for the program being added.\nLISTER Specifies how much of the listing to save in the PROTSYM file.\nCUTPRINT Specifies how much of the listing to write to the OUTPUT file.\n 1417", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5c8334e1781c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAdding IN25COB2 to Your COBOL Procedure\nTo automatically update the symbolic information in your PROTSYM file whenever a COBOL program is compiled, you\ncan add a postprocessor step directly to the JCL procedure that you use to compile your programs.\nNOTE\nThese same steps also apply to the Optimizer/II  procedure.\nFollow these steps to update your existing compile procedure:\n1.Ensure that your compile step specifies all of the required COBOL options.\n2.Change the DD statement so that a temporary disk file is created for your listing, if the SYSPRINT output from your\ncompile step is written to SYSOUT.\n3.Add a new IN25PARM step following your compile step to generate the parameter statement for the postprocessor.\n4.Add a new IN25COB2 step to postprocess the listing from the compile step. The INPUT DD on this step refers to the\nsame file as the SYSPRINT DD from the compile step.\n5.Add a new IEBGENER step to print the compiler listing only if the compiler detects errors.\nThe following example shows modifications to a compile procedure:\n //COB      EXEC PGM=IGYCRCTL,REGION=4M,                                 \n //  PARM='S,MAP,X,LIST,NONUM,&OPTIONS'                   <= 1  \n  \n      (Your existing DD statements for COBOL II)\n  \n //SYSPRINT DD DSN=&&LST,DISP=(NEW,PASS),                 <= 2\n //            UNIT=SYSDA,SPACE=(CYL,(1,2))    \n //*\n //*   GENERATE THE PARAMETER STATEMENT FOR IN25COB2\n //*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5c8334e1781c-1", "text": "//*\n //*   GENERATE THE PARAMETER STATEMENT FOR IN25COB2\n //*\n //CARDS   EXEC PGM=IN25PARM,REGION=1M,COND=(4,LT),       <= 3              \n //   PARM='&MEMBER,LISTER=ALL'                             \n //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR                                     \n //CARDS    DD DSN=&&CARDS,DISP=(NEW,PASS),                             \n //            UNIT=SYSDA,SPACE=(TRK,(1,1))                               \n //*\n //*    POST-PROCESS THE COMPILER LISTING\n //*\n //SYM      EXEC PGM=IN25COB2,REGION=4M,COND=(4,LT)       <= 4              \n //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR                                     \n //PROTSYM  DD DSN=USER.PROTSYM,DISP=SHR                                    \n //OUTPUT   DD SYSOUT=*,\n //            DCB=(LRECL=133,BLKSIZE=3990,RECFM=FBA)          \n //INPUT    DD DSN=&&LST,DISP=(OLD,PASS)                      (See Note 1)\n //CARDS    DD DSN=&&CARDS,DISP=(OLD,DELETE)                  (See Note 2)\n //MESSAGE  DD SYSOUT=*                                                 \n //*\n //PRINT    EXEC PGM=IEBGENER,COND=(5,GT,COB)         <= 5   \n //SYSUT1   DD DSN=&&LST,DISP=(OLD,DELETE)                              \n //SYSUT2   DD SYSOUT=*                                                 \n //SYSPRINT DD DUMMY                                                    \n //SYSIN    DD DUMMY                                                    \n \nNOTE\n 1418", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "036f46d01c00-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022If the SYSPRINT DD on your compile step refers to a permanent data set, the INPUT DD for IN25COB2\nmust point to the same data set.\n\u2022If you prefer to pass your parameter statement as an override in the invoking JCL, delete the CARDS step,\ndelete this DD statement, and add SYM.CARDS DD to your invoking JCL member.\nControlling Printed Output with the CUTPRINT Option\nBecause you can load symbolic information from a permanent data set or a temporary listing file, you can also print all or\npart of the listing generated by the compiler.\nAppend the CUTPRINT option to your parameter statement to control printing of the compiler listing as follows:\n,CUTPRINT=ALL\nDo not print any of the compiler listing.\n,CUTPRINT=REF\nPrint the listing up to, but not including, the cross reference of data names.\nThe following sample parameter statement saves symbolic information for program ORDEDIT and prints only the source\ncode section of the compiler listing:\n //CARDS   DD *\n ORDEDIT,CUTPRINT=REF\n /*\n \nNOTE\nSpecify the CUTPRINT parameter only when you do not want all or part of your listing printed. The entire listing\nis printed if this parameter is omitted.\nSaving Your Listing for Online Display with the LISTER Option\nAppend the LISTER option to your parameter statement to control which portion of your source listing is saved to the\nPROTSYM file, as follows:\n,LISTER=ALL\nSaves the entire compiler listing.\n,LISTER=REF\nSaves the compiler listing up to, but not including, the cross reference of data names.\nThe following sample parameter statement saves symbolic information for program ORDEDIT, does not print any of the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "036f46d01c00-1", "text": "The following sample parameter statement saves symbolic information for program ORDEDIT, does not print any of the\nlisting, and saves the listing up to, but not including, the Data Division map report to the PROTSYM file:\n //CARDS DD  *\n ORDEDIT,CUTPRINT=ALL,LISTER=MAP\n /*\n \nNOTE\n\u2022If the LISTER parameter is omitted, no listing is saved in the symbolic file.\n\u2022The LISTER parameter is required for use with Optimizer/II , SymDump  Batch, and InterTest Batch.\n\u2022To reduce overhead and save space in your PROTSYM file, we recommend that you specify LISTER=MAP\nwhen executing IN25CPPR unless compiling with Optimizer/II, which requires LISTER=MMAP.\nSetting Data as Nonpurgeable\nYou can mark any saved symbolic data for this program as nonpurgeable. If a program's data is marked as nonpurgeable,\nthe data is not removed from the PROTSYM when deleting programs using a purge interval batch run. However, you can\n 1419", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f4b98fa069bf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\ndelete the data by program name. See Maintaining a PROTSYM File for instructions on deleting data from the symbolic\nfile.\nTo mark data as nonpurgeable, add the NOPURGE option to your parameter statement as the last option.\nThe following sample parameter statement saves symbolic information for program ORDEDIT, prints the entire listing,\nsaves the entire listing in the PROTSYM file, and does not let symbolic data be removed from the symbolic file by a purge\ninterval batch run.\n //CARDS DD  *\n ORDEDIT,LISTER=ALL,NOPURGE\n /*\n \nIN25SYMP\nUse program IN25SYMP to load symbolic information for programs compiled using any of the following products:\n\u2022Enterprise PL/I for z/OS\n\u2022IBM PL/I for MVS and VM\n\u2022Visual Age PL/I\n\u2022OS PL/I\nNOTE\nIn this section, the term PL/I refers to any of the PL/I dialects supported by the IBM compilers previously listed.\nExecute IN25SYMP as a standalone batch job to load a single PL/I listing that has been previously saved to a permanent\nfile, or add it to your existing PL/I JCL procedure. The method you select depends entirely on the procedures at your own\ninstallation. Both methods are described in this article.\nIN25SYMP JCL\nThe following table describes the DD statements used by IN25SYMP:\nDDname Description\nSTEPLIB The load library containing IN25SYMP.\nINPUTT The listing that was written to SYSPRINT by the PL/I compiler\nduring compilation.\nSYSPRINT All or part of the original compiler listing is written to this file,\ndepending on your request.\nMESSAGE and MSGS Messages produced by IN25SYMP during postprocessing are\nwritten to these files.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f4b98fa069bf-1", "text": "written to these files.\nPROTSYM The file to which the symbolic information is written.\nCARDS The input control statements that define the request.\nNOTE\nIf you are adding a new step for IN25SYMP to a JCL procedure, use program IN25PARM to write your input\ncontrol statements to the CARDS file.\nIN25SYMP Options\nOptions are passed to IN25SYMP using a parameter statement in the CARDS DD. Specify the parameter statement as an\nin-stream control card, or when using a JCL procedure, generate it using program IN25PARM as follows:\n 1420", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0bfab36fa116-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n //IN25PARM EXEC PGM=IN25PARM,PARM='parameter statement'\n //STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD\n //CARDS    DD DISP=(,PASS),DSN=&&CARDS,UNIT=SYSDA,SPACE=(TRK,(1,1))\n \nParameter statements in the CARDS DD must begin in column 1.\nThe program name is the only required field on the parameter statement. This positional parameter defines the name\nthat is used to store the symbolic information in the PROTSYM file. This name is used by the Broadcom  Application\nQuality and Testing Tools products to locate the symbolic information and is displayed when listing the contents of your\nPROTSYM.\nWhen loading symbolic information for use with InterTest for CICS, you must specify the name of the CICS program\ndefinition, or when using composite support, specify the monitor name.\nThe following example shows an in-stream parameter statement that you can use to save symbolic information using the\nname ORDEDIT:\n //CARDS  DD *\n ORDEDIT\n /*\n \nControlling Printed Output with the CUTPRINT Option\nBecause you can load symbolic information from a permanent data set or a temporary listing file, you can also print all or\npart of the listing generated by the compiler.\nAppend the CUTPRINT option to your parameter statement to control printing of the compiler listing as follows:\n,CUTPRINT=ALL\nPrints none of the compile listing.\n,CUTPRINT=REF\nTerminates printing after the XREF table.\n,CUTPRINT=OFFSET\nTerminates printing after the table of offsets.\nThe following sample parameter statement saves symbolic information for program ORDEDIT and terminates printing\nafter the XREF table:\n //CARDS   DD *", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0bfab36fa116-1", "text": "after the XREF table:\n //CARDS   DD *\n ORDEDIT,CUTPRINT=REF\n /*\n \nNOTE\nSpecify the CUTPRINT parameter only when you do not want all or part of your listing printed. The entire listing\nis printed if you omit this parameter.\nSaving Your Listing for Online Display with the LISTER Option\nAppend the LISTER option to your parameter statement to control which portion of your source listing is saved to the\nPROTSYM file, as follows:\n,LISTER=ALL\nSaves the entire PL/I listing.\n 1421", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5b8a98b44775-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n,LISTER=REF\nSaves only the source and XREF sections.\n,LISTER=OFFSET\nSaves the listing up to, and including, the table of offsets.\nThe following sample parameter statement saves symbolic information for program ORDEDIT, does not print any of the\nlisting, and saves only the source and XREF sections of the listing:\n //CARDS DD  *\n ORDEDIT,CUTPRINT=ALL,LISTER=REF\n /*\n \nNOTE\n\u2022If the LISTER parameter is omitted, no listing is saved in the symbolic file.\n\u2022The LISTER parameter is required for use with Optimizer/II , SymDump  Batch, and InterTest Batch.\nSetting Data as Nonpurgeable\nYou can mark any saved symbolic data for this program as nonpurgeable. If a program's data is marked as nonpurgeable,\nthe data is not removed from the PROTSYM when deleting programs using a purge interval batch run. However, you\ncan delete the data by program name. See Maintaining a PROTSYM File for instructions about deleting data from the\nsymbolic file.\nTo mark data as nonpurgeable, add the NOPURGE option to your parameter statement as the last option.\nThe following sample parameter statement saves symbolic information for program ORDEDIT, prints the entire listing,\nsaves the entire listing in the PROTSYM file, and does not let symbolic data be removed from the symbolic file by a purge\ninterval batch run.\n //CARDS DD  *\n ORDEDIT,LISTER=ALL,NOPURGE\n /*\n \nRequired PL/I Options\nThe following compiler options are required to load symbolic information for PL/I programs when using the OS PL/I or IBM\nPL/I for MVS and VM compiler:\nAGGREGATE\nATTRIBUTES(FULL)\nMAP", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5b8a98b44775-1", "text": "AGGREGATE\nATTRIBUTES(FULL)\nMAP\nNEST\nNOGONUMNONUMBER\nOPTIONS\nSOURCE\nSTMT or GOSTMT\nSTORAGE\nXREF(FULL)\n 1422", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "567d099b6528-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe following compiler options are required to load symbolic information for PL/I programs when using Enterprise PL/I for\nz/OS or Visual Age PL/I:\nAGGREGATE\nATTRIBUTES(FULL)\nLIMITS(NAME(31))\nLIST\nMAP\nNATLANG(ENU)\nNESTNOGONUM\nNOSTMT\nNUMBER\nOPTIONS\nSOURCE\nSTORAGE\nXREF(FULL)\nNOTE\n\u2022Because of special considerations, if you must use the %NOPRINT compiler option, contact Broadcom\nSupport .\n\u2022For the Broadcom  Application Quality and Testing Tools products to support date/time stamp comparison\nbetween your symbolic information and your executables, you must select TSTAMP=YES when installing\nyour PL/I compiler.\n\u2022InterTest Batch, SymDump  Batch, and Optimizer/II  display only controlled variables.\n\u2022When using the IBM PL/I for MVS and VM compiler, the ESD option is required for programs that have\ncontrolled variables.\nExecuting IN25SYMP as a Standalone Program\nMember CAVHSYMP in CAI.CAVHPROC contains sample JCL for executing postprocessor IN25SYMP as a standalone\nbatch job. Use this member to load symbolic information from previously saved PL/I listings as follows:\n //CAVHSYMP PROC PROTSYM=CAI.PROTSYM,\n //             NAME=XXXXXXXX,                                \n //             LISTLIB=USER.LISTLIB, \n //             MEMBER=XXXXXXXX,                          \n //             LISTER=ALL,                                      \n //             CUTPRINT=ALL                                     \n //*                                                             \n //IN25PARM EXEC PGM=IN25PARM,REGION=512K,                       \n //             PARM='&MEMBER,LISTER=&LISTER,CUTPRINT=&CUTPRINT'", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "567d099b6528-1", "text": "//STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD                           \n //CARDS    DD DSN=&&CARDS,DISP=(,PASS),                         \n //            UNIT=SYSDA,SPACE=(TRK,(1,1))                      \n //*                                                             \n //IN25SYMP EXEC PGM=IN25SYMP,REGION=2M                          \n //STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD                           \n //PROTSYM  DD DISP=SHR,DSN=&PROTSYM                             \n //INPUTT   DD DISP=SHR,DSN=&LISTLIB(&MEMBER)                    \n //CARDS    DD DSN=&&CARDS,DISP=(OLD,DELETE)                     \n //SYSPRINT   DD SYSOUT=*        \n //MESSAGE  DD SYSOUT=*                                               \n //MSGS     DD SYSOUT=*                                               \n //                                                               \n \n 1423", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3bc54e35738b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nYou can override the following procedure variables:\nVariable Description\nPROTSYM Specifies the name of the symbolic file being updated.\nNAME Specifies the name that is used to store the symbolic information\nin the PROTSYM file. This name is used by the Broadcom\nApplication Quality and Testing Tools products to locate the\nsymbolic information and is displayed when listing the contents of\nyour PROTSYM.\nWhen loading symbolic information for use with InterTest for CICS,\nspecify the name of the CICS program definition, or for composite\nsupport, specify the monitor name.\nLISTLIB Specifies the name of the partitioned data set containing the listing\nfrom the PL/I compiler.\nMEMBER Specifies the name of the member in the listing library that\ncontains the compiler listing for the program being added.\nLISTER Specifies how much of the listing to save in the PROTSYM file.\nCUTPRINT Specifies how much of the listing to write to the OUTPUT file.\nAdding IN25SYMP to Your PL/I Procedure\nTo automatically update the symbolic information in your PROTSYM file whenever a PL/I program is compiled, add a\npostprocessor step directly to the JCL procedure you use to compile your programs.\nFollow these steps to update your existing compile procedure:\n1.Ensure that your compile step specifies all of the required PL/I options.\n2.Change the DD statement so that a temporary disk file is created for your listing, if the SYSPRINT output from your\ncompile step is written to SYSOUT.\n3.Add a new IN25PARM step following your compile step to generate the parameter statement for the postprocessor.\n4.Add a new IN25SYMP step to postprocess the listing from the compile step. The INPUTT DD on this step refers to the\nsame file as the SYSPRINT DD from the compile step.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3bc54e35738b-1", "text": "same file as the SYSPRINT DD from the compile step.\n5.Add a new IEBGENER step to print the compiler listing only if the compiler detects errors.\nThe following example shows modifications to a compile procedure:\n //PLI      EXEC PGM=IBMZPLI,REGION=4M,                          \n //  PARM=('OBJ,X(F),A(F),OP,MAP,STG,AG,NEST,LIST',       <= 1  \n //       'NIS,S,NOPT,LIMITS(NAME(31)),FLAG(W)')\n  \n      (Your existing DD statements for PL/I)\n  \n //SYSPRINT DD DSN=&&LST,DISP=(NEW,PASS),                 <= 2\n //            UNIT=SYSDA,SPACE=(CYL,(1,2))    \n //*\n //*   GENERATE THE PARAMETER STATEMENT FOR IN25SYMP\n //*\n //CARDS   EXEC PGM=IN25PARM,REGION=1M,COND=(4,LT),       <= 3              \n //   PARM='&MEMBER,LISTER=ALL'                             \n //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR                                     \n //CARDS    DD DSN=&&CARDS,DISP=(NEW,PASS),                             \n //            UNIT=SYSDA,SPACE=(TRK,(1,1))                               \n //*\n 1424", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fb314086511b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n //*    POST-PROCESS THE COMPILER LISTING\n //*\n //SYM      EXEC PGM=IN25SYMP,REGION=4M,COND=(4,LT)       <= 4              \n //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR                                     \n //PROTSYM  DD DSN=USER.PROTSYM,DISP=SHR                                    \n //SYSPRINT DD SYSOUT=*\n //INPUTT   DD DSN=&&LST,DISP=(OLD,PASS)                      (See Note 1) \n //CARDS    DD DSN=&&CARDS,DISP=(OLD,DELETE)                  (See Note 2) \n //MESSAGE  DD SYSOUT=*                                                 \n //MSGS     DD SYSOUT=*                                                 \n //*\n //PRINT    EXEC PGM=IEBGENER,COND=(5,GT,PLI)         <= 5   \n //SYSUT1   DD DSN=&&LST,DISP=(OLD,DELETE)                              \n //SYSUT2   DD SYSOUT=*                                                 \n //SYSPRINT DD DUMMY                                                    \n //SYSIN    DD DUMMY                                                    \n \nNOTE\n\u2022If the SYSPRINT DD on your compile step refers to a permanent data set, the INPUTT DD for IN25SYMP\nmust point to the same data set.\n\u2022If you prefer to pass your parameter statement as an override in the invoking JCL, delete the CARDS step,\ndelete this DD statement, and add SYM.CARDS DD to your invoking JCL member.\nIN25SYMA\nUse program IN25SYMA to load symbolic information for Assembler programs into your PROTSYM file.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fb314086511b-1", "text": "Execute IN25SYMA as a standalone batch job to load a single Assembler listing that has been previously saved to a\npermanent file, or add it to your existing Assembler JCL procedure. The method you select depends entirely on the\nprocedures at your own installation. Both methods are described in this article.\nIN25SYMA JCL\nThe following table describes the DD statements used by IN25SYMA:\nDDname Description\nSTEPLIB The load library containing IN25SYMA.\nINPUT The listing that was written to SYSPRINT by the Assembler.\nOUTPUT All or part of the original Assembler listing is written to this file,\ndepending on your request.\nMESSAGE Messages produced by IN25SYMA during postprocessing are\nwritten to this file.\nPROTSYM The file to which the symbolic information is written.\nCARDS The input control statements that define the request.\nNOTE\nIf you are adding a new step for IN25SYMA to a JCL procedure, use program IN25PARM to write your input\ncontrol statements to the CARDS file.\n 1425", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "89f43a78c083-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIN25SYMA Options\nOptions are passed to IN25SYMA using a parameter statement in the CARDS DD. Specify the parameter statement as an\nin-stream control card, or when using a JCL procedure, generate it using program IN25PARM as follows:\n //IN25PARM EXEC PGM=IN25PARM,PARM='parameter statement'\n //STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD\n //CARDS    DD DISP=(,PASS),DSN=&&CARDS,UNIT=SYSDA,SPACE=(TRK,(1,1))\n \nParameter statements in the CARDS DD must begin in column 1.\nThe program name is the only required field on the parameter statement. This positional parameter defines the name\nthat is used to store the symbolic information in the PROTSYM file. This name is used by the Broadcom  Application\nQuality and Testing Tools products to locate the symbolic information and is displayed when listing the contents of your\nPROTSYM.\nIn most cases, this name should be the same as the first CSECT in the Assembler listing. When loading symbolic\ninformation for use with InterTest for CICS, you must specify the name of the CICS program definition, or when using\ncomposite support, specify the monitor name.\nThe following example shows an in-stream parameter statement that can be used to save symbolic information using the\nname ORDEDIT:\n //CARDS  DD *\n ORDEDIT\n /*\n \nControlling Printed Output with the CUTPRINT Option\nBecause you can load symbolic information from a permanent data set or a temporary listing file, you can also print all or\npart of the listing generated by the assembler.\nAppend the CUTPRINT option to your parameter statement to control printing of the assembler listing as follows:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "89f43a78c083-1", "text": "Append the CUTPRINT option to your parameter statement to control printing of the assembler listing as follows:\n,CUTPRINT=ALL\nDo not print any of the assembler listing.\n,CUTPRINT=REF\nStops printing the listing after the Cross Reference report.\nThe following sample parameter statement saves symbolic information for program ORDEDIT without printing any of the\nlisting:\n //CARDS   DD *\n ORDEDIT,CUTPRINT=ALL\n /*\n \nNOTE\nSpecify the CUTPRINT parameter only when you do not want all or part of your listing printed. The entire listing\nis printed if this parameter is omitted.\nSaving Your Listing for Online Display with the LISTER Option\nAppend the LISTER option to your parameter statement to control which portion of your source listing is saved to the\nPROTSYM file as follows:\n 1426", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8008fd014647-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n,LISTER=ALL\nSaves the entire assembler listing.\n,LISTER=REF\nSaves the listing up to, but not including, the Cross Reference report.\nThe following sample parameter statement saves symbolic information for program ORDEDIT while printing and saving\nthe listing up to, but not including, the Cross Reference report:\n //CARDS DD  *\n ORDEDIT,CUTPRINT=REF,LISTER=REF\n /*\n \nNOTE\n\u2022If the LISTER parameter is omitted, no listing is saved in the symbolic file.\n\u2022The LISTER parameter is required for use with Optimizer/II , SymDump  Batch, and InterTest Batch.\nSetting Data as Nonpurgeable\nYou can mark any saved symbolic data for this program as nonpurgeable. If a program's data is marked as nonpurgeable,\nthe data is not removed from the PROTSYM when deleting programs using a purge interval batch run. However, you can\ndelete the data by program name. See Maintaining a PROTSYM File for instructions on deleting data from the symbolic\nfile.\nTo mark data as nonpurgeable, add the NOPURGE option to your parameter statement as the last option.\nThe following sample parameter statement saves symbolic information for program ORDEDIT, prints the entire listing,\nsaves the entire listing in the PROTSYM file, and does not let symbolic data be removed from the symbolic file by a purge\ninterval batch run.\n //CARDS DD  *\n ORDEDIT,LISTER=ALL,NOPURGE\n /*\n \nRequired Assembler Options\nThe following listing options are required to load symbolic information for assembler programs:\nOption Description\nDXREF DSECT Cross-Reference\nESD External Symbol Dictionary\nNOBATCH Only one assembler source program is in the input source file\nUSING Using Map report", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8008fd014647-1", "text": "NOBATCH Only one assembler source program is in the input source file\nUSING Using Map report\nXREF(FULL) or XREF(SHORT) Full cross-reference or cross-reference of referenced names\nNOTE\n\u2022Do not suppress statements that define the start of a DSECT in the listing by PRINT OFF or PRINT NOGEN.\n\u2022High Level Assembler r2.0 users must also specify the LIST(121) option.\n\u2022High Level Assembler r4.0 users must specify the THREAD option. The NOTHREAD option is not supported.\n 1427", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "73d1b8a41d1d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nExecuting IN25SYMA as a Standalone Program\nMember CAVHSYMA in CAI.CAVHPROC contains sample JCL for executing postprocessor IN25SYMA as a standalone\nbatch job. Use this member to load symbolic information from previously saved Assembler listings.\n //CAVHSYMA PROC PROTSYM=CAI.PROTSYM,\n //             NAME=XXXXXXXX,                                \n //             LISTLIB=USER.LISTLIB, \n //             MEMBER=XXXXXXXX,                          \n //             LISTER=ALL,                                      \n //             CUTPRINT=ALL                                     \n //*                                                             \n //IN25PARM EXEC PGM=IN25PARM,REGION=512K,                       \n //             PARM='&MEMBER,LISTER=&LISTER,CUTPRINT=&CUTPRINT' \n //STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD                           \n //CARDS    DD DSN=&&CARDS,DISP=(,PASS),                         \n //            UNIT=SYSDA,SPACE=(TRK,(1,1))                      \n //*                                                             \n //IN25SYMA EXEC PGM=IN25SYMA,REGION=2M                          \n //STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD                           \n //PROTSYM  DD DISP=SHR,DSN=&PROTSYM                             \n //INPUT    DD DISP=SHR,DSN=&LISTLIB(&MEMBER)                    \n //CARDS    DD DSN=&&CARDS,DISP=(OLD,DELETE)                     \n //OUTPUT   DD SYSOUT=*, DCB=(RECFM=FBM,LRECL=121,BLKSIZE=2420)\n //MESSAGE  DD SYSOUT=*                                               \n //                                                                   \n \nYou can override the following procedure variables:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "73d1b8a41d1d-1", "text": "//                                                                   \n \nYou can override the following procedure variables:\nVariable Description\nPROTSYM Specifies the name of the symbolic file being updated.\nNAME Specifies the name that is used to store the symbolic information\nin the PROTSYM file. This name is used by the Broadcom\nApplication Quality and Testing Tools products to locate the\nsymbolic information and is displayed when listing the contents of\nyour PROTSYM.\nIn most cases, this is the name of the first CSECT in the\nassembler listing. When loading symbolic information for use\nwith InterTest for CICS, specify the name of the CICS program\ndefinition, or for composite support, specify the monitor name.\nLISTLIB Specifies the name of the partitioned data set containing the\nAssembler listing.\nMEMBER Specifies the name of the member in the listing library that\ncontains the Assembler listing for the program being added.\nLISTER Specifies how much of the listing to save in the PROTSYM file.\nCUTPRINT Specifies how much of the listing to write to the OUTPUT file.\nAdding IN25SYMA to Your Assembler Procedure\nTo automatically update the symbolic information in your PROTSYM file whenever a program is assembled, add a\npostprocessor step directly to the JCL procedure that you use to assemble your programs.\n 1428", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3c304db43012-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFollow these steps to update your existing assembly procedure:\n1.Ensure that your assemble step specifies all of the required Assembler options.\n2.If the SYSPRINT output from your assemble step is written to SYSOUT, change the DD statement so that a temporary\ndisk file is created for your listing.\n3.Add a new IN25PARM step following your assemble step to generate the parameter statement for the postprocessor.\n4.Add a new IN25SYMA step to postprocess the listing from the assemble step. The INPUT DD on this step refers to the\nsame file as the SYSPRINT DD from the assemble step.\n5.Add a new IEBGENER step to print the Assembler listing only if errors were detected during the assembly.\nThe following example shows modifications to an assembly procedure:\n //ASM      EXEC PGM=ASMA90,REGION=4M,                          \n //  PARM='LIST,OBJECT,XREF(FULL),ESD'                    <= 1  \n  \n      (Your existing DD statements for the Assembler)\n  \n //SYSPRINT DD DSN=&&LST,DISP=(NEW,PASS),                 <= 2\n //            UNIT=SYSDA,SPACE=(CYL,(1,2))    \n //*\n //*   GENERATE THE PARAMETER STATEMENT FOR IN25SYMA\n //*\n //CARDS   EXEC PGM=IN25PARM,REGION=1M,COND=(4,LT),       <= 3              \n //   PARM='&MEMBER,LISTER=ALL'                             \n //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR                                     \n //CARDS    DD DSN=&&CARDS,DISP=(NEW,PASS),", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3c304db43012-1", "text": "//CARDS    DD DSN=&&CARDS,DISP=(NEW,PASS),                             \n //            UNIT=SYSDA,SPACE=(TRK,(1,1))                               \n //*\n //*    POST-PROCESS THE COMPILER LISTING\n //*\n //SYM      EXEC PGM=IN25SYMA,REGION=4M,COND=(4,LT)       <= 4              \n //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR                                     \n //PROTSYM  DD DSN=USER.PROTSYM,DISP=SHR                                    \n //OUTPUT   DD SYSOUT=*,DCB=(RECFM=FBM,LRECL=121,BLKSIZE=2420)\n //INPUT    DD DSN=&&LST,DISP=(OLD,PASS)                      (See Note 1)\n //CARDS    DD DSN=&&CARDS,DISP=(OLD,DELETE)                  (See Note 2)\n //MESSAGE  DD SYSOUT=*                                                 \n //*\n //PRINT    EXEC PGM=IEBGENER,COND=(5,GT,ASM)             <= 5\n //SYSUT1   DD DSN=&&LST,DISP=(OLD,DELETE)                              \n //SYSUT2   DD SYSOUT=*                                                 \n //SYSPRINT DD DUMMY                                                    \n //SYSIN    DD DUMMY                                                    \n \nNOTE\n\u2022If the SYSPRINT DD on your compile step refers to a permanent data set, the INPUT DD for IN25SYMA\nmust point to the same data set.\n\u2022If you prefer to pass your parameter statement as an override in the invoking JCL, delete the CARDS step,\ndelete this DD statement, and add SYM.CARDS DD to your invoking JCL member.\n 1429", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e9e7ae0e5b44-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIN25LINK\nUse program IN25LINK to define the additional symbolic information required for testing composite modules using\nInterTest for CICS.\nA composite module consists of separately compiled or assembled parts that are brought together under a single module\nname by the IBM Linkage Editor. In CICS, a composite module has only one CICS program definition. You can write the\nmain program and the called subroutines in the same or different languages.\nThe Composite Support feature of InterTest for CICS lets you test the subroutines of a composite module as if they were\nseparate programs with separate CICS program definitions. For more information about this feature, see Composite\nSupport.\nIN25LINK uses output from the IBM Linkage Editor and your own additional input cards to associate the subroutines of\na composite module with the monitor names you define. Typically, this program is executed as a standalone batch job to\nload output from a single link step.\nIf the Symbolic File in the JCL PROTSYM DD statement was initialized to allow multiple program version support, the\nIN25LINK control statement information will be associated with the latest or most recently compiled program version\nspecified by the monitor-name .\nNOTE\nWhile it is more efficient to use IN25LINK for composite support, you can provide the same information online\nusing the InterTest for CICS COMPOSITE command or CNTL menu.\nIN25LINK JCL\nThe following table describes the DD statements used by IN25LINK:\nDDname Description\nSTEPLIB The load library containing IN25LINK.\nINPUT The listing that was written to SYSPRINT by the IBM Linkage\nEditor.\nOUTPUT All or part of the original listing is written to this file, depending on\nyour request.\nMESSAGE Messages produced by IN25LINK during postprocessing are\nwritten to this file.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e9e7ae0e5b44-1", "text": "MESSAGE Messages produced by IN25LINK during postprocessing are\nwritten to this file.\nPROTSYM The file to which the symbolic information is written.\nCARDS The input control statements that define the relationships between\nyour monitor names and the subroutines of your composite\nmodule.\nIN25LINK Options\nOptions are passed to IN25LINK using parameter statements in the CARDS DD. Parameter statements in the CARDS DD\nmust begin in column 1.\nIdentifying the Composite Module\nThe first parameter card is required . It specifies the CICS program definition name of the composite module, beginning in\ncolumn 1, as follows:\n composite-name[,NOPURGE]\n \n 1430", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "29cfd371d44c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe program name specified in this parameter statement must be the same as the CICS program definition name of the\ncomposite module.\nYou can also specify the NOPURGE option on this statement. This option specifies that symbolic information for the\ncomposite module cannot   be purged from the PROTSYM file during a purge interval batch job.\nIdentifying the Main Program and Subroutines\nSubsequent parameter cards optionally identify the main program and each subroutine that you want to test separately.\nThese cards can be entered in any order and must specify two names, separated by commas, as follows:\n link-name, monitor-name\n \nlink-name identifies the name of the control section as listed in the link-edit map, and must begin in column 1. For a PL/I\nprogram, specify the name of the compiler-generated control section that ends with '1'.\nmonitor-name specifies the name under which the program is monitored. Follow these rules in selecting a monitor-name :\n\u2022Each monitor-name must be unique.\n\u2022The monitor-name of a subroutine cannot be the same as a CICS program definition name.\n\u2022The monitor-name can be identical to the link-name .\nOnly the first parameter card is required; omit all subsequent cards. If you omit the subsequent parameter cards, only the\nname of the composite module is stored in the PROTSYM file. When you attempt to monitor the composite module with\nInterTest for CICS, you are prompted for additional composite information.\nExcluding Subroutines\nBy default, IN25LINK excludes subroutines with CEE, DFH, DLZ, IBM, IGZ, and ILB prefixes when it reads the link-edit\nmap. Usually, you will not want to test these programs.\nYou can change the default exclusion rules using a parameter card, positioned anywhere in the CARDS file after the first", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "29cfd371d44c-1", "text": "card, beginning in column 1, as follows:\n EXCLUDE=\n \n(or)\n EXCLUDE=name[,name,\u2026,name]\n \nSpecifying EXCLUDE without any names instructs IN25LINK not to exclude any subroutines.\nSpecifying EXCLUDE= xxxxxxxx  instructs IN25LINK to exclude subroutines whose names are represented by xxxxxxxx .\nSpecify the entire link-name  to exclude a specific subroutine, or specify a prefix to exclude a group of subroutines.\nFor example, to exclude all subroutines with the prefix ACA1, specify:\n EXCLUDE=ACA1\n \nExample\nA composite module with the CICS program definition name BIGMOD consists of several separately compiled programs\nand library modules. Its main program is named MAINMOD and is written in COBOL.\nBIGMOD also has three Assembler subroutines named SUBMODA, SUBMODB, and SUBMODC that you want to test\nseparately. None of the subroutines has its own CICS program definition entry.\n 1431", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "21d024829a6f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAfter assembling SUBMODA, SUBMODB, and SUBMODC, you loaded their symbolic information by executing\npostprocessor IN25SYMA. You selected monitor names of ASMMODA, ASMMODB, and ASMMODC for the subroutines.\nNext, you compiled MAINMOD and loaded its symbolic information by executing postprocessor IN25COB2. You specified\nBIGMOD as the monitor name, matching the CICS program definition as required.\nThe linkage editor combines the main program and its three subroutines, creating the composite load module named\nBIGMOD. The link-edit map output for BIGMOD shows a main entry address of 160, that BIGMOD has been replaced in\nthe load library, and that it contains the following modules:\n Control Section Origin  Length  Description \n DFHECI      00  160 Command level COBOL stub    \n MAINMOD     160 78A8    Main program-COBOL  \n ILBOATB     7A08    11A COBOL library module    \n ILBOCOM0    7B28    73  COBOL library module    \n SUBMODA 7CA0    1200    Subprogram-Assembler    \n SUBMODB 8EA0    100 Subprogram-Assembler    \n SUBMODC 9EA1    93  Subprogram-Assembler    \n \nSample JCL for the link-edit step and IN25LINK is shown as follows:\n //*\n //* Link Edit Step\n //*\n //LKED     EXEC PGM=IEWL,......\n //SYSLIB   DD.....\n //SYSLMOD  DD.....\n //SYSUT1   DD.....\n //SYSLIN   DD.....\n //SYSPRINT DD DSN=&&INPUT,DISP=(,PASS),", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "21d024829a6f-1", "text": "//SYSPRINT DD DSN=&&INPUT,DISP=(,PASS),\n //   UNIT=SYSDA,SPACE=(TRK,(2,5)),\n //   DCB=(DSORG=PS,LRECL=121,BLKSIZE=2420,RECFM=FB)\n //*\n //* IN25LINK Step\n //*\n //POSTLINK EXEC PGM=IN25LINK,REGION=512K\n //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR\n //INPUT    DD DSN=&&INPUT,DISP=(OLD,DELETE)\n //MESSAGE  DD SYSOUT=*\n //OUTPUT   DD SYSOUT=*,\n //   DCB=(RECFM=FBA,LRECL=121,BLKSIZE=2420)\n //PROTSYM  DD DSN=INTRTST.PROTSYM,DISP=SHR\n //CARDS    DD *\n BIGMOD             CICS program definition name of composite module  \n MAINMOD,BIGMOD     link-name and monitor-name of main program  \n SUBMODA,ASMMODA    link-name and monitor-name of subprogram  \n SUBMODB,ASMMODB    link-name and monitor-name of subprogram  \n SUBMODC,ASMMODC    link-name and monitor-name of subprogram  \n /*\n \nRequired Linkage Editor Options\nIf you are using DFSMS 1.1, you must specify the MAP parameter on the link-edit step.\n 1432", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dfd169daa8ea-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nExecuting IN25LINK as a Standalone Program\nMember CAVHLINK in CAI.CAVHPROC contains sample JCL for executing postprocessor IN25LINK as a standalone\nbatch job. Use this member to load composite information from a previously saved Linkage Editor listing.\n //CAVHLINK PROC PROTSYM=CAI.PROTSYM,                          \n //             LISTLIB=USER.LISTLIB                          \n //             MEMBER=XXXXXXXX\n //*                                                          \n //IN25LINK EXEC PGM=IN25LINK,REGION=2M                       \n //STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD                        \n //PROTSYM  DD DISP=SHR,DSN=&PROTSYM                          \n //INPUT    DD DISP=SHR,DSN=&LISTLIB(&MEMBER)                 \n //OUTPUT   DD SYSOUT=*,DCB=(LRECL=121,BLKSIZE=2440,RECFM=FBA)\n //CARDS    DD DDNAME=CARDS                                   \n //MESSAGE  DD SYSOUT=*                                                                                      \n      \n \nYou can override the following procedure variables:\nVariable Description\nPROTSYM Specifies the name of the symbolic file being updated.\nLISTLIB Specifies the name of the partitioned data set containing your\nsaved IBM Linkage Editor output listings.\nMEMBER Specifies the name of the member in the listing library that\ncontains the listing for the composite module.\nWhen invoking this JCL procedure, you must include a CARDS DD statement in the invoking JCL.\nAdding IN25LINK to Your Link-Edit Procedure\nTo automatically update the symbolic information in your PROTSYM file whenever a program is link-edited, you can add a\npostprocessor step directly to the JCL procedure that you use to link-edit your programs.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dfd169daa8ea-1", "text": "postprocessor step directly to the JCL procedure that you use to link-edit your programs.\nFollow these steps to update your existing link-edit procedure:\n1.Ensure that your link-edit step specifies all of the required link-edit options.\n2.If the SYSPRINT output from your link-edit step is written to SYSOUT, change the DD statement so that a temporary\ndisk file is created for your listing.\n3.Add a new IN25PARM step following your link-edit step to generate the parameter statement for the postprocessor.\n4.Add a new IN25LINK step to postprocess the listing from the link-edit step. The INPUT DD on this step refers to the\nsame file as the SYSPRINT DD from the link-edit step.\n5.Add a new IEBGENER step to print the linkage editor listing only if errors were detected during the link.\nThe following example shows modifications to a link-edit procedure:\n //LINK      EXEC PGM=IEWL,REGION=2M,                          \n //  PARM='LIST,LET,XREF,MAP'                             <= 1  \n  \n      (Your existing DD statements for the link edit)\n  \n //SYSPRINT DD DSN=&&LST,DISP=(NEW,PASS),                 <= 2\n //            UNIT=SYSDA,SPACE=(CYL,(1,2))    \n //*\n 1433", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ff0f20eaf9e7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n //*   GENERATE THE PARAMETER STATEMENT FOR IN25LINK\n //*\n //CARDS   EXEC PGM=IN25PARM,REGION=1M,COND=(4,LT),       <= 3              \n //   PARM='&MEMBER'                             \n //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR                                     \n //CARDS    DD DSN=&&CARDS,DISP=(NEW,PASS),                             \n //            UNIT=SYSDA,SPACE=(TRK,(1,1))                               \n //*\n //*    POST-PROCESS THE LINK EDIT OUTPUT\n //*\n //SYM      EXEC PGM=IN25LINK,REGION=4M,COND=(4,LT)       <= 4              \n //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR                                     \n //PROTSYM  DD DSN=USER.PROTSYM,DISP=SHR                                    \n //OUTPUT   DD SYSOUT=*,DCB=(RECFM=FBM,LRECL=121,BLKSIZE=2420)\n //INPUT    DD DSN=&&LST,DISP=(OLD,PASS)                      (See Note 1)\n //CARDS    DD DSN=&&CARDS,DISP=(OLD,DELETE)                  (See Note 2)\n //MESSAGE  DD SYSOUT=*                                                 \n //*\n //PRINT    EXEC PGM=IEBGENER,COND=(5,GT,LINK)            <= 5\n //SYSUT1   DD DSN=&&LST,DISP=(OLD,DELETE)                              \n //SYSUT2   DD SYSOUT=*                                                 \n //SYSPRINT DD DUMMY                                                    \n //SYSIN    DD DUMMY                                                    \n \nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ff0f20eaf9e7-1", "text": "//SYSIN    DD DUMMY                                                    \n \nNOTE\n\u2022If the SYSPRINT DD on your link-edit step refers to a permanent data set, the INPUT DD for IN25LINK must\npoint to the same data set.\n\u2022If you prefer to pass your parameter statement as an override in the invoking JCL, delete the CARDS step,\ndelete this DD statement, and add SYM.CARDS DD to your invoking JCL member.\nNOTE\nUsing this method, IN25PARM only generates the first parameter card identifying the name of the composite\nmodule. No subsequent cards are generated. This serves only to identify the name of the composite module,\nwhich is stored in the PROTSYM file. When you attempt to monitor the composite module with InterTest for\nCICS, you may be prompted for additional composite information.\nIN25SYMD\nUse program IN25SYMD to load symbolic information from multiple COBOL, Assembler, C, or PL/I listings into your\nPROTSYM in a single run.\nThe following table describes the DD statements used by IN25SYMD:\nDDname Description\nSTEPLIB The load library containing IN25SYMD.\nPROTSYM The file to which the symbolic information is written.\nLISTLIB The data set name of the PDS, PDSE, Librarian  library, Panvalet\nlibrary, or Endevor  library containing the listings to be added.\nREPORT An execution summary is written to this file.\nOPTIN The input control statements that define the request.\n 1434", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "efe4f663ade1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWhen you load symbolic information from Endevor , ensure that the Endevor  AUTHLIB, CONLIB, and the data set\ncontaining C1DEFLTS are either in LINKLIST or in the STEPLIB concatenation. When you load symbolic information from\nLibrarian  or Panvalet , ensure that the Librarian  or Panvalet  CAILIB is either in Linklist or in the STEPLIB concatenation.\nIN25SYMD Options\nOptions are passed to the IN25SYMD using parameter statements in the OPTIN DD. Specify the parameter statements as\nan in-stream file.\nParameter statements contain one or more control statements, separated by commas, and each having the following\nsyntax:\nkeyword=value\nSpecify the following option keywords to IN25SYMD:\nKeyword Description\nLTYP Identifies the library type of the listing library specified by the\nLISTLIB DD statement. This keyword is required. Valid values are:\nPDS -- Partitioned data set (including PDSE)\nSEQ -- Sequential data set (see Note)\nLIB -- Librarian  library\nPAN -- Panvalet  library\nNDV -- Endevor  library\nFROM Identifies the member name for single listings, the starting\nmember name for a range of members, or a name prefix with\ntrailing asterisk. This keyword is required.\nTO Identifies the last member name in a range of members.\nMSG Identifies the message reporting level. Valid values are:\nALL -- displays all messages.\nRC -- displays a one-line return code message for each program.\nNONE -- suppresses all messages.\nNOTE\nWhen LTYP=SEQ is specified, the sequential file contains only one program listing. Specify the symbolic name\nusing the FROM keyword, omit the TO keyword, and change the LISTLIB DD name to INPUT.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "efe4f663ade1-1", "text": "using the FROM keyword, omit the TO keyword, and change the LISTLIB DD name to INPUT.\nWhen using LTYP=NDV, you must also change the EXEC card to the following JCL:\n//STEP1   EXEC PGM=NDVRC1,PARM='IN25SYMD',REGION=4M\nExamples\nThis section contains postprocessor IN25SYMD examples.\nExample 1\nAll of the programs with the prefix PAY are loaded into the PROTSYM file from a Librarian  library, with all of the messages\ndisplayed in the REPORT file.\n//STEP1    EXEC PGM=IN25SYMD,REGION=4M                                 \n//STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD                        \n//PROTSYM  DD DISP=SHR,DSN=USER.PROTSYM                       \n 1435", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9e5a9a6eed32-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n//LISTLIB  DD DISP=SHR,DSN=USER.LIBRARIAN.LIBRARY\n//REPORT   DD SYSOUT=*                                                 \n//OPTIN    DD *                                                        \n LTYP=LIB,FROM=PAY*,MSG=ALL  \n/*   \nExample 2\nProgram COBDEMO is loaded into the PROTSYM file from a sequential listing file, with messages suppressed. Note that\nthe DD statement for the LISTLIB has been renamed to INPUT for LTYP=SEQ.\n//STEP1    EXEC PGM=IN25SYMD,REGION=4M                                 \n//STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD                        \n//PROTSYM  DD DISP=SHR,DSN=USER.PROTSYM                       \n//INPUT    DD DISP=SHR,DSN=USER.SEQ.LISTING                                 \n//REPORT   DD SYSOUT=*                                                 \n//OPTIN    DD *                                                        \n LTYP=SEQ,FROM=COBDEMO,MSG=NONE\n/*   \nExample 3\nPrograms whose names begin with C, D, or E are loaded into the PROTSYM file from a partitioned data set. A one-line\nreturn code message is written to the REPORT file for each program.\n//STEP1    EXEC PGM=IN25SYMD,REGION=4M                                 \n//STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD                        \n//PROTSYM  DD DISP=SHR,DSN=USER.PROTSYM                       \n//LISTLIB  DD DISP=SHR,DSN=USER.PDS.LIBRARY                               \n//REPORT   DD SYSOUT=*                                                 \n//OPTIN    DD *                                                        \n LTYP=PDS,FROM=C,TO=E9999999,MSG=RC", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9e5a9a6eed32-1", "text": "LTYP=PDS,FROM=C,TO=E9999999,MSG=RC\n/*\nMaintaining a PROTSYM File\nThe IN25UTIL batch utility program maintains and reports on the symbolic file. This program runs in batch, separate from\nthe postprocessors that are used to load symbolic information into the symbolic file. This article describes how to maintain\nthe PROTSYM file using IN25UTIL.\nIN25UTIL JCL\nMember CAVHUTIL in CAI.CAVHJCL contains the following sample JCL for executing IN25UTIL:\n //         JOB                                          \n//IN25UTIL EXEC PGM=IN25UTIL,REGION=2M                  \n//STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD                   \n//PROTSYM  DD DISP=SHR,DSN=USER.PROTSYM                 \n//OUTPUT   DD SYSOUT=*,DCB=(LRECL=133,BLKSIZE=3990)     \n//MESSAGE  DD SYSOUT=*                                  \n//CARDS    DD *                                         \n(input cards go here)                                                                                        \n  \n/*\n 1436", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5a38f3e6a5be-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n \nThe following table describes the DD statements used by IN25UTIL:\nDDname Description\nSTEPLIB The load library containing IN25UTIL.\nPROTSYM The file on which maintenance or reporting is being performed.\nMESSAGE Output and messages from IN25UTIL are written to this file.\nOUTPUT Output from the PRINT function is written to this file.\nUNLOAD Program is written to this file by the UNLOAD function.\nRELOAD Program is read from this file by the RELOAD function.\nCARDS Contains the function request statements.\nIN25UTIL Functions\nIN25UTIL functions are requested using control statements in the CARDS file. All control statements in the CARDS file\nmust begin in column 1.\nNOTE\nSome of the following functions support parameters that modify the function results. Supported parameters are\nnoted in the function description. For complete parameter descriptions, see IN25UTIL Parameters.\nDELETE=name\nDeletes all symbolic data for the program specified by name.\nThe PASSWORD control statement, if specified, must precede the DELETE control statement.\nYou can use generic program names on the DELETE control statement. Use a trailing wildcard (*) in the program\nname to delete all matching programs.\nThe DELETE function supports the following parameters: AFTERDATETIME, ALL, BEFOREDATETIME,\nDATETIME, NEWEST, OLDEST. You cannot use these parameters with a generic program name.\nExample: Delete Symbolic Information by Program\nThe following example deletes all symbolic data for program ORDEDIT and the oldest version of program TEST1. It also\ndeletes all programs that start with COB.\n //UTILITY  JOB\n //STEP1    EXEC PGM=IN25UTIL\n //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR\n //MESSAGE  DD SYSOUT=*", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5a38f3e6a5be-1", "text": "//MESSAGE  DD SYSOUT=*\n //PROTSYM  DD DSN=CAI.PROTSYM,DISP=SHR\n //CARDS    DD *\n PASSWORD=12345678\n DELETE=ORDEDIT,ALL\n DELETE=TEST1,OLDEST\n DELETE=COB*\n /*\n \nINITIALIZE\nInitializes the symbolic file. This function must always be run after a symbolic file is created using VSAM Access\nMethod Services.\nFor a newly defined file, the IN25UTIL program preformats all records. If you perform this function for an existing\nfile, all symbolic data is removed.\nThe PASSWORD control statement, if specified, must precede the INITIALIZE control statement.\n 1437", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "762a5986f6f8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe INITIALIZE function supports the MAXPGMVER and USEDSPACEMSG parameters.\nExamples: Initialize a Symbolic File\nThe following example initializes a symbolic file without support for multiple program versions:\n //UTILITY  JOB\n //STEP1    EXEC PGM=IN25UTIL\n //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR\n //MESSAGE  DD SYSOUT=*\n //PROTSYM  DD DSN=CAI.PROTSYM,DISP=SHR\n //CARDS    DD *\n PASSWORD=12345678\n INITIALIZE\n /*\n \nThe following example initializes a symbolic file that allows for up to three versions of each program:\n //UTILITY  JOB\n //STEP1    EXEC PGM=IN25UTIL\n //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR\n //MESSAGE  DD SYSOUT=*\n //PROTSYM  DD DSN=CAI.PROTSYM,DISP=SHR\n //CARDS    DD *\n PASSWORD=12345678\n INITIALIZE,MAXPGMVER=3\n /*\n \nPASSWORD=pw\nSpecifies a password that is required when maintaining the symbolic file. You need to specify the password only\nonce per execution, but it must precede the first update request.\nThe value specified must match the value of the SYMPSWD keyword in the CAVHCONF macro.\nIf EXTSEC=SYMBOLIC is enabled on the CAVHCONF macro, then the PASSWORD=pw statement is not\nrequired and will be ignored.\nThe default installation password is 12345678.\nPRINT=name\nPrints the newest or most recent version of the program on the PROTSYM file specified by name. Ensure to\nprovide the OUTPUT DDname.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "762a5986f6f8-1", "text": "provide the OUTPUT DDname.\nThe PRINT function supports the following parameters: AFTERDATETIME, ALL, BEFOREDATETIME,\nDATETIME, NEWEST, OLDEST.\nExample: Print a Program Listing\nThe following example prints the newest saved listing for program ORDEDIT, all saved listings for program TEST1, and all\nlistings for program TEST2 that were saved after 28 January, 2014:\n //UTILITY  JOB\n //STEP1    EXEC PGM=IN25UTIL\n //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR\n //MESSAGE  DD SYSOUT=*\n //OUTPUT   DD SYSOUT=A,DCB=(LRECL=133,BLKSIZE=3990)\n //PROTSYM  DD DSN=CAI.PROTSYM,DISP=SHR\n //CARDS DD *\n PRINT=ORDEDIT\n PRINT=TEST1,ALL\n 1438", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ac7ad3205636-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n PRINT=TEST2,AFTERDATETIME=2014/01/28\n /*\n \nPURGE=nnn\nRemoves symbolic data for any program that has not been compiled or assembled within the number of days\nspecified by nnn, where nnn is a decimal number from 1 to 365.\nThe PASSWORD control statement, if specified, must precede the PURGE control statement.\nData for programs loaded using the NOPURGE postprocessor option are not affected by this function.\nExample: Purge Symbolic Information by Age\nThe following example purges all programs that have not been compiled or assembled within the last 20 days:\n //UTILITY  JOB\n //STEP1    EXEC PGM=IN25UTIL\n //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR\n //MESSAGE  DD SYSOUT=*\n //PROTSYM  DD DSN=CAI.PROTSYM,DISP=SHR\n //CARDS    DD *\n PASSWORD=12345678\n PURGE=20\n /*\n \nRELOAD= name\nReloads all symbolic data from a dataset to the symbolic file for the program specified by name . To reload\nsymbolic data for all programs, specify RELOAD=ALL. Ensure to provide the RELOAD DDname with the following\nDCB parameter:\nDCB=(RECFM=FB,LRECL=2042,BLKSIZE=20420)\nThe PASSWORD control statement, if specified, must precede the RELOAD control statement.\nYou can use generic program names on the RELOAD control statement. Use a trailing wildcard (*) in the program\nname to reload all matching programs.\nThe RELOAD function supports the following parameters: AFTERDATETIME, ALL, BEFOREDATETIME,", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ac7ad3205636-1", "text": "DATETIME, NEWEST, OLDEST. These parameters cannot be used with a generic program name.\nYou can rename a program that is being a reloaded by providing a new program name after the RELOAD control\nstatement and any multiversion subparameters. You cannot rename a program when you specify a generic\nprogram name.\nExample: Reload Programs\nThe following example reloads the newest version of program ORDEDIT and all versions that were processed in\nFebruary, 2015. It also reloads the oldest version of ORDEDIT while renaming it to ORDEDIT2 and reloads all programs\nthat start with COB.\n //UTILITY  JOB\n //STEP1 EXEC PGM=IN25UTIL\n //STEPLIB DD DSN=CAI.CAVHLOAD,DISP=SHR\n //MESSAGE DD SYSOUT=*\n //RELOAD   DD  DISP=SHR,DSN=USER.UNLOAD, \n //         DCB=(RECFM=FB,LRECL=2042,BLKSIZE=20420)\n //PROTSYM DD DSN=CAI.PROTSYM,DISP=SHR\n //CARDS DD *\n PASSWORD=12345678\n RELOAD=ORDEDIT\n RELOAD=ORDEDIT,DATETIME=2015/02\n 1439", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d0546f7f5c81-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n RELOAD=ORDEDIT,OLDEST,ORDEDIT2\n RELOAD=COB*\n /*\n \nREPORT\nProduces a Symbolic File report that contains statistics and a detailed report on each program.\nExample: Generate Reports\n //UTILITY  JOB\n //STEP1    EXEC PGM=IN25UTIL\n //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR\n //MESSAGE  DD SYSOUT=*\n //PROTSYM  DD DSN=CAI.PROTSYM,DISP=SHR\n //CARDS    DD *\n REPORT\n /*\n \nUNLOAD= name\nUnloads all symbolic data from the symbolic file to a dataset for the program specified by name. To unload\nsymbolic data for all programs, specify UNLOAD=ALL. Ensure to provide the UNLOAD DDname with the\nfollowing DCB parameter:\nDCB=(RECFM=FB,LRECL=2042,BLKSIZE=20420)\nYou can use generic program names on the UNLOAD control statement. Use a trailing wildcard (*) in the program\nname to unload all matching programs.\nThe UNLOAD function supports the following parameters: AFTERDATETIME, ALL, BEFOREDATETIME,\nDATETIME, NEWEST. You cannot use these parameters with a generic program name.\nExample: Unload Programs\nThe following example unloads all versions of program ORDEDIT that were processed after 31 December, 2014. It also\nunloads all programs that start with COB.\n //UTILITY  JOB\n //STEP1 EXEC PGM=IN25UTIL\n //STEPLIB DD DSN=CAI.CAVHLOAD,DISP=SHR\n //MESSAGE DD SYSOUT=*\n //PROTSYM DD DSN=CAI.PROTSYM,DISP=SHR", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d0546f7f5c81-1", "text": "//PROTSYM DD DSN=CAI.PROTSYM,DISP=SHR\n //UNLOAD   DD  DSN=USER.UNLOAD, \n //         DISP=(NEW,CATLG,CATLG),SPACE=(CYL,(5,10),RLSE),\n //         DCB=(RECFM=FB,LRECL=2042,BLKSIZE=20420)\n //CARDS DD *\n UNLOAD=ORDEDIT,AFTERDATETIME=2014/12/31\n UNLOAD=COB*\n /*\n \nUPDATE\nUpdates the values for the USEDSPACEMSG parameter. The PASSWORD control statement, if specified, must\nprecede the UPDATE control statement.\nExample: Update a PROTSYM Parameter\nThe following example sets the USEDSPACEMSG parameter of the symbolic file to 80:\n //UTILITY  JOB\n 1440", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9f1d068760f9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n //STEP1    EXEC PGM=IN25UTIL\n //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR\n //MESSAGE  DD SYSOUT=*\n //PROTSYM  DD DSN=CAI.PROTSYM,DISP=SHR\n //CARDS    DD *\n PASSWORD=12345678\n UPDATE,USEDSPACEMSG=80\n /*\n \nExample: Reorganize the Symbolic File\nThe following example reorganizes or changes the size of the symbolic file. This job unloads all programs, deletes and\ndefines the symbolic file, initializes the symbolic file, reloads all programs, and generates a system report.\n //UTILITY  JOB\n //UNLOAD   EXEC PGM=IN25UTIL\n //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR\n //SYSUDUMP DD SYSOUT=*\n //MESSAGE  DD SYSOUT=*\n //UNLOAD   DD  DSN=USER.RELOAD, \n //         DISP=(NEW,CATLG,CATLG),SPACE=(CYL,(5,10),RLSE),\n //         DCB=(RECFM=FB,LRECL=2042,BLKSIZE=20420)\n //PROTSYM  DD DSN=CAI.PROTSYM,DISP=SHR\n //CARDS    DD *\n UNLOAD=ALL\n /*\n //IDCAMS   EXEC PGM=IDCAMS,COND=(0,NE,UNLOAD)\n //SYSUT1   DD  UNIT=SYSDA,VOL=SER=SYMVOL,DISP=SHR\n //SYSIN    DD  *\n       DELETE 'CAI.PROTSYM'\n       DEFINE CLUSTER (NAME(CAI.PROTSYM) -", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9f1d068760f9-1", "text": "DEFINE CLUSTER (NAME(CAI.PROTSYM) -\n                   VOLUME(SYMVOL)   -\n                   FILE(SYSUT1)     -\n                   CYLINDERS(20)    -\n                   CISZ(2048)       -\n                   RECSZ(2040 2040) -\n                   SHR(4 4)         -\n                   NUMBERED)        -\n      DATA (NAME(CAI.PROTSYM.DATA))\n /*\n //RELOAD   EXEC PGM=IN25UTIL,COND=(0,NE,UNLOAD)\n //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR\n //SYSUDUMP DD SYSOUT=*\n //MESSAGE  DD SYSOUT=*\n //RELOAD   DD  DISP=SHR,DSN=USER.RELOAD, \n //         DCB=(RECFM=FB,LRECL=2042,BLKSIZE=20420)\n //PROTSYM  DD DSN=CAI.PROTSYM,DISP=SHR\n //CARDS    DD *\n PASSWORD=12345678\n INITIALIZE\n RELOAD=ALL\n REPORT\n /*\n 1441", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e0c578978173-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n \nIN25UTIL Parameters\nSome functions support parameters that modify the function results. The functions that support these parameters are\nnoted in the function description.\nAFTERDATETIME=YYYY/MM/DD HH:MM:SS\nApplies the function to all versions of the saved source listing for the program specified by name  which were\ncompiled after the specified date timestamp.\nYou can provide a partial timestamp by omitting time values starting from the smallest unit of time.\nNOTE\nA partial timestamp can also be provided for BEFOREDATETIME and DATETIME.\nALL\nApplies the function to all versions of the saved source listing for the program specified by name . Do not confuse\nthe ALL parameter with the RELOAD=ALL and UNLOAD=ALL functions.\nBEFOREDATETIME=YYYY/MM/DD HH:MM:SS\nApplies the function to all versions of the saved source listing for the program specified by name  which were\ncompiled before the specified date timestamp.\nDATETIME=YYYY/MM/DD HH:MM:SS\nApplies the function to all versions of the saved source listing for the program specified by name  which were\ncompiled on the specified date timestamp.\nMAXPGMVER\nIndicates the number of versions of a single program the PROTSYM will allow (up to 255). The default value\nis 1, which indicates no multiple program versions. For assembler programs, multiple program version support\nuses the HLASM compile date/time on the listing that has the format 2014/08/04 08.36. Hence, multiple program\nlistings for the same program that are compiled within the same minute are not supported.\nNEWEST\nApplies the function to the newest version of the saved source listing for the program specified by name .\nOLDEST", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e0c578978173-1", "text": "OLDEST\nApplies the function to the oldest version of the saved source listing for the program specified by name .\nUSEDSPACEMSG\nSpecifies the limit of used space in PROTSYM in percentage. When the limit is reached, the SYM070 message is\nissued. If the value equals 0, the SYM070 message is not issued.\nDefault: 0\nValues: 0-99\nDynamic Symbolic Support for Endevor  Software Change Manager\nDynamic symbolic support is an automated way to update your PROTSYM files. Dynamic symbolic support is available\nto all Endevor  for Mainframe customers. This feature helps ensure that the correct symbolic is used for debugging,\ndiagnostics, or measurements. The SymDump  and InterTest products support the automatic updating of symbolic files\n(PROTSYM).\nDynamic Symbolic Support Activation\nWhen symbolic information is required for a program, the testing tools product looks for this information in the PROTSYM\nfiles specified for the program that is being debugged or reviewed.\n 1442", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f9c341750378-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIf one of the PROTSYM entries matches the compile date and time, that entry in the PROTSYM is used. If a matching\nentry is not found, and if dynamic symbolic support is activated, the system attempts to locate the Endevor  footprint and\nthe listing associated with the load module library, from where the load module was loaded.\nIf a match is found, the system automatically post-processes the Endevor  listing into a designated PROTSYM file so that\nthe correct symbolics are used without any interruption or program setup.\nDynamic symbolic support is activated based on individual product installation and option settings. However, the service\nthat dynamic symbolic support provides is centrally delivered through the symbolic common components. We recommend\nthat you install only one copy of the symbolic common components.\nDynamic Symbolic Support Execution\nDynamic symbolic support execution depends on whether your site has installed Endevor , and whether your installation\nuses a single Endevor  site ID or multiple Endevor  site IDs.\nSingle Site ID\nUsers with a single Endevor  site ID have the following options:\n\u2022Have one copy of C1DEFLTS.\n\u2022Run dynamic symbolic support in the address space of the Broadcom  testing tools product.\nNOTE\nTo implement dynamic symbolic support in a testing tools environment, see Interfaces and Compatibility.\nMultiple Site IDs\nUsers with multiple Endevor  site IDs have the following options:\n\u2022Have multiple C1DEFLTS.\n\u2022Allow dynamic symbolic support for multiple site IDs to be implemented using the Listing Server.\nNOTE\nIf you are using dynamic symbolic support in a CICS environment, the Listing Server methodology is always\nused regardless of the number of site IDs.\nListing Server\nWhen dynamic symbolic support service is requested, Listing Server is spawned as a started task (STC) through CAICCI.\nNOTE", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f9c341750378-1", "text": "NOTE\nData set CAI.CAVHPROC contains a sample PROC that can be used to start the Listing Server.\nDefine Unique PROC\nDefine a unique PROC in your PROCLIB for each Endevor  site ID in your environment.\nEach copy of the PROC must have the following PROCNAME:\nxxxxxxxy\n\u2022xxxxxxx  is the first seven characters of the PROCNAME defined in the testing tools product.\n\u2022y, the eighth character, is your Endevor  site ID.\nFor example, if the first seven characters of the PROCNAME are INTNDVR and the Endevor  site ID is 4, the\nPROCNAME defined in your PROCLIB is INTNDVR4.\n 1443", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b9b9d85e4467-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nThe first seven character names defined in your PROCLIB must match the PROCNAME defined to the\nBroadcom  testing tools product.\nPROCNAME is defined in the following elements by product:\n\u2022InterTest Batch is defined in IN25SITE\n\u2022SymDump  Batch is defined in CAOUXFDR\n\u2022InterTest for CICS is defined in IN25OPTS\n\u2022SymDump  for CICS is defined in IN25OPTS\n\u2022MAT is defined in the TUNUDEFS member of the option library\nPROC Customization\nThe sample PROC can be found in CAI.CAVHPROC. When modifying the PROC, consider the following\nrecommendations:\n\u2022Specify MSGLEVEL= (1,1) on the JOB statement so that a more comprehensive view of the events leading up to a\nproblem can be obtained. Set MSGCLASS to a class that does not get purged immediately after job termination. A\nsample JOB statement is shown next:\n //INTNDVR4 JOB (JOBACNT),MSGLEVEL=(1,1),MSGCLASS=X\n \n\u2022Remove the STEPLIB DD statement containing the CAI.CAVHLOAD data set name if the data sets that contain the\nsymbolic common components are defined in the LINKLIST. A sample STEPLIB DD statement is shown next:\n //STEPLIB DD DSN=CAI.CAVHLOAD,DISP=SHR                <== MODIFY\n \nNOTE\nThe load module data sets containing symbolic common components must be APF-authorized.\n\u2022The MODLRESP DD statement specifies the model space allocation (for Endevor  response files) to override\nthe default of (TRK, (5,5)). Depending on your requirement, you can override this limit to avoid SB37s. A sample\nMODLRESP DD statement is shown next:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b9b9d85e4467-1", "text": "MODLRESP DD statement is shown next:\n //MODLRESP DD DUMMY,SPACE=(CYL,(1,1))    MODEL FOR RESPONSE DATASET \n \n\u2022The MODLLIST DD statement specifies the model space allocation (for Endevor  listing files) to override the default\nof (TRK, (5,5). Depending on your requirement, you can override this limit to avoid SB37s. A sample MODLLIST DD\nstatement is shown next:\n //MODLLIST DD DUMMY,SPACE=(CYL,(5,5))    MODEL FOR LISTING DATASET    \n \n\u2022The SRVPRINT DD statement is used to log CAICCI activities. The presence of SRVPRINT triggers logging\ninformation across all dynamic symbolic support components, including Endevor  activities, system assigned DDnames\nand space allocated for all the work files. A sample SRVPRINT DD statement is shown next:\n //SRVPRINT DD SYSOUT=*    <== COMMENT OUT TO TURN OFF LOGGING\n \nNOTE\nWe strongly recommend that you do not comment out this DD statement because the information is critical\nfor Broadcom Support  to help you resolve any problems you encounter.\n\u2022The DSSLOG DD statement is used to log dynamic symbolic support-related diagnostic messages including Binder\nerrors and CAICCI feedback messages. A sample DSSLOG DD statement is shown next:\n //DSSLOG   DD SYSOUT=*    <== COMMENT OUT TO TURN OFF DSS LOGGING\n \n 1444", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b649ef84ce84-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nWe strongly recommend that you do not comment out this DD statement because the information is critical\nfor Broadcom Support  to help you resolve any problems you encounter.\n\u2022The JOBLOG DD statement is used to trigger message extraction when any subtask encounters critical errors or\nabends. The extracted messages, including PSW and the registers when the abend occurred, are reported back to the\nremote host. A sample JOBLOG DD statement is shown next:\n //JOBLOG   DD SYSOUT=*    <== REQUIRED FOR REPORTING REMOTE FAILURES\n \nNOTE\nWe strongly recommend that you do not comment out this DD statement because the information is critical\nfor Broadcom Support  to help you resolve any problems you encounter.\nIf the data sets containing the Endevor  C1DEFLTS, Endevor  CSIQLOAD (CONLIB), and CSIQAUTH (AUTHLIB) data sets\nare not defined in the LINKLIST, also define these data sets in the STEPLIB DD statement concatenation.\nNOTE\nCONLIB must be defined with a DDName of CONLIB. not part of the STEPLIB concatenation.\nJCL Considerations\nFor single C1DEFLTS environment, in addition to the DD statements required to run the Broadcom  testing tools product,\nyou must take the following actions:\n\u2022If the data sets containing the load module libraries of the symbolic common components are not defined in the\nLINKLIST, define them using the STEPLIB DD statement concatenation.\nNOTE\nThe load module data sets containing symbolic common components must be APF-authorized.\nIf the data sets containing the Endevor  C1DEFLTS, Endevor  CSIQLOAD (CONLIB), and CSIQAUTH (AUTHLIB) data", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b649ef84ce84-1", "text": "sets are not defined in the LINKLIST, also define these data sets in the STEPLIB DD statement concatenation.\nNOTE\nCONLIB must be defined with a DDName of CONLIB, not part of the STEPLIB concatenation.\n\u2022Set//SRVPRINT DD SYSOUT=* to trigger dynamic symbolic support related logging\n\u2022Set//DSSLOG DD SYSOUT=* to receive the messages extracted from the list server when you have a multiple user\nenvironment.\nNOTE\nThe DSSLOG DD statement is not required for a single C1DEFLTS environment.\nEndevor  Auto-Populate Activity Log\nThe following is a sample Auto Populate Activity Log that displays a list of activities with details such as date and time of\neach dynamic symbolic support event.\n *** IN25NDVR STARTED AT: 05182011.15021439.                                 \n ***      L O G   F I L E    DDNAME:SYS00045                                 \n *** ALLOCATING PROTSYM INPUTT FILE.                                         \n *** PROTSYM INPUTT FILE ALLOCATED. DDNAME: SYS00046 SPACE=(TRK,(50,50))     \n *** ALLOCATING PROTSYM OUTPUT FILE.                                         \n *** PROTSYM OUTPUT FILE ALLOCATED. DDNAME: SYS00047 SPACE=(TRK,(50,50))     \n *** ALLOCATING PROTSYM CARDS   FILE.                                        \n *** PROTSYM CARDS   FLE ALLOCATED. DDNAME: SYS00048 SPACE=(TRK,(01,01))     \n *** ALLOCATING PROTSYM MESSAGE FILE.                                        \n *** PROTSYM MESSAGE FLE ALLOCATED. DDNAME: SYS00049 SPACE=(TRK,(01,03))     \n 1445", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c874b3474e85-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n *** ALLOCATING PROTSYM   MSGS  FILE.                                        \n *** PROTSYM MSGS    FLE ALLOCATED. DDNAME: SYS00050 SPACE=(TRK,(01,03))     \n *** ALLOCATING PROTSYM REPORT FILE.                                         \n *** PROTSYM REPORT FILE ALLOCATED. DDNAME: SYS00051 SPACE=(TRK,(01,03))     \n *** ALLOCATING NDVR MESSAGE FILE. *    \n *** NDVR MESSAGE FILE ALLOCATED. DDNAME: SYS00052   SPACE=(TRK,(01,03))        \n *** ALLOCATING RESPONSE FILE    ***                                            \n *** NDVR RESPONSE FILE ALLOCATED.  DDNAME: SYS00053 SPACE=(TRK,(05,05))        \n *** ALLOCATING LISTING FILE.    ***                                            \n *** NDVR LISTING FILE USED AS INPUT TO PROTSYM POST PROCESSOR ALLOCATED. DDNAME: SYS00054 SPACE=(CYL,(05,05))\n ** FOOTPRINT:                                                                  \n    @TTOOLSQABASE    COBQAA05  COBCICS PRD     10104...15:35.0......&\\...\\{.    \n *** CALLING ENDEVOR API FOR AEPRE OPTION ***                                   \n *** BALRING TO ENA$NDVR ****                                                   \n *** ENDEVOR API STARTED AT:    15:02:14:57 NDVRELEM:COBQAA05   NDVRNAM2:COBQAA05\n *** ENDEVOR API ENDED   AT:    15:02:17:05                                     \n *** ENDEVOR AEPRE API FUNCTION RETURNED RC 0 ***                               \n *** ALLOCATING PROTSYM FILE. DSN:  AD1QA.SYMDUM85.GUI.NDVRSYM.NDV14", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c874b3474e85-1", "text": "*** PROTSYM FILE ALLOCATED.     DDNAME: SYS00066                               \n *** ADDING  COBQAA05 AS  COBQAA05 TO PROTSYM DSN: AD1QA.SYMDUM85.GUI.NDVRSYM.ND\n *** IN25CDRV RETURN CODE = 0    ***  \n *** CALLING NDVR TO TERMINATE API ***          \n *** ENA$NDVR API TERMINATED. ***               \n *** IN25NDVR ENDED AT: 05182011.15021770.\n \nRestrictions for PL/I\nFollow these restrictions when using symbolic support:\n\u2022Controlled Variables are not supported. For example:\nDCL A CTL;\nIn the DCL above, there would be no symbolic support and CORE='A' would not work.\n\u2022Use of redefine is not supported. For example:\nDCL A CHAR(10); \nDCL B DEF A;\nIn the example above, displaying B with CORE would not work.\n\u2022Adjusted variables are not supported. For example:\nPROC1 : PROC;\nDCL SIZE BIN FIXED(15,0) INIT(10); \nPROC2 : PROC; \nDCL ARRAY(SIZE) BIN(15,0); \nEND; \nEND;\nIn the example above, an array could not be displayed using CORE.\n\u2022Individual array entries are not supported. For example:\nCORE= 'A(5)'\n 1446", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "663ddf571101-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThis array entry will not work.\n\u2022Duplicate symbol names in the same PROC are not supported. For example:\nDCL A CHAR(5);\nDCL 1 Z,\n2 P BIN FIXED, \n2 A BIN FIXED;\nUsing the previous example, when CORE='A' is issued, unpredictable results occur. However, the same variable name\nin different PROCs is supported. For example:\nPROC1 : PROC;\nDCL A CHAR; \nPROC2 : PROC; \nDCL A BIN FIXED;\nIn the previous example, if CORE='A' were issued in 'PROC1', then the value of 'A' for 'PROC1' would be displayed. If\n'PROC2' had been executed to display the value of 'A' in 'PROC2', use the following command: CORE='PROC2:A'.\n\u2022Variables that use the PL/I ALLOC and FREE commands can be looked at with CORE only after the ALLOC executes\nand before the FREE executes. For example:\nDCL A BASED(P); ... cannot view \"A\".    \nALLOC A;    ... can use CORE to view \"A\".   \nFREE A; ... can no longer view \"A\". \n\u2022Variables declared in a block can't be viewed until the execution of that PROC's PROC/BEGIN statement. For\nexample:\nPROC2 : PROC;\nDCL Z CHAR; ... cannot view \"P\".    \n    ... can view \"Z\"..  \nPROC2 : PROC;\nDCL P CHAR;     ... can view \"P\".   \n    ... can view \"Z\"..  \n\u2022At least one automatic variable must be declared in a program for symbolics to function.\n\u2022Only one label can appear on a PROC statement. For example:\nLABEL1 : LABEL2 : PROC ;", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "663ddf571101-1", "text": "LABEL1 : LABEL2 : PROC ;\nThis is not supported.\nUse of the PL/I pre-processor options %NOPRINT, NUMBER, GONUM, and MARGINI is prohibited. If you must use\n%NOPRINT, call Broadcom Support .\nHow Postprocessors Store Symbolic Information\nWhen your application programs are compiled or assembled, symbolic information about the program is written to various\nreports in the output listing. A program called postprocessor reads the output listing, collects the symbolic information, and\nstores it in a symbolic repository called a PROTSYM.\nPROTSYM\nThe PROTSYM  is a VSAM RRDS defined by IDCAMS and initialized using the symbolic utility program IN25UTIL.\nFor more information about creating a PROTSYM file, see Creating a PROTSYM File.\n 1447", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d39bbd04a34b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPostprocessors\nSeveral postprocessors exist to extract symbolic information from the supported compilers and assemblers. Each\npostprocessor is discussed in detail in Adding Symbolic Information.\nPostprocessor Supported Compilers\nIN25SYMC OS/VS COBOL\nIN25COB2 Enterprise COBOL for z/OS and OS/390\nIBM COBOL for OS/390 and VM\nIBM COBOL for MVS and VM\nAD/CYCLE COBOL/370\nVS COBOL II\nIN25SYMP Enterprise PL/I for z/OS and OS/390\nIBM PL/I for MVS and VM\nIN25SYMA IBM High Level Assembler for MVS, VM, and VSE\nAssembler H\nAdditionally, a batch utility driver program, IN25SYMD, is provided to enable loading of more than one member from a\nlibrary in a single execution .\nFor more information about IN25SYMD, see Symbolic Support.\nExecute Postprocessors\nTo automatically invoke or execute the postprocessors in batch, use the sample JCL procedures provided in\nCAI.CAVHPROC or modify your COBOL, PL/I, or Assembler procedures. The method you select depends on the\nrequirements of your installation. Examples of each method are provided in the Adding Symbolic Information section.\nAlternatively, load your PROTSYM files online from the CAIPRINT Repository viewer using the SYM primary command in\nSymDump  Batch.\nFor more information about loading symbolic information from the viewer, see CAIPRINT Repository Viewer.\nIf you have installed and activated the dynamic symbolic support for Endevor  feature, the system automatically populates\nor postprocesses symbolic files if there are mismatches, and thus saves you program setup time.\nFor more information, see Dynamic Symbolic Support.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d39bbd04a34b-1", "text": "For more information, see Dynamic Symbolic Support.\nUsing the listing postprocessors to collect symbolic information does not change your program in any way. The listing\nproduced by your compiler or assembler is used only as input. Your object module is not changed. Only the PROTSYM is\nupdated.\nCOBOL OPTIMIZE Compiler Option\nTo increase program efficiency during execution, the OPTIMIZE  compiler option affects how the COBOL code is\nstructured after compilation. However, for debugging purposes, if the original source code is used as a base for the\nprogram flow and other operations, the OPTIMIZE  compiler option might affect the expected results.\nTo check the effects of the following options, enable the LIST  compiler option and check the outputs for the compilation\njob. Details of the debugging might also show how the program is executed for different optimization cases.\nOPTIMIZE Compiler Option Values\nThe following OPTIMIZE values might have different effects on generated code after compilation, which affects the\ncorresponding debug cases.\n 1448", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9a88a0b46e71-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nOPTIMIZE(0)\n(Default)\nAll COBOL statements generate code as usual in the order that they appear without compiler code suppression or\nreorganization for execution time optimization.\nOPTIMIZE(1)\nNot all COBOL statements generate code, and lines that are generated might not appear in the same order as in\nthe source code. The following reorganization might result:\n\u2022Some moving values (MOVE statements) might occur before the start of the monitored code.\n\u2022Some computations or calculations might occur before the start of the code.\n\u2022Branches do not strictly follow the code flow.\nNote:  This result is more pronounced with OPTIMIZE(2) . The INLINE option might change the order in which\nPERFORM statements appear in the code.\n\u2022Unreachable code, for example, statements after unconditional branches, is removed.\nOPTIMIZE(2)\nNot all COBOL statements generate code and the lines that are generated might not appear in the same order as\nin the source code.\nNote:  These effects are more pronounced than with OPTIMIZE(1) and, in addition to the points listed under\nOPTIMIZE(1), the following reorganization might result:\n\u2022More branches do not strictly follow the code flow and more code reorganization is possible. The INLINE\noption might change the order in which PERFORM statements appear in the code.\n\u2022More unreachable code is removed. If the value of a field can be determined at a decision point during\ncompilation, changing the value of this field during execution does not affect the flow, and alternative paths are\nremoved.\nTEST(EJPD) +OPTIMIZE(1) /OPTIMIZE(2)\nSuppresses optimization", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9a88a0b46e71-1", "text": "Suppresses optimization\nNote:  If TEST(EJPD)  is in use, compilation with OPTIMIZE(1)  or OPTIMIZE(2)  generates code in the same order\nas OPTIMIZE(0) . After compilation, you can confirm in the listing that this option has a different appearance from\nOPTIMIZE(0) .\nNOTE\nThe STGOPT  option is not related to code execution. When STGOPT  is on, storage is not allocated for unused\nfields, and fields before and after the removed fields are still properly mapped during a debugging session.\nOptimization Level and Debugging Suggestions\nGeneral Behavior\nWhen you debug an optimized program, consider the following behavior:\n\u2022Since the optimized program structure might differ from the source code, the statement execution order might differ,\nand some statements might be suppressed. Therefore, some breakpoints might occur out of order or not occur at all.\n\u2022Since SKIP , GO stmt# , or CS stmt#  commands have the original source as a reference, changes to the program flow\nmight generate unexpected results and abends.\n\u2022Optimization might also affect other functionalities such as an ABEND statement indication being in an unexpected\nposition.\nDevelopment\nFor development, OPTIMIZE(0)  or intended production OPTIMIZE level + TEST(EJPD)  provides the following benefits:\n\u2022A higher level of flow control\n\u2022A higher level of control of field values\n\u2022A better understanding of the source code intentions\n 1449", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3a078fb6f13b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDiagnosis\nFor further diagnosis of production problems in a program that uses optimization, debugging with as much optimization\nmight provide more information about what occurred, including the following examples:\n\u2022When a specific field changes\n\u2022The paths followed\n\u2022The order of statement execution\nNOTE\nDepending on the level of changes that occurred during optimization, debugging the program with no\noptimization might be preferable.\nPre-production testing\nFor pre-production level testing or execution where you want to have the same behavior as in production, we recommend\nthat you use the same OPTIMIZE level and review the new flow after compilation to check how the program will run.\nFor more information, see the following Programming Guide  sections in the Enterprise COBOL for z/OS documentation\nlibrary  of the IBM Knowledge Center  at ibm.com:\nCompiler options\n(Under Compiling and debugging your program )\nTuning your program\n(Under Improving performance and productivity )\nDebugger for Mainframe Extension for VS Code\nThe Debugger for Mainframe extension provides a modern debugging experience for CICS and Batch programs written in\nCOBOL, and is currently available as a Visual Studio Code extension, or as part of the Code4z package for Visual Studio\nCode.\nInterTest users are entitled to support for this VS Code extension.\nThe extension requires incremental release 11.0.07 or higher of InterTest for CICS or InterTest Batch, as well as the\nTesting Tools Server.\nYou can install Debugger for Mainframe  or Code4z  on Visual Studio Code from the Visual Studio Code marketplace.\nFor user documentation and release information, see the Debugger for Mainframe Git repository .\nHow can we improve Debugger for Mainframe? Let us know\nAbend Analyzer for Mainframe Extension for Visual Studio Code", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3a078fb6f13b-1", "text": "Abend Analyzer for Mainframe Extension for Visual Studio Code\nView Abend reports in a modern IDE interface with the Abend Analyzer for Mainframe extension.\nAbend Analyzer for Mainframe is an IDE extension for SymDump with which you can view and manage SymDump\nAbend reports and symbolic data in a modern IDE interface. Abend Analyzer for Mainframe is available as a Visual Studio\nCode extension. With this extension, you can perform the following actions on SymDump Abend reports:\n\u2022View reports\n\u2022Filter and sort reports\n\u2022Lock and unlock reports\n\u2022Delete reports\n\u2022Load symbolic data from a PROTSYM\nSymDump users are entitled to support for this Visual Studio code extension.\n 1450", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2277b34c9d67-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe extension requires the Testing Tools Server, SymDump REST API, and incremental PTF LU02175 to run.\nTo install and view the user documentation for this extension, refer to the Visual Studio Code Marketplace .\nAbend Analyzer for Mainframe is also part of Code4z , an all-round package that offers a modern experience for\nmainframe application developers, including extensions for language support, data editing, testing, and source code\nmanagement.\n 1451", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8a715b8b8950-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nMessages and Codes\nThis section contains the messages and abend codes for InterTest and SymDump.\nExplanations for the occurrence of each message and the action to be taken are also covered.\nInterTest for CICS Messages\nThe following InterTest for CICS messages are explained:\nSYM messages\nLists informational and error messages produced by the InterTest for CICS Symbolic Post-processor programs\nIN25COB2, IN25SYMA, and IN25SYMC.\nSYMP messages\nLists informational and error messages produced by the InterTest for CICS Symbolic Post-processor program\nIN25SYMP.\nUTIL messages\nLists informational and error messages produced by the IN25UTIL program.\nPWR messages\nLists informational and error messages produced by the InterTest for CICS VSE/POWER facility.\nSymDump  for CICS Messages\nThe following SymDump  for CICS messages are explained:\n\u2022IN25COLD messages\n\u2022IN25EXTI messages\n\u2022IN25INIT messages\n\u2022IN25PDMP messages\nInterTest Batch Messages\nThe following InterTest Batch messages are explained:\n\u2022ABA messages\n\u2022CAMRA messages\n\u2022CAMR messages\n\u2022CAMRS messages\n\u2022INTA messages\n\u2022INTB messages\n\u2022INTG messages\n\u2022XDAIR messages\nSymDump  Batch Messages\nThe following SymDump  Batch messages are explained:\n 1452", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f1bb53b8acb9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022CAPC messages\n\u2022CAPD messages\n\u2022CAPE messages\n\u2022CAPH messages\n\u2022CAPI messages\n\u2022CAPR messages\n\u2022CAPU messages\nSymDump  REST API Messages\nThe following SymDump  Batch and CICS REST API messages are explained:\n\u2022CAVHR messages\nIN25SYMP Abend Codes\nCode Explanation\n0 Program execution has completed normally.\n4 Program execution has completed normally. However, warning\nmessages were issued. See the MSGS DD/DLBL for more\ndetailed information.\n16 or 1016 Program execution has completed abnormally. See the MSGS\nDD/DLBL for more information.\n1020 The MSGS DD/DLBL is not coded properly in the JCL. Check your\nJCL and resubmit the job.\n1024 An error has occurred in the routine responsible for writing error\nmessages. This caused an abnormal termination of IN25SYMP.\nCheck the job log for information from the operating system or PL/\nI concerning the error condition.\nInterTest for CICS Error Codes\nInterTest for CICS issues the following error codes when error conditions are discovered:\nCORE\nIs the same as the transaction code of the CORE transaction at your site. It means that the CORE transaction intercepted\na CICS abend that makes it impossible to continue the transaction.\nINHA\nIndicates that a program (usually a user program) has corrupted an InterTest for CICS storage area so that InterTest for\nCICS cannot continue processing. Check the CICS statistics to see if any storage violations occurred. If you find any, see\nwhich program caused the violation. This would be a program not being monitored by InterTest for CICS.\nINTE\nIndicates that an automatic breakpoint cannot be executed because:\n\u2022The InterTest for CICS automatic breakpoint facility is disabled.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f1bb53b8acb9-1", "text": "\u2022The InterTest for CICS automatic breakpoint facility is disabled.\n\u2022There is no terminal on which to show the breakpoint display.\n\u2022The terminal designated to receive the breakpoint display is not a 3270type CRT (or compatible model).\nINTP\nIndicates that a PLI LE program was linked without CEESTART as its first CSECT and InterTest abends the task with an\nINTP abend code.\nKERN\n 1453", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2f596611d47a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIndicates that the task at a breakpoint could not recover from an abend. If you know the reason (for example, you\nabended the task), ignore this code; otherwise, contact InterTest for CICS technical support.\nNATI\nIndicates that a breakpoint display is being directed to a terminal that does not have the Automatic Task Initiation (ATI)\ncapability. If the status of the terminal is either transceive  or receive  (preferably, transceive), the terminal has the ATI\ncapability. You can adjust the status by the CEMT service transaction.\nSymDump  for CICS Error Codes\nSymDump  for CICS uses the following error code when it discovers error conditions:\nEXT2\nThis abend occurs during the SymDump  for CICS transaction dump capture process. A failure occurred during the final\nphase of dump capture, when the Last SQL Statement information was being obtained for capture to the PROTDMP file.\nThe EXT2 abend is produced by a background task that runs after the application task has abended and been intercepted\nby SymDump  for CICS.\nWhen this abend code occurs, perform the following steps:\n1.Examine the CICS message log carefully for error messages that may explain the problem. There may be diagnostic\nmessages for you to review.\n2.The EXT2 abend should have produced a transaction and, possibly, a system dump. Collect these items with the\nJESLOG and contact Broadcom Support  for a resolution.\n3.The transaction dump that was captured by SymDump  for CICS for the application abend is complete with the\nexception of the LASTSQL information.\nEndevor  Interface Codes\nMessage CAIN2912 Program NOT FOUND in any of the InterTest for CICS Symbolic Files  may be followed by an", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2f596611d47a-1", "text": "informational message providing information regarding the Endevor  status.\nA message similar to this may appear:\nDynamic PROTSYM load failed, RC = < NDVR > , REASON = < SITE >\nThe following table defines the RC = and Reason = values.\nRC = < NDVR > Reason = < SITE > Message\nINQY SYMF Inquiry on the NDVRSYM file failed.\nLOAD MODL Load of program IN25NIDR failed.\nNDVR SITE Extract of the Endevor  SITE_ID failed.\nCCI_ INIT The CCI_INIT function failed.\nCCI_ INQY The CCI_INQY function failed.\nCCI_ SPWN The CCI_SPWN function failed.\nCCI_ CONV The CCI_CONV function failed.\n2 NIDR Getmain failed in program IN25NIDR\n32 NIDR Load of program IN25NDSB failed in\nprogram IN25NIDR.\n48 NIDR Csect mismatch in IN25NIDR.\n4 NDSB Endevor  Footprint is invalid, program\nin25NDSB.\nnn CSVQ nn = Retrun code from CSVQUERY.\n 1454", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7f4c52ba1a3a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nnn nnnn Numeric return code and reason codes are\nEndevor  codes.\nnn CDRV nn = Return code from the post processor,\nIN25COB2, IN25SYMA, and so on.\nInterTest for CICS Messages\nMost of the InterTest for CICS messages are in online Help. Messages that are not accessible from online Help are listed\nin this section. \nCAIN3478\nAccess is restricted for this selection\nReason:\nThe option requested is restricted from use.\nAction:\nEither do not use this option, or obtain security access to the option from your systems programmer.\nCAIN5340\nMM/DD/YYYY HH:MM:SS \u2013 XXXXXXXX\nReason:\nInterTest for CICS and SymDump  for CICS both use CCI SERVICES to enable communication between different regions\nwithin your CCI NETWORK. A CCI call has completed with a non-zero return code. The diagnostic messages are\nproduced to the CICS MSGUSR queue and/or the TRACE FORMAT REGION SYSPRINT file. XXXXXXXX is followed\nby internal information that describes that nature of the return code. In the event of a TRACE FORMAT timeout having\noccurred in the TRACE FORMAT REGION, these messages are informational only and do not indicate a problem.\nAction:\nThese messages may occur normally during use of the InterTest for CICS and SymDump  for CICS products, in which\ncase no action is required. The information is purely informational. If you suspect that there is a product malfunction,\nthen record the messages along with the time/date of the occurrence, and then contact your systems programmer for\nresolution. They may need to contact Broadcom Support  with the appropriate documentation.\nCAIN5900\nMM/DD/YYYY HH:MM:SS TASK STARTED\nReason:\nThe Region has started.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7f4c52ba1a3a-1", "text": "MM/DD/YYYY HH:MM:SS TASK STARTED\nReason:\nThe Region has started.\nAction:\nNone. This is an informational message indicating the task has started.\nCAIN5901\nMM/DD/YYYY HH:MM:SS IN25TRCM LOAD OF IN25OPTS HAS FAILED\nReason:\nThe SymDump  for CICS Trace Format Region cannot load the IN25OPTS module from the STEPLIB concatenation.\nProcessing terminates.\nAction:\n 1455", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "244a018b0093-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDetermine why the module is not available.\nCAIN5902\nMM/DD/YYYY HH:MM:SS IN25TRCM IN25OPTS HAS NO TRCFFMID\nReason:\nThe SymDump  for CICS Trace Format Region cannot use the IN25OPTS module from the STEPLIB concatenation.\nProcessing terminates.\nAction:\nReview your IN25OPTS module definition.\nCAIN5903\nMM/DD/YYYY HH:MM:SS TASK CCI INIT FAILED\nReason:\nWhile processing a request, the task uses CCI SERVICES to enable communication between CICS and the task within\nyour CCI NETWORK. A CCI initialization call has failed. A dump may be taken and there are diagnostic messages\nproduced to the CICS MSGUSR queue and/or the task log file.\nAction:\nReview the messages produced by the task. The most common problem that causes this situation is that CCI was not\nproperly initialized. Locate the Joblog for ENF and look for messages indicating the status of the CCI subsystem. There\nmust be a CAS9626I - CAICCI Subsystem is operational message. If this is not there, contact CCI technical support for\nassistance.\nRecord this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They\nmay need to contact Broadcom Support  with the appropriate documentation.\nCAIN5904\nMM/DD/YYYY HH:MM:SS TASK WAITING FOR WORK\nReason:\nAfter the task initializes, it becomes idle and waits for new work.\nAction:\nNone. This is an informational message indicating the task is waiting for more work.\nCAIN5905\nMM/DD/YYYY HH:MM:SS TASK RECVANY FAILED\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "244a018b0093-1", "text": "MM/DD/YYYY HH:MM:SS TASK RECVANY FAILED\nReason:\nWhile processing a request, the task uses CCI SERVICES to enable communication between CICS and the task within\nyour CCI NETWORK. A CCI receive any call has failed. A dump may be taken and there are diagnostic messages\nproduced to the CICS MSGUSR queue and/or the task log file.\nAction:\nRecord this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They\nmay need to contact Broadcom Support  with the appropriate documentation.\nCAIN5906\nMM/DD/YYYY HH:MM:SS IN25TRCM REQUEST FOR WORK RECEIVED FOR NNNNNNNN TRACE BLOCKS FROM\nCCID:\nReason:\nThe Trace Format Region parent task program IN25TRCM has received a request to format a trace that contains the\nspecified number of trace blocks. The CCI id number is also listed.\n 1456", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "15260f78ce25-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nNone. This is an informational message indicating that the Trace Format Region received a format request.\nCAIN5907\nMM/DD/YYYY HH:MM:SS TASK SENDSPEC FAILED\nReason:\nWhile processing a request, the task uses CCI SERVICES to enable communication between CICS and the task within\nyour CCI NETWORK. A CCI send specific call has failed. A dump may be taken and there are diagnostic messages\nproduced to the CICS MSGUSR queue and/or the task log file.\nAction:\nRecord this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They\nmay need to contact Broadcom Support  with the appropriate documentation.\nCAIN5908\nMM/DD/YYYY HH:MM:SS TASK GETMAIN FAILED\nReason:\nWhile processing a request, the task has encountered an internal error while trying to get main storage.\nAction:\nReview your message log for any obvious problems. You may need to increase your region size. Record this message\nnumber, and the time/date of the occurrence. Contact your systems programmer for resolution. They may need to contact\nBroadcom Support  with the appropriate documentation.\nCAIN5909\nMM/DD/YYYY HH:MM:SS IN25NSRV REQUEST RECEIVED FOR program-id :\nReason:\nThe task has received a request to extract the program, program-id , from Endevor .\nAction:\nNone. This is an informational message indicating that the Endevor  interface server has received a request.\nCAIN5910\nMM/DD/YYYY HH:MM:SS REQUEST REJECTED DUE TO MAX THREAD STORAGE REACHED (TRCFMEGT)\nReason:\nFormatting your CICS trace entries requires a considerable amount of virtual storage. To ensure that resource limits", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "15260f78ce25-1", "text": "Formatting your CICS trace entries requires a considerable amount of virtual storage. To ensure that resource limits\nare not exceeded, a maximum thread storage limit is specified in the IN25OPTS table used by the TRACE FORMAT\nREGION. In this case the maximum thread storage limit has been exceeded by the selected trace.\nAction:\nContact your Systems Programmer for resolution, by reviewing and possibly increasing the IN25OPTS TRCFMEGT value\nspecified.\nCAIN5911\nMM/DD/YYYY HH:MM:SS REQUEST REJECTED DUE TO MAX TOTAL STORAGE REACHED (TRCFMEGM)\nReason:\nFormatting your CICS trace entries requires a considerable amount of virtual storage. To ensure that resource limits are\nnot exceeded, a maximum total storage limit is specified in the IN25OPTS table used by the TRACE FORMAT REGION.\nIn this case the maximum total storage limit for all concurrent threads has been exceeded.\nAction:\n 1457", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2c1f149a38d5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThis may occur normally due to system loads. If the problem persists, Contact your Systems Programmer for resolution,\nby reviewing and possibly increasing the IN25OPTS TRCFMEGM value specified.\nCAIN5912\nMM/DD/YYYY HH:MM:SS REQUEST REJECTED DUE TO MAX THREADS REACHED (TRCFTHRD)\nReason:\nFormatting your CICS trace entries requires a considerable amount of virtual storage. To ensure that resource limits\nare not exceeded, a maximum total number of format threads is specified in the IN25OPTS table used by the TRACE\nFORMAT REGION. In this case the maximum total number of concurrent threads has been exceeded.\nAction:\nThis may occur normally due to system loads. If the problem persists, Contact your Systems Programmer for resolution,\nby reviewing and possibly increasing the IN25OPTS TRCFTHRD value specified.\nCAIN5913\nMM/DD/YYYY HH:MM:SS IN25NSRV SENDING RESPONSE\nReason:\nThe task has received a response from its sub-task and is sending the response back to the requesting CICS region.\nAction:\nNone. This is an information message only.\nCAIN5914\nMM/DD/YYYY HH:MM:SS IN25TRCM LOCAL STORAGE STARTS AT: NNNNNNNN\nReason:\nThis is an informational message used by Broadcom Support  for diagnostic purposes.\nAction:\nNone. This is an informational message.\nCAIN5915\nMM/DD/YYYY HH:MM:SS IN25OPTS TIMEOUT VALUE FOR THREAD: NNNN SECONDS (TRCFTOUT)\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS uses CCI SERVICES to enable communication between\nCICS and the TRACE FORMAT REGION within your CCI NETWORK. To ensure that finite resources are not wasted", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2c1f149a38d5-1", "text": "when the terminal is unattended, or during a system slowdown, a timeout limit is specified in the IN25OPTS for your\nTRACE FORMAT REGION (TRCFTOUT). This message simply tells you what the timeout value is set to.\nAction:\nNone. This is an informational message.\nCAIN5916\nMM/DD/YYYY HH:MM:SS IN25OPTS MAXIMUM NUMBER OF THREADS: NNNN (TRCFTHRD)\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS uses CCI SERVICES to enable communication between\nCICS and the TRACE FORMAT REGION within your CCI NETWORK. Trace formatting also requires a considerable\namount of virtual storage. To ensure that resource limits are not exceeded, a thread limit is specified in the IN25OPTS for\nyour TRACE FORMAT REGION (TRCFTHRD). This message simply tells you what the value is set to.\nAction:\nNone. This is an informational message.\n 1458", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a322049e9437-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN5917\nMM/DD/YYYY HH:MM:SS IN25OPTS MAX STORAGE PER THREAD: NNNN MEGS (TRCFMEGT)\nReason:\nFormatting your CICS trace entries requires a considerable amount of virtual storage. To ensure that resource limits are\nnot exceeded, a maximum thread storage limit is specified in the IN25OPTS table used by the TRACE FORMAT REGION\n(TRCFMEGT). This message simply tells you what the value is set to.\nAction:\nNone. This is an informational message.\nCAIN5918\nMM/DD/YYYY HH:MM:SS IN25OPTS MAX TOTAL STORAGE REQUEST: NNNN MEGS (TRCFMEGM)\nReason:\nFormatting your CICS trace entries requires a considerable amount of virtual storage. To ensure that resource limits\nare not exceeded, a maximum total storage limit for all threads is specified in the IN25OPTS table used by the TRACE\nFORMAT REGION (TRCFMEGM). This message tells you what the value is set to.\nAction:\nNone. This is an informational message.\nCAIN5919\nMM/DD/YYYY HH:MM:SS AVAILABLE EXTENDED PRIVATE: NNNN MEGS\nReason:\nAn informational message telling you what the available extended private storage area is for the TRACE FORMAT\nREGION. This value must be equal to or greater that the value specified in TRCFMEGM or the job will terminate.\nAction:\nNone. This is an informational message.\nCAIN5920\nMM/DD/YYYY HH:MM:SS INSUFFICIENT EXTENDED PRIVATE AREA TO START FORMAT TASK\nReason:\nThe available Extended Private area must be equal to or greater that the value specified in TRCFMEGM or the job will\nterminate.\nAction:\nNone. This is an informational message.\nCAIN5930", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a322049e9437-1", "text": "terminate.\nAction:\nNone. This is an informational message.\nCAIN5930\nMM/DD/YYYY HH:MM:SS TASK CCI FEEDBACK:\nReason:\nThis is an informational message used by Broadcom Support  for diagnostic purposes.\nAction:\nRecord this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They\nmay need to contact Broadcom Support  with the appropriate documentation. There are other messages that accompany\nthis message.\nCAIN5950\nMM/DD/YYYY HH:MM:SS TASK SHUTDOWN\nReason:\n 1459", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1f0078514170-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe task has shut down.\nAction:\nNone. This is an informational message.\nCAIN5951\nREPLY 'SHUTDOWN' TO TERMINATE TRACE FORMAT\nReason:\nThis is an outstanding write to operator with reply. When the mvs console operator responds with the SHUTDOWN reply,\nthe trace format region ends gracefully.\nAction:\nReply to this console message when the trace format region is to be shut down.\nCAIN5952\nM/DD/YYYY HH:MM:SS SUBXXXXX GETMAIN FAILURE\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS has encountered an internal error while trying to get main\nstorage.\nAction:\nReview your message log for any obvious problems. You may need to increase your region size. Record this message\nnumber, and the time/date of the occurrence. Contact your systems programmer for resolution. They may need to contact\nBroadcom Support  with the appropriate documentation.\nCAIN5953\nMM/DD/YYYY HH:MM:SS SHUTDOWN OF TRACE FORMAT REGION IN PROCESS\nReason:\nAfter replying SHUTDOWN to wtor message CAIN5951, this message indicates that the SymDump  for CICS Trace\nFormat Region is in the process of shutting down.\nAction:\nNone, this is an informational message only.\nCAIN5980\nMM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX STARTED, NNNNNNNN TRACE BLOCKS TO BE PROCESSED.\nReason:\nThe SymDump  for CICS Trace Format Region has established a CCI communications session with a CICS task.\nSUBXXXX uniquely identifies the subtask that is being started to format a CICS trace, the number corresponds to the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1f0078514170-1", "text": "CICS task number in the CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the\nformat request. The number of trace blocks being sent is also listed.\nAction:\nNone. This is an informational message indicating that the Trace Format Region started a format subtask.\nCAIN5981\nMM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX CCI INIT FAILURE\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS uses CCI SERVICES to enable communication between\nCICS and the TRACE FORMAT REGION within your CCI NETWORK. A CCI initialization call has failed. SUBXXXX\nuniquely identifies the subtask that has been started to format a CICS trace, the number corresponds to the CICS task\nnumber in the CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the format request.\n 1460", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "09d3c9e1a706-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nA dump may be taken and there are diagnostic messages produced to the CICS MSGUSR queue and/or the TRACE\nFORMAT REGION SYSPRINT file.\nAction:\nRecord this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They\nmay need to contact Broadcom Support  with the appropriate documentation.\nCAIN5982\nMM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX CCI CONVERSE FAILURE\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS uses CCI SERVICES to enable communication between\nCICS and the TRACE FORMAT REGION within your CCI NETWORK. A CCI converse call has failed. SUBXXXX uniquely\nidentifies the subtask that is being started to format a CICS trace, the number corresponds to the CICS task number in\nthe CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the format request. A dump\nmay be taken and there are diagnostic messages produced to the CICS MSGUSR queue and/or the TRACE FORMAT\nREGION SYSPRINT file.\nAction:\nRecord this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They\nmay need to contact Broadcom Support  with the appropriate documentation.\nCAIN5984\nMM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX API CCI CALL FAILURE FOR PROGRAM: IN25TRCF\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS uses CCI SERVICES to enable communication between\nCICS and the TRACE FORMAT REGION within your CCI NETWORK. A CCI call issued by IN25TRCF has failed.\nSUBXXXX uniquely identifies the subtask that has been started to format a CICS trace, the number corresponds to the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "09d3c9e1a706-1", "text": "CICS task number in the CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the\nformat request. A dump may be taken and there are diagnostic messages produced to the CICS MSGUSR queue and/or\nthe TRACE FORMAT REGION SYSPRINT file.\nAction:\nRecord this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They\nmay need to contact Broadcom Support  with the appropriate documentation.\nCAIN5990\nMM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX FDBVDESC:\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS uses CCI SERVICES to enable communication between\nCICS and the TRACE FORMAT REGION within your CCI NETWORK. A CCI call has received a non zero return code.\nSUBXXXX uniquely identifies the subtask that has been started to format a CICS trace, the number corresponds to the\nCICS task number in the CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the\nformat request. FDBVDESC will be followed by diagnostic information that must be provided to Broadcom Support , in the\nevent of a product malfunction. A dump may have been taken and there may be additional diagnostic messages produced\nto the CICS MSGUSR queue and/or the TRACE FORMAT REGION SYSPRINT file.\nAction:\nIn the event of a RECEIVE TIMEOUT in the TRACE FORMAT REGION, this message is purely informational and no\naction is required, although you may want to review your IN25OPTS definitions to increase your format timeout threshold\n(TRCFTOUT). If you suspect a product malfunction, then record this message number, the time/date of the occurrence,\nand then contact your systems programmer for resolution. They may need to contact Broadcom Support  with the\nappropriate documentation.\n 1461", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7d48e9dc7dba-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN5992\nMM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX FREEMAIN OF LIST HAS FAILED\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS has encountered an internal error while trying to freemain\nstorage previously acquired. SUBXXXX uniquely identifies the subtask that has been started to format a CICS trace, the\nnumber corresponds to the CICS task number in the CICS job that is sending the format request. CICSXXXX is the CICS\njob that is sending the format request.\nAction:\nRecord this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They\nmay need to contact Broadcom Support  with the appropriate documentation.\nCAIN5993\nMM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX GETMAIN FAILURE\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS has encountered an internal error while trying to getmain\nstorage. SUBXXXX uniquely identifies the subtask that has been started to format a CICS trace, the number corresponds\nto the CICS task number in the CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the\nformat request.\nAction:\nRecord this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They\nmay need to contact Broadcom Support  with the appropriate documentation.\nCAIN5994\nMM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX API CALL FAILURE:\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS has encountered an internal error. SUBXXXX uniquely\nidentifies the subtask that has been started to format a CICS trace, the number corresponds to the CICS task number in", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7d48e9dc7dba-1", "text": "the CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the format request. API CALL\nFAILURE is followed by diagnostic information that must be provided to Broadcom Support .\nAction:\nRecord this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They\nmay need to contact Broadcom Support  with the appropriate documentation.\nCAIN5995\nMM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX UNABLE TO DISPATCH IN25TRCM\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS has encountered an internal error. SUBXXXX uniquely\nidentifies the subtask that has been started to format a CICS trace, the number corresponds to the CICS task number in\nthe CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the format request.\nAction:\nRecord this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They\nmay need to contact Broadcom Support  with the appropriate documentation.\nCAIN5996\nMM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX CONVERSE ILLOGIC\nReason:\n 1462", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "959894fd7b4c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWhile formatting your CICS trace entries SymDump  for CICS has encountered an internal error. SUBXXXX uniquely\nidentifies the subtask that has been started to format a CICS trace, the number corresponds to the CICS task number in\nthe CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the format request.\nAction:\nRecord this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They\nmay need to contact Broadcom Support  with the appropriate documentation.\nCAIN5997\nMM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS has encountered an internal error. SUBXXXX uniquely\nidentifies the subtask that has been started to format a CICS trace, the number corresponds to the CICS task number in\nthe CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the format request.\nAction:\nRecord this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They\nmay need to contact Broadcom Support  with the appropriate documentation.\nCAIN5999\nMM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX FINISHED\nReason:\nThe SymDump  for CICS Trace Format Region has completed a CCI communications session with a CICS task.\nSUBXXXX uniquely identifies the subtask that is being started to format a CICS trace, the number corresponds to the\nCICS task number in the CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the\nformat request.\nAction:\nNone. This is an informational message indicating that the Trace Format Region completed a format request.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "959894fd7b4c-1", "text": "None. This is an informational message indicating that the Trace Format Region completed a format request.\nSymDump  for CICS Online Messages\nCASD3469\nAPI FAILURE OCCURRED DURING CAPTURE\nReason:\nDuring dump capture, program IN25STRU attempted to gather information for the abending task, but failed.\nAction:\nVerify that the security definitions for the abending task allow InterTest for CICS to perform the CICS inquiry commands\nnecessary to complete dump capture. Carefully review the security violation logs and correct the problem. If necessary,\ncontact your systems programmer.\nCASD3470\nCAPTURE FAILURE DUE TO NOTAUTH CONDITION\nReason:\nDuring dump capture, program IN25STRU attempted to gather information for the abending task, but failed due to a\nNOTAUTH condition.\nAction:\nVerify that the security definitions for the abending task allow SymDump  to perform the CICS inquiry commands\nnecessary to complete dump capture. Carefully review the security violation logs and correct the problem. If necessary,\ncontact your systems programmer.\n 1463", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0a13491b8879-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6048\nSYMDUMP is suppressing the CICS dump\nReason:\nSince SymDump  for CICS has captured the dump, it is suppressing the CICS transaction dump.\nAction:\nNone.\nCASD6049\nSYMDUMP R.0000 COLD ASM MM/DD/YYYY HH.MM\nReason:\nThis is an informational message always displayed when SymDump  for CICS is started, showing the release of the\nproduct, and the assembly date and time for IN25COLD, the primary dump capture module.\nAction:\nNone.\nCASD6050\nCICS WILL CAPTURE THIS DUMP\nReason:\nDue to the options set in the SymDump  for CICS PROTDMP file, SymDump  for CICS is not suppressing the CICS dump.\nCICS will capture the dump as it would have normally.\nAction:\nNone.\nCASD6069\nSYMDUMP INTERCEPT OF DUMP REQUEST FOR TRANSACTION NNNN: ABEND(NNNN),TASK(XXXXX),\nTERMINAL ID(XXXX)\nReason:\nInformational message denoting that SymDump  for CICS has intercepted a transaction dump, with the attributes shown.\nAction:\nNone.\nCASD6070\nSYMDUMP ANCHOR GETMAIN FAILURE ENCOUNTERED\nReason:\nA catastrophic internal system failure has occurred.\nAction:\nContact Broadcom Support .\nCASD6071\nA SYSTEM OR STORAGE DUMP HAS BEEN REQUESTED BY TRANSACTION NNNN DUMP CODE IS XXXXXXXX\nReason:\nInformational message indicating that SymDump  for CICS has intercepted a System or Storage dump with the code\nshown.\nAction:\nNone.\n 1464", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3063316162e2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6072\nSYMDUMP WILL NOT CAPTURE THIS DUMP\nReason:\nInformational message indicating that SymDump  for CICS will not capture the intercepted dump. There are other\nmessages indicating why this action has been taken.\nAction:\nNone.\nCASD6073\nSYMDUMP HAS CAPTURED THIS DUMP\nReason:\nInformational message indicating that SymDump  for CICS will capture the intercepted dump.\nAction:\nNone.\nCASD6074\nSYMDUMP EXCLUSION SPECIFIED FOR THIS ABEND\nReason:\nInformational message indicating that SymDump  for CICS will not capture the intercepted dump, due to exclusion\nspecified in the PROTDMP file. This is controlled through the SymDump  for CICS Configuration screen (SYMI).\nAction:\nNone.\nCASD6077\nSYMDUMP LSTACK GETMAIN FAILURE ENCOUNTERED\nReason:\nA catastrophic internal system failure has occurred.\nAction:\nContact Broadcom Support .\nCASD6078\nSYMDUMP TRACE GETMAIN FAILURE ENCOUNTERED\nReason:\nA catastrophic internal system failure has occurred.\nAction:\nContact Broadcom Support .\nCASD6079\nSYMDUMP STACK GETMAIN FAILURE ENCOUNTERED\nReason:\nA catastrophic internal system failure has occurred.\nAction:\nContact Broadcom Support .\n 1465", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fa0bf857bb8a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6080\nDUPLICATE DUMP SUPPRESSION IN EFFECT\nReason:\nInformational message indicating that duplicate dump suppression is active, and that the dump is being suppressed for\nthat reason.\nAction:\nNone.\nCASD6081\nSTIMERM FAILURE, CANNOT CAPTURE DUMP\nReason:\nA catastrophic internal system failure has occurred.\nAction:\nContact Broadcom Support .\nCASD6082\nPROTDMP index exceeded, probable application program loop. Dump not captured.\nReason:\nThe number of index entries on the PROTDMP file has been exceeded. This is most likely due to a loop in the application\nprogram. SymDump  for CICS was unable to capture the dump.\nAction:\nCorrect the application program loop.\nCASD6083\nSYMDUMP subtask has exceeded cputime limit: possible loop at offset +00000.\nReason:\nThe CPU timer has been exceeded. Either this is a very large dump and it is truly taking this long for SymDump  for CICS\nto capture it, or the subtask is looping.\nAction:\nContact your systems programmer to determine if the subtask is looping or if the CPU timer needs to be increased.\nCASD6084\nSYMDUMP subtask has abended at offset +00000.\nReason:\nDuring the dump capture process, the SymDump capture has abended at the given offset. SymDump  has recovered\nfrom this abend but did not capture the dump. SymDump  for CICS must take a normal transaction dump for the original\napplication abend in this case.\nAction:\nFor assistance, contact Broadcom Support .\nCASD6085\nSYMDUMP DOES NOT SUPPORT \"C\" LANGUAGE CAPTURE.\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fa0bf857bb8a-1", "text": "SYMDUMP DOES NOT SUPPORT \"C\" LANGUAGE CAPTURE.\nReason:\nSymDump  for CICS does not support capture or redisplay of transaction dumps for C language programs.\nAction:\n 1466", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8ab65cb7aa68-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSymDump  for CICS will not suppress the CICS transaction dump for a C program dump request. Format and review the\nCICS transaction dump to determine its cause.\nCASD6086\nDump is abbreviated.\nReason:\nSymDump  for CICS was unable to capture a complete dump of the abending/ dumping task for one of the following\nreasons:\n\u2022\n\u2022SymDump  for CICS is improperly installed\n\u2022\n\u2022DFHPEP did not execute at termination of the abending task\n\u2022\n\u2022The task abended recursively\n\u2022\n\u2022The task is not eligible for a complete dump capture. This occurs for the following abend codes: ACRI, AELA, AELB,\nAEMP, AETA, AEXY, AEXZ, AFCY, AICH, AISX, AISX, AJCE, AJCG, AKC3, AMSC, APTA, ASCP, ASPA, ASP5,\nATCH, ATCI, ATC7, ATCV, ATD3, ATMA, ATND, ATNI, ATPE, ATRA, AXF0, AXF4, AXSC, AZCN, AZIB, AZID, AZIE,\nAZI6, AZI7, AZI9, AZR3, AZVA, AZCT\n\u2022\n\u2022The abend was produced by the CSNE transaction.\n\u2022\nAction:\nThe dump is intact and can be viewed using SymDump  for CICS. It should be sufficient to resolve most abends. However,\nif the message occurs for all captured dumps, contact your systems programmer to ensure that DFHPEP has been\nmodified to link to IN25PEP, as described in the installation materials. If DFHPEP is set up correctly, refer to the CICS", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8ab65cb7aa68-1", "text": "Recovery and Restart Guide for reasons why DFHPEP may not execute. If the message was generated for one of the last\nthree reasons, no action is necessary.\nCASD6101\nERROR IN DISPLAYING SYMDUMP\nReason:\nThe program has encountered an unusual condition and terminated processing.\nAction:\nCheck the installation. Contact Broadcom Support .\nCASD6102\nSYMDUMP FILE IS NOT OPEN\nReason:\nThe SymDump  for CICS file could not be accessed.\nAction:\nUse the CEMT command to check the status of the file and to determine why the file was closed.\nCASD6103\nINSUFFICIENT STORAGE TO DISPLAY SYMDUMP\nReason:\n 1467", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4854bf9843f9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThere is not enough free DSA storage in CICS to process a SymDump  for CICS display request.\nAction:\nCheck why CICS is short on storage and reenter the transaction.\nCASD6104\nI/O ERROR ON SYMDUMP FILE\nReason:\nAn error occurred during a read or write to the SymDump  for CICS file.\nAction:\nCheck the CICS log for any VSAM messages relating to the file.\nCASD6105\nA PROGRAM WAS NOT DEFINED OR WAS DISABLED\nReason:\nOne of the SymDump  for CICS programs could not be located.\nAction:\nCheck the installation instructions to determine all the PPT entries that must be defined in CICS.\nCASD6106\nA TWA WAS NOT DEFINED FOR THIS TASK\nReason:\nThe transaction invoking this display requires a TWA size to be defined.\nAction:\nCheck the installation instructions to determine the correct TWA size for this task.\nCASD6108\nPROTDMP INDEX MISSING OR DAMAGED\nReason:\nThe dump of a program on the SymDump  for CICS file is not valid.\nAction:\nDetermine whether the problem occurs with other dumps as well. Contact Broadcom Support .\nCASD6109\nTCA NOT FOUND IN CAPTURED DUMP\nReason:\nSymDump  for CICS was unable to capture a complete transaction dump. A possible cause is storage corruption. The\nbreakpoint display may not show the actual point of abend, but areas captured by SymDump  for CICS will be available for\nyour review.\nAction:\nDetermine whether the problem occurs with other dumps as well. Contact Broadcom Support .\nCASD6110\nCURRENT PPT NOT FOUND IN DUMP\nReason:\n 1468", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "63ef09a12dcd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSymDump  for CICS was unable to capture a complete transaction dump. A possible cause is storage corruption. The\nbreakpoint display may not show the actual point of abend, but areas captured by SymDump  for CICS will be available for\nyour review.\nAction:\nDetermine whether the problem occurs with other dumps as well. Contact Broadcom Support .\nCASD6111\nCURRENT PROGRAM NOT FOUND IN DUMP\nReason:\nSymDump  for CICS was unable to capture a complete transaction dump. A possible cause is storage corruption. The\nbreakpoint display may not show the actual point of abend, but areas captured by SymDump  for CICS will be available for\nyour review.\nAction:\nDetermine whether the problem occurs with other dumps as well. Contact Broadcom Support .\nCASD6112\nPL/I STORAGE NOT FOUND IN DUMP\nReason:\nSymDump  for CICS was unable to capture a complete transaction dump. A possible cause is storage corruption. The\nbreakpoint display may not show the actual point of abend, but areas captured by SymDump  for CICS are available for\nyour review.\nAction:\nDetermine whether the problem occurs with other dumps as well. Contact Broadcom Support .\nCASD6113\nCOBOL STORAGE NOT FOUND IN DUMP\nReason:\nSymDump  for CICS was unable to capture a complete transaction dump. A possible cause is storage corruption. The\nbreakpoint display may not show the actual point of abend, but areas captured by SymDump  for CICS are available for\nyour review.\nAction:\nDetermine whether the problem occurs with other dumps as well. Contact Broadcom Support .\nCASD6114\nCSA NOT FOUND IN CAPTURED DUMP\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "63ef09a12dcd-1", "text": "CASD6114\nCSA NOT FOUND IN CAPTURED DUMP\nReason:\nSymDump  for CICS was unable to capture a complete transaction dump. A possible cause is storage corruption. The\nbreakpoint display may not show the actual point of abend, but areas captured by SymDump  for CICS are available for\nyour review.\nAction:\nDetermine whether the problem occurs with other dumps as well. Contact Broadcom Support .\nCASD6115\nEIUS NOT FOUND IN CAPTURED DUMP\nReason:\n 1469", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "344b72b8e655-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSymDump  for CICS was unable to capture a complete transaction dump. A possible cause is storage corruption. The\nbreakpoint display may not show the actual point of abend, but areas captured by SymDump  for CICS are available for\nyour review.\nAction:\nDetermine whether the problem occurs with other dumps as well. Contact Broadcom Support .\nCASD6116\nRSA NOT FOUND IN CAPTURED DUMP\nReason:\nSymDump  for CICS was unable to capture a complete transaction dump. A possible cause is storage corruption. The\nbreakpoint display may not show the actual point of abend, but areas captured by SymDump  for CICS are available for\nyour review.\nAction:\nDetermine whether the problem occurs with other dumps as well. Contact Broadcom Support .\nCASD6117\nTGT NOT FOUND IN CAPTURED DUMP\nReason:\nSymDump  for CICS was unable to capture a complete transaction dump. A possible cause is storage corruption. The\nbreakpoint display may not show the actual point of abend, but areas captured by SymDump  for CICS are available for\nyour review.\nAction:\nDetermine whether the problem occurs with other dumps as well. Contact Broadcom Support .\nCASD6118\nBACKTRACE TABLE NOT FOUND IN CAPTURED DUMP\nReason:\nSymDump  for CICS was unable to capture a complete transaction dump. A possible cause is storage corruption. The\nbreakpoint display may not show the actual point of abend, but areas captured by SymDump  for CICS are available for\nyour review.\nAction:\nDetermine whether the problem occurs with other dumps as well. Contact Broadcom Support .\nCASD6119\nAIBX not found in captured dump\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "344b72b8e655-1", "text": "CASD6119\nAIBX not found in captured dump\nReason:\nThe AIBX was not available when the dump was captured, and therefore not available to be viewed.\nAction:\nSome dump display selections are unavailable for viewing.\nCASD6122\nUnable to resolve backtrace\nReason:\nThe backtrace is not available because the CICS Internal Trace did not have sufficient information to build the backtrace\ntable.\nAction:\nNo action required.\n 1470", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "45d2cdd229d3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6123\nEIS not found in captured dump\nReason:\nThe EIS was not available when the dump was captured, so therefore not available to be viewed.\nAction:\nNo action required.\nCASD6124\nUnable to resolve abending address\nReason:\nSymDump  for CICS was unable to determine the address where the program abended.\nAction:\nNo action required.\nCASD6125\nRegion is shortonstorage\nReason:\nCICS is short on storage. The dump capture will be incomplete because SymDump  for CICS is curtailing activity to help\nCICS recover from system stress.\nAction:\nDiscuss the problem with your systems programmer. Determine the cause of the system stress and rectify it.\nCASD6126\nCaptured dump is incomplete, cannot be displayed.\nReason:\nThis message indicates that SymDump  for CICS failed during the dump capture process, and that the dump is incomplete\nand cannot be viewed. The user should contact systems programming to review the CICS message log for error\nmessages indicating the cause of the failure, so that they may collect this and any related documentation (including SVC\ndumps that may have been produced) to report and forward the information to Broadcom Support  for problem resolution.\nAction:\nNone.\nCASD6127\nCorrupt pointers found, dump may be incomplete.\nReason:\nThis message indicates that during the capture process, SymDump  for CICS was unable to follow a storage or control\nblock chain that normally would be found intact. SymDump  for CICS proceeds to capture as much of the dump as\npossible and the user is able to use all the basic functions of SymDump  for CICS to debug the abending task. There could", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "45d2cdd229d3-1", "text": "be areas and functions normally available that are not available to the user in the dump. The problem is probably related\nto the task abend, and does not indicate a problem with SymDump  for CICS.\nAction:\nContact your Systems programmer to collect documentation, and determine the cause of the broken chain.\nCASD6128\nDump is incomplete, task may have been purged.\nReason:\n 1471", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "85d90a2b70e0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThis message indicates that this task was purged from CICS, and because of this abnormal method of termination areas\nnormally found during dump capture could not be located for capture. Because of this, SymDump  for CICS tries to capture\nas much of the dump as possible, but the dump may be incomplete, or may not be available to the user for diagnostic\npurposes. This does not indicate a problem with SymDump  for CICS.\nAction:\nContact your Systems programmer to collect documentation, and determine the reason for the task purge.\nCASD6129\nSymDump shutdown is in progress\nReason:\nSymDump  for CICS is being shut down. No further dump captures can be performed.\nAction:\nNone.\nCASD6176\nINTERTEST HELP FILE IS UNDEFINED, CLOSED OR DISABLED\nReason:\nInformation explaining the cause of your dump is stored on the HELP file, which cannot be accessed.\nAction:\nDefine the HELP file correctly, and ensure that it is open and enabled.\nCASD6177\nINSUFFICIENT STORAGE TO PROVIDE REQUEST TRY LATER\nReason:\nAn internal storage request could not be honored by CICS.\nAction:\nFor CICS 3.1 and above, check that the minimum EDSA specifications have been made according to instructions in\nInstalling and Configuring for SymDump  for CICS. For all CICS release, review your system for excessive virtual and real\nstorage utilization.\nCASD6178\nERROR IN PROGRAM PROCESSING SEE DUMP\nReason:\nA serious problem or abend occurred in your task.\nAction:\nContact Broadcom Support  for help in analyzing the dump.\nCASD6179\nFUNCTION NOT SUPPORTED\nReason:\nAn unsupported option number was entered on a menu.\nAction:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "85d90a2b70e0-1", "text": "Reason:\nAn unsupported option number was entered on a menu.\nAction:\nSpecify only valid option numbers that appear on the menu.\nCASD6180\nI/O ERROR ON INTERTEST HELP FILE\n 1472", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "eb2cb48fcc32-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nA request for HELP file information resulted in and I/O error.\nAction:\nAsk your technical staff to check the usability of the disk and file.\nCASD6181\nPROGRAM: (*) HAS NOT BEEN DEFINED OR IS DISABLED\nReason:\nA request to access SymDump  for CICS program was not honored.\nAction:\nCheck that the SymDump  for CICS installation was completed and that no programs are disabled.\nCASD6182\nABEND/DUMP CODE IS NOT ON INTERTEST HELP FILE\nReason:\nBecause the abend/dump code is not found in the HELP file, SymDump  for CICS cannot analyze the reason for the\nabend.\nAction:\nTo take advantage of the HELP facility, allow abends and dumps to use CICS default codes.\nCASD6183\nFORMATTING OF TRACE TABLE HAS FAILED REQUEST ABORTED\nReason:\nFormatting of the trace table for display failed.\nAction:\nSubmit this request later. If it fails again, contact Broadcom Support  with the associated dumps.\nCASD6184\nA TRACE TABLE WAS NOT FOUND IN THIS DUMP\nReason:\nStorage for the task that abended was probably corrupted. The formatted trace table cannot be displayed for this dump.\nAction:\nNone.\nCASD6185\nNO SYMBOLIC DATA FOUND FOR THE ABENDING PROGRAM\nReason:\nThe source listing for the program that caused the abend cannot be displayed.\nAction:\nRecompile the abending program with the postprocessor and repeat the request.\nCASD6186\nREQUESTED AREA COULD NOT BE FOUND IN DUMP\nReason:\nStorage for the task that abended was probably corrupted. This area of the task cannot be viewed.\nAction:\n 1473", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "85cd2b99e94c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNone.\nCASD6187\nDUMP DATA COULD NOT BE RESOLVED FOR SYMBOLIC DISPLAY\nReason:\nEither a work area could not be built because of storage constraints or the data areas in the dump were overlaid in such a\nway that SymDump  for CICS could not resolve the symbolic information.\nAction:\nUse the TCA, TCTTE, EIB, trace table and other system areas to resolve the problem. The formatted versions of many of\nthese areas can be displayed.\nCASD6188\nSYMBOLIC DATA MAY NOT BE COMPLETE\nReason:\nThe transaction that abended had an invalid storage chain. Therefore, some symbolic data may be missing.\nAction:\nTry to follow the storage chains to determine where the task was destroyed.\nCASD6189\nOPTION IS ONLY VALID FOR COBOL PROGRAMS\nReason:\nThis option is only valid for COBOL programs.\nAction:\nSelect a valid option.\nCASD6226\nINSUFFICIENT STORAGE TO PROVIDE REQUEST TRY LATER\nReason:\nAn internal storage request could not be honored by CICS.\nAction:\nFor CICS 3.1 and above, check that the minimum EDSA specifications have been made according to instructions in\nInstalling and Configuring for SymDump  for CICS. For all CICS releases, review your system for excessive virtual and real\nstorage utilization.\nCASD6227\nERROR IN PROGRAM PROCESSING SEE DUMP\nReason:\nA serious problem or abend occurred in your task.\nAction:\nContact Broadcom Support  for help in analyzing the dump.\nCASD6228\nPROGRAM: (*) HAS NOT BEEN DEFINED OR IS DISABLED\nReason:\nA request to access SymDump  for CICS program was not honored.\nAction:\n 1474", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1611c51e6268-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCheck that the SymDump for CICS installation was completed and that no programs are disabled.\nCASD6229\nBOTTOM OF DATA\nReason:\nThe end of the data is displayed.\nAction:\nTo see additional data, scroll up.\nCASD6230\nTOP OF DATA\nReason:\nThe top of the data is displayed.\nAction:\nTo see additional data, scroll down.\nCASD6231\nINVALID COMMAND\nReason:\nThe command is not listed in the menu, or is contradicted by the PK key that was pressed.\nAction:\nSpecify the correct command.\nCASD6232\nSCROLL LIMIT REACHED\nReason:\nThe maximum scroll limit has been reached.\nAction:\nReduce the scroll amount, or scroll in the other direction.\nCASD6233\nNO TRACE ENTRIES WERE CAPTURED\nReason:\nThe trace cannot be displayed, because no entries were captured.\nAction:\nDetermine if the problem occurs with other dumps as well. Contact Broadcom Support .\nCASD6234\nCURRENT FILTER MASK ENTRIES LISTED ABOVE\nReason:\nInformational.\nAction:\nNone.\n 1475", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4b99ec38c4cb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6235\n(*) NOT FOUND, BOTTOM OF DATA REACHED\nReason:\nThe FIND command failed.\nAction:\nPF12 retrieves the command. Correct the entry and try again.\nCASD6236\n(*) NOT FOUND, TOP OF DATA REACHED\nReason:\nThe FIND command failed.\nAction:\nPF120 retrieves the command. Correct the entry and try again.\nCASD6237\nMASK ERROR, PLEASE RESPECIFY\nReason:\nThere was a mask format error.\nAction:\nReview the mask entries and correct the error.\nCASD6238\nGETMAINS WITHOUT FREEMAINS ARE HIGHLIGHTED\nReason:\nThe HOGM command has successfully located GETMAINs without freemains and has highlighted them.\nAction:\nUse the FIND HILITE command to locate the highlighted entries, or scroll to visually scan for them.\nCASD6239\nALL GETMAINS HAVE MATCHING FREEMAINS\nReason:\nThe HOGM command did not find any unmatched getmains and freemains.\nAction:\nReview the filter selection mask to ensure that you have included all of the entries that you wanted to be checked.\nCASD6241\nPLACE STRING IN QUOTES OR REMOVE LEADING SPACES\nReason:\nThe FIND command could not be processed.\nAction:\nCorrect the command and try again.\nCASD6242\nHIGHLIGHTING OF TRACE RECORDS HAS NOT BEEN PERFORMED\nReason:\n 1476", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "afbab9e8a6b0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nA FIND HILITE command was issued, but there are not highlighted entries at this time.\nAction:\nIssue the HOGM command, and try again.\nCASD6243\nNO GETMAINS WERE FOUND, HIGHLIGHTING WAS NOT PERFORMED\nReason:\nA HOGM command was issued, but there were no getmains in the trace entries.\nAction:\nEnsure that your filter mask is correct.\nCASD6244\nPLEASE ENTER A FIND ON THE COMMAND LINE\nReason:\nPF5 Repeat FIND was entered, but there is no FIND command to repeat.\nAction:\nSpecify a FIND command.\nCASD6245\nROWS ARE LOGICAL \"AND\"S\nReason:\nEach row is logically anded and used as a filter selection criteria.\nAction:\nNone.\nCASD6246\nROWS ARE LOGICAL \"AND\"S, COLUMNS ARE LOGICAL \"OR\"S\nReason:\nEach row is logically anded, and the columns are logically ored.\nAction:\nNone.\nCASD6247\n(*) FOUND IN ENTRY (*)\nReason:\nThe FIND command located the specified string in the specified entry.\nAction:\nNone.\nCASD6250\nSYMDUMP/CICS COULD NOT LOCATE THE TRACE FORMAT REGION\nReason:\nTo format the CICS trace entries, SymDump  for CICS must locate the Trace Formatting Region within your existing\nCCI NETWORK. In this case, this region could not be found. Either the region has not been started, or the IN25OPTS\nTRCFFMID is incorrect.\nAction:\n 1477", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "16bc0a887482-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nContact your Systems Programmer for resolution.\nCASD6251\nCCI INIT FAILURE SEE DUMP\nReason:\nWhile trying to format your CICS trace entries, SymDump  for CICS needed to perform an initialization call to CCI\nSERVICES within your CCI NETWORK. This call failed. A dump has been produced, and there may also be diagnostic\nmessages produced to the CICS MSGUSR queue and/or the TRACE FORMAT REGION SYSPRINT file.\nAction:\nContact your Systems Programmer with this information.\nCASD6252\nIN25OPTS MISSING OR INCORRECT\nReason:\nSymDump  for CICS was unable to locate a proper IN25OPTS module. Processing cannot continue.\nAction:\nContact your Systems Programmer. Determine why the IN25OPTS module cannot be located and resolve the issue.\nCASD6253\nCCI CONVERSE FAILURE SEE DUMP\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS uses CCI SERVICES to enable communication between\nCICS and the TRACE FORMAT REGION within your CCI NETWORK. A CCI call has failed. A dump has been taken\nand there will be diagnostic messages produced to the CICS MSGUSR queue and/or the TRACE FORMAT REGION\nSYSPRINT file.\nAction:\nRecord this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They\nmay need to contact Broadcom Support  with the appropriate documentation.\nCASD6254\nSUBTASK SEND FAILURE SEE DUMP\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS uses CCI SERVICES to enable communication between\nCICS and the TRACE FORMAT REGION within your CCI NETWORK. A CCI call has failed. A dump has been taken\nand there will be diagnostic messages produced to the CICS MSGUSR queue and/or the TRACE FORMAT REGION", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "16bc0a887482-1", "text": "and there will be diagnostic messages produced to the CICS MSGUSR queue and/or the TRACE FORMAT REGION\nSYSPRINT file.\nAction:\nRecord this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They\nmay need to contact Broadcom Support  with the appropriate documentation.\nCASD6255\nINSUFFICIENT STORAGE TRY AGAIN LATER\nReason:\nDuring Trace Formatting, a CICS getmain request failed due to insufficient storage. You are advised to try the request\nagain to see if the storage has become available.\nAction:\n 1478", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "03fe19b24d74-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nTry request again. If the problem persists, contact your Systems Programmer to review the virtual storage limits specified\nfor your CICS region, and increase these as needed.\nCASD6256\nIN25BTRC FORMAT CONVERSE TIMEOUT, TRY AGAIN LATER\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS uses CCI SERVICES to enable communication between\nCICS and the TRACE FORMAT REGION within your CCI NETWORK. To ensure that finite resources are not wasted\nwhen the terminal is unattended, or during a system slowdown, a timeout limit is specified in the IN25OPTS for your CICS\nregion. In this case the timeout limit has been exceeded.\nAction:\nThis may occur normally due to system loads. If the problem persists, contact your systems programmer for resolution.\nThey may need to contact Broadcom Support  with the appropriate documentation. Review the IN25OPTS parameter\nTRCFTOUT for controlling the timeout duration.\nCASD6257\nTRACE TIMEOUT, ALL FILTERS AND OVERRIDES HAVE BEEN RESET\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS uses CCI SERVICES to enable communication between\nCICS and the TRACE FORMAT REGION within your CCI NETWORK. To ensure that finite resources are not wasted\nwhen the terminal is unattended, or during a system slowdown, a timeout limit is specified in the IN25OPTS for your CICS\nregion. In this case the time-out limit has been exceeded, and any filters and/or overrides you have specified are reset.\nAction:\nThis may occur normally due to system loads, or the operator has not solicited any terminal output for longer than\nthe timeout limit specified in IN25OPTS. If the problem is persistent, contact your systems programmer for resolution.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "03fe19b24d74-1", "text": "They may need to contact Broadcom Support  with the appropriate documentation. Review the IN25OPTS parameter\nTRCFTOUT for controlling the timeout duration.\nCASD6258\n(*) hilited in (*) entries\nReason:\nThis is a purely informational message in response to a HILITE or 'H' command having been entered on the command\nline. All occurrences of a specified string have been located, and the entries are highlighted.\nAction:\nNone.\nCASD6259\nIN25BTRC CCI CONVERSE - (*)\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS uses CCI SERVICES to enable communication between\nCICS and the TRACE FORMAT REGION within your CCI NETWORK. A CCI call has failed. A dump may have been\ntaken and diagnostic messages are produced to the CICS MSGUSR queue and/or the TRACE FORMAT REGION\nSYSPRINT file.\nAction:\nRecord this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They\nmay need to contact Broadcom Support  with the appropriate documentation.\n 1479", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f1d34b2553f1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6260\nIN25DTRC CCI CONVERSE (*)\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS uses CCI SERVICES to enable communication between\nCICS and the TRACE FORMAT REGION within your CCI NETWORK. A CCI call has failed. A dump may have been\ntaken and diagnostic messages are produced to the CICS MSGUSR queue and/or the TRACE FORMAT REGION\nSYSPRINT file.\nAction:\nRecord this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They\nmay need to contact Broadcom Support  with the appropriate documentation.\nCASD6261\nMAXIMUM THREADS REACHED FOR TRACE FORMAT, TRY AGAIN LATER\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS uses CCI SERVICES to enable communication between\nCICS and the TRACE FORMAT REGION within your CCI NETWORK. Trace formatting also requires a considerable\namount of virtual storage. To ensure that resource limits are not exceeded, a thread limit is specified in the IN25OPTS for\nyour CICS region. In this case the thread limit has been exceeded, and you are advised to wait until a thread becomes\navailable.\nAction:\nThis may occur normally due to system loads. If the problem persists, Contact your Systems Programmer for resolution,\nby reviewing and possibly increasing the IN25OPTS TRCFTHRD value specified.\nCASD6262\nINSUFFICIENT STORAGE FOR TRACE FORMAT, TRY AGAIN LATER\nReason:\nFormatting your CICS trace entries requires a considerable amount of virtual storage. To ensure that resource limits are\nnot exceeded, a maximum total storage limit is specified in the IN25OPTS table used by the TRACE FORMAT REGION.\nIn this case, this maximum total storage limit for all concurrent threads has been exceeded.\nAction:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f1d34b2553f1-1", "text": "In this case, this maximum total storage limit for all concurrent threads has been exceeded.\nAction:\nThis may occur normally due to system loads. If the problem persists, Contact your Systems Programmer for resolution,\nby reviewing and possibly increasing the IN25OPTS TRCFMEGM value specified.\nCASD6263\nTRACE SIZE BEYOND OPTS LIMIT, CONTACT SYSTEMS PROGRAMMER.\nReason:\nFormatting your CICS trace entries requires a considerable amount of virtual storage. To ensure that resource limits\nare not exceeded, a maximum thread storage limit is specified in the IN25OPTS table used by the TRACE FORMAT\nREGION. In this case, this maximum thread storage limit has been exceeded by the selected trace.\nAction:\nContact your Systems Programmer for resolution, by reviewing and possibly increasing the IN25OPTS TRCFMEGT value\nspecified.\nCASD6264\nTRACE TIMEOUT, OVERRIDES ARE RESET, FILTERS ARE RETAINED.\nReason:\n 1480", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dcdd0c19d1f9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWhile formatting your CICS trace entries SymDump  for CICS uses CCI SERVICES to enable communication between\nCICS and the TRACE FORMAT REGION within your CCI NETWORK. To ensure that finite resources are not wasted\nwhen the terminal is unattended, or during a system slowdown, a timeout limit is specified in the IN25OPTS for your\nCICS region. In this case the timeout limit has been exceeded, and any overrides you have specified are reset. Filters are\nretained.\nAction:\nThis may occur normally due to system loads, or the operator has not solicited any terminal output for longer than the\ntimeout limit specified in IN25OPTS. If the problem is persistent, contact your systems programmer for resolution. They\nmay need to contact Broadcom Support  with the appropriate documentation.\nCASD6275\nTWA SIZE IS SMALLER THAN REQUIRED AMOUNT\nReason:\nThe TWA size for transaction SYMD is incorrect.\nAction:\nSee Installing for the minimum length requirement and correct the TWA size entry.\nCASD6276\nONLY 'S', 'D', 'H' AND 'R' ARE VALID SELECT LETTERS\nReason:\nYou did not specify a valid letter.\nAction:\nCorrect the selection.\nCASD6277\nINSUFFICIENT STORAGE TO PROVIDE REQUEST TRY LATER\nReason:\nThere isn't enough storage in the CICS region to process this request.\nAction:\nContact your systems programmer. If the problem cannot be resolved, contact Broadcom Support .\nCASD6278\nERROR IN PROGRAM PROCESSING SEE DUMP\nReason:\nThe program has encountered an unusual condition and terminated processing.\nAction:\nPrint the dump, and contact Broadcom Support .\nCASD6279\nSYMDUMP DUMP DISPLAY FACILITY HAS ENDED\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dcdd0c19d1f9-1", "text": "CASD6279\nSYMDUMP DUMP DISPLAY FACILITY HAS ENDED\nReason:\nProgram termination was requested by the user with PF4.\nAction:\nTo display dumps again, reenter the transaction.\n 1481", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e018aff03d78-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6280\nTOP OF DATA\nReason:\nYou have used PF7 to scroll to the beginning of the dump list. The first item on the list is the most recent dump.\nAction:\nUse PF8 to scroll forward, if desired.\nCASD6281\nBOTTOM OF DATA\nReason:\nYou have used PF8 to scroll to the bottom of the dump list.\nAction:\nScroll backward using PF7, if desired.\nCASD6282\nI/O ERROR IN FILE PROCESSING\nReason:\nAn error has occurred during a READ or WRITE to the SymDump  for CICS file.\nAction:\nCheck the CICS log for any VSAM messages relating to the file.\nCASD6283\nFILE IS NOT OPEN\nReason:\nThe SymDump  for CICS file could not be accessed.\nAction:\nUse the CEMT command to check the status of the file and to determine why the file was closed.\nCASD6284\nREMOTE FILE CANNOT BE ACCESSED\nReason:\nA READ or WRITE command issued to a remote file failed to complete successfully.\nAction:\nCheck the file definition and the CICS connection to the remote system.\nCASD6285\nFILE IS NOT DEFINED\nReason:\nThe SymDump  for CICS file could not be accessed because it was not defined in CICS.\nAction:\nCheck the FCT definition for the file in CICS and reenter the transaction.\nCASD6286\nPRESS ENTER TO CONFIRM DELETE\nReason:\n 1482", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b0348adcf1c7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nD was entered next to a dump, requesting that the entry be deleted.\nAction:\nPress Enter to delete the dump from the file. Any other entry cancels the delete request.\nCASD6287\nINVALID DATE SUPPLIED\nReason:\nThe date specified in the selection criteria was not in the form mmddyy, or the month, day and year that you specified was\nnot valid.\nAction:\nSpecify a valid day, month and year.\nCASD6288\nINVALID TIME SUPPLIED\nReason:\nThe time specified in the selection criteria was not in the form hh or the hour was not within the range of 0 to 24.\nAction:\nSpecify a valid hour parameter.\nCASD6289\nINVALID DUMP FILE NAME SUPPLIED\nReason:\nThe file name specified may not defined in the FCT, or the SYMDWILD= option is specified in IN25OPTS and your\nwildcard specification is invalid.\nAction:\nDefine the file in the FCT, and review your SYMDWILD= value. Reenter the transaction criteria specification.\nCASD6290\nNO FILE ENTRIES MATCH THE SEARCH CRITERIA\nReason:\nNo dump entries were found on the SymDump  for CICS file that corresponded to the criteria specified.\nAction:\nCheck the criteria and alter the specifications, if desired, or use PF4 to exit.\nCASD6292\nDUMP NO LONGER EXISTS\nReason:\nThe dump requested has been deleted either by an explicit delete request or by SymDump  for CICS (if the dump was not\nbeing HELD).\nAction:\nNone.\nCASD6293\nOVERFLOW IN FREESPAN AREA OF SYMDUMP FILE\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b0348adcf1c7-1", "text": "CASD6293\nOVERFLOW IN FREESPAN AREA OF SYMDUMP FILE\nReason:\nToo many freespace fragments on a SymDump  for CICS file caused an overflow of the freespan list.\n 1483", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3c0e5a9b0d80-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nDelete any unnecessary dumps.\nCASD6294\nPROGRAM IN25COLD NOT FOUND\nReason:\nThe IN25COLD program was not found in the PPT or could not be loaded.\nAction:\nIf SymDump  for CICS is being used in this CICS system for analysis only, no action is required. If SymDump  for CICS is\nalso going to be used to capture dumps in this system, you must determine why the program cannot be found or loaded.\nCASD6295\nSYMDUMP FILE IS FULL\nReason:\nThere is not enough free space on the SymDump  for CICS file for more dumps.\nAction:\nDelete unnecessary dumps.\nCASD6296\nSYMDUMP FILE IS WRONG FORMAT\nReason:\nThe PROTDMP file was not properly initialized and cannot be used. CICS 3.1 and above users of SymDump for CICS\ncannot use the same PROTDMP file as CICS 2.1 and below users.\nAction:\nInitialize PROTDMP correctly.\nCASD6297\nTry function later, Dump in progress\nReason:\nThe PROTDMP file is busy capturing a dump and cannot process your request right now.\nAction:\nTry the request again later.\nCASD6298\nI/O error on CA SymDump file notify systems programmer\nReason:\nThere was an I/O error on the SymDump  for CICS file.\nAction:\nNotify your systems programmer.\nCASD6299\nAbend in DSP0, vsam acb open notify systems programmer\nReason:\nThere was an abend in IN25DSP0.\nAction:\nNotify your systems programmer.\n 1484", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1c70deb2e5d4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6300\nDump is already held\nReason:\nAn attempt was made to HOLD a dump that had previously been marked HOLD.\nAction:\nNo action required.\nCASD6301\nDump is already released\nReason:\nAn attempt was made to release a dump that had been previously released.\nAction:\nNo action required.\nCASD63010\nSORT command syntax is invalid\nReason:\nThe SORT command was specified incorrectly. Valid syntax for the SORT command is:\nSORT {DUMPFILE|TRAN|PROGRAM|OFFSET|ABEND|CREATED} {A|D}\nThe second parameter signifies which column to SORT by and the third parameter signifies whether to SORT in\nascending or descending order. If you do not specify a third parameter, the default is ascending.\nIf you specify the SORT command without parameters, the default SORT sequence is used, which is descending datetime\nwithin Dump File Id.\nAction:\nCorrect the command and retry.\nCASD6375\nCICS INTERNAL TRACE HAS BEEN CAPTURED BY SYMDUMP\nReason:\nThe SYMT transaction has successfully captured the CICS internal trace.\nAction:\nNone.\nCASD6376\nPROGRAM (*) WAS NOT FOUND\nReason:\nOne of the SymDump  for CICS programs could not be located.\nAction:\nCheck the installation instructions to determine all the PPT entries that must be defined in CICS.\nCASD6377\nSYMDUMP NOT STARTED, TRACE CAPTURE NOT PERFORMED\nReason:\nSymDump  for CICS must be started before you can issue the SYMT transaction.\nAction:\nStart SymDump  for CICS, and reenter the SYMT transaction.\n 1485", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f35c22a59737-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6378\nSYMDUMP UNABLE TO CAPTURE TRACE, PROTDMP IS FULL\nReason:\nThe SYMT transaction could not capture the CICS internal trace because the PROTDUMP file is full.\nAction:\nDelete entries from the PROTDUMP file, or redefine it, then the SYMT transaction will work.\nCASD6379\nSYMDUMP UNABLE TO CAPTURE TRACE, INSUFFICIENT SPACE ON PROTDMP\nReason:\nThe SYMT transaction could not capture the CICS internal trace because the PROTDUMP file is full.\nAction:\nDelete entries from the PROTDUMP file, or redefine it, then the SYMT transaction will work.\nCASD6380\nSYMDUMP UNABLE TO CAPTURE TRACE DUE TO GETMAIN FAILURE\nReason:\nThe SYMT transaction could not capture the CICS internal trace because a getmain request could not be satisfied.\nAction:\nExamine the CICS message log for other messages that explain the lack of storage. Examine the size of the CICS internal\ntrace table and reduce the size prior to reexecuting the trace capture.\nCASD6509\nABENDED TASK (*) STORAGE (*)\nReason:\nThis message identifies which storage area captured by SymDump  for CICS is currently being displayed using the CORE\nfacility. A list of SymDump  for CICS tags and their related storage block areas are listed in CICS Abend Analysis.\nAction:\nNone.\nCASD6510\nINVALID ADDRESS, NOT CAPTURED BY SYMDUMP\nReason:\nStorage at the requested address was not captured by SymDump  for CICS at the point of abend, and is not available for a\nCORE display.\nAction:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f35c22a59737-1", "text": "CORE display.\nAction:\nReview the request. Refer to CICS Abend Analysis for a list of storage areas that SymDump  for CICS captures. Modify\nthe request appropriately.\nCASD6511\nSSCR DATA STREAM INCOMPLETE, CAPTURED DATA DISPLAYED\nReason:\nThe SSCR data stream was incomplete, but as much data as was captured has been displayed.\nAction:\nNone.\n 1486", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2e1ad41b41f3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6512\nSSCR DATA HAS EXTENDED ATTRIBUTES (NOT SUPPORTED ON THIS TERMINAL)\nReason:\nThis terminal does not support the extended attributes needed to display the screen.\nAction:\nRetry this request from a terminal that supports extended attributes.\nCASD6550\nSQLCODE NNN OCCURRED DURING DUMP CAPTURE\nReason:\nThis error occurs during the SymDump  for CICS transaction dump capture process. The query issued to obtain the Last\nSQL Statement failed due to reasons explained by the SQLCODE information in the message. SymDump  for CICS was\nunable to obtain the Last SQL Statement issued by the application.\nAction:\nSee the SQLCODE in the DB2 Messages and Codes  manual for a detailed explanation of why the failure occurred.\nCorrect the problem so that this does not occur in the future.\nCASD6551\nCA SYMDUMP/CICS HAS PRODUCED AN EXT2 TRANSACTION DUMP FOR THE FOLLOWING REASON\nReason:\nThis error occurs during the SymDump  for CICS transaction dump capture process. For some reason the secondary\nphase of the transaction dump capture where the LASTSQL information would be written to the PROTDMP file was not\ncompleted. An EXT2 transaction dump was produced to aid in diagnosis. Error message CASD6552 contains additional\ninformation.\nAction:\nReview message code CASD6552, which accompanies CASD6551. Contact Broadcom Support  for additional help if the\nproblem cannot be resolved with the information provided in the message text.\nCASD6552\nTASK NNNNN XXXXXX\nReason:\nThis error occurs during the SymDump  for CICS transaction dump capture process. For some reason the secondary\nphase of the transaction dump capture where the LASTSQL information would be written to the PROTDMP file was not", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2e1ad41b41f3-1", "text": "completed. An EXT2 transaction dump was produced to aid in diagnosis. Error message CASD6551 contains additional\ninformation. Task NNNNN is the EXT2 abending task; XXXXXX is additional text describing the reason for the EXT2\nabend.\nAction:\nReview message code CASD6552, which accompanies CASD6551. Contact Broadcom Support  for additional help if the\nproblem cannot be resolved with the information provided in the message text.\nCASD6607\nINSUFFICIENT STORAGE TO PROVIDE REQUEST TRY LATER\nReason:\nAn internal storage request could not be honored by CICS.\nAction:\nFor CICS 3.1 and above, check that the minimum EDSA specifications have been made according to instructions in\nInstalling and Configuring. For all CICS releases, review your system for excessive virtual and real storage utilization.\n 1487", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bdded6a35af7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6608\nERROR IN PROGRAM PROCESSING SEE DUMP\nReason:\nThe transaction that abended had an invalid storage chain. Therefore, some symbolic data may be missing.\nAction:\nTry to follow the storage chains to determine where the task was destroyed.\nCASD6609\nPROGRAM: (*) HAS NOT BEEN DEFINED OR IS DISABLED\nReason:\nA request to access SymDump  for CICS program was not honored.\nAction:\nAsk your technical staff to check the usability of the disk and file.\nCASD6801\nERROR IN INITIATING SYMDUMP\nReason:\nThe program has encountered an unusual condition and terminated processing.\nAction:\nCheck the product installation. Contact Broadcom Support .\nCASD6802\nPROGRAM (*) WAS NOT FOUND\nReason:\nThe specified program was not found in the PPT.\nAction:\nCheck the installation procedure and correct any errors.\nCASD6803\nNO VALID REQUEST WAS FOUND\nReason:\nThe SymDump  for CICS initialization program did not receive a valid start request.\nAction:\nCheck Installing for the necessary PCT definitions.\nCASD6804\nSYMDUMP HAS INITIALIZED SUCCESSFULLY\nReason:\nA start request has been issued using the SymDump  for CICS primary menu (option 2) and the function has completed\nsuccessfully.\nAction:\nDumps will now be written to the SymDump  for CICS file.\nCASD6805\nREQUEST REJECTED DUE TO INSUFFICIENT VIRTUAL STORAGE TRY LATER\n 1488", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "991c4510160a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nThere isn't enough free DSA storage in CICS to fill a storage request.\nAction:\nCheck why CICS is short on storage and reenter the transaction.\nCASD6806\n\"END\" REQUEST REJECTED. ERROR CODE: (*)\nReason:\nA VSAM error was encountered during processing of an END request. SymDump  for CICS was not terminated.\nAction:\nCheck the VSAM manual for an explanation of the error code.\nCASD6807\nSTART REQUEST FAILED\nReason:\nSymDump  for CICS could not be started because of a VSAM error encountered during OPEN processing.\nAction:\nUse the CEMT command to determine the status of the file.\nCASD6808\nSTART REQUEST REJECTED. ERROR CODE: (*)\nReason:\nSymDump  for CICS could not be started because of a VSAM error encountered during OPEN processing.\nAction:\nCheck the VSAM manual for an explanation of the error code.\nCASD6809\nSTART REQUEST PROCESSED. WARNING CODE: (*)\nReason:\nThe SymDump  for CICS file was opened successfully, but VSAM has issued a warning during OPEN processing.\nAction:\nCheck the VSAM manual for an explanation of the error code.\nCASD6810\nSYMDUMP HAS BEEN INITIALIZED BUT PARAMETERS HAVE NOT BEEN LOADED\nReason:\nSymDump  for CICS initialization has completed successfully, but no valid initialization parameters were found on the\nSymDump  for CICS file.\nAction:\nDefault parameters will be used during processing.\nCASD6811\nSYMDUMP HAS ENDED\nReason:\nAn end request has been issued from the SymDump  for CICS primary menu (option 3) and SymDump  for CICS has been\nterminated.\n 1489", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ebf23657af62-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nDumps will now be written to the CICS dump file.\nCASD6812\nPROGRAM IN25COLD IS THE WRONG RELEASE\nReason:\nThe release of program IN25COLD does not match the release of the IN25INST program.\nAction:\nPerform the following steps:\n1.\n2.Run the transaction VRPT and use option 4 to check for any other programs that may be the wrong release.\n3.\n4.Check that all SymDump  for CICS programs are coming from the same library.\n5.\n6.Recheck the outputs produced during installation.\n7.\nCASD6813\nA CA LMP RIMSTAT ERROR HAS BEEN DETECTED\nReason:\nLMP check failed for SymDump  for CICS.\nAction:\nContact Broadcom Support .\nCASD6814\nSYMDUMP WAS ALREADY STARTED\nReason:\nSymDump  for CICS has already been started.\nAction:\nNone.\nCASD6815\nSYMDUMP WAS ALREADY TERMINATED\nReason:\nSymDump  for CICS has already been terminated.\nAction:\nNone.\nCASD6816\nSYMDUMP FILE IS WRONG FORMAT\nReason:\nThe PROTDMP file was not properly initialized and cannot be used. CICS 3.1 and above users of SymDump  for CICS\ncannot use the same PROTDMP file as CICS 2.1 and below users.\nAction:\nInitialize PROTDMP correctly.\n 1490", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "30d3c4b89760-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6817\nUser is not authorized to issue request\nReason:\nThis user is not authorized to do this request.\nAction:\nObtain proper authority and then reissue the request.\nCASD6818\nGlobal exit program IN25STRU is not enabled\nReason:\nProgram IN25STRU is required for proper dump capture, but is currently not available.\nAction:\nNotify your systems programmer.\nCASD6819\nCA SymDump not available on this system as set in CAVHCONF\nReason:\nThe CAVHCONF configuration module, which is loaded into the CSA, indicates that the product is not intended to be used\non this system.\nAction:\nContact your systems programmer to ensure that the CAVHCONF configuration macro was implemented correctly on this\nsystem and that the CAVHINIT process was run.\nCASD6820\nCAVHCONF module not found in the CSA\nReason: The CAVHCONF configuration module was not found in the CSA.\nAction:\nCheck with your system programmer to ensure that the CAVHINIT process was run.\nCASD6951\nINVALID INPUT DATA FOUND\nReason:\nThe data entered where the cursor is positioned is not valid.\nAction:\nSpecify valid data in the field.\nCASD6952\nINSUFFICIENT STORAGE TO PROVIDE REQUEST TRY LATER\nReason:\nThere isn't enough free DSA storage in CICS to fill a storage request.\nAction:\nDetermine why CICS is short on storage and reenter the transaction.\n 1491", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a27275193315-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6953\nRROR IN PROGRAM PROCESSING SEE DUMP\nReason:\nThe program has encountered an unusual condition and terminated processing.\nAction:\nPrint the dump and contact Broadcom Support .\nCASD6954\nSYMDUMP INITIALIZATION PROCESSING HAS ENDED\nReason:\nThe user requested program termination with PF4.\nAction:\nTo redisplay the initialization menu, reenter the transaction.\nCASD6955\nOPTION IS NOT AVAILABLE\nReason:\nThe transaction through which this option is invoked is not defined in CICS.\nAction:\nDefine the appropriate transactions in CICS as specified in Installing.\nCASD6956\nPARAMETERS HAVE BEEN UPDATED BY ANOTHER TASK ENTER AGAIN\nReason:\nWhile the current parameters were displayed, another task has updated the parameters. The new parameters are now\ndisplayed.\nAction:\nSpecify the changes again, and ensure that another user is not currently updating the parameters. Enter option 1 again to\nupdate the file.\nCASD6957\nSYMDUMP PARAMETERS HAVE BEEN UPDATED\nReason:\nUpdate of SymDump  for CICS parameters (option 1) was requested and processing has successfully completed.\nAction:\nNone.\nCASD6958\nINVALID OPTION ENTER 1, 2, OR 3\nReason:\nThe command specified on the command line was not valid.\nAction:\nSpecify a valid option or END.\n 1492", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7a046751ceb5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6959\nPROGRAM IN25COLD NOT FOUND\nReason:\nThe IN25COLD program was not active in the PPT or could not be loaded.\nAction:\nCheck all installation steps, correct any errors, and resubmit the job. Dumps will not be captured until this error is\ncorrected.\nCASD6960\nSYMDUMP IS ACTIVE\nReason:\nSymDump  for CICS is active.\nAction:\nNone.\nCASD6961\nSYMDUMP IS NOT ACTIVE\nReason:\nSymDump  for CICS is not active.\nAction:\nNone.\nCASD6962\nSYMDUMP IS ACTIVE; SYMDUMP FILE IS FULL\nReason:\nSymDump  for CICS is active. However, there is not enough free space on the SymDump  for CICS file for more dumps.\nAction:\nDelete any unnecessary dumps or release dumps currently being held.\nCASD6963\nSYMDUMP IS NOT ACTIVE; SYMDUMP FILE IS FULL\nReason:\nSymDump  for CICS is not active. However, there is not enough free space on the SymDump  for CICS file for more\ndumps.\nAction:\nDelete any unnecessary dumps or release dumps currently being held.\nCASD6964\nI/O ERROR IN DUMP FILE PROCESSING\nReason:\nThe SymDump  for CICS file specified could not be opened.\nAction:\nCheck the installation procedures.\n 1493", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "77598c07c0dc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6965\n(*) FILE IS NOT OPEN\nReason:\nThe SymDump  for CICS file specified could not be opened.\nAction:\nCheck the installation procedures.\nCASD6966\nREMOTE DUMP FILE CANNOT BE ACCESSED\nReason:\nThe SymDump  for CICS file specified could not be opened.\nAction:\nCheck the installation procedures.\nCASD6967\n(*) FILE IS NOT DEFINED\nReason:\nThe FCT entry for the specified SymDump  for CICS file could not be found.\nAction:\nCheck the installation procedures.\nCASD6968\n(*) FILE IS NOT INITIALIZED, OR IS DAMAGED\nReason:\nSymDump  for CICS could not read the first record on the SymDump  for CICS dump file.\nAction:\nCheck the installation procedures.\nCASD6969\nPress ENTER to confirm parameter update request; PF3 to cancel\nReason:\nThis is a confirmation warning.\nAction:\nIf you are sure you want to update the configuration parameters, press enter; otherwise press PF3 to cancel.\nCASD6970\nI/O error on CA SymDump file notify systems programmer\nReason:\nThere was an I/O error on the SymDump  for CICS file.\nAction:\nNotify your systems programmer.\nCASD6971\nTry function later, Dump in progress\nReason:\n 1494", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b5be73e40459-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe PROTDMP file is busy capturing a dump and cannot process your request right now.\nAction:\nTry the request again later.\nCASD6972\nAbend in DSP0, vsam acb open notify system programmer\nReason:\nThere was an abend in IN25DSP0.\nAction:\nNotify your systems programmer.\nCASD7007\nINSUFFICIENT STORAGE TO PROVIDE REQUEST TRY LATER\nReason:\nAn internal storage request could not be honored by CICS.\nAction:\nFor CICS 3.1 and above, check the minimum EDSA specifications have been made according to instructions in Installing\nand Configuring. For all CICS releases, review your system for excessive virtual and real storage utilization.\nCASD7008\nERROR IN PROGRAM PROCESSING SEE DUMP\nReason:\nA serious problem or abend occurred in your task.\nAction:\nContact Broadcom Support .\nCASD7011\nPROGRAM: (*) HAS NOT BEEN DEFINED OR IS DISABLED\nReason:\nThe dump of a program on the SymDump  for CICS file is not valid.\nAction:\nDetermine whether the problem occurs with other dumps as well. Contact Broadcom Support .\nCASD7087\nFREESPAN ERROR BEFORE CAPTURE\nReason:\nDuring dump capture, SymDump  for CICS detected a problem with the available free space on the PROTDMP file. The\nmost likely cause is that the PROTDMP file is corrupted. IN25COLD will attempt to produce a U0908 diagnostic abend.\nAction:\nTake the following steps, and then contact Broadcom Support .\n1. Collect all dumps produced in the timeframe of the occurrence.\n2. Make an idcams repro copy of the PROTDMP file.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b5be73e40459-1", "text": "2. Make an idcams repro copy of the PROTDMP file.\n3. Run an IN25DMPU \u2018LIST ALL\u2019. An rc08 means the file is corrupt and should be rebuilt. You can copy old dumps from\nthe corrupt file to a new PROTDMP file using IN25DMPU.\n 1495", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b6a2ccd9ee6a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD7207\nINSUFFICIENT STORAGE TO PROVIDE REQUEST TRY LATER\nReason:\nAn internal storage request could not be honored by CICS.\nAction:\nFor CICS 3.1 and above, check the minimum EDSA specifications have been made according to instructions in Installing\nand Configuring. For all CICS releases, review your system for excessive virtual and real storage utilization.\nCASD7208\nERROR IN PROGRAM PROCESSING SEE DUMP\nReason:\nA serious problem or abend occurred in your task.\nAction:\nContact Broadcom Support .\nCASD7211\nPROGRAM: (*) HAS NOT BEEN DEFINED OR IS DISABLED\nReason:\nA request to access SymDump  for CICS program was not honored.\nAction:\nEnsure that SymDump  for CICS installation was completed and that no programs are disabled.\nCASD7301\nINSUFFICIENT STORAGE TO VERIFY FILE TRY LATER\nReason:\nThere is not enough storage at this time.\nAction:\nTry later when more storage is available.\nCASD7302\nERROR IN PROGRAM PROCESSING SEE DUMP\nReason:\nAn abend occurred.\nAction:\nAnalyzed the dump.\nCASD7303\nI/O ERROR ON DUMPFILE\nReason:\nThe dump file definitions did not allow reading, browsing or updating of the file.\nAction:\nFix the file definitions, and try again.\nCASD7304\nLOST RECORD SPAN RECLAIMED TO FREESPANS OF SYMDUMP FILE\n 1496", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "888ebc047718-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nSymDump  for CICS has internally freed space in the file. This may have occurred because the index section of the file\nwas about to overflow.\nAction:\nNone. If this happens too often, contact Broadcom Support .\nCASD7305\nBAD FREE SPAN REMOVED FROM LIST OF SYMDUMP FILE\nReason:\nSymDump  for CICS has internally freed space in the file. This may have occurred because the index section of the file\nwas about to overflow.\nAction:\nNone. If this happens too often, contact Broadcom Support .\nCASD7306\nRECORDS HAVE BEEN FOUND TO BELONG TO TWO OR MORE SYMDUMPS\nReason:\nRecords belong to multiple SymDump  for CICS data sets, which is a problem that should not occur.\nAction:\nPrint the first five records in the file, and contact Broadcom Support .\nCASD7308\nSYMDUMP FILE NOT REPAIRED VERIFICATION TO BE RETRIED\nReason:\nDuring verification, a new dump was written to the file. The verification must be repeated.\nAction:\nNone.\nCASD7309\nSYMDUMP FILE COULD NOT BE REPAIRED VERIFICATION ABORTED\nReason:\nDuring verification, a new dump was written to the file. This has happened twice. The verification must be tried later when\nthe system is less active.\nAction:\nNone.\nCASD7400\nIN25EXIT does not have required global work area.\nReason:\nDuring dump capture, program IN25STRU failed due to a catastrophic internal failure.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7401\nSymDump cannot process this abend.\nReason:\n 1497", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "97e8f88de757-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDuring dump capture, program IN25STRU failed due to a catastrophic internal failure.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7402\nGETMAIN failure in IN25EXIT for thread ECB.\nReason:\nDuring dump capture, program IN25STRU failed due to a catastrophic internal failure.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7403\nIN25EXIT failure on MVS_WAIT (exception).\nReason:\nDuring dump capture, program IN25STRU failed due to a catastrophic internal failure.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7404\nIN25EXIT failure on MVS_WAIT (invalid).\nReason:\nDuring dump capture, program IN25STRU failed due to a catastrophic internal failure.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7405\nIN25EXIT failure on MVS_WAIT (kernerror).\nReason:\nDuring dump capture, program IN25STRU failed due to a catastrophic internal failure.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7406\nIN25EXIT failure on MVS_WAIT (purged).\nReason:\nDuring dump capture, program IN25STRU failed due to a catastrophic internal failure. This may be due to the operator\npurging tasks that were in the process of dump capture.\nAction:\nSave all output, including the complete JESLOG and any dumps produced. Review the CICS log for signs of system", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "97e8f88de757-1", "text": "stress. If you cannot determine the cause of the task purges, contact Broadcom Support .\nCASD7407\nIN25EXIT failure on MVS_WAIT (disaster).\nReason:\nDuring dump capture, program IN25STRU failed due to a catastrophic internal failure.\nAction:\n 1498", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6155a75cc529-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7409\nTerminal receive failure in IN25STRU\nReason:\nDuring dump capture, program IN25STRU attempted to capture the current contents of the 3270 screen, but failed.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7410\nAPI failure IN25STRU\nReason:\nDuring dump capture, program IN25STRU attempted to gather information for the abending task, but failed.\nAction:\nVerify that the security definitions for the abending task allow SymDump  for CICS to perform the CICS inquiry commands\nnecessary to complete dump capture. Carefully review the security violation logs, and correct the problem. If necessary,\ncontact your systems programmer.\nCASD7411\nDump capture will be incomplete.\nReason:\nDuring dump capture, SymDump  for CICS was unable to capture a complete dump. Other messages may indicate the\nreason for the problem.\nAction:\nReview the dump, as it may still be useful. If it is unusable and you cannot determine the cause of the failure, contact\nBroadcom Support .\nCASD7412\nA system or storage dump has been requested by transaction nnnn dump code is xxxxxxxx (task xxx).\nReason:\nSymDump  for CICS has intercepted a system dump request, but does not capture system dumps. This is an informational\nmessage, which is displayed if messages to the console are enabled through SYMI.\nAction:\nNone.\nCASD7413\nSymDump will not capture this dump.\nReason:\nCheck for other messages which indicate why the dump was not captured. This is an informational message, which is", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6155a75cc529-1", "text": "displayed if messages to the console are enabled through SYMI.\nAction:\nNone.\nCASD7414\nSymDump is suppressing the CICS dump.\nReason:\n 1499", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7bd8b60218bc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe configuration options 'Suppress AP0001 dumps' and/or 'Suppress transaction dumps' have been set to 'Y' through\nSYMI. This is an informational message, which is displayed if messages to the console are enabled through SYMI.\nAction:\nNone.\nCASD7415\nCICS will capture this dump.\nReason:\nCheck for other messages which indicate why the dump was not captured. This is an informational message, which is\ndisplayed if messages to the console are enabled through SYMI.\nAction:\nNone.\nCASD7417\nSTIMERM failure, cannot capture dump.\nReason:\nDuring dump capture, SymDump  for CICS encountered a catastrophic internal failure.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7418\nRecursive XDUREQ entry, cannot capture dump.\nReason:\nDuring dump capture, SymDump  for CICS encountered a catastrophic internal failure.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7419\nSymDump intercept of dump request for transaction nnnn: abend(nnnn), task(xxxxx)\nReason:\nThis is an informational message, which is displayed if messages to the console are enabled through SYMI.\nAction:\nNone.\nCASD7420\nTask missing IN25STRU work area\nReason:\nIf SymDump  for CICS tries to capture an abend for a task that started before SymDump  for CICS started, a SymDump  for\nCICS work area that must be attached to the task can be missing. In this case, SymDump  for CICS cannot capture the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7bd8b60218bc-1", "text": "dump and it terminates. The problem can also occur when Top Secret has put a terminal into LOCK MODE and the task is\nabended.\nAction:\nNone. The dump in question cannot be captured by SymDump  for CICS.\nCASD7500\nDump capture has terminated abnormally\n 1500", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4bf4bea3ebab-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nThis message appears with one or more other messages. It indicates there is a problem with SymDump  for CICS dump\ncapture.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7501\nPlease contact CA SymDump technical support.\nReason:\nThis message appears with one or more other messages.\nAction:\nContact your systems programmer (who should then contact Technical support).\nCASD7502\nIN25STRU failure, GLWA not available.\nReason:\nDuring dump capture, program IN25STRU failed due to a catastrophic internal failure.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7503\nIN25STRU is requesting a dump (SDUMP)\nReason:\nSymDump  for CICS program IN25STRU has detected a problem and has requested an SDUMP of the region.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7504\nIN25STRU recovery routine has no SDWA\nReason:\nDuring dump capture, program IN25STRU failed due to a catastrophic internal failure.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7505\nIN25STRU GETMAIN failure unable to take dump\nReason:\nDuring dump capture, program IN25STRU failed due to a catastrophic internal failure.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7506\nTRANSACTION XXXX (TASK NNNNN) IS NOT RESPONSIVE, DUMP CAPTURE WILL BE ABBREVIATED\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4bf4bea3ebab-1", "text": "Reason:\nDuring dump capture, SymDump  for CICS has put the task into a wait state for more than one minute. SymDump  for CICS\nis capturing an abbreviated dump for this task, and will continue to process other dumps.\n 1501", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "489613cb3257-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nDetermine the cause of the task going into a wait state, and resolve the problem so that future dumps can be captured\ncompletely.\nSymDump  for CICS Messages\nMost of the SymDump  for CICS messages display in online Help. Messages not accessible from online Help are listed\nhere.  \nCASD5351\nMM/DD/YYYY HH:MM:SS \u2013 FUNCTION: XXXXXXXX\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS uses CCI SERVICES to enable communication between\nCICS and the TRACE FORMAT REGION within your CCI NETWORK. A CCI call has failed. There will be diagnostic\nmessages produced to the CICS MSGUSR queue and/or the TRACE FORMAT REGION SYSPRINT file. Function is\nfollowed by internal information that describes that last activity performed.\nAction:\nRecord this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They\nmay need to contact Broadcom Support  with the appropriate documentation.\nCASD5352\nMM/DD/YYYY HH:MM:SS \u2013 IN25BTRC SENT NNNNNNNN OF NNNNNNNN BLOCKS\nReason:\nWhile formatting your CICS trace entries SymDump  for CICS uses CCI SERVICES to enable communication between\nCICS and the TRACE FORMAT REGION within your CCI NETWORK. A CCI call has failed. There will be diagnostic\nmessages produced to the CICS MSGUSR queue and/or the TRACE FORMAT REGION SYSPRINT file. This message\ngives counts of how many trace data blocks were sent to the Trace Format Region.\nAction:\nRecord this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They\nmay need to contact Broadcom Support  with the appropriate documentation.\nCASD60490", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "489613cb3257-1", "text": "may need to contact Broadcom Support  with the appropriate documentation.\nCASD60490\nSYMDUMP x.x.x COLD ASM date time\nReason:\nModule IN25COLD of SymDump  for CICS was assembled at the indicated date and time. This message is displayed\nwhen IN25COLD is made resident during initialization. x.x.x is your SymDump  for CICS release number.\nAction:\nNone.\nCASD60500\nCICS WILL CAPTURE THIS DUMP\nReason:\nSymDump  for CICS has finished processing the abend, and is returning control to CICS and directing it to record the\ndump in its own dump data set.\nAction:\nNone.\n 1502", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "897f0a1100d5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6051\nVSAM I/O ERROR ON SYMDUMP FILE. FUNC= xxx, RC= 00, FDBK= 000\nReason:\nA VSAM error occurred for the function xxx while accessing the SymDump  for CICS file.\nAction:\nCheck the VSAM manual for an explanation of the return code and FDBK code for the function specified.\nCASD6052\nSTANDARD CICS DUMP WILL BE TAKEN\nReason:\nAn I/O error occurred while accessing the SymDump  for CICS file. See message CASD6051.\nAction:\nDetermine the cause of the error from the VSAM return codes.\nCASD6053\nINSUFFICIENT VIRTUAL STORAGE FOR SYMDUMP PROCESSING\nReason:\nThere is not enough free DSA storage in CICS to fill a storage request.\nAction:\nCheck why CICS is short on storage and reenter the transaction.\nCASD6054\nINSUFFICIENT NONHELD RECORDS FOR SYMDUMP PROCESSING\nReason:\nThere is not enough free space on the SymDump  for CICS file to accommodate more dumps.\nAction:\nDelete unnecessary dumps or release dumps currently being held.\nCASD6055\nOVERFLOW IN FREESPAN AREA OF SYMDUMP FILE\nReason:\nToo many freespace fragments exist on the SymDump  for CICS file.\nAction:\nDelete unnecessary dumps to reduce the number of freespace fragments.\nCASD6056\nOVERFLOW IN INDEX AREA OF SYMDUMP FILE\nReason:\nThe maximum number of dumps has been exceeded.\nAction:\nDelete unnecessary dumps.\nCASD6057\nMANUAL DELETION OF DUMP ENTRIES NECESSARY\nReason:\n 1503", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9880ac4a08b5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFreespan area overflow or index area overflow has occurred. See messages CASD6055 and CASD6056.\nAction:\nDelete unnecessary dumps.\nCASD6060\nINVALID POINTER TO DATA\nReason:\nAn invalid storage address was found while dumping storage areas for a given task.\nAction:\nAnalyze the dump to determine the cause of the transaction abend.\nCASD6061\nINVALID POINTER TO NEXT LLA ON CHAIN\nReason:\nAn invalid pointer to the next LLA was found while dumping storage areas for a given task.\nAction:\nAnalyze the dump to determine the cause of the transaction abend.\nCASD6062\nINVALID POINTER TO NEXT USER STORAGE BLOCK ON CHAIN\nReason:\nAn invalid pointer to the next user storage block was found while dumping storage areas for a given task.\nAction:\nAnalyze the dump to determine the cause of the transaction abend.\nCASD6063\nINVALID POINTER TO NEXT TIOA STORAGE BLOCK ON CHAIN\nReason:\nAn invalid pointer to the next TIOA storage block was found while dumping storage areas for a given task.\nAction:\nAnalyze the dump to determine the cause of the transaction abend.\nCASD6064\nINVALID POINTER TO NEXT ANCHOR BLOCK ON CHAIN\nReason:\nAn invalid pointer to the next anchor block was found while dumping storage areas for a given task.\nAction:\nAnalyze the dump to determine the cause of the transaction abend.\nCASD6065\nINVALID POINTER TO NEXT PCB BLOCK ON CHAIN\nReason:\nAn invalid pointer to the next PCB block was found while dumping storage areas for a given task.\nAction:\nAnalyze the dump to determine the cause of the transaction abend.\n 1504", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "05b690f192b9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6066\nPROGRAM CHECK PSW DOES NOT POINT WITHIN DSA OF CICS\nReason:\nThe abending program was not a CICS loaded program.\nAction:\nUse the storage area dump around the PSW to help determine the cause of the transaction abend.\nCASD6067\nPROGRAM CHECK PSW POINTS WITHIN CURRENT PROGRAM\nReason:\nThe storage area around the PSW was not dumped separately because the abend occurred within the current program\nthat appears in the dump.\nAction:\nUse the storage area dump around the PSW to help determine the cause of the transaction abend.\nCASD6068\nSYMDUMP FILE IS LOGICALLY DESTROYED \u2013 CLOSE SYMDUMP PRINT FIRST FIVE RECORDS FOR ERROR\nANALYSIS AND REINITIALIZE THE FILE AT YOUR CONVENIENCE YOU MAY STILL PRINT EXISTING DUMPS\nBEFORE REINITIALIZATION\nReason:\nThe PROTDMP file has been damaged. No more dumps can be written to this file.\nAction:\nStop SymDump  for CICS, print the dumps, and obtain a hex printout of the first five records in the PROTDMP file.\nReinitialize the file and restart SymDump  for CICS. Contact Broadcom Support  for help in resolving the problem.\nCASD60690\nSYMDUMP INTERCEPT OF DUMP REQUEST FOR TRANSACTION aaaa (ABEND bbbb)\nReason:\nSymDump  for CICS has intercepted a CICS transaction dump for transaction code aaaa. The abend code for the dump is\nbbbb.\nAction:\nNone.\nCASD60700\nSYMDUMP GETMAIN FAILURE ENCOUNTERED\nReason:\nSymDump  for CICS was unable to obtain the storage required to capture this transaction dump. Processing is terminated.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "05b690f192b9-1", "text": "CICS takes a normal transaction dump.\nAction:\nReview other messages accompanying this message to determine the cause.\nCASD60710\nA SYSTEM OR STORAGE DUMP HAS BEEN REQUESTED FOR TRANSACTION aaaa DUMP CODE IS bbbbbbbb\nReason:\nSymDump  for CICS has intercepted an AP0001 system dump or an EXEC CICS dump request on behalf of transaction\naaaa. The dump type is shown as bbbbbbbb.\n 1505", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1624dcfcc6bf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nNone.\nCASD60720\nSYMDUMP WILL NOT CAPTURE THIS DUMP\nReason:\nSymDump  for CICS will not record this dump to the PROTDMP file. This is due to one of the following reasons:\n\u2022\n\u2022The dump is an AP0001 or EXEC CICS dump, which SymDump  for CICS does not handle.\n\u2022\n\u2022The dump has been EXCLUDED from SymDump  for CICS processing through an abend code entry on the SymDump\nfor CICS Initialization screen.\n\u2022\nAction:\nReview the SymDump  for CICS initialization parameters through the SYMI transaction. You can update the parameters to\nspecify how you want SymDump  for CICS to handle specific dumps.\nCASD60730\nSYMDUMP x.x.x HAS CAPTURED THIS DUMP\nReason:\nSymDump  for CICS has captured the dump. x.x.x represents your SymDump  for CICS release number.\nAction:\nNone.\nCASD60740\nSYMDUMP EXCLUSION SPECIFIED FOR THIS ABEND\nReason:\nSymDump  for CICS does not record this dump to the PROTDMP file because this abend code has been excluded from\nSymDump  for CICS processing. The exclusion is specified on the Initialization screen.\nAction:\nIf you want to capture this abend, enter the transaction SYMI to update the initialization parameters. Remove the\nappropriate abend code from the list of abend codes to be \"EXCLUDED.\"\nCASD60770\nSYMDUMP LSTACK getmain failure encountered\nReason:\nIN25COLD failed on a getmain request.\nAction:\nReview your CICS messages for any indications as to why this failure occurred. If none exists, contact SymDump  for\nCICS technical support.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1624dcfcc6bf-1", "text": "CICS technical support.\nCASD60780\nSYMDUMP TRACE getmain failure encountered\nReason:\nIN25COLD failed on a getmain request.\nAction:\n 1506", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a2ded83d5227-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReview your CICS messages for any indications as to why this failure occurred. If none exists, contact SymDump  for\nCICS technical support.\nCASD60790\nSYMDUMP STACK getmain failure encountered\nReason:\nIN25COLD failed on a getmain request.\nAction:\nReview your CICS messages for any indications as to why this failure occurred. If none exists, contact SymDump  for\nCICS technical support.\nCASD6107\nENQ Failure - PROTDMP file not available\nReason:\nThe PROTDMP file is in use by another user or system.\nAction:\nTry the request again later.\nCASD6120\nTry function later, dump in progress\nReason:\nThe PROTDMP file is busy capturing a dump and cannot process your request right now.\nAction:\nTry the request again later.\nCASD6291\nPROTDMP ENQ Failure - try function later\nReason:\nThe PROTDMP file is in use by another user or system.\nAction:\nTry the request again later.\nCASD6303\nFile not defined for UPDATE\nReason:\nThe PROTDMP file must be defined for update for the requested function.\nAction:\nModify the file definition.\nCASD6401\nCASD6401 ERROR DURING IN25COLD ATTACH\nReason:\nA request from IN25COKE program to attach IN25COLD program failed. IN25COKE terminates, product is no longer able\nto capture dumps.\nAction:\nAction: Save all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\n 1507", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7c6ba5dc9a94-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6403\nCASD6403 CRITICAL IN25COLD ERROR - PRODUCT NO LONGER USABLE\nReason:\nCritical error occurred in a SymDump  component resulting in the termination of IN25COLD program. SymDump  is no\nlonger usable and is not able to capture dumps.\nAction:\nRestart SymDump  product. If this doesn't help save all output, including the complete JESLOG and any dumps produced,\nand contact Broadcom Support .\nCASD6404\nCASD6404 POSSIBLE IN25COLD RESTARTING LOOP\nReason:\nIN25COKE recovery program restarted IN25COLD program too many times during a short period of time. There is a\npossibility of a loop in the restarting logic. IN25COLD is not going to be restarted again and IN25COKE terminates.\nProduct is no longer able to capture dumps.\nAction:\nRestart SymDump product. If this doesn't help save all output, including the complete JESLOG and any dumps produced,\nand contact Broadcom Support .\nCASD6405\nCASD6405 GENERAL IN25COKE ERROR DETECTED\nReason:\nA general error in IN25COKE recovery program has been detected. IN25COKE terminates, product is no longer able to\ncapture dumps.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD65090\nABENDED TASK xxxx STORAGE yyyy\nReason:\nThis message identifies the storage area (yyyy) that was captured by SymDump  for CICS and is currently being displayed\nwith the CORE facility of InterTest for CICS. The storage areas captured by SymDump  for CICS are listed in the following\ntable.\nAction:\nNone.\nSymDump  for CICS Tag Storage Block Area", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7c6ba5dc9a94-1", "text": "table.\nAction:\nNone.\nSymDump  for CICS Tag Storage Block Area\nAPE Pseudoactive Program Element Chain\nBMSE BMS Extension\nCLOT DB2 CICS Life of Task\nCOMM Commarea\nCPTE Current PPTE\nCPPT Current PPT\nCPRG Current Program\nCSA+ Common System Storage (for example, CSA, CSA WORK AREA)\n 1508", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0ab0d56f136c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCTA DLI DGB Control Transaction Area\nCWA CWA\nDGB DLI DBCTL CICS Global Block\nDLP DLI Interface Parameter List\nEIBS System Exec Interface Block\nEIBU User Exec Interface Block\nEISB Exec Interface Structure\nEISR Register Save Area of Application\nEIUS User Exec Interface Structure\nFCTE FCT Entry\nFIOA File I/O Area\nISB DLI Interface Scheduling Block\nJSTG Journal Control Area Storage\nKERH Current Kernel Error Header\nKERR Current Kernel Error Data\nKSTK Kernel Stack Entries\nLFCT FCT Entries List\nLLA Load List Area\nLLE Load List Entry\nOFPF Optional Features List\nPCAS Abend Associated Program Storage\nPCB DLI PCB\nPCBL DLI PCB List\nPCT Current PCT\nPICA Program Interrupt Save Area\nPLB Program Language Block\nPLCB Program Level Control Block\nPPT PPT Entry\nPPTE PPTE\nPRG Program Storage\nPSNT Pseudo Signon Table\nPST DLI PST\nPTA Program Transaction Area\nRDIN DB2 RDIIN\nRIET Resource Interface Element\nRSA Program Control Link Register Save Area\nRSB DLI Remote Scheduling Block\nSC24 CICS 24bit Subpool storage\nSC31 CICS 31bit Subpool storage\nSCD DLI System Content Directory\nSMDM Storage Manager Domain Control Block\n 1509", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b98eeb9132bc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSMX Transaction Storage Area\nSQLC DB2 SQLCA\nSU24 User 24bit Subpool storage\nSU31 User 31bit Subpool storage\nSYMD SymDump  for CICS storage currently in use (not captured as part\nof abended task storage)\nTACB Transaction Abend Control Block\nTAS Task Entry Storage\nTCA+ Task Related Storage (for example: STCA, UTCA, TWA, EIB, EIS)\nTCTE TCTTE\nTCTU TCTUA\nTIE DLI Transaction Interface Element\nTIOA Terminal Storage\nTWA Transaction Work Area\nTXD Static Transaction Definition\nTXN Transaction Storage\nUIB DLI User Interface Block\nCASD6701\nINITIALIZATION OF SYMDUMP DUMPFILE STARTING\nReason:\nThe SymDump  for CICS file initialization program is beginning execution.\nAction:\nNone.\nCASD6702\nNUMBER OF RECORDS IN SYMDUMP DUMPFILE IS: nnnnnn\nReason:\nThe SymDump  for CICS file initialization program has completed formatting the number of records specified.\nAction:\nNone.\nCASD6703\nINITIALIZATION TOOK PLACE AT HH:MM:SS ON MM/DD/YY\nReason:\nThe SymDump  for CICS file initialization program has completed formatting the file on the above time and date.\nAction:\nNone.\nCASD6704\nINITIALIZATION OF SYMDUMP DUMPFILE COMPLETED\nReason:\nThe SymDump  for CICS file initialization program has ended successfully.\n 1510", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d66441689997-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nNone.\nCASD6705\nINITIALIZATION OF SYMDUMP DUMPFILE TERMINATED\nReason:\nThe SymDump  for CICS file initialization program has ended execution because of an error condition.\nAction:\nSee additional messages for an explanation of the error.\nCASD6706\nINSUFFICIENT NUMBER OF RECORDS IN FILE \u2013 CHECK FILE DEFINITION\nReason:\nA minimum of six records must be defined in the SymDump  for CICS file.\nAction:\nCheck the file definition and increase the number of records specified for the file.\nCASD6707\nERROR IN GET PROCESSING\nReason:\nA read operation was not successful.\nAction:\nSee message CASD6709 for details of the error and determine the cause of the problem by checking the error codes in\nthe VSAM manual.\nCASD6708\nERROR IN PUT PROCESSING\nReason:\nA write operation was not successful.\nAction:\nSee message CASD6709 for details of the error and determine the cause of the problem by checking the error codes in\nthe VSAM manual.\nCASD6709\nR15: nn, FTNCD: nn, FDBK: nnn\nReason:\nAn error occurred during a read or write operation to the SymDump  for CICS file.\nAction:\nConsult the VSAM manual for an explanation of the error code (register 15) and the feedback code.\nCASD6710\nR15: nn, R0: nn\nReason:\nAn error occurred during VSAM MODCB processing.\nAction:\nConsult the VSAM manual for an explanation of the error codes.\n 1511", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "adde0ed5d72f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6711\nERROR IN MODCB PROCESSING\nReason:\nAn error occurred during VSAM MODCB processing.\nAction:\nSee message CASD6710 for details of the error and determine the cause of the problem by checking the error codes in\nthe VSAM manual.\nCASD6712\nERROR IN OPEN PROCESSING\nReason:\nOPEN processing of the SymDump  for CICS file was not successful.\nAction:\nSee message CASD6714 for details of the error and determine the cause of the problem by checking the error codes in\nthe VSAM manual.\nCASD6713\nWARNING IN OPEN PROCESSING\nReason:\nThe SymDump  for CICS file was opened successfully, but VSAM has issued a warning message.\nAction:\nSee message CASD6714 for details of the error and determine the cause of the problem by checking the error codes in\nthe VSAM manual.\nCASD6714\nRC: nn, ERRCODE: nnn\nReason:\nAn error or a warning has occurred during OPEN processing of the SymDump  for CICS file.\nAction:\nConsult the VSAM manual for an explanation of the error codes.\nCASD6715\nSuppress AP0001 dumps: < >\nReason:\nStates whether or not full AP0001 SVC dumps will be suppressed for ASRA and ASRB abends. N denotes dumping will\nconform to the specifications defined for your CICS system.\nAction:\nNone.\nCASD6716\nMessages to operator: < >\nReason:\nStates whether or not SymDump  for CICS informational message is written to the console when the dump or trace\nrequests are intercepted by SymDump  for CICS.\nAction:\nNone.\n 1512", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6233c359fe1f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6717\nSuppress CICS transaction dumps: < >\nReason:\nStates whether a transaction dump should be written to the CICS dump data set or suppressed by SymDump  for CICS.\nAction:\nNone.\nCASD6718\nCapture EXEC CICS dumps: < >\nReason:\nStates whether transaction dumps produced by EXEC CICS DUMP commands should be captured by SymDump  for\nCICS.\nAction:\nNone.\nCASD6719\nAutomatic purge of dumps: < >\nReason:\nStates whether automatic purging of dumps will occur during startup of SymDump  for CICS. Qualification for purging is\ndetermined by age (number of days to hold dumps), or the HOLD indicator setting on the Selection List menu.\nAction:\nNone.\nCASD6720\nDump only current program: < >\nReason:\nStates whether the dump should include just the active program or all linked and loaded programs.\nAction:\nNone.\nCASD6721\nNumber of days to hold dumps: < >\nReason:\nStates the number of days dumps should be retained.\nAction:\nNone.\nCASD6722\nDump select start date: < >\nReason:\nStates the date that the dump selection will start.\nAction:\nNone.\n 1513", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "143d8c1dce0b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD6723\nParameter error, default set: < >\nReason:\nThere was a parameter error on one of the input cards to IN25INST.\nAction:\nReview the default chosen. If it is not acceptable, correct the erroneous parameter and rerun the job.\nCASD6724\nInvalid Statement Discarded: < >\nReason:\nIN25INST could not recognize the parameter card it read and has discarded it.\nAction:\nReview the default chosen. If it is not acceptable, correct the parameter input and rerun the job.\nCASD6974\nPROTDMP ENQ Failure - try function later\nReason:\nThe PROTDMP file is in use by another user or system.\nAction:\nTry the request again later.\nCASD7126\nNO REQUESTS READ FROM SYSIN. CHECK INPUT.\nReason:\nThe SYSIN input file did not contain any input records.\nAction:\nEnsure that the SYSIN DD statement is followed by valid input.\nCASD7127\nBLANK STATEMENT FOUND. IGNORED.\nReason:\nAn input record did not contain any data and was skipped.\nAction:\nRemove the blank input record.\nCASD7128\nEXPECTING CONTINUATION. INVALID STATEMENT FOUND. THIS REQUEST BYPASSED.\nReason:\nThe previous input record ended with a comma and was not followed by additional keywords.\nAction:\nCheck input command syntax.\nCASD7129\nINVALID FUNCTION. THIS REQUEST BYPASSED.\nReason:\n 1514", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7c4746ee561d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe function requested was not INDEX or PRINT.\nAction:\nCheck input command syntax.\nCASD7130\nINVALID KEYWORD. THIS REQUEST BYPASSED.\nReason:\nThe keyword requested was not valid for the function specified.\nAction:\nCheck input command syntax.\nCASD7131\nSTATEMENT BYPASSED DUE TO PREVIOUS ERROR.\nReason:\nA continuation statement was not processed because of an error in the previous statement.\nAction:\nCheck input command syntax and correct the error.\nCASD7132\nINVALID KEYWORD VALUE LENGTH. THIS REQUEST BYPASSED.\nReason:\nThe length of the data specified for the keyword is not valid.\nAction:\nCorrect the data for the keyword.\nCASD7133\nINVALID FROMDATE VALUE SPECIFIED. THIS REQUEST BYPASSED.\nReason:\nThe FROMDATE parameter was not in the form yymmdd or the year, month or day values were not valid.\nAction:\nCorrect the data for the FROMDATE keyword.\nCASD7134\nINVALID FROMTIME VALUE SPECIFIED. THIS REQUEST BYPASSED.\nReason:\nThe FROMTIME parameter was not in the form hhmmss or the hour, minute or second values were not valid.\nAction:\nCorrect the data for the FROMTIME keyword.\nCASD7135\nINVALID KEYWORD REPETITION. THIS REQUEST BYPASSED.\nReason:\nThe same keyword was specified more than once for a given function.\nAction:\nCheck the input command and correct the error.\n 1515", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "57687ef6a2a3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD7136\nTODATE VALUE LESS THAN FROMDATE VALUE. ILLOGICAL. THIS REQUEST BYPASSED.\nReason:\nThe TODATE value must be greater than or equal to the FROMDATE value.\nAction:\nCorrect the data for the keyword in error.\nCASD7137\nTOTIME VALUE LESS THAN FROMTIME VALUE. ILLOGICAL. THIS REQUEST BYPASSED.\nReason:\nThe TOTIME value must be greater than or equal to the FROMTIME value when FROMDATE and TODATE are identical.\nAction:\nCorrect the data for the keyword in error.\nCASD7138\nINVALID TODATE VALUE SPECIFIED. THIS REQUEST BYPASSED.\nReason:\nThe TODATE parameter was not in the form yymmdd or the year, month or day values were not valid.\nAction:\nCorrect the data for the TODATE keyword.\nCASD7139\nINVALID TOTIME VALUE SPECIFIED. THIS REQUEST BYPASSED.\nReason:\nThe TOTIME parameter was not in the form hhmmss or the hour, minute or second values were not valid.\nAction:\nCorrect the data for the TOTIME keyword.\nCASD7140\nNO RELEVANT DATA ON SYMDUMP FILE FOR THIS REQUEST.\nReason:\nNo dumps were found on the SymDump  for CICS file that corresponded to the criteria specified.\nAction:\nCheck the criteria and alter specifications, if desired.\nCASD7141\nMUTUALLY EXCLUSIVE KEYWORDS SPECIFIED. THIS REQUEST BYPASSED.\nReason:\nThe keyword ALL cannot be specified with any other keywords.\nAction:\nSpecify search criteria or ALL but not both.\nCASD7142\nINSUFFICIENT VIRTUAL STORAGE \u2013 PROCESSING TERMINATED.\nReason:\n 1516", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "53126bbb0878-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nA request for virtual storage could not be satisfied.\nAction:\nSpecify a larger region for this job step and rerun job.\nCASD7145\nERROR IN DUMP PRINTING PROGRAM. SEE JOB LOG. PROCESSING TERMINATED.\nReason:\nRequired DD statements are missing.\nAction:\nCheck the job log and installation instructions for a list of the required DD statements.\nCASD7146\nCA SYMDUMP \u2013 ABENDING PROGRAM: xxxxxxxx\nReason:\nA hard copy of a transaction dump produced by SymDump  for CICS was requested. This message indicates which\nprogram produced the abend/dump.\nAction:\nNone.\nCASD7150\nVSAM ERROR. FUNCTION = xxxxx RETURN CODE = 99 ERROR CODE = 999. THIS REQUEST BYPASSED.\nReason:\nA VSAM error occurred for the function xxxxx.\nAction:\nCheck the VSAM manual for an explanation of the return code and error code for the function specified.\nCASD7300\nBatch Utility has started\nReason:\nThe batch utility has started.\nAction:\nNone.\nCASD73010\nBatch Utility has ended\nReason:\nThe batch utility has ended.\nAction:\nNone.\nCASD73020\nBatch Utility is terminated\nReason:\nThe batch utility was terminated due to a previous error. See previous message.\nAction:\nCorrect the error and rerun the batch utility.\n 1517", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d7a24fc1ae01-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD73050\nNo valid DSN name was used\nReason:\nAn invalid name specifying the data set name was used in the DSN command.\nAction:\nCorrect the data set name and rerun the batch utility.\nCASD73060\nNo valid ODSN name was used\nReason:\nAn invalid name specifying the data set name was used in the ODSN command.\nAction:\nCorrect the data set name and rerun the batch utility.\nCASD7307\nWrong DATE was entered\nReason:\nThe date was entered in the wrong format or the value is not valid.\nAction:\nCorrect the date using format MM/DD/YYYY and rerun the batch utility.\nCASD73080\nWrong KEYWORD or PARAMETER was used\nReason:\nThe batch utility did not recognize the command. Either the wrong command was used or positional parameters (or\nvalues) were wrong.\nAction:\nCheck the syntax of the command, correct it, and rerun the batch utility.\nCASD73090\nPROTDMP corruption\nReason:\nThe PROTDMP size does not match the size specified in the PROTDMP header.\nAction:\nCheck the VSAM data set size and value in the PROTDMP header. Manually correct the value in the PROTDMP header.\nCASD7310\nDataset is not available or does not exist\nReason:\nThe data set used in the DSN or ODSN commands does not exist or the batch utility cannot access it.\nAction:\nCheck the system messages in the joblog. Check the data set name and its status, and rerun the batch utility. If the\nproblem persists, contact the system programmer.\n 1518", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d5cb7fc881ac-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD7311\nError in accessing dataset\nReason:\nThe data set name is valid. However, the batch utility cannot work with it.\nAction:\nCheck the system messages in the joblog, correct the situation, and rerun the batch utility. If the problem persists, contact\nthe system programmer.\nCASD7312\nError during READ dataset\nReason:\nAn unpredictable error occurred while reading the data set. The batch utility is not able to read it.\nAction:\nCheck the system messages in the joblog, correct the situation, and rerun the batch utility. If the problem persists, contact\nthe system programmer.\nCASD7315\nDump header has changed\nReason:\nWhile processing the requested action, another job has modified the dump.\nAction:\nCheck the PROTDMP content. If still required, repeat the action.\nCASD7321\nCannot COPY, source and destination are the same\nReason:\nThe PROTDMP source and destination are the same. This is not allowed for the COPY command.\nAction:\nNone.\nCASD7322\nDump CODE suppressed, not copied\nReason:\nThe dump code of the copied dump is suppressed in the PROTDMP destination.\nAction:\nTo copy the dump, use the OPT command, change the suppressing option in the destination PROTDMP, and rerun the\nbatch utility.\nCASD7323\nDump CODE excluded, not copied\nReason:\nThe dump code of the copied dump is excluded in the PROTDMP destination.\nAction:\nTo copy the dump, use the OPT command, change the excluding option in the PROTDMP destination, and rerun the\nbatch utility.\n 1519", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "381db18c2f07-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD7324\nNo free space, dump not copied\nReason:\nThere is no space in the PROTDMP destination for storing another dump.\nAction:\nDelete unneeded dumps in the PROTDMP destination, and repeat the action. Space depends on the deleted dump's size.\nCASD7325\nMax number of dumps reached, dump not copied\nReason:\nThe maximum number of possible stored dumps in the PROTDMP destination was reached. No other dump could be\nstored.\nAction:\nDelete unneeded dumps in the PROTDMP destination, and repeat the action. Space depends on the deleted dump's\ncount.\nCASD7330\nDump is locked already\nReason:\nThe LOCK function was requested for a dump that is already locked.\nAction:\nNone.\nCASD7335\nDump is not locked\nReason:\nThe UNLOCK function was requested for a dump that is not locked.\nAction:\nNone.\nCASD7340\nDump is deleted already\nReason:\nWhile processing the DELETE command, another job has already performed the same action.\nAction:\nNone.\nCASD7341\nNothing found to DELETE\nReason:\nThere are no dumps to delete.\nAction:\nNone.\n 1520", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3ef3dde086e7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCASD7342\nDump is LOCKed, not deleted\nReason:\nThe selected dump for a delete action is locked.\nAction:\nUnlock the dump using the UNLOCK command, and use the DELETE command again.\nCASD7350\nBad VALUE used, command ignored\nReason:\nA value used in a parameter of the command is not valid.\nAction:\nCorrect the value and rerun the batch utility.\nCASD7351\nBad COMMAND used, command ignored\nReason:\nThe requested command is not valid.\nAction:\nCorrect the command and rerun the batch utility.\nCASD7352\nCannot add abend code, already on the list\nReason:\nThe specified abend code cannot be added to the exclusion list because the code is already on the list.\nAction:\nNone.\nCASD7353\nCannot add abend code, list is full\nReason:\nThe specified abend code cannot be added to the exclusion list because the list is full.\nAction:\nRemove abend codes which are no longer needed or use a wildcard to reduce the number of codes on the list. Rerun the\nbatch utility.\nCASD7354\nCannot delete abend code, code not found\nReason:\nThe specified abend code cannot be removed from the exclusion list because the code is not found.\nAction:\nNone.\nCASD7507\nTRANSACTION xxxx (TASK nnnnn) HAS TIMED OUT DURING SCREEN CAPTURE\n 1521", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d2c097bab4f1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nDuring dump capture, SymDump  attempts to read the last screen image from the terminal. If the terminal does not\nrespond within 16 seconds, the last screen capture times out and this informational message displays on the console log.\nThe last screen image will not have been captured for the dump.\nAction:\nDetermine the reason the terminal was not responding, and resolve the problem so that future dumps can be captured\ncompletely.\nCASD8981\nLine commands D, H, and R are valid for local files only\nReason:\nDelete, Hold, and Release functions are not valid for a remote file.\nAction:\nDump the PROTDMP file as local or enter the commands in another region.\nCASD7431\nFile Information Block request failure in IN25SYMZ\nReason:\nDuring dump capture, program IN25SYMZ attempted to capture the File Information Block, but failed.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7432\nTransaction Information Block request failure in IN25SYMZ\nReason:\nDuring dump capture, program IN25SYMZ attempted to capture the Transaction Information Block, but failed.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7433\nLast SQL request failure in IN25SYMZ\nReason:\nDuring dump capture, program IN25SYMZ attempted to capture Last SQL information, but failed.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7434\nTerminal Information Block request failure in IN25SYMZ\nReason:\nDuring dump capture, program IN25SYMZ attempted to capture the Terminal Information Block, but failed.\nAction:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d2c097bab4f1-1", "text": "Action:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7435\nGeneral request failure in IN25SYMZ\nReason:\n 1522", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "85b9673aeeb8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDuring dump capture, program IN25SYMZ failed because of unknown reason. IN25SYMZ resumes processing.\nAction:\nAction: Save all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7436\nIN25SYMZ unknown failure\nReason:\nDuring dump capture, program IN25SYMZ failed because of unknown reason. IN25SYMZ terminates.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7437\nIN25SYMZ failure, missing COMMAREA\nReason:\nDuring dump capture, program IN25SYMZ failed because of missing COMMAREA. IN25SYMZ terminates.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7438\nIN25SYMZ failure, missing EXCAAREA\nReason:\nDuring dump capture, program IN25SYMZ failed because of missing EXCAAREA. IN25SYMZ terminates.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nCASD7439\nIN25SYMZ is requesting a dump (SDUMP)\nReason:\nSymDump  for CICS program IN25SYMZ has detected a problem and has requested an SDUMP of the region.\nAction:\nSave all output, including the complete JESLOG and any dumps produced, and contact Broadcom Support .\nInterTest for CICS Online Help Messages\nThe messages in this section are produced by InterTest for CICS and can be viewed in the online Help facility.\nCAIN0001\nCKPT scheduling failed\nReason:\nCheckpoint processing was unable to schedule the next checkpoint.\nAction:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "85b9673aeeb8-1", "text": "Reason:\nCheckpoint processing was unable to schedule the next checkpoint.\nAction:\nCheck your CICS console for temporary storage errors. Correct any errors or if there are none, contact Broadcom\nSupport .\nCAIN0002\nCKPT function abnormally terminated\n 1523", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2c7e54f193a5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nAn abend occurred during checkpoint processing.\nAction:\nCollect the transaction dump and contact Broadcom Support .\nCAIN0003\n(*) not in FCT\nReason:\nThe file is not defined to CICS or has not been installed.\nAction:\nDefine and install the file.\nCAIN0004\ninvalid processing options in FCT for (*)\nReason:\nThe file (*) has the wrong service options specified for the file.\nAction:\nCorrect the file's options, and resubmit the request.\nCAIN0005\nVSAM err code=(*) return code= (*) file= (*)\nReason:\nAn error occurred while accessing the checkpoint file.\nAction:\nEnsure that the file is accessible. For more information on the error and return codes, see the VSAM Programmer's\nGuide .\nCAIN0006\ndynamic open failure code = (*) file = (*)\nReason:\nInterTest for CICS was unable to open the file.\nAction:\nEnsure that the file is accessible. For more information on the error and return codes, see the VSAM Programmer's\nGuide .\nCAIN0007\nCICS error = (*) detected in file (*)\nReason:\nAn error occurred while accessing the checkpoint file.\nAction:\nEnsure that the file is accessible. For more information on the error and return codes, see the VSAM Programmer's\nGuide .\nCAIN0008\nCKPT function abnormally terminated\nReason:\n 1524", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "871cea44807e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAn abend occurred during checkpoint processing.\nAction:\nCollect the transaction dump and contact Broadcom Support .\nCAIN0009\n(*) file space exhausted\nReason:\nThe checkpoint file has insufficient space to hold all the requests.\nAction:\nIncrease the size of the checkpoint file.\nCAIN0010\nscheduling for CA InterTest CKPT has failed\nReason:\nCheckpoint processing was unable to schedule the next checkpoint.\nAction:\nCheck your CICS console for temporary storage errors. Correct any errors or, if there are none, contact Broadcom\nSupport .\nCAIN0011\nCKPT function completed at (*)\nReason:\nCheckpoint completed successfully.\nAction:\nNone.\nCAIN0201\nRECEIVING FIELD HAS BEEN CHANGED AS SHOWN\nReason:\nThe MOVE= command was performed and the result is displayed on the screen.\nAction:\nNone.\nCAIN0202\nPROGRAM IS ASSEMBLER - REQUESTS DISREGARDED\nReason:\nThe MOVE= command was entered for an Assembler program that is supported for COBOL and PL/I only.\nAction:\nNone.\nCAIN0203\nXXXXXXXX USAGE-TYPE NOT SUPPORTED\nReason:\nThe USAGE-TYPE, for the data-item xxxxxxxx, was not valid. The MOVE= command can only handle data-items that are\ndefined as COMP, COMP-3, GROUP, DISPAY-NUMERIC, or DISPLAY.\nAction:\n 1525", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "caeea041fb96-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNone.\nCAIN0204\nFIGURATIVE CONSTANT ALL FORMAT ERROR\nReason:\nA MOVE ALL xx...' command was found to be in error. The 'ALL' option may only be a FIGURATIVE CONSTANT, like\nZERO or SPACES, or a non-numeric literal.\nThe format is the same as is described in your COBOL APPLICATION PROGRAMMING LANGUAGE REFERENCE\nmanual.\nAction:\nCorrect command and resubmit.\nCAIN0205\nLITERAL FOR ALL KEYWORD IS MISSING FROM COMMAND\nReason:\nA MOVE ALL xx...' command was found to be in error. The 'ALL' option may only be a FIGURATIVE CONSTANT, like\nZERO or SPACES, or a non-numeric literal.\nThe format is the same as is described in your COBOL APPLICATION PROGRAMMING LANGUAGE REFERENCE\nmanual.\nAction:\nCorrect command and resubmit.\nCAIN0206\nSENDING FIELD DOES NOT CONTAIN A VALID NUMERIC VALUE\nReason:\nWhen using a 'MOVE data1 TO data2' command format, the 'data2' field was defined as numeric but the'data1' was not.\nAction:\nCorrect command and resubmit.\nCAIN0207\nNUMERIC LITERAL IS NON-NUMERIC\nReason:\nA numeric literal was found to contain non-numeric characters.\nAction:\nCorrect command and resubmit.\nCAIN0208\nSENDING FIELD CONTAINS MORE THAN 18 DIGITS\nReason:\nThe sending field, a data item or numeric literal, was found to be longer than 18 numeric characters. This is a COBOL\nrestriction.\nAction:\nCorrect command and resubmit.\nCAIN0209\nUNPAIRED QUOTES AROUND LITERAL\n 1526", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6693212b92af-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nA literal was entered that did not contain an even number of quotation marks.\nAction:\nCorrect command and resubmit.\nCAIN0210\nLITERAL IS GREATER THAN 120 CHARACTERS\nReason:\nA literal was entered that contains more than 120 characters. This is a COBOL restriction.\nAction:\nCorrect command and resubmit.\nCAIN0211\nA NULL LITERAL HAS BEEN ENTERED\nReason:\nA literal was entered that contains only two (2) quotation marks.\nAction:\nCorrect command and resubmit.\nCAIN0212\nINDEXING FORMAT IS INCORRECT\nReason:\nThe SUBSCRIPT or INDEX format that was entered for a data item was found to be invalid.\nAction:\nCorrect command and resubmit.\nCAIN0213\nKEYWORD TO IS MISSING FROM COMMAND\nReason:\nThe MOVE= command requires the keyword TO. The format of the MOVE= command is the same as described in your\nCOBOL APPLICATION PROGRAMMING LANGUAGE MANUAL.\nAction:\nCorrect command and resubmit.\nCAIN0214\nCOMMAND IS INCOMPLETE\nReason:\nThe MOVE= command was found to be incomplete. This may occur if the following command was entered: MOVE\nSPACES TO\nAction:\nCorrect command and resubmit.\nCAIN0215\nRECEIVING FIELD NOT CONTAINED WITHIN YOUR STORAGE\nReason:\nThe receiving data item did not reside in an area of storage that was owned by the task.\n 1527", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f8e8dd7a0eb6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nNone.\nCAIN0216\nxxxxxx CANNOT BE MOVED TO A FIELD DEFINED AS NUMERIC\nReason:\nThe figurative literal, xxxxxx, cannot be moved to a data item that is described as numeric.\nAction:\nCorrect command and resubmit.\nCAIN0217\nHIGH-ORDER TRUNCATION MIGHT HAVE OCCURRED\nReason:\nA numeric receiving data item was smaller than the sending data item. This condition may cause a loss of high-order data.\nAction:\nNone.\nCAIN0218\nLOW-ORDER TRUNCATION MIGHT HAVE OCCURRED\nReason:\nA non-numeric receiving data item was smaller than the sending data item. This condition may cause a loss of low-order\ndata.\nAction:\nNone.\nCAIN0219\nMOVE PERFORMED WITHOUT DATA CONVERSION\nReason:\nOne of the data items was found to be a GROUP item. When a GROUP item is found, the data is moved without any\nconversion.\nAction:\nNone.\nCAIN0220\nSYMBOLIC RETRIEVAL PROGRAM ACCESS FAILURE\nReason:\nThe InterTest for CICS program, IN25SGET, was either not found in the PPT or was diagnosed disabled.\nAction:\nCorrect condition.\nCAIN0221\nNOTAUTH CONDITION - RESOURCE LEVEL SECURITY FAILED FOR \"(*)\"_\nReason:\nThis transaction is not authorized to use the resource specified.\nAction:\nAdjust your security definitions, and resubmit the request.\n 1528", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5e05ef2f1b35-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0222\nCAIN0222 Invalid data or invalid numeric value for data type.\nReason: You entered invalid data or an invalid numeric value for the data type. For example, you entered a zero or a\nnegative value in a numeric index field.\nAction:  \nCorrect the data or press ENTER to redisplay screen.\nCAIN0401\nCOMMAND TEXT EXCEEDS MAXIMUM LENGTH\nReason:\nThe input command exceeded a maximum of 72 characters. This normally occurs when a CORE command is entered by\novertyping an existing display.\nAction:\nIf the error is caused by overtyping an existing display then simply place the cursor at the first character that follows the\nCORE command, then use the ERASE EOF key and resubmit the command.\nCAIN0402\nAN AICA HAS OCCURRED\nReason:\nWhile processing the CORE request an AICA occurred and was recovered.\nAction:\nNone.\nCAIN0403\nAREA TO BE CHANGED RESIDES OUTSIDE OF CICS\nReason:\nThe area that is being changed does not reside within the CICS address space.\nAction:\nCheck your previous CORE commands to see how this address was generated and, if possible, correct and retry the\nchange operation.\nCAIN0404\nINVALID ADDRESS/OFFSET\nReason:\nAn ADDRESS or OFFSET was requested that was greater than 8 characters long, or the Address Offset contained a non-\nhexadecimal character.\nAction:\nCorrect and resubmit command.\nCAIN0405\nINVALID KEYWORD\nReason:\nThe argument that followed an '=' sign was not found in the list of allowable keywords.\nAction:\nCorrect and resubmit command.\n 1529", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "21de7712b332-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0406\nREQUESTED IDENTIFICATION NOT FOUND\nReason:\nThe item requested could not be found in the area specified.\nAction:\nCorrect and resubmit command.\nCAIN0407\nLOAD MACRO FAILED, PPT ENTRY IS DISPLAYED\nReason:\nA =LOAD=program request, in an XA environment, resulted in a failure. The CORE program displays the program's PPT\nentry.\nAction:\nNone.\nCAIN0408\nSYNTAX ERROR\nReason:\nWhile editing a CORE request, an error in the syntax was found.\nAction:\nCorrect and resubmit request.\nCAIN0409\nINVALID OPERATION\nReason:\nThe request could not be performed.\nAction:\nCorrect and resubmit request.\nCAIN0410\nSPECIFIED DATA AREA IS EITHER STORE OR FETCH PROTECTED\nReason:\nWhile trying to display or change a data area, a PROTECTION EXCEPTION occurred.\nAction:\nCorrect and resubmit request.\nCAIN0411\nCURRENT USE COUNT IS 0 FOR PROGRAM\nReason:\nWhen trying to do a =DLTE=program request, the program's use count was found to be 0.\nAction:\nNone.\nCAIN0412\nPROGRAM NOT IN MAIN STORAGE\n 1530", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6c8e931ed442-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nThe program that was specified in an =PGM=program request was not loaded into CICS.\nAction:\nChange the request to =LOAD=program and resubmit.\nCAIN0413\nREQUESTED AREA WAS NOT FOUND\nReason:\nThe area, that was requested, was not found.\nAction:\nNone.\nCAIN0414\nINIT= IS INVALID\nReason:\nThe INIT= field, for a =GETM request, was not within the range of X'00' through X'FF'.\nAction:\nCorrect and resubmit.\nCAIN0415\nINVALID COMPARATOR CODE\nReason:\nThe comparator code, found in a =IF request, was not valid.\nAction:\nCorrect and resubmit.\nCAIN0416\nINVALID IF STATEMENT\nReason:\nThe =IF request was found to be invalid.\nAction:\nCorrect and resubmit.\nCAIN0417\nTASK NOT AT BREAKPOINT\nReason:\nA CORE request was made that requires a task at a breakpoint and one was not found.\nAction:\nNone.\nCAIN0418\nSTORAGE NOT AVAILABLE, DL1=NO SPECIFIED IN SIT\nReason:\nNo DL/1 is available in the CICS region and an attempt was made to display a DL/1 storage area.\nAction:\nNone.\n 1531", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "778756c27b3b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0419\nTASK NUMBER UNKNOWN\nReason:\nThe task number, which is being used, was not found in CICS.\nAction:\nVerify task number using a CSMT TAS or CEMT I TAS command.\nCAIN0420\nHEX=xxxxxxxx DEC=yyyyyyyyyy\nReason:\nAs a result of a CALC command, both the HEXadecimal value (xxxxxxxx) and a DECimal value (yyyyyyyyyy) are\ndisplayed for the function.\nAction:\nNone.\nCAIN0421\nSTORAGE NOT AVAILABLE\nReason:\nThe storage, requested by a =GETM request, could not be obtained.\nAction:\nNone.\nCAIN0422\nPASSWORD REJECTED\nReason:\nThe password entered, in response to the CORE000 message' was incorrect.\nAction:\nEnter the correct password.\nCAIN0423\nxxxxx BYTES CHANGED AS SHOWN AT yyyyyyy\nReason:\nAfter a =CHG request has been processed, the number of bytes changed (xxxxx) and the address of the first byte\nchanged (yyyyyyy) is shown.\nAction:\nNone.\nCAIN0425\nILLEGAL USAGE OF SYMBOLIC NAME\nReason:\nA symbolic name has been used in a CORE request that cannot support a symbolic name.\nAction:\nCorrect and resubmit.\n 1532", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "40d95f302ef4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0426\nNOT VERIFIED\nReason:\nA verification request, =VER, has resulted in a non-match condition.\nAction:\nCorrect and resubmit.\nCAIN0427\nDATA VERIFIED\nReason:\nA verification request, =VER, has resulted in a match condition.\nAction:\nNone.\nCAIN0428\nDUMP WRITTEN TO CICS DUMP DATA SET\nReason:\nA =DUMP request has been completed with the dump being written to the CICS dump data set.\nAction:\nNone.\nCAIN0429\nPGM RELOAD=YES, NOT LOADED WHEN MONITORED\nReason:\nThe program to be loaded, by a LOAD=program request, was found to be at a breakpoint and the program was defined\nwith a RELOAD=YES option.\nAction:\nNone.\nCAIN0430\nA COPY OF PGM, RELOAD=YES, USED IN ADDRESSING\nReason:\nA =DUMP request has been completed with the dump being written to the CICS dump data set.\nAction:\nNone.\nCAIN0431\nRESULT IS TRUE\nReason:\nA true condition was found in response to an =IF request.\nAction:\nNone.\nCAIN0432\nRESULT IS NOT TRUE\n 1533", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "84076004db91-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nA false condition was found in response to an =IF request.\nAction:\nNone.\nCAIN0433\nPROGRAM IS DISABLED\nReason:\nThe program, specified in a =LOAD=program request was found to be disabled.\nAction:\nUse CSMT or CEMT to enable the program and then resubmit the request.\nCAIN0434\nINCOMPATIBLE SCREEN SIZE\nReason:\nDuring the processing of a =SSCR request, the terminal being used for the CORE transaction is not in the same mode as\nthe terminal used for the breakpoint. For example - the user's program displayed a screen on a MODEL 5 terminal and is\nnow trying to display it on a MODEL 2 terminal.\nAction:\nNone.\nCAIN0435\nTASK POSTED FOR ASRA\nReason:\nIn response to a =PURGE request, the task has been terminated with an ASRA condition.\nAction:\nNone.\nCAIN0436\nCOMPARISON LENGTHs MISSING\nReason:\nDuring the processing of a =IF request, it was found that either one or both length fields were missing.\nAction:\nCorrect request and resubmit.\nCAIN0437\nCOMPARISON LENGTHS NOT EQUAL\nReason:\nDuring the processing of a =IF request, it was found that the length fields were not the same length.\nAction:\nCorrect request and resubmit.\nCAIN0438\nMON/NOM OPTIONS ARE SET FOR PROG - DELETE DENIED.\nReason:\nThe program to be deleted contains MON or NOM monitoring options.\n 1534", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9edb2ff49c23-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nRemove the MON and/or NOM options and retry the request.\nCAIN0439\nCOMPARE LENGTHs ARE GREATER THAN MAX FOR DATA TYPE\nReason:\nDuring the processing of a =IF request, it was found that either one or both length fields were greater than the maximum\nfor the data type. For example - a maximum of 16 bytes is permitted for packed (comp-3) data.\nAction:\nCorrect request and resubmit.\nCAIN0440\nINVALID KEYWORD FOUND IN \"KEEP\" REQUEST\nReason:\nThe keyword specified is not valid for a KEEP request.\nAction:\nThe keyword cannot be used.\nCAIN0441\nLITERAL IS TOO LONG\nReason:\nA literal was entered that was greater than 50 characters long, which is the maximum for one request.\nAction:\nCorrect request and resubmit.\nCAIN0442\nPL/I PROCEDURE NAME NOT FOUND.\nReason:\nThe PL/I procedure name could not be found.\nAction:\nCorrect the procedure name and retry the request.\nCAIN0443\nOFFSET IN PL/I MAIN CSECT IS (*)\nReason:\nInformational.\nAction:\nNone.\nCAIN0444\nINVALID HEXADECIMAL LITERAL\nReason:\nA literal, specified in an X'....' format, was found to contain non-hexadecimal characters or there were an odd number of\ncharacters specified.\nAction:\nCorrect request and resubmit.\n 1535", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aafbbf2bc147-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0445\nINVALID CHARACTER LITERAL\nReason:\nA literal, specified in a C'....' format, was found to contain characters that were less than a blank, X'40'.\nAction:\nCorrect request and resubmit.\nCAIN0446\nINVALID PACKED DECIMAL LITERAL\nReason:\nA literal, specified in a P'....' format, was found to contain non-numeric characters and/or the first character was no a '+' or\n'-'.\nAction:\nCorrect request and resubmit.\nCAIN0447\nINVALID HALFWORD LITERAL\nReason:\nA literal, specified in a H'....' format, was found to contain non-numeric characters and/or the first character was not a '+' or\n'-'.\nAction:\nCorrect request and resubmit.\nCAIN0448\nINVALID FULLWORD LITERAL\nReason:\nA literal, specified in a F'....' format, was found to contain non-numeric characters and/or the first character was not a '+' or\n'-'.\nAction:\nCorrect request and resubmit.\nCAIN0449\nCommand invalid when viewing past data values.\nReason:\nThe specified command is not valid while navigating the statement trace table with the DATAMON option in effect.\nAction:\nSpecify a valid command.\nCAIN0450\nINDIRECT ADDRESSING IS INVALID FOR THIS KEYWORD\nReason:\nThe keyword, specified by a keyword or %keyword request, may not be used for indirect addressing.\nAction:\nCorrect request and resubmit.\n 1536", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9672b304e3c7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0451\nMODEL TCT ENTRY FOUND FOR REMOTE TERMINAL ID\nReason:\nThe terminal specified by a TERM=termid request was found to a model TCT entry.\nAction:\nNone.\nCAIN0452\nFIELD DOES NOT CONTAIN A VALID PACKED DECIMAL (COMP-3) VALUE\nReason:\nThe displayed COBOL data item, which was defined as a COMP-3 field, was found to contain an invalid value.\nAction:\nNone.\nCAIN0453\nttttttttt - VALUE OF FIELD = xxxxxxxxx\nReason:\nThe decimal value, xxxxxxxxx, is displayed for a PL1 data item which was defined as ttttttttt.\nAction:\nNone.\nCAIN0454\n=MOVEIN COMMAND MISSING LENGTH (L=) PARAMETER\nReason:\nThe length parameter, L=, was not found while processing a =MOVEIN request.\nAction:\nCorrect request and resubmit.\nCAIN0455\n=MOVEIN COMMAND MISSING FROM= PARAMETER\nReason:\nThe from parameter, FROM=, was not found while processing a =MOVEIN request.\nAction:\nCorrect request and resubmit.\nCAIN0456\nLENGTH FIELD (L=) IS ZERO\nReason:\nThe length parameter, L=, was found to contain a zero value.\nAction:\nCorrect request and resubmit.\nCAIN0457\nLENGTH FIELD (L=) IS GREATER THAN MAXIMUM ALLOWED\nReason:\n 1537", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "56dda54157a9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe length parameter, L=, was found to contain a value, which was greater than the maximum permitted.\nAction:\nCorrect request and resubmit.\nCAIN0458\nxxxxxxxx NOT FOUND IN PPT OR IS DISABLED\nReason:\nThe program, xxxxxxxx, specified in the CORE request was either not found in the PPT or diagnosed disabled.\nAction:\nUse CSMT or CEMT to locate the program, if found, enable the program and resubmit request.\nCAIN0459\nUNABLE TO START ISER TASK - TRANSACTION NOT DEFINED\nReason:\nNo CORE commands can be processed.\nAction:\nEnsure that the ISER transaction is properly installed.\nCAIN0460\nUNABLE TO START ISER TASK - TRANSACTION IS NOT ENABLED_\nReason:\nNo CORE commands can be entered.\nAction:\nEnable the ISER transaction.\nCAIN0461\nTO MANY INDEX NAMES (MAX = 3)\nReason:\nToo many subscripts or indexes were found when processing a ='data-name(x1,..,xn)' request. A maximum of 3 levels\nmay be specified. This is a COBOL restriction.\nAction:\nCorrect request and resubmit.\nCAIN0462\nFIRST SYMBOLIC REFERENCE IS NOT A EQUATED TO A REGISTER\nReason:\nThe first symbolic reference, in a symbolic request for an assembled data item, was not a register.\nAction:\nCorrect request and resubmit.\nCAIN0463\nINVALID NUMERIC VALUE FOR DATA TYPE\nReason:\nWhen changing data, by over-typing, in the Structure Display Format area, an invalid numeric value was entered for the\ndata type. This can occur by entering a numeric value that is too large for the data type. For example, the maximum value", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "56dda54157a9-1", "text": "an S9(4) COMP field can hold is +32767. The screen is restored to its original condition.\n 1538", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4f2618b837d5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nRetype your change.\nCAIN0464\nINVALID USE= SYNTAX - FORMAT NOT = MODULE.NAME OR *.NAME\nReason:\nA =USE request was not specified correctly.\nAction:\nCorrect and resubmit.\nCAIN0465\nINVALID CHARACTER ENTERED OR A FIELD WAS ERASED\nReason:\nWhen changing data, by over-typing, in the hexadecimal area, a non-hexadecimal character was entered or an ERASE\nEOF key was hit. The screen is restored to its original condition.\nAction:\nRetype your change.\nCAIN0466\nAT FIRST ENTRY IN STRUCTURE\nReason:\nThe first data item, displayed for a structure request, is the first item in that structure.\nAction:\nNone\nCAIN0467\nAT LAST ENTRY IN STRUCTURE\nReason:\nThe last data item displayed, for a structure request, is the last item in that structure.\nAction:\nNone\nCAIN0468\nSTRUCTURE DISPLAY FORMAT (SDF) UNAVAILABLE\nReason:\nPrior to InterTest 6.2, Assembler modules did not carry the data type on the symbolic file. Because of this, the format of\nthe data cannot be determined. The data displays in the hexadecimal / character format.\nAction:\nReassemble the program using the InterTest 6.2 version of IN25SYMA.\nCAIN0469\nPROGRAM CANNOT BE DELETED\nReason:\nThe program is being used by some task.\nAction:\nTerminate the task holding the resource and retry this request.\n 1539", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "940aec76f914-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0470\nCANNOT DIVIDE BY 0\nReason:\nA division by zero request was made in a CALC function.\nAction:\nCorrect request and resubmit.\nCAIN0471\nPRESS CLEAR TO SEE NEXT ITEM OR PF3 TO CANCEL DISPLAYS\nReason:\nThis message appears only when multiple display requests are made from the source code viewing screen.\nAction:\nIf you wish to see the data item requested, then press the Clear key. If you wish to cancel the remaining display requests,\npress PF3.\nCAIN0472\nINVALID DFHAID ENTERED\nReason:\nThe AID byte entered is unrecognizable. This is a logic error in program IN25CORE.\nAction:\nCollect the dump and contact Broadcom Support .\nCAIN0473\nGETM, CLASS=TERM, IS INVALID FOR THIS TASK\nReason:\nThe task does not have an associated terminal.\nAction:\nNone.\nCAIN0474\nLOWER CASE CHARS FOUND - PRESS PF9 AND RE-ENTER CHANGES_\nReason:\nLower case characters were found in the line being modified, but the terminal is in upper case mode.\nAction:\nPress PF9 and re-enter the changes.\nCAIN0475\nNO STRUCTURE INFORMATION FOR A FIND= REQUEST\nReason:\nThe name specified does not exist in the structure.\nAction:\nCorrect the name and retry the request.\nCAIN0476\nFIND= REQUEST HAS WRAPPED\n 1540", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0a04acb519d5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nThe name requested occurs before the first name currently displayed.\nAction:\nNone.\nCAIN0478\n(*) FIELD CONTAINS INVALID PACKED DATA\nReason:\nA field defined as PACKED contains non-PACKED data.\nAction:\nCorrect the field.\nCAIN0479\nKEYWORD NOT SUPPORTED IN THIS RELEASE OF CICS\nReason:\nThe keyword is not supported by the CICS release you are using.\nAction:\nNone.\nCAIN0480\nABEND OCCURRED IN PROGRAM (*) AT OFFSET (*)\nReason:\nThe ABEND occurrence in the Kernel Error Data Block points to the program at the stated offset.\nAction:\nUse this information and the register contents to debug the abend.\nCAIN0481\nNO PROGRAM NAME FOUND MATCHING STORAGE ADDRESS\nReason:\nThe address does not occur in any program in the CICS region.\nAction:\nNone.\nCAIN0482\nADDRESS POINTS TO PROGRAM (*) AT OFFSET (*)\nReason:\nThe address specified in the WHERE request points to the program at the offset specified.\nAction:\nNone.\nCAIN0483\nINVALID OPERATION FOR SymDump\nReason:\nThe keyword requested is invalid under SymDump  for CICS.\nAction:\nNone.\n 1541", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ae762fe25221-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0484\nCORE/KEEP WINDOW REFERENCED PROTECTED CSA ABEND SUPPRESSED_\nReason:\nThe KEEP window was requested to display a fetch-protected area. This area cannot be displayed.\nAction:\nCorrect the KEEP window request.\nCAIN0485\nInterTest RELEASE (*) NOT COMPATIBLE WITH CICS RELEASE (*)_\nReason:\nThe wrong C InterTest for CICS release is installed in your CICS region.\nAction:\nInstall the proper InterTest for CICS release.\nCAIN0486\nCORE FACILITY TERMINATED\nReason:\nThe CORE facility was terminated.\nAction:\nNone.\nCAIN0487\nNOTAUTH CONDITION - RESOURCE LEVEL SECURITY FAILED FOR \"(*)\"_\nReason:\nThe transaction is not authorized to use the resource.\nAction:\nAdjust your security definitions, and resubmit the request.\nCAIN0489\nSECURITY PASSWORD ====>\nReason:\nAn attempt is being made to change storage which does not belong to a break-pointed task and InterTest for CICS has\nbeen generated with CORESEC=YES.\nAction:\nDo one of the following:\n\u2022\n\u2022Enter the password, which allows the change to be made.\n\u2022\n\u2022If you do not know the password or if you do not wish to make the change, press the Enter key. This action produces\nthe CORE022 message.\n\u2022\nCAIN0490\nOPERATION VALID FOR SymDump ONLY\n 1542", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0dae40ebed62-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nThe keyword requested is only valid when using SymDump  for CICS.\nAction:\nReview your request and select another keyword.\nCAIN0491\nVALUE OF FIELD = (*)\nReason:\nThe decimal value, xxxxxxxxx, is displayed for a COBOL data item that was defined as numeric. The sign, a '+' or '-',\nappears as the first character 's'.\nAction:\nNone.\nCAIN0492\nSQLCODE CODE (*) HAS OCCURRED\nReason:\nA serious SQL return code xxxxx has occurred. This could be caused possibly by an incomplete/incorrect installation of\nthe InterTest for CICS DB2 interface.\nAction:\nContact your site InterTest for CICS or SymDump  for CICS installer and report this error.\nCAIN0499\n(*)\nReason:\nMiscellaneous informational CORE messages.\nAction:\nSee message text.\nCAIN0601\nRECORD OBTAINED FOR VIEWING\nReason:\nIn response to the FUNC=GET, FUNC=NEXT, or FUNC=PREV that you entered, a record has been received and its data\nhas been placed in the WORK AREA that is currently displayed.\nAction:\nNone.\nCAIN0603\nWORK AREA OBTAINED\nReason:\nA WORK AREA has been obtained in response to the FUNC=ADDN or FUNC=ADDU that you entered.\nAction:\nNone.\nCAIN0604\nBROWSE BEGUN\nReason:\n 1543", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "11a9e0885497-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nA browse operation began in response to your command.\nAction:\nNone.\nCAIN0605\nBROWSE TERMINATED\nReason:\nA browse operation has ended in response to the FUNC=ENDB that you entered.\nAction:\nNone.\nCAIN0606\nWORK AREA SAVED\nReason:\nThe current WORK AREA has been saved, in response to the FUNC=SAVE that you entered.\nAction:\nNone.\nCAIN0607\nSAVED WORK AREA REPLACED\nReason:\nAn existing saved WORK AREA has been replaced by a new saved WORK AREA, in response to the FUNC=SAVE that\nyou entered.\nAction:\nNone.\nCAIN0608\nSAVED WORK AREA IS DISPLAYED\nReason:\nThe saved WORK AREA is displayed on your screen, in response to the FUNC=DISS that you entered.\nAction:\nNone.\nCAIN0609\nWORK AREA IS DISPLAYED\nReason:\nThe WORK AREA is displayed on your screen, in response to the FUNC=DISW that you entered.\nAction:\nNone.\nCAIN0610\n(DUPKEY) RECORD OBTAINED FOR VIEWING\nReason:\nA VSAM record has been retrieved by an alternate index, in response to the FUNC=GET that you entered. However, there\nare other records in the data set that have the same alternate key. The VSAM record's data was placed in the WORK\nAREA, which is now displayed on the screen.\n 1544", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fca3276bb61e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nA browse retrieves the duplicate records.\nCAIN0611\nRECORD OBTAINED FOR UPDATE\nReason:\nThe record specified in the RCID= field has been retrieved for update, in response to the FUNC=GETU that you entered.\nThe record's data was placed in the WORK AREA, which is now displayed on your screen.\nAction:\nNone.\nCAIN0612\nFWA HAS BEEN RELEASED\nReason:\n(1) For MODE=UPDATE, the record specified in the RCID= field, which had previously been retrieved for update, has\nbeen released. (2) For MODE=ADD or MODE=ADDM, this indicates that you have specified that no more records will be\nadded.\nAction:\nNone.\nCAIN0613\nRECORD DELETED\nReason:\nThe record specified in the RCID= field has been deleted from the file specified in the FILEID= field, in response to the\nFUNC=DEL or FUNC=PUT/SUBFUNC=DEL that you entered. The record's data is still available in the WORK AREA,\nwhich is displayed on your screen.\nAction:\nNone.\nCAIN0614\nRECORD ADDED\nReason:\nThe record specified in the RCID= field has been added to the file specified in the FILEID= field, in response to the\nFUNC=PUT that you entered. The record's data is still available in the WORK AREA, which is displayed on your screen.\nAction:\nNone.\nCAIN0615\nRECORD UPDATED\nReason:\nThe record specified in the RCID= field has been replaced in the file specified in the FILEID= field, in response to the\nFUNC=PUT that you entered. The record's data is still displayed in the WORK AREA, which is displayed on your screen.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fca3276bb61e-1", "text": "Action:\nNone.\n 1545", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "00fc8dc7ab1a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0616\nDATA HAS BEEN LOCATED\nReason:\nThe data specified in the DATA= field has been found, in response to the FUNC=SRCH that you entered. The record was\nretrieved and its data placed in the WORK AREA, which is displayed on your screen, beginning with the byte where the\ndata was found.\nAction:\nNone.\nCAIN0617\nEND OF FILE\nReason:\nAn endoffile condition has been encountered during a FUNC=NEXT or a beginningoffile condition was found during a\nFUNC=PREV. The browse operation has been terminated.\nAction:\nNone.\nCAIN0618\nREQUEST PROCESSED\nReason:\nYour request has been processed successfully.\nAction:\nNone.\nCAIN0619\nTS RECORD RETRIEVED\nReason:\nA record has been retrieved from the temporary storage area specified in the RCID= field, in response to the FUNC=GET\nthat you entered. The record's data was placed in the WORK AREA, which is now displayed on your screen.\nAction:\nNone.\nCAIN0620\nTS RECORD RETRIEVED AND RELEASED\nReason:\nA record has been retrieved and released from the temporary storage area specified in the RCID= field, in response to the\nFUNC=REL or FUNC=GET/SUBFUNC=REL that you entered.\nAction:\nNone.\nCAIN0621\nTS QUEUE RECORD RETRIEVED\nReason:\nThe temporary storage queue record specified in the RCID=and ENTRY= fields has been retrieved, in response to the\nFUNC=GETQ that you entered. The record's data was placed in the WORK AREA, which is now displayed on your\nscreen.\n 1546", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f2dda5d047b5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nNone.\nCAIN0622\nTS QUEUE PURGED\nReason:\nThe temporary storage queue specified in the RCID= field has been purged, in response to the FUNC=PURG that you\nentered.\nAction:\nNone.\nCAIN0623\nTS RECORD WRITTEN\nReason:\nA record has been written to the temporary storage area specified in the RCID= field, in response to the FUNC=PUT that\nyou entered. The record's data is still available in the WORK AREA, which is displayed on your screen.\nAction:\nNone.\nCAIN0624\nTS RECORD WRITTEN AND REPLACED\nReason:\nA record has been replaced in the temporary storage area specified in the RCID= field, in response to the FUNC=PUT/\nSUBFUNC=REPL that you entered. The record's data is still active in the WORK AREA, which is displayed on your\nscreen.\nAction:\nNone.\nCAIN0625\nTS QUEUE RECORD WRITTEN\nReason:\nA record has been written to the temporary storage queue specified in the RCID= field, in response to the FUNC=PUTQ\nthat you entered. The record's data is still available in the WORK AREA, which is displayed on your screen.\nAction:\nNone.\nCAIN0626\nTS QUEUE RECORD WRITTEN AND REPLACED\nReason:\nA record has been placed in the temporary storage queue specified in the RCID= and ENTRY= fields, in response to the\nFUNC=PUTQ/SUBFUNC=REPL that you entered.\nAction:\nNone.\nCAIN0627\nTD RECORD RETRIEVED\n 1547", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8e9cb247ecc6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nA transient data record has been retrieved from the transient data destination specified in the DESTID= field, in response\nto the FUNC=GET that you entered. The record's data was moved to the WORK AREA, which is displayed, on your\nscreen.\nAction:\nNone.\nCAIN0628\nTD RECORD WRITTEN\nReason:\nThe specified record was written to the transient data destination specified in the DESTID= field, in response to the\nFUNC=PUT that you entered. The record's data is still available in the WORK AREA, which is displayed on your screen.\nAction:\nNone.\nCAIN0629\nDESTINATION PURGED\nReason:\nThe transient data destination specified in the DESTID= field was purged, in response to the FUNC=PURG that you\nentered.\nAction:\nNone.\nCAIN0630\nSIZE= INVALID OR MISSING\nReason:\nSelfexplanatory.\nAction:\nCorrect the error, and resubmit your request.\nCAIN0631\nCHGELEN= INVALID OR MISSING\nReason:\nSelfexplanatory.\nAction:\nCorrect the error, and resubmit your request.\nCAIN0632\nLOC= INVALID OR MISSING\nReason:\nThe LOC= field does not contain one of the following values: all numerics, ?, FWD, BWD, or ANY.\nAction:\nCorrect the error and resubmit the request.\nCAIN0633\nRCID= INVALID OR MISSING\n 1548", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6c169fe0c652-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nThe record identification must be entered exactly as required in the CICS/VS Application Programmer's Reference\nManual. This includes all the necessary bytes; the FILE transaction provides no padding. If character and hexadecimal\nvalues have to be mixed in the record identification, use C' ' and X' ' strings.\nAction:\nCorrect the error, and resubmit the request.\nCAIN0634\nDATATYPE= INVALID\nReason:\nThe DATATYPE= field was not an FC, TS, TD, or DL (if DL/I support is generated).\nAction:\nCorrect the error, and resubmit the request.\nCAIN0635\nFUNC= INVALID\nReason:\nThe function you selected is not known to the FILE transaction or is not supported for the specified file.\nAction:\nCorrect the error, and resubmit the request.\nCAIN0635\nFUNC= INVALID\nReason:\nThe function you selected is not known to the FILE transaction or is not supported for the specified file.\nAction:\nCorrect the error, and resubmit the request.\nCAIN0636\nSUBFUNC= INVALID\nReason:\nSelfexplanatory.\nAction:\nCorrect the error and resubmit the request.\nCAIN0637\nRETMETH= INVALID\nReason:\nThe RETMETH= field does not contain 'KEY' or 'RELREC'.\nAction:\nCorrect the error and resubmit the request.\nCAIN0638\nSRCHTYP= INVALID\nReason:\nThe SRCHTYP= field does not contain one of the following: 'FKEQ', 'FKGE', 'GKEQ', or 'GKGE'.\nAction:\nCorrect the error and resubmit the request.\n 1549", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "937beebe9382-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0639\nDATA= INVALID OR MISSING\nReason:\nSelfexplanatory. Note that if both hexadecimal and character bytes are to be entered, a concatenation of C' ' and X' '\nstrings is most practical.\nAction:\nCorrect the error and resubmit the request.\nCAIN0640\nTODEST= INVALID OR MISSING\nReason:\nThe TODEST= field is either not filled in or is filled in with an invalid transient data destination. You can check the CICS\nDestination Control Table by issuing the CORE=DCT or CORE=DEST=destid command.\nAction:\nCorrect the error and resubmit the command.\nCAIN0641\nARGTYP= INVALID\nReason:\nThe ARGTYP= field does not contain 'KEY', 'RBA' or 'XRBA'.\nAction:\nCorrect and resubmit.\nCAIN0642\nENTER program.structure NAME IN USE= FIELD\nReason:\nInstructional message.\nAction:\nEnter the program.structure name in the USE= field.\nCAIN0651\nENTRY ERROR\nReason:\nThe number specified in the ENTRY= field is not within the limits of the existing queue.\nAction:\nCorrect and resubmit.\nCAIN0652\nNO SPACE ON AUXILIARY STORAGE\nReason:\nThere is no space available in auxiliary storage.\nAction:\nNone.\n 1550", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f301b52dd1e1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0653\nTS RECORD NOT FOUND. CANNOT BE REPLACED\nReason:\nThe temporary storage record to be replaced cannot be found.\nAction:\nNone.\nCAIN0654\nIDENTIFICATION ERROR\nReason:\nThe symbolic temporary storage identification in the RCID= field could not be found. This is usually the same as a 'record\nnot found' condition.\nAction:\nCorrect the RCID= and resubmit.\nCAIN0655\nREMOTE DATAID'S NOT SUPPORTED\nReason:\nAccess to remote temporary storage queues is not supported.\nAction:\nNone.\nCAIN0661\nQUEUE IS BUSY\nReason:\nThe transient data queue could not be accessed due to a busy condition.\nAction:\nTry the request later.\nCAIN0662\nQUEUE IS ZERO\nReason:\nThere are no records in the Transient Data Queue.\nAction:\nNone.\nCAIN0663\nINVALID DESTINATION\nReason:\nThe Transient Data Queue name is not defined to CICS.\nAction:\nCorrect the queue name and resubmit.\nCAIN0665\nDESTINATION NOT OPEN\n 1551", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "724a2922442d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nThe destination entered in the DESTID= field is not opened.\nAction:\nDetermine why the destination is not open. If possible, use the CEMT or CSMT service transactions to open the\ndestination.\nCAIN0666\nNO SPACE ON QUEUE\nReason:\nThe intrapartition data set specified in the DESTID= field is out of space.\nAction:\nNone.\nCAIN0667\nWRITE NOT SERVICEABLE\nReason:\nThe extrapartition data set specified in the DESTID= field is out of space.\nAction:\nNone.\nCAIN0668\nREMOTE DESTID'S NOT SUPPORTED\nReason:\nInformational message.\nAction:\nNone.\nCAIN0671\nINVALID FILE NAME\nReason:\nThe file named in the FILEID= was not found in the CICS File Control Table (FCT).\nAction:\nCorrect the file name in the FILEID= field and resubmit the request.\nCAIN0672\nDUPKEY RECORD ERROR\nReason:\nYou attempted to add a record whose record key already exists.\nAction:\nNone.\nCAIN0673\nRECORD NOT FOUND\nReason:\nYou attempted to read a record that does not exist.\nAction:\n 1552", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "70e95509e7f2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCorrect the record ID and resubmit the request.\nCAIN0674\nDUPLICATE RECORD\nReason:\nA duplicate record occurred while you were executing a file request.\nAction:\nCorrect the record ID, and resubmit the request.\nCAIN0675\nINVALID REQUEST\nReason:\nAn invalid request occurred while executing a file request.\nAction:\nCheck the FCT entry for the FILEID to ensure that it allows the type of processing that you requested.\nCAIN0676\nINPUT/OUTPUT ERROR\nReason:\nAn Input/Output error occurred during the CICS requests and processing did not complete correctly.\nAction:\nRetry the request. If the error still occurs, contact your CICS Systems Programmer.\nCAIN0677\nFILE DISABLED\nReason:\nEXEC CICS names a disabled or nonexisting program.\nAction:\nCheck that the program is in the correct CICS Load Library. Check the program definition for the program you requested.\nCAIN0678\nNO DASD SPACE FOR ADDING RECORD\nReason:\nThere is no space available on the direct access device for adding records to a data set. Your program did not have a\nHANDLE CONDITION for this error.\nAction:\nExpand the data set or cancel your transaction by pressing PF9, ENTER and PF3.\nCAIN0679\nFILE IS NOT OPEN\nReason:\nThe error occurred because the file you are trying to access is not open to CICS. Your program did not have a HANDLE\nCONDITION for this error.\nAction:\nDisconnect your terminal from InterTest for CICS and use the CEMT transID to open the file. Then reconnect you terminal\nto InterTest for CICS and use the resume task menu to execute the CICS request again.\n 1553", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d72d0be36769-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0680\nYOU ARE ATTEMPTING TO CHANGE THE RECORD KEY\nReason:\nYou cannot modify the key of a record.\nAction:\nNone.\nCAIN0681\nDL/1 CANNOT BE ACCESSED FROM DATATYPE=FC\nReason:\nThe file you are accessing is a DL/I database and DL/I cannot be accessed from DATATYPE=FC.\nAction:\nSpecify DATATYPE=DL.\nCAIN0682\nSIZE= VALUE IS GREATER THAN MAX FOR FILE\nReason:\nInformational message.\nAction:\nCorrect and resubmit.\nCAIN0683\nRECFORM=Undefined. NOT SUPPORTED\nReason:\nThe file specified in the FILEID= field is defined as RECFORM= Undefined.\nAction:\nNone.\nCAIN0684\nFILE COULD NOT BE OPENED\nReason:\nInformational message.\nAction:\nDetermine why the file could not be opened. Correct the problem and resubmit your request.\nCAIN0685\nRECORD LENGTH IS INVALID\nReason:\nYou attempted to update or insert a record that is too long (RECFM=V) or not equal (RECFM=F) to the file's record\ndefinition.\nAction:\nSpecify the correct length and resubmit the request.\nCAIN0686\nMRO/ISC ABEND PROCESSING A REMOTE FILE\n 1554", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f8f2c1e863f5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nAbend xxxx occurred while processing a remote request.\nAction:\nProbable MRO/ISC setup error. Check that the MRO/ISC connections are properly established and that InterTest for CICS\nrelease 4.2 or above is installed in each region.\nCAIN0687\nREMOTE BDAM FILES ARE NOT SUPPORTED\nReason:\nThe file to be processed is not local to the region.\nAction:\nUse InterTest for CICS in the region that owns the file.\nCAIN0688\nMRO/ISC ERROR PROCESSING A REMOTE FILE\nReason:\nAn error occurred while establishing the session to the remote region. Probable MRO/ISC setup error.\nAction:\nCheck the MRO/ISC connections. Ensure that InterTest for CICS release 4.2 or above is installed in each region. You can\nuse CEDF to debug this problem and stop at ALLOCATE commands.\nCAIN0689\nFILE STATUS IS CLOSED, UNENABLED\nReason:\nInformational message.\nAction:\nNone.\nCAIN0690\nDATABASE NOT IN DDIR, CLOSED OR INVALID ARG\nReason:\nThe database is not defined to CICS, or it has not been started.\nAction:\nEnsure that the database exists and resubmit the request.\nCAIN0691\nPSB NAME NOT IN DIRECTORY\nReason:\nThe file to be processed is not local to the region.\nAction:\nUse InterTest for CICS in the region that owns the file.\nCAIN0692\nPROGRAM NOT DEFINED IN APPL CNTL TABLE\nReason:\n 1555", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d80690fbdd71-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe PSB is not defined in the IN25FLF program's entry in the DL/I Application Control Table. The IN25FLF must be in the\nACT because that programs issues the DL/I calls for the FILE transaction.\nAction:\nAdd the PSB to the IN25FLF entry in the ACT.\nCAIN0693\nCALLING PROGRAM IS CURRENTLY SCHEDULED\nReason:\nThe PSB has already been scheduled.\nAction:\nContinue with the request.\nCAIN0694\nPSB SPECIFIES PLI\nReason:\nThe specified PSB was generated as PL/I.\nAction:\nChange the PSB language specification and regenerate, or generate a duplicate PSB that specifies the languages as\nASM.\nCAIN0695\nPSB COULD NOT BE INITIALIZED\nReason:\nThe PSB could not be scheduled.\nAction:\nDetermine the reason for this failure.\nCAIN0696\nPSB NOT DEFINED IN PROGS APPL CNTL TAB ENTRY\nReason:\nThe PSB is not defined in the IN25FLF program's entry in the DL/1 Application Control Table. The IN25FLF must be in the\nACT because that program issues the DL/1 calls for the FILE transaction.\nAction:\nAdd the PSB to the IN25FLF entry in the ACT.\nCAIN0697\nDLI INTERFACE HAS BEEN TERMINATED\nReason:\nInformational message.\nAction:\nDetermine why the DL/1 interface has been terminated.\nCAIN0698\nTASK HAS NOT SCHEDULED A PSB\nReason:\nA proper PSB must be scheduled to complete your DLI call.\n 1556", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "041439a4ae39-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nSpecify the correct PSB, and resubmit the request.\nCAIN0699\nENTER PSB / DBD\nReason:\nInformational message.\nAction:\nEnter the appropriate value.\nCAIN0700\nINVALID PCB ADDRESS\nReason:\nThe proper PSB must be scheduled to complete your DLI call.\nAction:\nCheck the PSB specified, and resubmit the request.\nCAIN0701\nNO PCB FOR DBD\nReason:\nThe DBD specified in the DBD= field was not found in the PSB that was entered in the PSB= field.\nAction:\nEnter the correct PSB or DBD and resubmit.\nCAIN0702\nINVALID PCB NUMBER FOR DBD\nReason:\nThe PCB number in the NO= field for this DBD is invalid.\nAction:\nSpecify the correct PCB number and resubmit.\nCAIN0703\nSSA IS INVALID\nReason:\nInformational message.\nAction:\nSpecify the correct SSA and resubmit.\nCAIN0709\nDL/1 NOT ACTIVE\nReason:\nYou attempted to access a DL/I database, but your attempt has failed, because the DL/I is not defined to the region.\nAction:\nCheck the SIT parameter, DL1=.\n 1557", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0c8c409034d5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0711\nNO WORKAREA. REQUEST IGNORED\nReason:\nNo WORK AREA was found for a FUNC= DISW request.\nAction:\nEnter the appropriate value.\nCAIN0712\nCOPY INVALID WHEN LOGGING OR AUDIT=YES\nReason:\nThe transient data copy function may not be used while the logging or audit functions are active.\nAction:\nDeactivate these functions, and resubmit the request.\nCAIN0713\nNLOG INVALID BECAUSE AUDIT=YES IS ACTIVE\nReason:\nThe system installation defined automatic logging through AUDIT=YES, and the no logging (NLOG) parameter was\nspecified by the user.\nAction:\nLogging is performed.\nCAIN0714\nFUNC= PREV INVALID FOR BDAM FILE\nReason:\nBDAM files cannot be read in reverse.\nAction:\nNone.\nCAIN0715\nLOC IS BEYOND WORK AREA\nReason:\nThe value in the LOC= field points beyond the WORK AREA.\nAction:\nEnter the correct value and resubmit.\nCAIN0716\nNO SAVED WORK AREA. REQUEST IGNORED\nReason:\nThere was no work area available for the specified function.\nAction:\nIssue a save command, and resubmit the request.\nCAIN0717\nFROMLOC IS BEYOND SAVED WORK AREA\n 1558", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "22e88ec3efa2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nInformational message.\nAction:\nCorrect and resubmit.\nCAIN0719\nENTER THE PASSWORD\nReason:\nThe file or DBD you are working with is passwordprotected. The password is missing from the PASSWORD= field or PS=\nfield. The person who generated InterTest for CICS at your installation should be able to answer any questions about FILE\npasswords.\nAction:\nEnter the correct password.\nCAIN0720\nPASSWORD INVALID\nReason:\nThe password that you entered was incorrect.\nAction:\nObtain the appropriate password and resubmit.\nCAIN0726\nFUNCTION SEQUENCE ERROR\nReason:\nInformational message.\nAction:\nRefer to CICS Debugging for the proper sequence.\nCAIN0728\nDATA NOT FOUND\nReason:\nThe data specified in the DATA= field has been not been found after searching the number of records specified in the\nSIZE= field, in response to the FUNC= SRCH command that you entered.\nAction:\nEnter a different data string.\nCAIN0731\nENTER FILEID\nReason:\nThe file name, or identification, is missing from the FILEID= field.\nAction:\nEnter the appropriate value.\nCAIN0732\nENTER DEST ID\nReason:\n 1559", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e1f2253a2693-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe transient data destination name, or identification, is missing from the DESTID= field.\nAction:\nEnter the appropriate value.\nCAIN0733\nFILE TRANSACTION IS NOT AUTHORIZED\nReason:\nThe FILE transaction is not authorized to access the file.\nAction:\nIf the file or TS queue is remote, check the CICS mirror transaction authority. You can use CEDF to debug this problem.\nCAIN0734\nFILE HAS BEEN DISABLED\nReason:\nInformational message.\nAction:\nNone.\nCAIN0735\nDESTINATION HAS BEEN DISABLED\nReason:\nYou attempted to access a disabled transient data queue.\nAction:\nEnable the queue, and resubmit your request.\nCAIN0736\nUNRECOGNIZED SBA ON INPUT REENTER DATA\nReason:\nA logic error occurred in the file transaction.\nAction:\nContact Broadcom Support .\nCAIN0737\nIN25SEC2 NOT FOUND IN PPT OR IS DISABLED\nReason:\nThe FILE transaction goes to the InterTest for CICS program IN25SEC2 to check to see if a password is valid. However,\nthe transaction was unable to find IN25SEC2.\nAction:\nReport the problem to the person who installed InterTest for CICS.\nCAIN0738\nUNEXPECTED ERROR RECEIVED\nReason:\nAn unexpected error has occurred.\nAction:\nResubmit your request. If you still get an error, contact Broadcom Support .\n 1560", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a7ec4a13d30b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0739\nFUNC= COMMAND NOT SUPPORTED IN THIS RELEASE\nReason:\nThe command you entered is not supported in this release of InterTest for CICS.\nAction:\nNone.\nCAIN0740\nILLOGIC ERROR\nReason:\nThis error occurs after all other error conditions have been checked.\nAction:\nCheck the VSAM error code in the VSAM Messages and Codes  manual and proceed accordingly. The value in\nVSWARTNC is the same as the value in register 15 on return from the VSAM macro. The value in VSWAERRC is the\nerror code from the RPL block in the VSWA area. Both values are expressed in hexadecimal format.\nCAIN0741\nUNIDENTIFIED ERROR\nReason:\nA logic error occurred in the file transaction.\nAction:\nContact Broadcom Support .\nCAIN0742\nAUDIT FAILURE VALIDATE GLOG DESTID\nReason:\nThe global logging Transient Data Destination ID is not defined to CICS or it cannot be written to.\nAction:\nEnsure that the Destination ID exists and can be written to.\nCAIN0750\nDATANAME WAS NOT FOUND IN THE STRUCTURE\nReason:\nA 'FIND' request for an undefined data name was issued.\nAction:\nSpecify a valid data name, and resubmit the request.\nCAIN0751\nAT FIRST ENTRY IN STRUCTURE\nReason:\nThis item is the first item in a structured request.\nAction:\nNone.\n 1561", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "33d34f716b0e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0752\nAT LAST ENTRY IN STRUCTURE\nReason:\nThis item is the last item displayed for a structured request.\nAction:\nNone.\nCAIN0753\nSTRUCTURE NAME FOUND BEFORE SEARCH START LOC\nReason:\nYou were displaying a structured work area before setting a breakpoint or UBP option.\nAction:\nStart InterTest for CICS at the first area in the procedure division or at #1 before looking at the item.\nCAIN0754\nSTRUCTURE TRUNCATED TO WORK AREA LENGTH\nReason:\nThe structured file is longer than the area that you are trying to access.\nAction:\nSpecify the actual length of the structured file and insert that information into the program. Recompile the program and run\nthe NEW COPY function.\nCAIN0755\nLAST STRUCTURE NAME EXPANDED\nReason:\nThis item is the last field of the structure. It has been redefined.\nAction:\nNone.\nCAIN0756\nDATANAME OFFSET EXCEEDS WORK AREA LENGTH\nReason:\nThe length of the item you are trying to view is longer than the length of the work area.\nAction:\nIncrease the length of the work area. Recompile the program and run the NEW COPY option.\nCAIN0757\nLOC= IS PAST THE END OF RECORD\nReason:\nThe specified location is not part of your record.\nAction:\nCheck the listing to find out where the field is located and correct the LOC= entry.\nCAIN0758\nTRANSACTION HAS BEEN TERMINATED\n 1562", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "95cfd19aad09-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nThe transaction was abended or the transaction ended correctly\nAction:\nPress PF1 to display the abend, or specify the next transaction.\nCAIN0759\nFILE FACILITY TERMINATED\nReason:\nYou pressed Clear and terminated the FILE facility.\nAction:\nNone.\nCAIN0760\nEDIT ERRORS\nReason:\nErrors are present in your listing.\nAction:\nCheck your listing to determine where the errors occurred.\nCAIN0761\n(*) BYTES CHANGED\nReason:\nThis message indicates that (*) bytes changed. It gives the address of the first byte (YYYYYYY).\nAction:\nNone.\nCAIN0762\nDB2 PGM NOT DEFINED IN PPT OR NOT IN LOADLIB\nReason:\nThe program was not loaded in the proper CICS load LIB. The PPT entry was disabled and cannot be loaded.\nAction:\nModify or correct the PPT name. Ensure that the program is loaded into the correct load LIB.\nCAIN0763\nMRO/ISC ABEND (*) PROCESSING A REMOTE FILE\nReason:\nA remote file cannot be accessed, or it is not defined properly.\nAction:\nCheck the file definitions and the CICS connection to the remote system.\nCAIN0764\nABEND (*) HAS OCCURED WHEN ACCESSING DBCTL\nReason:\nThe specified abend occurred while you were trying to access the DBCTL.\nAction:\nFor more information, see the DB2 Messages and Codes  manual. Correct the problem and retry.\n 1563", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "158c837d074f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0765\n(*) RECORDS DELETED\nReason:\nYou requested that specified records be deleted using the FILE facility of InterTest for CICS.\nAction:\nNone.\nCAIN0766\nMRO/ISC ERROR ON REMOTE FILEEIBRESP IS (*)\nReason:\nThe file you were searching for was not found.\nAction:\nCheck the FCT entries to see where the file is located. Correct the FCT entry if necessary.\nCAIN0767\nILLOGIC ERROR. EIB RTNC (*) EIB ERRC (*)\nReason:\nThere is a logic error. The EIB return code (N), EIB error code (X) follows.\nAction:\nExamine your program and correct the logic.\nCAIN0768\nUNIDENTIFIED ERROR. TCAFCTR (*)\nReason:\nAn internal logic problem exists in the FILE transaction.\nAction:\nContact Broadcom Support .\nCAIN0769\nLOWERCASE CHARS FOUND, PRESS PF9 AND REENTER\nReason:\nYou attempted to modify lowercase data to uppercase data because you are in Caps On mode. The lower case data was\nnot modified.\nAction:\nPress PF9 to switch to Caps Off mode, and reenter the modified data, or switch to Format H and modify the data.\nCAIN0770\nSRCHTYP MUST BE FKEQ OR GKEQ FOR FUNC=DEL\nReason:\nYou entered the wrong search type. To delete records, enter FKEQ or GKEQ.\nAction:\nSpecify FKEQ or GKEQ as your search type.\nCAIN0771\nPARTIAL DUMP TAKEN\n 1564", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "644a068b9b9c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nA partial dump occurred. It contains registers and the last instruction that was executed.\nAction:\nEnable ITTrace to obtain a valid dump: CNTL=ITTRACE,ON. Or, fix the error that caused the dump to occur.\nCAIN0780\nCALL COMPLETED\nReason:\nThe DL/I CALL that you specified executed successfully.\nAction:\nNone.\nCAIN0781\nHIERARCHICAL ERROR IN SSAS\nReason:\nThe DL/I CALL that you specified did not execute successfully. Refer to the IBM IMS/VS Application Programming Guide\nfor CICS Users for a detailed explanation of the DL/I status code, which appears on the FILE menu.\nAction:\nContact Broadcom Support .\nCAIN0782\nREQUIRED SSAs MISSING\nReason:\nThis database call requires that the SSAs be properly specified.\nAction:\nCorrect the SSAs and resubmit, or contact Broadcom Support .\nCAIN0783\nDATA MANAGEMENT OPEN ERROR\nReason:\nThe database you are trying to open could not be accessed.\nAction:\nCheck the parameters you set and resubmit, or contact Broadcom Support .\nCAIN0784\nSSA QUALIFICATION FORMAT INVALID\nReason:\nInformational message.\nAction:\nCheck the parameters you set and resubmit, or contact Broadcom Support .\nCAIN0785\nINVALID SSA FIELD NAME\nReason:\nInformational message.\nAction:\n 1565", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c71a113f25c0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCorrect the SSA field name and try again, or contact Broadcom Support .\nCAIN0786\nCALL INCOMPATIBLE WITH PROCESSING OPTIONS\nReason:\nYour request is illogical.\nAction:\nCorrect your request and try again, or contact Broadcom Support .\nCAIN0787\nI/O ERROR\nReason:\nAn I/O error occurred during the CICS request, and processing was not successfully completed.\nAction:\nCorrect your request and try again, or contact Broadcom Support .\nCAIN0788\nNO SUCH COMMAND\nReason:\nThere is no such command in InterTest for CICS.\nAction:\nRefer to CICS Debugging for a list of valid commands.\nCAIN0789\nCOMMAND EXECUTED\nReason:\nThe command you entered in your program executed successfully.\nAction:\nNone.\nCAIN0790\nCOMMAND VIOLATES SECURITY\nReason:\nThe command you entered violates security.\nAction:\nCheck the command you entered. See your facility's systems people to find out what caused the security violation.\nCAIN0791\nKEY FIELD OR NONREPLACEABLE FIELD CHANGED\nReason:\nWhile completing a FILE transaction, you attempted to change a nonreplaceable or segment key field.\nAction:\nCorrect your request and try again, or contact Broadcom Support .\n 1566", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "71ea29385e2d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0792\nNO PREVIOUS SUCCESSFUL GHX CALL\nReason:\nThe command you entered requires that a previous GHX had been successfully executed.\nAction:\nCorrect your request and try again, or contact Broadcom Support .\nCAIN0793\nVIOLATED DELETE RULE\nReason:\nYou did not enter the FUNC=DEL command properly.\nAction:\nRefer to CICS Debugging for a list of valid commands, correct your request and try again, or contact Broadcom Support .\nCAIN0794\nCROSSED HIERACHICAL BOUNDRY INTO HIGHER LVL\nReason:\nA DL/1 request was issued, which caused a hierarchy boundary change.\nAction:\nCorrect your request and try again, or contact Broadcom Support .\nCAIN0795\nEND OF DATASET\nReason:\nAn End of Dataset was encountered while processing the DL/I request.\nAction:\nNone.\nCAIN0796\nSEGMENT NOT FOUND\nReason:\nThe segment that you requested is not on the file.\nAction:\nNone.\nCAIN0797\nDIFFERENT SEGMENT TYPE AT SAME LEVEL\nReason:\nYour data includes 2 or more field names at this level.\nAction:\nCorrect your request and try again, or contact Broadcom Support .\nCAIN0798\nNO PARENTAGE ESTABLISHED\nReason:\n 1567", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "be40d1c9e5de-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nA DL/I GNP or GHNP call was executed, but no parentage was established.\nAction:\nNone.\nCAIN0799\nSEGMENT ALREADY EXISTS\nReason:\nYou are trying to add a record that already exists.\nAction:\nDelete the older record before you add this record, or clear out this record.\nCAIN0800\nVIOLATED INSERT RULE\nReason:\nYour attempt to insert or add a record or record segment was invalid.\nAction:\nRefer to CICS Debugging for a list of rules on how to use the File Request option. Correct your request and try again, or\ncontact Broadcom Support .\nCAIN0801\nSEGMENT BEING LOADED ALREADY EXISTS\nReason:\nThe segment that you are trying to add is already on the database.\nAction:\nContact Broadcom Support .\nCAIN0802\nKEY FIELD OF SEGMENT OUT OF SEQUENCE\nReason:\nThe key field of the segment being loaded is out of sequence.\nAction:\nCheck the segment and determine where it should be loaded.\nCAIN0803\nNO PARENT FOR THIS SEGMENT HAS BEEN LOADED\nReason:\nAn illogical DL/1 request has been made.\nAction:\nRespecify the command, or contact Support.\nCAIN0804\nOUT OF SEQUENCE FOR SIBLING SEGMENT\nReason:\nAn illogical DL/1 request has been made.\nAction:\nRespecify the command.\n 1568", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6089326c23ef-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN0805\nVIOLATED REPLACE RULE\nReason:\nYou did not enter the correct information to replace a record or field.\nAction:\nRefer to the CICS Debugging for a list of rules on how to replace a record or field.\nCAIN0806\nNO Message FOR THIS STATUS CODE\nReason:\nThere is no message available for this status.\nAction:\nNone.\nCAIN1001\nPA/PF key function is undefined.\nReason:\nThe key that was hit on the terminal keyboard is not defined to InterTest for CICS asgrammed function.\nAction:\nPress Enter or one of the PF keys listed on rows 2223.\nCAIN1002\nCA InterTest internal error at (*).\nReason:\nA logic error occurred in the indirect command processing program at the hexadecimal offset location indicated in the\nmessage text.\nAction:\nContact Broadcom Support .\nCAIN1004\nPA/PF key function entered is invalid.\nReason:\nThe function defined for the PF key entered is not valid for currently displayed screen.\nAction:\nPress Enter or one of the PF keys listed on rows 2223.\nCAIN1010\nSecurity violation request ignored.\nReason:\nThe user is not defined to external security with adequate access authority for the requested function or resource.\nAction:\nContact your external security administrator.\nCAIN1019\nInvalid statement number reenter.\n 1569", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c7da29beaed4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nThe statement number entered on an indirect GOTO command is not defined as valid in the program listing PROTSYM\nsymbolic file.\nAction:\nCorrect the invalid statement number and continue.\nCAIN1020\nUpdate is for a protected or undefined type data\nReason:\nThe indirect MOVE command defined would result in modifying an area in storage that is either not owned by the task or\nis of an unsupported data type (for example, paragraph label).\nAction:\nCorrect the offending indirect command and continue.\nCAIN1021\nInvalid location reenter.\nReason:\nThe paragraph or label name entered in an indirect GOTO command was not found on the PROTSYM symbolic file\nprogram listing.\nAction:\nCorrect the command and continue.\nCAIN1022\nInvalid displacement reenter.\nReason:\nThe program displacement value entered in an indirect GOTO command was either not a valid even hexadecimal value or\nexceeded the program length.\nAction:\nCorrect the command and continue.\nCAIN1041\nGetmain error processing symbolics.\nReason:\nA CICS GETMAIN attempt failed while processing an indirect command symbolic argument.\nAction:\nRetry when less system activity or contact systems programmer.\nCAIN1042\nI/O error occurred while reading the PROTSYM.\nReason:\nA PROTSYM file I/O error occurred during indirect command processing.\nAction:\nInspect log for VSAM diagnostic messages and codes.\nCAIN1043\nStatement number not found enter valid statement number.\n 1570", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "98cd77c24b88-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nThe statement number entered on an indirect command line does not exist on the PROTSYM file program listing.\nAction:\nCorrect the command and continue.\nCAIN1044\nSymbolic information for program not found.\nReason:\nSymbolics for the requested program do not exist on any of the active PROTSYM files. Indirect command support is not\navailable without program symbolic information.\nAction:\nRecompile and postprocess the program and retry.\nCAIN1045\nShortonstorage (SOS) condition detected.\nReason:\nA CICS GETMAIN attempt failed during indirect command processing.\nAction:\nRetry when less system activity or contact systems programmer.\nCAIN1055\nRequested program is not available or is marked disabled.\nReason:\nIndirect command processing could not be invoked because the requested program could not be loaded.\nAction:\nDefine or enable the requested CICS program and retry.\nCAIN1064\nTime stamp error message all variable (*).\nReason:\nThe date/time stamp of the executable copy of the requested program does not match that of the copy on the PROTSYM\nfile. Indirect command symbolic references may not be valid.\nAction:\nRecompile the program and/or NEWCOPY the executable copy.\nCAIN1066\nNo date/time stamp in module module check ignored.\nReason:\nThe date/time stamp of the executable copy of the requested program was not found. Indirect command symbolic\nreferences may not be valid.\nAction:\nRecompile the program and/or NEWCOPY the executable copy.\nCAIN1106\nBLL cell has not been initialized.\nReason:\n 1571", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8d03207344c4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAn execution request was made against a program symbolic data area that has not yet been established in the active\nprogram.\nAction:\nRefer to the area at a valid point in the program logic.\nCAIN1150\nParagraph name not found, enter valid paragraph name.\nReason:\nAn indirect command GOTO command specified a program paragraph name that could not be found on the PROTSYM\nfile listing.\nAction:\nCorrect the paragraph name or recompile and postprocess.\nCAIN1170\nIndirect commands not supported for requested program.\nReason:\nIndirect command processing was requested for an assembler language program that is not supported.\nAction:\nNone.\nCAIN1174\nData cannot be displayed in native mode.\nReason:\nUndefined.\nAction:\nUndefined.\nCAIN1177\nInternal error locating symbolic data.\nReason:\nUndefined.\nAction:\nUndefined.\nCAIN1179\nInternal error locating storage data.\nReason:\nUndefined.\nAction:\nUndefined.\nCAIN1180\nInternal error determining COBOL data type.\nReason:\nCOBOL working storage could not be found for the monitored program.\nAction:\n 1572", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3fab4ff52dd1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nContact Broadcom Support .\nCAIN1181\nCannot locate storage data address is invalid.\nReason:\nThe address on the requested symbolic area has either not yet been established or does not belong to the task.\nAction:\nCorrect or refer to the area at a valid point in the program.\nCAIN1182\nEdited data is invalid as defined in the data division.\nReason:\nUndefined.\nAction:\nUndefined.\nCAIN1185\nLinkage sect/dyn storage is not available in native mode.\nReason:\nUndefined.\nAction:\nUndefined.\nCAIN1186\n(*) is not a data name on symbolic file.\nReason:\nThe symbolic name specified in the indirect command could not be found on the PROTSYM file listing.\nAction:\nCorrect the name or recompile and postprocess the program.\nCAIN1187\n(*) is an invalid data name.\nReason:\nThe data name specified in the indirect command is greater than 31 characters long.\nAction:\nCorrect the command and continue.\nCAIN1188\n(*) contains invalid data.\nReason:\nAn indirect command could not be successfully processed because the area specified does not contain a value that\nconforms to its defined data type.\nAction:\nCorrect the area by moving a valid value into it and retry.\n 1573", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bcd991cb0207-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN1189\nInvalid data type for subscript.\nReason:\nUndefined.\nAction:\nUndefined.\nCAIN1191\nInvalid literal in command.\nReason:\nThe literal specified in an indirect command does not contain valid values, matching delimiters, or is incorrect in length.\nAction:\nCorrect the command and continue.\nCAIN1192\nIncompatible data type in command.\nReason:\nAn indirect command is attempting to modify or compare a data area with a value or data area of another type.\nAction:\nCorrect the command and continue.\nCAIN1193\nMove literal is too long for data name truncated.\nReason:\nAn indirect MOVE command is attempting to move a literal into an area too small to contain it in its entirety. Only the\nportion that fits is moved.\nAction:\nShorten the literal or increase the data area.\nCAIN11930\nMove literal is too short for data name, data padded.\nReason:\nAn indirect MOVE command is attempting to move a literal that is shorter than the target area. The value is padded with\nfill characters for the full length of the area.\nAction:\nNone.\nCAIN1194\nMove command has been executed.\nReason:\nUndefined.\nAction:\nUndefined.\n 1574", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3c64954a5785-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN1197\nStandard variable list command.\nReason:\nUndefined.\nAction:\nUndefined.\nCAIN1250\nWKS/TGT currently not allocated for this COBOLII pgm.\nReason:\nThe COBOLII working storage or TGT area is not available at the current breakpoint location in the program.\nAction:\nInvoke indirect commands at another location in the program.\nCAIN1252\nRequested DSA not available.\nReason:\nUndefined.\nAction:\nUndefined.\nCAIN1255\nNo indirect commands exist for this program/terminal.\nReason:\nThe CMD option has been newly defined for the program/terminal and does not yet contain any command text or all\ncommands have been deleted.\nAction:\nDefine indirect commands or remove the 'EXEC=' breakpoint.\nCAIN1256\nIndirect command exceeds specified input buffer size.\nReason:\nThe total cumulative size of the indirect command text defined for the program/terminal exceeds the maximum amount\nspecified in IN25OPTS value ICMDBUF.\nAction:\nReduce indirect commands or increase IN25OPTS ICMDBUF value.\nCAIN1257\nIndirect command number is out of numeric range.\nReason:\nThe indirect command statement number entered is not in the 5 digit numeric range of 199999.\nAction:\nEnter a valid statement number.\n 1575", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "944f961facd8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN1258\nIndirect command number xxxxx does not exist.\nReason:\nAn indirect GOTO or a CNTL=GO,...C,EXEC= command was issued to indirect command statement number xxxxx which\nhas not been defined.\nAction:\nChange the number or add a statement with that value.\nCAIN1259\nIndirect command limit exceeded for program request ignored.\nReason:\nThe number of indirect command statements entered for the program/terminal exceeds the maximum amount specified in\nIN25OPTS value ICMDMAX.\nAction:\nReduce indirect commands or increase IN25OPTS ICMDMAX value.\nCAIN1260\nIndirect command input format is invalid.\nReason:\nThe indirect command entered contains a missing or incomplete statement number or command text.\nAction:\nComplete the command and continue.\nCAIN1261\nIndirect commands added.\nReason:\nOne or more indirect command statements were added for the program/terminal.\nAction:\nNone.\nCAIN1262\nIndirect commands deleted.\nReason:\nOne or more indirect command statements were deleted for the program/terminal.\nAction:\nNone.\nCAIN1263\nIndirect commands replaced.\nReason:\nOne or more indirect command statements were replaced for the program/terminal.\nAction:\nNone.\n 1576", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0cab501296fe-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN1264\nEnd of indirect commands.\nReason:\nThe indirect commands display screen was positioned on the last command statements defined for the program/terminal.\nAction:\nNone.\nCAIN1265\nInvalid indirect command.\nReason:\nThe indirect command verb entered is not a valid command, is misspelled, or requires more characters to remove\nambiguity.\nAction:\nCorrect the command and continue.\nCAIN1266\nMaximum indirect command execution count reached.\nReason:\nThe number of indirect commands executed exceeds the maximum amount specified in IN25OPTS value ICMDEXE. A\npossible indirect command logic loop exists.\nAction:\nReduce the number of commands executed or increase ICMDEXE value.\nCAIN1267\nGOTO, EXIT or BREAK command missing processing terminated.\nReason:\nThe last indirect command was executed for a program/terminal without a following GOTO, EXIT, or BREAK/PAUSE\ncommand. The default BREAKpoint action was performed.\nAction:\nTerminate the command set with a GOTO, EXIT, or BREAK command.\nCAIN1268\nIndirect command function not supported.\nReason:\nFunction is obsolete, not yet supported or invalid in the current debugging mode.\nAction:\nCorrect the erroneous command and continue.\nCAIN1269\nIndirect command syntax error.\nReason:\nAn indirect command's arguments do not follow the rules of the indirect command verb specified.\nAction:\nCorrect the command and continue.\n 1577", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "88edc8cfdd43-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN1270\nMaximum level of active perform commands reached.\nReason:\nThe level of active PERFORM commands has reached the maximum of 5. A possible indirect command logic loop exists.\nAction:\nReduce the number of PERFORMs executed or check for looping.\nCAIN1271\nNo equated data names exist for this program.\nReason:\nUndefined.\nAction:\nUndefined.\nCAIN1272\nEquated data name limit (10) exceeded request ignored.\nReason:\nAn indirect EQUATE command was entered for the 11th time, exceeding the maximum allowable number.\nAction:\nReplace an existing EQUATE statement or use full data name.\nCAIN1273\nEquate symbol not defined.\nReason:\nUndefined.\nAction:\nUndefined.\nCAIN1274\nEquate symbol previously defined.\nReason:\nAn indirect EQUATE command was specified for an equated symbol that already exists in another statement.\nAction:\nReplace the original EQUATE statement or use another symbol.\nCAIN1275\nInvalid expression.\nReason:\nAn indirect command numeric expression contains unmatched parenthesis or invalid values or operators.\nAction:\nCorrect the command and continue.\nCAIN1276\nArithmetic expression error.\nReason:\n 1578", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a16f60052c22-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAn indirect command contains an illegal mathematic expression or exceeds the 18digit numeric limit.\nAction:\nCorrect the command and continue.\nCAIN1277\nEquate symbol length cannot exceed 8 characters.\nReason:\nAn indirect EQUATE command was specified with a symbol longer than the maximum allowable length of 8.\nAction:\nCorrect the command and continue.\nCAIN1343\nThis storage cannot be located without a locator(>).\nReason:\nUndefined.\nAction:\nUndefined.\nCAIN1344\nToo many procedure or embeddedprogram names in command\nReason:\nAn indirect command was specified with a data name containing more than 1 procedure name delimiter characters ':'.\nAction:\nCorrect the command and continue.\nCAIN1345\nBit value should be enclosed in quotes.\nReason:\nUndefined.\nAction:\nUndefined.\nCAIN1346\nCannot find based variable locator table.\nReason:\nUndefined.\nAction:\nUndefined.\nCAIN1347\nThis type of move is not supported in this release.\nReason:\nUndefined.\nAction:\nUndefined.\n 1579", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5e6806550672-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN1348\nThis dataname reference is ambiguous; you must qualify.\nReason:\nUndefined.\nAction:\nUndefined.\nCAIN1349\nData name was not found in named procedure.\nReason:\nUndefined.\nAction:\nUndefined.\nCAIN1350\nArray information not found; data name is not an array.\nReason:\nUndefined.\nAction:\nUndefined.\nCAIN1351\nToo many subscripts have been entered in the command.\nReason:\nUndefined.\nAction:\nUndefined.\nCAIN1358\nSpare msg area .\nReason:\nUndefined.\nAction:\nUndefined.\nCAIN1701\nENTER THE SQL COMMAND TO BE EXECUTED.\nReason:\nInstructional message.\nAction:\nEnter the SQL command to be executed on the FILE screen. Refer to CICS Debugging for a list of valid commands.\nCAIN1702\n(*) INVALID SQLTYPE.\nReason:\n 1580", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f8e6a0269871-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe SQL type that you entered was invalid.\nAction:\nRefer to CICS Debugging for a list of valid SQL types and commands.\nCAIN1703\nLOC MUST BE NUMERIC FROM 1 9999\nReason:\nYou entered a character other than 1 to 99999, which is not considered numeric.\nAction:\nSpecify data in hexadecimal format (for example X'F1F2F3') or as data without quotes (for example, 1234).\nCAIN1704\n(*) EXECUTED SUCCESSFULLY.\nReason:\nThe command you specified executed successfully.\nAction:\nNone.\nCAIN1705\n(*) COMMAND NOT SUPPORTED.\nReason:\nThe command that you entered is not supported by InterTest for CICS.\nAction:\nRefer to CICS Debugging for a list of valid commands.\nCAIN1706\nNO SAVED COMMANDS.\nReason:\nYou either did not specify a valid save command, or you cleared the screen and did not save your commands.\nAction:\nEnter the correct save command.\nCAIN1707\nTRANSMIT ERROR.\nReason:\nWhen you pressed ENTER or one of the PF keys, it did not take effect.\nAction:\nPress the proper PF key.\nCAIN1708\nMODIFY COMMAND OR PRESS ENTER TO EXECUTE.\nReason:\nInstructional message.\nAction:\nModify the command or press ENTER to execute it.\n 1581", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dbcf4fd5aed7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN1709\n(*) ROWS SELECTED.\nReason:\nThe rows that you specified were selected.\nAction:\nNone.\nCAIN1710\nNO ROWS SELECTED\nReason:\nThe number of rows you specified was not selected.\nAction:\nReenter the number of rows.\nCAIN1711\nSQL/DS NOT ACTIVE.\nReason:\nA DB2 request received an \"AEYA\" abend, which usually means SQL/DS is not active.\nAction:\nEnsure that SQL/DS is correctly defined in your CICS region.\nCAIN1712\nDSNC NOT ACTIVE OR DB2 NOT AVAILABLE.\nReason:\nA DB2 request received an \"AEYA\" abend, which usually means DB2 is not active.\nAction:\nEnsure that SQL/DS is correctly defined in your CICS region.\nCAIN1714\nENTER C TO COMMIT, R TO ROLLBACK.\nReason:\nYou must commit your previous changes or roll them back.\nAction:\nEnter C or R.\nCAIN1713\n(*) ABEND HAS OCCURRED.\nReason:\nA DB2 request received a CICS abend other than \"AEYA\".\nAction:\nRefer to your CICS MESSAGES and CODES manual.\nCAIN1715\nERROR HAS OCCURRED\nReason:\n 1582", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cc0ef30dddb5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nA CICS transient data write error has occurred. The EIBRCODE field identifies the error code, which can be found in your\nCICS Application Programming Reference.\nAction:\nCorrect the error, and resubmit the request.\nCAIN1716\nENTER X TO REEXECUTE OR M TO MODIFY A COMMAND\nReason:\nInformational message.\nAction:\nNone.\nCAIN1717\n(*) RECORDS INSERTED\nReason:\nDuring the FILE transaction, you added the number of records indicated in the message.\nAction:\nNone.\nCAIN1718\n(*) RECORDS DELETED\nReason:\nThe DEL function executed successfully.\nAction:\nNone.\nCAIN1719\n(*) RECORDS UPDATED\nReason:\nYou have successfully updated the number of records indicated in the message.\nAction:\nNone.\nCAIN1720\nDATA TABLE ROW > 65K\nReason:\nThe Data Table Row is greater than 65K.\nAction:\nExamine your program; reduce the Data Table Row to less than 65K.\nCAIN1901\n(*) FUNCTION IS NOT AVAILABLE ON THIS TERMINAL.\nReason:\nOn this type of terminal, the function you specified is invalid.\nAction:\nSee Configuring for a list of valid functions for your terminal.\n 1583", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9231decbea05-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN1902\n(*) FUNCTION TERMINATED.\nReason:\nA Clear or PF3 key was entered, and the HELP transaction was terminated.\nAction:\nNone.\nCAIN1903\n(*) FUNCTION VSAM ERROR ON CA InterTest HELP FILE\nReason:\nA VSAM error occurred on the Help File.\nAction:\nContact the systems programmer. Determine the problem with the file.\nCAIN1904\n(*) FUNCTION END OF FILE.\nReason:\nWhile you were browsing a file, an end of file condition occurred.\nAction:\nEither enter 'PREV' or a previous code, or browse using a different key, or end this file function.\nCAIN1905\n(*) FUNCTION INCORRECT FCT ENTRY FOR CA InterTest HELP FILE.\nReason:\nThe HELP file was incorrectly defined to your system.\nAction:\nContact the system programmer.\nCAIN1906\n(*) FUNCTION HELP FILE COULD NOT BE OPENED.\nReason:\nInformation about the requested function could not be obtained, because the Help File could not be opened.\nAction:\nEnsure that the Help File is properly defined to the region and is not disabled.\nCAIN1908\n(*) FUNCTION HELP FILE IS NOT OPEN.\nReason:\nInformation on the requested function could not be obtained because the Help File is not open.\nAction:\nOpen the Help File and reenter your request.\nCAIN1909\n(*) FUNCTION HELP FILE INCOMPLETE.\nReason:\n 1584", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8e8d741d409b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInformation on the requested function could not be obtained because the Help File cannot be accessed.\nAction:\nCheck the status of the Help File to ensure that it is enabled. Rerun the IDCAMS repro to recreate the Help File, if\nnecessary.\nCAIN1910\n(*) FUNCTION NO MAIN STORAGE AVAILABLE.\nReason:\nThere is not enough space available in main storage to complete your request.\nAction:\nWhen storage becomes available, reenter your request.\nCAIN1911\nINVALID TRANSACTION\nReason:\nThe transaction that you entered was not a valid InterTest for CICS transaction.\nAction:\nCorrect your error and reenter the proper transaction code.\nCAIN1912\nINTERTEST RELEASE (*) NOT COMPATIBLE WITH CICS RELEASE (*)\nReason:\nThe version of InterTest for CICS that you are running is not supported by the installed version of CICS.\nAction:\nInstall the correct version of InterTest for CICS.\nCAIN1913\nNOTAUTH CONDITION RESOURCE LEVEL SECURITY FAILED FOR \"(*)\"\nReason:\nThe resource that you named failed the resource level security check.\nAction:\nDetermine the reason for the failure, and change the security parameters if necessary.\nCAIN2301\nENTER data or CLEAR to exit from menu.\nReason:\nNo data has been entered on the menu screen.\nAction:\nEnter data or Clear to exit from menu.\nCAIN2302\nPROG, TRAN, or TERM names not allowed for systemwide functions.\nReason:\nThis was a restriction in InterTest for CICS version 2.3. These entries are ignored in InterTest for CICS version 2.4 and\nlater.\nAction:\n 1585", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a0be8e7e6fad-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nErase highlighted entries.\nCAIN2303\nPrograms, transactions, and terminals may not be combined in the same command.\nReason:\nMonitoring options can be specified to programs, transactions, or terminals.\nAction:\nMake separate entries for programs, transactions, and terminals.\nCAIN2304\nMissing or invalid function number.\nReason:\nThe entered function is blank or not A through L.\nAction:\nEnter function A through L or Clear to exit menu.\nCAIN2305\nEntry Required if interval or queue or terminal entered.\nReason:\nA time interval was entered and neither PURGE nor CKPT was selected or, ABP terminal was entered with ABP.\nAction:\nEnter on/off for desired function.\nCAIN2306\nInvalid fields highlighted. Correct and press ENTER.\nReason:\nThe keyword ON/OFF was not entered on the SystemWide Options Menu.\nAction:\nEnter the keyword ON or OFF.\nCAIN2307\nProgram, transaction, or terminal entries required for selected function.\nReason:\nFunction A through H was entered on the function selection menu and no program, transaction or terminal identification\nwas entered.\nAction:\nEnter at least one program or transaction or terminal identification.\nCAIN2308\nInvalid function specified. Letters A N only.\nReason:\nNo entry was entered on the Function Selection Menu.\nAction:\nEnter Function A through N or Clear to exit menu.\n 1586", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f929a0ec4e1d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2309\nInvalid PF key entered.\nReason:\nOne of the listed PF keys was not entered.\nAction:\nChoose one of the listed PF keys.\nCAIN2310\nEnter location in only one format.\nReason:\nMore than one format has data entered.\nAction:\nEnter data in only one format.\nCAIN2311\nOne element must be entered for each side of the condition.\nReason:\nData was entered for one side of the condition and not the other on the Conditional Breakpoint Menu.\nAction:\nEnter data for the other side of the condition.\nCAIN2312\nTask cannot be both abended and resumed at a new location.\nReason:\nData was entered in the RESUME EXECUTION and the ABEND fields on the Resume Task Execution Menu.\nAction:\nSelect one of these options.\nCAIN2313\nTask cannot be both abended and singlestepped.\nReason:\nData was entered in the SINGLE STEP and ABEND fields on the Resume Task Execution Menu.\nAction:\nSelect one of these options.\nCAIN2314\nAbend and dump options was allowed together.\nReason:\nData was entered in the DUMP and ABEND fields on the Resume Task Execution Menu.\nAction:\nSelect one of these options.\nCAIN2315\nCommand not processed. Correct and resubmit or CLEAR to exit from menus.\nReason:\n 1587", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e131527a65b1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe generated command was incorrect.\nAction:\nContact Broadcom Support .\nCAIN2316\nReplaced and replacement program names must both be entered.\nReason:\nData entered in only one side of the replace program name option on the Replacement Options Menu.\nAction:\nEnter data in both fields.\nCAIN2317\nReplaced and replacement file names must both be entered.\nReason:\nData was entered in only one side of the Replace file name option on the Replacement Options Menu.\nAction:\nEnter data in both fields.\nCAIN2318\nReplaced and replacement Transient Data queue names must both be entered.\nReason:\nData was entered in only one side of the Replace TD queue name option on the Replacement Options Menu.\nAction:\nEnter data in both fields.\nCAIN2319\nReplaced and replacement Temporary storage masks must be entered.\nReason:\nData was entered in either the TS selection on TS replacement mask fields on the Replacement Options Menu.\nAction:\nEnter data in both fields.\nCAIN2320\nBypass FROM and TO addresses must both be entered.\nReason:\nData was entered in either the FROM or TO fields of the Bypass Storage Protection option on the Protection Options\nMenu.\nAction:\nEnter data in both the FROM and TO fields.\nCAIN2321\nCSA/CWA offset and length must both be entered.\nReason:\nData was entered in either the Offset or Length fields of the unprotect CSA option or the CWA option on the Protect\nOptions Menu.\nAction:\n 1588", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "38ed8ced3efc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nEnter data in both the offset and length fields of the CSA or the CWA options.\nCAIN2322\nUnprotect address and length must both be entered.\nReason:\nData was entered in either the Address or Length fields of the unprotect main storage area option on the Protection\nOptions Menu.\nAction:\nEnter data in both fields.\nCAIN2323\nProtect address and length must both be entered.\nReason:\nData was entered in either the Address or Length fields of the protect main storage area option on the Protection Options\nMenu.\nAction:\nEnter data in both fields.\nCAIN2324\nEnter only one element for each side of condition.\nReason:\nData was entered in more than one field that is used for either the Left Side or the Right Side of the condition on the\nConditional Breakpoint Menu.\nAction:\nErase the data in all fields but one.\nCAIN2325\nInvalid operator. Enter EQ, NE, GT, LT, GE, or LE.\nReason:\nOne of the shown operators was not selected on the Conditional Breakpoint Menu.\nAction:\nEnter one of the six displayed operators.\nCAIN2326\nLeft side length must be entered\nReason:\nA packed decimal literal was entered in the literal field and no length was specified for the leftside comparison on the\nConditional Breakpoint Menu.\nAction:\nSpecify the length for the leftside condition.\nCAIN2327\nRight side length must be entered\nReason:\nYou did not enter a length for the rightside comparison on the Conditional Breakpoint Menu.\nAction:\n 1589", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3da69ee46a86-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSpecify a length for the rightside condition.\nCAIN2328\nInterval required for CKPT or PURGE ON\nReason:\nThe keyword 'ON' was entered in the PURGE and/or CHKPT fields without an interval specified on the Systemwide\nOptions Menu.\nAction:\nSpecify a time interval.\nCAIN2329\nProgram invalid or NEW option or SYM option not specified\nReason:\nData was entered in the program name field for the NEW and/or SYM option, but no function was selected on the Utility\nOptions menu.\nAction:\nSelect the desired function.\nCAIN2330\nProgram required with NEW or SYM option\nReason:\nThe SYM or NEW option was selected on the Utility Options Menu, but the associated program name field was left blank.\nAction:\nSpecify a program name.\nCAIN2331\nModifier must begin with =, , or .\nReason:\nData was entered in the Optional Offset Field without the proper lead character on the Conditional Breakpoint Menu.\nAction:\nStart the data with one of the shown characters.\nCAIN2332\nProgram name not found in PPT.\nReason:\nThe program name entered on the Function Selection Menu or on the Utility Options Menu does not have a PPT entry.\nAction:\nEnter the name of a valid program. Check the PPT Table.\nCAIN2333\nTransaction code not found in PCT.\nReason:\nThe transaction name entered on the Function Selection Menu does not have a PCT entry.\nAction:\nEnter the name of a valid transaction.\n 1590", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "863c2479794f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2334\nTerminal name not found in TCT.\nReason:\nThe terminal identification entered on the Function Selection Menu or the SystemWide Menu was not found in the TCT.\nAction:\nEnter a valid terminal identification.\nCAIN2335\nNext function invalid or missing.\nReason:\nUndetermined.\nAction:\nContact Broadcom Support .\nCAIN2336\nEnter one or more locations or CLEAR to exit.\nReason:\nNo data was entered on the Breakpoint Locations Menu.\nAction:\nEnter data or Clear to exit.\nCAIN2337\nID numbers cannot be entered in combination with any other fields.\nReason:\nData was entered in one or more of the Identification # fields as well as in a location, loop control number, or terminal\nidentification field on the Remove Breakpoint Menu.\nAction:\nIf ID numbers are entered, they must be the only fields entered on this menu.\nCAIN2338\nTask number required when not at a breakpoint.\nReason:\nNo data was entered in the task number field of the Resume Task Execution Menu.\nAction:\nEnter a valid task number.\nCAIN2339\nMaximum of 9 locations allowed in one command.\nReason:\nMore than nine locations were entered on the Breakpoint Locations Menu.\nAction:\nEnter a maximum of nine locations.\nCAIN2340\nParagraph name, Assembler or PL1 label cannot start with a period.\n 1591", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f145de2638d9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nData entered started with a period on the Breakpoint Locations Menu.\nAction:\nRemove the leading period.\nCAIN2341\nBreakpoints can be set or removed on only one program\nReason:\nMultiple program names were entered together with functions11 through 13 on the Function Selection Menu.\nAction:\nSpecify only one program name.\nCAIN2342\nBreakpoints cannot be set or removed on a transaction\nReason:\nBreakpoints may only be set for a program on the Function Selection Menu.\nAction:\nRemove the transaction ID, and enter a program name.\nCAIN2343\nBreakpoints cannot be set or removed on a terminal\nReason:\nBreakpoints may only be set on the Function Selection Menu.\nAction:\nRemove the terminal ID, and enter a program name.\nCAIN2344\nLIST, SYM or INQ must be chosen when using TD queue\nReason:\nA TD queue was chosen to receive a report from the Utility Options Menu, but no keyword was entered.\nAction:\nSpecify LIST, SYM, or INQ in addition to the name of a TD queue.\nCAIN2345\n.ALL not acceptable for a set option ON command\nReason:\nALL is acceptable only when removing options specified on the Protection Options Menu.\nAction:\nPress PF8 to return to the Main Menu, then enter R to remove protection.\nCAIN2346\n.ALL and OFF not acceptable for TON ON command.\nReason:\nInvalid data was entered for the Limit monitoring function on the Replacement Options or on the Protection Options Menu.\nAction:\nEnter a * or a valid terminal identification.\n 1592", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6189020efd17-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2347\nDump codes may not begin with the letter \"A\".\nReason:\nA dump code beginning with the letter A was entered on the Resume Task Execution Menu.\nAction:\nChange the first letter.\nCAIN2348\nNEW and SWI cannot both be entered. (2.42 Users Only)\nReason:\nBoth New and SWI functions were selected on the Utility Options Menu.\nAction:\nSelect one or the other function.\nCAIN2349\nPURGE and CKPT cannot both be entered.\nReason:\nBoth functions were selected on the SystemWide Options Menu.\nAction:\nSelect one or the other function.\nCAIN2350\n.ANY only acceptable for setting conditional breakpoints.\nReason:\nInvalid data was entered on the Breakpoint Locations Menu.\nAction:\nEnter valid data or press PF9.\nCAIN2351\nS or R indicator is required for this function\nReason:\nFunction 10 through 22 was entered on the Function Selection Menu, but S (set) or R (remove) was not specified.\nAction:\nSpecify either S or R with these functions.\nCAIN2352\nBreakpoints cannot be set on program = .ALL or .OPTIONS\nReason:\nBreakpoints cannot be set on a global basis.\nAction:\nEnter a specific program name.\nCAIN2353\nALL cannot be requested in combination with individual entries\nReason:\n 1593", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c6a124fcb69c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nGlobal options cannot be set with options for specific program names.\nAction:\nSet options either globally or for individual program names.\nCAIN2354\nMaximum of 9 entries allowed in one command\nReason:\nMore than 9 entries were specified on the Breakpoint Locations Menu.\nAction:\nEnter a maximum of 9 locations.\nCAIN2355\nSTATUS report unavailable no program, transaction or terminal id\nReason:\nFunction 30 was requested on the Main Menu, but no program, transaction or terminal ID was entered.\nAction:\nEnter at least one program name, transaction code or terminal ID when you specify Function 30.\nCAIN2356\nBreakpoints cannot be set on generic program name\nReason:\nA generic value was specified as the program name.\nAction:\nEnter a specific program name.\nCAIN2357\nEnter one of the two options for abending task\nReason:\nFrom the Resume Task Menu, the task cannot be abended without specifying an abend code or \"XXXX\" to abend without\na dump.\nAction:\nSpecify either an abend code or 'X' to abend without a dump.\nCAIN2358\nThis feature will be available in general release\nReason:\nThis feature is not available with this release of InterTest for CICS, but is available with the specified release.\nAction:\nNone.\nCAIN2359\nComposite support not removed. Use function 10 to remove monitoring\nReason:\n'R' was entered with Function 23 to remove monitoring from a composite program.\nAction:\nUse Function 10 to remove monitoring.\n 1594", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "413e59d8ac74-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2360\nComposite support cannot be set on generic program\nReason:\nA generic value was entered as the program name.\nAction:\nEnter a specific program name.\nCAIN2361\nComposite support can be set on only one program\nReason:\nMultiple program names were entered for Function 23.\nAction:\nEnter only one program name.\nCAIN2362\nProgram required for selected function\nReason:\nThe function selected also requires that a program name be specified.\nAction:\nSpecify a program name.\nCAIN2363\nComposite support cannot be set on a transaction\nReason:\nComposite support can only be set on a program.\nAction:\nDelete the transaction name and specify a program name.\nCAIN2364\nComposite support cannot be set on a terminal\nReason:\nComposite support can only be set for a program.\nAction:\nDelete the terminal ID, and specify a program name.\nCAIN2365\nComposite support cannot be set on a subprogram\nReason:\nThe name specified in the program name field is not the PPT name for the module.\nAction:\nSpecify the PPT of the composite module.\nCAIN2366\nFunctions 13 and 23 are not available under CICS release 1.5\nReason:\n 1595", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "de0781a2cee2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nRequest breakpoints and composite support are not available with this release of CICS.\nAction:\nNone.\nCAIN2367\nFollow options available under CICS release 1. are ON or NOPPT\nReason:\nThe FOL= PPTname Option is not supported by this release of CICS.\nAction:\nEnter either 'ON' or 'NO PPT'.\nCAIN2368\n# of seconds must be within the range 1-5*\nReason:\nThe wait amount does not contain a value from 1 through 59.\nAction:\nSpecify the number of seconds from 1 to 59 for the wait amount.\nCAIN2369\nEnter one of the two options for halting AUTO STEPPING\nReason:\nThe stop value does not contain the word \"CALL\" or a numeric value of 1 through 9999.\nAction:\nSpecify the word 'CALL' or enter a value from 1 to 9999.\nCAIN2370\nThe HALT value range is 1 999\nReason:\nThe data entered in the STDA value field is not in the range of 1 through 9999.\nAction:\nSpecify a value of 1 through 9999.\nCAIN2371\nYou must specify a WAIT value with a HALT value\nReason:\nEither the wait value or the halt value was left blank.\nAction:\nSpecify valid values for the wait field and the halt field.\nCAIN2372\nAUTO STEP value must be specified with WAIT and HALT values\nReason:\nEither the wait value or the stop value is missing.\nAction:\nSpecify a valid wait value and halt value.\n 1596", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9dd5e3ac041c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2373\nDB2 cannot be requested in combination with CALLs\nReason:\nYou attempted to set request breakpoints at both CALLs to DB2 and all IN25UEXI defined CALLs.\nAction:\nSpecify either CALLs or DB2.\nCAIN2374\nPress Enter to process commands shown, CLEAR to exit.\nReason:\nInstructional message.\nAction:\nPress Enter to execute the displayed commands. Press Clear to exit from this display.\nCAIN2375\nPress Enter to continue or CLEAR to exit from menu\nReason:\nInstructional message.\nAction:\nPress Enter to continue with the specified function. Press Clear to exit from the menu.\nCAIN2376\nInvalid PF key entered\nReason:\nYou entered a PF key that is not available with this screen.\nAction:\nSpecify a valid PF key.\nCAIN2377\nTransaction terminated, GETMAIN failed\nReason:\nThere was not enough storage available to complete this request.\nAction:\nWhen storage space becomes available, reenter your request.\nCAIN2378\nCommand not processed fatal error\nReason:\nAn internal error has occurred in InterTest for CICS.\nAction:\nObtain a dump, and contact Broadcom Support .\nCAIN2379\nMenu processing ended\nReason:\n 1597", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c9818282851f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nYou pressed Clear to exit the menu.\nAction:\nNone.\nCAIN2380\nInternal error command not processed\nReason:\nAn internal error has occurred in InterTest for CICS.\nAction:\nObtain a dump and contact Broadcom Support .\nCAIN2381\nUse LIST to set/remove options on duplicate subprograms\nReason:\nA duplicate subroutine has been declared for monitoring. The LIST facility or transaction must be used to set/remove\noptions on a duplicate subroutine. The COMPOSITE command must be used in the LIST facility to declare the\nsubprogram's owning load module.\nAction:\nUse the COMPOSITE command in the LIST facility.\nCAIN2390\nTerminal identifications and ID numbers cannot both be entered.\nReason:\nWhen ID numbers are entered, no other field may have data on the Remove Locations Menu.\nAction:\nRemove data from terminal identification fields.\nCAIN2391\nInvalid special keyword.\nReason:\nThe Special Keyword Field contains invalid data on the Conditional Breakpoint Menu.\nAction:\nPress PF1 to obtain a list of valid keywords.\nCAIN2392\nInvalid message number passed to message module.\nReason:\nUndetermined.\nAction:\nFor assistance, contact Broadcom Support .\nCAIN2393\nSegmented monitoring can be set for a program only.\nReason:\nSegmented monitoring cannot be set for a transaction or terminal ID. It can be set for a program only.\nAction:\n 1598", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1e16387088fe-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSpecify a valid CICS program name.\nCAIN2394\nTerminal ID or user ID required for DM option.\nReason:\nA specific terminal ID or user ID is required to enable data monitoring.\nAction:\nSpecify a valid terminal ID or user ID.\nCAIN2501\nEnter only one area to be displayed.\nReason:\nYou have specified more than one area to be displayed.\nAction:\nOn the CORE=Bkpt for Assembler programs menu enter data in the special element fields or the Assembler base and\nLabel fields or the Assembler base and Label fields or the Register # field or the Argument # field.\nOn the CORE=Bkpt for COBOL programs menu enter data in the COBOL name field or the special element field.\nOn the CORE=Bkpt for PL/I programs menu enter data in the PL/I data name field or the Special element field.\nOn the CORE=Syst menu enter data in the CICS AREA field or the ADDRESS field or the one of the CICS TABLE entry\nfields.\nCAIN2502\nInvalid PF key entered.\nReason:\nOne of the listed PF keys was not entered.\nAction:\nChoose one of the listed PF keys.\nCAIN2503\nNonnumeric characters found in numeric field.\nReason:\nCharacters other than 0 9 have been entered in a numeric field.\nAction:\nEnter valid numeric characters 0 9.\nCAIN2504\nAssembler base and label must be entered together.\nReason:\nData was entered in one but not both of the fields on the CORE=Bkpt menu for Assembler programs.\nAction:\nEnter data in both fields.\nCAIN2505\nWhen Getmain parameters are entered, no other entries area allowed.\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1e16387088fe-1", "text": "When Getmain parameters are entered, no other entries area allowed.\nReason:\nBoth the Task AREA and the GET STORAGE size fields have data entered on the CORE=TASK Menu.\n 1599", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3d333f07d122-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nRemove the data from one of the fields.\nCAIN2506\nInvalid fields highlighted. Correct and press enter.\nReason:\nAn invalid keyword has been entered in either the CICS area field of the CORE=Syst Menu, the Task AREA of the\nCORE=Task Menu or the special element field of the CORE=BKPT Menu.\nAction:\nPress PF1 to obtain the list of all valid keywords.\nCAIN2507\nScan value and length must both be entered.\nReason:\nOnly one of the above two fields has data entered.\nAction:\nEnter data in both fields.\nCAIN2508\nValue must be X,C,P,F, or H followed by '...'. X and C can be combined.\nReason:\nThe new data field starts with something other than the valid letters in the message.\nAction:\nCorrect, and enter data.\nCAIN2509\nSpecify location or special element or MOVE from and to.\nReason:\nEither no field has data entered on the CORE=Bkpt Menu for COBOL programs or only a SCAN, an existing data field or\na new data field, has data entered.\nAction:\nEnter data in the COBOL name, special element, or MOVE fields.\nCAIN2510\nProgram name required when LOAD, DELETE or MAP is requested.\nReason:\nA request was made to load or delete without entering a program name.\nAction:\nEnter a program name.\nCAIN2511\nSCAN backward request is invalid without scan value and length.\nReason:\nA request was made to scan backwards without entering data in the Scan value and Scan range fields.\nAction:\nEnter data in both fields.\n 1600", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6c345e0c18f3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2512\nEnter data or CLEAR to exit.\nReason:\nNo data was entered on the CORE=Syst menu.\nAction:\nEnter data or Clear to exit.\nCAIN2513\nGetmain size is required when class or initial value is entered.\nReason:\nA request was made to GET STORAGE but only the class and/or the Initial value fields had data entered.\nAction:\nEnter a number in the Size field.\nCAIN2514\nOffset must start with ,+,, or %.\nReason:\nData was entered in the Optional Offset field that did not start with the ,+,, or % special character.\nAction:\nBegin the data with one of the special characters.\nCAIN2515\nTask number must be numeric.\nReason:\nA nonnumeric task number has been entered.\nAction:\nEnter a task number that consists of numbers.\nCAIN2516\nValue must be X'...', C'...', or combinations.\nReason:\nThe existing data field must be either a hexadecimal, or character or combination of the two.\nAction:\nEnter the data in the correct format.\nCAIN2517\nSCAN length must be hex value or decimal number followed by T.\nReason:\nThe data entered in the Scan range field is neither a valid hexadecimal nor decimal number.\nAction:\nEnter a number in the range of 0 F.\nCAIN2518\nBMSG command request ignored; no breakpoint task waiting at terminal.\nReason:\n 1601", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b353235b326a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe special keyword BMSG was requested when there was no breakpointed task waiting at the user's terminal.\nAction:\nSelect another special keyword.\nCAIN2519\nTask number required.\nReason:\nData was entered for a location on either the CORE=Bkpt Menus or the CORE=Task Menu without a task number.\nAction:\nEnter a valid decimal number in the Task number field.\nCAIN2520\nFunction not generated.\nReason:\nThe special keyword selected is not one of the valid keywords.\nAction:\nPress PF1 to obtain a list of all valid keywords.\nCAIN2521\nBoth FROM and TO fields must be entered.\nReason:\nData was entered in either the move from or move to fields of the CORE=Bkpt Menu for COBOL programs.\nAction:\nEnter data in both fields.\nCAIN2522\nWhen MOVE parameters are entered, no other entries are allowed.\nReason:\nData has been entered in some other field than the Move From or Move To fields on the CORE=Bkpt Menu for COBOL\nprograms.\nAction:\nErase data from other fields on the menu.\nCAIN2523\nSpecify location or special element.\nReason:\nThe Optional offset and/or the Scan value and/or VERIFY and/or CHANGE fields have been entered without entering a\nlocation or special element.\nAction:\nEnter a location or a special element.\nCAIN2524\nSpecify area, address, table or program.\nReason:\nData was entered on the CORE=Syst Menu without selecting data in the CICS AREA, ADDRESS, OR CICS TABLE entry\nfields.\n 1602", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "127c5fda31b5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nEnter data in one of the fields.\nCAIN2525\nData name must be entered with Procedure name.\nReason:\nA procedure name followed by a colon was entered in the PL/I data name field on the CORE=Bkpt Menu for PL/I\nprograms without following it with a data name.\nAction:\nAdd a data name after the colon.\nCAIN2526\nThe number of characters entered exceeds 58.\nReason:\nThe total number of characters entered in the fields of the Complex Cobol Data Names Menu is greater than 58.\nAction:\nReduce the total number of characters to 58 or less.\nCAIN2527\nThe first data name field must be entered.\nReason:\nData was not entered in the Data name field of the Complex Cobol Data Names Menu.\nAction:\nEnter the name of the field you wish to display.\nCAIN2528\nInvalid message number, code error.\nReason:\nThe CORE menus have generated an invalid message number.\nAction:\nContact Broadcom Support  with the exact information of the data entered.\nCAIN2529\nNOTAUTH CONDITION RESOURCE LEVEL SECURITY FAILED FOR \"(*)\"\nReason:\nThe named resource failed a resource level security check.\nAction:\nEither use a different resource or obtain the proper authority for the named resource.\nCAIN2530\nMENU PROCESSING ENDED\nReason:\nYou pressed Clear to exit the menu.\nAction:\nNone.\n 1603", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f52261c3d73f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2531\nTRANSACTION TERMINATED, GETMAIN FAILED\nReason:\nThere was not enough storage available to complete this problem.\nAction:\nWhen storage becomes available, reenter your request.\nCAIN2601\nTop row of data table\nReason:\nYou reached the top row of the data table in a structured display.\nAction:\nNone.\nCAIN2602\nBottom row of data table\nReason:\nYou reached the bottom row of the data table in a structured display.\nAction:\nNone.\nCAIN2603\nInvalid monitor name\nReason:\nA monitor name is empty, or you entered an invalid character in a monitor name.\nAction:\nProvide a monitor name. Ensure that you enter the following characters only in a monitor name: A-Z, 0-9, $, @, #.\nCAIN2604\nReview warnings, and press PF5 to monitor composite module\nReason:\nComments have been generated for this display.\nAction:\nReview the comments, and press PF5 to continue.\nCAIN2605\nTable validation OK, press PF5 to monitor composite module\nReason:\nThe data table was validated with no errors or warnings.\nAction:\nTo set composite support, press PF5.\nCAIN2606\nUse plus (+) immediately after ASM components\nReason:\n 1604", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6be1f247e6de-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nYou entered a plus sign (+) after a non ASM or deselected component.\nAction:\nEnter a plus sign (+) immediately after an ASM component. A plus sign can follow another plus sign.\nCAIN2607\nSymbolic retrieval error\nReason:\nSymbolic data retrieval from PROTSYM failed.\nAction:\nEnsure that PROTSYM is accessible. If PROTSYM is accessible, and you still receive this error, contact Broadcom\nSupport .\nCAIN2608\nA monitor name matches a CICS program name\nReason:\nA CICS defined program cannot be specified as a subprogram monitor name.\nAction:\nSpecify a subprogram monitor name that does not match a CICS defined program name. You may need to recompile the\nsubprogram and assign the subprogram a PROTSYM name that does not match a CICS defined program name.\nCAIN2609\nInvalid command\nReason:\nYou entered an invalid command.\nAction:\nEnter a valid command.\nCAIN2610\nArgument <position> not recognized\nReason:\nYou entered an invalid argument in the specified position.\nAction:\nEnter a valid argument.\nCAIN2611\nNot enough arguments; min. number: <number>\nReason:\nYou did not enter the minimum required number of arguments.\nAction:\nEnter the minimum required number of arguments specified in the message.\nCAIN2612\nToo many arguments; max. number: <number>\nReason:\nYou exceeded the maximum allowed number of arguments.\nAction:\n 1605", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "61c6e6398aec-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReduce the number of arguments that you entered to match the allowed maximum number of arguments specified in the\nmessage.\nCAIN2613\nEnter a FIND command\nReason:\nYou did not enter the string that you want to find.\nAction:\nEnter the string that you want to find using the FIND command.\nCAIN2614\nString not found\nReason:\nThe string is not found or you reached the last occurrence of the string that you wanted to find.\nAction:\nNone.\nCAIN2615\nInvalid scroll amount\nReason:\nYou specified a non-numeric value as the scroll amount, or exceeded the maximum scroll limit of 9999 rows.\nAction:\nUse a numeric scroll value lower than or equal to 9999.\nCAIN2616\nDuplicate monitor names not allowed in one composite module\nReason:\nA duplicate monitor name exists in the same composite module.\nAction:\nSpecify a different monitor name.\nCAIN2617\nInvalid PF key\nReason:\nYou pressed an unassigned PF key.\nAction:\nNone.\nCAIN2618\nNOTAUTH condition - resource level security check failed for \"(*)\"\nReason:\nThe named resource failed a resource level security check.\nAction:\nSelect a different resource with the proper authority, or obtain the necessary authority for the named resource.\n 1606", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ad9c5f387a92-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2619\nNo data to display\nReason:\nThere are no subprograms that meet your filter criteria, or you specified a composite load module that could not be found.\nAction:\nApply a filter with less restrictive conditions, and ensure that you specify an existing composite load module.\nCAIN2620\nNot all subprograms are selected\nReason:\nMonitor names for some subprograms are not specified.\nAction:\nTo test the subprograms that are not selected, provide monitor names for the subprograms.\nCAIN2701\nSyntax error in input Message.\nReason:\nThe input message is invalid.\nAction:\nCorrect the input and reenter the request.\nCAIN2702\nRequest disregarded.\nReason:\nInterTest for CICS ignored your request.\nAction:\nCheck to see if your request is valid. Correct and resubmit.\nCAIN2703\nError in Temp. Storage detected.\nReason:\nThe target area is beyond the permitted storage area, which caused an I/O error during the read/write to temporary\nstorage.\nAction:\nNone.\nCAIN2704\nThe task that sent bkpt to this term was not found.\nReason:\nThe terminal that was supposed to receive the breakpoint is out of service or was not found in the Terminal Control Table\n(TCT).\nAction:\nCheck the TCT to find out the status of the terminal.\n 1607", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "74715736b2fd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2705\nError in Transient Data PUT.\nReason:\nThis error occurs when a transient data write operation is requested and a length of zero is specified.\nAction:\nCheck the input length and respecify if necessary.\nCAIN2706\nNo task at a breakpoint found for ?  or *.\nReason:\nThe task requested could not be found at the specified breakpoint.\nAction:\nNone.\nCAIN2707\nSymbolic Facility not supported request ignored\nReason:\nA request was made for symbolic support for a function that does not support symbolic requests, or program symbolics\nwere not found in the Symbolic file of InterTest for CICS.\nAction:\nCheck the Symbolic File.\nCAIN2708\nStorage chains damage detected.\nReason:\nA storage chain has been broken.\nAction:\nNone.\nCAIN2751\nTRANSACTION TERMINATED, GETMAIN FAILED\nReason:\nAn illegal or failed GETMAIN has been terminated.\nAction:\nRetry the transaction. If the error persists, contact Broadcom Support .\nCAIN2752\nCOMMAND NOT PROCESSED FATAL ERROR\nReason:\nAn internal logic error has occurred.\nAction:\nContact Broadcom Support .\nCAIN2753\nMENU PROCESSING ENDED\n 1608", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "39ac7848f5a3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nThe menu processing has ended normally.\nAction:\nNone.\nCAIN2754\nNOTAUTH CONDITION RESOURCE LEVEL SECURITY FAILED FOR \"(*)\"\nReason:\nThe transaction is not authorized to access the program name.\nAction:\nCorrect the authorization settings of the InterTest for CICS transactions.\nCAIN2801\nTRANSACTION TERMINATED, GETMAIN FAILED\nReason:\nAn illegal or failed GETMAIN has been detected, which caused the transaction to be terminated.\nAction:\nRetry the transaction. If the error persists, contact Broadcom Support .\nCAIN2802\nMENU PROCESSING ENDED\nReason:\nThe menu processing has ended.\nAction:\nNone.\nCAIN2803\nCOMMAND NOT PROCESSED FATAL ERROR\nReason:\nAn internal logic error occurred.\nAction:\nContact Broadcom Support .\nCAIN2804\nNOTAUTH CONDITION RESOURCE LEVEL SECURITY FAILED FOR \"(*)\"\nReason:\nA nonauthorized condition was detected.\nAction:\nCheck the condition.\nCAIN2901\nRequested PROGRAM was found in UPDATE MODE\nReason:\nThe only symbolic data that was found for the requested program was in update mode. This may happen when the\nprogram is being compiled or assembled or the InterTest for CICS postprocessor failed to run successfully.\nAction:\n 1609", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "04e55f46831e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nRecompile/assemble your application program.\nCAIN2902\nSequence number is invalid\nReason:\nWhile processing a request, a bad sequence number was found. A sequence number is an internal reference for\nprocessing. This error indicates a corrupted InterTest for CICS Symbolic File.\nAction:\nFor assistance, contact Broadcom Support .\nCAIN2903\nRequested STATEMENT NUMBER is nonnumeric\nReason:\nThe data entered in the Stmt # field was found to contain one or more nonnumeric characters, that is, not within the range\nof 0 through 9.\nAction:\nCorrect the data and resubmit request.\nCAIN2904\nMARGIN value is INVALID\nReason:\nThe data entered in the Margin= field was invalid. Valid entries are 1 to 50.\nAction:\nCorrect and resubmit request.\nCAIN2905\nRequested DISPLACEMENT is not hexadecimal\nReason:\nThe data entered in the Displacement= field contained one or more nonhexadecimal characters. Valid hexadecimal\ncharacters are all numbers from 0 through 9 and all characters from A through F.\nAction:\nCorrect and resubmit request.\nCAIN2906\nInvalid OPTION # entered\nReason:\nThe data entered in the Option # field was invalid.\nAction:\nAfter returning from the HELP facility, press PF4 to display the Lister Profile screen. The two lines, starting at the one\nlabeled OPTS, describes the valid options.\nCAIN2907\nSEARCH ARGUMENT is MISSING\nReason:\nA search request, options 9 or 10, has been made without having any data entered in the Label/Search Arg= field.\nAction:\n 1610", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f7d19f5fea48-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nEnter the search data and retry the request.\nCAIN2908\nMore than ONE REQUEST Submitted\nReason:\nMore than one request was entered, such as a statement number and a displacement request.\nAction:\nCorrect and resubmit request.\nCAIN2909\nRequested Data or Area was NOT FOUND in the saved listing\nReason:\nThe area requested in the Option # field does not exist in the saved listing. This may occur when the InterTest for CICS\npostprocessor was run with a LISTER=REF and OPTION # 6 (crossreference) is requested. This error also occurs when\nOption # 5 (Clist/Pmap) is requested for a COBOL program that was compiled with the CAPEX optimizer. Another reason\nfor this error message is when a Search request, Options 9 or 10, is made for an argument that was not found.\nAction:\nNone.\nCAIN2910\nThe KEY hit was not CLEAR, ENTER or a valid PF KEY\nReason:\nA terminal control key, which does not has an assigned function, has been entered. Examples of this would be, pressing\nPF10 (single step) when a program is not at a breakpoint or pressing the PA1 key.\nAction:\nNone.\nCAIN2911\nProgram is not at a breakpoint GOTO (G) request is ignored\nReason:\nA program must be held at a InterTest for CICS breakpoint to use a GOTO request.\nAction:\nNone.\nCAIN2912\nProgram NOT FOUND in any of the InterTest Symbolic Files\nReason:\nThe name entered in the Program= field could not be found in any the InterTest for CICS symbolic files that are known to", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f7d19f5fea48-1", "text": "this CICS region. Either the program name is not in any of the InterTest for CICS symbolic files, or one or more symbolic\nfiles are inaccessible because they are disabled or not open.\nAction:\nCheck the status of your InterTest for CICS symbolic file by using option 03 of the VRPT transaction. If all the symbolic\nfiles are accessible, compile/assemble the missing program with a procedure that contains a InterTest for CICS\npostprocessor step.\n 1611", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2f1f5772669c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2913\na Program Name was not entered\nReason:\nA program name was missing from the Program= field when an ENTER or PF key was pressed.\nAction:\nEnter the program name and retry request.\nCAIN2914\nxxxxxxxx is defined as a yyyy\nReason:\nA display request for the assembler data item, xxxxxxxx, was rejected because of its data type, yyyy. For example, a\nrequest to display the data name CSAX21, when used in the instruction TM CSAOPREL,CSAX21, would be rejected with\nthe message ' CSAX21 is defined as a MASK '.\nAction:\nNone.\nCAIN2915\nThe CURSOR was placed within a PL/I comment\nReason:\nWhen processing a display request from the lister screen for a PL/I program, the cursor was found placed within a\ncomment.\nAction:\nRetry request with the cursor positioned under a data name.\nCAIN2916\nThe Terminal ID xxxx was not found in the TCT\nReason:\nThe name entered in the Terminal ID = field, from the Profile, could not be found in the Terminal Control Table (TCT).\nAction:\nCorrect the data and resubmit.\nCAIN2917\nBREAKPOINTS may only be set when MONITORING by PROGRAM\nReason:\nThe LISTER facility was entered from a breakpoint and a request to set a breakpoint was made for the displayed program.\nHowever, the program was not being monitored at a program level.\nAction:\nNone.\nCAIN2918\na DISPLAY (D) or MOVE (M) may not be requested at xxxx\nReason:\nThe location, indicated by xxxx , may not be used for a CORE display or move request. This error may occur if a TIOA", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2f1f5772669c-1", "text": "compression package is installed in the system. You may also receive the CAIN2919 and CAIN2954 messages.\nAction:\nEnsure that all InterTest for CICS transactions are not affected by any TIOA compression packages.\n 1612", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0b306d5364d1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2919\nan InterTest option may not be set at XXXXX\nReason:\nInterTest options - breakpoints, may not be set at the location XXXXX. This error may occur if a TIOA compression\npackage is active in system. You may also receive the CAIN2918 and CAIN2954 messages.\nAction:\nEnsure that all of the InterTest for CICS transactions are not affected by any TIOA compression packages.\nCAIN2920\na GOTO (G) request may not be requested at XXXXX\nReason:\nThe location, indicated by xxxxx, is not a valid location for a GOTO request. This error occurs when the request is made at\na data names definition.\nAction:\nRetry the GOTO request at a valid location.\nCAIN2921\nList composite mode set. Enter subprogram to add/remove breakpoints\nReason:\nThe composite command has completed successfully, and the current composite load module has been established. The\ncurrent composite load module is used as a qualifier when setting breakpoint options on composite subroutines.\nAction:\nNone.\nCAIN2922\nComposite mode set for load module xxxxxxxx\nReason:\nYou tried to display a subroutine that is part of one or more monitored composite load modules.\nAction:\nIf you want to refer to a subroutine that belongs to a different composite module, specify the name of the desired\ncomposite module in the Program window.\nCAIN2923\nVSAM ERR CODE=xx RETURN CODE=yy\nReason:\nA VSAM request, for the InterTest for CICS Symbolic File has failed. The message provides you with the VSAM ERROR\nCODE (in hex) and the VSAM RETURN CODE (in hex).\nAction:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0b306d5364d1-1", "text": "CODE (in hex) and the VSAM RETURN CODE (in hex).\nAction:\nLook up the VSAM ERROR and RETURN CODE in your VSAM manual and then take the recommended action. Note:\nThe lister transaction terminates on any input after this message is displayed.\nCAIN2924\na DISPLAY (D) request must be the ONLY request entered from the screen\nReason:\nA request to display data has been entered along with other types of requests. For example, a display request is entered\non one line and a request to set a breakpoint is entered on another line.\n 1613", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "64f1f09d3d59-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nYou may either remove the display requests and process or remove the other requests and process.\nCAIN2925\nOnly ONE GOTO (G) request may be entered from the screen\nReason:\nMore than one GOTO request, G, has been entered on the source display.\nAction:\nRemove all of the GOTO except for the one that is required and press the ENTER key to process.\nCAIN2926\nNo Listing was saved for the requested program\nReason:\nThe LISTER= option was not specified when doing the InterTest Batch postprocessor step for this program.\nAction:\nRecompile or reassemble the application program with the InterTest Batch postprocessor step that has the LISTER+\noption specified.\nCAIN2927\nOnly one Conditional Breakpoint (C) request may be entered\nReason:\nMore than one request to set a conditional breakpoint, C, was found after examining the screen input.\nAction:\nAfter returning from the help facility, remove all but one of the conditional breakpoint requests and press the ENTER key.\nAfter that request has been processed, you may make the next conditional breakpoint request.\nCAIN2928\nScreen request was not valid\nReason:\nA character was entered at the beginning of a displayed line of source that has no function. Valid characters are B C D M\nU X + @ %.\nAction:\nRemove or change any invalid characters that were entered on the screen and retry request.\nCAIN2929\nAbend Code Options:\nReason:\nInterTest for CICS detected an abend in the program.\nAction:\nCall Broadcom Support .\nCAIN2930\nAbend Codes that start with the letter A are invalid\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "64f1f09d3d59-1", "text": "CAIN2930\nAbend Codes that start with the letter A are invalid\nReason:\nAn abend request has been made with an abend code that starts with the letter A. Abend codes that start with the letter A\nare restricted to IBM usage.\n 1614", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3a537be3506d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nRequest the abend with a different abend code.\nCAIN2931\nInvalid data was entered in the Display titles = field\nReason:\nThe data entered did not contain one of the following values:\nY\nDisplay with titles\nN\nDisplay without titles\nR\nDisplay registers instead of titles\nAction:\nCorrect data and retry request.\nCAIN2932\nNonnumeric data was entered in the Stepping amount = field\nReason:\nThe data entered was found to contain one or more nonnumeric characters.\nAction:\nCorrect the data and retry request.\nCAIN2933\nInvalid data was entered in the PF7/8 amount = field\nReason:\nThe data entered was not one of the following:\nPAGE\nScroll forward or backward a full page\nHALF\nScroll forward or backward a half page\nSTOP\nScroll to the next or previous breakpoint location number scroll forward or backward by this amount\nAction:\nCorrect data and retry.\nCAIN2934\nInvalid data was entered in the Source List BKPT = field\nReason:\nThe data entered was not one of the following:\nON\nUse the source listing breakpoint display\nOFF\nUse the detailed breakpoint display\nAction:\nCorrect and retry request.\n 1615", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ccac44523f8e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2935\nThis facility will be TERMINATED on the next input command\nReason:\nThe program has encountered an unusual condition and will be terminated by the next input command.\nAction:\nNone.\nCAIN2936\nThe data entered in a displayed Register was invalid\nReason:\nThe contents of one of the displayed registers contained one or more nonhexadecimal characters.\nAction:\nCorrect the contents of the register and retry request.\nCAIN2937\na MOVE (M) request has to be the only request entered from the screen\nReason:\nThe data entered from the lister screen contained one or more MOVE requests along with other request types.\nAction:\nRemove the other requests and process only the MOVE requests.\nCAIN2938\nThe cursor was not positioned under a data name\nReason:\nA lister service request was made which uses the cursor position to determine the data name that it applies to. However,\nthe cursor was not found under any part of a data name.\nAction:\nReposition the cursor so that it is under any part of the data name and retry the request.\nCAIN2939\nNo STMT # was found for the requested LABEL\nReason:\nThe program statement number for the requested label was not found.\nAction:\nNone.\nCAIN2940\na B (BYP) request must be made at a location preceded by a A\nReason:\nA bypass error request, B, was entered on the lister screen. However, it was not used on the statement that had the error.\nAction:\nRemove the B from its current location and enter it at the correct location.\nCAIN2941\nRequest not supported for this ASSEMBLER instruction\n 1616", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c718bb4223d3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nA display request was made on an assembler instruction that does not contain any fields that can be displayed; for\nexample, SVCs.\nAction:\nNone.\nCAIN2942\nno BASE REGISTER was found for the data name\nReason:\nAn assembler data name display request was made at an instruction that uses Register 0 as a base register.\nAction:\nNone.\nCAIN2943\na MOVE request is invalid for ASSEMBLER programs\nReason:\nMOVE requests cannot be used on an assembler program.\nAction:\nNone.\nCAIN2945\nThe requested CNTL menu option is invalid\nReason:\nThe CNTL option entered in the Option # field did not contain a known option.\nAction:\nPressing PF2 from the lister screen displays the CNTL menu. The option numbers displayed on this screen are the only\nvalid entries.\nCAIN2946\nSet/Remove indicator was not a S or R\nReason:\nThe character that follows the CNTL menu request was not an S (set) or R (remove). This character indicates if the\nrequested options are to be set or removed for the monitored program.\nAction:\nCorrect and resubmit the request.\nCAIN2947\nInvalid option entered for a XREF data name\nReason:\nAn invalid request was entered for a data name.\nAction:\nEnter a valid request and retry or remove the invalid request.\nCAIN2948\nInvalid option entered for an XREF label\nReason:\n 1617", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2d74bb9d3036-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAn invalid request was entered for a Procedure name or label.\nAction:\nCorrect and resubmit.\nCAIN2949\nCntl SystemWide functions cannot be requested from the LIST facility\nReason:\nThe usage of the SystemWide options selection menu, =32, or CNTL oneline commands that request systemwide\nfunctions are not permitted when requested from the ZIST facility. Systemwide functions include: START, END, RESTART,\nGLOG, CKPT, and PURGE.\nAction:\nExit the lister facility. Then enter the CNTL menus directly or enter the oneline command from a clear screen.\nCAIN2950\nNo breakpoints are set for the program\nReason:\nA scroll request, which has STOP set for the amount, was made for a program that does not have any breakpoints.\nAction:\nPress PF4 to view the lister profile, change the PF7/8 amount field and retry the scroll request.\nCAIN2951\nAt the first breakpoint for the program\nReason:\nA scroll backward request, which has STOP set for the amount, was made from a screen that is currently showing the first\nbreakpoint set in the program.\nAction:\nNone.\nCAIN2952\nAt the last breakpoint for the program\nReason:\nA forward scroll request, which has STOP set for the amount, was made from a screen that is currently showing the last\nbreakpoint set for the program.\nAction:\nNone.\nCAIN2953\nMargins cannot be greater than 34 for this display request\nReason:\nA display request, for an assembler data name, cannot be done from the displayed dsect because of the margin value.\nAction:\nReset the margin value to 34 or less, and then try the display request.\nCAIN2954", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2d74bb9d3036-1", "text": "CAIN2954\nTIOA compression software is active request ignored\nReason:\n 1618", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5800b640df8e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWhen trying to process a screen request, the saved TIOA was found to contain data from software that compresses\nTIOAs. Some examples of these packages are CTOP and 3270 SUPER OPTIMZER.\nAction:\nExclude all InterTest for CICS transactions from the TIOA compression software package.\nCAIN2956\nInvalid data or invalid numeric value for data type in the keep window\nReason:\nWhen changing data, by over-typing, in the keep window, invalid data or an invalid numeric value was entered for the data\ntype. This occurs when entering data that does not match the data type or a numeric value that is too large for the data\ntype. For example, the maximum value an S9(4) COMP field can hold is +32767.\nAction:\nCorrect the data or press ENTER to redisplay screen.\nCAIN2957\nRequest is invalid when using SymDump\nReason:\nCertain requests, like abending the task, are not allowed when the ZIST facility is entered from the SymDump facility.\nAction:\nNone.\nCAIN2958\nThe Wait amount does not contain a number from 1 to 5\nReason:\nAn invalid number has been entered in the Wait amount = field.\nAction:\nCorrect and retry.\nCAIN2959\nNo help information for this Abend code\nReason:\nThe InterTest for CICS help facility does not contain any information about the abend that has occurred in your program.\nAction:\nFor diagnostic information related to this abend, see the IBM CICS Messages and Codes for your version of the CICS\ntransaction server for z/OS.\nCAIN2960\na MON (+) or NOM () option cannot be set here\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5800b640df8e-1", "text": "CAIN2960\na MON (+) or NOM () option cannot be set here\nReason:\nThe location chosen for the setting of a MON or NOM option is invalid.\nAction:\nReview the restrictions for the setting of these options, then retry the request.\nCAIN2961\nInvalid data was entered in the Autostepping = field\nReason:\n 1619", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5aebcd961212-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe data entered for this field did not contain one of the following values:\nON\nTo activate the autostepping facility\nOFF\nTo deactivate the autostepping facility\nAction:\nCorrect and retry.\nCAIN2962\nInvalid data was entered in the Stop value = field\nReason:\nThe data entered in this field was not one of the following: CALL to stop autostepping at Commands, Macros, or UEXI\ncalls number the number of steps to perform before stopping\nAction:\nCorrect the data and retry.\nCAIN2963\nCommand does not start with a known InterTest transaction code\nReason:\nThe data entered on the Command= line did not start with a InterTest for CICS transaction code.\nAction:\nCorrect and retry.\nCAIN2964\nProgram must be at a Breakpoint to use this command\nReason:\nA InterTest for CICS dispatch command was requested for a program that is not currently stopped at a breakpoint. A\ndispatch command has either a CNTL*... or a CNTL=GO,.. syntax.\nAction:\nNone.\nCAIN2965\nInvalid option entered for a KEEP element\nReason:\nThe character entered at left of the KEEP element was invalid. The following are valid options:\nD, @, or %\nTo display a KEEP element\nM\nTo generate a MOVE request for a KEEP element\nX\nTo remove a KEEP element\nK\nTo keep a dynamic KEEP element (AutoKeep feature only)\nAction:\nChange the option and retry or press ENTER to redisplay the screen.\n 1620", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "355774b38a5f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2966\nThe KEEP element selected for a MOVE request was not a COBOL or PL/I data name\nReason:\nA MOVE (M) request was made for a KEEP element that was not defined as a COBOL or PL/I data name.\nAction:\nOvertype the data that is displayed in the KEEP window or type a \"D\" at the left of the KEEP element that needs to be\nchanged, then change data from within the CORE facility.\nCAIN2967\nThe InterTest security module IN25SEC2 was not found or was disabled\nReason:\nThe InterTest for CICS security program was found to be unusable when an attempt was made to verify the CORE\npassword.\nAction:\nReport the problem to the person within your organization who is responsible for the InterTest for CICS product.\nCAIN2968\nInvalid hexadecimal data was entered in the KEEP window\nReason:\nThe hexadecimal data displayed for a KEEP element was overtyped with nonhexadecimal data. Valid hexadecimal data\nconsists of the numbers 0 through 9 and the characters A through F.\nAction:\nCorrect the data and retry the request.\nCAIN2969\nEnter the CORE security password  to change the data for\nReason:\nAn attempt is being made to modify data that is not owned by this task, by overtyping the data shown in a KEEP window.\nThe KEEP element that is in error is displayed with this message.\nAction:\nEnter the same password that is generated in your system for the InterTest for CICS CORE facility in the area \" \". The\nchange to the data is ignored if the correct password is not entered.\nCAIN2970\nThe CORE security password is invalid\nReason:\nThe password entered in the CAIN2969 message was incorrect.\nAction:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "355774b38a5f-1", "text": "Reason:\nThe password entered in the CAIN2969 message was incorrect.\nAction:\nRetry the password just in case it was mistyped.\nCAIN2971\nThis CNTL command may not be requested from the LISTER screen\nReason:\nThe CNTL command entered on the LISTER command line, for example CNTL=NEW,..., is not permitted.\nAction:\nExit the LISTER facility and reissue the command.\n 1621", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dcd0f7facfec-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2972\nLowercase characters found make changes in the hexadecimal area\nReason:\nAn attempt was made to change the character portion of a KEEP window, which contains lowercase characters.\nAction:\nEither enter the changes in the hexadecimal portion of the KEEP window or type a D at the right of the keep item and then\nmake the changes on the CORE screen.\nCAIN2973\nThe data for xxxxx is storeprotected\nReason:\nThe data displayed in the KEEP window for xxxxx is storeprotected and may not be changed.\nAction:\nThe change request is ignored and the original data is displayed.\nCAIN2974\nMON/NOM support not generated\nReason:\nA + or character was entered at the beginning of a displayed line of source code. These characters request the MON or\nNOM options, respectively. However, MON/NOM support has not been enabled at your installation.\nAction:\nRemove or change the + or characters and retry your request. To enable MON/NOM, contact your systems programmer.\nCAIN2975\nA VARIABLE CHANGE request is invalid for PL1 programs\nReason:\nA V line command was entered at the beginning of a displayed line of source code. This character represents establishing\na variable change breakpoint, which is not supported for PL/I language programs.\nAction:\nRemove or change the V character and retry your request.\nCAIN2976\nThe language specified is not defined in the install options\nReason:\nThe character entered does not match either the default or alternate national language defined by the LANG1= and\nLANG2= InterTest for CICS customization parameters.\nAction:\nEnter one of the language characters displayed in the profile screen.\nCAIN2977\nLister function terminated\nReason:\nThe InterTest for CICS LISTER function was terminated.\nAction:\nNone.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dcd0f7facfec-1", "text": "The InterTest for CICS LISTER function was terminated.\nAction:\nNone.\n 1622", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "24ad8ba6e468-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2978\nNo valid Backtrace Table entry was found\nReason:\nThe SOURCE BACKTRACE function could not find a valid backtrace table entry. There is an internal InterTest for CICS\nproblem or the backtrace table storage has been damaged.\nAction:\nRequest a transaction dump, and contact Broadcom Support .\nCAIN2979\nNo valid Master Index Records found\nReason:\nThe master index records cannot be found in the Symbolic file. The SOURCE BACKTRACE function cannot display the\nBacktrace Summary Menu. This is an internal InterTest for CICS problem or a critical control block has been damaged.\nAction:\nRequest a transaction dump and contact Broadcom Support .\nCAIN2980\nA Stmt/Offset Detail Record error\nReason:\nAn internal error occurred scanning the Symbolic File records The SOURCE BACKTRACE function cannot display the\nBacktrace Summary Menu. This is an internal InterTest for CICS problem or a critical control block has been damaged.\nAction:\nRequest a transaction dump, and contact Broadcom Support .\nCAIN2981\nWARNING Listing date/time (*) not equal to load (*)\nReason:\nThe Source Listing's date and time stamps are not equal to the program's load module's post processing data and time.\nAction:\nCheck the source and load dates and times. If they do not match, recompile to PROTSYM File.\nCAIN2982\nMultiple Selects and duplicate or numeric 'Bmrk' not allowed\nReason:\nYou specified 'S' next to more than one Backtrace Statement Block, and you specified a duplicate or a numeric bookmark.\nOnly one 'S' is allowed, and bookmarks must be unique and contain at least one nonnumeric character.\nAction:\nCorrect the error and try again.\nCAIN2983\nMultiple Selects not allowed or s field invalid\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "24ad8ba6e468-1", "text": "CAIN2983\nMultiple Selects not allowed or s field invalid\nReason:\nYou specified 'S' next to more than one Backtrace Statement Block or you specified a character in the 'S' column that is\nnot an 'S'.\nAction:\nCorrect the error and try again.\n 1623", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aac7461d196d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2984\nDuplicate or numeric 'Bkmk' not allowed\nReason:\nYou specified a duplicate or a numeric bookmark. Only one 'S' is allowed, and bookmarks must be unique and contain at\nleast one nonnumeric character.\nAction:\nCorrect the error and try again.\nCAIN2985\nInput data in error. Correct and try again\nReason:\nYou specified an invalid key or entered invalid data on the Backtrace Summary screen.\nAction:\nCorrect the error and try again.\nCAIN2986\nFirst Backtrace Stmt Block\nReason:\nYou are positioned at the first (or oldest) entry in the internal backtrace table.\nAction:\nNone.\nCAIN2987\nLast Backtrace Stmt Block\nReason:\nYou are positioned at the last (or newest) entry in the internal backtrace table. The last entry reflects where the current\nbreakpoint is positioned.\nAction:\nNone.\nCAIN2988\nFirst and Last Backtrace Stmt Block\nReason:\nThe Backtrace Summary screen displays the first (or oldest) and last (or newest) entries in the internal backtrace table.\nAction:\nNone.\nCAIN2989\n'From' value cannot be greater than 'Of' value\nReason:\nThe numeric value specified in the 'From' field on the Backtrace Summary menu cannot be greater than the 'Of' value.\nThe 'Of' value is the maximum number of internal backtrace table entries currently active for this program. You can also\nspecify a valid 'bmrk' value in the 'From' field to reposition the Backtrace Summary screen.\nAction:\nCorrect the error and try again.\n 1624", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8f627e7002e1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN2990\n 'From' Bkmk not found\nReason:\nThe 'bmrk' value specified in the 'From' field was not a valid bookmark. You either specified an incorrect bookmark or the\ninternal backtrace entry associated with the previously defined bookmark had been deleted.\nAction:\nSpecify the correct bookmark.\nCAIN2991\nOption 12 was selected and no 'U' or 'C' breakpoints specified\nReason:\nOption 12 must be used with one or more 'U' or 'C' type breakpoints. This option is used to select additional breakpoints\noptions such as the first 'Indirect Command' to be executed when this breakpoint is encountered.\nAction:\nOnly use Option 12 with one or more 'U' or 'C' breakpoints\nCAIN2992\nan INDIRECT COMMAND request is invalid for ASSEMBLER program.\nReason:\nOption 11 was specified for an ASSEMBLER program and INDIRECT COMMANDS are not supported for ASSEMBLER\ntype programs.\nAction:\nDo not specify option 11 for ASSEMBLER type programs.\nCAIN2993\nDataname (*) was not found in XREF\nReason:\nThe dataname specified by the cursor position on a D, K, M, or V line command could not be found in the programs XREF.\nAction:\nEnsure that you used the proper COBOL II or COBOL/370 compile options when the program was compiled.\nCAIN2994\nCA InterTest program (*) is not available\nReason:\nThe InterTest for CICS program specified is not defined to your CICS region or cannot be loaded.\nAction:\nEnsure that the program is available in the DFHRPL concatenation.\nCAIN2995\nInvalid data was entered in the AutoKeep Display = field\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8f627e7002e1-1", "text": "CAIN2995\nInvalid data was entered in the AutoKeep Display = field\nReason:\nThe data entered was not one of the following:\nON\nUse the AutoKeep display feature\nOFF\nDo not use the AutoKeep display feature\n 1625", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2400ced921d4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nCorrect and retry request.\nCAIN2996\nAutoKeep not supported under this language or compiler\nReason:\nThe AutoKeep display feature is not available under this programming language or under this version of a language's\ncompiler.\nAction:\nReview the documentation provided with the latest release and genlevel of InterTest for CICS to verify which languages\nand compilers support the AutoKeep display feature.\nCAIN2997\nAutoKeep cannot be activated because monitoring not in effect\nReason:\nThe AutoKeep display feature cannot be activated until monitoring has been requested for the program.\nAction:\nInitiate monitoring by either hitting PF5 or setting a breakpoint request within the program before activating the AutoKeep\ndisplay feature.\nCAIN2998\nInvalid data was entered in the Code Counting = field\nReason:\nThe data entered was not one of the following:\nON\nStart the Code Coverage feature\nOFF\nStop the Code Coverage feature\nAction:\nCorrect and retry request.\nCAIN2999\nCounting cannot be activated because monitoring not in effect\nReason:\nThe Code Coverage feature cannot be activated until monitoring has been requested for the program.\nAction:\nInitiate monitoring by either hitting PF5 or setting a breakpoint request within the program before activating the Code\nCoverage feature.\nCAIN3000\nCounting cannot be activated already in effect at \"From\" terminal\nReason:\nThe Code Coverage feature can only be activated for a single user at a specific \"From\" terminal.\nAction:\nNo action can be taken until the user at the \"From\" terminal stops their Code Coverage session.\n 1626", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2d3925ec903e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN3001\nCounting cannot be deactivated in use by another active task\nReason:\nCode Coverage is in use by another task attached to the \"From\" terminal. Due to this fact, the Counts Table is in use and\ncannot be removed.\nAction:\nNo action can be taken until the other task ceases use of the Counts Table.\nCAIN3006\nStatement Trace Table not found\nReason:\nThe PREV or ADV command was specified but the Statement Trace facility is not active.\nAction:\nSpecify the TRACE command to activate the Statement Trace facility.\nCAIN3007\nEnd of Statement Trace Table\nReason:\nThe PREV command was specified but the Statement Trace Table is already positioned at the first entry OR the ADV\ncommand was specified but the Statement Trace Table is already positioned at the last entry.\nAction:\nNone.\nCAIN3008\nError retrieving past data values\nReason:\nAn internal error occurred while retrieving past data values for the DATAMON option.\nAction:\nCall Broadcom Support .\nCAIN3010\nCurrently there are no current channels active.\nReason:\nThere are no current channels active.\nAction:\nNo action can be taken.\nCAIN3020\nCAIN3020 Keep window line command +/- not valid for this item.  Reason: The + or - line command for this item is not\nsupported in the keep window. \nAction: Use the + and - line commands for COBOL index items only.\nCAIN3050\nProgram not defined to CICS\nReason:\n 1627", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f1c6384a02c1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe program does not have a PPT entry although the symbolic information for the program is available.\nAction:\n\u2022\n\u2022If the program that you specified is a subroutine of a composite module, enable monitoring for the whole composite\nmodule.\n\u2022\n\u2022Enter the name of a valid program.\n\u2022\nCAIN3051\nInvalid load module name\nReason:\nThe program does not have a PPT entry.\nAction:\nEnter the name of a valid load module.\nCAIN3052\nProgram defined to CICS but has no symbolics\nReason:\nThe program has a PPT entry, but the symbolic information for the program is not available.\nAction:\n\u2022\n\u2022If you specified the name of a composite module, enable composite monitoring.\n\u2022\n\u2022Provide symbolic information for the program.\n\u2022\nCAIN3099\nNOTAUTH CONDITION RESOURCE LEVEL SECURITY FAILED FOR \"(*)\"\nReason:\nA nonauthorized condition was detected.\nAction:\nCheck the condition.\nCAIN3100\nInterTest RELEASE (*) NOT COMPATIBLE WITH CICS RELEASE (*)\nReason:\nThe InterTest for CICS release that you are running is not compatible with the release of CICS that is running.\nAction:\nInstall the correct release of InterTest for CICS.\nCAIN3101\nMAP NOT IN PPT, OR PPT ENTRY DISABLED.\nReason:\n 1628", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f5abd038180a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterTest for CICS could not find a map in the PPT, or the PPT entry is disabled.\nAction:\nCheck to see it the PPT entry is present, and ensure that it is enabled.\nCAIN3102\nBMS ABEND INTERCEPTED. ABEND CODE=(*)\nReason:\nA BMS abend has been intercepted by InterTest for CICS. The abend code appears as (*).\nAction:\nCheck the BMS map and the requested input.\nCAIN3103\nRETURNED FROM MAP DISPLAY.\nReason:\nInformational message.\nAction:\nNone.\nCAIN3104\nMAP IS TOO LARGE. TERMINAL CODE=(*)\nReason:\nThe map is too large for display on terminal code=(*).\nAction:\nNone.\nCAIN3105\n'INVALID REQUEST' RETURN FROM BMS.\nReason:\nThe request you made is invalid.\nAction:\nCorrect your request and resubmit.\nCAIN3106\nTEMP. STORAGE I/O ERROR.\nReason:\nAn I/O error occurred while you were trying to access temporary storage.\nAction:\nCorrect the temporary storage I/O error, and retry the transaction.\nCAIN3107\nBMS ERROR ON LUTYPE4 LOGICAL UNIT.\nReason:\nThe CORE=MAP command received an IGREQCD condition when sending the map to an LUTYPE4 logical unit.\nAction:\nDetermine the reason that the terminal could not receive the map, and resubmit the request.\n 1629", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b73eeb7d4410-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN3108\nBMS ERROR DETECTED.\nReason:\nAn IGREQCD condition was received during a send map request.\nAction:\nEnsure that your LUTYPE4 Terminal is defined correctly in CICS.\nCAIN3109\nI/O ERROR WHILE LOADING THE MAP.\nReason:\nAn I/O error was detected while loading a BMS map.\nAction:\nNone.\nCAIN3110\nPPT ENTRYUSAGE IS NOT 'MAP'.\nReason:\nThe CORE=MAP command was entered for an entry that is not defined as a map to CICS.\nAction:\nCorrect the program definition, and resubmit the request.\nCAIN3111\nPROCESSING ERROR IN IN25MAPD.\nReason:\nAn internal logic error has occurred.\nAction:\nContact Broadcom Support .\nCAIN3201\nInvalid option or command entered.\nReason:\nThe option or command entered is not valid for this function.\nAction:\nCorrect the option or command and resubmit.\nCAIN3202\n(*) transaction ended.\nReason:\nThe transaction specified has ended.\nAction:\nNone.\nCAIN3203\n(*) transaction ended due to a processing error.\nReason:\n 1630", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "083b6d775c5f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThere was a processing error in the specified transaction.\nAction:\nIf a dump was taken, contact Broadcom Support . Review the commands and processing for completeness. Resubmit if\nnecessary.\nCAIN3205\nNo entries were found.\nReason:\nNo entries were found to match the selection criteria specified.\nAction:\nCorrect the selection criteria and resubmit.\nCAIN3206\nInsufficient storage available to satisfy request.\nReason:\nThere was not enough storage available to complete the request.\nAction:\nContact your systems programmer for assistance.\nCAIN3207\nEntry was not found.\nReason:\nThe requested entry could not be found.\nAction:\nVerify and correct the selection criteria and resubmit.\nCAIN3208\nFile is unenabled or disabled.\nReason:\nThe requested file is not available because it is either unenabled or disabled.\nAction:\nMake the file enabled and try again.\nCAIN3209\nFile is not open or is closing.\nReason:\nThe file needs to be open to complete the request.\nAction:\nOpen the file and try again.\nCAIN3211\nUse \"S\" to make a selection.\nReason:\nA character other than \"S\" was used to make a selection.\nAction:\nUse \"S\" to make the selection and resubmit.\n 1631", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e75a8e2c2d1e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN3212\nInactive command entered.\nReason:\nThe command entered is currently inactive in this release of the product.\nAction:\nNone.\nCAIN3213\nError occurred reading file.\nReason:\nThere was a problem reading the file.\nAction:\nContact your systems programmer for assistance.\nCAIN3230\nRequired command parameter is missing or invalid.\nReason:\nOne of the parameters required by this command was either invalid or missing.\nAction:\nCheck the command syntax, correct, and try again.\nCAIN3231\nValid scroll amounts: M, P, H, C, D or 1 to 9999.\nReason:\nA value other than a valid scroll amount was specified.\nAction:\nReview the valid scroll values listed above and try again.\nCAIN3247\nInvalid selection.\nReason:\nThe requested selection is invalid.\nAction:\nChoose a valid selection and try again.\nCAIN3264\nInvalid selection character entered.\nReason:\nThe selection character used is invalid for this function.\nAction:\nReview the valid selection characters and try again.\nCAIN3265\nRequired input data is missing.\nReason:\n 1632", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c9c00bde815b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nA required input data field is missing\nAction:\nFill in the highlighted field and resubmit.\nCAIN3266\nInput data is invalid.\nReason:\nThe data entered is not valid or a program, transaction, or terminal was specified that is not defined to the CICS region.\nAction:\nCorrect the data and try again.\nCAIN3267\nOption is valid for specific programs only.\nReason:\nThis option is not valid for generic programs, .ALL, or .OPTIONS.\nAction:\nSpecify a specific program and try again.\nCAIN3268\nOption is valid for COBOL or PL/I programs only.\nReason:\nThis option is only available for COBOL and PL/I programs.\nAction:\nCheck the program name and language and try again.\nCAIN3308\nRequest unsupported for selected entry.\nReason:\nThe selected entry does not allow use of the requested function.\nAction:\nVerify the entry and request and try again.\nCAIN3323\nRestricted option entered.\nReason:\nThe option requested is restricted from use.\nAction:\nEither do not use this option, or obtain security access to the option from your systems programmer.\nCAIN3359\nValue is out of range.\nReason:\nThe value specified is outside the range of valid values.\nAction:\nCorrect the value and try again.\n 1633", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "210c05150316-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN3360\nOption is not installed.\nReason:\nThe requested option is not installed at this site.\nAction:\nContact your systems programmer for assistance.\nCAIN3361\nRequest denied. Currently in breakpoint or dump analysis.\nReason:\nThe requested action is not available during breakpoint processing or while in dump analysis.\nAction:\nTry again the request when not at a breakpoint or in dump analysis.\nCAIN3395\nRecord added.\nReason:\nThe requested record was successfully added.\nAction:\nNone.\nCAIN3396\nRecord already exists.\nReason:\nThe requested record already exists on the file; therefore, it cannot be added.\nAction:\nNone.\nCAIN3397\nRecord updated.\nReason:\nThe requested record was successfully updated.\nAction:\nNone.\nCAIN3398\nRecord deleted.\nReason:\nThe requested record was successfully deleted.\nAction:\nNone.\nCAIN3399\nRecord not found.\nReason:\n 1634", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "675a81f45152-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe requested record was not found on the file; therefore, it cannot be displayed.\nAction:\nNone.\nCAIN3405\nAdd failed. EIBRESP=X\"<>\", EIBRESP2=X\"<>\".\nReason:\nThe requested record could not be added. Use the information in the EIBRESP and EIBRESP2 to determine the problem.\nAction:\nCorrect the problem and retry.\nCAIN3406\nUpdate failed. EIBRESP=X\"<>\", EIBRESP2=X\"<>\".\nReason:\nThe requested record could not be updated. Use the information in the EIBRESP and EIBRESP2 to determine the\nproblem.\nAction:\nCorrect the problem and retry.\nCAIN3407\nDelete failed. EIBRESP=X\"<>\", EIBRESP2=X\"<>\".\nReason:\nThe requested record could not be deleted. Use the information in the EIBRESP and EIBRESP2 to determine the\nproblem.\nAction:\nCorrect the problem and retry.\nCAIN3408\nFile not found.\nReason:\nThe file needed for this activity was not found.\nAction:\nContact your systems programmer.\nCAIN3409\nFile not authorized.\nReason:\nThe file needed for this activity was not authorized.\nAction:\nContact your systems programmer.\nCAIN3416\nFile names cannot exceed 8 characters\nReason:\nYou have elected to browse files but have entered a file name that contains more than 8 characters.\nAction:\n 1635", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7ad9402c8eab-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCheck the file name and shorten it to be less than or equal to 8 characters.\nCAIN3417\nTD queue names cannot exceed 4 characters\nReason:\nYou have elected to browse transient data queues but have entered a TDQueue name that contains more than 4\ncharacters.\nAction:\nCheck the TDQueue name and shorten it to be less than or equal to 4 characters.\nCAIN3418\nCICS crumple zone damage detected, * address flagged below\nReason:\nThe leading and trailing crumple zones of the indicated storage do not match.\nAction:\nThis is the result of a storage violation. Check the application responsible for the storage for references for possible\naccess beyond the end of the storage area. It may also be necessary to check applications for use of storage areas that\nhave been FREEd.\nCAIN3419\nStructure Display Format\nReason:\nData displays in Structure Display Format.\nAction:\nNone.\nCAIN3475\nUse LIST to set/remove options on duplicate subprograms\nReason:\nA duplicate subroutine has been declared for monitoring. The LIST facility or transaction must be used to set/remove\noptions on a duplicate subroutine. The COMPOSITE command must be used in the LIST facility to declare the\nsubprogram's owning load module.\nAction:\nUse the COMPOSITE command in the LIST facility.\nCAIN3477\nDump is from a different CICS release. Enter to continue.\nReason:\nThe selected dump was captured on a different CICS release than the region that you are using to review the dump.\nAction:\nThis is an informational message. Press Enter to view the dump.\nCAIN3501\nTASK=(*) ABENDED BY CA InterTest, ABEND CODE=(*), ERROR CODE=(*)\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7ad9402c8eab-1", "text": "Reason:\nThe task was abended by InterTest for CICS.\n 1636", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "25aedb027023-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nNone.\nCAIN3502\nMON. TABLE ENTRY=(*), PGM=(*), TRANS=(*), TERM=(*).\nReason:\nThe task was abended by InterTest for CICS.\nAction:\nNone.\nCAIN3627\nTerminal released from CA InterTest.\nReason:\nThe terminal is released from the control of InterTest.\nAction:\nNone.\nCAIN3628\nAutomatic breakpoint;\nReason:\nThe monitored program has encountered an automatic breakpoint.\nAction:\nYou can use the InterTest for CICS Help facility to determine the cause of the error and to correct it.\nCAIN3629\nUnconditional breakpoint\nReason:\nThe monitored program has encountered an unconditional breakpoint.\nAction:\nUse the InterTest for CICS Help facility to find out more about breakpoints.\nCAIN3630\nConditional breakpoint\nReason:\nThe monitored program has encountered a conditional breakpoint.\nAction:\nUse the InterTest for CICS Help facility to find out more about breakpoints.\nCAIN3631\nSinglestepping breakpoint.\nReason:\nThe monitored program has encountered a singlestep breakpoint.\nAction:\nUse the InterTest for CICS Help facility to find out more about breakpoints.\n 1637", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "55871e47d73c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN3632\nAutostepping breakpoint.\nReason:\nThe monitored program has encountered an autostep breakpoint.\nAction:\nUse the InterTest for CICS Help facility to find out more about breakpoints.\nCAIN3634\nProgrammed breakpoint (coded as a CALL 'PBP').\nReason:\nThe monitored program issued a programmed breakpoint.\nAction:\nUse the InterTest for CICS Help facility to find out more about breakpoints.\nCAIN3637\nRequest bkpt;\nReason:\nThe monitored program has encountered a request breakpoint.\nAction:\nUse the InterTest for CICS Help facility to find out more about breakpoints.\nCAIN3638\nYou can continue only from terminal that received breakpoint display.\nReason:\nYou cannot continue from a breakpoint unless you are on the terminal that received the original breakpoint.\nAction:\nLog in to the terminal that received the previous breakpoint, and continue your test session.\nCAIN3639\nTo release this terminal, replace (*) with DISC\nReason:\nInformational message.\nAction:\nNone.\nCAIN3640\nPlease depress the CLEAR key.\nReason:\nInformational message.\nAction:\nPress Clear.\nCAIN3641\nHit CLEAR to restore screen, then only CA InterTest functions.\nReason:\n 1638", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "22d9b72f7199-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nA non- InterTest for CICS transaction was requested from a detailed breakpoint screen. Only InterTest for CICS\ntransactions are allowed.\nAction:\nPress Clear, and specify a InterTest for CICS transaction.\nCAIN3642\nRelated CICS work in other regions may remain pending.\nReason:\nYour request to abend the task at a breakpoint may leave work started in remote CICS regions pending.\nAction:\nNone.\nCAIN3643\nPress PF3 to proceed\nReason:\nAn abend of a task at a breakpoint has been requested.\nAction:\nIf you still wish to abend the task, press PF3. If you want to cancel the abend, press Clear.\nCAIN3644\nOr replace the XXXX with a dump code.\nReason:\nYou have requested an abend of a breakpointed task with no dump.\nAction:\nIf you want a dump, request the abend again, and specify an abend code other than \"XXXX\".\nCAIN3645\nDisconnect cannot be done for task. CLEAR will restore screen.\nReason:\nThe task that you are trying to disconnect was started without a terminal facility, and cannot be disconnected.\nAction:\nPress Clear.\nCAIN3647\nEDF facility activated. Please depress Clear.\nReason:\nCEDF has been requested for this transaction.\nAction:\nCEDF is now activated.\nCAIN3648\nUser's task will\nReason:\nInformational\nAction:\nNone.\n 1639", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c4d204916253-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN3653\nThis terminal released for other transactions, including logoff.\nReason:\nYour CNTL=DISC request has been successfully completed.\nAction:\nClear your screen and continue.\nCAIN3654\nThe task remains waiting at the breakpoint\nReason:\nYour CNTL=DISC request has been processed. The breakpoint task is suspended at the breakpoint until you reconnect.\nAction:\nClear your screen and continue.\nCAIN3655\nHit ENTER key to terminate routing session, otherwise hit clear key.\nReason:\nYour CNTL=DISC request has been processed for a remote terminal.\nAction:\nPress Enter to complete the disconnection, or press Clear to cancel the disconnection.\nCAIN3656\nThe task will be abended without dump and exits will be canceled.\nReason:\nAn abend request for the breakpointed task has been requested without a dump, and Handle Abend Exits will be\ncanceled.\nAction:\nNone.\nCAIN3659\nSource code display is not available.\nReason:\nThere is no program entry in the InterTest for CICS PROTSYM file.\nAction:\nEnsure that the proper InterTest for CICS Symbolic File is specified in your CICS region.\nCAIN3661\nSymbolic information\nReason:\nInformational message.\nAction:\nNone.\nCAIN3662\n(Program's data missing in (*) file.)\n 1640", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "73cc66be9ce7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nSymbolic program information was requested, but it is not in the InterTest for CICS Symbolic File.\nAction:\nEnsure that the proper InterTest for CICS Symbolic File is specified in your CICS region.\nCAIN3701\n(*) WILL ATTACH THIS COMMAND\nReason:\nThe InterTest for CICS PLT startup module was executed and will issue the InterTest for CICS Start command.\nAction:\nNone.\nCAIN3702\n(*) - (*) CANNOT BE USED.\nReason:\nThe InterTest for CICS programs are not defined in your CICS region or are defined with improper security.\nAction:\nEnsure that InterTest for CICS is properly installed.\nCAIN3703\n(*) FAILED TO FIND (*).\nReason:\nThe InterTest for CICS programs are not defined in your CICS region or are defined with improper security.\nAction:\nEnsure that InterTest for CICS is properly installed.\nCAIN3704\n(*) FAILED TO START CA InterTest.\nReason:\nInterTest for CICS could not be started during PLT initialization.\nAction:\nCheck previous messages for additional errors that were encountered.\nCAIN3705\n(*)ERROR WRITING TO GLOG TDQ.\nReason:  InterTest for CICS has encountered a problem writing to the GLOG TDQ during PLT initialization. This message\nwill be followed by message CAIN3704, which indicates that InterTest for CICS failed to start during the initialization.\nAction:  Check that the transient data destination specified in the GLOG= parameter in IN25OPTS is available and can be\nwritten to. The default setting, GLOG=CSSL, provides the statistics destination that is always present in the CICS system\nand is usually printed when the CICS system is terminated.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "73cc66be9ce7-1", "text": "and is usually printed when the CICS system is terminated.\nCAIN3751\nCA InterTest (*) COMMAND BEING ISSUED:\nReason:\nThe InterTest for CICS PLT shutdown module has executed the InterTest for CICS terminate command.\n 1641", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2e805f3b0a21-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nNone.\nCAIN3752\nCA InterTest IN25PLTE ERROR LOADING (*) PROGRAM\nReason:\nThe InterTest for CICS PLT shutdown module could not load the InterTest for CICS program.\nAction:\nEnsure that InterTest for CICS was properly installed, or that your CICS PPT table was not corrupted.\nCAIN3753\nCA InterTest (*) ERROR ISSUING START COMMAND\nReason:\nThe InterTest for CICS CNTL transaction could not be started during PLT shutdown.\nAction:\nEnsure that InterTest for CICS has been installed properly.\nCAIN3754\nCA InterTest (*) PROCESSING TERMINATED ABNORMALY\nReason:\nThe InterTest for CICS PLT shutdown module terminated abnormally.\nAction:\nReview any previous messages for additional error information.\nCAIN3500\nCAIN3500\nMessage: CAIN3500 DWARF API call failed with RC ...\nReason: DWARF symbolic information processing error.\nAction:  Contact Broadcom Support  with the return code.\nCAIN3503\nCAIN3503\nProgram not found in the current load module.\nReason: The load module specified in the 'Load module=' field does not contain DWARF symbolic information for the\nprogram specified in the 'PROGRAM=' field.                                    \nAction:  None.\nCAIN3504\nCAIN3504\nCommand not available for a subprogram. Use composite monitoring.\nReason:  The currently displayed program is a subprogram in the load module. The command or action requested is not\navailable for subprograms unless composite monitoring is used.                                 \n 1642", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d52ab33e5e78-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:  Turn on composite monitoring for the load module.\nCAIN4301\nSyntax error in input command\nReason:\nYour CNTL command contains a syntax error.\nAction:\nCorrect the command, and resubmit your request.\nCAIN4302\nRequest disregarded.\nReason:\nThe CNTL command was disregarded because of an error.\nAction:\nReview your command syntax and any previous error messages. Correct the command, and resubmit your request.\nCAIN4303\nPlease depress Clear key.\nReason:\nInformational message.\nAction:\nPress Clear.\nCAIN4304\nPROTCPF 1st read error, TCAFCTR=(*)\nReason:\nA READ error occurred on the InterTest for CICS checkpoint file during a RESTART command.\nAction:\nContact the person who installed InterTest for CICS.\nCAIN4305\nRestart could not be done.\nReason:\nAn error occurred during CNTL=RESTART.\nAction:\nCheck your command syntax, and resubmit your request.\nCAIN4306\nRecent CKPT was not today.\nReason:\nCNTL=RESTART for the current date failed, because the last checkout was made on a different day.\nAction:\nA normal START occurs.\n 1643", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8b1480fa3d63-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4307\nRestart was incomplete.\nReason:\nCNTL=RESTART failed.\nAction:\nReview the errors and correct them.\nCAIN4308\nCurrent use count of the program is not zero,\nReason:\nCNTL=NEW failed, because the program is in use by another task or was loaded with the HOLD option.\nAction:\nCheck to see if other tasks are using the program. If there are none, issue CORE=DLTE=prgname and resubmit the\nrequest.\nCAIN4309\nOld copy remains. Monitoring status remains.\nReason:\nNEW COPY failed. Refer to the accompanying messages.\nAction:\nNone.\nCAIN4310\nResetting of the PPT entry failed.\nReason:\nThe program specified in the request was either not found in the PPT or it was disabled.\nAction:\nLocate and determine the status of the program and resubmit the request.\nCAIN431\nMonitor Table entry was removed.\nReason:\nAn attempt to NEW COPY a program failed, which caused the Monitoring Table entry to be removed.\nAction:\nSee associated messages for the action to be taken.\nCAIN4312\nThe PPT entry for the program is now reset.\nReason:\nThis is the normal CICS response when CNTL=NEW is executed for a program.\nAction:\nNone.\nCAIN4313\nInvalid request range.\n 1644", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "402540ac4b98-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nThe request you made was not within the range.\nAction:\nCorrect and resubmit you request.\nCAIN4314\nUnable to LOAD table (*).\nReason:\nThe program name specified could not be loaded.\nAction:\nEnsure that the program exists in the DFHRPL concatenation and in the installed program definitions.\nCAIN4315\nDefault start will be done.\nReason:\nSTART failed. A normal InterTest for CICS START (CNTL=START) occurs. See accompanying messages.\nAction:\nCorrect any errors.\nCAIN4316\nCA LMP RIMSTAT error has been detected.\nReason:\nThe License Management Program definitions do not contain a license for InterTest for CICS.\nAction:\nEnsure that you have the proper level of Common Components and Services  software installed. Contact Broadcom\nSupport .\nCAIN4317\nCA InterTest cannot be initialized.\nReason:\nA serious error occurred during initialization.\nAction:\nReview any error messages. Contact Broadcom Support  if this is not an installation error.\nCAIN4318\nFamilies to be initialized\nReason:\nProgram families have been defined.\nAction:\nNone.\nCAIN4319\n(*) member not in PPT.\nReason:\nThere was no PPT entry found for the specified program, or the program's name is spelled incorrectly.\nAction:\n 1645", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "56501471e4a5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nPlace the program name in the PPT or correct the spelling of the program name.\nCAIN4320\n(*) member is RELOAD=YES.\nReason:\nInformational message.\nAction:\nNone.\nCAIN4321\n(*) family initialized.\nReason:\nThe family name that you specified has been successfully initialized.\nAction:\nNone.\nCAIN4322\nCA InterTest initializing...\nReason:\nInterTest for CICS is in the process of initializing in an ESA environment.\nAction:\nNone.\nCAIN4323\nCA InterTest successfully initialized.\nReason:\nInformational message.\nAction:\nNone.\nCAIN4324\nNote- IN25SEC2 not available.\nReason:\nNo security module was found.\nAction:\nInterTest for CICS security is disabled.\nCAIN4325\nCA REALIA II HOST TEST option is not available.\nReason:\nThe Realia II  HOST TEST option is not installed.\nAction:\nNone.\n 1646", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fcea4029bdf2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4326\nCA InterTest not active.\nReason:\nInterTest for CICS is not active at this time.\nAction:\nStart InterTest for CICS.\nCAIN4327\nCKPT not active.\nReason:\nThe checkpoint facility is not active at this time.\nAction:\nYou may start the checkpoint facility if you wish.\nCAIN4328\nCKPT could not be (*).\nReason:\nA checkpoint could not be scheduled or canceled.\nAction:\nNone.\nCAIN4329\nCKPT is active already.\nReason:\nThe checkpoint facility is already active.\nAction:\nNone.\nCAIN4330\nINTRVAL=(*) or higher required (hhmm).\nReason:\nYou have requested an interval for the checkpoint facility that is below the 20minute minimum.\nAction:\nRespecify the command with a valid interval.\nCAIN4331\nMON/NOM options will not be checkpointed.\nReason:\nInformational message.\nAction:\nNone.\nCAIN4332\nPURGE is not active.\nReason:\n 1647", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "10a1bf0e792d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe InterTest for CICS PURGE facility is not active.\nAction:\nActivate the PURGE facility.\nCAIN4333\nPURGE could not be canceled.\nReason:\nA request to stop the purge facility has failed.\nAction:\nNone.\nCAIN4334\nPURGE is active already.\nReason:\nThe PURGE facility is already active.\nAction:\nNone.\nCAIN4335\nINTRVAL=HHMM 20 minutes or higher required.\nReason:\nThe interval that you specified is below the 20minute minimum.\nAction:\nRespecify the command with a valid interval.\nCAIN4336\nPURGE scheduling failed.\nReason:\nA request to stop the purge facility has failed.\nAction:\nNone.\nCAIN4337\nINTRVAL not accepted.\nReason:\nThe interval value specified is either too low or too high. The interval must be in the proper range.\nAction:\nSpecify an appropriate value and resubmit the request.\nCAIN4338\nPURGE scheduled at INTRVAL=(*) hh:mm.\nReason:\nThe PURGE command executes every time the specified time interval elapses.\nAction:\nNone.\n 1648", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "36c15eca5da7-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4339\n(*) tasks purged this time.\nReason:\nThis message indicates how many tasks were purged.\nAction:\nNone.\nCAIN4340\n(*) entry already excluded.\nReason:\nYou have tried to exclude an item that is already in the exclusion table.\nAction:\nNone.\nCAIN4341\n(*) entry not in Exclusion Table.\nReason:\nAn attempt to remove an entry from the exclusion table has failed, because the entry was not found. The entry name\nspecified in the INCL command must be an exact match to an entry that was added to the exclusion table by a previous\nEXCL command.\nAction:\nNone.\nCAIN4342\n(*) already in Monitor Table. Ignored.\nReason:\nThe entry specified already existed.\nAction:\nNone.\nCAIN4343\nRequest processed.\nReason:\nInformational message.\nAction:\nNone.\nCAIN4344\n(*) entry not found in PPT, ignored.\nReason:\nThe program you specified was not found in the PPT. Your request was ignored.\nAction:\nNone.\n 1649", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c100fe06fd66-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4345\n(*) entry not found in table, ignored.\nReason:\nYou attempted to turn monitoring off for an entry that was not found.\nAction:\nSpecify an appropriate entry and resubmit the request.\nCAIN4346\n(*) is remote. It is local as (*) in CICS Sysid=(*).\nReason:\nInformational message.\nAction:\nNone.\nCAIN4347\n(*) name contains * or + and, if used,\nReason:\nA generic name was entered.\nAction:\nNone.\nCAIN4348\nwill increase overhead of CA InterTest tables scan.\nReason:\nA generic name was entered, which causes InterTest for CICS to spend more time scanning its memory, which increases\nprocessing overhead.\nAction:\nNone.\nCAIN4349\nDepress PF3 to confirm, any other key to reject.\nReason:\nInstructional message.\nAction:\nTo process your command, press PF3. To cancel your request, press any other key.\nCAIN4350\n(*) name contains * or + and is ignored.\nReason:\nA generic name was entered when a fully qualified name was expected.\nAction:\nSpecify a fully qualified name and resubmit the request.\nCAIN4351\nActive tasks still in system. Try later.\n 1650", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1b2bf827dcdb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nInterTest for CICS cannot be terminated while there are still active tasks at breakpoints.\nAction:\nTry again later.\nCAIN4352\nNo new tasks will be monitored, unless requested.\nReason:\nThe system is quiescent. No new tasks will be automatically monitored.\nAction:\nNone.\nCAIN4353\nDisable of Global User Exits has failed.\nReason:\nDuring termination of InterTest for CICS, the global user exits were not properly disabled.\nAction:\nRefer to message CAIN4354.\nCAIN4354\nEIBRCODE = X\"(*)\"\nReason:\nThis is the reason that the global user exit enable/disable failed.\nAction:\nNone.\nCAIN4355\nCA REALIA II HOST TEST option termination error.\nReason:\nTermination of the Realia II  Host Test option has failed. Refer to the accompanying messages.\nAction:\nCorrect the error and resubmit the request.\nCAIN4356\nCA InterTest (*) has been terminated.\nReason:\nInterTest for CICS has been successfully terminated.\nAction:\nNone.\nCAIN4357\nIN25SERS pgm abend STPS at (*)\nReason:\nAn internal logic error has occurred.\nAction:\nContact Broadcom Support .\n 1651", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "895c3c66c1ac-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4358\n(*) \nReason:\nSee accompanying messages.\nAction:\nNone.\nCAIN4359\nStartup error at IN25SERS+(*), code=(*).\nReason:\nInterTest for CICS was not able to start.\nAction:\nContact Broadcom Support  with the code and offset.\nCAIN4360\nCA InterTest cannot initialize and will abend INTT.\nReason:\nAn internal logic error has occurred.\nAction:\nContact Broadcom Support .\nCAIN4361\nUnable to LOAD IN25ABEN table.\nReason:\nAll abends will be intercepted by InterTest for CICS, because the exclusion table IN25ABEN was not loaded.\nAction:\nNone.\nCAIN4362\nIN25ABEN table incorrect.\nReason:\nThe IN25ABEN Table was incorrectly assembled or linkedited.\nAction:\nCorrect the error and resubmit the request.\nCAIN4363\nEnable of Global User Exit (*) has failed.\nReason:\nDuring termination of InterTest for CICS, the global user exits were not successfully disabled.\nAction:\nNone.\nCAIN4364\nEIBRCODE = X\"(*)\"\nReason:\n 1652", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3cfc35dbbac6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThis is the reason code that defines why the global user exit enable/disable failed.\nAction:\nNone.\nCAIN4365\nEnable of Global User Exit (*) has failed.\nReason:\nInformational message.\nAction:\nContact Broadcom Support .\nCAIN4366\nEIBRCODE = X\"(*)\", Initialization Continues\nReason:\nEnable of the global or task related user exit has failed.\nAction:\nCheck the DFHRPL concatenation and the installed program definitions for modules IN25HOOK and IN25TRUE.\nCAIN4367\nThe IN25UEXI entry (*) can be confused with\nReason:\nThe installation defined IN25UEXI module contains entries that are identical to the module entry code of CICS STUB\nmodules.\nAction:\nRemove the entry from your IN25UEXI. Reassemble or linkedit the module and restart InterTest for CICS.\nCAIN4369\nThe IN25UEXI entry (*) was incorrectly linkedited.\nReason:\nYou did not linkedit the entry correctly.\nAction:\nFollow the directions in Configuring for linkediting IN25UEXI.\nCAIN4370\nThe entry is now invalidated.\nReason:\nThe installation defined IN25UEXI module contains entries that are identical to the module entry code of CICS STUB\nmodules.\nAction:\nRemove the entry from your IN25UEXI. Reassemble or linkedit the module and restart InterTest for CICS.\nCAIN4371\nEnable of TRUE has failed.\nReason:\nEnable of InterTest for CICS Task related user exit has failed.\nAction:\n 1653", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1231d2a2532f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSee accompanying messages for reason for the failure.\nCAIN4372\nIN25COBI unavailable, dynamic call monitoring may fail\nReason:\nThe program IN25COBI is required for dynamic call monitoring but is currently unavailable.\nAction:\nContact your systems programmer for assistance.\nCAIN4373\nTask number is invalid.\nReason:\nThe task number specified is invalid.\nAction:\nCorrect the task number and resubmit.\nCAIN4374\nIN25IBMC unavailable, dynamic call monitoring may fail\nReason:\nThe program IN25IBMC is required for dynamic call monitoring but is currently unavailable.\nAction:\nContact your systems programmer for assistance.\nCAIN4375\nCCI_(*) failed.\nReason:\nCICSPlex communication failed with the reason indicated.\nAction:\nContact your systems programmer.\nCAIN4376\nCICS START of (*) transaction failed.\nReason:\nThis message appears with other messages detailing the reason the transaction failed.\nAction:\nContact your systems programmer.\nCAIN4377\nEIBRESP=X'(*)', EIBRESP2=X'(*)'.\nReason:\nThis message is produced in conjunction with another message. This message shows the contents of the above fields.\nAction:\nContact your systems programmer.\n 1654", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2fbc01500635-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4378\nCICSPlex support is disabled for this region.\nReason:\nThis message appears in conjunction with one or more other messages. Use the messages together to determine the\nproblem.\nAction:\nContact your systems programmer.\nCAIN4379\nCICSPlex resynchronization initiated with...\nReason:\nThis message appears with a second message.\nAction:\nNone.\nCAIN4380\nPLEX_ID = '(*)'.\nReason:\nThis message identifies the CICSPlex family member with whom this member synchronizes its monitoring options.\nAction:\nNone.\nCAIN4381\nLocal start performed, no active CICSPlex member to synchronize with.\nReason:\nCICSPlex=YES was specified, but this is the first member to start. Therefore, there are no other family members with\nwhom to synchronize.\nAction:\nNone.\nCAIN4382\nCICSPlex resynchronization failed, CICSPlex environment is not active.\nReason:\nThe CICSPlex environment has not been started, or has ended. Therefore, this CICSPlex member cannot resynchronize\nwith other family members.\nAction:\nContact your systems programmer.\nCAIN4383\nCA InterTest not available on this system as set in CAVHCONF.\nReason:\nThe CAVHCONF configuration module, which is loaded into the CSA, indicates that the product is not intended to be used\non this system.\nAction:\nContact your systems programmer to ensure that the CAVHCONF configuration macro was implemented correctly on this\nsystem and that the CAVHINIT process was run.\n 1655", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f2f7953ec694-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4384\nCAVHCONF module not found in the CSA.\nReason:\nThe CAVHCONF configuration module was not found in the CSA.\nAction:\nContact your systems programmer to ensure that the CAVHINIT process was run.\nCAIN4385\nNO TCA, COBOL DYNAMIC CALLS MAY FAIL\nReason:\nEnclave ended abnormally, no TCA.\nAction:\nFollow these steps:\n1.Stop INTERTEST (CNTL=END).\n2.Make sure your CICS LE environment is properly configured.\n3.Restart INTERTEST.\n4.If you get the same message again, contact Broadcom Technical support with CICSLOG.\nNOTE\nYou can continue to use the Product but COBOL Dynamic calls may fail.\nCAIN4386\nNO TCA, COBOL DYNAMIC CALLS MAY FAIL\nReason:\nCAA \u2013 LE Anchor is no more available.\nAction:\nFollow these steps:\n1.Stop INTERTEST (CNTL=END).\n2.Make sure your CICS LE environment is properly configured.\n3.Restart INTERTEST.\n4.If you get the same message again, contact Broadcom Technical support with CICSLOG.\nNOTE\nYou can continue to use the Product but COBOL Dynamic calls may fail.\nCAIN4387\nNO LIBVEC2, COBOL DYNAMIC CALLS MAY FAIL\nReason:\nVECTOR Table is no longer attached to CAA.\nAction:\nFollow these steps:\n1.Stop INTERTEST (CNTL=END).\n 1656", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "159044be9805-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n2.Make sure your CICS LE environment is properly configured.\n3.Restart INTERTEST.\n4.If you get the same message again, contact Broadcom Technical support with CICSLOG.\nNOTE\nYou can continue to use the Product but COBOL Dynamic calls may fail.\nCAIN4388\nDYN CALLS NOT INITIALISED, COBOL DYNAMIC CALLS MAY FAIL\nReason:\nSomething went wrong while initializing information for Dynamic calls.\nAction:\nFollow these steps:\n1.Stop INTERTEST (CNTL=END).\n2.Make sure your CICS LE environment is properly configured.\n3.Restart INTERTEST.\n4.If you get the same message again, contact Broadcom Technical support with CICSLOG.\nNOTE\nYou can continue to use the Product but COBOL Dynamic calls may fail.\nCAIN4501\nSyntax error in (*) command.\nReason:\nA syntax error was detected in the command.\nAction:\nCorrect the command and resubmit it.\nCAIN4502\nThis request disregarded.\nReason:\nThe command was not processed.\nAction:\nNone.\nCAIN4503\nMonitoring status for this program is now reset.\nReason:\nThe program has been successfully NEWCOPYed and all monitoring options have been reset.\nAction:\nNone.\nCAIN4504\nCA InterTest x.x restart accomplished.\nReason:\nThe CNTL=RESTART command has been successfully completed. InterTest for CICS is ready for use.\n 1657", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8100a9a4f30d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nNone.\nCAIN4505\nCA InterTest x.x is already active.\nReason:\nA START or RESTART command was requested, but is already active.\nAction:\nNone.\nCAIN4506\nCondition description for CBP is too long.\nReason:\nThe text specified on the CBP is longer than 254 bytes.\nAction:\nShorten the text so it is less than or equal to 254 bytes and retry the command.\nCAIN4507\nCurrent use count of the program is not zero\nReason:\nThe NEW COPY command could not be completed because the program is currently in use.\nAction:\nNone.\nCAIN4508\nOld copy remains. Monitoring status remains.\nReason:\nCNTL=NEW command cannot NEW COPY the program.\nAction:\nRefer to the accompanying messages to correct the error.\nCAIN4510\nBut is disabled for any new tasks.\nReason:\nThe monitoring entry is in use for a task running in CICS. Future invocations of the program, transaction or terminal will\nnot be monitored.\nAction:\nNone.\nCAIN4511\nPlease consult your System Programmer.\nReason:\nSee accompanying messages.\nAction:\nContact your system programmer.\n 1658", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1e3e6f15da4a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4513\nThis request has been processed.\nReason:\nThe command you specified has been processed successfully.\nAction:\nNone.\nCAIN4515\nCA InterTest Work Area could not be found.\nReason:\nA CICS storage violation occurred. InterTest for CICS storage accounting control block was overlaid.\nAction:\nContact Broadcom Support .\nCAIN4516\nCommand to continue task is incorrect or incomplete\nReason:\nThe command to continue this task is incorrect or incomplete.\nAction:\nRestate the command correctly, and reenter it.\nCAIN4518\nErrors to next breakpt/CICS request will be permitted\nReason:\nProgram execution continues, overriding an error detected during program monitoring.\nAction:\nNone.\nCAIN4519\nPressing PF3 will give permission to proceed.\nReason:\nInstructional message.\nAction:\nPress PF3 to proceed.\nCAIN4520\nThis request has been serviced.\nReason:\nInformational message.\nAction:\nNone.\nCAIN4521\nTAL option is not activewas not declared.\nReason:\n 1659", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9262e175565f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nA request was made to turn the TAL option off, but this option was never turned on.\nAction:\nThe command is ignored.\nCAIN4522\nThis option could not be found.\nReason:\nThe option you entered was incorrect or could not be found.\nAction:\nCheck the index for the proper command, and reenter it.\nCAIN4523\nThis option is already disabled.\nReason:\nThe condition that you entered was disabled during a file transaction.\nAction:\nCheck the FCT.\nCAIN4527\nSyntax error more than 9 items.\nReason:\nA maximum of 9 items may be entered.\nAction:\nEnter 9 or fewer items.\nCAIN4528\nCA InterTest (*) is not active in CICS.\nReason:\nInterTest for CICS is not active in CICS.\nAction:\nEnter the following command to start InterTest for CICS: CNTL=INQ.\nCAIN4529\nNaming by * rejectedno task at breakpoint found.\nReason:\nThe task you started has no breakpoints set at its location.\nAction:\nTo check where breakpoints are set, enter the following command: CNTL=INQ.\nCAIN4530\nDepress clear for return, or correct Command error\nReason:\nThe function that you entered has either executed correctly or you must enter the correct command in order for the\ncommand to execute correctly.\nAction:\nIf you entered the command incorrectly, reenter the correct command.\n 1660", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "176987f88adc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4532\nDepress Clear for return.\nReason:\nInstructional message.\nAction:\nPress Clear to return to the original screen.\nCAIN4533\n\"\" not valid outside of program, or in CNTL=OFF*\nReason:\nYou were trying to take InterTest for CICS off a program, or you were looking at an area that is outside the area in which\nInterTest for CICS is running.\nAction:\nOn a clear screen, enter CNTL=INQ.\nCAIN4536\ncompiled with COBOL II optimization.\nReason:\nInformational message. You used IN25COB2, COBOL II optimization.\nAction:\nNone.\nCAIN4537\nMore than 1 breakpoint created because program was\nReason:\nYou tried to set a breakpoint at a location that already contains a breakpoint.\nAction:\nSelect another location for the breakpoint, or enter CNTL=INQ or CNTL=OFF,PROG=xxxxxxxx on a clear screen.\nCAIN4538\nLocation cannot be accepted because program was\nReason:\nInformational message. You used IN25COB2, COBOL II optimization.\nAction:\nNone.\nCAIN4539\nDepress PF3 if you want to start InterTest now.\nReason:\nInterTest for CICS is not active.\nAction:\nPress PF3 to start InterTest for CICS.\nCAIN4540\nThis option accepted only for a specific PROG=name.\n 1661", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fdcd21bf09fc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nThe requested option is not valid with a generic program specification.\nAction:\nDo not use a generic specification for this option.\nCAIN4541\nOnly ALLCOM, ALLMAC, ALLCAL, ALLDL1, ALLBEG.\nReason:\nAn invalid keyword was entered.\nAction:\nSpecify a valid keyword in the command and resubmit.\nCAIN4542\nOnly requests of the same kind in an RBP option.\nReason:\nInterTest for CICS only accepts requests to produce breakpoints with the same Relative Breakpoint.\nAction:\nSee CICS Debugging for information on requesting breakpoints and the RBP option.\nCAIN4543\nThe #1 converted into RBP=ALLBEG.\nReason:\nA generic program request for UBP=All was converted to the equivalent command RBP=AllReg.\nAction:\nNone.\nCAIN4544\nOver 20 breakpoints will be set if you depress PF3.\nReason:\nYou are placing breakpoints at paragraph names, when you press PF3, more than 20 breakpoints are set in your program.\nAction:\nNone.\nCAIN4547\nAny mistake in use of MON or NOM options may cause\nReason:\nUse MON and NOM option with care.\nAction:\nNone.\nCAIN4548\nunpredictable results, including system breakdown.\nReason:\nIf you continue, you may get unpredictable results or your system may break down.\nAction:\nNone.\n 1662", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a6e96eebdb0d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4549\nDepress PF1 for more information or PF3 to execute.\nReason:\nInstructional message.\nAction:\nPress PF1 for HELP information, and press PF3 to execute.\nCAIN4550\nSystemwide maximum of 255 MON/NOM options reached.\nReason:\nYou have reached a systemwide maximum of 255 MON/NOM options in your program.\nAction:\nRemove the MON/NOM breakpoints that are not being used, and resubmit your request.\nCAIN4551\nCSA/CWA offset specified extends beyond area boundary.\nReason:\nThe offset specified plus the length exceeds the high boundary of the control block to be unprotected.\nAction:\nCorrect the OFFSET and/or LENGTH parameter and retry.\nCAIN4552\nChanging TERMID for stopped task may cause failure\nReason:\nInformational message. If you change the terminal ID for a stopped task, you may cause a failure to occur.\nAction:\nDo not change the terminal ID for a stopped task.\nCAIN4553\n(*) will be issued\nReason:\nA CNTL=RECON command has been issued to reconnect the application program to its breakpoint on the terminal\nindicated by TRMB.\nAction:\nThe breakpoint has been reestablished.\nCAIN4554\nProgram symbolics missing or mismatched.\nReason:\nThe program is not in the Symbolic File, or the New Copy option has to be run.\nAction:\nRecompile the program, or run the New Copy option with the following command: CNTL=NEW,PROG=progname.\nCAIN4555\nInvalid or unsupported CNTL function.\n 1663", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "213daac5c3a9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nThe CNTL function you tried to use is invalid.\nAction:\nRefer to CICS Debugging for a list of valid CNTL functions.\nCAIN4556\nFrom/To terminal name not found in the TCT.\nReason:\nYou tried to use a clientspecified terminal ID in a command that does not exist.\nAction:\nEnter the correct terminal ID. Enter CORE=TERM=x for a list of valid terminal IDs.\nCAIN4557\nNo A.T.I. or invalid type of the TOterminal.\nReason:\nThe TOterminal that you specified is invalid.\nAction:\nEnter the correct terminal ID.\nCAIN4558\nTask will be abended without dump and exits canceled.\nReason:\nYou selected a PF key that abends the task without a dump.\nAction:\nPress PF3 to continue.\nCAIN4559\nCICS work in remote systems may remain pending\nReason:\nIf an MRO environment is being used, processing in a remote system will not complete.\nAction:\nTask will be abended.\nCAIN4560\nThe task will be abended without dump.\nReason:\nInformational message. A soft abend occurred, or you entered 'xxxx' so a dump will not take effect.\nAction:\nNone.\nCAIN4561\nPress PF3 to display composite menu for (*)\nReason:\nYou set monitoring for a program for which InterTest for CICS has link-edit information.\nAction:\n 1664", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "129afcf72de8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nFollow these steps:\n1.Press PF3 to access the Composite Support screen.Link-edit information is displayed on the Composite Support\nscreen.\n2.Select the subprograms that you want to monitor, and press PF5 to confirm the selection.\n \nCAIN4562\nInterTest RELEASE (*) NOT COMPATIBLE WITH CICS RELEASE (*)\nReason:\nInformational message. The release of InterTest for CICS that you are running is not compatible with the CICS release\nthat is running.\nAction:\nSee Installing. Contact Broadcom Support .\nCAIN4563\nNOTAUTH CONDITION RESOURCE LEVEL SECURITY FAILED FOR \"(*)\"\nReason:\nThe resource specified did not pass the authorization checks.\nAction:\nContact the systems programmer.\nCAIN4564\n(*) Load Table processed.\nReason:\nThe JCL you used to load a table was successful.\nAction:\nNone.\nCAIN4565\n(*) entry not found in TCT/PCT Ignored\nReason:\nThe entry you made was not found in the Program Control Table or in the Task Control Area.\nAction:\nCheck the program with PCT or TCT.\nCAIN4566\n(*) entry not found in table. Ignored.\nReason:\nThe entry you made was not found in the Program Control Table or in the Task Control Area.\nAction:\nCheck your program for PCT or TCT.\nCAIN4567\n(*) found on Exclusion list. Ignored.\nReason:\n 1665", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "73e8c4293a3e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSince the entry was already in the Exclusion Table, the entry you made was ignored by InterTest for CICS.\nAction:\nNone.\nCAIN4568\n(*) entry active. Cannot be released,\nReason:\nYou were trying to turn off InterTest for CICS for a module that is not finished executing.\nAction:\nComplete the transaction, abend the task or delete it from the system.\nCAIN4569\n(*) facility not generated.\nReason:\nThe facility requested is not installed.\nAction:\nContact the systems programmer.\nCAIN4570\n(*) could not be found. Ignored.\nReason:\nThe requested program was not found.\nAction:\nCheck your program definitions and the DFHRPL data set concatenation.\nCAIN4571\nAttempted to set MON on an ODDvalue address\nReason:\nValid machine instructions are always on evennumbered addresses.\nAction:\nCorrect the address and resubmit the command.\nCAIN4572\nKEP= request rejected, no saved listing for program\nReason:\nThere is no symbolic listing information for the saved program and Keep Windows are only valid with symbolic listing\nbreakpoints.\nAction:\nThe KEP option cannot be set for this program.\nCAIN4573\nAttempted to set MON on contiguous instructions\nReason:\nThe MON= option cannot be set on contiguous instructions. At least one machine instruction must exist between MON=\nsettings.\nAction:\n 1666", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0ea7c32fee32-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNone.\nCAIN4574\nMON or NOM option cannot be set in readonly DSA\nReason:\nThe readonly DSA is storeprotected and MON or NOM options cannot be specified for programs that reside there.\nAction:\nMON and NOM options cannot be set for this program.\nCAIN4575\nKEP= entry not found, OFF request failed\nReason:\nA CNTL=OFF command is issued for an entry that has no active KEP.\nAction:\nCorrect the request and retry. The CNTL=INQ transaction may be used to display the active KEP options.\nCAIN4576\nKEP= request may only be set for a program\nReason:\nKEP= options cannot be set for a terminal or a transaction.\nAction:\nNone.\nCAIN4577\nKEP= request rejected, request is too long\nReason:\nThe information that you entered contains too many characters.\nAction:\nRefer to CICS Debugging for information on the KEP option.\nCAIN4578\ninvalid TERMID specified in T= option\nReason:\nThe terminal ID you entered is invalid.\nAction:\nSpecify a valid terminal ID, or bypass this function.\nCAIN4579\n(*) option disregarded.\nReason:\nThe indicated option was disregarded.\nAction:\nRefer to CICS Debugging for information on using the option.\n 1667", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6b590bb73f39-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4580\n(*) options processed\nReason:\nThe option you entered was executed successfully.\nAction:\nNone.\nCAIN4581\nGlobal Logging (*)\nReason:\nGlobal logging has been changed due to the command entered.\nAction:\nNone.\nCAIN4582\nBreakpoints not generated.\nReason:\nYou tried to enter a breakpoint, but it was not generated.\nAction:\nCheck the date and time of the load compared to the Symbolic File; there may be a mismatch. Recompile the program\nagain, and ensure that all steps run successfully.\nCAIN4583\nProgram will continue from (*)\nReason:\nYou entered a 'GO TO' condition, and the program will now continue from the indicated point.\nAction:\nNone.\nCAIN4584\nCurrent breakpoints (*)\nReason:\nIn response to CNTL=INQ, the following is a list of your breakpoints.\nAction:\nNone.\nCAIN4585\nABP global termid is XXXX.\nReason:\nThis is the automatic breakpoint terminal ID.\nAction:\nNone.\nCAIN4586\n(Known as (*) in system (*))\n 1668", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "28f13fa61203-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nThe terminal ID specified for the ABP command is defined in a Terminal Owning Region (TOR). The terminal ID in the\nTOR and the System ID of the TOR are listed in this message.\nAction:\nInformational.\nCAIN4587\nError found in processing (*) option no (*)\nReason:\nAn error was detected in the CNTL command option identified by the option number.\nAction:\nCorrect the command and resubmit.\nCAIN4588\n(*) name contains * or + which, if used,\nReason:\nA generic monitoring entry was specified. See message CAIN4589 for more information.\nAction:\nNone.\nCAIN4589\ncould increase overhead of CA InterTest tables scan.\nReason:\nOverhead for these tables could be increased due to the above condition (that is, +, , . ).\nAction:\nEnsure that your table does not begin with a plus sign, minus sign or period.\nCAIN4590\nDepress PF3 to confirm, any other key to reject.\nReason:\nInstructional message.\nAction:\nPress PF3 to confirm what you did. Press any other key to reject what you did.\nCAIN4591\n(*) name contains * or + and is ignored.\nReason:\nA generic name was entered instead of a fully qualified name.\nAction:\nSpecify a fully qualified name and resubmit.\nCAIN4592\n(*) program is not defined to CICS\nReason:\nThe program you entered was incorrectly defined to CICS and was ignored by InterTest for CICS, or the monitoring for a\nmain composite program was not requested before a composite subprograms.\n 1669", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6d4544049d8c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nEnsure that the program is defined to CICS. Or, if the program is a composite subprogram, you must start monitoring for\nthe main composite program before starting monitoring its composite subprograms.\nCAIN4593\n(*) entry not found in the TCT, ignored.\nReason:\nThe terminal ID was not found in the TCT.\nAction:\nCheck the TCT for the correct terminal ID.\nCAIN4594\n(*) entry not found in the PCT.\nReason:\nThe program you entered was not found in the PCT.\nAction:\nCheck the PCT for the correct program.\nCAIN4595\nThis name has been ignored.\nReason:\nA CNTL command was issued for an invalid or remote program, and the request will be ignored.\nAction:\nEnsure that the program name is correct.\nCAIN4596\n(*) is remote. It is local as XXXX in CICS Sysid=(*).\nReason:\nA InterTest for CICS command has been entered for transaction (*). This transaction is a remote entry.\nAction:\nNone.\nCAIN4597\nSpecified MON address is not a supported instruction\nReason:\nYou have specified an address on an instruction that is not supported by InterTest for CICS.\nAction:\nSelect an address for monitoring on a valid instruction.\nCAIN4598\nor a MON is already established at this address\nReason:\nYou have selected an address where MON has already been\nAction:\nSelect an address that does not have monitoring assigned to it yet.\n 1670", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "474d69fc6df3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4599\n(*) password:\nReason:\nYou have selected a function that requires you to enter a password.\nAction:\nEnter the password.\nCAIN4600\npassword (*)\nReason:\nYou have selected a function that requires you to enter a password.\nAction:\nEnter the password.\nCAIN4601\nSymbolic name not found, or\nReason:\nThe program name you specified cannot be found in any of the Symbolic Files.\nAction:\nSpecify a valid program name.\nCAIN4602\nProgram not in PPT, or disabled, or\nReason:\nThe specified program is not defined in the PPT or it has been disabled.\nAction:\nSpecify a valid program name, or enable the program.\nCAIN4603\nSymb.name is not a label or a paragraphname, or\nReason:\nThe symbolic name that you specified is not a label or paragraph name.\nAction:\nSpecify a valid label or paragraph name.\nCAIN4604\nProgram not in PPT, or\nReason:\nThe program that you specified is not in the PPT.\nAction:\nSpecify a program that is defined to the PPT, or update the PPT with the program name.\nCAIN4605\nOption invalid for (*)=EDIT function.\nReason:\n 1671", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "cecf62f7d9cc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe CNTL=EDIT function is valid for option CMD only.\nAction:\nCorrect the command and retry.\nCAIN4606\n(*) (*) indirect commands currently in use. Try later.\nReason:\nThe indirect commands defined for the program/terminal are currently either being edited or executed from another\nterminal. They cannot be accessed concurrently.\nAction:\nWait until they are available and retry.\nCAIN4607\nAn error occurred processing indirect commands\nReason:\nAn error occurred while attempting to execute indirect commands or access program IN25ICMD. The reason for the error\nfollows in the succeeding message.\nAction:\nNone.\nCAIN4608\nProgram (*) is not available.\nReason:\nThe program specified cannot be found or loaded.\nAction:\nEnsure that the program is defined in the PPT and can be loaded.\nCAIN4609\nStorage chains damage detected.\nReason:\nInterTest for CICS storage chains have been damaged.\nAction:\nGet an SVC dump and contact Broadcom Support .\nCAIN4610\nCWA does not exist.\nReason:\nThe unprotect CWA option was requested in a CICS region which does not have a CWA generated.\nAction:\nYou are either on the wrong CICS region or you must restart your CICS region with a CWA specified.\nCAIN4611\nCOBOL II runtime module (*) is not defined as ASSEMBLER.\nReason:\nThe COBOL II runtime modules IGZCPCC and IGZCPAC cannot be defined as other than ASSEMBLER. Therefore,\nCOBOL dynamic calls cannot be monitored.\n 1672", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1ceb7ca5d6fc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nDefine IGZCPCC and IGZCPAC as ASSEMBLER or verify that AUTOINSTALL is not defining them as other than\nASSEMBLER.\nCAIN4612\nCOBOL dynamic calls cannot be monitored.\nReason:\nThe COBOL II runtime modules IGZCPCC and IGZCPAC cannot be defined as other than ASSEMBLER. Therefore,\nCOBOL dynamic calls cannot be monitored.\nAction:\nDefine IGZCPCC and IGZCPAC as ASSEMBLER or verify that AUTOINSTALL is not defining them as other than\nASSEMBLER.\nCAIN4613\nMON or NOM option can only be set on a program.\nReason:\nThe MON and NOM options cannot be set for a terminal or transaction monitoring entry.\nAction:\nCorrect the request and retry.\nCAIN4614\nPROG=.ALL is already set for user (*).\nReason:\nThe PROG=.ALL can only be set by one user and it has already been set by the user specified.\nAction:\nNone.\nCAIN4615\nPROG=.OPTIONS is already set for user (*).\nReason:\nThe PROG=.OPTIONS can only be set by one user and it has already been set by the user specified.\nAction:\nNone.\nCAIN4616\nCICS LINK to (*) program failed.\nReason:\nThe requested program was not available.\nAction:\nContact your systems programmer.\nCAIN4617\nEIBRESP=X'(*)', EIBRESP2=X'(*)'.\nReason:\nThis message is produced in conjunction with another message. This message shows the contents of the above fields.\nAction:\n 1673", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7f516bb531c6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nContact your systems programmer.\nCAIN4618\nCICSPlex resynchronization request failed.\nReason:\nThis message is produced in conjunction with one or more other messages which give information as to why the request\nfailed.\nAction:\nContact your systems programmer.\nCAIN4619\nCNTL=OFF,ALL,... command syntax error\nReason:\nCNTL=OFF,ALL syntax rules are:\n1.TTR= and FTR=, or USR= are required. TTR and FTR terminal IDs must be equal. .ANY or .ALL not allowed\n2.No other CNTL options are allowed on the command\nExample:\nCNTL=OFF,ALL,TTR=T001,FTR=T001\nCNTL=OFF,ALL,USR=SMIJO01\nAction:\nCorrect the command and resubmit.\nCAIN4620\nNo breakpoints found for TTR/FTR=terminal or USR=userid\nReason:\nCNTL=OFF,ALL,... command did not find any breakpoints for the TTR/FTR=terminal or USR=userid.\nAction:\nEnsure that you specified the correct terminal or user id.\nCAIN4621\nProgram is not COBOL \u2013 (*) option disregarded.\nReason:\nThe indicated option is only valid for COBOL programs.\nAction:\nSelect a valid option.\nCAIN4622\nMonitor logging *\nReason:\nMonitor logging has been started, stopped, canceled, or deleted.\nAction:\nNo action is required.\nCAIN4623\nMonitor logging error *\n 1674", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8843fa683905-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReasons:\nWrite failed.\nSession not found.\nStop failed. \nDelete failed.\nStart failed.\nCancel failed. No active session.\nPROTMLOG file not available. \nAction:\nCorrect the command entered and retry.\nCAIN4701\nRequested service NOT SUPPORTED Request Bytes = xxxxxx\nReason:\nAn INVALID request was made by one of the InterTest for CICS programs. This is an internal problem.\nAction:\nFollow these steps:\n1.Try the request again\n2.If you still have the problem, contact Broadcom Support  for assistance.\n \nCAIN4702\nUTILITY in Progress Request NOT PROCESSED\nReason:\nThe InterTest for CICS Symbolic File was found to be in use by batch UTILITY program.\nAction:\nFollow these steps:\n1.Try request again\n2.Run a batch utility REPORT function and then retry request\n \nCAIN4703\ninvalid sequence number\nReason:\nAn internal error occurred while reading data from the InterTest for CICS Symbolic file.\nAction:\nTry recompiling the program and if the problem persists, call Broadcom Support .\nCAIN4704\nstatement number is invalid\nReason:\nThe specified statement number could not be found on the InterTest for CICS Symbolic File for the requested program.\nAction:\nIf the program is PL1, this statement may have been removed due\n 1675", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "147a0d3ae660-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4705\nSubscripts are not supported for this variable\nReason:\nThe PL1 variable was not defined as an array or the dimensions of the array could not be determined.\nAction:\nNone.\nCAIN4707\nprogram NOT FOUND IN ANY SYMBOLIC FILE\nReason:\nThe program was not found on any symbolic file.\nAction:\nSpecify a correct program name and retry the command.\nCAIN4708\nrequest NOT SUPPORTED for xxxxx\nReason:\nA request has been made which is not supported for the language, indicated xxxxx.\nAction:\nNone.\nCAIN4709\nprogram MUST be at a BREAKPOINT to service request\nReason:\nTo view a dataitem, the program must be sitting at an InterTest for CICS breakpoint.\nAction:\nNone.\nCAIN4710\nNO STRUCTURE INFORMATION for request\nReason:\nA STRUCTURE (PF12) request was made for a symbolic data item that was not contained in an Assembler DSECT or\nwas COBOL data item that did not have a valid level number. For example: a COBOL paragraph name or an Assembler\ndata item, which was defined within a CSECT.\nAction:\nNone.\nCAIN4711\nSTRUCTURE request is INVALID for a PL/I program\nReason:\nA STRUCTURE (PF12) request was made for a symbolic data item which was defined in a PL/I program. At this time,\nSTRUCTURE requests are invalid for PL/I programs.\nAction:\nNone.\n 1676", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7e2308013429-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4712\nINCORRECT SYNTAX First assembler dataname IS NOT a Register\nReason:\nThe first argument for an ASSEMBLER data name was not found to be a register.\nAction:\nCorrect the command and resubmit the request Syntax: 'register.dataname'\nregister\nSpecifies a symbolic reference for a register, like TIOABAR, or it may be specified as Rn, where n is the register number,\nlike R15 for register 15.\n.\nSpecifies a required delimiter.\ndataname\nSpecifies the name of the data area which you wish to see.\nCAIN4713\nxxxxx Not Found in Symbolic File have ASSUMED its Register\nReason:\nA symbolic request was made for an Assembler data item, with the register value (first argument) of 'Rn'. The 'Rn' name\nwas NOT found in the Symbolic File, but an assumed value was used. For example: the value R15 was specified and not\nfound, so register 15 was used.\nAction:\nCorrect command and resubmit request if the assumed value was incorrect.\nCAIN4714\nSUBSCRIPTS and INDEXES cannot be intermixed\nReason:\nA symbolic request was made for a COBOL data item with the following syntax: 'dataitem(x1,.,xn)' and the values\nspecified for 'x1,.xn' were found to be a mixture of SUBSCRIPTS and INDEX names.\nAction:\nChange the command to specify all SUBSCRIPTS or INDEXES and resubmit the command.\nCAIN4715\nto many SUBSCRIPTS or INDEXES specified\nReason:\nA symbolic request was made for a COBOL data item with the following syntax: 'dataitem(x1,.,xn)' and the number of", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7e2308013429-1", "text": "exceeded the number of OCCURS clauses that could be used.\nAction:\nChange the command to specify the correct number of SUBSCRIPTS or INDEXES and resubmit command.\nCAIN4716\nxxxxxxx not found in Symbolic File\nReason:\nThe data item, indicated by xxxxxxx, was not found in the InterTest for CICS Symbolic File.\nAction:\nCheck for the following conditions:\n 1677", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "62eeb60e981d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022Correct spelling of dataname.\n\u2022The name in the crossreference (The dataname may not be referenced and you compiled with the XREF(SHORT)\noption)\n\u2022Are you using the correct program?\n \nCAIN4717\nxxxxxxx is NEGATIVE\nReason:\nThe SUBSCRIPT or INDEX, specified by xxxxxxx, contained a NEGATIVE value.\nAction:\nCorrect the value and resubmit the request.\nCAIN4718\nxxxxxxx is NOT NUMERIC\nReason:\nThe SUBSCRIPT or INDEX, specified by xxxxxxx, did not contain a NUMERIC value.\nAction:\nCorrect the value and resubmit the request.\nCAIN4719\nxxxxxxx is NOT a NUMERIC DATA TYPE\nReason:\nThe SUBSCRIPT or INDEX, specified by xxxxxxx, was not defined with a NUMERIC PICTURE clause.\nAction:\nChange the command to specify a valid SUBSCRIPT/INDEX, or correct program.\nCAIN4720\nxxxxxxx CANNOT be used for QUALIFICATION\nReason:\nA symbolic request was made for a COBOL data item with the following syntax: 'dataitem2 OF dataitem1' and the value\nspecified for 'dataitem1' was incorrectly specified. This could occur if its level number was greater than or equal to\n'dataitem2' or it was an INDEX name.\nAction:\nCorrect the command and resubmit request.\nCAIN4721\nMultiple OFFSETS found because of COBOL II OPTIMIZER Option\nReason:\nA symbolic request for a COBOL II paragraph name or statement number resulted in more than one offset being found.\nThis occurs because of the use of the COBOL II Optimize feature.\nAction:\nNone.\n 1678", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "faf4ef0dae03-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4722\nxxxxxxx NOT Found or BLOCK NOT Active\nReason:\nA PL1 label (xxxxxxxx) could not be found or the Procedure name block the label is defined in is not active.\nAction:\nRetry when the PL1 Block is active .\nCAIN4723\nxxxxxxx NOT Allocated\nReason:\nStorage for the COBOL dataname (xxxxxxxx) has not been allocated\nAction:\nRetry after the dataname has been allocated .\nCAIN4724\n(*) PROC/BLOCK NOT Active\nReason:\nThe PROC/BLOCK specified is not active.\nAction:\nSpecify an active PROC/BLOCK.\nCAIN4725\nStatement number past the end of the program\nReason:\nSpecified program statement number is greater than the highest statement number in the program.\nAction:\nEnsure that the statement number you specified is defined in the program\nCAIN4726\n(*) BASE pointer not supplied\nReason:\nThe printer was not set up for a BASED variable.\nAction:\nSupply a BASE pointer.\nCAIN4727\nData Item is an INDEX set to occurrence (*)\nReason:\nThe item selected is an INDEX set to (*).\nAction:\nNone.\nCAIN4728\nNO Data Names Index found\nReason:\n 1679", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9a7769e0b5fe-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNo data names index was found.\nAction:\nCheck your compiler options.\nCAIN4729\nSYMBOLIC DATA was created with an older release\nReason:\nThe symbolic data found for the program specified was postprocessed by an older release of InterTest for CICS.\nAction:\nRecompile the program and use the postprocessor from the current release.\nCAIN4730\n(*) NOT FOUND in requested area\nReason:\nThe data (*) was not found in the area that you specified.\nAction:\nChange the area that you are searching or change what you are searching for.\nCAIN4731\nData Item is an INDEX - occurrence could not be calculated\nReason:\nThe data item specified is indexed and InterTest for CICS is unable to calculate the number of times the data item occurs.\nAction:\nSpecify a non-indexed data item.\nCAIN4732\nNo Source Listing saved for program\nReason:\nThere is no source listing saved to the Symbolic File for this program.\nAction:\nCheck your compile options.\nCAIN4733\nCrossReference not saved\nReason:\nThere is no crossreference section saved to the Symbolic File for this program.\nAction:\nUse LISTER=MAP or LISTER=ALL in your InterTest for CICS post compile processor parameters.\nCAIN4734\n(*) not referenced\nReason:\nThe field indicated (*) was defined, but not referenced in the program.\nAction:\nNone.\n 1680", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7041d825bf85-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4735\nNo LinkageEditor data saved for program\nReason:\nThere is no linkageeditor map saved to the Symbolic File for this program.\nAction:\nInterTest for CICS was unable to save the linkageeditor map. Check the linkageeditor step for errors.\nCAIN4736\n88LEVEL items are not supported.\nReason:\nThe data item is defined as an '88' level, and it cannot be referenced by InterTest for CICS.\nAction:\nDo not reference data items defined as 88 level.\nCAIN4737\nQualified Names are only for Based Variables\nReason:\nYou attempted to specify a qualified name for a nonBASED variable.\nAction:\nSpecify qualified names only for BASED variables.\nCAIN4738\nNo Paragraph names were found\nReason:\nThere were no paragraph names found for this program.\nAction:\nNone.\nCAIN4739\nNo Labels were found\nReason:\nThere were no labels found in this program.\nAction:\nNone.\nCAIN4740\nrequest NOT SUPPORTED for an INDEX\nReason:\nThe request you made is not a valid request for an index.\nAction:\nSpecify a valid index request.\nCAIN4741\nNOTAUTH CONDITION RESOURCE LEVEL SECURITY FAILED FOR \"(*)\"\nReason:\n 1681", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "10e62af410a2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nYou are not authorized to perform the requested task. Resource level security checking is in effect.\nAction:\nContact the Security Administrator.\nCAIN4742\nNo procedure names were found\nReason:\nNo procedure names were found to match the specified criteria.\nAction:\nCheck the selection criteria and try again.\nCAIN4743\nPROTSYM record not found file corrupted\nReason:\nThe PROTSYM file is corrupted so the requested record could not be found.\nAction:\nContact your systems programmer for assistance.\nCAIN4744\nSyntax error in command\nReason:\nThere was a syntax error in the command.\nAction:\nCorrect the command syntax and try again.\nCAIN4745\nToo many indexes specified\nReason:\nMore indexes were specified than are allowed. COBOL and PL/I support 7 and 15 levels of subscripting, respectively.\nAction:\nCorrect the request and resubmit.\nCAIN4746\nProgram language is not supported\nReason:\nThe language used in the specified program is not supported.\nAction:\nNone.\nCAIN4747\nToo many qualifications (max = 15)\nReason:\nMore than 15 qualifications were requested.\nAction:\nCorrect the request and try again.\n 1682", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "37e46677feff-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN4748\nIndexed qualified names are not supported\nReason:\nA request was made for indexed qualified names but this is not supported.\nAction:\nNone.\nCAIN4749\n(*) contains too many numeric digits\nReason:\nThe field specified contains too many numeric digits.\nAction:\nCorrect the request and resubmit.\nCAIN4750\n(*) datatype not supported for subscript\nReason:\nThe specified datatype is not supported for subscripting.\nAction:\nNone.\nCAIN4751\nReference Modification fields are out of range\nReason:\nThe values entered for the starting point and/or length reference a location that is greater than the dataname's length.\nAction:\nCorrect the erroneous fields and reenter the request.\nCAIN4752\nReference Modification field not positive number\nReason:\nEither the starting position or the length field is not a positive number.\nAction:\nCorrect the field and reenter the request.\nCAIN4753\nArray usage requires latest postprocessor output\nReason:\nYour PL1 program needs to be recompiled and post processed with the latest PL1 PostProcessor module IN25SYMP.\nThis new version has enhanced support for displaying PL1 arrays.\nAction:\nRecompile your program using the newest PL1 postprocessor.\nCAIN4901\nInterTest RELEASE (*) NOT COMPATIBLE WITH CICS RELEASE (*)\n 1683", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "245018a3438d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nThe release of InterTest for CICS is not compatible with the release of CICS.\nAction:\nInstall a compatible version of InterTest for CICS, or contact Broadcom Support .\nCAIN4902\nEND OF TRANSACTION\nReason:\nThe transaction has ended.\nAction:\nNone.\nCAIN4903\nINCORRECT VERSION OF IN25OPTS SHOWN VALUES MAY BE INCORRECT\nReason:\nInterTest for CICS has determined that an incorrect version of IN25OPTS is being used, and the values may be incorrect.\nAction:\nRegenerate IN25OPTS.\nCAIN4904\nNO IN25OPTS TABLE FOUND DEFAULTS ARE DISPLAYED\nReason:\nIN25OPTS module was not found, and the defaults are displayed.\nAction:\nGenerate an IN25OPTS module.\nCAIN4905\nInvalid option or command entered.\nReason:\nAn invalid option or command was entered.\nAction:\nCorrect the request and retry.\nCAIN4906\nCurrent GENLEVEL is 970\nReason:\nThis message informs you of your site's current GENLEVEL of InterTest for CICS.\nAction:\nNone.\nCAIN4624\nIncorrect path set for headless debugging *\nReasons:\nUSS path not found, has incorrect syntax, or is more than 243 characters long.\n 1684", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6fc911b2682d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\n\u2022Correct the USS path entered in IN25OPTS options.\n\u2022Assemble and refresh IN25OPTS options.\nCAIN4625\nError loading API for headless debugging *\nReason:\nCAVHFMIO API load failed.\nAction:\nContact Broadcom Support .\nCAIN4626\nBreakpoints are not allowed on statements that contain ENTRY verbs\nReason:\nStatement contains an ENTRY verb.\nAction:\nPut the breakpoint on the next statement.\nCAIN5101\nLANG= value doesn't match install options\nReason:\nInterTest for CICS has determined that the LANG= value does not match the installed options.\nAction:\nCheck the LANG= parameter, and select an installed option.\nCAIN5102\nTerminal ID specified is invalid or not installed\nReason:\nThe terminal specified was not found or has not been installed.\nAction:\nSpecify a valid terminal or install the terminal you want to use.\nCAIN5103\nCA InterTest profile update failed\nReason:\nYour request to update the InterTest for CICS profile failed.\nAction:\nCheck your request for errors. If you find None, contact Broadcom Support .\nCAIN5104\nLoad on IN25OPTS failed\n 1685", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "20a0f987a5dd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nModule IN25OPTS was not loaded due to an error.\nAction:\nCheck the assembly and CHEDT of IN25OPTS, and try to load the module again.\nCAIN5105\nInvalid keyword in command\nReason:\nYou have specified an invalid keyword in your command.\nAction:\nCheck your spelling. Specify a valid command.\nCAIN5198\nCA InterTest profile updated with default options\nReason:\nThe InterTest for CICS profile has been updated with the default options.\nAction:\nNone.\nCAIN5199\nCA InterTest profile updated\nReason:\nThe InterTest for CICS profile has been updated.\nAction:\nNone.\nCAIN5301\nVIRC: TERMINAL STORAGE GETMAIN FAILURE=\nReason:\nA Terminal Storage getmain request failed in transaction VIRC.\nAction:\nEnsure that your CICS region has enough DSA storage available. If it does, contact Broadcom Support .\nCAIN5302\nVIRC: CRTE TRANSACTION NOT FOUND IN TOR\nReason:\nThe CICS 'CRTE' transaction is not defined in the TOR\nAction:\nEnsure that the TOR has the CRTE transaction id defined.\nCAIN5303\nVIRC: TRANSACTION STARTED WITH NO DATA\nReason:\nThe InterTest for CICS VIRC transaction was started improperly.\nAction:\n 1686", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5a0200f140db-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nEnsure that InterTest for CICS was installed properly for MRO usage, and that there are no nonInterTest programs in your\nCICS region that issue a START for program IN25VIRC.\nCAIN5304\nVIRC: A REMOTE VTAT TRAN NOT DEFINED IN TOR=XXXX FOR AOR=XXXX\nReason:\nThe required InterTest for CICS transactions were incorrectly defined for MRO operation.\nAction:\nOne VTAT transaction must be defined as local in each AOR. A remote VTAT transaction must be defined in the TOR for\neach AOR One VIRC transaction must be defined as local in the TOR and AORs.\nExample:\nTOR AOR1 AOR2\nVTA1 >VTAT\nVTA2 >VTAT\nVIRC VIRC VIRC \nCAIN8000\nThe latest Symbolic file version does not match the current load module\nReason:\nYou have multiple symbolic versions of the program and the datetime of the load module does not match the most\nrecently compiled symbolic version. If an older version of the program matches the load, it is indicated as DATE/TIME\nMATCH in the Symbolic File Selection Screen Comment field.\nAction:\nIf the load module is the correct version (you did not forget to do a NEW COPY after recompiling, then select the symbolic\nfile which matches the load. If you forgot to do a NEW COPY after recompiling then Clear the screen, new copy the\nprogram, and retry the request\nCAIN8001\nWARNING ssssssss Symbolic yyddd/hh:mm mismatches load yyddd/hh:mm\nReason:\nThe active load module is out of sync with the preselected symbolic file, or does not match any symbolic file members.\nPossible causes of this message are:\n\u2022", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5a0200f140db-1", "text": "Possible causes of this message are:\n\u2022\n\u2022A symbolic file was previously selected and it does not match the active load module.\n\u2022\n\u2022The program was recompiled after a symbolic file was preselected, and a CNTL=NEW was not executed.\n\u2022\n\u2022One or more of your symbolic files is defined incorrectly or not available. The VRPT transaction (Option 03) can be\nused to display your symbolic files and their statuses.\n\u2022\nAction:\nPress Enter and continue with breakpoint using the program from the ssssssss symbolic file. Once at the breakpoint\nscreen you can continue monitoring, or abend the task, correct the mismatch problem, and reexecuted the program.\nCAIN8002\nWARNING Symbolic file date/time not equal to module date/time.\n 1687", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "321018da7387-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nYou have one symbolic version of a COBOL or PL/I program and it does not match the current load module datetime. The\npossible causes of this message are as follows:\n\u2022\n\u2022You don't have the proper symbolic files and load libraries defined.\n\u2022\n\u2022Your PL/I program may have been postcompiled with a InterTest for CICS release earlier than 4.4 or 5.3.\n\u2022\n\u2022Your PL/I compiler was installed with the TSTAMP=NO option.\n\u2022\n\u2022You recompiled your program and did not do a CEMT NEW copy or CNTL=NEW.\n\u2022\nAction:\nPress Clear to cancel the LIST or process the CNTL command with no symbolics, or select a symbolic to use. In either\ncase, you have an outofsync problem that you should correct.\nCAIN8003\nInvalid character entered\nReason:\nA character other than S was specified next to a symbolic file.\nAction:\nTry selecting a symbolic file by specifying S.\nCAIN8004\nNo selection made.\nReason:\nYou pressed ENTER without selecting a symbolic file.\nAction:\nEither select a symbolic file, or press Clear to cancel the LIST request or process the CNTL request with no symbolics.\nCAIN8005\nOnly one \"S\" may be entered\nReason:\nYou tried to select more than one symbolic file.\nAction:\nEither select a single symbolic file, or press Clear to cancel the LIST request or process the CNTL request with no\nsymbolics.\nCAIN8006\nMatching Symbolic must be used. Symbolic display will be switched*\nReason:\nYou tried to set monitoring for a non matching symbolic file and there is a matching load/protsym combination available.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "321018da7387-1", "text": "InterTest for CICS is going to switch the display to the matching symbolic for you.\nAction:\nReview and respecify your monitoring request using the proper symbolic file that matches the load module.\n 1688", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f580ff2533c5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN8981\nLine commands D, H, and R are valid for file PROTDMP only\nReason:\nAn attempt was made to Delete, Hold, or Release a dump not belonging to this region.\nAction:\nYou can only Delete, Hold, or Release dumps belonging to the current region's Dump file.\nCAIN8982\nInternal trace was empty at dump capture, trace unavailable\nReason:\nThere was no information to gather for the trace, so no trace was taken. The CICS Systems Initialization Table (SIT)\nspecifies no internal tracing is to be performed in the region.\nAction:\nContact your systems programmer.\nCAIN8983\nCA InterTest is not started\nReason:\nInterTest for CICS has not been started.\nCAIN8007\nPROTSYM version mismatch. DWARF data available.\nReason:  There is no PROTSYM file for this load module, or you have multiple symbolic versions of the program and\nthe date/time of the load module does not match the most recently compiled symbolic version. If an older version of the\nprogram matches the load, it will be indicated as DATE/TIME MATCH in the Symbolic File Selection Screen Comment\nfield. However, DWARF data is available which is always a match.\nAction:  Either use DWARF, or if the load module is the correct version, then select the symbolic file which matches the\nload. If there is no matching symbolic file available, CLEAR the screen, create a NEW COPY of the program, and retry the\nrequest.\nInterTest Batch Messages and Abend Codes\nInterTestBatch Messages and Abend Codes\nABA00\nPROGRAM CHECK INTERRUPTION WHILE PROCESSING I/O REQUEST\nABA03\nWHEN TASK ATTEMPTED TO TERMINATE, ONE OR MORE SUBTASKS NOT TERMINED\nABA05", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f580ff2533c5-1", "text": "ABA05\nAREA TO BE FREED BY FREEMAIN MACRO OVERLAPPED\nReason:  Free area in virtual storage or part of the area was still fixed in real storage.\n 1689", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "46f31b755515-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nABA06\nPRIOR REQUEST FOR QUEUED MODULE NOW REQUESTED BY LINK, LOAD, ATT OR XCTL MACRO\nABA0A\nR-TYPE FREEMAIN MACRO SPECIFIED AREA THAT OVERLAPPED\nReason:  Free area in virtual storage or part of area was still fixed in real storage.\nABA13\nDATA SET REQUESTED BY OPEN MACRO NOT FOUND (TAPE ONLY)\nABA14\nCLOSE MACRO ENCOUNTERED I/O ERROR WHILE ATTEMPTING PARTIAL RELEASE OF SPACE IN DASD\nCAMRA011\nNO MEMBERS IN LIBRARY\nReason:  The library specified contains no members.\nCAMRA012\nNO MATCHES\nReason:  The pattern specified produced no matches.\nCAMRA013\nCAN'T OPEN LIBRARY\nReason:  An error occurred when opening specified library.\nCAMRA014\nFREED\nReason:  All possible ddnames were freed.\nCAMRA028\nMEMBER IS EMPTY\nReason:  The member does not contain any JCL.\nCAMRA029\nNOT AN EXEC STATEMENT\nReason:  Selected statement is not a valid JCL statement.\nCAMRA033\nCANNOT LOAD JCLCHECK\nReason:  Load module JCLCHECK cannot be found or loaded.\n 1690", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b742f461d32c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAMRA034\nNO PROCLIB\nReason:  You must supply at least one PROCLIB\nCAMRA035\nINVALID DSN\nReason:  The data set name is not valid.\nCAMRA036\nDDNAME NOT ALLOCATED\nReason:  The ddname specified was not pre-allocated as required.\nCAMRA037\nSELECTION NOT ALLOWED\nReason:  Member selection list is not allowed; member name is required.\nCAMRA038\nSOME ALLOCATIONS FAILED\nReason:  Review for highlighted allocations errors.\nCAMRA090\nDDNAME REQUIRED\nReason:  Data set cannot be allocated without ddname.\nCAMRA092\nBROWSE/EDIT ERROR\nReason:  ISPF is unable to browse or edit selected data set.\nCAMRA093\nINVALID LINE COMMAND\nReason:  Enter ALLOCATE, BROWSE, CONVERT (CLIST), EDIT, or FREE.\nCAMRA094\nINVALID LIBRARY TYPE\nReason:  Only PDS, Librarian , and Panvalet  are supported.\nCAMRA095\nNOTHING TO ALLOCATE/FREE\nReason:  The member contains only messages or empty lines.\n 1691", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "74ac93464b11-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAMRA097\nNO ALLOS TO ALLOCATE\nReason:  ALIB member is empty or contains only message allos.\nCAMRA098\nINTERNAL ERROR - PLIST\nReason:  Invalid PLIST supplied.\nCAMRA099\nCANNOT LOAD FAIR/OPEN ERROR\nReason:  Cannot load Librarian  FAIR modules or OPEN failed.\nCAMRA101\nINVALID LINE CMD\nReason:  Enter BROWSE, EDIT/SELECT, ALLOC, FREE, or CONVERT.\nCAMRA102\nMEMBER NAME REQUIRED\nReason:  Enter a member name in the provided field.\nCAMRA103\nMEMBER REPLACED\nReason:  Member was replaced in data set.\nCAMRA104\nINVALID LINE CMD\nReason:  Enter F to free, B to browse, or E to edit.\nCAMRA105\nINVALID LINE CMD\nReason:  Enter B to browse or S to select for JCL conversion.\nCAMRA107\nINVALID LINE CMD\nReason:  Enter I, D, R, S, AL, or F line command.\nCAMRA301\nOPEN ERROR\nReason:  OPEN failed for ALIB library.\n 1692", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "09aecf8ea832-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAMRA302\nMEMBER NOT FOUND\nReason:  Requested member was not found in library.\nCAMRA303\nFIND ERROR\nReason:  FIND caused an error other than not found.\nCAMRA304\nINVALID RECORDS\nReason:  Invalid ALLO records found in member.\nCAMRA305\nEMPTY MEMBER\nReason:  Member requested contains no records.\nCAMRA306\nNEW MEMBER\nReason:  Member not found in library; new member created.\nCAMR900E\nInitialization error - CA LMP not installed.\nReason:\nThe license management component of Common Components and Services  was not installed properly.\nAction:\nContact Broadcom Support .\nCAMR901E\nCAVHCONF module not found in the CSA.\nReason:\nThe CAVHCONF configuration module was not found in the CSA.\nAction:\nCheck with your system programmer to ensure that the CAVHINIT process was run.\nCAMR902W\nCA InterTest not available on this system as set in CAVHCONF.\nReason:\nThe CAVHCONF configuration module, which is loaded into the CSA, indicates that the product is not intended to be used\non this system.\n 1693", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e0e337a10aa5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nCheck with your system programmer to ensure that the CAVHCONF configuration macro was implemented correctly on\nthis system and that the CAVHINIT process was run.\n \nCAMR910E\nSYM RECORD WITHOUT SYMBOLIC OPERAND\nCAMR911E\nSYM REPLACEMENT RECORD NOT FOUND\nCAMR912E\n\"PGM=\" NOT FOUND IN PROGRAM RECORD\nCAMR914E\nIBM DB2 \"SYSTSIN\" DD NOT FOUND\nCAMR915E\nIBM DB2 \"LIB\" STATEMENT ERROR\nCAMR916E\nIBM DB2 \"LIB\" STMT INVALID DSNAME\nCAMR917E\nIBM DB2 \"PROGRAM\" STATEMENT ERROR\nCAMR950I\nSVC INTERCEPT INSTALLED SUCCESSFULLY\nCAMR951E\nSVC NUMBER WAS NOT SPECIFIED\nReason:\nAn SVC number is required when the CAVHINIT initialization program executes on an LPAR that has InterTest Batch\nenabled.\nAction:\nSpecify a three-digit SVC number from 200 to 255 in your CAVHINIT parameters.\n 1694", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "06e868a0d9d0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAMR952E\nINVALID ARGUMENT LENGTH\nCAMR954E\nVALUE OUT OF RANGE (MUST BE 200-255)\nCAMR955E\nUNABLE TO LOAD SVC INTERCEPT MODULE\nCAMR956E\nUNABLE TO LOAD SVC INTERCEPT PROLOGUE\nCAMR957E\nUNABLE TO INSTALL SVC INTERCEPT\nCAMR960E\nSYSTEM NOT INITIALIZED FOR BATCH LINK, REPLY \"RETRY\" OR \"CANCEL\"\nCAMR961E\nINT1OPTS DD MISSING OR INVALID\nReason:  The INT1OPTS DD statement was not included in the JCL for a Batch Link step, or the file referenced by the DD\nstatement is the wrong format for Batch Link options. Correct the JCL and resubmit the job.\nCAMR962E\nEXEC= OPTION MISSING OR INVALID\nReason:  The INT1OPTS DD statement did not contain any EXEC= option, or the name specified was invalid. Correct the\nJCL and resubmit the job.\nCAMR963E\nEXEC=CAMRBL01 IS NOT VALID IN INT1OPTS\nReason:  EXEC=CAMRBL01 in INT1OPTS is not valid when you submit batch jobs for Batch Link.\nCAMRS01W\nBLSCHTBL NOT ANCHORED.\nReason:  Batch Link Schedule table not created and anchored off the CAAT. Review the initialization job log to determine\ncause. Rerun the initialization after correcting the cause.\nCAMRS02E\nINT1SKUT DD NOT FOUND.\n 1695", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "26b925293fa1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:  The DD statement with INT1SKUT name was not found in the job stream. Correct error and rerun the\nappropriate job.\nCAMRS03E\nCANNOT DETERMINE DSORG. EXPORT ABORTED.\nReason:  Export operation has aborted because the DSORG of the dataset pointed to by INT1SKUT DD statement is\nunknown. DSORG must be either PS or PO.\nCAMRS04E\nINVALID MEMBER NAME SPECIFIED FOR SEQUENTIAL DATASET. EXPORT ABORTED.\nReason:  Export operation has aborted because a member name was specified for a sequential dataset. Correct the error\nand rerun Export.\nCAMRS05E\nPDS WITH NO MEMBER NAME SPECIFIED.\nReason:  Schedule found a partitioned dataset but there was no member name specified. Correct the error and rerun the\njob.\nCAMRS06I\nSCHEDULE EXPORTED TO ==> xxxxx\nReason:  Schedule is being exported to an external dataset named xxxxx.\nCAMRS07I\nTOTAL RECORDS EXPORTED TO INT1SKUT DD: nnnn \nReason:  During a Schedule Export operation, nnnn records were exported to the INT1SKUT DD.\nCAMRS08I\nBLSCHTBL IS EMPTY.\nReason:  Batch Link Schedule Table was found anchoring off CAAT, however it does not contain any active schedules.\nCAMRS09E\nDSORG NOT SUPPORTED, EXPORT ABORTED.\nReason:  Schedule Export operation has aborted due to the DSORG of the dataset pointed to by INT1SKUT DD\nstatement is of a type not supported. DSORG must be either PS or PO.\nCAMRS10I\nINT1SKUT DD OPENED.\nReason:  Informational message.\nCAMRS011I", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "26b925293fa1-1", "text": "Reason:  Informational message.\nCAMRS011I\nINT1SKUT DD OPEN FAILED.\nReason:  The dataset pointed to by the INT1SKUT DD statement cannot be opened. Determine cause and rerun the job.\n 1696", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "afc1896bd888-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAMRAS12I\nRECORD SKIPPED. INVALID DB TYPE\nReason:  Schedule IMPORT operation found an import record with an invalid TYPE. The record is not imported.\nCAMAS13I\nIMPORT DSN ==> xxxxx\nReason:  xxxxx is the fully qualified dataset containing the Schedule to be imported.\nCAMRS14W\nSCHEDULE IMPORT NON ZERO RC = nn\nReason:  Import operations received a non zero return code of nn. Possible RC from Import:\n0 = Import successful\n4 = BLSCHTBL either is not anchored or does not exist\n8 = INT1SKUT DD statement is missing.\nCAMRS15I\nRECORDS READ FROM INT1SKUT DD: nnnnn\nReason:  During a Schedule Import operation, nnnn records were imported\nCAMRS16I\nBATCH LINK SCHEDULE IMPORTED\nReason:  Informational Message.\nCAMRS17I\nSCHEDULE WILL BE IMPORTED TO REFRESH BLSCHTBL\nReason:  The default refresh option will be used to import the Schedule.\nCAMRS18I\nSCHEDULE WILL BE ADDED TO BLSCHTBL.\nReason:  ADD option specified by the Execution PARM is used to add from external dataset to the current active\nschedules in CSA.\nCAMRS19E\nINT1SKUT DD OPEN FAILED.\nReason:  Open of dataset pointed to by INT1SKUT DD card failed.\nCAMRS20E\nINT1SKUT DD CARD NOT FOUND.\nReason:  INT1SKUT DD card is missing from the execution JCL. Make sure the DD Name is correctly spelled.\n 1697", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fd845e566147-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAMRS20E0\nBATCH LINK SCHEDULE NOT IMPORTED.\nReason:  For reasons stated in previous messages, the Batch Link Schedule was not imported.\nCAMRS21I\nINT1SKUT CLOSED.\nReason:  Informational message.\nCAMRS22W\nBLSCHTBL NOT ANCHORED.\nReason:  The Batch Link Schedule table is not anchored off CAAT. Review the initialization job log to determine cause.\nCorrect error and rerun export operation.\nCAMRS23I\nSP241 ACQUIRED AT ADDR ==> xxxxxxxx\nReason:  Information. Subpool 241 at address xxxxxxxx was acquired for Batch Link Schedule in-core table.\nCAMRS24E\n#CAAT ADD CA ANCHOR FAILED. RC=nn\nReason:  The #CAAT facility to add Batch Link Schedule table failed. Return code is nn. Make sure the initialization\nprogram, CAVHINIT, is executing out of an APF authorized library.\nCAMRS25W\nSP241 GETMAIN FAILED.\nReason:  GETMAIN for Subpool 241 storage failed. This could be caused by excessive number of entries defined as\nSCHTBSIZE in CAVHCONF. Each entry requires 27 bytes. Another likely cause - your CSA is over utilized. Discuss this\nissue with your Systems Programmer.\nCAMRS26I\nACQUIRED SP241\nReason:  Informational message.\nCAMRS27I\nCA ANCHORED ADDED.\nReason:  Informational. The Batch Link Schedule table was successfully anchored by the initialization routine.\nCAMRS28W\nCAMBSTBZ LOAD FAILED. SCHEDULING DISABLED.\nReason:  LOAD of CAMBSTBZ table failed, Batch Link Scheduling facility has been disabled. Make sure the load library", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fd845e566147-1", "text": "containing CAMRBSTBZ is in the STEPLIB concatenation stream. Rerun the initialization routine.\n 1698", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fbf97685e86d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAMRS29I\nMAXIMUM SCHEDULE ENTRIES DEFINED: nnn\nReason:  Your installation has defined nnn as the maximum number of schedule entries that can be defined in the\nschedule table.\nCAMRS29W\n0 ENTRIES DEFINED. SCHEDULING DISABLED.\nReason:  Informational. The SCHTBSIZE option in CAVHCONF defined 0 entries for Batch Link Schedule table, resulting\nin the Schedule facility being disabled. To enable the Schedule facility, change the value of the SCHTBSIZE option. See\nInstalling for instructions on modifying this table. Rerun InterTest Batch initialization routine.\nCAMRS30I\nNUMBER OF SCHEDULE ENTRIES IMPORTED: nnn\nReason:  The total number of entries successfully imported is nnn entries.\nCAMRS31W\nINSUFFICIENT SCHEDULE TABLE SIZE. nn SCHEDULE ENTRIES NOT IMPORTED.\nReason:  There were nn entries from the INT1SKUT data set not imported due to the size restriction of the Batch Link\nScheduling Table (option SCHTBSIZE in CAVHCONF). A return code of 12 was also raised. To review the entries that\nwere imported, select Option 1 from the InterTest Batch DB2 and IMS Schedule Menu.\nCAMRS32W\nBLSCHTBL IS FULL. CANNOT ADD ANY MORE.\nReason:  The In Core Schedule Table is full. Additional schedule entries cannot be added. A return code of 4 indicated\nsome of the entries from the INT1SKUT data set were added. A return code of 8 indicated that none of the entries from\nthe INT1SKUT were added. You can display the contents of the schedule table by selecting Option 1 from the InterTest\nBatch DB2 and IMS Schedule Menu.\nCAMRS33E", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fbf97685e86d-1", "text": "Batch DB2 and IMS Schedule Menu.\nCAMRS33E\nSLOT NUMBER REQUESTED > MAXIMUM SIZE.\nReason:  Internal schedule component error. Contact Broadcom  for assistance.\nCAMRS34E\nBLSCHTBL SLOT NUMBER ERROR. FOUND=> nnnn.  IN SLOT NUMBER => nnnn.\nReason:  Internal schedule component error. Contact Broadcom  for assistance.\nINTA006\nDATA SET NOT CATALOGED\nReason:  The data set requested on the panel is not a cataloged data set. Check the name of your fully qualified data set\nand retry.\n 1699", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c5a42e1e9cc0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nINTA007\nDATA SET IS AN ALIAS\nINTA008\nCATALOG DOES NOT EXIST\nINTA009\nSYNTAX ERROR IN DSNAME\nINTA010\nINVALID DATA SET NAME\nReason:  The data set name entered has invalid syntax.\nINTA020\nCA PANVALET LIB INVALID\nReason:  Only OS libraries can be specified for output.\nINTA021\nENTER REQUIRED FIELD\nReason:  Enter required field at the cursor.\nINTA110\nINVALID DATA SET NAME\nReason:  The data set name entered has invalid syntax.\nINTA120\nNO DD STATS TRANSLATED\nReason:  The step selected contained no DD statements to translate.\nINTA130\nSTEP NOT FOUND\nReason:  The input JCL either does not contain an exec card, or the step requested on the input specification panel\ncannot be found in the member specified.\nINTA210\nINVALID DATA SET ORG\nReason:  The data set name entered has invalid syntax.\nINTA211\nINVALID RECORD FORMAT\n 1700", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "849abce9bbd8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:  The record format is not fixed.\nINTA212\nINVALID RECORD LENGTH\nReason:  The record length must be 80.\nINTA220\nMISSING DDNAME\nReason:  Ddname must be specified at the cursor position.\nINTA221\nNO DSN, TERM, OR SYSOUT\nReason:  Enter a data set name, terminal, or SYSOUT at the cursor.\nINTA222\nINVALID DATA SET NAME\nReason:  Check data set name.\nINTA223\nINVALID DISPOSITION\nReason:  The DISP is incorrect. Valid DISP entries are SHR, OLD, and NEW.\nINTA224\nINVALID COMMAND\nReason:  An invalid command was entered on the command line.\nINTA225\nINVALID RECORD FORMAT\nReason:  Check record format.\nINTA226\nINVALID DSORG\nReason:  Use a DSORG of PS or PO.\nINTA300\nMSL BUILD ERROR PDS ERR\nINTA301\nMSL BUILD ERROR PAN ERR\nReason:  A Panvalet  read error or access error may have occurred.\n 1701", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "06f834025984-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nINTA302\nMEMBER NOT FOUND\nReason:  The member name requested on the panel cannot be found in the specified PDS.\nINTA303\nNOT A PDS OR PANLIB\nReason:  Input file is neither a PDS nor a PANLIB.\nINTA304\nMEMBER NOT FOUND/PRESENT\nReason:  Selected member was not found or not present during ALIB I/O.\nINTA305\nI/O ERROR ON DIRECTORY\nReason:  An I/O error occurred during the read of a PDS directory.\nINTA306\nINPUT FILE NOT PRE-ALLOC\nReason:  The input file was not pre-allocated or the allocation failed.\nINTA307\nINPUT FILE OPEN ERROR\nReason:  The input PDS you have entered is an ALIB, with a RECL=150. The input data set can be either a JCL PDS or a\nCA PANVALET LIB.\nINTA308\nOUT FILE NOT PRE-ALLOC\nReason:  The output file was not pre-allocated or the allocation failed.\nINTA309\nOUTPUT FILE OPEN ERROR\nReason:  The output PDS you have entered as an ALIB is not defined correctly. An ALIB PDS must be defined as\nRECL=150.\nINTA310\nINVALID ACCESS CODE\nReason:  Enter this member's correct access code.\nINTA311\nMEMBER NOT READ\nReason:  An internal error occurred when trying to read member.\n 1702", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "45be9939e276-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nINTA312\nINVALID CONTROL CODE\nReason : Enter this library's correct control code.\nINTA510\nALLOCATION FAILED\nReason:  The browse temporary data set could not be allocated.\nINTA520\nDCB OPEN FAILED\nReason:  The browse temporary data set could not be opened.\nINTA610\nCLIST ERROR HAS OCCURED\nINTA620\nCLIST WRITE ERROR\nReason:  An error occurred during CLIST file write.\nINTA621\nCLIST BUILD ERROR\nReason:  An error occurred during CLIST build.\nINTAK210\nDATA SET NOT AVAILABLE\nReason:  The DISP specified is requesting exclusive control and the data set may already be in use.\nINTAK218\nVOLUME IS NOT MOUNTED\nReason:  The volume specified in the JCL is not active. Modify the volume and retry allocation\nINTAK219\nUNIT NAME UNDEFINED\nReason:  The specified unit name is undefined in DSNAME allocation.\nINTAK350\nINVALID PARM IN TEXT\nReason:  There is an unacceptable parameter in the JCL. The JCL being used is not valid for execution in batch. Modify\nthe JCL and retry allocation.\n 1703", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a4cfbc6664de-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nINTAK360\nINVALID KEY IN TEXT\nReason:  Invalid key specified in text unit (all SVC 99 functions).\nINTAK364\nDSNAME ALLOCATION ERROR\nReason:  JOBLIB, STEPLIB, JOBCAT, and STEPCAT are not valid ddnames for TSO.\nINTAK368\nUNAUTHORIZED USER\nReason:  An authorized function was requested by an unauthorized user.\nINTAK369\nINVALID PARAMETER LIST\nReason:  Invalid parameter list format (all SVC 99 functions).\nINTAK410\nDDNAME UNAVAILABLE\nReason:  One of the ddnames being allocated is already defined to your TSO session. Free the DD and try to allocate\nagain.\nINTAK420\nDDNAME IS OPEN\nINTAK438\nDDNAME NOT ALLOCATED\nINTAK448\nDATA SET ALREADY EXISTS\nReason:  Occurs when attempting to allocate a data set with a DISP=NEW and the data set already exists.\nINTAL708\nDATA SET NOT CATALOGED\nReason:  One of the data sets in your JCL is defined with a DISP=OLD or SHR and the data set is not cataloged.\nINTAM100\nINVALID OPTION\nReason:  Options 1, 2, 3, 4, and 5 are the only options available.\n 1704", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a439f175fc30-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nINTAM704\nDUPLICATE DSN ON VOL\nINTAM714\nSPACE NOT AVAILABLE\nReason:  The JCL you are attempting to allocate contains a new data set, and the volume specified for that data set does\nnot have sufficient space to allocate it. Specify another volume.\nINTAN708\nCATALOG ERROR\nReason:  Structure inconsistent.\nINTB000\nFUNCTION FAILED\nINTB001\nCATALOG I/O ERROR\nINTB002\nCATALOG I/O ERROR\nINTB003\nINVALID MEMBER NAME\nINTB004\nINVALID DATA SET NAME\nINTB005\nVOLUME NOT AVAILABLE\nINTB006\nDAIR ERROR\nReason:  Error occurred using Dynamic Allocation Interface Request.\nINTB007\nDAIR CATALOG ERROR\nINTB008\nDAIR ALLOCATE ERROR\n 1705", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0d21abef5f03-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nINTB009\nDAIR FREE ERROR\nReason:  Dynamic Allocation Interface Request attempted to free a data set via ddname unsuccessfully.\nINTB100\nNOTHING TO ALLOCATE\nReason:  Allocate was requested but no ddnames existed to allocate.\nINTB101\nREQUEST BLOCK FAILURE\nReason:  GETMAIN failed to get storage for request block in SVC99.\nINTB102\nPAGE FAILED FOR TEXTUNIT\nReason:  GETMAIN failed to get a page for SVC99 text units and PTR\nINTG001\nINVALID LINE COMMAND\nINTG002\nNUMBER IS INVALID\nReason:  A number is not allowed with the \"AL\" line command\nINTG003\nMEMBER NOT FOUND\nReason:  Selected member was not found.\nINTG005\nINVALID PRIMARY COMMAND\nReason:  Enter UP, DOWN, END, RETURN, SELECT, or LOCATE.\nINTG007\nNO OPERATOR FOUND\nReason:  Operator for command not present or valid.\nINTG008\nMEMBER IS SAVED\nReason:  Intaenter has overwritten the input member and DSN\n 1706", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c46c6e6ed595-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nINTG009\nMEMBER IS CREATED\nReason:  Intaenter has written to a new member or DSN.\nINTG101\nCOMMAND NOT FOUND\nReason:  Command is either not found or miskeyed.\nINTG102\nMEM REPLACE NOT ALLOWED\nReason:  REPLACE NO was specified on out panel. Use Y.\nXDAIR004\nINVALID PARM LIST\nReason:  The parameter list passed to DAIR was invalid.\nXDAIR008\nCATALOG ERROR\nReason:  An error occurred in the catalog management routine.\nXDAIR016\nNO TIOT ENTRIES\nReason:  No TIOT entries are available for use.\nXDAIR020\nDSNAME UNAVAILABLE\nReason:  The data set requested is not available.\nXDAIR024\nDSNAME IS CONCATENATED\nReason:  DSNAME requested is a member of a concatenated group.\nXDAIR028\nDSNAME IS NOT ALLOCATED\nReason:  DSN is not allocated or its attribute list is not found.\nXDAIR032\nDSN PREVIOUSLY ALLOCATED\nReason:  DSN previously allocated permanently, DISP=NEW not allowed.\n 1707", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ad1fe97e23b5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nXDAIR036\nERROR OCCURRED IN CATLG\nReason:  An error occurred on a catalog information routine (IKJEHCIR)\nXDAIR040\nRETURN AREA EXHAUSTED\nReason:  The provided return area is exhausted and more index blocks exist.\nXDAIR044\nDELETE PREVIOUSLY USED\nReason:  You specified DELETE or a request of OLD, MOD, or SHR with no volume.\nXDAIR048\nRESERVED\nXDAIR052\nREQUEST DENIED\nReason:  Request has been denied by installation exit.\n001\nI/O error.\nAttempt to read after AT END.\nReading a wrong length record.\n002\nI/O error.\n003, 004, and 008\nI/O error.\n013\nSomething does not match up between the program and the DD statement. Check the system message (IEC141I)\nfor a more complete description of the error.\n02x\nConflicting DCB for a direct file\n030\nError in DCB for ISAM file.\n 1708", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "271d6b01be85-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n031\nI/O error on an ISAM file.\n032\nError in DCB for ISAM file.\n033\nI/O error on an ISAM file.\n034\nError in DCB for ISAM file.\n035\nError in DCB for ISAM file.\n036\nNo prime data area was specified for an ISAM file.\n037\nInvalid buffer length was specified.\n038\nThe index area is too small.\n039\nEND-OF-DATA problem with an ISAM file.\n03A\nI/O error on an ISAM file.\n03B\nOpening an ISAM file that is already open.\n03C\nError in DCB for an ISAM file.\n03D\nConflict in DCB for ISAM file - the DCB=DSORG=IS was omitted.\n 1709", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fb1e28b96969-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n03E\nI/O error during the load of an ISAM file.\n0C1, 0C2, and 0C3\nInvalid or missing DD statement.\nReading or writing an unopened file.\nRunaway or uninitialized subscript or index.\nDropping out of end of program.\n0C4 and 0C6\nInvalid or missing DD statement.\nReading or writing an unopened file.\nRunaway or uninitialized subscript or index.\nDropping out of end of program.\nOpening or closing a file twice.\nCoding equal BLKSIZE and LRECL for variable length records.\nOmitting a parameter from a CALL list.\nUsing a divisor or multiplier that is too large.\nUsing the wrong SORTLIB in a COBOL sort.\n0C7\nData item not initialized.\nDISPLAY data moved to a numeric group item.\nImproper definition in LINKAGE SECTION.\nImproper definition in FILE SECTION.\nInvalid or improperly aligned data in an input file.\nImproper initialization using MOVE ZERO.\nRunaway or uninitialized subscript or index.\n0C8 and 0CA\nArithmetic overflow: the receiving field of an arithmetic operation is too small.\n0C9 and 0CB\nDivide exception: dividing by zero.\n0CC, 0CD, 0CE, and OCF\nA problem in floating point operation. Did you specify COMP-1 or COMP-2 usage accidentally?\n13E in BMP Region\nCA InterTest Batch END, QUIT, or CANCEL caused a detach error in the BMP region.\n 1710", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e3eebe85e7c8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n213\nThe system could not find the file as specified in the allocate statement. Check system message for further\nReason.\n437\nAn I/O error occurred while processing the end-of-volume condition.\n706\nAttempt to execute a program that has been marked 'not executable' by the linkage editor.\nAttempt to execute an object file.\nAttempt to execute a source file.\n806\nThe load module was not found in the system library or the dynamic STEPLIB you provided.\n80A\nNot enough virtual storage was available to allocate the amount required by the program. Log on specifying\na larger region size and retry. Some data centers have TSO size restrictions. If you specify a size larger than\npermitted, the size allocated will default to the data center's default size.\n90A\nAn area of main storage was released by a program, but it was an area that was not attached to the program. This\nusually means a file was closed twice.\n913\nA security or password violation has occurred.\nB37\nThe file required more direct access space than was requested by the DD statement. This is usually caused by\nincorrect direct access space allocation or a program loop that contains a WRITE statement.\nC03\nThe application that you were debugging has left some files open. Correct the logic in your application to close\nthe files before exiting.\nD37\nThe file required more direct access space than was requested by the DD statement. This is usually caused by an\nunderestimated direct access space allocation or a program loop that contains a WRITE statement.\n 1711", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6047760b06fa-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nE37\nThe volume does not contain enough available space to allocate the amount requested for a file.\n519\nA procedure exit has been reached, and the user has bypassed statements so the references to the calling\nstatement are not defined.\nSymDump  Batch Messages\nThis section defines all the errors, warnings, and informational messages specific to SymDump  Batch. It serves as a\ndebugging tool for programmers using SymDump  Batch in a z/OS environment. \nMessage Format\nAll messages issued by SymDump  Batch are in the format CAP xyyyz , where CAP is the message prefix for SymDump\nBatch and xyyyz  are described in the following table:\nCode Description Value Description\nx Component issuing the\nmessageC\nD\nE\nH\nI\nR\nU\nZExecution Monitor\nSymDump\nAbend Handler\nTSO facility\nRepository Interface\nAnalyzer Reporter\nUtilities\nREST API\nyyy Message number I-999 Message identifier\nz Action to be taken E\nI\nWAn error has occurred.\nProcessing will not continue.\nThis is an informational\nmessage, no action is required.\nThis is a warning message.\nProcessing will continue, but\nthere may be an impact on\nresults.\nThree vertical dots between two messages mean that all message numbers falling between those two numbers produce\nthe same message text and have the same Reason and Action text as the surrounding messages.\nExample:\nCAPR334E . . . CAPR338E\nOptimizer/II  Considerations\nSymDump  Batch can be used as a replacement execution-time environment for Optimizer/II  users. However, some\nmessages specifically relating to the Analyzer and Detector features of Optimizer/II  do not appear in this section.\n 1712", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a668885c10a0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWhen executing OS/VS COBOL programs that have been optimized with the DTECT or XCOUNT option, you may\nencounter individual messages related to these features with the following prefixes that do not appear in this section:\nPrefix Description\nCAPA Analyzer\nCAPC Execution Monitor\nCAPD Detector\nCAPE Extended Detector\nCAPR Reporter\nIf you encounter any messages beginning with these prefixes, you should always refer to this section first.\nCAPC011W\nNO INPUT DATA PRESENT \u2013 INSTALLATION DEFAULTS USED.\nReason:\nThere were no records in the CAIOPTS data set. All the installation-specified option settings in the default CSECT module\napply for this execution.\nAction:\nEnsure that default options are intended; see the Options in Effect section of the Execution Monitor Summary. Make any\nnecessary corrections and rerun.\nCAPC012I\nINPUT OPTION DISPLAY COMPLETE.\nReason:\nThis message is printed on CAIPRINT to announce the end of input data in the CAIOPTS data set.\nAction:\nNone.\nCAPC013I\n'keyword' PARAMETER IGNORED DUE TO PREVIOUSLY DEFINED dddddddd STATEMENT.\nReason:\nThe SYMDSN, PRTLIB, or NDVRDSN parameter was specified in the CAIOPTS data set, but the CAISYM, CAIPRTLB, or\nCAINDVR DD was already coded in the JCL. These parameters cannot be used to override DD statements in the JCL.\nAction:\nThis is an informational message, no action is required. The parameter is ignored.\nHowever, to eliminate this error, remove the DD statement from your JCL or remove the parameter from CAIOPTS.\nCAPC018E", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a668885c10a0-1", "text": "CAPC018E\nDYNAMIC ALLOCATION FAILED FOR DDNAME dddddddd, RC=nn, S99INFO=hhhh, S99ERROR=hhhh.\nReason:\nAn error occurred during an attempt to dynamically allocate the file specified by DDNAME. This could be a simple user\nerror such as a misspelled data set name, or it could be a system problem. nn is the return code from SVC 99. hhhh gives\nvarious informational reason codes about the error encountered during SVC 99 processing.\nDepending on the error, the job step may be terminated. If the allocation was for a symbolic (PROTSYM or CSL) data set,\nexecution continues. However, some symbolic information may not be available in your reports.\nAction:\n 1713", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8e10ea8cdb4c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSee one of the following IBM publications for an interpretation of these SVC 99 error codes, or retain all JCL and console\nlog information and contact Broadcom Support  for assistance.\n\u2022\n\u2022GC28-1150-1 MVS/XA SPL: System Macros and Facilities Volume 1\n\u2022\n\u2022GC28-0627-2 OS/VS2 MVS SPL: Job Management, pages 27-31.\n\u2022\nCAPC020W\n'string' IS NOT RECOGNIZED AND WILL BE IGNORED.\nReason:\nAn unrecognizable keyword has been located in the CAIOPTS DD and is ignored. Scanning resumes with the next token\non the card image or the next record, and execution continues.\nAction:\nCorrect the string on the CAIOPTS DD statement and resubmit the job.\nCAPC021I\n'string' IS AN INVALID OPERAND FOR 'keyword'. KEYWORD REJECTED.\nReason:\nAn unrecognizable operand has been located in the 'keyword' option of the CAIOPTS DD statement that was specified;\nthe operand is ignored. Scanning resumes with the next token on the card image or the next record, and execution\ncontinues.\nAction:\nCorrect the string and resubmit the job.\nCAPC022I\n'string' IS AN INVALID OPERAND FOR 'keyword'. NAME MUST NOT EXCEED 8 CHARACTERS.\nReason:\nA valid keyword is followed by a token (option value) that is greater than 8 characters. The keyword is ignored. Scanning\nresumes with the next token on the card image or the next record, and execution continues.\nAction:\nCorrect the token, make it fewer than 9 characters, and resubmit the job.\nCAPC023I", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8e10ea8cdb4c-1", "text": "CAPC023I\n'string' IS AN INVALID OPERAND FOR 'keyword'. NAME CONTAINS AN INVALID CHARACTER.\nReason:\nA valid 'keyword' is followed by a token (option value) that contains a non-alphanumeric character. The 'keyword' is\nignored. Scanning resumes with the next token on the card image or the next record. Execution continues.\nAction:\nCorrect the token, make it an alphanumeric character, and resubmit the job.\nCAPC024I\n'string' IS AN INVALID OPERAND FOR 'keyword'. VALUE EXCEEDS MAXIMUM ALLOWABLE SIZE.\nReason:\nA valid keyword contains an option value that exceeds the limit placed on the magnitude or size of that value. The value is\nset to the maximum.\n 1714", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f14b5ad2f79f-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nNo action required. However, to eliminate this informational message, correct the value of the option and resubmit the job.\nCAPC025I\n'string' IS AN INVALID OPERAND FOR 'keyword'. VALUE MUST BE NUMERIC.\nReason:\nA valid 'keyword' contains a non-numeric option value. The 'keyword' is ignored, and the default (if any) for this keyword is\nused. Scanning resumes with the next token on the card image or the next record, and execution continues.\nAction:\nNo action required. However, to eliminate this informational message, correct the value of the option and resubmit the job.\nCAPC030I\nCA SymDump Batch RTL INITIALIZATION REQUESTED.\nReason:\nThe RTL initialization program was invoked to initialize the SymDump  Batch RTL.\nAction:\nNone.\nCAPC031I\nCA SymDump Batch RTL INITIALIZATION COMPLETED.\nReason:\nThe SymDump  Batch RTL was initialized successfully.\nAction:\nNone.\nCAPC032E\nCA SymDump Batch RTL INITIALIZATION FAILED.\nReason:\nAn error was encountered while attempting to initialize the SymDump  Batch RTL.\nAction:\nSave all output listings and contact Technical Support.\nCAPC033I\nCA SymDump Batch RTL REFRESH REQUESTED.\nReason:\nThe RTL initialization program was called but the SymDump  Batch RTL was already initialized. A refresh will instead be\nattempted.\nAction:\nNone.\nCAPC034I\nCA SymDump Batch RTL REFRESH COMPLETED.\nReason:\nThe SymDump  Batch RTL was refreshed.\nAction:\nNone.\n 1715", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "38f62d799012-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPC035E\nCA SymDump Batch RTL REFRESH FAILED.\nReason:\nThe SymDump  Batch RTL was not refreshed because the DELETE function failed one or more modules.\nAction:\nSave all output listings and contact Broadcom Support .\nCAPC040I\nCA SymDump Batch RTL TERMINATION REQUESTED.\nReason:\nThe RTL termination program was invoked to terminate the SymDump  Batch RTL.\nAction:\nNone.\nCAPC041I\nCA SymDump Batch RTL TERMINATION COMPLETED.\nReason:\nThe SymDump  Batch RTL was terminated successfully.\nAction:\nNone.\nCAPC042E\nCA SymDump Batch RTL TERMINATION FAILED.\nReason:\nThe SymDump  Batch RTL was not terminated because the DELETE function failed for one or more modules.\nAction:\nSave all output listings and contact Technical Support.\nCAPC043W\nCA SymDump Batch RTL IS NOT INITIALIZED.\nReason:\nThe SymDump  Batch RTL was not terminated because it had not been previously initialized.\nAction:\nNone.\nCAPC077E\nERROR ADDING FILE TO THE CAIPRINT REPOSITORY.\nReason:\nAn error occurred while adding a CAIPRINT report to the central VSAM repository.\nAction:\nReview the supplementary CAPC077E message that follows for more information about the nature of the error. Take\nappropriate steps to resolve the indicated error. A list of supplementary CAPC077E messages follows:\n 1716", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fbd8d9330002-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022CAPC077E Invalid request\n\u2022CAPC077E Unable to allocate ACB\n\u2022CAPC077E Unable to allocate RPL\n\u2022CAPC077E Unable to modify RPL\n\u2022CAPC077E Unable to allocate repository\n\u2022CAPC077E ENQUEUE failed\n\u2022CAPC077E Unable to open repository\n\u2022CAPC077E Unable to read repository record\n\u2022CAPC077E Unable to read repository record for update\n\u2022CAPC077E Unable to write repository\n\u2022CAPC077E Unable to close repository\n\u2022CAPC077E DEQUEUE failed\n\u2022CAPC077E repository is full\n\u2022CAPC077E Logic error, READ prior to OPEN\n\u2022CAPC077E Invalid index id requested\nVerify the following:\n\u2022The repository was correctly generated at installation time (see Allocate CAIPRINT Repository Library).\n\u2022The PRTLIB option in the default CSECT, CAOETABL, specifies the correct library.\n\u2022The repository is not full. If it is full, use the utility program, CAOUPRTU, to delete or archive selected reports.\nIf the error persists, save all output listings and contact Technical Support.\nCAPC078W\nFILE NOT ADDED TO THE CAIPRINT REPOSITORY.\nReason:\nConditions prevented a CAIPRINT report from being written to the repository.\nAction:\nReview the supplementary CAPC078W message that follows for more information about what prevented the\nCAIPRINT report from being written to the repository. If needed, take appropriate steps to resolve the problem. A list of\nsupplementary CAPC078W messages follows:\n\u2022CAPC078W Report not found in repository\n\u2022CAPC078W Report date mismatch\n\u2022CAPC078W Report time mismatch\n\u2022CAPC078W Lock error", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "fbd8d9330002-1", "text": "\u2022CAPC078W Report time mismatch\n\u2022CAPC078W Lock error\n\u2022CAPC078W Duplication limit exceeded\n\u2022CAPC078W Repository is empty\nIf you want to have CAIPRINT reports written to the central VSAM repository, verify the following:\n\u2022The repository was correctly generated at installation time (see Allocate CAIPRINT Repository Library).\n\u2022The PRTLIB option in the default CSECT, CAOETABL, specifies the correct library.\n\u2022The DUPLIM option in the default CSECT, CAOUDFRX is not set too low.\n\u2022If you do not want to have CAIPRINT reports written to the central VSAM repository, set the PRTREPT option in the\ndefault CSECT, CAOETABL, to PRTDD.\nIf the problem persists, save all output listings and contact Technical Support.\n 1717", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "583d962287e1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPC081E\nINVALID PROGRAM RETURN SEQUENCE. SEE USER GUIDE FOR CALL/ENTRY/RETURN REQUIREMENTS.\nReason:\nThe Execution Monitor is in the process of monitoring the exit of a given program. During save area chain validity\nchecking, it is determined that a serious violation of save area linkage has occurred that makes further execution\nimpossible. The Execution Monitor abends the task with a U1081 abend and a dump.\nAction:\nReview the source code of the named module for proper adherence to standard linkage conventions. If all appears\nreasonable, save all the documentation and contact Broadcom Support  for assistance.\nCAPC082E\nOUT OF SPACE FOR INTERNAL CONTROL BLOCKS. INCREASE REGION SIZE.\nReason:\nA conditional GETMAIN failed in an attempt to obtain more storage from subpool 0 (user storage). Execution is terminated\nimmediately with a U1082 abend.\nAction:\nIncrease the region size available to the job step and resubmit the job.\nCAPC084E\nINVALID ERROR CODE PASSED TO CAOCER00.\nReason:\nInternal programming error. A module has called the error print module, CAOCER00, with an invalid error code in Register\n0. Execution is terminated immediately with a U1084 abend.\nAction:\nThis is a product error. Contact Broadcom Support  for assistance.\nCAPC088E\nUNABLE TO LOAD MODULE CAODMAIN\nReason:\nThe Execution Monitor was unable to load Abend Reporter module, CAODMAIN. Execution terminates.\nAction:\nVerify that the library containing module CAODMAIN is available at execution-time in LINKLIST or LPA, or was specified in\nthe JCL in STEPLIB or JOBLIB.\nCAPC089E\nINVALID CALL TO CPXCEM INTERNAL ENTRY POINT\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "583d962287e1-1", "text": "CAPC089E\nINVALID CALL TO CPXCEM INTERNAL ENTRY POINT\nReason:\nAn error has occurred upon entry to the Execution Monitor. The task abends with a U-1089 abend.\nAction:\nSave all the output and contact Technical Support for assistance.\nCAPC091E\nINTERNAL ERROR. MTAP/XTAP CANNOT BE TRACED ACROSS THE RUN UNIT.\nReason:\nExecution is terminated with a U1091 abend and a dump. Either Abend Reporter or MAPPER called the Execution\nMonitor to locate the first MTAP or XTAP associated with the run unit prior to the current one supplied as input.\n 1718", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7a2e5401dc1b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nSave all related documentation, including the dump, and contact Technical Support for assistance.\nCAPC094E\nPRINT FILE HAS BEEN OMITTED AND CANNOT BE ALLOCATED. RUN TERMINATED.\nReason:\nThis message is issued after message CAPC018E is issued to the console and user log. The CAIPRINT file is required for\nexecution, and the allocation failure causes immediate termination of the run with a U1094 abend code and dump.\nAction:\nCAPC018E should provide clues to the failure of dynamic allocation, or you can supply a DD statement of your own to\nidentify the problem. Correct the error accordingly and resubmit the job.\nCAPC097E\nINTERNAL ERROR. DIAGNOSTIC PGM IN CONTROL.\nReason:\nThe error recovery mechanisms (for example, ESTAE exits) of the Batch runtime system have encountered an\nunexpected and unrecoverable abend. The most likely event is an unexpected 0Cx abend in the runtime system.\nThis could be traceable to an invalid control block, product logic error, or user error. The runtime system captures a few\ndata elements related to the abend and attempts to relate the abending PSW address to an offset within a named module.\nThe abend code (e.g., 0C4) and the registers at abend, along with other pertinent information are written to CAIPRINT.\nThe execution monitor then issues a user ABEND code of 1097 and an ABEND dump is produced.\nThe difference in abend code reflects what process was in control at the time of the abend.\nThis message is issued (abend code 1097) when a user diagnostic program was in control and did not return to its caller.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7a2e5401dc1b-1", "text": "Configuring documents how a customer can create a reporting module for specific abend codes that are given control\nby Abend Reporter to report on the error. For example, assume that the runtime system has initially trapped a system\n0C1. Normally, Abend Reporter calls the distributed module CAOD00C1 to produce the abend box (description, probable\ncauses, etc.). If a 1097 abend appears, you should look for the presence of an entry for 0C1 in the user abend table\nmodule CAOCAB80. This customization process is also discussed in Configuring.\nAction:\nContact Broadcom Support to report the problem after the dump is available. In the RTM2WA summary, abends are\nrepresented by a chain of SDWA control blocks displayed in chronological order from the oldest to the newest. Generally,\ndiagnose the problem by finding the SWDA in the RTM2WA SUMMARY chain that matches the abend code and registers\ndisplayed on CAIPRINT. The unexpected and unrecoverable abend is documented as the SDWA that is queued just prior\nto the final user abend code 1097.\nCAPC098E\nINTERNAL ERROR. ABEND REPORTER IN CONTROL.\nReason:\nThe error recovery mechanisms (for example, ESTAE exits) of the runtime system have encountered an unexpected and\nunrecoverable abend. The most likely event is an unexpected 0Cx abend in the runtime system.\nThis could be traceable to an invalid control block, product logic error, or user error. The runtime system captures a few\ndata elements related to the abend and attempts to relate the abending PSW address to an offset within a named module.\nThe abend code (for example, 0C4) and the registers at abend, along with other pertinent information, are written to", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7a2e5401dc1b-2", "text": "CAIPRINT. The execution monitor then issues a user abend code of 1098 and an abend dump is produced.\nAs the message text implies, the difference in abend code reflects what process was in control at the time of the abend.\nThis message is issued when SymDump  (CAOD xxxx) was in control and did not return to its caller.\nAction:\nContact Broadcom Support  to report the problem after the dump is available. In the RTM2WA summary, abends are\nrepresented by a chain of SDWA control blocks displayed in chronological order from the oldest to the newest. Generally,\n 1719", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1c846dc62d38-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\ndiagnose the problem by finding the SDWA in the RTM2WA SUMMARY chain that matches the abend code and registers\ndisplayed on CAIPRINT. The unexpected and unrecoverable abend is documented as the SDWA that is queued just prior\nto the final user abend code 1098.\nCAPC099E\nINTERNAL ERROR. EXECUTION MONITOR OR MAPPER IN CONTROL.\nReason:\nAn unrecoverable abend has occurred in the runtime system. The most likely event is an unexpected 0Cx abend.\nAction:\nContact Broadcom Support  to report the problem after the dump is available.\nCAPD107E\nINSUFFICIENT MAIN STORAGE AVAILABLE.\nReason:\nSymDump  ran out of memory.\nAction:\nIf possible, increase the region size. If this does not resolve the problem, save all output materials and contact Broadcom\nSupport .\nCAPD109W\nSNAPSHOT CALL TURNED OFF.\nReason:\nThe region size is not large enough for operation of the SNAP feature. The feature is turned off and program processing\ncontinues.\nAction:\nIncrease region size. For details, see CICS Interfaces and Compatibility.\nCAPD110W\nSYMBOLIC FILE INITIALIZATION FAILED.\nReason:\nAn error was detected while trying to access a PROTSYM or CSL file. SymDump  reporting continues, but symbolic\nsupport will not be provided for this execution.\nAction:\nVerify that your PROTSYM and CSL data set names have been specified correctly and that the files are correctly defined.\nRerun the job if necessary. If you cannot determine the cause of this message, contact Broadcom Support .\nCAPD112W\nNO SYMBOLIC INFORMATION FOUND FOR PROGRAM \"xxxxxxxx\".\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1c846dc62d38-1", "text": "CAPD112W\nNO SYMBOLIC INFORMATION FOUND FOR PROGRAM \"xxxxxxxx\".\nReason:\nAbend Reporter is attempting to retrieve symbolic information for a program, but no information was found in any of the\nPROTSYM or CSL files available to Abend Reporter.\nAbend Reporter processing continues, but symbolic support is not provided for the program.\nAction:\nFirst, verify that the symbolic information has been written to a PROTSYM file or a CSL file. Then verify that the symbolic\nfile is available to Abend Reporter using your installation defaults, your JCL, or a SYMDSN override.\nIf you still cannot determine the cause of this message, contact Technical Support.\n 1720", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "231230c1ce4d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPD113W\nSYMBOLIC MEMBER DATE/TIME DOES NOT MATCH CURRENT PROGRAM.\nReason:\nSymbolic information was found for at least one version of your program in one of the available symbolic files, but the time\nstamp in the program does not exactly match the symbolic information.\nAction:\nFirst, verify that the symbolic information for the current version of your program has been written to a PROTSYM file or\na CSL file. If the program has been recompiled and relinked, the symbolic file must be reloaded. This problem can also\noccur if your program has been recompiled and the symbolic file updated, but the program has not yet been relinked. If\nyou have correctly loaded the latest symbolic information into a symbolic file, verify that the symbolic file is available to\nAbend Reporter using your installation defaults, your JCL, or a SYMDSN override.\nIf you still cannot determine the cause of this message, contact Technical Support.\nCAPD114W\nSYMBOLIC FILE READ ERROR-SYMBOLIC INFORMATION MAY BE INCOMPLETE.\nReason:\nAn error was detected while attempting to read symbolic information from one of the available symbolic files. SymDump\nprocessing continues, but symbolic information may be incomplete.\nAction:\nVerify that all of your available symbolic files are valid, and that their data set names are specified correctly in your\ninstallation defaults, JCL, or CAISYM override statements. Correct the error and rerun the job if necessary. If you still\ncannot determine the cause of this message, contact Broadcom Support .\nCAPD115W\nINTERRUPT OCCURRED IN REGION OR SYSTEM. NO CSECT DUMP WAS PRODUCED.\nReason:\nAn interrupt occurred outside of a user program or outside the user region. Processing continues.\nAction:\nNone.\nCAPD116W", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "231230c1ce4d-1", "text": "Action:\nNone.\nCAPD116W\nCSECT LENGTH UNKNOWN, PROCEEDING TO DUMP ENTIRE LOAD MODULE.\nReason:\nAbend Reporter was unable to determine the length of a control section, so the entire load module has been dumped\ninstead using a standard \"dump\" format.\nAction:\nNone.\nCAPD117W\nUNABLE TO LOCATE LOAD MODULE; LOAD MODULE DUMP SUPPRESSED.\nReason:\nAbend Reporter was unable to relate an interrupt address with a load module name during a scan of system control\nblocks (CDE chain queued off the TCB). Processing continues.\nAction:\nNone.\n 1721", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bae3e4985a35-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPD118W\nPROCESSING TERMINATED DUE TO INSTALLATION REQUEST.\nReason:\nAn entry in the user table CAOCAB80 specified that DETECT equals OFF. A report will not be produced.\nAction:\nNone.\nCAPD123I\nINSTRUCTION LOCATED PRIOR TO THE FIRST PROCEDURE STATEMENT. POSSIBLE ERROR COMPUTING THE\nSIZE OF A VARIABLE-LENGTH TABLE.\nReason:\nThe instruction which corresponds to the indicated program offset is located prior to the first Procedure Division statement\nin the program and does not correspond to a COBOL source statement. One possible reason for this is that an error\noccurred while computing the size of a variable-length table.\nAction:\nVerify that the DEPENDING ON variables for any variable-length tables are initialized before the tables are referenced.\nAlternatively, if a CAPD113W message was displayed, indicating that the symbolic file member does not exactly match the\nprogram in the executable load module, follow the action specified for that message.\nCAPD137I\nCSECT DUMP SUPPRESSED DUE TO EXCLUSION CRITERIA.\nReason:\nThe abending CSECT was not displayed in the Abend Reporter because it was specifically excluded using the\nCAOUXMOD option of default options member, CAOUDFRX.\nAction:\nNone.\nCAPD138I\nINTERRUPT OCCURRED IN REGION OR SYSTEM. DUMPING CSECT FOR CALLING PROGRAM.\nReason:\nAn interrupt occurred outside of a user program or outside of the user region. The CSECT dump will be generated for the\npreviously active user program (as indicated in the save area chain).\nAction:\nNone.\nCAPD140E\nINTERNAL ERROR DURING DB2 PROCESSING. DB2 PROCESSING HALTED.\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bae3e4985a35-1", "text": "INTERNAL ERROR DURING DB2 PROCESSING. DB2 PROCESSING HALTED.\nReason:\nAn error occurred in the reporter which accesses the DB2 catalog. Processing is halted for the DB2 section of the report.\nAction:\nRerun the job with the options DUMP ON and DB2TRACE ON specified in the CAIOPTS DD. Collect all output including\nJCL, log messages and dump. Contact Broadcom Support .\nCAPD141E\nERROR PROCESSING SQLCODE. RETURN CODE FROM DSNTIAR=rc.\nReason:\n 1722", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9135b4543201-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAn error occurred while trying to print the message associated with SQLCODE. The return code from DB2 module\nDSNTIAR is indicated in the message.\nAction:\nRerun the job with the options DUMP ON and DB2TRACE ON specified in the CAIOPTS DD. Collect all output including\nJCL, log messages, and dump. Contact Broadcom Support .\nCAPD142W\nTHE PARAMETER LIST FOR THE LAST SQL CALL WAS NOT FOUND.\nReason:\nThe parameter list for the last SQL call was not found in the DB2 control block.\nAction:\nIf an SQL statement has been executed in the application, collect all output (including JCL, log messages, and dump) and\ncontact Technical Support. Otherwise, no action is necessary.\nCAPD143W\nPROGRAM pppppppp HAS BEEN RECOMPILED SINCE IT WAS LAST BOUND.\nReason:\nThe indicated program has been recompiled since the last time that the package or plan containing the program was\nbound.\nAction:\nIf you are using a product such as Bind Analyzer , which allows programs to be changed without rebinding, no action is\nnecessary. Otherwise, rebind the package or plan for the program.\nCAPD144W\nUNABLE TO FIND A UNIQUE SQL STATEMENT IN SECTION sssss FOR THE INDICATED STATEMENT TYPE.\nReason:\nThe SQL statement number could not be used to find the last SQL statement (because the program was recompiled since\nthe last time it was bound or the statement number was greater than 32767, and was therefore saved in the catalog table\nas 0). When Detector tried to use the section number and statement type to find the last SQL statement, it found multiple\nstatements of that type in the section.\nAction:\nNone.\nCAPD145W", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9135b4543201-1", "text": "statements of that type in the section.\nAction:\nNone.\nCAPD145W\nSQL STATEMENT sssss WAS NOT FOUND IN THE DB2 CATALOG.\nReason:\nThe indicated SQL statement could not be found in DB2 catalog table SYSSTMT or SYSPACKSTMT.\nAction:\nContact Broadcom Support .\nCAPD146W\nPLAN pppppppp WAS NOT FOUND IN THE DB2 CATALOG.\nReason:\nThe indicated plan could not be found in the DB2 catalog table SYSPLAN.\nAction:\nCollect all output including JCL, log messages, and dump. Contact Broadcom Support .\n 1723", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bb4f2e22f316-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPD147I\nNO OBJECT DEPENDENCIES WERE FOUND FOR PLAN pppppppp.\nReason:\nNo entries were found in the DB2 catalog table SYSPLANDEP for the indicated plan.\nAction:\nNone.\nCAPD148I\nNO PACKAGE LIST WAS FOUND FOR PLAN pppppppp.\nReason:\nNo entries were found in the DB2 catalog table SYSPACKLIST for the indicated plan.\nAction:\nNone.\nCAPD149I\nNO ACTIVE PACKAGES WERE FOUND FOR PLAN pppppppp.\nReason:\nNone of the entries found in the DB2 catalog table SYSPACKLIST for the indicated plan corresponded to programs that\nwere active at the time of the report.\nAction:\nNone.\nCAPD150I\nNO OBJECT DEPENDENCIES WERE FOUND FOR PACKAGE pppppppp.\nReason:\nNo entries were found in the DB2 catalog table SYSPACKDEP for the indicated package.\nAction:\nNone.\nCAPD151I\nNO DBRMS WERE FOUND FOR PLAN pppppppp.\nReason:\nNo entries were found in the DB2 catalog table SYSDBRM for the indicated plan.\nAction:\nNone.\nCAPD152I\nNO ACTIVE DBRMS WERE FOUND FOR PLAN pppppppp.\nReason:\nNone of the entries found in the DB2 catalog table SYSDBRM for the indicated plan corresponded to programs that were\nactive at the time of the report.\nAction:\nNone.\n 1724", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d92a648f00e4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPD153E\nCHARACTER CONVERSION FAILED: RC = nn, REASON = mm.\nReason:\nAn error occurred when converting a string from UTF-8 to EBCDIC.\nAction:\nCollect all output including JCL, log messages, and dump. Contact Broadcom Support .\nCAPD154W\nCAODSTKN \u2013 LOAD OF CAOUDIXR FAILED.\nReason:\nDynamic symbolic support encountered an error loading module CAOUDIXR.\nDynamic symbolic support is not able to populate mismatched symbolic for the abending CSECTs.\nAction:\nEnsure that the SymDump  Batch product load module libraries are correctly defined in your JCL or are defined in your\ninstallation's LNKLST.\nCAPD157W\nCAOFMAIN \u2013 LOAD OF CAODNDVR FAILED.\nReason:\nDynamic symbolic support encountered an error loading module CAODNDVR.\nDynamic symbolic support will not be able to populate mismatched symbolic for the abending CSECTs.\nAction:\nEnsure that the SymDump  Batch product load module libraries are correctly defined in your JCL or are defined in your\ninstallation's LNKLST.\nCAPD158W\nCAOFMAIN \u2013 LOAD OF CAOUDIXR FAILED.\nReason:\nDynamic symbolic support encountered an error loading module CAOUDIXR.\nDynamic symbolic support will not be able to populate mismatched symbolic for the abending CSECTs.\nAction:\nEnsure that the SymDump  Batch product load module libraries are correctly defined in your JCL or are defined in your\ninstallation's LNKLST.\nCAPE001E\nmmmmmmmm NOT FOUND - INITIALIZATION INCOMPLETE.\nReason:\nAn Abend Handler module was not available during initialization of Abend Handler.\nAction:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d92a648f00e4-1", "text": "An Abend Handler module was not available during initialization of Abend Handler.\nAction:\nEnsure that all Abend Handler modules from CAI.CAVHLOAD are available when initializing Abend Handler.\nCAPE002E\nINTERCEPT FAILED - INITIALIZATION INCOMPLETE.\nReason:\nThe SymDump  SVC hook could not be inserted.\nAction:\n 1725", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f15a448573dc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReview all installation procedures. Rerun the job once more. If this message appears again, notify Broadcom Support .\nCAPE003I\nUNABLE TO OBTAIN LOCK. REFRESH WILL CONTINUE WITHOUT LOCK.\nReason:\nAnother job was using SymDump  when an attempt was made to reinitialize. SymDump  is reinitialized.\nAction:\nNone.\nCAPE003W\nUNABLE TO OBTAIN LOCK. CONTINUE INITIALIZATION WITHOUT LOCK?\nReason:\nAnother job was using SymDump  when an attempt was made to reinitialize.\nAction:\nIf you reply Y or YES, SymDump  reinitializes. If you reply N or NO, initialization is terminated.\nCAPE004I\nSQA TABLE RESIDES IN CORE AT ADDRESS nnnnnnnn.\nReason:\nThis message is for diagnostic purposes only.\nAction:\nNone.\nCAPE005I\nINITIALIZATION COMPLETED.\nReason:\nYou have successfully initialized or refreshed the SymDump  system.\nAction:\nNone.\nCAPE006E\nINTERNAL ABEND ENCOUNTERED.\nReason:\nThis message is issued whenever SymDump  has detected an internal error.\nAction:\nCollect all output including JCL, log messages, and dump. Contact Broadcom Support .\nCAPE007E\nINTERRUPT AT PSW xxxxxxxx EP=xxxxxxxxR0-R3 xxxxxxxx xxxxxxxx  xxxxxxxx  xxxxxxxxR4-R7 xxxxxxxx\nxxxxxxxx  xxxxxxxx  xxxxxxxxR8-RB xxxxxxxx  xxxxxxxx  xxxxxxxx  xxxxxxxxRC-RF xxxxxxxx  xxxxxxxx  xxxxxxxx\nxxxxxxxx\nReason:\nThe SymDump  ESTAE has intercepted an internal error. This message indicates the PSW and registers from the time of\nthe error.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f15a448573dc-1", "text": "the error.\nAction:\nCollect all output including JCL, log messages, and dump. Contact Broadcom Support .\n 1726", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9ad95f2a832b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPE008E\nREPORT TERMINATED BECAUSE XXXXXXXXXXXXXXX.\nReason:\nA condition has occurred which has prevented the completion of the SymDump .\nAction:\nCollect all output including JCL, log messages, and dump. Contact Broadcom Support .\nCAPE009E\nREPORT WAS NOT PRODUCED BECAUSE NO PRB WAS FOUND.\nReason:\nAbend Handler could not find a Program Request Block (PRB) on the RB chain.\nAction:\nNone.\nCAPE010E\nUNABLE TO LOCATE RUNTIME MODULES. INITIALIZATION INCOMPLETE.\nReason:\nA module required for initialization was not found.\nAction:\nEnsure that all SymDump  Batch modules are available when initializing SymDump .\nCAPE011E\nEXCEPTION ENCOUNTERED IN CAOETSEL.\nReason:\nThis message is issued whenever SymDump  has detected an internal error in module CAOETSEL while attempting to\nevaluate possible exclusion criteria.\nAction:\nCollect all output including JCL, log messages, and dump. Contact Broadcom Support .\nCAPE013I\nUNABLE TO OBTAIN LOCK. ABEND HANDLER WILL BE DISABLED WITHOUT LOCK.\nReason:\nAnother job was using SymDump  when an attempt was made to disable it. SymDump  will be disabled.\nAction:\nNone.\nCAPE013W\nUNABLE TO OBTAIN LOCK. CONTINUE TO DISABLE ABEND HANDLER WITHOUT LOCK?\nReason:\nAnother job was using SymDump  when an attempt was made to disable it.\nAction:\nIf you reply Y or YES, SymDump  will be disabled. If you reply N or NO, it will not.\nCAPE014I\nABEND HANDLER IS NOT ACTIVE - NO ACTION WILL BE TAKEN.\n 1727", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "13a9fa7705aa-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nAn attempt was made to disable SymDump  support when it was already disabled. SymDump  remains disabled.\nAction:\nNone.\nCAPE015I\nABEND HANDLER IS NOW DISABLED.\nReason:\nSymDump  has been successfully disabled.\nAction:\nNone.\nCAPE016W\nOPTIONS NOT UPDATED BECAUSE MODULE CAOETABL IS NOT AVAILABLE.\nReason:\nAn attempt to update CAOETABL was made, but CAOETABL was not available.\nAction:\nThe SymDump  options table is not updated. Ensure that CAOETABL is available through STEPLIB, JOBLIB, LINKLIST or\nLPA and is APF authorized.\nCAPE017I\nABEND HANDLER IS NOT CURRENTLY ACTIVE - NO ACTION WILL BE TAKEN.\nReason:\nAn attempt was made to update the SymDump  options, but SymDump  was not initialized on the system.\nAction:\nThe options are not updated. Your options table will be loaded when you initialize SymDump .\nCAPE018I\nOPTIONS SUCCESSFULLY UPDATED.\nReason:\nA successful update of CAOETABL has been completed.\nAction:\nNone.\nCAPE019I\nUNABLE TO OBTAIN LOCK. OPTIONS WILL BE UPDATED WITHOUT LOCK.\nReason:\nAnother job was using SymDump  when an attempt was made to update the options table. The SymDump  options will be\nupdated\nAction:\nNone.\nCAPE019W\nUNABLE TO OBTAIN LOCK, SHOULD TABLE UPDATE CONTINUE WITHOUT LOCK?\nReason:\nAnother job was using Abend Handler when an attempt was made to update the options table.\n 1728", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8b6679f70988-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nIf you reply Y or YES, Abend Handler will be updated. If you reply N or NO, it will not.\nCAPE021E\nREPORT WAS NOT PRODUCED BECAUSE A NECESSARY MODULE WAS MISSING.\nReason:\nAbend Handler was unable to load CAOCEM00.\nAction:\nEnsure that the SymDump  Batch RTL is available through STEPLIB, JOBLIB, LINKLIST or LPA.\nCAPE022I\njjjjjjjj  ssssssss ABENDED taaa IN PROGRAM pppppppp AT OFFSET +oooooo.\nReason:\nSymDump  has completed a report, but no symbolic information was available for the abending program.\nAction:\nUse your report to correct the application.\nCAPE023I\njjjjjjjj  pppppppp ABENDED taaa AT ssssssssssssssssssssssssss.\nReason:\nSymDump  has completed a report, and symbolic information was available for the abending program.\nAction:\nUse your report to correct the application.\nCAPE024E\nxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\nReason:\nAn invalid reply was entered by the operator.\nAction:\nReply Y or N.\nCAPE025I\njjjjjjjj  ssssssss UNHANDLED CONDITION CEEnnnnx RAISED IN PROGRAM pppppppp AT OFFSET +oooooo.\nReason:\nSymDump  has completed an unhandled LE condition, but no symbolic information was available for the offending\nprogram.\nAction:\nUse your report to correct the application.\nCAPE026I", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8b6679f70988-1", "text": "program.\nAction:\nUse your report to correct the application.\nCAPE026I\njjjjjjjj  pppppppp UNHANDLED COND CEEnnnnx AT ssssssssssssssssssssssssssssssssssssssssssssssss\nReason:\nSymDump  has completed an unhandled LE condition, and symbolic information was available for the offending program.\nAction:\nUse your report to correct the application.\n 1729", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f4e968972bcf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPE027I\nABEND REPORT SUPPRESSED DUE TO STOPDD ddname\nReason:\nThe indicated DD name was specified in the JCL for the abending job step. The abend report is suppressed.\nAction:\nNone\nABEND REPORT SUPPRESSED DUE TO KEY LESS THAN 8\nReason: SymDump  Batch reports on abends that occur in key 8. If the abend occurs in any other key, SymDump  Batch\nwill not report on the abend.  \nAction: None\nABEND REPORT SUPPRESSED DUE TO RMODE 64 PSW\nReason: The abending program resides above the bar. The abend report is suppressed. \nAction: None\nCAPE028I\nABEND REPORT NOT GENERATED DUE TO EXCLUSION CRITERION: keyword value\nReason:\nThe abending job step matched an exclusion criterion specified either in the CAOETXCL macro of default member\nCAOETABL, or in user exit CAOEUSR1. The message indicates the matching criterion.\nAction:\nNone\nCAPE029I\nABEND REPORT GENERATED REGARDLESS OF EXCLUSION CRITERIA DUE TO EXIT CAUEUSR1\nReason:\nThe abending job step matched inclusion criteria specified in user exit CAOEUSR1. The abend report is generated\nregardless of whether it matched exclusion criteria specified in the CAOETXCL macro of default member CAOETABL.\nAction:\nNone\nCAPE030W\nALLOCATE FOR dddddddd FAILED. NETMAN INTERFACE NOT AVAILABLE. LOAD for mmmmmmmm FAILED.\nNETMAN INTERFACE NOT AVAILABLE.\nReason:\nThe specified module could not be loaded or the specified DDNAME could not be dynamically allocated.\nAction:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f4e968972bcf-1", "text": "Action:\nEnsure that the instructions for using the Netman  interface in Configuring have been followed and that all installation\ndefaults have been set up correctly. If so, contact Broadcom Support.\nCAPE031I\nRECORD HAS BEEN ADDED TO NETMAN FILE.\nReason:\nA record was added by Abend Handler to the Netman  database using the Machine Generated Problem Tracking system.\n 1730", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "19c78630eebf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nThe record is now available for review by an authorized Netman  user.\nCAPE032W\nNETMAN INTERFACE FAILED DURING UPDATE.\nReason:\nAn error has occurred while attempting to log a record to Netman  for Machine Generated Problem Tracking.\nAction:\nEnsure that the instructions for using the Netman  interface in Configuring have been followed and that all installation\ndefaults have been set up correctly. If so, contact Broadcom Support.\nCAPE033W\nCAOECEEI\u2013LOAD OF CAOEGMSG FAILED.\nReason:\nLanguage Environment Unhandled Condition support encountered an error loading module CAOEGMSG. LE Unhandled\nCondition messages will not be retrieved.\nAction:\nEnsure that the SymDump  Batch product load module libraries are correctly defined in your JCL or are defined in your\ninstallation's LNKLST.\nCAPE034W\nCAOECEEI \u2013 CAOEGMSG FAILED. RC = nnnn .\nReason:\nRetrieval of LE messages function failed, where nnnn  is the severity code returned by CEEMGET, LE Callable Service.\nAction:\nContact Broadcom Support  for assistance.\nCAPH600W\nmember NOT CONVERTED, ALREADY EXISTS ON OUTPUT.\nReason:\nCAOHCNVT has determined that the CLIST being converted already exists in the output library. CAOHCNVT bypasses\nconverting this member and attempts to convert the next member. The program ends with a Return Code of 4.\nAction:\nTo convert this member, you either have to rename it in the source library (SYSUT1) data set, or rerun CAOHCNVT\nspecifying PARM=REPLACE.\nCAPH601E\nmember NOT CONVERTED, OUTPUT DIRECTORY FULL.\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "19c78630eebf-1", "text": "CAPH601E\nmember NOT CONVERTED, OUTPUT DIRECTORY FULL.\nReason:\nDuring an attempt to update the directory of the output CLIST library, the directory became filled.\nAction:\nCAOHCNVT terminates processing and ends with a return code of 8. Either reallocate the output library (SYSUT2) with\nadditional directory space, or scratch unused members.\nCAPH602E\nCONVERSION ABORTED, PERMANENT I/O ERROR HAS OCCURRED.\n 1731", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "74aeecedc956-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nDuring an attempt to update or read the directory of the output CLIST library, a permanent I/O error occurred. CAOHCNVT\naborts with a U1602 abend.\nAction:\nCheck the allocation of the output library and reallocate it on a different disk if necessary. Rerun the job.\nCAPH603E\nCONVERSION ABORTED, OUTPUT LIBRARY UNOPENED.\nReason:\nDuring an attempt to update the directory of the output CLIST library, the STOW SVC ended with a return code indicating\nthe CLIST library did not open.\nCAOHCNVT aborts with a U1603 abend. This should not occur since, if the output library does not open, an S0C1 should\noccur on the first WRITE. This indicates that there may be a probable IOS error.\nAction:\nContact Broadcom Support .\nCAPH604E\nmember NOT CONVERTED, INSUFFICIENT VIRTUAL STORAGE.\nReason:\nDuring an attempt to process the directory of the output CLIST library (SYSUT2), the BLDL or STOW routine ended\nabnormally due to insufficient virtual storage availability. CAOHCNVT ends with a return code of 8.\nAction:\nIncrease the REGION size on the EXEC or JOB card and resubmit the job.\nCAPH605I\nmember HAS BEEN SUCCESSFULLY CONVERTED.\nReason:\nCAOHCNVT has successfully converted the named input CLIST library member to variable format and stored it under the\nsame name into the output CLIST library. CAOHCNVT attempts to process the next member (if any).\nAction:\nNone.\nCAPH606E\nsynadaf error message text.\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "74aeecedc956-1", "text": "None.\nCAPH606E\nsynadaf error message text.\nReason:\nAn I/O error has occurred while accessing either the input or output CLIST libraries causing the CAOHCNVT SYNAD\nroutine to get control. CAOHCNVT invokes the SYNADAF facility to format an error message, after which it aborts with a\nU1606 abend.\nAction:\nCheck the DCB attributes of the two libraries, correct the error, and resubmit the job.\nCAPI000E\nInternal error during initialization.\nReason:\nAn internal error was detected while attempting to initialize the repository viewer API. This typically indicates that an ISPF\nenvironment could not be established.\nAction:\n 1732", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bfd96f819ef1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nVerify that a valid ISPF environment exists.\nIf you cannot determine the cause of this error, save any output or screen shots and contact Technical Support.\nCAPI002E\n<char> is not a valid line command.\nReason:\nA line command was entered that is not supported by the current selection list.\nAction:\nReturn to the selection list from which this message was displayed, then press HELP to display the help text for the\ndisplay.\nThe valid line commands for the selection list will be listed in the help text. Enter a valid line command.\nIf you believe that the line command that you entered was valid, contact Technical Support.\nCAPI004E\n<keyword> is not a valid command for this screen.\nReason:\nA command was entered on the command line that is not supported by the current display.\nAction:\nReturn to the screen from which this message was displayed, then press HELP to display the help text for the screen.\nThe valid commands for the screen will be listed in the help text. Enter a valid command.\nIf you believe that the command that you entered was valid, contact Technical Support.\nCAPI005E\n<keyword> is only valid while a report is loaded.\nReason:\nA command was entered on the command line that is not supported unless a report has been selected for viewing.\nAction:\nOnly the TAG (.label), LOCATE, and NOTES commands require an open report to be valid. Enter HELP  command-name\nfor more information about any of these commands.\nIf you received this message after entering any other command, contact Technical Support.\nCAPI006E\n<keyword> is not a valid command.\nReason:\nAn unrecognized command was entered on the command line.\nAction:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bfd96f819ef1-1", "text": "Reason:\nAn unrecognized command was entered on the command line.\nAction:\nReturn to the screen from which this message was displayed, then press HELP to display the help text for the screen.\nThe valid commands for the screen will be listed in the help text. Enter a valid command.\nIf you believe that the command that you entered was valid, contact Technical Support.\nCAPI007E\nCommand argument exceeds maximum length of 32 characters\nReason:\nAn argument specified for the command exceeds 32 characters.\nAction:\nRepeat the command with the correct arguments.\nIf you are not sure about the required arguments for the command, enter HELP  command-name  for more information.\n 1733", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7eff8a55e135-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPI010E\nInternal error.\nReason:\nAn internal error was detected while the repository viewer was attempting to locate a column header in the current display.\nAction:\nContact Broadcom Support .\nCAPI011W\nNo column specified.\nReason:\nA command was entered that requires a column header as an argument, but no column header was provided.\nAction:\nRepeat the command with the correct arguments.\nIf you are not sure about the required arguments for the command, enter HELP  command-name  for more information.\nCAPI012W\nColumn does not exist.\nReason:\nA command was entered that requires a column header as an argument, but the argument provided does not match any\ncolumn header for the current display.\nAction:\nRepeat the command with the correct column header argument.\nIf you are not sure about the required arguments for the command, enter HELP  command-name  for more information.\nCAPI015E\nInternal error.\nReason:\nAn internal error was detected while the repository viewer was attempting to interpret a d line command.\nAction:\nContact Broadcom Support .\nCAPI016I\nDelete cancelled.\nReason:\nA delete confirmation pop-up message was displayed in response to a d line command entered on the repository index\nselection list, and you responded by pressing END to cancel the request.\nAction:\nThis is an informational message, no action is required.\nIf you intended to delete the report from your repository, repeat the d line command and confirm the deletion by pressing\nEnter as described in the text of the pop-up message.\nFor more information about confirming a deletion request, enter HELP DELETE  or press HELP while the pop-up message\nis displayed.\nCAPI017E\nError deleting report.\nReason:\n 1734", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "93f0258e6c6d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nYou attempted to delete a report from your repository, but an error was detected and the report could not be deleted.\nAction:\nThe report may have been deleted by another user after you had entered the viewer.\nReturn to the repository index selection list, then enter REFRESH  and press Enter to rebuild the list.\nIf the report still appears in the list, contact Technical Support.\nCAPI018I\nDelete cancelled.\nReason:\nA report was successfully deleted from your repository in response to a d line command from the repository index\nselection list.\nAction:\nThis is an informational message, no action is required.\nCAPI021W\nNo search argument specified.\nReason:\nA FIND command was entered on the command line, but no search argument was provided.\nAction:\nRepeat the command with the correct arguments.\nIf you are not sure about the required arguments for this command, enter HELP FIND  for more information.\nCAPI022E\nInternal error.\nReason:\nAn internal error was detected while the repository viewer was attempting to execute a FIND request.\nAction:\nContact Broadcom Support .\nCAPI023W\nNot found.\nReason:\nA FIND command was entered on the command line, but the search argument was not found.\nAction:\nIf the search was executed in the forward direction, enter RFIND  to resume the search starting from the top of the display.\nIf the search was executed in the backward direction, enter RFIND  to resume the search starting from the bottom of the\ndisplay.\nIf you are not sure about the required arguments for this command, enter HELP FIND  for more information.\nCAPI026W\nSort invalid for this display.\nReason:\nA SORT command was entered on the command line, but the current display does not support sorting.\nAction:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "93f0258e6c6d-1", "text": "Action:\nSorting is only allowed on the repository index selection list or a symbolic file member selection list.\nIf you have entered a SORT command from one of these displays and this message appeared, contact Technical Support.\n 1735", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d4d7040ba389-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPI027I\nSort completed.\nReason:\nThis message is displayed in response to a successful SORT command. The current display has been sorted on the\ncontents of the specified column and in the order requested.\nAction:\nThis is an informational message, no action is required.\nEnter *SORT ** to restore the current display to its original order.\nCAPI030I\nSetIndex cancelled.\nReason:\nYou entered a SETINDEX command to change the name of your repository, but when prompted for a new data set name,\nyou pressed END to cancel the request.\nAction:\nThis is an informational message, no action is required.\nIf you intended to change the repository data set name, repeat the SETINDEX command, enter a new name in the field\nprovided, and press Enter to complete the command.\nEnter HELP SETINDEX  for more information about this command, or press HELP when prompted for a new repository\nname.\nCAPI035W\nCursor not on a data line.\nReason:\nA KEEP command was entered but the cursor was not in a valid position. No change was made to your keep window.\nAction:\nIf you are attempting to add a data line to your keep window, place the cursor on the data line and repeat the command.\nOnly data lines located below the information and header lines can be added to the keep window.\nIf you are attempting to remove a data line from your keep window, place the cursor on the line within the keep window\nthat you would like to remove and repeat the command.\nEnter HELP KEEP  for more information about this command.\nCAPI036I\nKeep window is enabled.\nReason:\nThis message is displayed in response to a KEEP ON command. The keep window is displayed, unless it is empty.\nAction:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d4d7040ba389-1", "text": "Action:\nThis is an informational message, no action is required.\nEnter KEEP OFF  to disable the keep window, or enter HELP KEEP  for more information about this command.\nCAPI037I\nKeep window is disabled.\nReason:\nThis message is displayed in response to a KEEP OFF command. The keep window is suppressed, even if it contains\ndata.\nAction:\nThis is an informational message, no action is required.\n 1736", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bd3755370fc0-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nEnter KEEP ON  to enable the keep window, or enter HELP KEEP  for more information about this command.\nCAPI040I\nOptions updated.\nReason:\nThis message is displayed when you press END from the report options display to return to the repository index selection\nlist.\nThe repository is updated to reflect the options that you have selected for the report.\nAction:\nThis is an informational message, no action is required.\nUse CANCEL instead of END to exit the report options screen without updating the report options in your repository.\nEnter HELP RPTOPTS or press HELP while the report options screen is displayed for more information about viewing\nand updating report options.\nCAPI041E\nError updating options.\nReason:\nAn error was detected while attempting to update report options in your repository.\nAction:\nThe report may have been deleted by another user after you had entered the viewer.\nReturn to the repository index selection list, then enter REFRESH  and press Enter to rebuild the list.\nIf the report still appears in the list, contact Technical Support.\nCAPI042I\nOptions update cancelled.\nReason:\nYou entered a CANCEL command from the report options screen to return to the repository index selection list.\nAny changes to your report options were discarded.\nAction:\nThis is an informational message, no action is required.\nCAPI045I\nNotes request cancelled.\nReason:\nYou attempted to open the electronic notepad for a report by entering an n line command from the repository index\nselection list or by entering the NOTES command on the command line, but no existing notes were found in your profile\nfor the report.\nBecause your profile can only hold notes for a limited number of reports, a confirmation is required before a new notepad\ncan be created.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "bd3755370fc0-1", "text": "can be created.\nWhen prompted for a confirmation, you pressed END to cancel the request instead of pressing Enter to continue.\nThe request is cancelled, and the notepad is not created.\nAction:\nThis is an informational message, no action is required.\nCAPI049W\nCursor is not on a valid data field.\nReason:\n 1737", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3e95e15805b9-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nA cursor-sensitive command was entered on the command line without any argument, but the cursor was not located on a\nvalid data field.\nThe command fails because no argument can be determined.\nAction:\nRepeat the command by specifying a valid argument or position your cursor on a valid data line.\nCAPI052I\nProfile restored as of <hh:mm:ss> on <yyyy/mm/dd>.\nReason:\nA report which you have already viewed at least once has been selected for viewing again. The viewing environment\nfor this report, including the contents and status of the keep window, have been restored from your profile to its previous\nstate.\nThe time and date appearing in the message indicate the last time this report was exited by your userid.\nAction:\nThis is an informational message, no action is required.\nCAPI055I\nTag request cancelled.\nReason:\nYou entered a TAG or . command to create a bookmark in the current report, but you failed to specify a tag name. When\nprompted for a name, you responded by pressing END to cancel the request or by leaving the name field blank.\nThe command is cancelled, no bookmark is created.\nAction:\nThis is an informational message, no action is required.\nEnter HELP TAG for more information about this command, or repeat the command and press HELP while the pop-up\nprompt is displayed.\nCAPI056I\nTag <label> added for line number <nnnnn>.\nReason:\nThis message is displayed in response to a successful TAG or .label command. The new tag name and corresponding\nline number are displayed in the text of the message.\nAction:\nThis is an informational message, no action is required.\nEnter L label  at any time in the current session to instantly position the viewer to the current line.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3e95e15805b9-1", "text": "Enter HELP TAG or HELP LOCATE for more information about setting and retrieving bookmarks.\nCAPI057I\nTag <label> replaced for line number <nnnnn>.\nReason:\nThis message is displayed in response to a successful TAG or .label command, if the label you specified already existed\nfrom a previous TAG or .label command. The tag name and line number are displayed in the text of the message.\nAction:\nThis is an informational message, no action is required.\nEnter L label  at any time in the current session to instantly position the viewer to the current line.\nEnter HELP TAG or HELP LOCATE for more information about setting and retrieving bookmarks.\n 1738", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "58640c0d7391-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPI058I\nLocate request cancelled.\nReason:\nYou entered a LOCATE command to position the viewer to a bookmark, but you failed to specify a tag name. When\nprompted for a name, you responded by pressing END to cancel the request or by leaving the name field blank.\nThe command is cancelled, no repositioning is performed.\nAction:\nThis is an informational message, no action is required.\nEnter HELP LOCATE for more information about this command, or repeat the command and press HELP while the pop-\nup prompt is displayed.\nCAPI059E\nTag<label> not found.\nReason:\nYou entered a LOCATE command to position the viewer to a bookmark, but the tag name you specified was not\nrecognized.\nThe command is cancelled, no repositioning is performed.\nAction:\nCheck the spelling of your tag name, then repeat the command.\nEnter HELP LOCATE for more information about this command, or repeat the command and press HELP while the pop-\nup prompt is displayed.\nCAPI060I\nPrint cancelled.\nReason:\nYou initiated a print request for one of the following:\n\u2022\n\u2022The current display using a PRINT command.\n\u2022\n\u2022An entire report using a p line command from the repository index selection list.\n\u2022\n\u2022A symbolic listing using a p line command from a symbolic file member selection list.\n\u2022\nWhen prompted for specifications, you pressed END to cancel the request. No data was printed.\nAction:\nThis is an informational message, no action is required.\nIf you intended to complete the print request, repeat the command. When prompted for specifications, complete the fields\non the pop-up screen and press Enter to print.\nFor more information about the specifications, press HELP while the pop-up screen is displayed.\nCAPI061E", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "58640c0d7391-1", "text": "CAPI061E\nError printing member.\nReason:\nAn error occurred while attempting to print a listing from a symbolic (PROTSYM or CSL) file.\nThe listing is not printed.\nAction:\n 1739", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "a8bbec435e21-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThis is an internal error, contact Technical Support.\nCAPI062E\nError printing report.\nReason:\nAn error occurred while attempting to print one of the following:\n\u2022\n\u2022The current display using a PRINT command.\n\u2022\n\u2022An entire report using a p line command from the repository index selection list.\n\u2022\nThe listing is not printed.\nAction:\nThis is an internal error, contact Technical Support.\nCAPI063I\n<nnn> page(s) printed.\nReason:\nThis message is displayed in response to a successful PRINT request. < nnn> indicates the number of pages printed from\nthe current display.\nThe number of pages is determined by the number of lines printed and the number of lines per page requested.\nAction:\nThis is an informational message, no action is required.\nCAPI064I\nPrint was successful.\nReason:\nThis message is displayed in response to a successful p line command. The selected report or symbolic listing was\nprinted.\nAction:\nThis is an informational message, no action is required.\nCAPI066I\nProfile updated.\nReason:\nYou have successfully completed a PROFILE command or option 5 of the SYM command: Dynamic Symbolic Support for\nEndevor . Your profile variables have been updated.\nAction:\nThis is an informational message, no action is required.\nCAPI067I\nProfile update cancelled.\nReason:\nYou pressed END to exit either the PROFILE dialog or the Dynamic Symbolic Support Options window (option 5 of the\nSYM command). Your profile variables were not updated.\nAction:\n 1740", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8f83ce58a7b3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThis is an informational message, no action is required.\nIf you intended to update the profile, repeat the command. When you have set all of the variables as desired, press Enter\nto exit the dialog and update your profile with the new settings.\nCAPI070W\nNo program name specified.\nReason:\nYou entered a VIEW primary command but failed to specify which program name you wanted to view.\nAction:\nNo listing is displayed for viewing. Enter HELP VIEW  for more information about the VIEW command.\nCAPI071W\nSymbolic information not found in report.\nReason:\nYou entered a VIEW primary command but no symbolic information was found in the report for the specified program.\nAction:\nNo listing is displayed for viewing.\nCheck that the program name was spelled correctly, and that symbolic information was used for the program when the\nreport was formatted.\nYou may need to add the program listing to a symbolic file, or add the symbolic file to your global or supplemental\nsymbolic file list.\nEnter HELP VIEW  for more information about the VIEW command.\nCAPI074W\nMember not found.\nReason:\nYou entered a SELECT primary command but the member you selected was not found in the member list.\nAction:\nNo listing is displayed for viewing. Check that the program name was spelled correctly, and that the member actually\nexists in the symbolic file.\nCAPI075W\nNo program name specified\nReason:\nYou entered a SELECT primary command but did not specify the name of the program you would like to select for\nviewing.\nAction:\nNo listing is displayed for viewing. Enter the command again with a valid program name argument.\nCAPI075W0\nDynalloc failed for <ddname>, rc=<nn>, reason=<nnn>\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8f83ce58a7b3-1", "text": "Dynalloc failed for <ddname>, rc=<nn>, reason=<nnn>\nReason:\nA dynamic allocation failure occurred. The ddname and return codes from SVC 99 are displayed in the text of the\nmessage.\nAction:\nEvaluate the return codes from SVC 99 (dynalloc) to determine the cause of the failure.\n 1741", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b46907e6e8f8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThis error is often caused by a pre-existing allocation for the same ddname. If this is the case, free the allocation and try\nagain.\nIf you cannot determine the cause of this error, contact Technical Support.\nCAPI098E\nError initializing repository API, rc=nnn.\nReason:\nAn internal error was detected while attempting to initialize the repository API.\nThis may indicate one of the following conditions:\n\u2022\n\u2022Insufficient storage was available to load the API modules.\n\u2022\n\u2022One or more API modules could not be located.\n\u2022\n\u2022The license management program was not available.\n\u2022\nAction:\nVerify that your session has a sufficient region size, that your product libraries have been made available by LIBDEF or\nthrough linklist, and that the Common Components and Services  has been properly installed.\nIf you are still unable to determine the cause of this error, contact Technical Support.\nCAPI099E\nError initializing symbolic API, rc=nnn.\nReason:\nAn internal error was detected while attempting to initialize the symbolic API.\nThis may indicate one of the following conditions:\n\u2022\n\u2022Insufficient storage was available to load the API modules.\n\u2022\n\u2022One or more API modules could not be located.\n\u2022\nAction:\nVerify that your session has a sufficient region size, and that your product libraries have been made available by LIBDEF\nor through linklist.\nIf you are still unable to determine the cause of this error, contact Technical Support.\nCAPI100I\nRepository contains <nnn> report(s).\nReason:\nThis message appears whenever the repository index selection list is initially displayed or updated.\nThis occurs when you:\n 1742", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ee7f4e08fdfd-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022\n\u2022Start a new viewer session.\n\u2022\n\u2022Use the REFRESH command to update the contents of the list.\n\u2022\n\u2022Use the SETINDEX command to select a new repository.\n\u2022\n<nnn> indicates the number of reports in the repository, each of which appears in the selection list, sorted in descending\norder by date.\nAction:\nThis is an informational message, no action is required.\nCAPI101W\nHelp file DD is not allocated.\nReason:\nA HELP command was entered but the CAOIHELP DD statement is not properly allocated. Help cannot be displayed.\nAction:\nAllocate CAI.CAVHHELP using DDNAME CAOIHELP and restart the viewer.\nCAPI102E\nError reading help file.\nReason:\nA HELP command was entered but the CAOIHELP DD statement does not point to the CAI.CAVHHELP data set.\nAction:\nFree and reallocate CAOIHELP to point to CAI.CAVHHELP, then restart the viewer.\nCAPI103W\nHelp not available for <topic>.\nReason:\nA HELP command was entered with an explicitly defined topic name, but no help member was found for that topic.\nAction:\nTry one of the following HELP topics:\n\u2022\n\u2022HELP ALL lists all available help topics.\n\u2022\n\u2022HELP MSG lists help topics for Broadcom  messages.\n\u2022\n\u2022HELP SCREENS list help topics for viewer screens.\n\u2022\n\u2022HELP COMMANDS list help topics for viewer commands.\n\u2022\nCAPI108W\nSelected entry cannot be <action>.\nReason:\n 1743", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e309c9f24c95-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nYou have selected an item from the report tree selection list for an expand, collapse, toggle, or explode action.\nThe item that you selected has no subordinate items, so the action cannot be performed.\nItems that can be expanded, collapsed, or exploded are indicated by + or - in the area between the line number and item\ndescription, as follows:\n\u2022+ indicates that an item has subordinate items which are not visible, and therefore the item can be expanded or\nexploded. Use + or / to expand the item or ! to explode it.\n\u2022- indicates that an item has subordinate items which are already visible, and therefore the item can be collapsed. Use -\nor / to collapse it.\nNOTE\nAn expanded item indicated by - can also be exploded using ! if any of its subordinate items have the + indicator.\nAction:\nSelect a different item or use a different line command.\nCAPI109W\nSelected entry is already <expanded|collapsed>.\nReason:\nYou have selected an item from the report tree selection list for an expand + or collapse - action.\nThe item that you selected was already expanded or collapsed, so your action cannot be performed.\nItems which can be expanded, collapsed, or exploded are indicated by + or - in the area between the line number and\nitem description, as follows:\n\u2022+ indicates that an item has subordinate items which are not visible, and therefore the item can be expanded or\nexploded. Use + or / to expand the item or ! to explode it.\n\u2022- indicates that an item has subordinate items which are already visible, and therefore the item can be collapsed. Use -\nor / to collapse it.\nNOTE\nAn expanded item indicated by - can also be exploded using ! if any of its subordinate items have the + indicator.\nAction:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e309c9f24c95-1", "text": "Action:\nSelect a different item or use a different line command.\nCAPI111E\nError deleting report.\nReason:\nYou attempted to delete a report from your repository, but an error was detected and the report could not be deleted.\nAction:\nThe report may have been deleted by another user after you had entered the viewer.\nReturn to the repository index selection list, then enter REFRESH and press Enter to rebuild the list.\nIf the report still appears in the list, contact Technical Support.\nCAPI112W\nReport is locked and cannot be deleted.\nReason:\nYou attempted to delete a report from your repository, but the report has been locked and cannot be deleted.\nAction:\nThe user owning the lock is displayed in the Lock field of the repository index selection list. Contact this user to determine\nif the report is still needed. If not, use the u line command to unlock the report.\n 1744", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "37a66e3074ec-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPI118E\nAccess denied, request=<nn>, rc=<nn>.\nReason:\nYou attempted to access the contents of a repository, but access was denied by your system administrator.\nThe request types are:\n\u2022\n\u20225 - Open a report for viewing\n\u2022\n\u20229 - Delete a report from the repository\n\u2022\n\u202216 - Lock a report to prevent accidental deletion\n\u2022\n\u202217 - Unlock a report to allow deletion\n\u2022\n\u202221 - Update report options\n\u2022\n\u202222 - Print a report\n\u2022\nThe return codes are defined by your system administrator in the custom security exit.\nAction:\nContact your system administrator.\nCAPI120W\nReport is already locked.\nReason:\nYou attempted to lock a report using an l line command, but the report was already locked.\nAction:\nThe user owning the lock is displayed in the Lock field of the repository index selection list. Contact this user to determine\nif the lock is still needed. If not, ask the user to unlock the report, then try again.\nCAPI121E\nLock error, rc=<nnn>.\nReason:\nAn error occurred while you were attempting to lock a report. The report was not locked.\nAction:\nThis usually indicates that the report was locked or deleted by another job or user after your repository index selection list\nwas initially displayed.\nUse the REFRESH command to update the contents of the repository index selection list. If the report still appears in the\nlist, and the report has not been locked by another user, this may indicate an internal error. Contact Broadcom Support .\nCAPI122I\nReport has been locked.\nReason:\nA report was successfully locked in your repository in response to an l line command from the repository index selection\nlist.\nAction:\n 1745", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "51683ce5480b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThis is an informational message, no action is required.\nCAPI123W\nReport is not locked.\nReason:\nYou attempted to unlock a report using a u line command, but the report was not locked.\nAction:\nThis is a user error, the report cannot be unlocked.\nCAPI124E\nUnlock error, rc=<nnn>.\nReason:\nAn error occurred while you were attempting to unlock a report. The report was not unlocked.\nAction:\nThis usually indicates that the report was unlocked or deleted by another job or user after your repository index selection\nlist was initially displayed.\nUse the REFRESH command to update the contents of the repository index selection list. If the report still appears in the\nlist, and the report is still locked, this may indicate an internal error. Contact Broadcom Support .\nCAPI125I\nReport has been unlocked.\nReason:\nA report was successfully unlocked in your repository in response to a u line command from the repository index selection\nlist.\nAction:\nThis is an informational message, no action is required.\nCAPI140E\nInvalid value for <option>, specify <value-type>.\nReason:\nYou entered an invalid value for a report option.\nThe name of the option for which the error was detected and the correct value type for that option are both identified in the\ntext of the message.\nAction:\nEnter HELP RPTOPTS to list all of the options and their possible values. Correct the value for the option and press Enter\nto validate it.\nCAPI141E\nInternal Error.\nReason:\nAn internal error was detected while you were attempting to update report options.\nAction:\nContact Broadcom Support .\nCAPI145E\nDynalloc failed for <ddname>, rc=<nn>, reason=<nnn>.\n 1746", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3e4111dfc338-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nA dynamic allocation failure occurred while you were attempting to display your system installation options using an\nOPTIONS command.\nThe ddname and return codes from SVC 99 are displayed in the text of the message.\nAction:\nEvaluate the return codes from SVC 99 (dynalloc) to determine the cause of the failure.\nThis error is often caused by a pre-existing allocation for the same ddname. If this is the case, free the allocation and try\nagain.\nIf you cannot determine the cause of this error, contact Technical Support.\nCAPI146E\nError writing report, rc=<nnn>.\nReason:\nAn error occurred while you were attempting to display the system installation options.\nThe return code from the options program CAOUOPTS is included in the text of the message.\nAction:\nFor more information, execute CAOUOPTS in batch using the sample JCL provided in CAI.CAVHJCL or the following JCL\nmodel:\n// JOB\n//STEP1    EXEC PGM=CAOUOPTS //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR//SYSPRINT DD SYSOUT=*\nIf the return code in batch matches the return code from this message, review the job output for information related to the\nerror.\nIf you cannot determine the cause of this error, contact Technical Support.\nCAPI147E\nError opening report.\nReason:\nAn error occurred while you were attempting to display the system installation options.\nThe output from CAOUOPTS containing your installation options could not be opened.\nAction:\nThis probably indicates an internal error.\nTo view your options, execute CAOUOPTS in batch using the sample JCL provided in CAI.CAVHJCL or the following JCL\nmodel:\n// JOB", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3e4111dfc338-1", "text": "model:\n// JOB\n//STEP1    EXEC PGM=CAOUOPTS//STEPLIB DD DSN=CAI.CAVHLOAD,DISP=SHR\n//SYSPRINT DD SYSOUT=*\nIf this problem persists, contact Technical Support.\nCAPI199E\nLicense Management not installed.\nReason:\nThe license management component of Common Components and Services  was not properly installed.\nAction:\nContact Broadcom Support .\nCAPI201E\nDynalloc failed for <ddname>, rc=<nn>, reason=<nnn>.\nReason:\n 1747", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8c67e809c0ef-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nA dynamic allocation failure occurred while you were executing the symbolic utilities using a SYM command.\nThe ddname and return codes from SVC 99 are displayed in the text of the message.\nAction:\nEvaluate the return codes from SVC 99 (dynalloc) to determine the cause of the failure.\nThis error is often caused by a pre-existing allocation for the same ddname. If this is the case, free the allocation and try\nagain.\nIf you cannot determine the cause of this error, contact Technical Support.\nCAPI202E\nInvalid symbolic file.\nReason:\nThe data set you have entered as a symbolic file is not a valid PROTSYM or CSL file.\nAction:\nCorrect the data set name and try again.\nIf you cannot determine the cause of this error, contact Technical Support.\nCAPI203E\nSymbolic API error, func=<name>, rc=<nnn>.\nReason:\nAn error occurred while attempting to execute a symbolic utility using a SYM command.\nThe function name and return code are provided in the text of this message to assist Broadcom Support  with the problem\ndetermination.\nAction:\nFor some function types, this may be caused by an invalid symbolic file. Verify that your symbolic file name is correct.\nIf you still cannot determine the cause of this error, contact Technical Support.\nCAPI204E\nError retrieving CSL directory, rc=<nnn>.\nReason:\nAn error occurred while attempting to display a list of members for a CSL file.\nThe return code from program CAOUCSLD is included in the text of this message.\nAction:\nFor more information, execute CAOUCSLD in batch using the sample JCL provided in CAI.CAVHJCL or the following JCL\nmodel:\n// JOB", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8c67e809c0ef-1", "text": "model:\n// JOB\n//STEP1    EXEC PGM=CAOUCSLD//STEPLIB DD DSN=CAI.CAVHLOAD,DISP=SHR// DD\nDSN=CAI.CAVHLOAD,DISP=SHR//CAISYM   DD DSN=your.csl.dsn,DISP=SHR//SYSPRINT DD SYSOUT=*\n\u2022\n\u2022Note that your installation may use an alternate name for CAISYM.\nIf the return code in batch matches the return code from this message, review the job output for information related to\nthe error.\nIf you cannot determine the cause of this error, contact Technical Support.\n\u2022\nCAPI205E\nOpen failed for <ddname>.\nReason:\n 1748", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "03add32d47d3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAn error occurred while attempting to execute a symbolic utility using the SYM command.\nA file required by the utility could not be opened.\nThe ddname identifying the file is included in the text of the message.\nAction:\nContact Broadcom Support .\nCAPI206E\nError printing CSL member, rc=<nnn>.\nReason:\nAn error occurred while attempting to display a listing for a CSL member.\nThe return code from program CAORMAIN is included in the text of this message.\nAction:\nFor more information, execute CAORMAIN in batch using the sample JCL provided in CAI.CAVHJCL or the following JCL\nmodel:\n// JOB\n//STEP1    EXEC PGM=CAORMAIN//STEPLIB DD DSN=CAI.CAVHLOAD,DISP=SHR\n// DD DSN=CAI.CAVHLOAD,DISP=SHR//CAISYM   DD DSN=your.csl.dsn,DISP=SHR//CAIPRINT DD SYSOUT=//\nCAIPRNT1 DD SYSOUT= //CAIPRNT2 DD SYSOUT= //CAIOPTS  DD   PRINTCSL member-name/*\n\u2022\n\u2022Note that your installation may use alternate names for CAISYM, CAIPRINT, CAIPRNT1, CAIPRNT2, and CAIOPTS.\nIf the return code in batch matches the return code from this message, review the job output for information related to\nthe error.\nIf you cannot determine the cause of this error, contact Technical Support.\n\u2022\nCAPI207I\nMember <name> deleted from <dsname>.\nReason:\nThis message is displayed in response to a successful deletion of a symbolic file member.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "03add32d47d3-1", "text": "Reason:\nThis message is displayed in response to a successful deletion of a symbolic file member.\nThe member name and symbolic file dsname are both identified in the text of the message.\nAction:\nThis is an informational message, no action is required.\nCAPI208E\nError deleting member.\nReason:\nAn error occurred while attempting to delete a symbolic file member. The member could not be deleted.\nAction:\nThis problem can occur if the member was already deleted by another job or user after your member selection list was\ndisplayed.\nIf you are deleting from a PROTSYM file, verify that the delete password was entered correctly.\nIf you still cannot determine the cause of this error, contact Technical Support.\nCAPI209W\nCA SymDump not available on this system as set in CAVHCONF\nReason:\n 1749", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0ea4e1a0d98a-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe CAVHCONF configuration module, which is loaded into the CSA, indicates that the product is not intended to be used\non this system.\nAction:\nContact your systems programmer to ensure that the CAVHCONF configuration macro was implemented correctly on this\nsystem and that the CAVHINIT process was run.\nCAPI210E\nCAVHCONF module not found in the CSA\nReason:\nThe CAVHCONF configuration module was not found in the CSA.\nAction:\nCheck with your system programmer to ensure that the CAVHINIT process was run.\nCAPR312W\nNO SYMBOLIC INFORMATION FOUND FOR PROGRAM \"PPPPPPPP\".\nReason:\nSymbolic information was requested for a program but no information was found in any of the available PROTSYM or CSL\nfiles.\nMissing symbolic information usually results in termination of the requested report generation.\nAction:\nFirst, verify that the symbolic information has been written to a PROTSYM file or a CSL file. Then verify that the symbolic\nfile is available in your installation defaults, your JCL, or a SYMDSN override.\nIf you still cannot determine the cause of this message, contact Technical Support.\nCAPR313E\nERROR SEARCHING SYMBOLIC FILE DIRECTORY.\nReason:\nPossible internal error.\nAction:\nSave all output materials and contact Technical Support.\nCAPR318E\nERROR READING SYMBOLIC INFORMATION FOR PROGRAM <PPPPPPPP>.\nReason:\nPossible internal error.\nAction:\nSave all output materials and contact Technical Support.\nCAPR321E\nCSECT xxxxxxxx SYMBOLIC INFORMATION IS INCOMPLETE.\nReason:\nThe symbolic information for CSECT xxxxxxxx  is incomplete.\nAction:\n 1750", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "88a127bf956e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReload the program listing into the symbolic file. If the program was CAoptimized, recompile/optimize the program using\nthe SYM option to update your PROTSYM file, then relink the program and ensure that the updated PROTSYM file is\navailable. If the program was not CAoptimized, reload the listing using the appropriate postprocessor.\nIf you still cannot determine the cause of this message, contact Technical Support.\nCAPR322E\nCSECT xxxxxxxx SYMBOLIC INFORMATION CONTAINS NO LISTING DATA.\nReason:\nAn unexpected end of file was detected while reading the symbolic information for CSECT xxxxxxxx .\nAction:\nReload the program listing into the symbolic file. If the program was CAoptimized, recompile/optimize the program using\nthe SYM option to update your PROTSYM file, then relink the program and ensure that the updated PROTSYM file is\navailable. If the program was not CAoptimized, reload the listing using the appropriate postprocessor.\nIf you still cannot determine the cause of this message, contact Technical Support.\nCAPR323E\nCSECT xxxxxxxx SYMBOLIC INFORMATION CONTAINS ERRORS.\nReason:\nAn error was detected while reading the symbolic information for CSECT xxxxxxxx .\nAction:\nReload the program listing into the symbolic file. If the program was CAoptimized, recompile/optimize the program using\nthe SYM option to update your PROTSYM file, then relink the program and ensure that the updated PROTSYM file is\navailable. If the program was not CAoptimized, reload the listing using the appropriate postprocessor.\nIf you still cannot determine the cause of this message, contact Technical Support.\nCAPR327W\nCSECT xxxxxxxx IS AN INVALID CSECT NAME AND HAS BEEN IGNORED.\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "88a127bf956e-1", "text": "Reason:\nAn invalid CSECT name was encountered during input options processing.\nAction:\nCorrect the invalid CSECT name and rerun the job.\nIf you still cannot determine the cause of this message, contact Technical Support.\nCAPR333W\nTIMSV FILE FOR JOB xxxxxxxx IS INCOMPLETE.\nReason:\nNot all of the expected timing measurement information appears in the CAITIMSV.\nAction:\nCheck the execution step for any abnormal completions, and rerun the job. Contact Broadcom Support  for assistance.\nCAPR334E\nINTERNAL ERROR CONDITION DETECTED. CONTACT CA.\nReason:\nA serious internal error occurred during processing of the COBOL program. Processing of the COBOL program\nterminates. Diagnostic information for use by Broadcom Support  personnel is displayed. The job step abends.\nAction:\nRetain all JCL and listings and contact Technical Support for assistance. \n 1751", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ff8f0c70e890-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPR338E\nINTERNAL ERROR CONDITION DETECTED. CONTACT CA.\nReason:\nA serious internal error occurred during processing of the COBOL program. Processing of the COBOL program\nterminates. Diagnostic information for use by Broadcom Support  personnel is displayed. The job step abends.\nAction:\nRetain all JCL and listings and contact Technical Support for assistance.\nCAPR339E\nMAXIMUM WORKSPACE EXCEEDED. CANNOT PROCESS REQUESTED QUANTITY OF INPUT/OUTPUT.\nReason:\nThe internal sort routine ran out of space. The allowable maximum working space has been exceeded.\nAction:\nRerun the job with fewer report requests.\nCAPR340E\nWORKSPACE EXCEEDED. PLEASE INCREASE REGION BY UP TO xxxx K.\nReason:\nThe internal sort routine ran out of space.\nAction:\nIncrease the region size, or reduce the number of reports requested.\nCAPR436E\nINTERNAL ERROR CONDITION DETECTED. CONTACT CA.\nReason:\nA serious internal error occurred during processing of the COBOL program. Processing of the COBOL program\nterminates. Diagnostic information to be used by Broadcom Support  personnel is displayed. The job step abends.\nAction:\nRetain all JCL and listings and contact Technical Support for assistance.\nCAPR441W\nxxxxxxxx MUST PRECEDE yyyyyyyy, FOUND zzzzzzzz. yyyyyyyy IS IGNORED.\nReason:\nAn input statement was ignored because the expected xxxxxxxx  was not found.\nAction:\nReview the edited input. Rerun the job with the correct input if necessary.\nCAPR442W\nxxxxxxxxxxxxxxxxxxx IS NOT RECOGNIZED AND WILL BE IGNORED.\nReason:\nAn input string was not recognized and will be ignored.\nAction:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ff8f0c70e890-1", "text": "Reason:\nAn input string was not recognized and will be ignored.\nAction:\nReview the edited input. Rerun the job with the correct input if necessary.\n 1752", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "483337c48fe1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPR443W\nOPTS FILE IS EMPTY OR OMITTED \u2013 DEFAULT VALUES ASSUMED.\nReason:\nThe input parameter file has no data. The default values are used.\nAction:\nReview the default values. Rerun the job if necessary.\nCAPR444W\nBLANKS ARE ILLEGAL WITHIN A SUBLIST. SUBLIST HAS BEEN TERMINATED IN ERROR.\nReason:\nA blank was found in a parentheses-enclosed list. The sublist was terminated by replacing the first blank with a right\nparenthesis. Any remaining data is ignored.\nAction:\nReview the edited input. Rerun the job with the correct input if necessary.\nCAPR445W\nCARD ENDED WITHOUT TERMINAL QUOTE. ONE IS ASSUMED.\nReason:\nCharacter strings are not permitted to extend across statements. A beginning quote was found without a corresponding\nending quote. An ending quote was supplied in column 73.\nAction:\nReview the edited input. Rerun the job with the correct input if necessary.\nCAPR446W\nRIGHT PARENTHESES ARE ILLEGAL EXCEPT TO TERMINATE A SUBLIST.\nReason:\nA right parenthesis was found without a corresponding left parenthesis. The right parenthesis was ignored.\nAction:\nReview the edited input. Rerun the job with the correct input if necessary.\nCAPR447W\nLEFT PARENTHESES ARE ILLEGAL EXCEPT TO START A SUBLIST.\nReason:\nA left parenthesis was found within a sublist. Multiple levels of parentheses are not allowed. The left parenthesis is\nignored.\nAction:\nReview the edited input. Rerun the job with the correct input if necessary.\nCAPR448W\nIMPROPER USAGE OF RESERVED WORD xxxxxxxx, WILL BE REJECTED.\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "483337c48fe1-1", "text": "IMPROPER USAGE OF RESERVED WORD xxxxxxxx, WILL BE REJECTED.\nReason:\nxxxxxxxx  is used in the wrong context or follows an error in a preceding keyword. xxxxxxxx  is ignored.\nAction:\nReview the edited input. Rerun the job with the correct input if necessary.\n 1753", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dd1122536755-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPR449W\nxxxxxxxx INVALID OPERAND FOR yyyyyyyy, KEYWORD REJECTED.\nReason:\nxxxxxxxx  is not a valid subparameter of keyword yyyyyyyy . The keyword is rejected.\nAction:\nReview the edited input. Rerun the job with the correct input if necessary.\nCAPR450W\nxxxxxxxx REQUIRES yyyyyyyy, FOUND zzzzzzzz. KEYWORD IGNORED.\nReason:\nThe keyword xxxxxxxx  is ignored because the expected yyyyyyyy  was not found.\nAction:\nReview the edited input. Rerun the job with the correct input if necessary.\nCAPR451W\nSUBLIST LIMIT OF kkkkkkkk (nnnn) HAS BEEN EXCEEDED. EXCESSIVE ENTRIES WILL BE IGNORED.\nReason:\nKeyword kkkkkkkk  has a maximum of nnn subparameters and that number was exceeded. Excess entries are ignored.\nAction:\nReview the edited input. Rerun the job with the correct input if necessary.\nCAPR452W\nxxxxxxxx TOO LONG FOR yyyyyyyy. KEYWORD REJECTED.\nReason:\nxxxxxxxx  is too long for keyword yyyyyyyy . The keyword is rejected.\nAction:\nReview the edited input. Rerun the job with the correct input if necessary.\nCAPR453W\nxxxxxxxx TOO LONG FOR yyyyyyyy. VALUE TRUNCATED.\nReason:\nValue xxxxxxxx  is too long for keyword yyyyyyyy . Value xxxxxxxx  is truncated to the correct length.\nAction:\nReview the edited input. Rerun the job with the correct input if necessary.\nCAPR499E\nINTERNAL ERROR CONDITION DETECTED. CONTACT CA.\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dd1122536755-1", "text": "CAPR499E\nINTERNAL ERROR CONDITION DETECTED. CONTACT CA.\nReason:\nA serious internal error occurred during processing of the COBOL program. Processing of the COBOL program\nterminates. Diagnostic information is displayed for Broadcom Support  personnel. The job step abends.\nAction:\nRetain all JCL and listings and contact Technical Support for assistance.\nCAPU001E\nSYSPRINT DD STATEMENT MISSING OR INVALID.\n 1754", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "07f80f34f4ff-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nThe SYSPRINT DD statement was not specified correctly.\nAction:\nCorrect the SYSPRINT DD statement in the JCL and rerun the job.\nCAPU002E\nLIBRARY DD STATEMENT MISSING.\nReason:\nThe library DD statement was not specified.\nAction:\nCorrect the library DD statement in the JCL and rerun the job.\nCAPU003E\nLIBRARY NOT DIRECT ACCESS.\nReason:\nThe library data set does not reside on direct access volume. The library cannot be processed by CAOUMRS.\nAction:\nCorrect the data set name in the JCL or move this library to a direct access volume.\nCAPU004E\nLIBRARY DD STATEMENT INVALID.\nReason:\nThe library data set was not specified correctly.\nAction:\nCorrect the library data set in the JCL and rerun the job.\nCAPU005E\nLIBRARY HAS AN INVALID VOLUME SEQUENCE NUMBER.\nReason:\nThe library data set resides on multiple volumes and cannot be processed by CAOUMRS.\nAction:\nCheck the JCL to ensure it points to the correct library.\nCAPU006E\nLIBRARY NOT A PARTITIONED DATASET.\nReason:\nThe library is not a partitioned data set and cannot be processed by CAOUMRS.\nAction:\nCheck the JCL to ensure it points to the correct library.\nCAPU007E\nLIBRARY DATASET HAS AN INVALID RECFM.\nReason:\nThe library data set is not a valid load library and cannot be processed by CAOUMRS.\nAction:\nCheck the JCL to ensure it points at the correct library.\n 1755", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6ac2aac11ccb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPU008E\nUNABLE TO READ LIBRARY DICTIONARY.\nReason:\nAn I/O error occurred while attempting to read the library directory. The directory may be damaged.\nAction:\nCheck the directory to ensure it contains valid data. Correct or restore the library and rerun the job.\nCAPU009E\nUNABLE TO READ LIBRARY MEMBER: XXXXXXXX.\nReason:\nAn I/O error occurred while attempting to read a library member. The member may be damaged.\nAction:\nCheck the member to ensure it contains valid data. Correct or restore the library member and rerun the job.\nCAPU010E\nUNEXPECTED END OF FILE PROCESSING MEMBER: XXXXXXXX.\nReason:\nThe load module text information is incomplete. A member may be damaged.\nAction:\nCheck the member to ensure it contains valid data. Correct or restore the member and rerun the job.\nCAPU011W\nMAXCSECT WAS EXCEEDED PROCESSING MEMBER XXXXXXXX.\nReason:\nThe load module being processed has more than 512 CSECTs.\nAction:\nPass PARM='MAXCSECT=nnnn ' on the exec card when invoking MRS to increase the value of MAXCSECT, where nnnn\nis the maximum number of CSECTs to be processed for a load module.\nCAPU012W\nBINDER ERROR PROCESSING xxxxxxxx FUNCTION. RC= xx REASON= xxxxxxxx\nReason:\nThe BINDER encountered an error during function xxxxxxxx .\nAction:\nCheck to ensure that all members are bound/link-edited correctly. Processing continues.\nCAPU013W\nBINDER ERROR PROCESSING xxxxxxxx  FUNCTION FOR MODULE xxxxxxxx . RC= xx REASON= xxxxxxxx\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6ac2aac11ccb-1", "text": "Reason:\nThe BINDER encountered an error during function xxxxxxxx.\nAction:\nCheck to ensure that all members are bound/link-edited correctly. Processing continues.\nCAPU014E\nMAXIMUM SYSIN RECORDS EXCEEDED FOR CAOZAP\n 1756", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d12367cfcf36-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nOnly 100 SYSIN records can be processed per run.\nAction:\nLimit the number of SYSIN records to a maximum of 100.\nCAPU122E\nLICENSE MANAGEMENT PROGRAM NOT INSTALLED.\nReason:\nThe API for the License Management Program could not be found.\nAction:\nThis error will not cause any immediate problems. Execution continues normally; however, this message will be repeated\neach time a SymDump  Batch module is executed until the License Management Program is installed correctly. For more\ninformation, see the Common Components and Services  documentation.\nCAPU301E\nCAIPRINT OPEN FAILED.\nReason:\nAn error occurred while attempting to open the CAIPRINT file. CAIPRINT formatting ends. No CAIPRINT output is\ngenerated.\nAction:\nContact Broadcom Support .\nCAPU302E\nOPEN FAILED FOR CAIPRINT WORK FILE.\nReason:\nAn error occurred while attempting to open the CAIPRINT work file. CAIPRINT formatting ends. No CAIPRINT output is\ngenerated.\nAction:\nContact Broadcom Support .\nCAPU303E\nOPEN FAILED FOR CAIPRINT REPOSITORY.\nReason:\nAn error occurred while attempting to open the CAIPRINT repository. CAIPRINT formatting ends. No CAIPRINT output is\ngenerated.\nAction:\nContact Broadcom Support .\nCAPU304E\nMEMORY MANAGER INITIALIZATION FAILED.\nReason:\nAn internal error was detected while formatting an Abend report.\nAction:\nSave all materials and contact Technical Support.\n 1757", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6b01d25ea8cb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPU305E\nMEMORY MANAGER PUT FAILED.\nReason:\nAn internal error was detected while formatting an Abend report.\nAction:\nSave all materials and contact Technical Support.\nCAPU306E\nMEMORY MANAGER GET FAILED.\nReason:\nAn internal error was detected while formatting an Abend report.\nAction:\nSave all materials and contact Technical Support.\nCAPU308I\nSYMBOLIC INFORMATION AUTO POPULATED TO dsn.\nReason:\nSymbolic information for the program name in the program box was automatically populated by the Endevor  dynamic\nsymbolic support feature to the PROTSYM data set named dsn.\nAction:\nNone. Informational only.\nCAPU309E\nSYMBOLIC FOR PROGRAM pgm  NOT POPULATED. DYNAMIC SYMBOLIC SUPPORT ERROR. RC=xxxx ,\nRSC= yyyy\nReason:\nSymbolic information for the pgm named in the program box was NOT populated due to an error encountered by the\nEndevor  dynamic symbolic support feature. Return code from DSS is xxxx. Reason code from DSS is yyyy.\nThe following table provides a list of possible return codes (RC) and reason codes (RSC) the API and various components\nmay return.\nNOTE\nOther numeric return codes and reason codes are also returned by Endevor  and z/OS binder services API\n(IEWBIND). For more information, see the respective articles.\nFunction RC RSC Meaning\nAPI 00 0 Operations completed\nsuccessfully.\nEndevor 12 0 1. Incorrect C1DEFLTS used.\n2. Listing data set referenced by\nthe footprint is not cataloged.\n3. For more information see\nthe SYSOUT containing the\nEndevor  API execution report.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6b01d25ea8cb-1", "text": "the SYSOUT containing the\nEndevor  API execution report.\nEndevor 32 15 Endevor  encountered critical\nerror and cannot continue.\n 1758", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "43817c2aa138-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAny function Any four digit code CCI The CAICCI component\nencountered an error\ncommunicating with the list\nserver (INTNDVRx). See\nappropriate CCI documents for\ndetails.\nAny function Any four digit code CDRV One of the components\n(Broadcom  Testing and Fault\nManagement) used by the list\nserver interface encountered\nan error. Examine SYSOUT\ndata sets from the started task\nINTNDVRx for appropriate\ncomponent error logs and\nsolutions.\nNDSB 04 NDSB Compressed footprint in IDRU\ninvalid.\nAPI 02 NDVR GETMAIN failed.\nAPI 08 NDVR Endevor  server not activated.\nAPI 12 NDVR Invalid or missing parameter\nin NDVRCOMM. Listing data\nset not found. See Endevor\nMessage and Response file.\nAPI 16 NDVR Bad return code from Endevor .\nSee Endevor  documentation.\nAPI 20 NDVR Data set open failed.\nAPI 28 NDVR Allocation error. See SRVPRINT\nfile.\nAPI 32 NDVR IN25DALC load failed.\nAPI 36 NDVR ENA$NDVR load failed.\nAPI 40 NDVR Endevor  footprint not found for\nrequested element.\nAPI 44 NDVR Requested CSECT not found.\nAPI 48 NDVR IN25CDRV load failed.\nNSRV 08 NSRV Listing server abort or failed.\nNIDR 02 XIDR GETMAIN failed.\nNIDR 08 XIDR PARM error.\nNIDR 20 XIDR CAOUXDSB load failed.\nNIDR 2C XIDR No IDRU found for CSECT in", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "43817c2aa138-1", "text": "NIDR 2C XIDR No IDRU found for CSECT in\nNDVR_NAM2 or NDVR_ELEM.\nCSVQ 30 XIDR CSECT from IDRU does not\nmatch CSECT in NDVR_NAM2.\nBINDER 44 XIDR Requested CSECT not found by\nbinder.\nAction:\nAppropriate action should be taken based on the return and reason code.\n 1759", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "06a3392373ab-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPU310W\nCAOFSYMP \u2013 LOAD OF CAODNDVR FAILED.\nReason:\nDynamic symbolic support encountered an error loading module CAODNDVR.\nDynamic symbolic support will not be able to populate the symbolic file.\nAction:\nEnsure that the SymDump  Batch product load module libraries are correctly defined in your JCL or are defined in your\ninstallation's LNKLST.\nCAPU311W\nNO FOOTPRINT WAS FOUND FOR PROGRAM XXXXXXXX. .\nReason:\nProgram XXXXXXXX  does not have the required Endevor  footprint.\nDynamic symbolic support is unable to populate the symbolic file for the indicated program.\nAction:\nEnsure that the indicated program is under Endevor  control and that the associated load modules were generated using\nthe Endevor  Generate facility.\nFor more information, see Dynamic Symbolic Support For Endevor  in Symbolic Support.\nCAPU312I\nEND OF DATA ENCOUNTERED BEFORE END OF MAP. SOME VARIABLES MAY NOT BE DISPLAYED.\nReason:\nThe storage associated with a data area is shorter than the map of the area in the symbolic file member. This can occur in\nthe following instances:\n\u2022The current record for a variable-length file is shorter than the maximum length defined in the File Section of a COBOL\nprogram.\n\u2022The BLLMAX value is smaller than the length of an 01 item in the Linkage Section of a COBOL program.\n\u2022The REGMAX value is smaller than the length of a DSECT definition for which there is an active USING in an\nAssembler program.\n\u2022The symbolic file member does not exactly match the program in the executable load module, as indicated by a\nCAPD113W message.\nAny variables that map to data beyond the end of the available storage will not be displayed.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "06a3392373ab-1", "text": "Any variables that map to data beyond the end of the available storage will not be displayed.\nAction:\nNo action is required. However, the message may be eliminated if it was not caused by a short record in a variable-length\nfile using one of the following methods:\n\u2022If the message is displayed because the BLLMAX value is smaller than the length of an 01 item in the Linkage Section\nof a COBOL program, specify a larger BLLMAX value and rerun the job.\n\u2022If the message is displayed because the REGMAX value is smaller than the length of a DSECT definition for which\nthere is an active USING in an Assembler program, specify a larger REGMAX value and rerun the job.\n\u2022If a CAPD113W message was displayed, indicating that the symbolic file member does not exactly match the program\nin the executable load module, follow the action specified for that message.\n \nCAPU313E\nOFFSET DOES NOT CORRESPOND TO A STATEMENT WITHIN THE PROGRAM.\nReason:\n 1760", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "62db4ac4f1ba-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe indicated program offset does not correspond to a source statement in the program. A source statement could not be\nfound.\nAction:\nIf a CAPD113W message was displayed, indicating that the symbolic file member does not exactly match the program in\nthe executable load module, follow the action specified for that message. Otherwise, contact Technical Support.\nCAPU399E\nINTERNAL ERROR. CAIPRINT FORMATTER IN CONTROL.\nReason:\nThe error recovery mechanisms (for example, ESTAE exits) of the CAIPRINT Formatter have encountered an unexpected\nand unrecoverable abend. The most likely event is an unexpected OCx abend.\nThis could be traceable to an invalid control block, product logic error, or user error. A few data elements related to the\nabend are captured and an attempt is made to relate the abending PSW address to an offset within a named module.\nThe abend code (for example, OC4) and the registers at abend, along with other pertinent information, are written to\nCAIPRINT and a dump is produced.\nAction:\nContact Broadcom Support  to report the problem after the dump is available. In the RTM2WA summary, abends are\nrepresented by a chain of SDWA control blocks displayed in chronological order from the oldest to the newest. Generally,\ndiagnose the problem by finding the SDWA in the RTM2WA SUMMARY chain that matches the abend code and registers\ndisplayed on CAIPRINT.\nCAPU400I\nTHE FOLLOWING EXPIRED REPORTS WILL BE DELETED:\nReason:\nWhile adding an Abend report to the repository, one or more reports were found that exceeded the expiration limit\nestablished for your installation by the EXPDAYS option in CAOUDFRX. These reports were deleted.\nAction:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "62db4ac4f1ba-1", "text": "Action:\nNo action is required. However, to prevent this message and the automatic deletion of abend reports from your repository,\nset the EXPDAYS option to zero.\nCAPU401I\nJ=jjjjjjjj,S=ssssssss,P=pppppppp,O=oooooo,ccccc.\nReason:\nThis informational message appears once for each report that was automatically deleted due to expiration. The job name,\nsystem name, program name, offset, and completion code are used to identify the message.\nAction:\nNo action is required. However, to prevent this message and the automatic deletion of abend reports from your repository,\nset the EXPDAYS option to zero.\nCAPU402I\nAUTO-MAINTENANCE COMPLETED.\nReason:\nThis message is written after all abend reports in your repository have been tested for expiration, only if reports were\nactually deleted during the process.\nAction:\nNo action is required.\n 1761", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "656a692ad730-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAPU502E\nRUN TIME DEFAULTS CSECT 'CAOUDFRX' NOT FOUND. REPORTING TERMINATED.\nReason:\nThe options reporting program was unable to find the runtime default options member, CAOUDFRX. Options reporting\nwas terminated.\nAction:\nVerify that the library containing the runtime options member, CAOUDFRX, is available to the options reporting program in\nLINKLIST or LPA, or was specified in the JCL in STEPLIB or JOBLIB.\nCAPU307E\nRecord Error. Special Record Expected But Not Found.\nReason:\nAn internal error was detected while formatting an Abend report.\nAction:\nSave all materials and contact Technical Support.\nCAPHC001I\nThe CA SymDump Batch repository file prtlib.name is at nn.n% capacity.\nSymDump  Batch is capable of capturing future abend reports to facilitate rapid problem diagnosis. This will help\nensure normal business processes complete in a timely manner.\nReason:\nThe SymDump  health check program CAOCHCHK has performed a check on the PRTLIB file and has found the file to be\nwithin safe capacity levels.\nAction:\nNo action is required.\nCAPHC001W\nCA SymDump Batch repository file is nearing capacity.\nFile prtlib.name is at nn.n% capacity.\nIf the repository becomes full, future abend reports will not be captured.\nReason:\nThe index file has met or exceeded the capacity trigger set in the CAOETABL options table parameter PRTLHCT=. The\nSymDump  Batch PRTLIB file is filling up and may not have the capacity to save future abend reports.\nAction:\nThe SymDump  Batch repository file must be maintained using utility program CAOUPRTU. Procedure CAIPRTU can be", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "656a692ad730-1", "text": "used to execute the utility to copy or delete dump reports from the repository file to free space for future abend reports.\nSymDump REST API Messages\nThis section defines errors, warnings, and informational messages specific to SymDump Batch REST API and SymDump\nCICS REST API.\nMessage Format\nAll messages issued by SymDump BATCH REST API and by SymDump CICS REST API are in the format CAVHR<xyz >\n 1762", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dcf6433776d6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n CAVHR01E\nInvalid key, no corresponding report found.\nReason:\nThe report key provided does not exist in the requested dump repository.\nAction:\nUse the Reports REST API endpoint of the dump repository to extract the report key, and provide a valid key.\nCAVHR03E\nWhen you populate a non LE-enabled ASSEMBLER option, \nthe ndvrDSSdsn option data set name of a PROTSYM file is required.\nReason:\nIf the ndvrDSSasm  value set to 'Y', the non LE-enabled ASSEMBLER option is active and the ndvrDSSdsn  option is\nrequired.\nAction:\nSpecify the ndvrDSSdsn  option, or remove ndvrDSSasm  option from the request body.\nCAVHR04E\nValues to populate a non LE-enabled ASSEMBLER option are 'Y' or 'N'.\nReason:\nValid ndvrDSSasm  option values to populate a non LE-enabled ASSEMBLER option are 'Y' or 'N'.\nAction:\nChange the ndvrDSSasm  option to 'Y' or 'N' as appropriate.\nCAVHR05E\nInvalid mainframe user credentials.\nReason:\nInvalid mainframe user name or password.\nAction:\nProvide valid mainframe user credentials.\nCAVHR06E\nChecked Exception with recoverable condition.\nReason:\nCheck the message for a reason\nAction:\nCheck the message for actions.\nCAVHR07E\n<dataset name > data set not found.\nReason:\nThe data set that was provided does not exist.\n 1763", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4a87b8686ffa-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nProvide a valid data set name.\nCAVHR08I\nDelete request successful.\nReason:\nA report was successfully deleted from your repository.\nAction:\nInformational message, no action required.\nCAVHR09E\nThis is an exception message originating from Spring Boot.\nReason:\nCheck the message for a reason.\nAction:\nCheck the message for actions.\nCAVHR10I\nLock request successful.\nReason:\nA report was successfully locked in your repository.\nAction:\nInformational message, no action required.\nCAVHR11E\nReport is already locked.\nReason:\nYou tried to lock a report that is already locked.\nAction:\nContact the user who locked the report to determine if the lock is still needed. If the lock is no longer needed, ask the user\nto unlock the report, then try again to lock the report.\nNOTE\nThe user who owns the lock is displayed in the Lock  field of Report REST API endpoint.\nCAVHR12I\nUnlock request successful.\nReason:\nA report in your repository was successfully unlocked.\nAction:\nInformational message, no action required.\n 1764", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b190796e33d3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAVHR13E\nReport is not locked.\nReason:\nYou attempted to unlock a report that is not locked. Unlocked reports cannot be unlocked\nAction:\nInformational message, no Action required.\nCAVHR14I\nUpdate report option is successful.\nReason:\nReport options are successfully updated in the repository.\nAction:\nInformational message, no action required.\nCAVHR15E\n<option_name > value exceeds the maximum size <size>.\nReason:\nThe < option_name > value exceeds the maximum number of characters allowed.\nAction:\nSpecify the ndvrDSSdsn  option, or remove ndvrDSSasm  option from the request body.\nCAVHR16E\nLocked report options cannot be updated.\nReason:\nThe requested options for the specific report are locked and cannot be updated.\nAction:\nUnlock the report and resend the update report options request.\nCAVHR17E\nReport is locked and cannot be deleted.\nReason:\nThe report you tried to delete is locked. You cannot delete locked reports.\nAction:\nUnlock and delete the report\nCommon Runtime Messages\nThe followong list shows common runtime messages\nCAVH001E UNKNOWN PARM PROCESSING ERROR. INITIALIZATION PROCESSING TERMINATED\nReason:\nProgram CAVHINIT encountered unrecognized or mutually exclusive parameters.\n 1765", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2b8b8c5b6bc4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nReview the PARM() parameters on the CAIRIM control statement that invokes CAVHINIT, and correct any errors. For\nmore information, see Activate Your Product.\nCAVH002E <table> ADD FAILED, INITIALIZATION TERMINATED\nReason:\nProgram CAVHINIT failed to load the specified table into CSA.\nAction:\nCorrect any errors that could have made the table unavailable and rerun. If the problem persists, contact Broadcom\nSupport.\nCAVH003I <table> LOADED\nReason:\nProgram CAVHINIT successfully loaded the specified table into CSA.\nAction:\nNone.\nCAVH004I PRODUCT INTENT: <option> OPTION <\u2019ON\u2019 or \u2018OFF\u2019>\nReason:\nProgram CAVHINIT documents the product intent option settings from table CAVHCONF. This message is issued once for\neach of the product intent options: DYNAMIC, INTBAT, SYMBAT, SYMCICS, and INTCICS.\nNote:  If DYNAMIC is ON, the settings for the products are set based on the availability of LMP keys.\nAction:\nNone.\nCAVH005E SBONLY AND RTLONLY MAY NOT CANNOT BOTH BE SPECIFIED\nReason:\nThese options are mutually exclusive.\nAction:\nSpecify SBONLY, RTLONLY, or neither and resubmit your CAIRIM job.\nCAVH006E #LPA ADD FOR CAOSBID FAILED\nReason:\nCAVHINIT cannot load CAOSBID into CSA.\nAction:\nVerify that module CAOSBID (in yourhlq .CAVHAUTH) is available.\nCAVH007E LICENSE MANAGEMENT PROGRAM NOT INSTALLED\nReason:\nThe CAIRIM Common Services component is not available.\nAction:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "2b8b8c5b6bc4-1", "text": "Reason:\nThe CAIRIM Common Services component is not available.\nAction:\nReview the CAIRIM/CAS9 job for errors. If the cause is not obvious, Broadcom Support.\n 1766", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9728e667bacc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDynamic Symbolic Support Messages\nThis section lists the messages that can be produced by the InterTest for CICS symbolic postprocessor program\nIN25SYMP. These messages include a description of the internal logical problem that caused the message to be issued.\nAlthough certain messages are duplicates, the different message codes help InterTest for CICS support personnel locate\nthe exact location of the error.\nNOTE\nDRC=n stands for a unique return code used by InterTest for CICS personnel for debugging purposes only.\nCAIN5900I\nmm/dd/yyyy  hh:mm:ss IN25NDVR STARTED FOR PRGNNAME \u2013 pppppppp.\nReason:\nThis message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was\nissued. This is an informational message indicating that the Listing Server is retrieving the symbolic for program named\npppppppp. This message is used to serve as a beginning bookmark for message extraction. All messages issued after\nthis message are extracted by message extraction service.\nAction:\nNone.\nCAIN5903E\nmm/dd/yyyy  hh:mm:ss IN25NSRV CCI SPNPARM FAILED.\nReason:\nThis message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was\nissued. This error occurred when IN25NSRV issued a CCI SPNPARM request. Message CAIN5930 is usually issued in\nconjunction with this message.\nAction:\nExamine feedback area provided in message CAIN5930 to determine the cause of the error, correct the error and do the\nrequest again.\nCAIN5903E0\nmm/dd/yyyy  hh:mm:ss IN25NSRV CCI INIT FAILED.\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9728e667bacc-1", "text": "mm/dd/yyyy  hh:mm:ss IN25NSRV CCI INIT FAILED.\nReason:\nThis message is issued by IN25NSRV. where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was\nissued. CCI INIT action has failed. This error occurred when IN25NSRV issued a CCI INIT request. Message CAIN5930 is\nusually issued in conjunction with this message.\nAction:\nExamine feedback area provided in message CAIN5930 to determine the cause of the error, correct the error and do the\nrequest again.\nCAIN5904I\nmm/dd/yyyy  hh:mm:ss IN25NSRV WAITING FOR WORK.\nReason:\nThis message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was\nissued. This is an informational message indicating that the Listing Server is waiting for work.\nAction:\nNone.\n 1767", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e7411477df9e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN5905E\nmm/dd/yyyy  hh:mm:ss IN25NSRV RECVANY FAILED.\nReason:\nThis message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was\nissued. This error occurred when IN25NSRV issued a CCI Receive Any request. Message CAIN5930 is usually issued in\nconjunction with this message.\nAction:\nExamine feedback area provided in message CAIN5930 to determine the cause of the error, correct the error and do the\nrequest again.\nCAIN5905E0\nmm/dd/yyyy  hh:mm:ss IN25NSRV RECVANY FAILED, INVALID DATA.\nReason:\nThis message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message\nwas issued. This error occurred when IN25NSRV issued a CCI Receive Any request and the data received are invalid.\nMessage CAIN5930 is usually issued in conjunction with this message.\nAction:\nExamine feedback area provided in message CAIN5930 to determine the cause of the error, correct the error and do the\nrequest again.\nCAIN5905E1\nmm/dd/yyyy  hh:mm:ss IN25NSRV RECVANY FAILED, RECEIVED NULLS.\nReason:\nThis message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was\nissued. This error occurred when IN25NSRV issued a CCI Receive Any request and the data received contained all null\nvalues. Message CAIN5930 is usually issued in conjunction with this message.\nAction:\nExamine feedback area provided in message CAIN5930 to inspect the block received. This could be the result of\ntransmission error. If the problem persists contact Broadcom Support .", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e7411477df9e-1", "text": "transmission error. If the problem persists contact Broadcom Support .\nCAIN5905E2\nmm/dd/yyyy  hh:mm:ss IN25NSRV RECVANY FAILED, INVALID LENGTH.\nReason:\nThis message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was\nissued. This error occurred when IN25NSRV issued a CCI Receive Any request and length of the data block received was\nincorrect. Message CAIN5930 is usually issued in conjunction with this message.\nAction:\nExamine feedback area provided in message CAIN5930 to inspect the length of data block received. This could be the\nresult of transmission error. If the problem persists contact Broadcom Support .\nCAIN5907E\nmm/dd/yyyy  hh:mm:ss IN25NSRV SENDSPEC FAILED.\nReason:\nThis message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message\nwas issued. This error occurred when IN25NSRV issued a CCI Send action. Message CAIN5930 is usually issued in\nconjunction with this message.\nAction:\n 1768", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0b3b47a49f28-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nExamine feedback area provided in message CAIN5930 to determine the reasons for the failure. This could be the result\nof transmission error. If the problem persists contact Broadcom Support .\nCAIN5908W\nmm/dd/yyyy  hh:mm:ss IN25NSRV GETMAIN FAILED.\nReason:\nThis message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was\nissued. The message indicated that GETMAIN for 32K of main storage has failed.\nAction:\nMake sure that you have specified a sufficiently large region size to meet the many main storage requirements of the\nListing service.\nCAIN5909I\nmm/dd/yyyy  hh:mm:ss IN25NSRV REQUEST RECEIVED FOR eeeeeeee.\nReason:\nThis message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was\nissued. This is an informational message indicating that a listing request for element named eeeeeeee has been received.\nAction:\nNone.\nCAIN5913I\nmm/dd/yyyy  hh:mm:ss IN25NSRV SENDING RESPONSE\nReason:\nThis message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message\nwas issued. This is an informational message indicating that the request by message CAIN5909 has been serviced and\nresponse is being sent back to the remote host.\nAction:\nNone.\nCAIN5930I\nmm/dd/yyyy  hh:mm:ss IN25NSRV CCI FEEDBACK: feedback info.\nReason:\nThis message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "0b3b47a49f28-1", "text": "issued. This is the message that is usually issued in conjunction with CCI-related error conditions. Feedback is a 256\nbytes area containing CCI return codes, reason codes, and brief description associated with the error encountered.\nAction:\nUse the information provided in this message in conjunction with the failure message to diagnose the error.\nCAIN5950I\nmm/dd/yyyy  hh:mm:ss IN25NSRV SHUTDOWN.\nReason:\nThis message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was\nissued. This is an informational message indicating that the Listing server is shutting down.\nAction:\nNone.\n 1769", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "82392533318e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN5970W\nLINK TO IN25SPOL FAILED.\nReason:\nThis message is issued by IN25NSRV indicating that LINK to IN25SPOL has failed. Message extraction will not be\nperformed.\nAction:\nDetermine that the data set containing IN25SPOL is either defined in the LINKLIST or is properly defined in the STEPLIB\nconcatenations.\nCAIN5980E\nCA SCM CRITICAL ERROR. ERROR CODE: eeee. REQUEST FOR pppppppp NOT SERVICED.\nReason:\nThis message is issued by IN25NSRV and is used as an end bookmark for message extraction. All messages issued\nbefore this message are extracted by the message extraction service.\nAction:\nNone.\nCAIN5980E0\nCA SCM CRITICAL ERROR. ERROR CODE: rrrr. REQUEST FOR mmmmmmmm NOT SERVICED.\nReason:\nThis message is issued by IN25NSRV. This indicated that Endevor  for mainframe encountered a critical error. The error\ncode is rrrr. Symbolic request for element named mmmmmmmm is not serviced.\nAction:\nUse the rrrr error code in conjunction with the SRVPRINT log and DSSLOG to determine the cause, correct the error and\nredo the request.\nCAIN5990I\nALLOCATION OF LOG FILE FAILED. LOGGING DISABLED.\nReason:\nThis message is issued by IN25FSYM, indicating that dynamic allocation for SRVPRINT DD has failed. Logging activities\nis disabled. This message is usually followed by IBM IKJ5635 message providing the dynamic allocation text unit that\nfailed.\nAction:\nDetermine and correct the cause for failure then retry the action.\nCAIN5990I0\nLINK TO IN25SPOL FAILED.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "82392533318e-1", "text": "CAIN5990I0\nLINK TO IN25SPOL FAILED.\nReason:\nThis message is issued by IN25NSRV. LINK SVC for IN25SPOL has failed. Message extraction will not be performed.\nAction:\nMake sure that the data set containing IN25SPOL is either defined in the LINKLIST or properly defined in the STEPLIB\nDD.\nCAIN5991W\nHHMM DOES NOT MATCH.\nReason:\n 1770", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ff856d85acaf-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThis message is issued by IN25FSYM. The hour and minute of the timestamp found in the symbolic does not match the\ntimestamp provided by the caller for the same symbolic. Requested action is not performed.\nAction:\nProvide the correct timestamp value and try the action again.\nCAIN5995E\nNO PROTSYM SEARCH LIST PROVIDED.\nReason:\nThis message is issued by IN25FSYM. User did not provide one or more PROTSYM data set names to perform symbolic\nsearch. Requested action is not performed.\nAction:\nProvide at least one or up to a maximum of eight PROTSYM fully qualified data set names to be used for symbolic search.\nCAIN6000E\nDYNAMIC UNALLOCATION FAILED FOR nnnnnnnn. RC= rr. RSN= ssssssss.\nReason:\nThis message is issued by IN25FSYM. Dynamic allocation of data set with nnnnnnnn DD name has failed. Return code\nfrom Dynamic Allocation is rr and the reason code is ssssssss.\nAction:\nUse the return code and reason code to determine the cause of the failure. Correct the error and retry the action.\nCAIN6000W\nDYNAMIC UNALLOCATION FAILED FOR dddddddd RC=rr. RSN=ssssssss\nReason:\nThis message is issued by IN25FSYM. Dynamic unallocation of dddddddd DD name has failed. The Dynamic\nUnallocation return code is rr and reason code is ssssssss.\nAction:\nUse the return code and reason code to determine the cause of the failure. Correct the error and retry the action. If the\nerror persists, call Broadcom Support .\nCAIN6010W\nLOAD OF pppppppp FAILED. RC= rr\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ff856d85acaf-1", "text": "LOAD OF pppppppp FAILED. RC= rr\nReason:\nThis message is issued by IN25FSYM. Loading of program named pppppppp has failed. The return code is rr.\nAction:\nMake sure that the data set containing the pppppppp program is in the LINKLIST or defined in the STEPLIB DD.\nCAIN6020W\nFAILED IN ROUTINE: rrrrrrrrrr RC= rr\nReason:\nThis message is issued by IN25FSYM. Routine named rrrrrrrr has failed with a return code of rr. This message is usually\nassociated with IN25SAPI and rrrrrrrr is the failed SAPI function.\nAction:\nDetermine the error and retry the request.\n 1771", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7b0ce7595889-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN6070E\nCRITICAL ERROR LD@DSSDSN INVALID VALUE.\nReason:\nThis message is issued by IN25FSYM. The data set name provided in LD@DSSDSN is invalid.\nAction:\nLD@DSSDSN should contain a valid DD name to be used for DSS logging. It is usually specified as DSSLOG. Correct\nthe DD name and retry the action.\nCAIN7000W\nIN25NDVR MAJOR ERROR, LOG FILE NOT OPENED\nReason:\nSRVPRINT log file not opened. Endevor activity log disabled.\nAction:\nWe recommend that //SRVPRINT DD SYSOUT=* be defined in the job's JCL so that relevant error can be captured to\nassist in problem analysis. This would avoid the need to recreate the error.\nCAIN7010I\nIN25NDVR ALLOCATION OF LOG FILE FAILED.\nReason:\nDynamic allocation of activity log has failed. This message is usually followed by IBM IKJ5635 message providing the\ndynamic allocation text unit that failed.\nAction:\nDetermine and correct the cause of the error and retry the request.\nCAIN7020W\nLOAD OF IN25DALC FAILED.\nReason:\nIN25NDVR encountered an error trying to LOAD IN25DALC. Endevor List request will not be performed.\nAction:\nMake sure that the data set containing IN25DALC load module is either defined in the LINKLIST or is defined in the\nSTEPLIB concatenation.\nCAIN7030W\nLOAD OF ENA$ NDVR FAILED.\nReason:\nIN25NDVR cannot LOAD the ENDEVOR API. Endevor List request will not be performed.\nAction:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7b0ce7595889-1", "text": "Action:\nMake sure that Endevor AUTHLIB and CONLIB data sets are either defined in the LINKLIST or defined in the job's JCL.\nCAIN8000W\nJESMSGLG JCT MTTR FOUND.\nReason:\nThis message is issued by IN25SPOL when Broadcom Support  requested diagnostic messages. The message indicates\nthat MTTR of JESMSGLG JCT was found.\nAction:\nNone.\n 1772", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7496ac168411-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN8010I\nJESYSMSG JCT MTTR FOUND.\nReason:\nThis message is issued by IN25SPOL when Broadcom Support  requested diagnostic messages. The message indicates\nthat MTTR of JESMSGLG JCT was found.\nAction:\nNone.\nCAIN8020I\nACQUIRED MSGLOG AND SYSMSG JCT\nReason:\nThis message is issued by IN25SPOL when Broadcom Support  requested diagnostic messages. This message indicates\nthat the JCT for JESMSGLG and JESYSMSG have been acquired.\nAction:\nNone.\nCAIN8030W\nUNABLE TO ACQUIRE JCT OF EITHER JESMSGLG OR JESYSMSG.\nReason:\nThis message is issued by IN25SPOL when Broadcom Support  requested diagnostic messages. The message indicated\nthat IN25SPOL was unable to acquire the JCT of either JESMSGLG or JESYSMSG. Message extraction will not be\nperformed.\nAction:\nContact Broadcom Support  with the information.\nCAIN8040I\nSTIMER WAIT FOR JQE UPDATE.\nReason:\nThis message is issued by IN25SPOL when Broadcom Support  requested diagnostic messages. The message indicated\nthat IN25SPOL has issued a STIMER SVC to wait for JQE update to complete.\nAction:\nNone.\nCAIN8050I\nTHERE ARE NO SJQES RETURNED.\nReason:\nThis message is issued by IN25SPOL indicating that IEFSSREQ did not return SJQES information. Message extraction\nwill not be performed.\nAction:\nNone.\nCAIN8060I\nTHERE ARE NO SOUTS RETURNED.\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7496ac168411-1", "text": "CAIN8060I\nTHERE ARE NO SOUTS RETURNED.\nReason:\nThis message is issued by IN25SPOL indicating that IEFSSREQ did not return SOUTS information. Message extraction\nwill not be performed.\n 1773", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "ad8ecf927c5e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nNone.\nCAIN8070I\nUNABLE TO ACCESS JOB QUEUE.\nReason:\nThis message is issued by IN25SPOL indicating that IEFSSREQ was unable to access JES job queue.\nAction:\nNone.\nCAIN8080I\nIN25SS71 LOAD FAILED.\nReason:\nThis message is issued by IN25SPOL indicating that loading of IN25SS71 has failed.\nAction:\nMake sure that the data set containing IN25SS71 is either in the LINKLIST or the STEPLIB concatenation is properly\ndefined.\nCAIN8090I\nIN25SDSB LOAD FAILED.\nReason:\nThis message is issued by IN25SPOL indicating that loading of IN25SDSB has failed.\nAction:\nMake sure that the data set containing IN25SDSB is either in the LINKLIST or the STEPLIB concatenation is properly\ndefined\nCAIN8091I\njjjj IS THE PRIMARY JOB ENTRY SUBSYSTEM. SYSTEM ID FROM JQRYSSID ===> iiii.\nReason:\nThis message is issued by IN25SPOL when Broadcom Support  requested diagnostic messages. This is an informational\nmessage indicating that jjjj is the primary job entry subsystem whose id is iiii.\nAction:\nNone.\nCAIN8092I\ndddddddd IS THE DDN OF jjjjjjjj RETURNED.\nReason:\nThis message is issued by IN25SPOL when Broadcom Support  requested diagnostic messages. This is an informational\nmessage indicating dddddddd is the DD name of jjjjjjjj returned. jjjjjjjj can either be JESMSGLG or JESYSMSG.\nAction:\nNone.\nCAIN8093I\nASSOCIATED DSN: datasetname.\nReason:\n 1774", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "726405eca972-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThis message is issued by IN25SPOL when Broadcom Support  requested diagnostic messages. This is an informational\nmessage indicating that the fully qualified data set name for the DD name cited in message CAIN8092 is datasetname.\nAction:\nNone.\nCAIN8094I\nJOBNAME: jobname JOBID: iiiiiiii\nReason:\nThis message is issued by IN25SPOL when Broadcom Support  requested diagnostic messages. This is an informational\nmessage indicating that the active job name is jobname whose jobid is iiiiiiii.\nAction:\nNone.\nCAIN8095I\nIEFSSREQ TYPE=QUERY FAILED. RETURN CODE= cccc REASON CODE= ssss\nReason:\nThis message is issued by IN25SPOL indicating that IEFSSREQ type of query has failed with a return code of cccc and\nreason code of ssss.\nAction:\nDetermine the cause of failure based on the return code and reason code.\nCAIN8096I\nIEFSSI SUBFUNCTION 80 FAILED. SSOBRETN= rrrr STATREAS= ssss.\nReason:\nThis message is issued by IN25SPOL indicating that IEFSSI subfunction 80 has failed. The subsystem return code is rrrr\nand reason code is ssss. Message extraction will not be performed.\nAction:\nContact Broadcom Support .\nCAIN8097I\nJESMSGLG dddddddd NOT FOUND.\nReason:\nThis message is issued by IN25SPOL indicating that dddddddd token for JESMSGLG is not found.\nAction:\nNone.\nCAIN8098W\nPOSSIBLE CHAINING ERROR. SEE REG 8 FOR DETAILS.\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "726405eca972-1", "text": "POSSIBLE CHAINING ERROR. SEE REG 8 FOR DETAILS.\nReason:\nThis message is issued by IN25SPOL indicating that IN252POL was unable to locate SSVE control blocks via chaining\nthrough various JES control blocks. Message extraction will not be performed. General Purpose Register 8 points to the\nchain.\nAction:\nContact Broadcom Support .\n 1775", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "adecf02484ac-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN8100I\nSPOOL READ FUNCTION CURRENTLY DOES NOT SUPPORT JES3 AT BELOW ZOS 01.11.01 LEVEL.\nReason:\nThis message is issued by IN25SPOL indicating that spool read function does not support JES3 at a level below ZOS\n01.11.01 level. Message extraction will not be performed.\nAction:\nNone.\nCAIN8100I0\nSTARTING MSGLOG00 PROCESS.\nReason:\nThis message is issued by IN25SS71 when Broadcom Support  requests diagnostic messages. This is an informational\nmessage indicating that message extraction of JESMSGLG is being started.\nAction:\nNone.\nCAIN8110I\nSTARTING SYSMSG00 PROCESS.\nReason:\nThis message is issued by IN25SS71 when Broadcom Support  requests diagnostic messages. This is an informational\nmessage indicating that message extraction of JESYSMSG is being started.\nAction:\nNone.\nCAIN8120I\nOBTAINED JCT FROM INSTOR BUFFER\nReason:\nThis message is issued by IN25SS71. It is an informational message indicating that JCT information was obtained from in-\nstorage buffer.\nAction:\nNone.\nCAIN8120I0\nOBTAINED IOT FROM INSTOR BUFFER\nReason:\nThis message is issued by IN25SS71. This is an informational message indicating that IOT information was obtained from\nin-storage buffer.\nAction:\nNone.\nCAIN8130E\nINVALID REQUEST.\nReason:\nThis message is issued by IN25SS71. This is a should not occur error.\nAction:\nContact Broadcom Support .\n 1776", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "24d665a77787-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN8140W\nFAILED TO LOCATE PDDBS FOR BOTH JESMSGLG AND JESYSMSG.\nReason:\nThis message is issued by IN25SS71 indicating that it cannot locate the PDDBs for JESMSGLG and JESYSMSG.\nAction:\nContact Broadcom Support .\nCAIN8150I\nJESMSGLG BUFR IS EMPTY\nReason:\nThis message is issued by IN25SS71 indicating that the JESMSGLG buffer is empty. Message extraction cannot be\nperformed.\nAction:\nNone.\nCAIN8160I\nMSGLOG OBTAINED FROM INSTOR BUFFER\nReason:\nThis message is issued by IN25SS71 when Broadcom Support  requests diagnostic messages. This is an informational\nmessage indicating that JESMSGLG messages were extracted from in-storage buffer.\nAction:\nNone.\nCAIN8170I\nMSGLOG READ FROM LAST TRACK.\nReason:\nThis message is issued by IN25SS71 when Broadcom Support  requests diagnostic messages. This is an informational\nmessage indicating that JESMSGLG messages were extracted from the last track specified in MTTR.\nAction:\nNone.\nCAIN8180I\nMSGLOG RECORD COUNT EXHAUSTED.\nReason:\nThis message is issued by IN25SS71 when Broadcom Support  requests diagnostic messages. This is an informational\nmessage indicating that JESMSGLG messages extraction has exhausted its record count.\nAction:\nNone.\nCAIN8190I\nSYSMSG RECORD COUNT IS ZERO.\nReason:\nThis message is issued by IN25SS71 when Broadcom Support  requests diagnostic messages. This is an informational\nmessage indicating that JESYSMSG record count is zero.\nAction:\nNone.\n 1777", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "df9b0a63b595-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN8200I\nSYSMSG OBTAINED FROM INSTOR BUFFER\nReason:\nThis message is issued by IN25SS71 when Broadcom Support  requests diagnostic messages. This is an informational\nmessage indicating the JESYSMSG information was extracted from in-storage buffer.\nAction:\nNone.\nCAIN8210I\nSYSMSG RECORD COUNT EXHAUSTED.\nReason:\nThis message is issued by IN25SS71 when Broadcom Support  requests diagnostic messages. This is an informational\nmessage indicating that JESYSMSG messages extraction has exhausted its record count.\nAction:\nNone.\nCAIN8230I\nSYSMSG READ FROM LAST TRACK.\nReason:\nThis message is issued by IN25SS71 when Broadcom Support  requests diagnostic messages. This is an informational\nmessage indicating that JESYSMSG messages were extracted from the last track specified in MTTR.\nAction:\nNone.\nCAIN8240E\nSUBSYSTEM FUNCTION 71 SPOOL READ FOR JCT FAILED. RC= rrrr SSOBRETN= cccc SSJIRETN= ssss.\nReason:\nThis message is issued by IN25SS71 indicating that IEFSSREQ subfunction 71 has failed reading the JCT. The return\ncode is rrrr, subsystem reason code is cccc, subsystem return code is ssss. Message extraction is not performed.\nAction:\nContact Broadcom Support  with the error message.\nCAIN8260W\nOUTPUT DCB OPEN FAILED.\nReason:\nThis message is issued by IN25SS71 indicating that open attempt of output DCB for JOBLOG DD statement has failed.\nMessage extraction will not be performed.\nAction:\nDetermine the reason for open failure. DD statement: //JOBLOG DD SYSOUT=* may be missing.\nCAIN8270I", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "df9b0a63b595-1", "text": "CAIN8270I\nNO MORE SYSOUT FROM JES.\nReason:\nThis message is issued by IN25SS71 indicating end of file condition has reached.\nAction:\nNone.\n 1778", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "91720a621fb2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCAIN8300I\nJCT RETREIVAL ERROR.\nReason:\nThis message is issued by IN25SDSB indicating there was an error retrieving job's JCT. Message extraction will not be\nperformed.\nAction:\nNone.\nCAIN8310I\nIOT RETRIEVAL ERROR.\nReason:\nThis message is issued by IN25SDSB indicating there was an error retrieving job's IOT. Message extraction will not be\nperformed.\nAction:\nNone.\nCAIN8320I\nOBTAINED IOT FROM INSTOR BUFFER\nReason:\nThis message is issued by IN25SDSB when Broadcom Support  requests for diagnostic messages. The message\nindicated that job's IOT information was obtained from in-storage buffer.\nAction:\nNone.\nCAIN8330E\nJESMSGLG ALLOCATION FAILED. MSGLOG NOT COLLECTED.\nReason:\nThis message is issued by IN25SDSB indicating that dynamic allocation of JESMSGLG data set name has failed.\nMessage extraction will not be performed.\nAction:\nNone.\nCAIN8340E\nJESYSMSG ALLOCATION FAILED. SYSMSG NOT COLLECTED.\nReason:\nThis message is issued by IN25SDSB indicating dynamic allocation of JESYSMSG data set name has failed. Message\nextraction will not be performed.\nAction:\nNone.\nCAIN8350W\nFAILED TO LOCATE PDDBS FOR BOTH JESMSGLG AND JESYSMSG.\nReason:\nThis message is issued by IN25SDSB indicating that attempts to locate the PDDBs for JESMSGLG and JESYSMSG has\nfailed. Message extraction will not be performed.\nAction:\n 1779", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "95e4bb992a17-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNone.\nCAIN8360I\nSUBSYSTEM FUNCTION 71 SPOOL READ FOR JCT FAILED. RC= rrrr SSOBRETN= ssss SSJIRETN=nnnn\nReason:\nThis message is issued by IN25SDSB indicating that IEFSSREQ subfunction 71 has failed reading the JCT. The return\ncode is rrrr, subsystem reason code is ssss, subsystem return code is nnnn. Message extraction is not performed.\nAction:\nContact Broadcom Support  with this message.\nCAIN8380I\nJESMSGLG ALLOCATED. DDNAME: dddddddd\nReason:\nThis message is issued by IN25SDSB when Broadcom Support  requests for diagnostic messages. The message provides\nthe dynamic allocation returned DDNAME as dddddddd.\nAction:\nNone.\nCAIN8390I\nJESMSGLG DYNAMIC ALLOCATION FAILED. RC/RSN: rrrr/ssss\nReason:\nThis message is issued by IN25SDSB indicating that dynamic allocation of SYSOUT for JESMSGLG has failed. The\ndynamic allocation return code is rrrr, its reason code is ssss. This message is usually followed by IBM IKJ5635 message\nproviding the dynamic allocation text unit that failed. Message extraction will not be performed.\nAction:\nDetermine and correct the cause for the failure, than retry the request.\nCAIN8400W\nINPUT DCB OPEN FAILED.\nReason:\nThis message is issued by IN25SDSB indicating that open of input DCB has failed. The two input data sets involved\nare JESMSGLG and JESYSMSG. When these data sets were allocated successfully, open should not fail. Message\nextraction will not be performed.\nAction:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "95e4bb992a17-1", "text": "extraction will not be performed.\nAction:\nDetermine and correct the cause of the failure, and retry the request.\nCAIN8410I\nINPUT DDNAME: sys E N D O F F I L E\nReason:\nThis message is issued by IN25SDSB indicating the end of file condition for DD named sys has reached.\nAction:\nNone.\nCAIN8410W\nOUTPUT DCB OPEN FAILED.\nReason:\n 1780", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d3a53f961715-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThis message is issued by IN25SDSB indicating that open of JOBLOG SYSOUT has failed.\nAction:\nVerify that //JOBLOG DD SYSOUT=* is defined in the job's JCL.\nSYMP001I\n*INTERTEST VERSION ID: x.x COMPILED: dd mm yy hh:mm:ss *****\nReason:\nInformative. Identifies the version and compile date and time for the InterTest for CICS PL/I postprocessor program,\nIN25SYMP.\nAction:\nNone.\nSYMP002I\nINTERTEST \u2014 PL/I POSTCOMPILER RUN FOR PROGRAM: progname\nReason:\nInformative during initialization of IN25SYMP. Processing for the requested program has begun.\nAction:\nNone.\nSYMP003I\nLISTER RECORDS ADDED TO PROTSYM FILE: nn\nReason:\nInformative during termination of IN25SYMP. The number of records used on the PROTSYM file for listing information\ndisplays.\nAction:\nNone.\nSYMP004I\nSYMBOLIC RECORDS ADDED TO PROTSYM FILE: nn\nReason:\nInformative during termination of IN25SYMP. The number of records used on the PROTSYM file for symbolic information\ndisplays.\nAction:\nNone.\nSYMP005I\nIN25ASMP RETURN CODE ON FINAL PROCESSING: nn\nReason:\nInformative. The final return code from routine IN25ASMP displays.\nAction:\nNone.\nSYMP006I\nIN25SYMP RETURN CODE ON FINAL PROCESSING: nn\nReason:\nInformative. The final return code from routine IN25SYMP displays.\n 1781", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "91d0703c46e3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nNone.\nSYMP101W\nBLOCK NAME CANNOT BE RESOLVED. VARIABLE AND PARAMETER RESOLUTION MAY BE AFFECTEDDRC=n\nBLOCK NAME= blockname\nReason:\nA variable was found in the Variable Storage Map section of the compiler output whose associated block cannot be\nidentified.\nAction:\nContact Broadcom Support  with program listings.\nSYMP102W\nVARIABLE DISPLACEMENT CANNOT BE DETERMINED.DRC=n, VARIABLE NAME= variable name\nReason:\nA variable was found in the Variable Storage Map section of the compiler output whose associated attributes could not be\nidentified.\nAction:\nEnsure that all data names are unique within each block.\nSYMP103W\nPARAMETER DISPLACEMENT CANNOT BE DETERMINED.DRC=n, PARAMETER NAME= parameter name\nReason:\nA parameter passed to a procedure could not be resolved and will not be available to the CORE transaction, or an\nassociated block could not be determined.\nAction:\nEnsure that all data names are unique within each block and that no procedure or entry statements are suppressed by\n%NOPRINT. Check for other error messages.\nSYMP104W\nBASED/DEFINED VAR PTR/BASE CANNOT BE FOUND.DRC=n, VARIABLE NAME= variable name POINTER NAME\n= pointer name\nReason:\nThe pointer associated with a BASED variable or the \"base\" variable of a \"redefined\" variable (see message SYMP115W)\ncould not be resolved. The \"pointer\" name can be either the name of the associated pointer or the \"base\" area for the\nredefinition.\nAction:\nTry simplifying the expression of the base area. For example, use the following syntax to declare a \"redefined\" variable:\n...BASED( ADDR( variable) )\nor", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "91d0703c46e3-1", "text": "...BASED( ADDR( variable) )\nor\n...DEFINED base_variable...\nAlso, ensure that the variable does not refer either to a subscripted array element or qualified name.\nSYMP105W\nADDRESSES OF THE FOLLOWING BASED VARIABLES CANNOT BE DETERMINED FROM THE PL/I CROSS\nREFERENCE. IN ORDER TO ACCESS THESE VARIABLES ONLINE, YOU MUST SPECIFY A QUALIFIED NAME IN\nTHE INTERTEST CORE COMMAND.   list of variable names\n 1782", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "91ee6e376f23-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nOne or more BASED (*) variables were found in the PL/I Cross Reference. IN25SYMP was unable to determine the\npointer to the variables specified.\nAction:\nInformational only. When attempting to view the variable online, you must use the POINTER option in the CORE\ncommand. For more information, see the section CORE Commands for PL/I Symbolic Programs in Accessing Main\nStorage CORE.\nSYMP106W\nADDRESSES OF THE BASED STRUCTURES CONTAINING THE FOLLOWING VARIABLES COULD NOT BE\nDETERMINED. IN ORDER TO ACCESS THESE VARIABLES ONLINE, YOU MUST SPECIFY A QUALIFIED NAME IN\nTHE INTERTEST CORE COMMAND.   list  of variable names\nReason:\nA SYMP105W message was issued for the major structure containing the variable name(s).\nAction:\nInformational only. When attempting to view the variable online, you must use the POINTER option in the CORE\ncommand. For more information, see the section CORE Commands for PL/I Symbolic Programs in Accessing Main\nStorage CORE.\nSYMP107W\nTHE FOLLOWING PL/I COMPILER OPTION IS REQUIRED IN ORDER FOR IN25SYMP TO PROCESS CORRECTLY\ncompiler option.\nReason:\nThe listed PL/I compiler option was not specified.\nAction:\nEnsure that the following options were specified to the PL/I compiler:\nAGGREGATE OPTIONS\nATTRIBUTES(FULL) SOURCE\nMAP STATEMENT (or GOSTMT)\nNEST STORAGE\nOFFSET XREF(FULL)\nIf all of the previous options were not specified, code the appropriate option(s) and rerun the job.\nIf all of the above options were specified, ensure that the options section is included in the PL/I compiler listing and that", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "91ee6e376f23-1", "text": "the output of the compiler was directed to the INPUTT DD statement, or that the compiler terminated with a return code of\n8 or less.\nSYMP108W\nWARNING: \"%NOPRINT\" OPTION SPECIFIED. ****\nNOTE\nIndiscriminate use of this option could cause program failure or incorrect results.\nReason:\nThe NOPRINT option was specified on the control card. This option suppresses checking for the occurrence of the\npreprocessor control statement \"%NOPRINT\". If the use of this facility suppresses the listing of PROCEDURE or ENTRY\nstatements that contain parameter lists, or suppresses the listing of the final END statement of the program, the results\nmay be unpredictable. Possible effects include the inability to resolve parameter variables properly as well as possible\nabnormal termination of SYMP.\nAction:\nRemove the NOPRINT option or ensure that the required information is not suppressed.\n 1783", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6ad148c5db78-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSYMP110W\nSTRUCTURE NAME \"IN\" ENCOUNTERED WHILE SCANNING CROSS REFERENCE/ATTRIBUTE LISTVARIABLE:\nvariable name STATEMENT NO: statement number\nReason:\nWhile resolving structure nesting information, the identified variable in the specified statement number was found in a\nmajor or minor structure named \"IN\". If this is not true, the variable may not be properly resolved.\nAction:\nNone, if the previous condition described is correct. Otherwise, call Broadcom Support .\nSYMP111W\nUNABLE TO DETERMINE LENGTH OF DATA ITEM. \"REFER\" OPTION NOT SUPPORTED FOR BASED\nVARIABLES.VARIABLE: variable name STATEMENT NO: statement number\nReason:\nDynamically sized items are not supported. Examples of such include string parameters that inherit their size from the\ncalling block, automatic strings whose length is an expression, and based strings whose length is specified by the REFER\noption. Such variables may not be available to the CORE transaction when debugging.\nAction:\nNone.\nSYMP112W\nUNEXPECTED CONVERSION ERROR WHILE PROCESSING THE CROSS REFERENCE/ATTRIBUTE LIST\nFOR:VARIABLE: variable name STATEMENT NO: statement number\nReason:\nAn unanticipated error occurred during processing of the attribute list.\nAction:\nCall Broadcom Support .\nSYMP113W\nLABEL DISPLACEMENT CANNOT BE DETERMINED FOR: xxxxxxxx\nReason:\nThe indicated label could not be associated with its block.\nAction:\nEnsure that the label names are unique. Check the statement/offset table for missing or outoforder entries. Do not use\nEND block_name statements to close multiple blocks.\nSYMP114W\nNO STORAGE WILL BE ALLOCATED FOR THE FOLLOWING UNREFERENCED VARIABLES. THE VARIABLES\nCANNOT BE ACCESSED.\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6ad148c5db78-1", "text": "CANNOT BE ACCESSED.\nReason:\nThe flagged variables within the PL/I program were unreferenced.\nAction:\nInformational only. The flagged variables cannot be viewed online.\nSYMP115W\nTHE FOLLOWING LINE CONTAINS \"%NOPRINT\" WHICH COULD PREVENT PROPER RESOLUTION OF SOME\nVARIABLES.  input  compiler record\n 1784", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "369e233499d4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nUse of the compiler option %NOPRINT may cause the suppression of information needed to resolve variables properly.\nAction:\nEnsure that %NOPRINT does not suppress the printing of:\n\u2022\n\u2022PROCEDURE or ENTRY statements containing parameter lists.\n\u2022\n\u2022Declarations of redefined variables using expressions such as\n\u2022\n...BASED( ADDR( variable ) )\nor\n...DEFINED base_variable...\nSYMP116W\nTHE FOLLOWING \"DEFINED\" STRUCTURE IS NESTED TOO DEEPLY TO PROPERLY RESOLVE ITS LENGTH:\nstructure\nReason:\nWhen a CORE command displays the specified structure, the area displayed is correct but is not be limited to the correct\nlength. This error occurs only with a structure nesting depth that exceeds 16, which is not currently allowed by any version\nof the PL/I compiler.\nAction:\nNone.\nSYMP117W\nLENGTH OF DEFINED STRUCTURE \"structure\" CANNOT BE RESOLVED DUE TO CONTAINED ARRAY \"array\"\nReason:\nWhen a CORE command displays the specified DEFINED structure containing an array or a substructure that contains\nan array, the area displayed is correct but it is limited to the correct length. This error occurs only with a structure nesting\ndepth that exceeds 16, which is not currently allowed by any version of the PL/I compiler.\nAction:\nNone.\nSYMP118W\nVARIABLE \"element name\" IS A DUPLICATE NAME WITHIN A STRUCTURE.STRUCTURE, \"structure name\", IS\nDECLARED IN STATEMENT statement numberDRC = n.\nReason:\nA duplicate name was found in a structure. All names must be unique within a major structure. If not, the following\nproblems can occur:\n 1785", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4d644afc4d24-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n\u2022\n\u2022Selection of an incorrect variable\n\u2022\n\u2022Incorrect attributes for a variable\n\u2022\n\u2022Incorrect resolution of parameters\n\u2022\n\u2022System errors not apparently related to these variables\n\u2022\nAction:\nAssign unique names.\nSYMP119W\nNO AUTOMATIC VARIABLES FOUND FOR PROCEDURE procnamePARAMETER parameter CANNOT BE\nRESOLVEDDRC = n.\nReason:\nNo AUTOMATIC variables were declared for the specified procedure. Parameters cannot be resolved for any PL/I\nprocedure unless AUTOMATIC variables are declared in it.\nAction:\nYou can circumvent this restriction by declaring an AUTOMATIC variable. This variable does not have to be referenced.\nSYMP120W\nSTRUCTURE INFORMATION FOR: variablename IS INVALID. SPECIFY CONNECT ATTRIBUTE, OTHERWISE\nONLINE STRUCTURE REQUEST WILL SHOW INVALID INFORMATION. STATEMENT #: nnn\nReason:\nThe CONNECT attribute is missing from the named variable, found in the specified statement number. When the\nCONNECT attribute is missing, InterTest for CICS and SymDump  for CICS cannot display a valid structured CORE\ndisplay.\nAction:\nRedefine the variable with the CONNECT attribute to obtain a structured CORE main storage display.\nSYMP121W\nCOMPILER EXTERNAL SYMBOL DICTIONARY NOT AVAILABLE. ADDRESSES OF THE FOLLOWING\nCONTROLLED VARIABLES CANNOT BE DETERMINED.\nList of variable names\nReason:\nThe External Symbol Dictionary is not in the compiler listings. As a result it is not possible to determine the address of\ncontrolled variables. Therefore they cannot be displayed.\nAction:\nInformational only. If you desire to display controlled variables, recompile with the ESD option.\nSYMP122W\nTHE FOLLOWING VARIABLES CAN ONLY BE ACCESSED THROUGH CA INTERTEST BATCH.\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4d644afc4d24-1", "text": "THE FOLLOWING VARIABLES CAN ONLY BE ACCESSED THROUGH CA INTERTEST BATCH.\nReason:\nThe flagged variables within the PL/I program are not supported.\nAction :\nInformational only. The flagged variables cannot be viewed online.\n 1786", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b7e021e10ccc-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSYMP123W\nTHE FOLLOWING EXTERNAL VARIABLES CANNOT BE ACCESSED THROUGH CA INTERTEST BATCH DUE TO\nTHE RENT OPTION.\nReason:\nThe flagged variables within the PL/I program are not supported.\nAction:\nInformational only. The flagged variables cannot be viewed with the use of the RENT option.\nSYMP124W\nTHE POINTER FOR A BASED(ADDR VARIABLE CAN NOT HAVE MORE THAN 3 SUBSCRIPTS.\nReason:\nLimit of 3 subscripts for the pointer.\nExample:\nDCL 1 ABC BASED(ADDR(BCD(1,2,3,4)))\nAction:\nNone.\nSYMP125W\nCURRENTLY, THE FOLLOWING VARIABLES CAN NOT BE PROPERLY DISPLAYED BY INTERTEST/CICS and\nINTERTEST BATCH.\nList of variables\nReason:\nInterTest for CICS and InterTest Batch cannot support variables with BASED ADDRESS variables with subscripts.\nAction:\nInformational only. These variables cannot be displayed.\nSYMP126W\nTHE FOLLOWING VARIABLES RESIDE WITHIN AN UNNAMED STRUCTURE AND MAY NOT BE QUALIFIED\nList of variables\nReason:\nThe indicated variables are defined within a structure that was defined with a name of ' '. Since the variable name ' '\ncannot be referenced, the structure name cannot be used as qualifier.\nAction:\nInformational only. If the variable names indicated are not unique, the variables may not be displayable by the Broadcom\nApplication Quality and Testing Tools.\nSYMP182W\nUNABLE TO OBTAIN TIMESTAMP INFORMATION FROM LISTING, CURRENT DATE/TIME WILL BE\nUSED.PARAMETER parameter  CANNOT BE RESOLVEDDRC = n.\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b7e021e10ccc-1", "text": "USED.PARAMETER parameter  CANNOT BE RESOLVEDDRC = n.\nReason:\nThe compiler generated times stamp cannot be found in the //SYSPRINT listing used as input. This may occur because\nSymDump  for CICS failed to find the date/time record. The date and time of the postprocessor's execution is used in lieu\nof the compiler timestamp.\nAction:\nContact Broadcom Support .\n 1787", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f868297fec64-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNote:  For messages SYMP500 to SYMP599: You are advised to contact Broadcom Support . Provide the message\nnumber, text, and DRC code (if available). Also provide the IN25SYMP version ID and compile date and time (see\nmessage SYMP001I) and the release number of the PL/I compiler you are using.\nSYMP500E\nERROR SCANNING SOURCE FOR COMMENTS/LITERALS STATEMENT NUMBER:statement number COMMENT/\nLITERAL SCAN FLAGS: xxxxxxxx\nReason:\nAn error occurred while scanning for comments and literals. If comments or literals contain text that resembles either a\nPROCEDURE or ENTRY statement with parameters, some parameter variables may not be properly resolved.\nAction:\nEnsure that comments and literals do not contain text as previously described. Check message SYMP103W. Call\nBroadcom Support  if this error occurs.\nSYMP501E\nUNABLE TO DETERMINE BEGINNING STATEMENT NUMBER FOR BLOCK. ANY VARIABLES DECLARED\nIN THIS BLOCK PRIOR TO THE INDICATED STATEMENT NUMBER WILL NOT BE RESOLVED. xxxxxxxx AT\nSTATEMENT:statement number\nReason:\nAn error occurred while identifying the beginning statement number for a block. Variables declared between the beginning\nof the block and the statement number may not be properly resolved.\nAction:\nPlace an executable statement before the first variable declaration in this block. Call Broadcom Support  if this error\noccurs.\nSYMP502E\nEXPECTED \"IN...\" NOT FOUND WHILE SCANNING CROSS REFERENCE/ATTRIBUTE LISTVARIABLE variable\nSTATEMENT NO: statement number\nReason:\nAn error occurred while resolving structure nesting. Structure elements may not be properly resolved.\nAction:\nCall Broadcom Support .\nSYMP503E", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f868297fec64-1", "text": "Action:\nCall Broadcom Support .\nSYMP503E\nWARNING \u2014 THE FOLLOWING LINE ASSUMED TO BE PART OF COMPILER INFORMATORY MESSAGE AND\nIGNORED:   input compiler  recordDRC = n.\nReason:\nThe specified compiler input record was ignored.\nAction:\nCall Broadcom Support .\nSYMP503E0\nWARNING \u2014 THE FOLLOWING LINE ASSUMED TO BE A REPETITION OF VARIABLE MAP COLUMN HEADINGS: \ninput compiler  recordDRC = n.\nReason:\nThe specified compiler input record was assumed to repeat variable map column headings.\nAction:\n 1788", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "841beb2745c2-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCall Broadcom Support .\nSYMP503E1\nWARNING \u2014 THE FOLLOWING LINE ASSUMED TO IDENTIFY COMPILER DIAGNOSTIC MESSAGES SECTION: \ninput compiler  recordDRC = n.\nReason:\nThe specified compiler input record was assumed to identify the compiler's diagnostic messages section.\nAction:\nCall Broadcom Support .\nSYMP503E2\nWARNING \u2014 THE FOLLOWING LINE CONTAINS TITLE IN UNEXPECTED POSITION \u2014 ASSUMED TO LIST\nSTATEMENT OFFSETS:  input compiler  recordDRC = n.\nReason:\nThe specified compiler input record contains a title in an unexpected position. This line is assumed to list statement\noffsets.\nAction:\nCall Broadcom Support .\nSYMP503E3\nWARNING \u2014 THE FOLLOWING LINE CONTAINS UNEXPECTED DECIMAL OFFSET \u2014 HEX VALUE WILL BE USED:\ninput compiler  recordDRC = n.\nReason:\nThe specified compiler input record contains a decimal offset. The hexadecimal value is used instead.\nAction:\nCall Broadcom Support .\nSYMP504E\nUNEXPECTED STRUCTURE NESTING DEPTH OF n EXCEEDS PREVIOUS COMPILER LIMIT IN STATEMENT\nstatement number\nReason:\nThe nesting depth exceeds the limit in the specified compiler statement.\nAction:\nCall Broadcom Support .\nSYMP505E\nBLOCK NOT FOUND FOR VARIABLE variable, DECLARED IN STATEMENT NO. nn\nReason:\nThe block for the specified variable could not be found.\nAction:\nCall Broadcom Support .\nSYMP507E\nSTATEMENT OUT OF EXPECTED RANGE FOR BLOCK block name\nReason:\nThe statement was out of the expected range for the specified block.\n 1789", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4a3a95d1a457-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nCall Broadcom Support .\nSYMP508E\nSEARCH FAILED FOR: variableDRC = n\nReason:\nThe specified variable could not be found.\nAction:\nCall Technical Support.\nSYMP509E\nINCLUDE OF USER FILES THROUGH INTEGRATED PREPROCESSOR NOT SUPPORTED. USE SEPARATE\nPREPROCESSOR STEP\nReason:\nThe integrated INCLUDE and MACRO preprocessors of PL/I for z/OS are not supported. If you are using the integrated\nSQL preprocessor, programs that contain EXEC SQL INCLUDE statements for user-defined members still require a\nseparate preprocessor step. (EXEC SQL INCLUDE statements for SQLCA and SQLDA are supported when using the\nintegrated SQL preprocessor.)\nAction:\nUse a separate preprocessor step to incorporate external files into your program.\nSYMP599E\nUNEXPECTED CHAR IN MARGIN DELIMITER POSITIONM, L, MACRO, MRGCHR: aaa, bbb, ccc, dddDRC = n.\nReason:\nAn unexpected character was found in the margin delimiter position.\nAction:\nCall Broadcom Support  and provide the information in the message.\nSYMP599E0\n\"aaaa\" POSITIONED AT BLANKSTRING: \"portion of listing line\"DRC = n.\nReason:\naaaa was positioned at a blank.\nAction:\nCall Broadcom Support  and provide the information in the message.\nSYMP599E1\n\"IN\" FOUND AT INVALID LOCATIONSTRING: \"portion of listing line\"DRC = n.\nReason:\nAn IN structure was found at an invalid location.\nAction:\nCall Broadcom Support  and provide the information in the message.\nSYMP599E2\nVARIABLE \"variable\", DECLARED IN STATEMENT statement number, IS ALREADY RESOLVEDDRC = n.\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "4a3a95d1a457-1", "text": "Reason:\nThe specified variable is already resolved.\n 1790", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e172b0b7a85d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nCall Broadcom Support  and provide the information in the message.\nSYMP599E3\nAGGREGATE NAME NOT MATCHED  aggregate name DRC = n.\nReason:\nThe specified aggregate name was not found.\nAction:\nCall Broadcom Support  and provide the information in the message.\nSYMP599E4\nFORWARD SCAN FAILED TO RESOLVE BLOCKOUTERMOST BLOCK ASSUMEDDRC = n.\nReason:\nThe block could not be resolved. The outermost block is assumed.\nAction:\nCall Broadcom Support  and provide the information in the message.\nSYMP599E5\nSTRUCTURE PROCESSING ERROR variable name\nReason:\nAn error has occurred in recording a variables structure position while processing the aggregate table.\nAction:\nThis can occur if the PL/I compile abnormally terminates or terminates with a return code greater than eight. Check these\nconditions and if they occur, correct them and rerun the job. If neither has occurred, contact Broadcom Support  with the\ncomplete job output.\nSYMP599E6\nSTORAGE DESCRIPTOR NAME NOT MATCHED variable name\nReason:\nA variable name in the storage offset table could not be matched.\nAction:\nThis can occur if the PL/I compile abnormally terminates or terminates with a return code greater than eight. Check these\nconditions and if they occur, correct them and rerun the job. If neither has occurred, contact Broadcom Support  with the\ncomplete job output.\nSYMP801E\nnn STATEMENTS ENCOUNTERED; PROGRAMS WITH MORE THAN 10,000 STATEMENTS NOT\nSUPPORTED.RESULTS WILL BE UNPREDICTABLE, WITH SEVERE ERRORS LIKELY.\nReason:\nBecause of a bug in the PL/I compiler that truncates high order digits from statement numbers in the statement/offset", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "e172b0b7a85d-1", "text": "table, programs with over 9,999 statements cannot be supported completely. This message is usually accompanied by\nother error messages. Online debugging is affected significantly.\nAction:\nNone.\n 1791", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3efd9b88f784-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSYMP901S\nTHE PL/I COMPILER OPTIONS LISTED ABOVE WERE NOT SPECIFIED AND HAVE CAUSED IN25SYMP TO\nTERMINATE\nReason:\nOne or more SYMP107W message(s) were issued.\nAction:\nEnsure that the following options were specified to the PL/I compiler:\nAGGREGATE\nOPTIONS\nATTRIBUTES(FULL)\nSOURCE\nMAP\nSTATEMENT (or GOSTMT)\nNEST\nSTORAGE\nOFFSET\nXREF(FULL)\nSee the SYMP107W messages for the specific options missing.\nIf all options were not specified, code the appropriate options and rerun the job.\nIf all of the above options have been specified, ensure that the options section is included in the PL/I compiler listing and\nthat the output of the compiler was directed to the INPUTT DD statement, or that the compiler terminated with a return\ncode of 8 or less.\nSYMP902S\nUNEXPECTED TERMINATION OF COMPILER OUTPUT HAS OCCURREDDRC = n.\nReason:\nWhile scanning the PL/I compiler output, an endoffile condition was raised for the INPUTT DD statement.\nAction:\nCheck that all the PL/I options required by IN25SYMP were set, or that the compiler terminated with a return code of 8 or\nless. Correct the problem and rerun the compile and IN25SYMP.\nSYMP903S\nUNEXPECTED ERROR DETECTED. ERROR CORE=nnnnDRC = n.\nReason:\nA PL/I error condition occurred that IN25SYMP was not designed to handle.\nAction:\nCheck the PL/I ONCODEs and take the appropriate suggested action. If unsuccessful, contact Broadcom Support  with the\ndump.\nSYMP904S\nIN25ASMP FUNCTION FAILED. FUNCTION CODE= n DRC = n.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3efd9b88f784-1", "text": "IN25ASMP FUNCTION FAILED. FUNCTION CODE= n DRC = n.\nReason:\nThe routine that does I/O to the PROTSYM file returned with a nonzero return code.\nAction:\nCheck the error messages from IN25ASMP and take appropriate action, and then rerun the job. This error normally\nindicates a problem with the PROTSYM file. If this is the first use of the PROTSYM file, check the job that initialized\nthe file for normal completion. If this is not the first use of the file, check for a physical or logical error on the file. The\nMESSAGE DD statement contains more information.\n 1792", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "20d4b25f10ca-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNOTE\nFunction code 8 usually means the file is full.\nSYMP905S\nERROR ENCOUNTERED ON FILE INPUTT, ERROR CODE = nnnnDRC = n.\nReason:\nAn error has occurred trying to open the INPUTT file.\nAction:\nEnsure that the ddNAME/DLBL INPUTT points to a file that contains the output listing of the PL/I compiler.\nSYMP906S\nERROR ENCOUNTERED ON FILE SYSPRINT, ERROR CODE = nnnnDRC = n.\nReason:\nAn error has occurred attempting to open the SYSPRINT file.\nAction:\nEnsure that the ddNAME/DLBL SYSPRINT is coded in your JCL.\nSYMP908S\nSUBSCRIPT OVERFLOW IN TABLE T4DRC = n.\nReason:\nThe internal table used to keep track of variable information has exceeded its limits.\nAction:\nThis error is usually caused when the Attribute and Cross Reference section of the compile output could not be found by\nIN25SYMP.\nThis can occur if the compiler options ATTRIBUTE(FULL) and XREF(FULL) were not specified, or if the PL/I compile\nabnormally terminates or terminates with a return code greater than 8. Check for these conditions and if they occur,\ncorrect and rerun the job. If neither has occurred, contact Broadcom Support  with the dump.\nSYMP909S\nSUBSCRIPT OVERFLOW IN TABLE T5DRC = n.\nReason:\nThe internal table used to keep track of PROC BLOCKS has exceeded its limits.\nAction:\nThis error is usually caused when the Storage Requirements section of the compile output could not be found by\nIN25SYMP. This can occur if the compiler option STORAGE was not specified, or if the PL/I compile has abnormally", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "20d4b25f10ca-1", "text": "terminated or terminated with a return code greater than 8. Check for these conditions and if they occur, correct and rerun\nthe job. If neither has occurred, contact Broadcom Support  with the dump.\nSYMP910S\nSUBSCRIPT OVERFLOW IN TABLE T6DRC = n.\nReason:\nAn internal table used to keep track of information about statements has overflowed.\nAction:\nThis occurs under several conditions. If reorder has been specified in the procedure block, remove the reorder option.\nThis may also occur if a large number of source statement lines contain multiple PL/I statements (such as, A=B; C = D; E\n= F;). In this case, separate the PL/I statements into multiple source lines.\n 1793", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6e59c60094fb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThis can also occur if the PL/I preprocessor command %NOPRINT was specified. In this case, remove the %NOPRINT\ncommand.\nSYMP911S\nSUBSCRIPT OVERFLOW IN TABLE T6ADRC = n.\nReason:\nAn internal table used to keep track of information about statements has overflowed.\nAction:\nThis occurs under several conditions. If reorder has been specified in the procedure block, remove the reorder option.\nThis may also occur if a large number of source statement lines contain multiple PL/I statements (e.g., A=B; C = D; E =\nF;). In this case, separate the PL/I statements into multiple source lines.\nThis can also occur if the PL/I preprocessor command %NOPRINT was specified. In this case, remove the %NOPRINT\ncommand.\n \nSYMP912S\nINPUT FROM THE PL/I COMPILER CONTAINS AN INVALID STATEMENT NUMBER IN COLUMNS 18 OF THE\nRECORD.  input compiler  record\nTHE ABOVE INPUT RECORD HAS CAUSED THE TERMINATION OF THE COMPILER OUTPUT PRESCAN\nReason:\nAn error was detected while attempting to find the largest PL/I statement number.\nAction:\nCheck compiler output and the line listed. Correct the problem and rerun the job.\nSYMP916S\nUNEXPECTED ERROR ENCOUNTERED DURING PHASE 1DRC = n.\nReason:\nAn error has occurred during Phase 1 of IN25SYMP processing.\nAction:\nCheck the Job Log for operating system or PL/I error indicators. Correct and rerun the job.\nSYMP917S\nDOS INITIALIZATION FAILED IN \"ASMP\"; POSTPROCESSOR SYMP WILL BE TERMINATED DRC = n.\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6e59c60094fb-1", "text": "Reason:\nFor VSE only. Probably, a control card is either missing or invalid. Or, there may be a problem with the Symbolic File or\nwith the JCL for the \"MESSAGE\" file.\nAction:\nCorrect the control card, Symbolic File, or JCL.\nSYMP919S\nEND OF FILE ENCOUNTERED FOR \"INPUTT\" DURING PHASE 1 OF PREPROCESSORDRC = n.\nReason:\nAn ENDOFFILE condition occurred during the Phase 1 scan of the PL/I compiler output.\nAction:\nIN25SYMP prints the compiler output and terminates processing. This condition can occur when the PL/I compiler detects\nprogram errors that would prohibit successful compilation. Refer to the PL/I compiler output for error messages.\n 1794", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c0f0b3caed52-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSYMP920S\n\"CDLOAD\" FAILED FOR \"IN25ASMP\". RETURN CODE = nnnn\nReason:\nVSE only. The VSAM I/O routine, IN25ASMP, could not be dynamically loaded. Possible causes include incorrect\ninstallation or partition/JCL that does not allow sufficient storage for loading this phase.\nAction:\nCheck that the specified phase is in the execution phase library and that there is adequate storage.\nSYMP921S\nPOWER SPOOL RETRIEVAL FAILURE: ATTEMPT NUMBER: request\nReason:\nFor VSE/POWER only. A POWER spool retrieval failed. This message identifies the request. If only one job gets this error,\nthe JCL for the job is probably incorrect. If all jobs get this error, InterTest for CICS may not have been properly installed\nand customized.\nAction:\nCheck the JCL and, if necessary, InterTest for CICS installation and customization.\nSYMP922S\nINCOMPLETE COMPILER OUTPUT DUE TO ERRORS HAS CAUSED TERMINATION OF IN25SYMP OPTION\nCAUSING PL/I COMPILER TERMINATION WAS: option\nReason:\nThe PL/I compiler options NOSYNTAX and NOCOMPILE can prevent the normal completion of the compilation process,\neither conditionally, depending on the severity of the errors, or unconditionally. The InterTest for CICS PL/I postprocessor\nprogram, IN25SYMP, terminates immediately when it recognizes an aborted compilation.\nAction:\nUsually, correction of compilation errors resolves this problem.\nSYMP923S\nTABLE SIZE EXCEEDS HALFWORD LIMIT FOR: name\nReason:\nAn internal table has exceeded the limit of the halfword index. The postprocessor program terminated to prevent\nsubsequent errors. This situation should not occur for programs with significantly less than 32,767 statements. Because", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c0f0b3caed52-1", "text": "support is limited to programs with less than 10,000 statements, this situation is unlikely to occur.\nAction:\nCall Broadcom Support  and provide the information in the message.\nSYMP924S\nSUBSCRIPT OVERFLOW IN TABLE T7\nReason:\nThe internal table used to keep track of variable displacements has exceeded its limits.\nAction:\nThis can occur if the PL/I compile abnormally terminates or terminates with a return code greater than eight. Check these\nconditions and if they occur, correct them and rerun the job. If neither has occurred, contact Broadcom Support  with the\ncomplete job output.\n 1795", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5cc1599159f6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSYMP925S\nSUBSCRIPT OVERFLOW IN TABLE T10\nReason:\nThe internal table used to keep track of the pseudo register information for controlled variables has exceeded its limits.\nAction:\nThis error is usually caused when the Attribute and Cross Reference section of the compile output could not be found by\nIN25SYMP.\nThis can occur if the compiler options ATTRIBUTE(FULL) and XREF(FULL) were not specified, or the if PL/I compile\nabnormally terminated or terminates with a return code greater than eight. Check these conditions and if they occur,\ncorrect and rerun the job. If neither has occurred, contact Broadcom Support  with the complete job output.\nSYMP926S\nSUBSCRIPT OVERFLOW IN TABLE T11\nReason:\nThe internal table used to keep track of external symbol dictionary entries has exceeded its limits.\nAction:\nThis can occur if the compiler option ESD was not specified, or the PL/I compiler abnormally terminated or terminates\nwith a return code greater than eight. Check these conditions and if they occur, correct and rerun. If neither has occurred,\ncontact Broadcom Support  with the complete job output.\nSYMP999S\nUNEXPECTED ERROR CODE. nnn PROCESSING TERMINATED\nReason:\nAn undocumented error code has forced termination of IN25SYMP.\nAction:\nContact Broadcom Support .\nError Codes\nThis section explains the error codes generated by InterTest for CICS and SymDump  for CICS.\nWD00\nReason:\nCAIRIM was not active when the #RIMSTAT macro was invoked.\nAction:\nEnsure that CAIRIM is installed and active before starting InterTest for CICS.\nWD01\nReason:\nReserved\nAction:\nNone, this is an informational message.\nWD02\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5cc1599159f6-1", "text": "Reserved\nAction:\nNone, this is an informational message.\nWD02\nReason:\nThe TWA size for the transaction ICDB is less than 1536.\n 1796", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "df301c4af082-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAction:\nIncrease the TWA size for the ICDB transaction to 1536 or more.\nWD03\nReason:\nReserved\nAction:\nNone, this is an informational message.\nWD09\nReason:\nInterTest for CICS communication failure.\nAction:\nEnsure that the workstation GUI interface was not disconnected from the CICS region. If the GUI was not disconnected\nthen activate the CICS auxiliary trace. Then issue the InterTest for CICS CNTL=ITTRACE_ON command and the\nICDB TRACE_ON command. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the\ntransaction dump, and any relevant messages sent to the terminal or the systems console. For assistance, contact\nBroadcom Support .\nWD12\nReason:\nAn internal error; TCP/IP send failure.\nAction:\nEnsure that the workstation GUI interface was not disconnected from the CICS region. If the GUI was not disconnected\nthen activate the CICS auxiliary trace. Then issue the InterTest for CICS CNTL =ITTRACE,ON command and the\nICDB TRACE_ON command. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the\ntransaction dump, and any relevant messages sent to the terminal or the systems console. For assistance, contact\nBroadcom Support .\nWD13\nReason:\nAn internal TCP/IP receive failure occurred.\nAction:\nEnsure that the workstation GUI interface was not disconnected from the CICS region. If the GUI was not disconnected\nthen activate the CICS auxiliary trace. Then issue the InterTest for CICS CNTL=ITTRACE_ON command and the\nICDB TRACE_ON command. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the\ntransaction dump, and any relevant messages sent to the terminal or the systems console. For assistance, contact", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "df301c4af082-1", "text": "transaction dump, and any relevant messages sent to the terminal or the systems console. For assistance, contact\nBroadcom Support .\nWD14\nReason:\nCould not load the InterTest for CICS IN25CUI9 message block module.\nAction:\nEnsure that the InterTest for CICS load module library in the CICS DFHRPL contains IN25CUI9. If the load module library\ncontains IN25CUI9, activate the CICS auxiliary trace. Retry the sequence of events that caused the error. Then collect the\nauxiliary trace, the transaction dump, and any relevant messages sent to the terminal. For assistance, contact Broadcom\nSupport .\n 1797", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "59e0fd37d64d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nWD15\nReason:\nCould not load the InterTest for CICS IN25PGM2 module.\nAction:\nEnsure that InterTest for CICS has been successfully started. If InterTest for CICS was successfully started, then\nactivate the CICS auxiliary trace. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the\ntransaction dump, and any relevant messages sent to the terminal. For assistance, contact Broadcom Support .\nWD16\nReason:\nCould not locate the InterTest for CICS PROM table.\nAction:\nEnsure that InterTest for CICS has been successfully started. If InterTest for CICS were successfully started, then\nactivate the CICS auxiliary trace. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the\ntransaction dump, and any relevant messages sent to the terminal. For assistance, contact Broadcom Support .\nWD17\nReason:\nCould not locate the InterTest for CICS PROM table appendix.\nAction:\nEnsure that InterTest for CICS has been successfully started. If InterTest for CICS was successfully started, then\nactivate the CICS auxiliary trace. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the\ntransaction dump, and any relevant messages sent to the terminal. For assistance, contact Broadcom Support .\nWD18\nReason:\nInterTest for CICS debugger internal logic error; unknown TWA function request.\nAction:\nEnsure that InterTest for CICS has been successfully started. If InterTest for CICS was successfully started, then\nactivate the CICS auxiliary trace. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the\ntransaction dump, and any relevant messages sent to the terminal. For assistance, contact Broadcom Support .\nWD22\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "59e0fd37d64d-1", "text": "WD22\nReason:\nThe ICDB transaction was not initiated by the graphical user interface PC user.\nAction:\nEnsure that ICDB transaction was started by the InterTest for CICS PC user. Otherwise, activate the CICS auxiliary trace.\nThen issue the InterTest for CICS CNTL=ITTRACE_ON and the ICDB TRACE_ON commands. Retry the sequence of\nevents that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to\nthe terminal or the systems console. For assistance, contact Broadcom Support .\nWD34\nReason:\nInterTest for CICS internal logic error; no message block.\nAction:\n 1798", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "41d9473e1ddb-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nIssue the InterTest for CICS CNTL=ITTRACE_ON command and the ICDB TRACE_ON command. Retry the sequence\nof events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to\nthe terminal. For assistance, contact Broadcom Support .\nWD45\nReason:\nInterTest for CICS internal logic error; invalid TWA user function request.\nAction:\nEnsure that InterTest for CICS has been successfully started. If InterTest for CICS were successfully started, then\nactivate the CICS auxiliary trace. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the\ntransaction dump, and any relevant messages sent to the terminal. For assistance, contact Broadcom Support .\nWD46\nReason:\nInterTest for CICS internal logic error; unknown error condition.\nAction:\nActivate the CICS auxiliary trace. Then issue the InterTest for CICS CNTL=ITTRACE_ON and the ICDB TRACE_ON\ncommands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump,\nand any relevant messages sent to the terminal or the systems console. For assistance, contact Broadcom Support .\nWD47\nReason:\nInterTest for CICS internal logic error; product version error.\nAction:\nFor assistance, contact Broadcom Support .\nWD48\nReason:\nAn internal TCP/IP macro failure; SEND failure.\nAction:\nActivate the CICS auxiliary trace. Then issue the InterTest for CICS CNTL=ITTRACE_ON and the ICDB TRACE_ON\ncommands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump,\nand any relevant messages sent to the terminal or the systems console. For assistance, contact Broadcom Support .\nWD49\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "41d9473e1ddb-1", "text": "WD49\nReason:\nAn internal TCP/IP macro failure; RECEIVE failure.\nAction:\nActivate the CICS auxiliary trace. Then issue the InterTest for CICS CNTL=ITTRACE_ON and ICDB TRACE_ON\ncommands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump,\nand any relevant messages sent to the terminal or the systems console. For assistance, contact Broadcom Support .\nWD50\nReason:\nInterTest for CICS internal logic error; unknown error encountered.\nAction:\n 1799", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "479fd6a55292-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nActivate the CICS auxiliary trace. Then issue the InterTest for CICS CNTL=ITTRACE_ON and ICDB TRACE_ON\ncommands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump,\nand any relevant messages sent to the terminal or the systems console. For assistance, contact Broadcom Support .\nWD51\nReason:\nInterTest for CICS internal logic error; corrupt program save area.\nAction:\nActivate the CICS auxiliary trace. Then issue the InterTest for CICS CNTL=ITTRACE_ON and ICDB TRACE_ON\ncommands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump,\nand any relevant messages sent to the terminal or the systems console. For assistance, contact Broadcom Support .\nWD56\nReason:\nInterTest for CICS internal logic error; PC-to-Mainframe session link error.\nAction:\nActivate the CICS auxiliary trace. Then issue the InterTest for CICS CNTL=ITTRACE_ON and ICDB TRACE_ON\ncommands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump,\nand any relevant messages sent to the terminal or the systems console. For assistance, contact Broadcom Support .\nWD57\nReason:\nInterTest for CICS internal logic error; EXEC CICS LOAD command error.\nAction:\nActivate the CICS auxiliary trace. Then issue the InterTest for CICS CNTL=ITTRACE_ON and ICDB TRACE_ON\ncommands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump,\nand any relevant messages sent to the terminal or the systems console. For assistance, contact Broadcom Support .\nWD62\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "479fd6a55292-1", "text": "WD62\nReason:\nInterTest for CICS internal logic error; security authorization failure on an execution of an EXEC CICS command.\nAction:\nActivate the CICS auxiliary trace. Then issue the InterTest for CICS CNTL=ITTRACE_ON and ICDB TRACE_ON\ncommands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump,\nand any relevant messages sent to the terminal or the systems console. For assistance, contact Broadcom Support .\nWD63\nReason:\nInterTest for CICS internal logic error; EXEC CICS command error.\nAction:\nActivate the CICS auxiliary trace. Then issue the InterTest for CICS CNTL=ITTRACE_ON and ICDB TRACE_ON\ncommands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump,\nand any relevant messages sent to the terminal or the systems console. For assistance, contact Broadcom Support .\nWD66\nReason:\n 1800", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3258bb76ad26-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInterTest for CICS internal error; invalid TWA length.\nAction:\nThe TWA size for the transaction must be equal to or greater than 1536 bytes. If it is equal to or greater than 1536 then\nactivate the CICS auxiliary trace.\nActivate the CICS auxiliary trace. Then issue the InterTest for CICS CNTL=ITTRACE_ON and ICDB TRACE_ON\ncommands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump,\nand any relevant messages sent to the terminal or the systems console. For assistance, contact Broadcom Support .\nCAWD073I\nCA InterTest for CICS IS NOT ACTIVE\nReason:\nThe process required for use with the graphical user interface is not activated.\nAction:\nNone, this is an informational message.\nCAWD074I\nCA InterTest for CICS IS ACTIVE\nReason:\nThe process required for use with the graphical user interface is activated.\nAction:\nNone, this is an informational message.\nCAWD100I\nCA InterTest for CICS ACTIVE\nReason:\nThe process required for use with the graphical user interface has been activated.\nAction:\nNone, this is an informational message.\nCAWD101I\nCA InterTest for CICS TERMINATED\nReason:\nThe process required for use with the graphical user interface has been terminated.\nAction:\nNone, this is an informational message.\nCAWD120I\nCA InterTest for CICS INTERNAL TRACE SET <ON>\nReason:\nInterTest for CICS ICDB TRACE_ON command has been activated. The IN25CUI0 module will log message packets to\nthe CICS regions MSGUSR DD.\nAction:\nNone, this is an informational message.\nCAWD121I", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "3258bb76ad26-1", "text": "Action:\nNone, this is an informational message.\nCAWD121I\nCA InterTest for CICS INTERNAL TRACE SET <OFF>\n 1801", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "96c225761397-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nInterTest for CICS ICDB TRACE_ON command has been deactivated.\nAction:\nNone, this is an informational message.\nCAWD090W\nCA InterTest for CICS PHASE <1> ABEND EXIT CALL <EXIT>\nReason:\nInterTest for CICS graphical user interface abend processing has completed.\nAction:\nNo action is required.\nCAWD091W\nCA InterTest for CICS PHASE <1> ABEND EXIT CALL <DENEP>\nReason:\nInterTest for CICS graphical user interface abend processing has completed.\nAction:\nNo action is required.\nCAWD095W\nCA InterTest for CICS INIT/TERM ABEND EXIT CALL <EXIT>\nReason:\nInterTest for CICS graphical user interface abend processing has completed.\nAction:\nNo action is required.\nCAWD099W\nCA InterTest for CICS INIT/TERM ABEND EXIT CALL <ENTER>\nReason:\nInterTest for CICS initialization/termination of the graphical user interface process encountered an abend.\nAction:\nFor a termination request, no action is required. For an initialization request, retry.\nCAWD126W\nCA InterTest for CICS DIAGNOSTIC PROGRAM IS NOT AVAILABLE <VMOD>\nReason:\nProgram IN25VRPT is not found.\nAction:\nEnsure that the InterTest for CICS load module library in the CICS DFHRPL contains IN25VRPT. If the load module\nlibrary contains IN25VRPT, activate the CICS auxiliary trace. Retry the sequence of events that caused the error. Then\ncollect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal. For assistance, contact\nBroadcom Support .\nCAWD018E", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "96c225761397-1", "text": "Broadcom Support .\nCAWD018E\nCA InterTest for CICS INTERNAL ERROR: INVALID_TWA_FUNC_REQUEST\nReason:\n 1802", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aa5eabfb992d-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nInternal logic error: unknown TWA function request.\nAction:\nActivate the CICS auxiliary trace. Then issue the InterTest for CICS CNTL=ITTRACE_ON and the ICDB TRACE_ON\ncommands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump,\nand any relevant messages sent to the terminal or the systems console. For assistance, contact Broadcom Support .\nCAWD047E\nCA InterTest for CICS INTERNAL ERROR: CVD_VERSION_ERROR\nReason:\nInternal logic error: product version error.\nAction:\nContact Broadcom Support .\nCAWD022E\nCA InterTest for CICS INTERNAL ERROR: ICDB_INVALID_PROGRAM_START\nReason:\nThe ICDB transaction was not initiated by the graphical user interface PC user.\nAction:\nActivate the CICS auxiliary trace. Then issue the InterTest for CICS CNTL=ITTRACE_ON and the ICDB TRACE_ON\ncommands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump,\nand any relevant messages sent to the terminal or the systems console. For assistance, contact Broadcom Support .\nCAWD023E\nCA InterTest for CICS INTERNAL ERROR: ICDB_RECEIVE_FAILURE\nReason:\nInterTest for CICS internal logic error; EXEC CICS RECEIVE command error.\nAction:\nActivate the CICS auxiliary trace. Then issue the InterTest for CICS CNTL=ITTRACE_ON and the ICDB TRACE_ON\ncommands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump,\nand any relevant messages sent to the terminal or the systems console. For assistance, contact Broadcom Support .\nCAWD024E\nCA InterTest for CICS INTERNAL ERROR: INVALID_TERMINAL_DATA\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aa5eabfb992d-1", "text": "CA InterTest for CICS INTERNAL ERROR: INVALID_TERMINAL_DATA\nReason:\nThe ICDB transaction was entered from a terminal with invalid data.\nAction:\nRetry the ICDB transaction with valid data. Otherwise, activate the CICS auxiliary trace. Then issue the InterTest for CICS\nCNTL=ITTRACE_ON and the ICDB TRACE_ON commands. Retry the sequence of events that caused the error. Then\ncollect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal or the systems console.\nFor assistance, contact Broadcom Support .\nCAWD035E\nCA InterTest for CICS INTERNAL ERROR: ICDB_SEND_BUFF_GETMFAIL_RQ\nReason:\nInterTest for CICS internal logic error; EXEC CICS GETMAIN command\nError for user TCP/IP message buffer.\nAction:\n 1803", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b7d4b2fe4b08-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nActivate the CICS auxiliary trace. Then issue the InterTest for CICS CNTL=ITTRACE_ON and the ICDB TRACE_ON\ncommands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump,\nand any relevant messages sent to the terminal or the systems console. For assistance, contact Broadcom Support .\nCAWD039E\nCA InterTest for CICS INTERNAL ERROR: TCP_RECEIVE_FAIL\nReason:\nInterTest for CICS internal logic error; TCP/IP receive from the PC failed.\nAction:\nActivate the CICS auxiliary trace. Then issue the InterTest for CICS CNTL=ITTRACE_ON and the ICDB TRACE_ON\ncommands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump,\nand any relevant messages sent to the terminal or the systems console. For assistance, contact Broadcom Support .\nIN25UTIL Program Messages\n This section lists the messages produced by the IN25UTIL program.\nUTIL001\nX....X\nReason:\nThis message is an echo of the input request. The request is indicated by X....X.\nAction:\nNone.\nUTIL002\nINITIALIZATION COMPLETED\nReason:\nThe InterTest for CICS Symbolic File has been initialized.\nAction:\nNone.\nUTIL003\nXXXXXXXX DELETED FROM SYMBOLIC FILE\nReason:\nProgram XXXXXXXX was deleted from the InterTest for CICS Symbolic File.\nAction:\nNone.\nUTIL004\nXXXXXXXX UNLOADED FROM SYMBOLIC FILE\nReason:\nProgram XXXXXXXX has been unloaded from the InterTest for CICS Symbolic File.\nAction:\nNone.\n 1804", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "da0e2f7a0533-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUTIL005\nXXXXXXXX RELOADED TO SYMBOLIC FILE\nReason:\nProgram XXXXXXXX was reloaded to the InterTest for CICS Symbolic File.\nAction:\nNone.\nUTIL006\nXXXXXXXX RELOADED TO SYMBOLIC FILE AND HAS BEEN RENAMED TO YYYYYYYY\nReason:\nProgram XXXXXXXX was reloaded to the InterTest for CICS Symbolic File with the name YYYYYYYY.\nAction:\nNone.\nUTIL007\nUNLOAD PROCESSING COMPLETED\nReason:\nThe UNLOAD function completed.\nAction:\nNone.\nUTIL008\nRELOAD PROCESSING COMPLETED\nReason:\nThe RELOAD function completed.\nAction:\nNone.\nUTIL009\nPURGE PROCESSING COMPLETED \u2014 XXXXX RECORDS HAVE BEEN FREED\nReason:\nThe PURGE function completed and freed up the number of records indicated by XXXXX.\nAction:\nNone.\nUTIL010\nDEVICE NOW CLOSED\nReason:\nThe device, specified by a CLOSE= function, closed. Any subsequent requests for this device cause that device to open\nat load point.\nAction:\nNone.\nUTIL011\nINTERTEST BATCH UTILITY RUN COMPLETED SUCCESSFULLY\n 1805", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "725d887ffa20-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nAll requested functions have been performed and the InterTest for CICS Symbolic File was updated successfully.\nAction:\nNone.\nUTIL012\nRELOAD PROCESSING STARTED FOR PROGRAM XXXXXXXX\nReason:\nThe RELOAD function began for program XXXXXXXX.\nAction:\nNone.\nUTIL047\nXXXXXXXX MUST BE DELETED\nReason:\nWhile processing program XXXXXXXX, a condition occurred that indicated that data for the program was corrupted.\nAction:\nDelete this program.\nUTIL048\nXXXXXXXX CANNOT BE UNLOADED\nReason:\nProgram XXXXXXXX was found to be corrupted and therefore could not be unloaded.\nAction:\nNone.\nUTIL049\nXXXXXXXX HAS ZERO RECORDS \u2014 ENTRY BYPASSED\nReason:\nProgram XXXXXXXX was found to be corrupted.\nAction:\nComplete the following steps:\n1.\n2.Delete the program from the Symbolic file.\n3.\n4.Run an UNLOAD=ALL UTILity request.\n5.\n6.Initialize the Symbolic file.\n7.\n8.Run a RELOAD=ALL UTILity request, using the file created in step 2 as input.\n9.\nUTIL050\nPASSWORD MISSING \u2014 REQUEST IGNORED\nReason:\n 1806", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dc6dd968a6c3-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe function requested requires a PASSWORD= parameter card. Only this request is ignored.\nAction:\nAdd a PASSWORD= parameter card as the first parameter card in the job stream and resubmit the job.\nUTIL051\nPASSWORD INCORRECT\nReason:\nThe password provided on the PASSWORD= parameter card does not match the password that was generated by the\nSYMPSWD= option of InterTest for CICS. The SYMPSWD= gen option is described in Configuring. The job is terminated.\nAction:\nChange the password specified by the PASSWORD= parameter card to match the generated password and resubmit the\nentire job stream.\nUTIL052\nINVALID REQUEST\nReason:\nThe function requested is not valid. This condition may be caused by a misspelled option or just bad input. The job is\nterminated.\nAction:\nCorrect the requested function and resubmit the entire job stream.\nUTIL053\nXXXXXXXX CANNOT FIT ON FILE \u2014 PROGRAM IS BYPASSED\nReason:\nThe InterTest for CICS Symbolic file did not contain enough free space to handle a RELOAD function for program\nXXXXXXXX. The program is bypassed.\nAction:\nComplete the following steps:\n1.\n2.Using the UTILITY job, run an UNLOAD=ALL request.\n3.\n4.Delete the InterTest for CICS Symbolic File using IDCAMS.\n5.\n6.Run an IDCAMS DEFINE for the InterTest for CICS Symbolic File with a larger space allocation. Remember that a\nsecondary space allocation is not permitted.\n7.\n8.Using the UTILITY job, run an INITIALIZE request.\n9.\n10.Using the UTILITY job, run a RELOAD=ALL request, using the file created in Step 1 as input.\n11.", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dc6dd968a6c3-1", "text": "11.\n12.Resubmit the original job.\n13.\nOr:\n1.\n2.Using the UTILITY job, run a PURGE= request to free up space.\n3.\n 1807", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "43104b499441-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n4.Resubmit the original job.\n5.\nUTIL054\nPURGE INTERVAL INVALID OR MISSING \u2014 REQUEST NOT PROCESSED\nReason:\nThe PURGE= request either did not specify a number of days or the number of days specified was not within the range of\n1 through 365. This request is ignored.\nAction:\nCorrect the PURGE= request and resubmit the job.\nUTIL055\nPROGRAM NOT FOUND IN FILE OR WAS NOT USABLE\nReason:\nThe program specified for a requested function was not found in the Symbolic File or was unusable. This request is\nignored.\nAction:\nRun a REPORT function. If the program is found, delete it and resubmit the original job.\nUTIL056\nPROGRAM NAME IS GREATER THAN 8 CHARACTERS LONG \u2014 REQUEST IGNORED\nReason:\nThe program specified for a requested function contained more than 8 characters. This request is ignored.\nAction:\nCorrect the requested function and resubmit the job.\nUTIL057\nSYMBOLIC FILE IS EMPTY \u2014 PLEASE RUN INITIALIZATION AS FIRST STEP\nReason:\nThe Symbolic File did not contain the required control records. The job is terminated.\nAction:\nUsing the UTILITY job, run an INITIALIZE request.\nUTIL058\nVSAM RECORD LENGTH NOT = 2040\nReason:\nThe Symbolic File was created with a wrong record size. The job is terminated.\nAction:\nFollow the instructions in Configuring for the creation of the InterTest for CICS Symbolic File.\nUTIL059\nNO LISTER INFORMATION FOR THIS PROGRAM \u2014 PRINT= REQUEST IGNORED\nReason:\nThe program specified by the PRINT= request did not contain any saved source. This request is ignored.\nAction:\n 1808", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8fdbffd720d6-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nNone.\nUTIL060\nREQUEST FOR VIRTUAL STORAGE FAILED\nReason:\nThe request for GETMAIN or GETVIS storage failed. The job is terminated.\nAction:\nResubmit the entire job stream, using a bigger region size or run the job in a larger partition.\nUTIL061\nOPEN FAILURE FOR UNLOAD DEVICE\nReason:\nThe open request for the device to be used for an UNLOAD= function failed.\nAction:\nCorrect the JCL and resubmit the job.\nUTIL062\nOPEN FAILURE FOR RELOAD DEVICE\nReason:\nThe open request for the device to be used for a RELOAD= function failed.\nAction:\nCorrect the JCL and resubmit the job.\nUTIL063\nUNLOAD=ALL HAS BEEN RUN \u2014 ALL OTHER UNLOAD REQUESTS ARE IGNORED\nReason:\nAn UNLOAD= request has been made after an UNLOAD=ALL request. This request is ignored.\nAction:\nResubmit the UNLOAD= request which was rejected in a separate job stream.\nUTIL064\nINPUT FROM RELOAD FILE IS INVALID\nReason:\nData being retrieved for a RELOAD= request was not in the correct format. This condition may be caused by incorrect\nJCL or by data that was overlaid since its creation by the UNLOAD= request. This request is ignored.\nAction:\nIf a bad JCL caused the error, correct the JCL and resubmit the request. If bad data caused the error, the problem is not\ncorrectable.\nUTIL065\nRELOAD FILE IS EMPTY\nReason:\nAn ENDOFFILE condition occurred on the first read from the RELOAD device. This condition occurs when the file is\nempty. This request is ignored.\nAction:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8fdbffd720d6-1", "text": "empty. This request is ignored.\nAction:\nIf a bad JCL caused the error, correct the JCL and resubmit the request; otherwise, the problem is not correctable.\n 1809", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "16d3aec0b899-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUTIL066\nXXXXXXXX ALREADY EXISTS IN FILE: RELOAD FOR THIS PROGRAM IGNORED\nReason:\nThe program to be reloaded already exists on the file. This request is ignored.\nAction:\nDelete the program, using a DELETE= request, and resubmit the RELOAD= request.\nUTIL067\nxxxxxxx yyyy ERROR R15 = X'rr' ERROR CODE = X'ee'\nReason:\nThe VSAM error has occurred while running the UTILITY program. The message contains the following information:\n\u2022\n\u2022xxxxxxx is the name of the InterTest for CICS Symbolic File\n\u2022\n\u2022yyyy is the type of request (OPEN, GET, or PUT)\n\u2022\n\u2022rr is the return code, in hexadecimal\n\u2022\n\u2022ee is the error code, in hexadecimal\n\u2022\nThe job may or may not be terminated, depending on the function requested and when the error occurred.\nAction:\nUsing the information from the message, find the explanation of the error in the VSAM manual that contains the error\nmessages. Handle the error as described in your manual.\nUTIL068\nSEQUENCE NUMBER NOT FOUND\nReason:\nWhile processing a request, an internal record key was not found. This condition indicates a corrupted file.\nAction:\nDelete the program that caused the problem.\nUTIL070\nRECORD COUNT ERROR AT ENDREQ\nReason:\nAn internal check of the file has failed. This condition indicates a corrupted file. The job is terminated with a dump.\nAction:\nFor assistance, contact Broadcom Support .\nUTIL071\nUNLOAD OR RELOAD NOT SPECIFIED\nReason:\nA CLOSE= request has been made but did not specify UNLOAD or RELOAD. The job is terminated.\nAction:\nCorrect the CLOSE= request and resubmit the entire job stream.\n 1810", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c6f2d0ff58f4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUTIL072\nERROR OCCURRED WHILE READING RELOAD DEVICE (DOS)\nReason:\nThe system detected an error condition while reading a record from the device pointed to by SYS005. The job is\nterminated.\nAction:\nDetermine the cause of the error, correct the problem, and resubmit the entire job stream.\nUTIL073\nERROR OCCURRED WHILE WRITING TO UNLOAD DEVICE (DOS)\nReason:\nThe system detected an error condition while writing a record to the device pointed to by SYS005. The job is terminated.\nAction:\nDetermine the cause of the error, correct the problem, and resubmit the entire job stream.\nUTIL074\nERROR OCCURRED WHILE READING PARAMETER CARDS (DOS)\nReason:\nThe system detected an error condition while reading a control card. The job is terminated.\nAction:\nDetermine the cause of the error, correct the problem, and resubmit the entire job stream.\nUTIL075\nENQ ERROR: CODE = X'yy' (DOS)\nReason:\nAn error occurred while issuing a SVC 63 (lock) request. The job is terminated.\nAction:\nFor assistance, contact Broadcom Support .\nUTIL076\nREQUESTED DATA SPACE EXCEEDS MAXIMUM FOR FILE\nReason:\nThe InterTest for CICS Symbolic File has been defined with a size that exceeds its capacity. The maximum size of this file\nis about 4,000,000 2K records. The job is terminated.\nAction:\nThis error would normally be caused by defining the file with a secondary space allocation. If this is the case, then\nredefine the file without a secondary allocation and then initialize it.\nUTIL077\nBATCH UTILITY RUN UNSUCCESSFUL \u2014 ALL UPDATES HAVE BEEN BACKEDOUT\nReason:", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "c6f2d0ff58f4-1", "text": "BATCH UTILITY RUN UNSUCCESSFUL \u2014 ALL UPDATES HAVE BEEN BACKEDOUT\nReason:\nThis message is produced on any error condition that terminates the job. If this message is produced, all requested\nfunctions, even if they were correct, are backed out.\nAction:\nAfter the error condition is corrected, the entire job stream must be resubmitted.\n 1811", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "508c8304731c-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUTIL078\nINTERTEST BATCH UTILITY RUN UNSUCCESSFULUPDATES HAVE NOT BEEN BACKED-OUT\nReason:\nThis message is produced when an error condition, which is not serious, has occurred. If this message is produced, only\nthe requests that were in error are ignored and all valid requests were performed.\nAction:\nReview the output for any previous error messages, resolve those errors, and try again.\nUTIL079\nPROGRAM NOT FOUND IN RELOAD FILE \u2014 REQUEST IGNORED\nReason:\nThe program specified by a RELOAD= request was not found in the reload file.\nAction:\nNone.\nUTIL080\nVSAM CI SIZE NOT = 2048\nReason:\nThe Symbolic File was created with the wrong CI size.\nAction:\nRecreate the Symbolic File with the correct CI size.\nUTIL094\nCANNOT BE RELOADED DUE TO PROTSYM FRAGMENTATION\nReason:\nWhen reloading program xxxxxxxx  it became too fragmented to add to the file properly. The program was not added to the\nfile.\nAction:\nFollow these steps:\n1.Using the UTILITY job, run an UNLOAD=ALL request.\n2.Delete the symbolic file using IDCAMS.\n3.Run an IDCAMS DEFINE for the symbolic file with a larger space allocation. Remember that a secondary space\nallocation is not permitted.\n4.Using the UTILITY job, run an INITIALIZE request.\n5.Using the UTILITY job, run a RELOAD=ALL request, using the file created in step 1 as input.\n6.Resubmit the original job.\nOr:\n1.Using the UTILITY job, run a PURGE request to free up space.\n2.Resubmit the original job.\n \nUTIL101", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "508c8304731c-1", "text": "2.Resubmit the original job.\n \nUTIL101\nINVALID RECORD ON FILE. UNLOAD AND RELOAD OF FILE RECOMMENDED\nReason:\n 1812", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1771e90ee0d8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAn invalid DATE/TIME field is found in a Program Master Index Record.\nAction:\nUnload and Reload of the PROTSYM file is recommended.\nUTIL102\nx22 CANCEL, ABEND PERCOLATED\nReason:\nA system cancel event occurred while IN25UTIL was executing.\nAction:\nCapture the dump if needed.\nUTIL103\nRECOVERY FAILURE, S0C1 GENERATED\nReason:\nA VSAM request failed.\nAction:\nCapture and save the S0C1 dump and contact Broadcom Support  for assistance.\nUTIL100\n*WARNING PROTSYM IS NOT COMPATIBLE WITH INTERTEST RELEASES BELOW 5.4*\nReason:\nYou are attempting to use an r5.4 symbolic file with an earlier InterTest release. The new, larger symbolic files can only be\nused with r5.4 and higher; they are not downward compatible with earlier InterTest releases.\nAction:\nFor InterTest releases prior to r5.4, only use symbolic files created with a pre-5.4 release.\nUTIL104\nINVALID DATE FORMAT - REQUEST IGNORED\nReason:\nThe DATETIME, BEFOREDATETIME, or AFTERDATETIME parameter was specified with an incorrect value or in an\nincorrect format. The date must exist, and its value should follow a yyyy/mm/dd hh:mm:ss format. The year is required,\nwhile all other fields are optional.\nAction:\nCorrect the value and resubmit the request.\nUTIL105\nYEAR CONTAINS NON NUMERIC DATA - REQUEST IGNORED\nReason:\nThe year specified for a DATETIME, BEFOREDATETIME, or AFTERDATETIME parameter contains a value which is not\nnumeric.\nAction:\nCorrect the value and resubmit the request.\nUTIL106\nMONTH CONTAINS NON NUMERIC DATA - REQUEST IGNORED", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "1771e90ee0d8-1", "text": "UTIL106\nMONTH CONTAINS NON NUMERIC DATA - REQUEST IGNORED\nReason:\n 1813", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9efc7bbf26f8-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nThe month specified for a DATETIME, BEFOREDATETIME, or AFTERDATETIME parameter contains a value which is not\nnumeric.\nAction:\nCorrect the value and resubmit the request.\nUTIL107\nDAY CONTAINS NON NUMERIC DATA - REQUEST IGNORED\nReason:\nThe day specified for a DATETIME, BEFOREDATETIME, or AFTERDATETIME parameter contains a value which is not\nnumeric.\nAction:\nCorrect the value and resubmit the request.\nUTIL108\nHOUR EXCEEDS MAXIMUM VALUE - REQUEST IGNORED\nReason:\nThe hour specified for a DATETIME, BEFOREDATETIME, or AFTERDATETIME parameter contains a value which is\ngreater than or equal to 24.\nAction:\nCorrect the value and resubmit the request.\nUTIL109\nHOUR CONTAINS NON NUMERIC DATA - REQUEST IGNORED\nReason:\nThe hour specified for a DATETIME, BEFOREDATETIME, or AFTERDATETIME parameter contains a value which is not\nnumeric.\nAction:\nCorrect the value and resubmit the request.\nUTIL110\nMINUTE EXCEEDS MAXIMUM VALUE - REQUEST IGNORED\nReason:\nThe minute specified for a DATETIME, BEFOREDATETIME, or AFTERDATETIME parameter contains a value which is\ngreater than or equal to 60.\nAction:\nCorrect the value and resubmit the request.\nUTIL111\nMINUTE CONTAINS NON NUMERIC DATA - REQUEST IGNORED\nReason:\nThe minute specified for a DATETIME, BEFOREDATETIME, or AFTERDATETIME parameter contains a value which is\nnot numeric.\nAction:\nCorrect the value and resubmit the request.\n 1814", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6bbfa55f1b8e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUTIL112\nSECOND EXCEEDS MAXIMUM VALUE - REQUEST IGNORED\nReason:\nThe second specified for a DATETIME, BEFOREDATETIME, or AFTERDATETIME parameter contains a value which is\ngreater than or equal to 60.\nAction:\nCorrect the value and resubmit the request.\nUTIL113\nSECOND CONTAINS NON NUMERIC DATA - REQUEST IGNORED\nReason:\nThe second specified for a DATETIME, BEFOREDATETIME, or AFTERDATETIME parameter contains a value which is\nnot numeric.\nAction:\nCorrect the value and resubmit the request.\nUTIL114\nINVALID PARAMETER FORMAT - REQUEST IGNORED\nReason:\nA parameter value was in an incorrect format or contained invalid characters.\nAction:\nCorrect the value and resubmit the request.\nUTIL115\nNON NUMERIC DATA ENTERED - MAXPGMVER HAS BEEN SET TO 1\nReason:\nA parameter value contained a value which was not numeric.\nAction:\nCorrect the value and resubmit the request.\nUTIL116\nMAXPGMVER WAS REACHED - RELOAD FOR THIS PROGRAM IGNORED\nReason:\nThe maximum number of program versions has been reached for the current program being reloaded.\nUTIL117\nMAXPGMVER WAS HIGHER THAN ALLOWED - MAXPGMVER HAS BEEN SET TO 255.\nReason:\nValid value range for MAXPGMVER is 1-255.\nUTIL118\nMAXPGMVER CANNOT BE ZERO - MAXPGMVER HAS BEEN SET 1.\nReason:\nValid value range for MAXPGMVER is 1-255.\n 1815", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "993f9dce1c79-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUTIL119\nINVALID DATA ENTERED - USEDSPACEMSG HAS BEEN SET TO 0.\nReason:\nThe valid value range for USEDSPACEMSG is 0-99.\nUTIL120\nFUNCTION NOT SUPPORTED IN THE VERSION OF PROTSYM.\nReason:\nYou used a function that is not supported in the current version of PROTSYM.\nAction:\nNone.\nUTIL121\nINVALID DATA ENTERED - REQUEST IGNORED.\nReason:\nA parameter value did not fall in a valid range.\nAction:\nCorrect the value and resubmit the request.\nUTIL122\nMULTIVERSION SUBPARAMETERS NOT VALID FOR GENERIC PROGRAM NAMES\nReason:\nA multiversion subparameter was used in conjunction with a generic program name.\nAction:\nRemove multiversion subparameters or provide a complete program name.\nUTIL123\nNUMBER OF SKIPPED PROGRAM ENTRIES:\nReason:\n Details how many invalid programs entries have been encountered and skipped. \n Action:\n No action required. \nUTIL124\nBATCH UTILITY COMPLETED, INVALID PROGRAM ENTRIES ENCOUNTERED AND SKIPPED\nReason:\nThe run was completed with encountered and skipped invalid program entries.\nAction:\nNo action needed. You can review the skipped programs and remove the invalid entries.  \n \n 1816", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f24a4ebcb676-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nUTIL200\nEXTERNAL SECURITY IS <ON | OFF>\nReason:\nThe external security option in CAVHCONF is either ON or OFF.\nAction:\nNone.\nUTIL201\nEXTERNAL SECURITY API IS MISSING\nReason:\nThe external security API, CAVHBAPI, cannot be loaded.\nAction:\nAdd the load library that contains CAVHBAPI to the LINKLIST or STEPLIB of your job.\nUTIL202\nEXTERNAL SECURITY CHECK FAILED. <Resource Class> <Entity> SAF RC=XXXX RACF RC=XXXX\nREASON=XXXX\nReason:\nThe user does not have the required level of access to perform the requested function\nAction:\nContact your security administrator to grant the permission.\nUTIL203\nEXTERNAL SECURITY CHECK SUCCESSFUL\nReason:\nThe user has passed external security verification\nAction:\nNone.\nSymbolic Post Processor Program Messages\nThis section lists messages produced by the InterTest for CICS symbolic postprocessor programs IN25COB2, IN25SYMA,\nand IN25SYMC.\nSYM002\nLISTER= OPTION INVALID, NO LISTING SAVED\nReason:\nThe LISTER= option was invalid.\nAction:\nCorrect the LISTER= option and resubmit your job stream.\nSYM003\nCUTPRINT= OPTION INVALID, LISTING WILL BE PRINTED\nReason:\nThe CUTPRINT= option was invalid.\nAction:\n 1817", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "dc36f3248678-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nCorrect the CUTPRINT= option and resubmit your job stream.\nSYM004\nSYMBOLIC INFORMATION HAS BEEN SET AS NONPURGABLE\nReason:\nThe NOPURGE option was specified on the parameter statement.\nAction:\nNone.\nSYM005\nPARAMETER OPTIONS INVALID, SYMBOLIC STEP NOT RUN\nReason:\nAn option was specified on the parameter statement was not recognizable.\nAction:\nCorrect the parameter statement and resubmit your job stream.\nSYM006\nLISTER=XXX REQUESTED\nReason:\nThis identifies the LISTER option specified.\nAction:\nNone.\nSYM007\nCUTPRINT=XXX REQUESTED\nReason:\nThis identifies the CUTPRINT option specified.\nAction:\nNone.\nSYM008\nCONTROL STATEMENT IS MISSING \u2014 JOB TERMINATED\nReason:\nNo parameter statement was found.\nAction:\nCorrect the parameter statement and resubmit your job stream.\nSYM009\nPROTSYM HAS REACHED MAXIMUM NUMBER OF PROGRAMS\nReason:\nThe InterTest for CICS Symbolic File has exceeded the maximum number of program entries.\nAction:\nDelete some programs for your file and resubmit your job stream. (The symbolic file capacity was greatly increased in\nRelease 5.4.) Or, define a new InterTest for CICS Symbolic File and then resubmit your job stream using the new file.\nRefer to the SYMFIL= parameter in Configuring for an explanation of how to handle multiple Symbolic files.\n 1818", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7183ee7b1610-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSYM010\nPROCESSING HAS BEGUN FOR PROGRAM NAME \u2014 XXXXXXXX\nReason:\nProgram XXXXXXXX is being processed and its output will reside on the InterTest for CICS Symbolic File.\nAction:\nNone.\nSYM011\nSEQUENCE NUMBERS ARE NOT IN ASCENDING SEQUENCE. JOB WILL BE TERMINATED \u2014 CONTACT\nTechnical Support\nReason:\nThis is an internal verification check error.\nAction:\nContact Broadcom Support .\nSYM012\nRECORD COUNT ERROR AT XXXXXXX\nReason:\nThis is an internal verification check error.\nAction:\nContact Broadcom Support .\nSYM013\nQQQQ ERROR R15 = X'YY' ERROR CODE = X'ZZ'\nReason:\nA VSAM request, QQQQ, has resulted in an error. InterTest for CICS has reached the maximum number of program\nentries. This normally indicates a corrupted file.\nAction:\nContact Broadcom Support .\nSYM014\nPROTSYM OUT OF SPACE\nReason:\nThe InterTestfor CICS Symbolic File has exceeded the maximum number records.\nAction:\nEither delete some programs for your file or increase the size of your symbolic file. (The symbolic file capacity was greatly\nincreased in Release 5.4). Then resubmit your job stream. Or, define a new InterTest for CICS Symbolic File and then\nresubmit your job stream using the new file. Refer to the SYMFIL= parameter in Configuring for an explanation of how to\nhandle multiple symbolic files.\nSYM015\nDD STATEMENT MISSING FOR PROTSYM\nReason:\nIn MVS, the DD JCL statement for the InterTest for CICS Symbolic File could not be found.\nAction:\nCorrect the JCL and resubmit the job stream.\n 1819", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "12b57a181ee1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSYM016\nENQ ERROR \u2014 CODE = X'YY'\nReason:\nIn VSE, an error occurred when an SVC 63 (ENQ) was issued. This is normally caused by a NOT FOUND condition for\nthe InterTest for CICS Symbolic file.\nAction:\nCheck the JCL and correct. Contact Broadcom Support  if the JCL is correct.\nSYM017\nUTILITY IN PROGRESS ON PROTSYM FILE \u2014 JOB TERMINATED\nReason:\nThe InterTest for CICS batch utility program was processing the Symbolic file at the same time that the postprocessor step\nwas running.\nAction:\nFirst ensure that the last UTILITY run was successful. To turn off this indicator, run a UTILITY job with a REPORT\nfunction.\nSYM018\nMAIN STORAGE NOT AVAILABLE \u2014 INCREASE REGION SIZE\nReason:\nA GETMAIN (MVS) or GETVIS (VSE) request has failed due to insufficient storage.\nAction:\nResubmit the job stream with a larger region size.\nSYM019\nPROGRAM ABENDED 111 AT DISPLACEMENT XXXXX\nReason:\nA condition has occurred that required a termination with a dump.\nAction:\nContact Broadcom Support .\nSYM020\nSYMBOLIC FILE UPDATED SUCCESSFULLY\nReason:\nThe postprocessor has ended successfully and the program has been added to the InterTest for CICS Symbolic File.\nAction:\nNone.\nSYM021\nXXXXXX SOURCE STATEMENTS SAVED\nReason:\nOn a successful completion, the number of source statements, XXXXXXX, displays.\nAction:\nNone.\n 1820", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "7d8e9f1cba6e-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSYM022\nYYYY TOTAL RECORDS INSERTED INTO SYMBOLIC FILE\nReason:\nOn a successful completion, the total number of records added to the InterTest for CICS Symbolic File, YYYY, displays.\nAction:\nNone.\nSYM023\nPOSTPROCESSOR TERMINATED\nReason:\nThe InterTest for CICS postprocessor program has ended.\nAction:\nNone.\nSYM024\nINPUT FILE PROCESSED\nReason:\nThe InterTest for CICS postprocessor program has read all of the data passed to it in the INPUT data set.\nAction:\nNone.\nSYM025\nPROCEDURE NAMES CROSSREFERENCE NOT FOUND\nReason:\nThe procedure names crossreference output area was not found.\nAction:\nWithout this area, InterTest for CICS will be unable to process any requests using a PARAGRAPH NAME. If PARAGRAPH\nNAMES are needed, correct the COBOL options and resubmit the job stream.\nSYM026\nINPUT FILE IS EMPTY\nReason:\nThe data set specified by the INPUT JCL statement was empty.\nAction:\nCorrect and resubmit the job stream.\nSYM027\nCAPEX OPTION ERROR \u2014 MLIST MUST BE SPECIFIED\nReason:\nThe required Optimizer/II  (CAPEX) option MLIST was not specified.\nAction:\nCorrect and resubmit the job stream.\nSYM028\nCOBOL COMPILER OPTIONS ARE INCORRECT \u2014 XXXX \u2014 NOT FOUND\n 1821", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "5b2ccde5a2ad-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nArea XXXXX could not be found in the COBOL listing. For Working Storage, at least one data item must be declared.\nAction:\nCorrect COBOL compiler options or add a Working Storage data item to produce the required area and resubmit the job\nstream.\nSYM029\nXXXXX NOT REQUESTED \u2014 PROCESSING TERMINATED\nReason:\nThe required COBOL II option, XXXXX, was not specified.\nAction:\nCorrect and resubmit the job stream.\nSYM030\nNO CSECT FOUND \u2014 PLEASE REMOVE ANY PRINT NOGEN STATEMENTS THAT MIGHT PREVENT THE CSECT\nSTATEMENT FROM BEING PRINTED\nReason:\nAfter examining the entire Assembler listing, no labeled CSECT could be found.\nAction:\nCorrect and resubmit the job stream.\nSYM031\nINPUT IS FROM COMMAND TRANSLATOR\nReason:\nThe input passed to the InterTest for CICS postprocessor program was generated by the CICS command translator and\nnot by the compiler or Assembler.\nAction:\nCorrect the procedure so that the passed output is from the compiler/Assembler.\nSYM032\nOPEN FOR INPUT FAILED\nReason:\nThe INPUT file could not be opened. Check the printed output for additional error messages that may have been\nproduced by the operating system.\nAction:\nCorrect the JCL and resubmit the job stream.\nSYM033\nOPEN FOR OUTPUT FAILED\nReason:\nThe OUTPUT file could not be opened. Check the printed output for additional error messages that may have been\nproduced by the operating system.\nAction:\nCorrect the JCL and resubmit the job stream.\n 1822", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "b71df12bb324-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSYM034\nOPEN FOR CARDS FAILED\nReason:\nThe CARDS file could not be opened. Check the printed output for additional error messages that may have been\nproduced by the operating system.\nAction:\nCorrect the JCL and resubmit the job stream.\nSYM035\nNO CROSSREFERENCE FOUND \u2014 SYMBOLIC NAMES CANNOT BE USED\nReason:\nThe CrossReference area could not be found in the Assembler listing. Without this area, Symbolic names cannot be\nresolved.\nAction:\nResubmit the job stream with either the XREF (SHORT) or XREF (FULL) Assembler parameter.\nSYM036\nPASSED PARAMETER STATEMENTS\nReason:\nThe next group of printed lines is an echo of all the parameter statements read by the postprocessor.\nAction:\nNone.\nSYM038\nXXX LINKEDITOR MAP RECORD(S) HAVE BEEN ADDED TO ENTRY\nReason:\nThe IN25LINK program has added XXX linkageeditor records to an existing Symbolic entry.\nAction:\nNone.\nSYM039\nNO LINKEDITOR ENTRY FOUND FOR XXXXXXXX\nReason:\nThe linkname, XXXXXXXX, specified on an IN25LINK postprocessor control card could not be found in the output\nproduced by the linkageeditor.\nAction:\nYou can do one of the following:\n\u2022\n\u2022Ignore the error\n\u2022\n\u2022Correct the parameter card and resubmit the job stream\n\u2022\n\u2022Use the CNTL Composite Support menu to add the information online\n\u2022\n 1823", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8ed82e6c5ce5-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSYM040\nTHE FOLLOWING OPTIONS WERE NOT SPECIFIED\nReason:\nThe list of options following this message was not specified. Without these options, some InterTest for CICS facilities may\nnot function.\nAction:\nCorrect the JCL and resubmit the job stream.\nSYM042\nNO STATEMENT INFORMATION WAS FOUND IN THE PASSED LISTING\nReason:\nThe postprocessor program could not find the data needed to process the statement information.\n\u2022\n\u2022For a COBOL program, this data is produced by the CLIST or PMAP compiler option.\n\u2022\n\u2022For a COBOL II program, this data is produced by the OFFSET or LIST compiler option.\n\u2022\n\u2022For an OPTIMIZER program, this data is produced by the MLIST option. For an Optimizer/II  program, this data is\nproduced by the MOFFSET option.\n\u2022\nThe following are some of the conditions that may cause this error:\n\u2022\n\u2022Errors in the compile which cause the suppression of the needed data\n\u2022\n\u2022Incorrect compiler options\n\u2022\n\u2022Compiler control statements that suppress the needed data\n\u2022\nAction:\nDetermine why the required area was suppressed. Correct and resubmit the job stream.\nSYM043\nTHE CSECT NAMED XXXXXXX WAS NOT FOUND IN THE EXTERNAL SYMBOL DICTIONARY\nReason:\nIn a VSE Assembler, a CSECT statement named XXXXXXX was found, but that name could not be found in the ESD list.\nAction:\nCorrect the JCL and resubmit the job stream.\nSYM044\nINPUT DATA WAS NOT PRODUCED BY THE LINKAGEEDITOR\nReason:\nThe data passed to the IN25LINK postprocessor via the INPUT JCL statement did not contain the output produced by the", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "8ed82e6c5ce5-1", "text": "linkageeditor step or the linkage editor PARM=MAP is not in effect.\nAction:\nCorrect the JCL and resubmit the job stream.\n 1824", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "113cf4d2d5ac-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSYM045\nINVALID POWER PARAMETER FORMAT\nReason:\nThe POWER= parameter was specified incorrectly.\nAction:\nCorrect the parameter card and resubmit the job stream.\nSYM046\nINVALID POWER CLASS SPECIFIED (NOT A \u2014 Z)\nReason:\nThe POWER LST class specified on the parameter card was not an alphabetic character.\nAction:\nCorrect the parameter card and resubmit the job stream.\nSYM047\nINVALID POWER JOB NAME\nReason:\nThe name specified in the POWER= parameter is invalid.\nAction:\nCorrect the parameter card and resubmit the job stream.\nSYM048\nIN25PWRI, POWER INTERFACE MODULE, WAS NOT FOUND\nReason:\nThe InterTest for CICS module, IN25PWRI, was not found in the load library specified in the JCL. This module is required\nwhen using the VSE/POWER LST queue.\nAction:\nYou may do one of the following:\n\u2022\n\u2022Change the JCL to point to a load library that contains the IN25PWRI module.\n\u2022\n\u2022Change the JCL to use SYSLST instead of POWER.\n\u2022\nSYM049\nIN25OPTS MODULE NOT FOUND \u2014 DEFAULTS ARE USED\nReason:\nThe InterTest for CICS module, IN25OPTS, was not found in the load library specified in the JCL.\nAction:\nIf the default POWER options can be used, no action is required. However, it is recommended that the correct IN25OPTS\nmodule be added to the load library.\nSYM050\nPOWER INTERFACE IS NOT ACTIVE\n 1825", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "f87b24884455-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nReason:\nThe POWER= parameter was specified incorrectly.\nAction:\nCorrect the parameter card and resubmit the job stream.\nSYM051\nSYNTAX ERROR IN WH= OPTION\nReason:\nA syntax error was found in the Realia Workbench Host Option parameter.\nAction:\nCorrect the parameter card and resubmit the job stream.\nSYM052\nWH= SOURCE FILE OPTION IS INCORRECT\nReason:\nAn error was found in the Realia Workbench Host Option parameter.\nAction:\nCorrect the parameter card and resubmit the job stream.\nSYM053\nWH= MEMBER NAME IS MISSING OR INCORRECT\nReason:\nAn error was found in the Realia Workbench Host Option parameter.\nAction:\nCorrect the parameter and resubmit the job stream.\nSYM054\nRELIA WORKBENCH HOST OPTION WAS REQUESTED WITHOUT HAVING A LISTER OPTION SPECIFIED\nReason:\nThe LISTER option was not specified in the Realia Workbench HostOption parameter.\nAction:\nThe LISTER=ALL option is set by default.\nSYM055\nRELIA WORKBENCH HOST OPTION INTERFACE MODULE WAS NOT LINKED WITH THIS MODULE\nReason:\nThe Realia Workbench Host Option Interface Module was not linked.\nAction:\nCorrect and resubmit the job.\nSYM056\nA CA-LMP RIMSTAT ERROR HAS BEEN DETECTED\nReason:\nThe License Management Program definition does not contain a license for PL1.\nAction:\nEnsure that you have the proper level of software installed. Contact Broadcom Support .\n 1826", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "6eac4ff0431b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSYM057\nCSECT NAME 'XXXXXXXX' IS GT 8 BYTES. CSECT IGNORED\nReason:\nCSECT name is greater than 8 bytes.\nAction:\nCorrect and resubmit the job.\nSYM058\nHLASM OPTION \"LIST(133|MAX)\" IS NOT SUPPORTED. USE OPTION \"LIST(121)\".\nReason:\nHLASM option \"LIST(133|MAX) is not supported.\nAction:\nCorrect the option. Use \"LIST(121)\".\nSYM059\nHLASM OPTION \"NOTHREAD\" IS NOT SUPPORTED. USE OPTION \"THREAD\".\nReason:\nThe NOTHREAD option is not supported.\nAction:\nCorrect the option. Use the THREAD option (IBM Default).\nSYM070\nJOBNAME=jobname, USER=userid, SYMBOLIC FILE XXX.XXXX.XXXX.XXXX IS XX% FULL.\nReason:\nThe message informs you that the user specified limit for used space in the symbolic file was reached.\nAction:\nNone.\nSYM090\nATTEMPT TO UPDATE SAM RECORD VIA DATA RPL\nSYM091\nATTEMPT TO UPDATE DATA RECORD VIA SAM RPL\nSYM092\nATTEMPT TO UPDATE DIRECTORY RECORD VIA DATA RPL\nSYM093\nATTEMPT TO UPDATE DATA RECORD VIA DIRECTORY RPL\nSYM094\nNO ENQ IS SET FOR A XXXXXX\n 1827", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "9ec7aec0bcb1-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nSYM095\nDIRECTORY RECORD IS CORRUPTED\nSYM097\nMISMATCH ON AVAILABLE FREE RECORDS IN ONE SAM\nSYM099\nMAXPGMVER WAS REACHED - OLDEST VERSION HAS BEEN DELETED TO PROCESS CURRENT REQUEST.\nSYM960\nMAX SAM RECS EXCEEDED. PROTSYM FILE MAY BE CORRUPTED\nSYM961\nMAX DIR RECS EXCEEDED. PROTSYM FILE MAY BE CORRUPTED\nDeployment Messages\n This section lists deployment errors and messages generated by InterTest and SymDump .\nCAVH100E\nCAVH100E\nTOMCAT HAS NOT BEEN INSTALLED\nReason:\nTomcat is not installed, or the Tomcat directory was not found at the specified location.\nAction:\nVerify that tomcat is installed, and that the specified directory location is correct.\n \n \n \nCAVH101E\nCAVH101E\nSERVER_DIR:$SERVER_DIR COULD NOT BE CREATED\nReason:\nUnable to create directory.\nAction:\nReview the job log for errors, address the errors, then retry the directory creation process.\n \n 1828", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "00f4c2078629-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\n \n \n \nCAVH102E\nCAVH102E\nERROR COPYING TOMCAT FILES\nReason:\nUnable to copy Tomcat files.\nAction:\nEnsure you have access rights to the directories, that the directories exist, and that enough space is available in the target\ndirectory.\nCAVH103E\nCAVH103E\nERROR COPYING FILE CAVHSVRX\nReason:\nThe file CAVHSVRX could not be copied.\nAction:\nEnsure you have access rights to the file, that the parent directory exists, and that enough space is available in the target\ndirectory.\n 1829", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "d7e5448d6fa4-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nAdditional Resources\nIncludes educational resources, product references, and support information.\nThis article provides product resources, including education, webcasts, support, and maintenance, to help optimize your\nproduct experience.\nEducation and Training\nUse the following links to learn more about this product:\n\u2022Broadcom Mainframe Education\n\u2022Broadcom Mainframe Education YouTube Channel\nProduct Support\nUse the following resources for product support:\n\u2022Broadcom Support  for InterTest for CICS\n\u2022Broadcom Support  for InterTest Batch\n\u2022Broadcom Support  for SymDump  for CICS\n\u2022Broadcom Support  for SymDump  Batch\nMaintenance\nUse the following resources for maintenance requirements:\n\u2022Maintenance Grid\n\u2022Mainframe Common Maintenance Procedures\nUser Communities\nConsult your peers, reach out to subject matter experts, and read the latest technical insights and information in our global\ncommunities:\n\u2022InterTest Community\n\u2022SymDump  Community\nSocial Media\nUse the following social media resources to connect with the Broadcom Mainframe Software Division global community:\n\u2022Broadcom Mainframe Software on Twitter\n\u2022Broadcom Mainframe Software on Linkedin\n 1830", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aacc628c599b-0", "text": "InterTest\u2122 and SymDump \u00ae 11.0\nDocumentation Legal Notice\nThis Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred\nto as the \u201cDocumentation\u201d) is for your informational purposes only and is subject to change or withdrawal by Broadcom\nat any time. This Documentation is proprietary information of Broadcom and may not be copied, transferred, reproduced,\ndisclosed, modified or duplicated, in whole or in part, without the prior written consent of Broadcom.\nIf you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make\navailable a reasonable number of copies of the Documentation for internal use by you and your employees in connection\nwith that software, provided that all Broadcom copyright notices and legends are affixed to each reproduced copy.\nThe right to print or otherwise make available copies of the Documentation is limited to the period during which the\napplicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your\nresponsibility to certify in writing to Broadcom that all copies and partial copies of the Documentation have been returned\nto Broadcom or destroyed.\nTO THE EXTENT PERMITTED BY APPLICABLE LAW, BROADCOM PROVIDES THIS DOCUMENTATION \u201cAS\nIS\u201d WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF\nMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL\nBROADCOM BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT,\nFROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST\nINVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF BROADCOM IS EXPRESSLY\nADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.\nThe use of any software product referenced in the Documentation is governed by the applicable license agreement and", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}
{"id": "aacc628c599b-1", "text": "The use of any software product referenced in the Documentation is governed by the applicable license agreement and\nsuch license agreement is not modified in any way by the terms of this notice.\nThe manufacturer of this Documentation is Broadcom Inc.\nProvided with \u201cRestricted Rights.\u201d Use, duplication or disclosure by the United States Government is subject to the\nrestrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)\n(3), as applicable, or their successors.\nCopyright \u00a9 2005-2022 Broadcom. All Rights Reserved. The term \u201cBroadcom\u201d refers to Broadcom Inc. and/or its\nsubsidiaries. All trademarks, trade names, service marks, and logos referenced herein belong to their respective\ncompanies.\n 1831", "source": "/Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf"}