Download
1 / 19
200 likes | 427 Views
Logger. Collect Statistics and Debugging information. Logger - Concepts. Component of zTPFGI and other TPF Software products Collects statistics, debugging information on a global level and other information specific to products and sends it to a common data repository
E N D
Logger Collect Statistics and Debugging information
Logger - Concepts • Component of zTPFGI and other TPF Software products • Collects statistics, debugging information on a global level and other information specific to products and sends it to a common data repository • Log data can be viewed using search criteria in zTPFGI
Logger • Test System Management • Helps operators to analyze the events happened in a test system • Gives information on the changes to the VPARS • System commands executed • System wide program load • Private program load • Core altered • File altered • Tool Management • Helps Tools Administrator to analyze the usage of the products • Debug problems in Products • Collect debugging information on Global Level • Helps us to narrow down to the problem
Log Server Components of Logger • Collect Log Data from: • VPARS • Worker • Save Log Data to Log Server • View Log Data in zTPFGI Data Worker Worker VPARS VPARS Admin
Components of Logger • Data Collection • Software part of the product is responsible for data collection and sending it to the server to save the data in a common place in VM. • Log Server / Data Repository • The collected data are stored in the common Data repository. Log Server is a VM machine always listening for the Log data from either the VPARS or the Worker Machine for the log data. The server refers to the configuration file to determine the location of each type of log data and also for the house keeping activities for each log type. • Report Generator • An utility is been provided in zTPFGI to generate report on the log data based on the filters provided by the administrator. There are no separate steps to install this component. The utility comes as a part of zTPFGI.
Data Collection • zTPFGI (ZIG – Host component) • Usage • Users • User Login and Logout time • Terminals Allocated to the user • Transaction Count • Products/Components • Activation and deactivation time for each product • Global Trace • Trace data – system trace • Audit • System commands executed by end users • System wide program load by end users • Private program load by end users • Core alters by end users • File alters by end users
Data Collection • zAutomation • VPARS usage up by zAutomation • VPARS used by whom • VPARS used for what purpose (ZIG, zRTF) • Etc. • Commands executed by zAutomation to bring up the VPARS • Commands used on the VPARS • Times VPARS put to sleep / wake up
Data Repository • PDWDATA (PRODUCT DATA REPOSITORY) • Data repository for zTPFGI components • Virtual Machine ID – usually PDWDATA • Trace Logs, Usage Logs, Audit Logs and other data files that are created by the various other products (RTF, DFX etc) of zTPFGI suite are saved. • PDWDATA VM ID has to be allocated to the SFS (Shared File System) Pool.
Log Server • Always running and listening to all the z/TPF VPARS test systems that are running the zTPFGI host server. • Listens on an IUCV Connection. • The zTPFGI Products (ZIG Debugger, RTF, DF Explorer) running under z/TPF Test systems send Information such as Trace Logs, Audit Logs, Usage Information and other product specific data that needs to be saved. • Receives messages from the various z/TPF systems running zTPFGI and saves the Information in specific files depending upon the message types. • Configuration files to instruct LOG Server on the destination path and file names based on type of log data • TSSLOGP is the PRODUCTION Logging Virtual Machine. • TSSLOGT is the test Logging Virtual Machine.
Log Server Configuration File • Location in the data repository • Path : Path where the data to be stored in Data Repository • House Keeping Parameters • Retention : Maximum number of retention to be maintained • Maxfiles : Maximum number of files to be created • Maxlines : Maximum number of lines in a file
Configuration File Sample [VPZTPF1] [VPZTPF1] AUDIT.RETENTION = 45 AUDIT.MAXFILES = 2 AUDIT.PATH = <sfspool>:PDWDATA.AUDIT.TEST.VPZTPF1 ' GLOBTRACE.RETENTION = 5 GLOBTRACE.MAXLINES = 10000 GLOBTRACE.PATH = <sfspool>:PDWDATA.GLOBTRACE.TEST. ' USAGE.RETENTION = 30 USAGE.MAXLINES = 1000 USAGE.MAXFILES = 2 USAGE.PATH = <sfspool>:PDWDATA.USAGE.TEST.VPZTPF1
Log Files • Naming Conventions of the data file • File name – YYYYMMDD • File type • First three characters – Message type • Last Five characters – running number to denote the Nth file for that message type on that day • GTR – GTR00001 • AUDIT – AUD00001 • USAGE – USA00001 • AUTOMATION – ATS00001 ATS00002 Eg: 20100601 GTR00001
Report Generator • Component of zTPFGI that helps Administrators to view the required logged data in more readable format. • Bring in the SFS directory where the log data is residing to the Host View in zTPFGI • Right click on the log file and choose the ‘Log Viewer’ option to open the dialogue box to key in the filters to look at the log data.
