zRTF R egression T est F acility

1. zRTFRegression Test Facility

2. Contents • 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

3. Definition: Regression/Volume “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”

4. zTPF TPFPROGRAMS zTPFPROGRAMS DATA DATA 2 1 2 =? Illustration Input Script Input Messages OutputLog 1 Events Planned changes are made to system Input script is run again, producing new output log Baseline and second-run data are compared

5. Overview • zRTF assistszTPFinstallations in determining changes that have occurred on theirzTPFsystem, 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

6. Why zRTF? • 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

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

8. Main Features • 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

9. Test Unit • Test unit can have • Application Entries • PH1,<ENTRIES> • PH2,<ENTRIES • ZGICMD Entries • ZGICMS Entries • Procedure to load the programs to PHASE II • PH2,ZGICMS $ZCMLOAD <loadset name> <oldr path> (SEL=N)

10. Recent Updates • 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 issuingzTPFInput and InterpretingzTPFOutput, making decisions etc… • ZGICMD is used to set User preferences, executezTPFinputs and Reallocate terminals etc.. • zRTF compare utility is enhanced with more options and functionalities

11. Recent Updates • 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.

12. CMSTPF/RTF cf. zRTF

13. Logging Options • 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.

14. Logging Options • 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.

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

16. zTPFVPARS zAPPLN s/w SERV TRN MONTR APM SERVE TCPIP IUCV AUTOLOG AND DISCONNECT Run Mode - Sequential DRIVER I & DRIVER II z/VM DRIVER I (worker m/c) LOGGER (worker m/c) zTPFGI LOG DATA USER ID (MAESTRO) DRIVER II (worker m/c) APM SERVE creates DRIVER II instance APM SERVE creates DRIVER I instance APM SERVE creates LOGGER instance Driver II starts running zRTF Phase II Driver I starts running zRTF Phase I

17. Maestro • 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

18. Driver I or II • SIGN ON, SIGN OFF to VPARS • Runs zRTF PREPHASE • zTPFcommands 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

19. Logger • 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

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