
Many modern tape drives can record faster than disk will for saves. The ’streaming’ technologies are examples of how tape drives have improved in the past couple decades. Where SAVFs can help is with multiple concurrent saves.
JOBQ(QSPL)
Using the QSPL job queue is possibly a bad choice. Consider using a job queue that routes to a work management configuration that much better suited for save operations.
Tom

IBM offers virtual tape systems, the big thing you would notice about theirs is the sheer horsepower or disk power behind them. Many are using dasd that will rival your own main systems disk storage and as well typically have as much processing power. The speed of saving to disk is going to have to have all parts either matched or the system you are saving to will have to be faster to see any improvement over tape.
To save start at AS400( disk read speed –> seek time –> cache –> throughput to controller –> throughput to enclosure –> throughput to dasd or san —> throughput from san controller to cache –> size of cache and overflow to disk ) whichever piece is slowest thats where your savf will slow down.
Explain to your boss, tape costs so much money because the tech that makes it fast doesnt come cheap. You cant just throw in a small san and expect it to move faster than tech that was developed to back up tons of data as quickly and reliably as tape and expect it to easily outperform it.

















