APAR status
Closed as canceled.
Error description
The items listed below can be used to maximize the FIS throughput numbers. 1. Priority relationships between CPCS 1.11 / CIMS Primary / CIMS Secondary/ and Format Image Statements. CPCS 1.11 and the CIMS Primary communicate with each other and therefore should be set up with equal priority in the MVS/ESA operating system. In addition their overall priority within the MVS/ESA operating system should be above average. CIMS Primary and CIMS Secondary communicate with each other, however due to the higher demand for CPU and I/O during the Capture Process (Secondary) the CIMS capture address space should have a priority one lower than CPCS 1.11 and CIMS Primary Address Space. This will prevent the CIMS Capture address space from preempting the CPCS 1.11 and CIMS Primary Address spaces. The priority for the Format Image Statements should be one lower than the CIMS Primary. 2. Isolate all files (including MIPF, ASF, PGM STATS) to unique DASD units. Do the same for work files if you are not using Virtual Input/ Output. 3. Use Virtual Input / Output for work files. (VIO) 4. Use BUFNO=25 parameter on the DCB Keyword in the Run JCL for Statement Print File, Merge Image Print File and Suspense File. 5. Increase region size to 0 Meg. This will request all available memory. 6. Use 3 or 4 subtasks per Image processor for maximum IP utilization. 7. For System utilization assume ... a. 7.0 Meg. Virtual Memory Per Subtask. b. 0.5 Meg. Real Memory Per Subtask. c. 0.5 Meg. Virtual Memory Once Per FIS JOB. d. 1.5 MIPS Per Subtask. 8. Use a large (TRK) Control interval size for the Account Summary File unless SIS contention is a problem. 9. If DLIP Resend messages are being received in the JES Log, make the following changes in your ALS MACRO - ELRXMBEG (The channel interface configuration table begin macro.) a. ELRXIASZ - from 40 to 24. b. ELRXIBSZ - from 40 to 24. 10. If you have multiple 3898 Image Processors, set up LAN Communications record sysin file (LANCOM) for maximum utilization of each IP. The FIS task controller assigns each subtask an IP to use by using the LANCOM field 'HPS004-FIS-LANCOM-IPU-INFO'. Each subtask will be assigned the next IP in the array. If not enough IPs are listed, the first IP will be assigned to the remaining subtasks. Therefore, specify enough IPs in the array as you have subtasks. Listing extra IPs will cause no harm. For example, if you have two IPs (PU000001 and PU000002) 5 FIS subtasks and a application host logical unit number 'STMTAHLU', the following is an efficient LANCOM: | | | | | STMTAHLU|PU000001|PU000002|PU000001|PU000002|PU000001 11. Make sure that all like Produce Codes (denoted in the hea markers) are grouped together in the Statement Print File Grouping statements will reduce the number of DB2 calls. 12. Output of FIS (Merged Image Print File) can be written to DASD instead of JES (i.e. make sure they are writting to a file and not SYSOUT). Keep in mind that this will incr performance for the FIS run, but the time to spool this f to print will still take time). 13. 486 upgrade: should see a 33% increase in the # of images processed). 14. VIO for workfiles: 5 - 10% increase. 15. For printing: DASD Fast Write / use of Cache: this affects spool time. TRKCELL = 10: provides a significant increase for despool time. 568815701, 568815702, FIS, PERFORMANCE, THROUGHPUT STATEMENTS
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
TIPS TO HELP CUSTOMERS FINE-TUNE HPTS STATEMENTS FIS PERFORMANCE
APAR Information
APAR number
II08030
Reported component name
PA LIB INFO ITE
Reported component ID
INFOPALIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1994-07-01
Closed date
1994-07-01
Last modified date
1994-07-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG32M","label":"APARs - VSE\/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]
Document Information
Modified date:
14 December 2020