EPV zParser Modernization Guide

zParser processes SMF records, IMS log records, and IDCAMS DCOLLECT data. It stores the processed data in SQL databases for reporting and analysis.

zParser is written in Perl and can run on any platform that supports Perl, including z/OS UNIX, UNIX, and Microsoft Windows.

zParser uses configuration files to define data mappings and processing rules. These files specify how SMF records and other data sources are transformed and loaded into the SQL database.

zParser supports storing processed data in various SQL databases, including DB2, Oracle, and others accessible via Perl's DBI module.

The core component is the Perl script that parses SMF records and other data sources. It uses configuration files to determine how to process and transform the data before loading it into the SQL database.

zParser uses Perl's DBI module to connect to and interact with SQL databases. The configuration files specify the database connection parameters.

zParser does not expose a REST or SOAP API. Integration is typically achieved through direct database access or by invoking the Perl script from other applications.

zParser relies on the underlying operating system and database security mechanisms for authentication and access control. It does not implement its own authentication methods.

zParser provides valuable insights into system usage and performance by processing SMF records and other data sources. This information can be used for capacity planning, cost allocation, and identifying performance bottlenecks.

By storing processed data in SQL databases, zParser enables users to generate custom reports and perform ad-hoc analysis using standard SQL tools.

zParser can help organizations optimize their IT infrastructure by providing detailed information about resource consumption and usage patterns.

zParser leverages the security features of the underlying operating system and database. It does not implement its own security mechanisms.

Access to the SQL database containing the processed data should be controlled using database-level security mechanisms, such as user accounts and permissions.

zParser relies on the audit and logging capabilities of the underlying operating system and database. It does not provide its own audit logging.

zParser is typically deployed by configuring the Perl script and associated configuration files on a system with access to the SMF records and the SQL database.

Monitoring zParser involves checking the execution logs of the Perl script and monitoring the database for any errors or performance issues.

Configuration parameters include database connection details, data mappings, and processing rules. These are typically defined in the configuration files.

zParser relies on the logging capabilities of the underlying operating system and Perl environment. It does not have built-in logging mechanisms.