SUBJECT: APAR NUMBER: PQ36341
REFERENCE: AREA: TPFDF CRUISE UTILITY
SEGMENT: C$CRUDEF13 - RELEASE: TPFDF (C-Header)
SEGMENT: C$CRUMRC13 - RELEASE: TPFDF (C-Header)
SEGMENT: C$CRUPRO13 - RELEASE: TPFDF (C-Header)
SEGMENT: C$CRUSTR13 - RELEASE: TPFDF (C-Header)
SEGMENT: C$CRUUSR13 - RELEASE: TPFDF (C-Header)
SEGMENT: C$IDCADF13 - RELEASE: TPFDF (C-Header)
SEGMENT: C$IRCBDF13 - RELEASE: TPFDF (C-Header)
SEGMENT: C$IRCHDF13 - RELEASE: TPFDF (C-Header)
SEGMENT: C$IRCMDF13 - RELEASE: TPFDF (C-Header)
SEGMENT: C$IRCTDF13 - RELEASE: TPFDF (C-Header)
SEGMENT: C$IRCXDF13 - RELEASE: TPFDF (C-Header)
SEGMENT: IDCADF13 - RELEASE: TPFDF (Dsect)
SEGMENT: IRCHDF13 - RELEASE: TPFDF (Dsect)
SEGMENT: IRCMDF13 - RELEASE: TPFDF (Dsect)
SEGMENT: IRCTDF13 - RELEASE: TPFDF (Dsect)
SEGMENT: IRCXDF13 - RELEASE: TPFDF (Dsect)
SEGMENT: UFHAG113 - RELEASE: TPFDF (C)
SEGMENT: UFHAG213 - RELEASE: TPFDF (C)
SEGMENT: UFHA0713 - RELEASE: TPFDF (C)
SEGMENT: UFHA0913 - RELEASE: TPFDF (C)
SEGMENT: UFHA1113 - RELEASE: TPFDF (C)
SEGMENT: UFHA1213 - RELEASE: TPFDF (C)
SEGMENT: UFHBG113 - RELEASE: TPFDF (C)
SEGMENT: UFHB0113 - RELEASE: TPFDF (C)
SEGMENT: UFHB0213 - RELEASE: TPFDF (C)
SEGMENT: UFHB0413 - RELEASE: TPFDF (C)
SEGMENT: UFHB0513 - RELEASE: TPFDF (C)
SEGMENT: UFHB0613 - RELEASE: TPFDF (C)
SEGMENT: UFHB0713 - RELEASE: TPFDF (C)
SEGMENT: UFHE0013 - RELEASE: TPFDF (C)
SEGMENT: UFHMBS13 - RELEASE: TPFDF (BuildScr)
SEGMENT: UFHM0013 - RELEASE: TPFDF (C)
SEGMENT: UFHNBS13 - RELEASE: TPFDF (BuildScr)
SEGMENT: UFHN0013 - RELEASE: TPFDF (C)
SEGMENT: UFI213 - RELEASE: TPFDF (Assembler)
SEGMENT: UFI513 - RELEASE: TPFDF (Assembler)
SEGMENT: UFTM13 - RELEASE: TPFDF (Assembler)
SEGMENT: UF1F13 - RELEASE: TPFDF (Assembler)
Pre-requisite APARs are (TPF only) :
FOR SEGMENT C$CRUDEF13 (C-Header) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT C$CRUPRO13 (C-Header) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT C$CRUSTR13 (C-Header) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT C$CRUUSR13 (C-Header) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT C$IDCADF13 (C-Header) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT C$IRCBDF13 (C-Header) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT C$IRCHDF13 (C-Header) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT IDCADF13 (Dsect) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT IRCHDF13 (Dsect) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT UFHAG113 (C) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT UFHAG213 (C) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT UFHA0713 (C) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT UFHA0913 (C) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT UFHA1113 (C) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT UFHA1213 (C) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT UFHBG113 (C) - REL TPFDF
PQ23871
FOR SEGMENT UFHB0113 (C) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT UFHB0213 (C) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT UFHB0413 (C) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT UFHB0513 (C) - REL TPFDF
PQ23489 PQ23871 PQ35353
FOR SEGMENT UFHB0613 (C) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT UFHB0713 (C) - REL TPFDF
PQ23489 PQ23871 PQ33713
FOR SEGMENT UFHE0013 (C) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT UFI213 (Assembler) - REL TPFDF
PQ23489 PQ23871
FOR SEGMENT UFI513 (Assembler) - REL TPFDF
PQ23489 PQ23871 PQ33410
FOR SEGMENT UFTM13 (Assembler) - REL TPFDF
PN73989 PN76852 PN84757 PQ23871 PQ33409 PQ30389
FOR SEGMENT UF1F13 (Assembler) - REL TPFDF
PQ23489 PQ23871
To be applied in the order listed for each segment.
ABSTRACT OF PROBLEM
___________________
Currently CRUISE chain chases all references to a single detail
file. CRUISE should be enhanced so that, if requested, only one
chain will be chased to the detail file.
COMMENTS ON PROBLEM
___________________
TPFDF capture/restore utility, information and statistics envi-
ronment (CRUISE) chain chases all references to detail files.
However, chain chasing uses additional system resources when a
detail file has multiple references. CRUISE should be enhanced
to allow the user to specify whether to chain chase all refer-
ences to a detail file or just a single reference.
SOLUTION
________
This APAR enhances CRUISE by adding multiple reference check
(MRC) support. The MRC parameter has been introduced to the
ZFCRU SETUP command. With this parameter, the user can specify
whether or not all references to a detail file are chain chased.
If you specify YES for the MRC parameter, CRUISE will chain
chase only one reference. If you specify NO, CRUISE will chain
chase all references as is done currently.
You must consider the following restrictions when using MRC=YES:
1
o Restoring using WID or ADR parameters will abort with the
FCRU0150I CPU SELECTIVE RESTORE COULD NOT COMPLETE DATA CAP-
TURED USING MRC message when a restore is attempted using a
capture where MRC=YES was specified.
o Complete STATISTICS may not be gathered during CRUISE proc-
essing with MRC=YES.
DEPENDENCIES
____________
Related Segments Affected By This APAR.
_______________________________________
Segments to be assembled or compiled:
Segments to be link edited:
On TPF: UFHA, UFHB, UFHD, UFHE, UFHF, UFHG, UFHM and UFHN
On ALCS: TPFDFH3
Load Modules to be loaded:
Migration Considerations
========================
o On the TPF system, do the following before installing this
APAR:
1. Apply TPF APAR PJ27305.
2. Add the following subsystem user (SSU) common record to
the FACE table:
Record type * REC ID * SIZE * NBR * Ordinals
*********************************************************
#IRCMDF * FD22 * L4 * 997 * 0-996 per processor
* * * * in loosley-coupled
* * * * complex
NOTE: The default number of ordinals per processor may
not be correct for your installation. Please refer to
the formula below to determine the appropriate number of
ordinals for your installation.
o On ALCS, do the following before installing this APAR:
1. A new fixed file #IRCMDF has been introduced with this
APAR. The DXCURID macro contains the new fixed file
definition. Update your DXCURID to include this new
fixed file. A sample DXCURID macro is included in the
dataset with a trailing qualifier of BDFJCL1.
2. New database definition (DBDEF) has been introduced with
this APAR. Assemble, link and load UF1F. Sample JCL,
BDFALUF1, for assembling and linking the DBDEF programs
is located in the dataset with the BDFJCL1 trailing
qualifier.
3. This APAR introduces new record #IRCMDF. Allocate this
new record by running a DASD generation. You will need
to update your DASD generation by coding additional
USRDTA macro statements for the new records. Sample DASD
generation, BDFGEND, is located in the dataset with the
trailing qualifier, BDFJCL1. Assemble and load your
DASD generation. Refer to the ALCS documentation for
more information on DASD generation.
NOTE: Please refer to the formula below to determine
the number of ordinals for your installation.
o All customers must consider the following:
- Use the following formula to determine the number of
#IRCMDF ordinals for your installation.
ord = prime (mr / 267 / avgch) where:
ORD is a prime number, to use for the #IRCMDF. On
the TPF system this is the number of ordinals
per processor in a loosley-coupled complex.
PRIME is the function to calculate the closest prime
number.
MR is the maximum estimated number of multiple
references in the file. You can use the RCI
count from the recoup phase 1 activity log as
a reference.
267 specifies the number of LRECs that are in a
data block for the MRC subfile.
AVGCH is the average number of overflow blocks for
each ordinal number in the #IRCMDF database.
When using MRC support, the recommended number
of chains to balance performance and resource
(fixed files) requirement is 1.5. If you
increase avgch, the number of ordinals needed
decreases, but CRUISE MRC performance
decreases. If you decrease avgch, the number
of ordinals needed increases, but CRUISE MRC
performance improves. Also, ordinary CRUISE
capture (non-MRC) performance will not be
affected. See your database administrator for
more information about specifying the avgch
value. See the TPFDF Utilities and the Instal-
lation and Customization publications for more
information about MRC.
- Initialize #IRCMDF using the ZUDFM OAINIT command as
record ID FD22.
- There is a new parameter, MRC, for the ZFCRU SETUP
command. The MRC parameter can have one of the fol-
lowing values:
NO specifies that MRC support is not used during
CRUISE capture processing
YES specifies that MRC support is used during
CRUISE capture processing.
- FCRU0150I CPU SELECTIVE RESTORE COULD NOT COMPLETE DATA
CAPTURED USING MRC online message was added with the
following explanation:
-- This is the normal response when you enter the ZFCRU
SETUP command and specify the ADR, or WID parameter
with multiple reference check (MRC) support. CRUISE
restore processing ends. See TPFDF Utilities for
more information about the ZFCRU SETUP command and
MRC support.
2
-- END APAR PQ36341
Download file(s) using new Server:
Login once to access server, leave window open, then
click on link(s) below.
|
