I don't know the entire process and we don't use EAV volumes at my shop, but I believe the first action to take would be checking for any PTF needed by running a SMP/E MISSINGFIX FIXCAT with category IBM.Function.EAV. I also believe category IBM.Device.* would help, depending on your DASD ESS.
*Lucas Rosalen* 2014-04-03 3:27 GMT-03:00 venkat kulkarni <[email protected]>: > We have requirement from customer to have EAV volumes on z/OS 1.12 > systems. > > Below are the step, I followed for this configuration. > > *a) Software requirements:* Extended address volumes require z/OS V1R10. > > *b) Hardware requirements:* A Licensed interal code (LIC) upgrade to an IBM > DS8000 is needed so that an EAV can be configured in the storage subsystem. > *c) *Allow SMS to select extended address volumes during its volume > selection processing. Set the USEEAV parameter in the IGDSMS*xx* PARMLIB > member to YES: USEEAV(YES). > > d) In the IGDSMS*xx* PARMLIB member, specify an optional break point value > for SMS to use when making volume selection decisions for VSAM data sets. > On the BreakPointValue parameter, specify a number of cylinders (0-65520). > > > Do we have any other steps, which I am missing before I use these EAV > volumes like, any thing has to be done on IODF side or something else. > > ---------------------------------------------------------------------- > 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
