CICS TS for VSE performance impact when using invalid VSAM file names
Ingolf24 120000DRN3 Visits (2435)
Today a CICS TS performance tip:
If you pass an 8 byte VSAM file name, e.g. "VSETESTC", you may see more CPU cycles than it should.
Reason: A valid VSAM file name should have a maximum of 7 bytes and a space as documented in the CICS Application Programming Reference (of the CICS bookshelf). An invalid specification causes CICS to spend some more CPU cycles to resolve it.
If you change the program to use a correct "7 bytes + space" file name, e.g. "VSETEST ", you can avoid such overhead.
Your program runs faster.
The old CICS/VSE was more tolerant of the wrong length file name. You may consider that, if you are still on CICS/VSE and plan to migrate to CICS TS.
Enjoy your weekend.
This weekend becomes hot in some areas of Germany - up do 40 C (about 100 F).