Suite

Suite Definitions – Regression/Volume Illustration Overview Why zRTF? Architecture Overview Main Features Test Unit Recent Updates CMS/RTF cf. zRTF Logging Options Run Mode – Parallel Run Mode – Sequential Components Overview Maestro Phase Driver Logger Transaction Monitor Contact Information 2

Suite “Regression testing means re-running test cases from existing test suites to build confidence that software changes have no unintended side-effects. The “ideal” process would be to create an extensive test suite and run it after each and every change.” Regression Testing focuses on testing the changes introduced by a software change (Program/Module or Package)  Tracks and Compares the changes to the Output messages, database changes etc, due to a specific Transaction Volume Testing (Or Stress Testing) exercises several transactions simultaneously examining for “Gross Errors and over all system performance” 3

Suite Planned changes are made to system Input script is run again, producing new output log Baseline and second-run data are compared zTPF TPF PROGRAMS DATA Input Script Output Log 1 Events Input Messages 21 =? 2 zTPF PROGRAMS DATA 4

Suite zRTF assists zTPF installations in determining changes that have occurred on their zTPF system, when new programs and data are loaded zRTF runs in three phases, they are:  Phase 1 - Baseline phase to collect log data associated with the current production system  Phase 2 - Updated phase to collect log data associated with a new run with updated programs, etc.  Phase 3 - Compare phase of the log data between Phase 1 and Phase 2 to determine changes 5

Suite Integration tester, Regression tester or Volume tester. Prevents software with bugs getting loaded to production  Prevents REVENUE loss due to error software load to production. Money not lost is actually money saved  Identifies the Failed transactions and gives developers more detailed log file. Which helps developers to fix problems much faster and hence, saves DEVELOPER time –Log file will have - Error transaction, SO name, OBJ name, FUNC name, Displacement, Dump details, Macro trace etc. –Time saved is Money saved Can be used as Meticulous testing environment, for z- migration of application software 6

Suite zTPF VPARS - 2 TRN MONTR SERV zAPPLN s/w APM SERVE creates DRIVER II instanceTRANSACTION LOGGING running parallel PHASE I & PHASE II APM SERVE creates LOGGER instanceAPM SERVE creates DRIVER I instance USER ID (MAESTRO) APM SERVE PH1 DRIVER (worker m/c) LOGGER (worker m/c) zTPF VPARS - 1 TRN MONTR SERV zAPPLN s/w PH2 DRIVER (worker m/c) LOG DATA z/VM zTPFGI TCPIP IUCV AUTOLOG AND DISCONNECT 7

Suite GUI Interface integrated into zTPFGI Runs on VPARS PHASES I & II can be run in parallel  Hence, making it faster Two major modes of operations supported  RTST mode – Regression mode with detailed Logging Information  VTST mode – Volume test mode with minimal Logging Information Flexibility of running zRTF phases (parallel or sequential) Respective terminal type (ALC, 3270, SNA) with user chosen LNIATA is assigned to key in the input messages Brief DUMP details included in the log file (INS or Macro line, PSW, REGS and ECB page) Bouquet of compare and browse APIs Trace lines at Object level and C- function call levels Log files at Transaction level Log file management and Memory Management 8

Suite Test unit can have  Application Entries  PH1,  PH2,<ENTRIES  ZGICMD Entries  ZGICMS Entries Procedure to load the programs to PHASE II  PH2,ZGICMS $ZCMLOAD (SEL=N) 9

Suite zRTF is now integrated with zAUTOMATION  This allows zRTF to use VPARS from the pool during zRTF run and release VPARS back to pool once the test is complete. zRTF is now integrated with Product worker functionalities to execute ZGICMS and ZGICMD  ZGICMS, functionality allows user to invoke REXX EXEC from the test unit. EXEC can be a script with issuing zTPF Input and Interpreting zTPF Output, making decisions etc…  ZGICMD is used to set User preferences, execute zTPF inputs and Reallocate terminals etc.. zRTF compare utility is enhanced with more options and functionalities 10

Suite Test unit now supports specifying different formats of Inputs for PH1 and PH2  This enables user to test application entries, for which Input format as been changed. Test unit now supports specifying the list of programs (oldr file) to be loaded for PHASE II zRTF run. PC Interface is enhanced to provide the ability to right click on an Input file or RTFMSG file and initiate the RTF run. 11

Suite CMSTPF/RTFzRTF Runs TPF 4.1 ApplicationRuns zTPF Application Dependent on Debugger (CMSTPF)Independent of Debugger Sequential run alone SupportedParallel and Sequential run Supported No Compare APIsCompare APIs provided Applications dependent on external channels cannot be tested (If no CTFS) All applications can be tested One single LOG file for RUN or Transaction level LOG file Transaction level LOG file Log files are not in compressed formatLog files are in compressed format No bufferingBuffering to run faster No Summary Log infoSummary Log info included 12

Suite TRACE LOGGING  User can specify. –ALL Macros or Macro groups for which trace lines are required. –Macro Overrides to Skip or Include Trace line for a Specific Macro. –SO Name Overrides to log Macro trace line for specific SOs or to Skip Macro trace line for specific SOs. DATA LOGGING  User can specify –RECID’s for which data written to the file have to be logged or skipped. –TAPE Names for which data written to the TAPE have to be logged or skipped. 13

Suite RUNMODE  User can specify. –RUNMODE = VTST. Volume test mode, All the trace options are neglected and only, INPUT, OUTPUT and SUMMARY LOG messages are logged. –RUNMODE = RTST. Regression Test mode, All the trace options are considered and based on the log options specified by the user, respective log data is logged (INPUT, OUTPUT, TRACE LINE, DATA LOG and SUMMARY LOG) NOTE:  Irrespective of LOG OPTIONS and RUNMODE. Transaction ERRORS (SERRC/CTL errors) are always logged. 14

Suite zTPF VPARS - 2 TRN MONTR SERV zAPPLN s/w APM SERVE creates DRIVER II instanceTRANSACTION LOGGING running parallel PHASE I & PHASE II APM SERVE creates LOGGER instanceAPM SERVE creates DRIVER I instance USER ID (MAESTRO) APM SERVE PH1 DRIVER (worker m/c) LOGGER (worker m/c) zTPF VPARS - 1 TRN MONTR SERV zAPPLN s/w PH2 DRIVER (worker m/c) LOG DATA z/VM zTPFGI TCPIP IUCV AUTOLOG AND DISCONNECT 15

Suite Driver I starts running zRTF Phase IAPM SERVE creates LOGGER instanceAPM SERVE creates DRIVER I instanceAPM SERVE creates DRIVER II instance DRIVER I & DRIVER II USER ID (MAESTRO) APM SERVE DRIVER I (worker m/c) LOGGER (worker m/c) zTPF VPARS TRN MONTR SERV zAPPLN s/w DRIVER II (worker m/c) LOG DATA z/VM Driver II starts running zRTF Phase II zTPFGI TCPIP IUCV AUTOLOG AND DISCONNECT 16

Suite Autologs DRIVER I, DRIVER II and LOGGER VALIDATES and INTERPRETS configuration file Initiates PHASE run and LOG action Drives compare operation Monitors and Synchronizes operations between DRIVER and LOGGER Displays zRTF progress at any point of time during the RUN Capable to ABORT run 17

Suite SIGN ON, SIGN OFF to VPARS Runs zRTF PREPHASE  zTPF commands to setup an zRTF run  Ex. Program Load, Database Initialization, etc. Updates user LOGGING options to VPARS CONVERTS INPUT file to RTFMSG file Runs multiple RTFMSG files in SEQUENTIAL or ROUND ROBIN fashion Drives inputs in RTFMSG file one by one to VPARS to execute and LOG transaction data Updates RUN status to MAESTRO 18

Suite Logs both PHASE I and PHASE II Log Data Creates and maintains individual transaction log files Maintains log files in compressed format Uses IUCV protocol 19

Suite zTPF component or HOST component SIGNs ON or SIGNs OFF zRTF user to zRTF product Allocates terminals dynamically Executes zRTF PREPHASE commands to zTPF and sends response back to respective DRIVER Executes RTFMSG input to zTPF Builds LOG data, based on user options in config file Updates Transaction run status to DRIVER Sends LOG data to LOGGER 20

Suite For more information, contact: Thiru Thirupuvanam TPF Software, Inc