|
| |
|
|
|
| |
TPF : Support : Maintenance : TPFDF
 |
SUBJECT: APAR NUMBER: PQ57527
REFERENCE: AREA: TPFDF RECOUP ROUTINES
SEGMENT: BRC013 - RELEASE: TPFDF (Assembler)
SEGMENT: BRC213 - RELEASE: TPFDF (Assembler)
SEGMENT: BRC813 - RELEASE: TPFDF (Assembler)
SEGMENT: GR0ZSR13 - RELEASE: TPFDF (Macro)
Pre-requisite APARs are (TPF only) :
FOR SEGMENT BRC013 (Assembler) - REL TPFDF
PQ00810 PQ29840 PQ42097
FOR SEGMENT BRC213 (Assembler) - REL TPFDF
PN40344 PN63712 PN63945 PQ42097 PQ49400
FOR SEGMENT BRC813 (Assembler) - REL TPFDF
PN49704 PN63704 PN63945 PQ29840 PQ42097
FOR SEGMENT GR0ZSR13 (Macro) - REL TPFDF
PN55359 PQ42097
To be applied in the order listed for each segment.
ABSTRACT OF PROBLEM
___________________
TPFDF recoup corrections: 1)Entries missing from ZRECP LOG 2)
OPR-DB0102 on ZRECP LOG 3) Inactive groups may be shown to be
active in the log display 4) Selective recoup can't find
fileaddr's in online errlog.
COMMENTS ON PROBLEM
___________________
1. Some TPFDF record IDs that are processed may not show up in
the TPFDF recoup log. This is due to a timing problem in
segment BRC8 where two ECBs can attempt to write the same
LREC in the recoup log file, GR0ZSR. If this happens, the
second entry will overwrite the contents of the first entry.
2. An OPR-IDB0102 may occur if the ZRECP LOG command is entered
with parameters that are not part of the valid syntax of the
command. For example, ZRECP LOG *. This occurs because
segment BRC0 does not parse the command properly and
attempts to interpret any extraneous parameters as a
processor ID.
3. If a ZRECP LOG command is entered while TPFDF recoup is
active, the entry will indicate which TPFDF record IDs are
currently being processed. However, if the command is
entered at the end of phase I when recoup is deferring to
correct fixed errors, log display will indicate several
record IDs are currently active when they aren't. Some
entries also contain invalid record IDs. This is caused by
an invalid check for active recoup restart areas in BRC0.
4. If a fixed error is found during TPFDF recoup, recoup defers
to allow the user to correct the error. If the user per-
forms a selective recoup to attempt to process the fixed
error record, recoup will generate a BKA10003A NO ERRORS
WITH THAT ID warning that the fixed error to be corrected
can't be found in the online error log, even though the
error really did occur.
SOLUTION
________
1. Segment BRC8 has been updated to increment LREC counter
BK0LRC before doing the DBADD to guarantee unique values.
The #STPF macro was also changed to use a compare and swap
mechanism.
2. Segment BRC0 has been updated to ignore extraneous parame-
ters on the ZRECP LOG command.
3. Segment BRC0 has also been updated to test for active groups
properly. Furthermore, active record IDs are now indicated
with the text "IN PROGRESS" instead of "ACTIVERECP".
4. Segment BRC2 has been updated such that when a fixed error
entry is written to the online error log, it is marked as a
fixed error so that it can be found if an attempt is made to
correct the error.
5. Finally, segment GR0ZSR has been updated such that the start
time field GR0ZTRC is properly split into the 4-byte start
time and 4-byte end time. Segment BRC0 has been updated to
use the appropriate new labels.
DEPENDENCIES
____________
Related Segments Affected By This APAR.
_______________________________________
Segments to be assembled or compiled:
Segments to be link edited:
Load Modules to be loaded:
Migration Considerations
========================
You must install TPF APAR PJ28453 for this APAR to correct the reported problem.
-- END APAR PQ57527
Download file(s) using new Server:
Login once to access server, leave window open, then
click on link(s) below.
|
|
|
|
|
|