We had the various CA DB2 Tools and Utilities (ie copy, reorg, load, unload, rc/query, etc.) but for various reasons we've decided to eliminate all of them except CA Insight/Sysview for DB2. We removed the various authcodes including RY for Fast Load but have found that users can still run Fast Load jobs without errors. Fast Unload does fail with RC=8 and a message saying the product isn't authorized.
We want to make sure we're not breaking any rules and don't want our users to be able to use Fast Load but haven't been able to figure out how to make that happen.
Does anyone know how to disable Fast Load for DB2?
2 thoughts – 1) run a strobe or some other product during a fast load execution and see what executables are reported – rename those executables ( you can always rename back that are used by other processes)
2) delete everything and re-install only the product you want to keep
Technology Architect, Database Infrastructure Services
Technology Solution Services
123 East Main Street
Louisville, KY 40202
(502) 476-2538 or 407-7266
Chris has some excellent suggestions in his prior post for this concern.
If you are specifically interested in disabling CA Fast Load you could renaming the parser module, FLL$PSE, in hlq.CDBALOAD and the CA Fast load job would fail with the following:
CSV003I REQUESTED MODULE FLL$PSE NOT FOUND
Another option would be to FREE the utilities plan or rename the utilities plan entry in the PLANSxx member
of hlq.CDBAPARM. The utilities plan is defined on the DGLPLN01= entry. The CA Fast Load job would then
PUT0014E - CAF Error: PLAN NAME: DGL1xxxx WAS NOT FOUND IN DB2 SUBSYSTEM ssid
Hopefully you will find one of these options helpful.
CA Technical Support
Thanks to everyone for the suggestions. We figured out a way to disable Load. We ended up commenting out the following line in the PLANS00 member:
DGLPLN01=DGL1P180 PUT General Utilities Plan
Once this was done, the CA Load job failed with RC=8 and the following error:
PUT0014E - CAF Error: PLAN NAME: DGL1PLAN WAS NOT FOUND IN DB2 SUBSYSTEM DB2R
We thought this was the safest and easiest way to do this since re-enabling the plan is a matter of uncommenting the line if we find it's needed for some reason.
Thanks again for taking the time to make suggestions on this.