Thank you Skip Robinson,
Over the past weekend we added a LPAR to our development system, thereby
having a SYSPLEX consisting of three LPARS = DEV0, DEV1 & ETE0
We introduced secondary lock structures in order to test VSAM RLS on our
DFHSM spheres (control data sets - MCDS, BCDS & OCDS). Our current setup
is as follows:
DEV0 & DEV1 shares one set of DFHSM control data sets
ETE0 has its own set of DFHSM control data sets.
In our storage classes we defined IGWLOCK01 for the DEV control data
sets and IGWLOCK02 for the ETE control data sets as the LOCKSETS
The cache set specified in the storage class points to the default lock
structure.
For some reason the lock table status for ETE0 remains in a FAILED
PERSISTANT state and NOT CONN, and when DFHSM is started, it comes back
with:
IEC161I 011(00000004 00000000)-0537,HSM,HSM,MIGCAT,,,
IEC161I DFHSM.D0E0.MCDS,DFHSM.D0E0.MCDS.DATA,CATALOG.ETEPLEX.SYSTEM
ARC0945I OPEN OF DDNAME=MIGCAT FAILED, VSAM REASON 117
ARC0945I (CONT.) CODE IS X'D1'
ARC0200I TRAP IN MODULE ARCCOPEN, CODE=0008, FATAL 118
ARC0200I (CONT.) ONCE ADDED
ARC0900I DFSMSHSM ERROR CODE 0008 IN MODULE ARCCOPEN 119
ARC0900I (CONT.) TYPE FATAL
The HSM PROC:
//HSM PROC CENTRE=&SYSCLONE, CENTRE ID
// CDSSHR=RLS, CDS SHARING TO USE RECORD LEVEL SHARING
//* LOGSW=NO, NO SWITCH OF LOGS AT STARTUP
// UID=DFHSM, DFHSM AUTHORIZED USER ID
// SIZE=0M, REGION SIZE FOR DFHSM
// PRIMARY=YES, ENABLING GRSPLEX SERIALIZATION
// RNAMEDSN=YES, ENABLING GRSPLEX SERIALIZATION
// HOSTMODE=MAIN,
// HOST=1Y,
// DDD=50, MAX DYNAMICALLY ALLOCATED DATA SETS
// RESTART='(HSM,EMERG=YES)'
The display of the XCF:
SYSPLEX DEV1PLEX: D0A0 D0A1 D0E0
The display of the SMS,SHCDS:
Name Size %UTIL Status Type
ACTIVE.VSOFTE0 43200Kb 1% GOOD ACTIVE
ACTIVE.VSOFTE1 43200Kb 1% GOOD ACTIVE
ACTIVE.VSOFTE2 43200Kb 1% GOOD SPARE
----------------- 0Kb 0% N/A N/A
----------------- 0Kb 0% N/A N/A
The display of the SMS,SMSVSAM,ALL
DISPLAY SMS,SMSVSAM - SERVER STATUS
SYSNAME: D0A1 AVAILABLE ASID: 003B STEP: SmsVsamInitComplete
SYSNAME: D0A0 AVAILABLE ASID: 000A STEP: SmsVsamInitComplete
SYSNAME: D0E0 AVAILABLE ASID: 008D STEP: SmsVsamInitComplete
SYSNAME: ........ ........... ASID: .... STEP: ....................
SYSNAME: ........ ........... ASID: .... STEP: ....................
SYSNAME: ........ ........... ASID: .... STEP: ....................
SYSNAME: ........ ........... ASID: .... STEP: ....................
SYSNAME: ........ ........... ASID: .... STEP: ....................
DISPLAY SMSVSAM - JOB STATUS
SUBSYSTEMS CONNECTED: 0 BATCH: 1
DISPLAY SMS,SMSVSAM - LOCK TABLE STATUS
FOR STRUCTURE IGWLOCK00
CONNECT STATUS:
SYSNAME: D0A1 ACTIVE RSN: 02010407 RbldNotActive
SYSNAME: D0A0 ACTIVE RSN: 02010407 RbldNotActive
SYSNAME: D0E0 ACTIVE RSN: 02010407 RbldNotActive
SYSNAME: ........ ................. RSN: ........ ................
SYSNAME: ........ ................. RSN: ........ ................
SYSNAME: ........ ................. RSN: ........ ................
SYSNAME: ........ ................. RSN: ........ ................
SYSNAME: ........ ................. RSN: ........ ................
COMPOSITE STATUS:
ORIGINAL STRUCTURE: NOT VOLATILE NOT FAILURE ISOLATED
STRUCTURE STATUS:
SYSNAME: D0A1 Simplex
SYSNAME: D0A0 Simplex
SYSNAME: D0E0 Simplex
SYSNAME: ........ ...........
SYSNAME: ........ ...........
SYSNAME: ........ ...........
SYSNAME: ........ ...........
SYSNAME: ........ ...........
DISPLAY SMS,SMSVSAM - LOCK TABLE STATUS
FOR STRUCTURE IGWLOCK01
CONNECT STATUS:
SYSNAME: D0A1 ACTIVE RSN: 00000000 RbldNotActive
SYSNAME: D0A0 ACTIVE RSN: 00000000 RbldNotActive
SYSNAME: D0E0 FAILED PERSISTANT RSN: ........ ................
SYSNAME: ........ ................. RSN: ........ ................
SYSNAME: ........ ................. RSN: ........ ................
SYSNAME: ........ ................. RSN: ........ ................
SYSNAME: ........ ................. RSN: ........ ................
SYSNAME: ........ ................. RSN: ........ ................
COMPOSITE STATUS:
ORIGINAL STRUCTURE: NOT VOLATILE FAILURE ISOLATED
STRUCTURE STATUS:
SYSNAME: D0A1 Simplex ENABLE 3
SYSNAME: D0A0 Simplex ENABLE 3
SYSNAME: D0E0 NOT CONN .......... ........
SYSNAME: ........ ........... .......... ........
SYSNAME: ........ ........... .......... ........
SYSNAME: ........ ........... .......... ........
SYSNAME: ........ ........... .......... ........
SYSNAME: ........ ........... .......... ........
Anyone that can assist as what we're doing wrong here?
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of Skip Robinson
Sent: 14 April 2011 04:49 PM
To: [email protected]
Subject: Re: SMSVSAM Sharing control data set - delete and activate
I'm not currently in a position to look this up in a manual, but in
general parallel sysplex configurations do not require system outages to
modify, nor are such outages commonly advised. While the procedure you
outline may work, I'd explore doing your migration dynamically with no
outages at all.
-- Migrate to new SHRCDS nondisruptively vis OS commands
-- IPL a new sysplex member nondisruptively
The biggest strength of doing these things dynamically is that if
something is wrong, you get an error message, and life goes on. When you
implement changes at IPL, problems may well cause IPL to fail.
.
.
JO.Skip Robinson
SCE Infrastructure Technology Services
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[email protected]
From: "Buckton, T. (Theo)" <[email protected]>
To: [email protected]
Date: 04/14/2011 04:36 AM
Subject: SMSVSAM Sharing control data set - delete and activate
Sent by: IBM Mainframe Discussion List <[email protected]>
Please advise:
We need to activate new sharing control data sets for SMSVSAM. Our plan
is:
- terminate the SMSVSAM address space
- delete the active and space shcds (v sms,smsvsam(shscds),delete
- IPL the machine (reason: new lpar is added to the sysplex)
-activate the new shcds on current and new lpar.
- display the SMSVSAM address space.
Please confirm if these steps are correct and in the correct sequence.
Regards
Theo
----------------------------------------------------------------------
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
********************
Nedbank Limited Reg No 1951/000009/06. The following link displays
the names of the Nedbank Board of Directors and Company Secretary.
[ http://www.nedbank.co.za/terms/DirectorsNedbank.htm ]
This email is confidential and is intended for the addressee only.
The following link will take you to Nedbank's legal notice.
[ http://www.nedbank.co.za/terms/EmailDisclaimer.htm ]
********************
----------------------------------------------------------------------
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
