View - Question for Fully-Composed AFP Datastreams

Products

• View

Issue/Introduction

We have a fully composed AFP datastream ReportID with a NO-OP record and a DEST specified to send to another repository.

The report is failing when sent down from View, to an in-house procedure, with the error:

 DATA IN AN INPUT RECORD OR RESOURCE IS NOT VALID: RECORD LENGTH DOES NOT AGREE WITH LENGTH IN STRUCTURED FIELD INTRODUCER.

This error has been seen previously, where the issue turned out to be the LRECL specified in the JCL for the file did not match the length specified in the structured field introducer specified on the NO-OP.

When we do a manual reprint from View, and send the report through the procedure, it loads fine with no error.

Does a manual View reprint change the LRECL as opposed to automatically sending using a distribution dest via Deliver?

 

Environment

Release : 14.0

Component : View

Resolution

Neither Deliver nor View change the LRECL of a printed report.

The change in LRECL was found to be within the client's automated print procedure.

The client determined that they would have best results doing the printing with a SARBCH /EPRINT statement, where they can define the CLASS and DEST for the report.