Suppose that your application makes connections to two different DB2® for z/OS® subsystems. You could capture the SQL statements that run against those connections into one pureQueryXML file. However, you will not be able to create and bind DB2 packages that contains SQL statements for both connections.
If you want to run the SQL statements statically, you must capture the SQL statements in two separate pureQueryXML files, one for each connection. In your application, you modify the URLs for making the two connections. Those URLs now look like this:
jdbc:db2://sys01:500/DB2M:pdqProperties=captureMode(ON),pureQueryXml(capture_sales.pdqxml);
jdbc:db2://sys01:501/DB2Q:pdqProperties=captureMode(ON),pureQueryXml(capture_employee.pdqxml);
The first URL tells pureQuery to capture SQL statements in the file capture_sales.pdqxml, and the second URL specifies to capture SQL statements in the file capture_employee.pdqxml. If the files do not yet exist when you run your application to start the capture process, pureQuery creates them.
If you do not want to create both pureQueryXML files at the same time, you can modify one URL, capture SQL statements in one pureQueryXML file, and then modify the second URL later.