Skip to content

clibjes2: jesprint cannot read the active SYSLOG from spool #4

Description

@mgrossmann

jesprint() cannot read the active SYSLOG from the JES2 spool (blocks mvslovers/mvsmf#145).

Findings (MVS 3.8j): jesjob(jes,"SYSLOG",FILTER_JOBNAME,1) finds the SYSLOG STC (STC00085) with DDs dsid 101-105 after WRITELOG/WRITELOG H. All report records=0 but mttr!=0 (e.g. dsid=102 mttr=558081) -> spool blocks are physically present. jesprint is record-count independent (follows the spool chain from jesdd->mttr via block->next) yet returns ZERO lines per SYSLOG DD.

Hypothesis: breaks early in the block loop (jesprint.c ~105-111) -- spool_read fails for SYSLOG blocks, or block jobkey/dsid mismatches the STC job (SYSLOG blocks keyed differently).

Next: instrument the jesprint loop (wtodumpf already present); determine SYSLOG spool block keying; add a read path / jesprint variant for system datasets.

Impact: unblocks reading the real SYSLOG (deep history) for mvsMF endpoint 4 (today MTT-window only).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions