Hello Howard.
Sorry for this answer to reach you too late, but we are GMT+1 and I'm just
reading IBM-MAIN post right now. Well, let's go to the point.
1. Is there a way to do a VSAM recat operation IODF11?
Yes, it is. But you must use, as Dave Kopischke point out, the following
statements for IDCAMS:
DEFINE CLUSTER(NAME(SYS1.IODF11.CLUSTER) –
VOL(SHR92B) –
LINEAR RECATALOG) –
CATALOG(CATALOG.MVSICFM.VZOSCT1)
2. Regarding suggestions about IODF location, let me introduce you our layout,
in case it's usefull for you.
- We've got 6 CPCs, 4 at Site_1 and 2 at Site_2, all of then sharing almost the
same IODF. I use Site_1 as the primary IODF source and Site_2 is just a mirror
of Site_1, using EMC SRDF synchronous remote copy.
- Those 6 CPCs hosts 21 z/OS systems belonguing to 10 diferent sysplexes.
- We use a schema of a pair of IODFs, located at diferent disk control unit,
for every IODF version and with exactly the same content, for availability
purpouses. Both IODF have SYS8 and SYS9 as HLQs and residing in SYSIO8 and
SYSIO9 volumes each. IODFs are suffixed from 00 to FF, in ascending order, as
they are updated.
- SYSIO8 is mirrored at Site_2 but SYSIO9 is not, in order to prevent remote
copy did not work and we were in need for updating IODF at Site_2. Till now, it
never happens. So, in normal operations, we rebuild SYSIO9 files at Site_2 from
SYSIO8 ones.
- SYSIO8 has a user catalog, CAT.SYS8, and SYSIO9 has CAT.SYS9, each of then
addressed by SYS8 and SYS9 aliases. Both, catalogs and aliases and connected
and defined in every sysplex master catalog.
- Everything within SYSIO8 has SYS8 for HLQ, and everything in SYSIO9 is
SYS9.**. No mix.
- SYSIOn only contains IODFs, IPLPARM and the refered user catalog.
- We use a pair of LOADxx members for every system in IPLPARM: LOADFx and
LOAD0x, being 'x' a system specific ID. First record looks like this:
<IODF -- PLEX$A 00> for LOADFx
<IODF ++ PLEX$A 00> for LOAD0x
This is for the IPLing system to select the proper IODF that matches the HSA
token of the CPC it's hosted at.
- At IPL time, operations group fills the LOADPARM with the SYSIO8 address plus
the 'Fx' suffix explained before. SYSIO9 is taken as a bakup IODF device. We
reserve the '0x' suffix for reverting a software only change: both LOADFx and
LOAD0x will be able to select version N and version N+1 IODF if a software only
change were made, just because the HSA token will match in both cases. Using
the 'Fx' suffix will perform a top/down IODF seach, so the system will select
the IODF with the highest suffix meeting the HSA token (version N+1). On the
other hand, using the '0x' suffix will perform a down/top seach, selecting
version N. Remember, a software only change doesn't change the token.
I ought to sorry for the long and may be less clear explaination, but english
is not my own language. If you have any specific questions regarding the above
information, feel free to contact me off-list.
Regards
--
José Mª Martínez Besteiro
z/OS System Programmer
Madrid - Spain
______________________________________________
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
