IBM eServer iSeries Support: Software Technical Document : 10064916
All high-level language programs (HLLs) use blocking at certain times and use single record I/O at other times, based on program specifications. Because blocking takes less system resources to perform a single I/O, a program that blocks performs better and uses less system resources. The default for the HLL uses record blocking if opening a file for output only (write) or input only (read). The programmer is expected to override the file or use larger blocks if the default is not appropriate. The HLLs do single I/O if files are opened for both input/output or update/delete. Blocking works well only if one reads many records sequentially because the block of records read are from some position in the file and the next N records. If one is going to position randomly within the file (CHAIN or set lower limit (SETLL) in RPG) and then read only two records, blocking may actually be a waste of system resources as the read after the random position reads a single record; however, the next read reads a block of records and the program reads only one.
The parameter on the override command that expresses the intent to block is sequential only (SEQONLY) to emphasize that the intent is to read some number of records in a row (you choose the number). Sequential only does not preclude the program from doing random positioning; however, remember the system reads an entire block of records when the second READ is run after the position (the first read accesses a single record only).
Thursday, January 20, 2005
- Journaling for Performance
- AS400 PRTF - Report Layout Utility
- RIAA sues the dead | The Register
- AS400 / ISeries Freeware / Shareware
- ibm as400 manuals v5r4
- Javalobby - Java J2EE Programming Forums - Coldtags suite 2.1: 210+ custom JSP tags
- Creating an as400 Query
- as400 Iseries Tips
- AS400 APIs
- AS400 API - QCMDEXC - Execute Command