Easytrieve Year-End Processing Projects

Year-end on the mainframe is a season not a single job. Finance closes the books. HR needs W-2 support registers. Tax prepares 1099 and informational returns. Auditors request YTD trial balance tie-outs. Regulators need annual statistical filings. Easytrieve programs that ran quietly all year become critical path—sorting twelve months of history, accumulating employee YTD earnings, producing proof listings penny perfect against tax engine output. Volume spikes, change freeze begins, batch windows extend past normal SLA, and every FINAL total faces external scrutiny. This tutorial describes year-end portfolio components, fiscal year parameterization, YTD accumulation patterns, tax support REPORT design, IRS file generation overview, reconciliation with payroll engine, archival and amendment workflows, operational runbook differences from daily and monthly jobs, and disaster recovery when year-end SORT abends at hour four. Beginners should study payroll and monthly report tutorials first—year-end composes those patterns at annual scale with compliance packaging on top.

Progress0 of 0 lessons

Year-End Portfolio Components

Common Easytrieve year-end deliverables
DeliverablePurposeAudience
YTD earnings registerEmployee wage proofHR and tax
Deduction summaryBox 12 and benefit validationTax vendor
1099 supportVendor payment totalsAccounts payable
Annual statisticalRegulatory filingCompliance
Archive extractMulti-year retentionAudit

INIT-YEAREND

text
1
2
3
4
5
6
7
8
9
10
INIT-YEAREND. PROC GET YEAREND-CTL IF CTL-CLOSE-STATUS NE 'FINAL' DISPLAY 'YEAR NOT CLOSED' STOP END-IF MOVE CTL-FISCAL-YEAR TO RPT-YEAR MOVE CTL-TAX-YEAR TO TAX-YEAR MOVE 'YTD EARNINGS REGISTER' TO RPT-TITLE END-PROC

Guard against running before finance final close—preliminary runs use PRELIM flag in TITLE for draft proof only. TAX-YEAR may differ from fiscal year for calendar tax reporting.

YTD Accumulation Pattern

Annual extract contains one row per employee per pay period or one consolidated YTD row per employee from payroll engine. If per-period rows, SORT by EMP-ID and REPORT CONTROL EMP-ID SUM GROSS NET TAX—accumulation in REPORT writer. If pre-consolidated YTD file, REPORT is formatting and validation not arithmetic. Mismatch between paths causes penny drift—document authoritative source.

text
1
2
3
4
5
6
7
8
9
SORT USING ANNUAL-PAY GIVING SORTED-YTD KEY EMP-ID ASCENDING END-SORT REPORT YTD-EARNINGS JOB INPUT SORTED-YTD CONTROL EMP-ID LINE EMP-ID EMP-NAME GROSS-YTD NET-YTD FED-TAX-YTD MASK MONEY-MASK SUM END-REPORT

Tax Support Versus Tax Filing

Support listings

Human-readable REPORT for HR review—employee can compare to last pay stub sum. Exception section lists negative amounts, missing SSN, zero gross with nonzero tax—VALIDATE in JOB before REPORT drives exception work file.

Filing files

Fixed-layout WRITE to IRS-1099-FILE per government spec—positions critical. Separate PROC per form type. Proof REPORT reads same file and prints interpretive listing for tax team—not sent to government.

Reconciliation With Payroll Engine

  1. Payroll engine produces authoritative YTD file.
  2. Easytrieve REPORT totals GROSS-YTD and NET-YTD FINAL.
  3. Compare to payroll control report hash—must match exactly.
  4. Employee-level compare on sample 500 employees.
  5. Sign-off document before tax vendor ingest.

Extended Batch Window Operations

Year-end SORT may run four to eight hours—allocate sufficient SORTWK space in JCL, monitor DASD free space weekly before season. Checkpoint restart from annual extract stage if SORT fails—do not re-extract from payroll production. On-call roster covers weekend runs. Change freeze means only pre-approved PTF—emergency fix requires tax director approval and parallel proof.

Amendment and Restatement

Post-filing correction produces AMENDED run with CTL-AMEND-VERSION incremented. TITLE prints AMENDED WATERMARK. Original year-end archive untouched. IRS correction files reference original control number per spec. Easytrieve INIT reads amendment control to include only affected employees when delta amendment supported.

Archival

Annual extract GDG retained per legal hold—often permanent for tax years. Report PDF and filing file stored with metadata FISCAL-YEAR TAX-YEAR RUN-VERSION. Catalog naming convention documented for auditors retrieving decade-old proof without operations heroics.

Year-End Versus Month-End

Scale and compliance differences
FactorMonth-endYear-end
VolumeOne monthTwelve months consolidated
External filingRareTax and regulatory
Change freezeNormalStrict
RuntimeHoursMay exceed shift
Error toleranceLowNear zero for tax

Disaster Recovery

If year-end abends, preserve SORT input and SYSOUT. Do not rerun payroll extract without understanding failure point. SORT restart from SORTWK if supported; else rerun SORT from annual extract. Document RTO in runbook—tax filing deadline immovable. DR LPAR full annual proof before production retry when logic changed.

Common Mistakes

  • Running before FINAL close status—draft numbers filed.
  • Tax year versus fiscal year confusion in filter.
  • Employee SORT missing—YTD split across duplicate CONTROL groups.
  • No payroll engine reconciliation—penny drift discovered at vendor.
  • Overwriting amended archive without version.

Explain It Like I'm Five

At the end of the school year the principal makes a big report card for the whole year—not just one month. The government wants a copy to make sure taxes are fair. Year-end processing is that whole-year report, checked many times, saved forever, and fixed with a clear amended label if someone finds a mistake later.

Exercises

  1. Write INIT-YEAREND with close status guard and STOP.
  2. Design YTD REPORT with EMP-ID CONTROL and SUM fields.
  3. List payroll reconciliation steps before tax vendor handoff.
  4. Describe amendment versioning for post-filing fix.
  5. Compare year-end batch window planning to daily SLA.

Quiz

Test Your Knowledge

1. Year-end Easytrieve jobs typically process:

  • Full fiscal or calendar year transaction history
  • Single day only
  • Compiler output
  • CICS maps

2. Fiscal year parameter comes from:

  • Year-end control file with FISCAL-YEAR and close status
  • SYSDATE only
  • JCL name
  • MACRO

3. W-2 support reports often:

  • Summarize earnings and deductions by employee for tax year
  • List compiler options
  • Print PF keys
  • Skip validation

4. Year-end batch window differs because:

  • Longer runtime and stricter change freeze tolerated
  • Jobs run faster
  • No FILE needed
  • SCREEN only

5. After year-end filing lock:

  • Reports archived immutable; corrections use amended run
  • Silent overwrite
  • Delete source
  • Skip archive
Published
Read time18 min
AuthorMainframeMaster
Reviewed by MainframeMaster teamVerified: Broadcom Easytrieve year-end REPORT YTD accumulation patternsSources: Broadcom Easytrieve 11.6 Report Generator; mainframe year-end tax and close practicesApplies to: Easytrieve year-end processing real-world projects