Mark,

Are you going to a hosting DR recovery site , I.e.; Sungard ..
If so, they also usually are pretty good to help out..


Scott Ford
Senior Systems Engineer
www.identityforge.com



On May 2, 2012, at 9:46 AM, Mark Jacobs <[email protected]> wrote:

> We don't, yet. It's only used for XCF sysplex partitioning activities. I'll 
> keep it in mind, but I'm not going to worry about it for a DR test.
> 
> Mark Jacobs  
> ________________________________________
> From: IBM Mainframe Discussion List [[email protected]] on behalf of Gary 
> DiPillo [[email protected]]
> Sent: Wednesday, May 02, 2012 9:34 AM
> To: [email protected]
> Subject: Re: zOS under zVM
> 
> I did not see this mentioned, but, if you use BCPII, it will not be available 
> in your Guest:
> 
> HWI010I BCPII DOES NOT OPERATE ON A VM GUEST. BCPII INITIALIZATION
> IS HALTED.
> 
> If you use BCPII for critical processes you may need a rethink.
> 
>> Thanks for confirming my own research on the subject.
>> 
>> Regards,
>> 
>> Mark Jacobs
>> ________________________________________
>> From: IBM Mainframe Discussion List [[email protected]] on behalf of Mary 
>> Anne Matyaz [[email protected]]
>> Sent: Wednesday, May 02, 2012 9:07 AM
>> To: [email protected]
>> Subject: Re: zOS under zVM
>> 
>> Mark,
>> 
>> Here's my doc on the subject...
>> 
>> Mary Anne
>> 
>> Differences b/w running native LPAR and running as a z/VM guest
>> 
>> In a single system:
>> 
>> The only issue I’m aware of is some strangeness with your performance 
>> monitors.
>> 
>> In a SYSPLEX:
>> 
>> --A new CFRM policy is required, specifying SIMDEV for the coupling facility:
>> 
>>              CF NAME(CFCC1
>>                     TYPE(SIMDEV)
>>                     MFG(IBM)
>>                     PLANT(EN)
>>                     SEQUENCE(0000000CFCC1)
>>                     PARTITION(0)
>>                     CPCID(00)
>>                     DUMPSPACE(2000)
>> 
>> Type Number (TYPE) - SIMDEV specifies that this is a z/VM simulated   
>> message device type.
>>    Manufacturer (MFG) - IBM® indicates IBM as the manufacturer.
>>    Plant (PLANT) - EN indicates Endicott as the manufacturing plant.
>>    Sequence # (SEQUENCE) - The 12-byte field will contain the CF Service 
>> Machine user ID    right justified. Pad all leading unused characters with 
>> EBCDIC zeros. For example, if a CF Service Machine of CFCC1 is specified, 
>> SEQUENCE is 0000000CFCC1. Your DR provider may have a different CF name.
>> 
>> 
>> --A different CLOCKxx member may be needed specifying SIMETRID:
>> 
>> TIMEZONE W.04.00.00
>> ETRMODE YES
>> ETRDELTA 10
>> ETRZONE YES
>> SIMETRID 00
>> 
>> --Possible CFSizing needed:
>> 
>> If you are on a processor that has a lower level of CF Code, you may need to 
>> resize your structures. For example, if your DR provider has a z10 (CFLEVEL 
>> 16) and you are running on a z9 (CFLEVEL 15), you may need to increase the 
>> storage size of the CF.
>> 
>> 
>>> It's been many, many years since we've run our sysplex under zVM. Our next 
>>> DR exercise will be hosted in a VM >environment and I'm looking for any 
>>> environmental setup concerns that I need to consider.
>> 
>>> I know that we'll have to change LOADxx, but I'm unsure about anything else.
>> 
>>> Any advice on what I have to do would be greatly appreciated.
>> 
>>> Mark Jacobs
>>> Time Customer Service
>> 
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to [email protected] with the message: INFO IBM-MAIN
>> 
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to [email protected] with the message: INFO IBM-MAIN
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to