Who's On?

	Membership:
	Latest: Lauren Beeker
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5222

	People Online:
	Visitors: 66
	Members: 0
	Total: 66

Name	Points
Greg Moeller	4184
David Williams	3349
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1377
Roger French	1315
mark.cook	1244
Chris Martin	825

Creating a custom Errors report

5 Replies

0 Subscribed to this topic

18 Subscribed to this forum

Sort:

Author

Messages

Woozy

Veteran Member

Posts: 709

New Poster

4/2/2012 5:12 PM

I am building a custom batch program and I want to add a secondary report (i.e for errors) to the Print Manager output for this report.

I added another $REPORT section to my .rpt file, and it included the error report as part of the .prt file rather than as a separate file and separate Print Manager record. Is there some trick to creating it as a separate file?

Thanks!

Ragu Raghavan

Veteran Member

Posts: 477

New Poster

Engaged Poster

Avid Poster

Engaged Reader

Avid Reader

4/2/2012 5:55 PM

Did you also add a file in workdef and assign this file to the new report?

Woozy

Veteran Member

Posts: 709

New Poster

4/2/2012 6:13 PM

Yes, I did. When I did that, then I get "No XRef for RptSub(1) to iXFFXRef file" errors. I haven't been able to find squat about that error.

Cindy Ashwell

New Member

Posts: 2

4/2/2012 6:40 PM

Look in the
Application Development Workbench Standards
Here's one of my examples.
****************************************************
$REPORT ZH210-R2
****************************************************
$PRINTFILE EXTRARPT
.
.
.
$ENDRPT

Work File Definition

Product Line TEST File Record Yes
System Code ZH Sort File No
Program Code ZH210 File Media Printer
File Name EXTRARPT Value/WsFld Id
Prefix File Status

Field Name Occurs Type Size 250

EXTRARPT-REC Alpha 250

Woozy

Veteran Member

Posts: 709

New Poster

4/2/2012 7:01 PM

Yep - that's exactly what my workdef looks like, except for the string length.

Woozy

Veteran Member

Posts: 709

New Poster

4/3/2012 1:56 PM

UGH! I'm a dork! I deleted my "old" job and created a new one and it worked fine. Of course.

Thanks for all your ideas, in any case!

Kelly