How can you have a DB stored procedure access a VSAM file without having to open the file every time the procedure is called? I have a stored procedure written in COBOL, which accesses a VSAM file. It runs in a DB2-established address space. It looks like every time the procedure returns, the VSAM file is closed. Is there a way to keep the VSAM file open even after the stored procedure returns, so the next time the procedure is called it won't have to waste time opening the file again.
I don't know any way around this other than to convert the VSAM file to a DB2 table. But, of course, your VSAM file is probably being used for other purposes, so this might not be a viable option.
Dig Deeper on IBM DB2 management
Our expert suggests that the best way to pass the SAP BW exam is to have hands-on job experience. But that's not all he has to say about ...
To export data from a DB2 table to a flat file, you need to run an export specifying the proper file format. The export utility exports data from a ...
Craig Mullins recommends two specific resources for learning how to create and support Binary Large Objects (BLOB) in DB2.