Hi
Thank you Lizette and Glenn.
As we have a separate test LPAR, seems to me easier to test independent
in a unique system.
If we are here , maybe to ask Glenn how the the actual communication is
working between a requester (RECALL or MIGRATE etc) and the HSM address
space
On 05.12.2012 22:27, Glenn Wilcock wrote:
Hi Lizette,
If the intent is to test a different version of an Exit, then there is a
possibility. I've never verified that this works, but it's something that may
be tried...
Use the MASH support to start an AUXILIARY HSM. (Yes, I know, our
documentation needs to be improved regarding MASH). For the AUXILIARY HSM
host, define the startup procedure with a STEPLIB of a library containing the
desired exits, that are unique from the STEPLIB specified for the MAIN HSM
host. A second library would need to be specified that contains the other
common modules (DFSMSdss, etc). This should enable the AUX HSM to use unique
exits. If the Exits reference the MCVT control block, then they need to be
updated to use the QCT to access the correct MCVT.
Note that the Control Data Sets will be the active ones, so all testing will
need to be mindful of any impact that will occur to the live CDSes.
Glenn Wilcock
DFSMShsm Architect
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
