View - Reports in View don't have same LRECL or format as created in the application job
search cancel

View - Reports in View don't have same LRECL or format as created in the application job

book

Article ID: 231623

calendar_today

Updated On:

Products

View

Issue/Introduction

Batch reports stored in VIEW have different LRECL and/or format than when it is created in the cycle.  This causes issues when retransmitting reports through SPOOL.

Normal batch cycle sends reports in SPOOL, and stores them in VIEW as well.  The SPOOL report transmit is the correct LRECL, but what is stored in VIEW is different.  When reports are lost, or need retransmitted, then reports are different.

Environment

Release : 14.0

Component :

Resolution

If the overall LRECL of what is being created in the application program is LRECL=200, if the last non-blank character in the record comes before position 200, then View (as designed) truncates the trailing blanks. 

If trailing blanks are a necessity on reprints, it is suggested that a reprint be done to a dataset with a DCB=(RECFM=FB, LRECL=200, BLKSIZE=2000), as then View will pad the records with the trailing blanks. 

Or, you can have the application write, in one of the records, something non-blank in the 200th byte, so that View will use that record as its largest record, and pad the rest of the records with blanks.