|
View previous topic :: View next topic
|
| Author |
Message |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
did You read the whole topic ... looks like not 
count how many times we have asked for the proper info
hoe many time the ts has posted useless info
( I deleted three posts with the same garbage content)
| Quote: |
| The cobol module splices 2 i/p files into a VB file.The data in the i/p files is same before and after the run.just we reduced the LRECL of the O/P VB file and the CPU execution time reduced drastically. |
it' s the TS who is offending/disrespecting the people who try to help him
on our own time, free of charge
the category/tone belong to the natural reaction of somebody sharing its experience
and spending ( rather wasting) time to help somebody who does not care to provide proper info
and keeps posting/venting the same useless information
but maybe it' s the free of charge that make people ask without any commitment ti properly pursue the issue |
|
| Back to top |
|
 |
Ronald Burr
Active User
Joined: 22 Oct 2009
Posts: 293
Location: U.S.A.
|
|
|
|
Perhaps the TS did NOT use the APPLY WRITE-ONLY clause for the file (or specify compiler option AWO), and thus a simple change in the LRECL (with NO change to the BLKSIZE) WOULD have made a significant impact on performance.
The Programmer's Guide says:
"Use the APPLY WRITE-ONLY clause to make optimum use of buffer and device space when you create a sequential file with blocked variable-length records. With APPLY WRITE-ONLY specified, a buffer is truncated only when the next record does not fit in the unused portion of the buffer. Without APPLY WRITE-ONLY specified, a buffer is truncated when it does not have enough space for a maximum-size record. The APPLY WRITE-ONLY clause has meaning only for sequential files that have variable-length records and are blocked. The AWO compiler option applies an implicit APPLY WRITE-ONLY clause to all eligible files. The NOAWO compiler option has no effect on files that have the APPLY WRITE-ONLY clause specified. The APPLY WRITE-ONLY clause takes precedence over the NOAWO compiler option. The APPLY-WRITE ONLY clause can cause input files to use a record area rather than process the data in the buffer. This use might affect the processing of both input files and output files."
With NOAWO and a 32K LRECL (with the REQUIRED 32K+4 BLKSIZE), one is guaranteed that there will be only 1 record per physical block regardless of actual record lengths.
With NOAWO and a 1K LRECL (with the SAME 32K+4 BLKSIZE), one is guaranteed that there will be at least 31 records per physical block, and perhaps a lot more).
With AWO (and the SAME 32K+4 BLKSIZE), the actual number of records per block would be totally independent of the STATED LRECL (which only represents the MAXIMUM possible LRECL), but would depend solely on the ACTUAL record lengths being passed to the I/O routines. |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
| Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
| Rahul_kumar wrote: |
...
Also,I [...] made a [change] in the program to calculate the record length [...] for each record.
... |
Why did you do this?
How did you do this?
How do think you were able to affect the record-length? |
|
| Back to top |
|
|
|
|
