legacy-ibmi-runtime-evidence-miner

To extract runtime evidence from IBM i job logs and spool files, you need an approved evidence manifest, redacted job logs, and inventory mappings. The extraction process outputs a structured runtime-evidence.jsonl file containing call sequences, error patterns, and timing observations.

Runtime evidence extraction from IBM i job logs is the process of parsing structured observed-in-runtime data to identify program behavior and system operations. It captures call sequences, error patterns, and timing observations to provide insights into nightly billing jobs and other operations.

Yes, you need Python and IBM i access to analyze job logs and spool files for runtime evidence extraction. The process also requires approved evidence manifests, redacted job logs, and inventory mappings to successfully parse and extract structured runtime data.

The file format used for structured runtime evidence output from spool file analysis is JSONL (runtime-evidence.jsonl). This format contains the extracted call sequences, error patterns, and timing observations parsed from the analyzed IBM i job logs and spool reports.

Yes, you can analyze spool file report structures and content from IBM i systems. The spool file analysis feature extracts structured observed-in-runtime evidence from approved spool files and report files, providing insights into program behavior and system operations.