About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
VDIBK | Back to Index page |
Prolog Control Block Contents VDIBK DSECT VDIDATA DSECT VDIVLT DSECT Storage Layout Cross Reference (Contains links to field and bit definitions) |
|
VDIBK Prolog | Top of page |
NAME : HCPVDIBK DESCRIPTION: VDISK data BlocK (Guest Relocation) DSECT : VDIBK VDIVLT FUNCTION : The VDIBK DSECT is used during Live Guest Relocation to accumulate a list of migratable VDISKs and their associated ASCBK addresses. The VDIVLT DSECT maps a table locating all VDIBKs used in the current relocation. LOCATED BY : The DSECTS within this block are pointed to by following fields in HCPRLOBK: RLOVDIFP - Points to first VDIBK in VDIBK chain RLOVDILP - Points to last VDIBK in VDIBK chain RLOVLTBL - Points to the VDISK location table (VDIVLT) VDIARNXT - Points to the next VDIBK in the chain, or zero if we're at the end of the chain CREATED BY : - On the source system: The VDIBK is created/updated by the VDISK Array routine (HCPRLLVA). This routine is called during I/O eligibility checking. VDIVLT is created by the Generate VDIBK Table, HCPRLLGT. This is called by source eligibility checking (HCPRLLSE). - On the destination system: The VDIBK is received over ISFC by destination eligibility checking (HCPRLLDE), which anchors it into the RLOBK on the destination. VDIVLT is created by HCPRLLGT, which is called by HCPRLLDE as it processes the VDIBKs sent over ISFC from the source system. DELETED BY : HCPRLNCU - LGR cleanup routine (source) HCPRLNCT - LGR cleanup routine (target) REFERENCES : None SERIALIZED : RLOVDILK There is a risk of STMGT LGR cleanup and destination I/O device creation running at the same time. As both access the VDIBK, the RLOVDILK lock was created to serialize all fields related to relocating VDISKs. This is a standard shared/exclusive lock. Furthermore, these DSECTs are *not* covered under the VDEV lock as changes to the VDISK configuration are not supported during a relocation; a DEFINE or DETACH VDISK command will fail a relocation in progress. RELOCATION CONSIDERATIONS : This block is sent from the source to the destination system. NOTES : On the destination system, flag VDIDNXIT is used to coordinate address space cleanup when a relocation is terminated prematurely. If the bit is set, then I/O relocation has created the VDISK as part of the relocating guest's I/O configuration. As such, the VDISK address space will be cleaned up when the relocation skeleton goes through logoff processing. If VDIDNXIT is not set, then relocation cleanup (HCPRLNCT) will destroy the VDISK address space. For a description of how the VDIVLT can be used to find a VDIBK during a relocation, see fields VPAAIDOF and VPAAIDIN in the VPABK. |
VDIBK Control Block Content | Top of page |
|
VDIBK Storage Layout | Top of page |
*** VDIBK - VDISK data BlocK (Guest Relocation) * * +-------------------------------------------------------+ * 0 | VDIBKNAM | * +---------------------------+-------------+-------------+ * 8 | VDIARNXT | VDIUSED | VDINDEX | * +---------------------------+-------------+-------------+ * 10 | VDISIZE | VDIPROCD | VDISKCNT | * +---------------------------+------+------+-------------+ * 18 | VDIBLCKS |:BSTAT|:CHKPT|/////////////| * +---------------------------+------+------+-------------+ * 20 * *** VDIBK - VDISK data BlocK (Guest Relocation) *** VDIDATA - VDISK data BlocK (Guest Relocation) * * +-------------------------------------------------------+ * 0 | | * = VDIDNAME = * | | * +-------------------------------------------------------+ * 18 | VDIDSIZE | * +---------------------------+---------------------------+ * 20 | VDIDNMBK | VDIDASCB | * +-------------+------+------+---------------------------+ * 28 | VDIDVNUM |:DSTAT|//////////////////////////////////| * +-------------+------+----------------------------------+ * 30 * *** VDIDATA - VDISK data BlocK (Guest Relocation) *** VDIVLT - VDISK data BlocK (Guest Relocation) * * +---------------------------+ * 0 | VDIVLTEN | 4 * +---------------------------+ * *** VDIVLT - VDISK data BlocK (Guest Relocation) |
VDIBK Cross Reference | Top of page |
Symbol Dspl Value -------------- ---- ----- VDIARNXT 0008 VDIBKLEN 002B 000000C4 VDIBKNAM 0000 VDIBLCKS 0018 VDIBSTAT 001C VDICHKPT 001D VDICRETD 001D 01 VDIDASCB 0024 VDIDASDS 002A 02 VDIDATLN 002B 00000030 VDIDMAX 002B 00000020 VDIDNAME 0000 VDIDNEXT 002B 00000030 VDIDNMBK 0020 VDIDNXIT 002A 01 VDIDSIZE 0018 VDIDSTAT 002A VDIDVNUM 0028 VDIFIRST 001C 01 VDIHDEND 001E 00000020 VDIHDSIZ 001E 00000020 VDINDEX 000E VDIPROCD 0014 VDISIZE 0010 VDISKCNT 0016 VDIUSED 000C VDIVLTEN 0000 VDIVLTNX 0000 00000004 VDIVLTSZ 0000 00000004 |
Copyright IBM Corporation, 1990, 2022