Hopefully he is still monitoring the thread.

-----Original Message-----
From: Lizette Koehler [mailto:stars...@mindspring.com] 
Sent: Wednesday, December 05, 2012 10:59 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Multiple HSM in one LPAR ?

That was what Miklos Szigetvari asked originally.  I was just trying to get an 
answer for him

Lizette

> 
> Lizette,
> 
> Is Setsys debug what you're looking for?
> 
> Setsys debug
> Enable exits to test
> Test function using exits
> Disable exits
> Setsys nodebug
> 
> Release Hardcopy
> Examine activity logs for the effects of testing exits.
> 
> No need for a second HSM.
> 
> -----Original Message-----
> From: Lizette Koehler [mailto:stars...@mindspring.com]
> Sent: Wednesday, December 05, 2012 10:28 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Multiple HSM in one LPAR ?
> 
> Glenn,
> 
> Is there any safe way to test HSM exits without having a TEST LPAR?  
> So if I only had an LPAR but needed to validate my code for an HSM Exit, any 
> way to do that safely?
> Or would it be safer to bring up a new sysres set with the exits?  Or 
> a new LPAR for testing?
> 
> Thanks
> 
> Lizette
> 
> 
> > -----Original Message-----
> > From: IBM Mainframe Discussion List 
> > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Glenn Wilcock
> >
> > No.  You should not attempt to start two distinct HSMs within the 
> > same LPAR.  Multiple HSMs within the same LPAR are only supported 
> > when they share the same control data sets and the secondary hosts 
> > are started with the HOSTMODE=AUX parameter.  A good example of why 
> > you can't have distinct HSMs is Recall.  HSM intercepts Open 
> > requests for migrated data sets and recalls them.  You can't have 
> > two distinct HSMs fighting over a Recall.  That is just one issue of 
> > many (serialization on functions & data sets, other intercepts, etc)
> >
> > 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

----------------------------------------------------------------------
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

Reply via email to