CA IMS Tools CA RS 1409 Service List

Transcription

1 CA IMS Tools CA RS 1409 Service List Description Type 16.0 RO72449 MESSAGE ITK6517E AFTER ITKSTC PAUSE=W STARTUP PTF RO72647 TGRFXV007E ZERO CELL LENGTH FOUND PTF RO72716 MISSING OR INVALID DBD RULES= WITH DECODE FUNCTION PTF RO72787 HPR RECOVER CREATES A BAD DATABASE PTF RO72788 HPR RECOVER CREATES A BAD DATABASE **HIPER** RO72789 HPR RECOVER CREATES A BAD DATABASE PTF RO72844 TASK COUNT INCORRECT PTF RO72920 HPR BUILDS BAD DB WITH CIC AND CHANGE ACCUM PTF RO72921 HPR BUILDS BAD DB WITH CIC AND CHANGE ACCUM *HIP/PRP* RO72951 SIB CREATES TOO MANY INDEX RECORDS. PTF RO73101 IMPROVE DBO3902E MSG DIAGNOSTICS. PTF RO73102 ITK PAUSE COLD/WARM START DISCREPANCIES PTF RO73103 DBA NOT PROVIDING POINTER ERROR DETAIL FOR PHIDAM ROOTS PTF The CA RS 1409 service count for this release is 13

2 CA IMS Tools CA RS 1409 Service List Description Type 15.0 NO-SRV2 CA RS 1409 Contains No Service For This Release of This Product. PTF The CA RS 1409 service count for this release is 0

3 CA IMS Tools CA RS 1409 Service List Description Type 14.0 NO-SRVC CA RS 1409 Contains No Service For This Release of This Product. PTF The CA RS 1409 service count for this release is 0

4 CA IMS Tools 4 CA RS 1409 Service List for CHPRG00 FMID Service Description Type CHPRG00 RO72787 HPR RECOVER CREATES A BAD DATABASE PTF The CA RS 1409 service count for this FMID is 1

5 CA IMS Tools 5 CA RS 1409 Service List for CIDAG00 FMID Service Description Type CIDAG00 RO73103 DBA NOT PROVIDING POINTER ERROR DETAIL FOR PHIDAM ROOTS PTF The CA RS 1409 service count for this FMID is 1

6 CA IMS Tools 6 CA RS 1409 Service List for CIDOG00 FMID Service Description Type CIDOG00 RO72788 HPR RECOVER CREATES A BAD DATABASE **HIPER** RO72920 HPR BUILDS BAD DB WITH CIC AND CHANGE ACCUM PTF RO72951 SIB CREATES TOO MANY INDEX RECORDS. PTF RO73101 IMPROVE DBO3902E MSG DIAGNOSTICS. PTF The CA RS 1409 service count for this FMID is 4

7 CA IMS Tools 7 CA RS 1409 Service List for CITKG00 FMID Service Description Type CITKG00 RO72716 MISSING OR INVALID DBD RULES= WITH DECODE FUNCTION PTF RO72789 HPR RECOVER CREATES A BAD DATABASE PTF RO72921 HPR BUILDS BAD DB WITH CIC AND CHANGE ACCUM *HIP/PRP* The CA RS 1409 service count for this FMID is 3

8 CA IMS Tools 8 CA RS 1409 Service List for CITSG00 FMID Service Description Type CITSG00 RO72449 MESSAGE ITK6517E AFTER ITKSTC PAUSE=W STARTUP PTF RO73102 ITK PAUSE COLD/WARM START DISCREPANCIES PTF The CA RS 1409 service count for this FMID is 2

9 CA IMS Tools 9 CA RS 1409 Service List for CTGRG00 FMID Service Description Type CTGRG00 RO72647 TGRFXV007E ZERO CELL LENGTH FOUND PTF RO72844 TASK COUNT INCORRECT PTF The CA RS 1409 service count for this FMID is 2

10 CA IMS Tools CA RS PTF RO RO72449 RO72449 M.C.S. ENTRIES = ++PTF (RO72449) MESSAGE ITK6517E AFTER ITKSTC PAUSE=W STARTUP PROBLEM DESCRIPTION: The FFOR component of CA Database Organizer for IMS for z/os (DBO) may receive error message HPO3006E after an attempt to issue /DBR command or PAUSE request to the ITKSTC and the BMPPAUSE component of the ITKSTC has been restarted with a PAUSE=W (Warm start) request. When an IMS control region is shut down, the ITKSTC recognizes the shutdown request and marks the BMPPAUSE control block associated with the region as down. A subsequent restart of the ITKSTC with PAUSE=W, fails to reset the control block on a subsequent restart of the IMS control region, thus preventing the ITKSTC from communicating with the IMS region. SYMPTOMS: The FFOR Job HPOMSGS dataset will contain the following message: HPO3006E FAILURE DURING REQUEST PROCESSING - CHECK HPO STC OUTPUT ON lpar HPO0A01E ERROR TRYING TO /DBR DATABASE dddddddd, R15=52B0 The following messages may appear in the ITKSTK Job log: ITK7400I SHUTDOWN DETECTED ON ssid. NO REGIONS IN PAUS MODE... ITK6517E ssid UNAVAILABLE FOR PAUSE ON dddddddd (rrrrrrrr) IMPACT: The Full Function Online Reorg (FFOR) job will terminate with a RC=12 and the HPO3006E message will be issued. CIRCUMVENTION: The ITKSTC Started task should be restarted with a PAUSE=C restart request to reset the BMPPAUSE router table. PRODUCT(S) AFFECTED: CA Database Organizer Release 16.0 Star Problem(s): DBO 1018 Copyright (C) 2014 CA. All rights reserved. R00185-I160-SP1 DESC(MESSAGE ITK6517E AFTER ITKSTC PAUSE=W STARTUP). ++VER (Z038) FMID (CITSG00) PRE ( RO69471 ) SUP ( TR72449 ) ++HOLD (RO72449) SYSTEM FMID(CITSG00) REASON (DYNACT ) DATE (14217) COMMENT ( IMS Toolkit Started Task Component Release 16.0 SEQUENCE After Apply PURPOSE Restart ITKSTC to refresh the shutdown or failed IMS region status after ITKSTC WARM Start. USERS Users of the FFOR component of CA Database Organizer AFFECTED for IMS for z/os (DBO). KNOWLEDGE Product Administration. REQUIRED ACCESS Operator Console. REQUIRED ************************** * STEPS TO PERFORM * ************************** 1. P STCITK (specify appropriate started task name for the ITK STC. 2. S STCITK,PAUSE=W

11 CA IMS Tools CA RS PTF RO72449 ) ).

12 CA IMS Tools CA RS PTF RO RO72647 RO72647 M.C.S. ENTRIES = ++PTF (RO72647) TGRFXV007E ZERO CELL LENGTH FOUND PROBLEM DESCRIPTION: Tiger reads the VVRs for all data sets it is copying. If the length of the VVR exceeded the size of the VVR buffer, the VVR was cut off at the end of the buffer. The cell appeared to have a zero length because it was not present in the buffer. This fix provides larger VVR buffer and adds code to look for VVR RECORD TRUNCATION. IF A VVR'S LENGTH EXCEEDS THE BUFFER SIZE, NEW message TGRFXV009E is issued indicating the size of the VVR and the size of the current buffer. Also, an overlay of the working storage by a service routine has been corrected. This overlay could manifest itself in unpredictable ways. SYMPTOMS: When performing FlashCopy operations, some data sets get message: TGRFXV007E (2) Zero cell length found at offset 0x0847 searching for type 0x27 cell in source VVR The copy operation fails for that data set. IMPACT: Data sets with large VVRs (typically those with many extents) cannot be processed. CIRCUMVENTION: None. PRODUCT(S) AFFECTED: PQC DB2 Tools Quick Copy Release B PQC DB2 Tools Quick Copy Release 17.0 PQC DB2 Tools Quick Copy Release 16.0 DBCOPY IMS Tools Copy Release B DBCOPY IMS Tools Copy Release 17.0 DBCOPY IMS Tools Copy Release 16.0 Star Problem(s): TGR 247 (C)2014 CA. All Rights Reserved.R02637-D16-SP1 DESC(TGRFXV007E ZERO CELL LENGTH FOUND). ++VER (Z038) FMID (CTGRG00) PRE ( RO42109 RO43040 RO52372 RO55596 RO67129 RO69014 RO70863 ) SUP ( RO56856 RO70956 RO71478 ZTGJ026 ) ++HOLD (RO72647) SYSTEM FMID(CTGRG00) REASON (MSGSKEL) DATE (14223) COMMENT ( Snapshot General Services Version 16.0 SEQUENCE After Apply PURPOSE Relink XMESSAGES USERS AFFECTED All CA DB2 Tools Users KNOWLEDGE REQUIRED CA DB2 Tools Post Install Customization. ACCESS 1. CA DB2 Tools Post Install REQUIRED 2. BIND Authority on DB2 subsystems ************************** * STEPS TO PERFORM * ************************** XMESSAGE components have changes as part of this

13 CA IMS Tools CA RS PTF RO72647 maintenance. If you do not customize XMESSAGES, no further action is required. If you do customize XMESSAGES, after maintenance is APPLIED re-apply any XMESSAGE customizations and relink the XMESSAGE load modules. Refer to the Post Installation and Customization Guide for details. ).

14 CA IMS Tools CA RS PTF RO RO72716 RO72716 M.C.S. ENTRIES = ++PTF (RO72716) MISSING OR INVALID DBD RULES= WITH DECODE FUNCTION Database Analyzer for IMS for z/os PROBLEM DESCRIPTION: The CA Database Analyzer for IMS for z/os (DBA) component Control Block Validity Manager (CBVM) DECODE function may omit or incorrectly list the DBD RULES= specification. Additionally, the MIGRATETOHALDB option has been improved to force the /SX field length to 8. SYMPTOMS: The RULES= for roots with logical children may be omitted. For some logical children, the insert rule (FIRST, LAST, or HERE) may be omitted or incorrect. This can affect application program segment positioning. IMPACT: With the incorrect insert rule, insertion of multiple children may result in status code II and the segment is not inserted. CIRCUMVENTION: None. PRODUCT(S) AFFECTED: CA Database Analyzer Release 16.0 Star Problem(s): DBA 466 Copyright (C) 2014 CA. All rights reserved. R00188-I160-SP1 DESC(MISSING OR INVALID DBD RULES= WITH DECODE FUNCTION). ++VER (Z038) FMID (CITKG00) SUP ( TR72716 )

15 CA IMS Tools CA RS PTF RO RO72787 RO72787 M.C.S. ENTRIES = ++PTF (RO72787) HPR RECOVER CREATES A BAD DATABASE Title: HPR RECOVER CREATES A BAD DATABASE CA High Performance Recovery for IMS for z/os PROBLEM DESCRIPTION: FUNCTION=RECOVER of CA High Performance Recovery for IMS for z/os (HPR) may create a broken database partition. This problem may occur under the following conditions: 1) DBRC=NO is specified for a HALDB database/partition and the recovery assets are a Concurrent Image Copy (CIC) and Change Accum (CA) file, where both files are supplied as JCL overrides 2) DBRC=YES is specified with the only recovery assets being CIC and CA file, as there were no ALLOC records known to DBRC with a start time later than the purge time on the CA file. SYMPTOMS: The HPR database recovery will end successfully. However Database Analyzer (DBA) or a pointer checker product will find errors. IMS processes will ABEND with a U0852 ABEND code when trying to read the database. Database utilities such as Secondary Index Builder (SIB) or Database Organizer (DBO) FUNCTION=UNLOAD, will end with errors and/or ABENDs when reading the database. IMPACT: HPR database recovery creates a bad database which cannot be read because of bad pointers. CIRCUMVENTION: IMS database recovery (DFSURDB0) can be used to recover the database dataset(s). PRODUCT(S) AFFECTED: CA High Performance Recovery Release 16.0 Star Problem(s): HPR 235 Copyright (C) 2014 CA. All rights reserved. R00190-I160-SP1 DESC(HPR RECOVER CREATES A BAD DATABASE). ++VER (Z038) FMID (CHPRG00) SUP ( TR72775 TR72787 ) ++IF FMID(CIDOG00) REQ( RO72788). ++IF FMID(CITKG00) REQ( RO72789).

16 CA IMS Tools CA RS PTF RO RO72788 RO72788 M.C.S. ENTRIES = ++PTF (RO72788) HPR RECOVER CREATES A BAD DATABASE Title: HPR RECOVER CREATES A BAD DATABASE CA High Performance Recovery for IMS for z/os PROBLEM DESCRIPTION: FUNCTION=RECOVER of CA High Performance Recovery for IMS for z/os (HPR) may create a broken database partition. This problem may occur under the following conditions: 1) DBRC=NO is specified for a HALDB database/partition and the recovery assets are a Concurrent Image Copy (CIC) and Change Accum (CA) file, where both files are supplied as JCL overrides 2) DBRC=YES is specified with the only recovery assets being CIC and CA file, as there were no ALLOC records known to DBRC with a start time later than the purge time on the CA file. SYMPTOMS: The HPR database recovery will end successfully. However Database Analyzer (DBA) or a pointer checker product will find errors. IMS processes will ABEND with a U0852 ABEND code when trying to read the database. Database utilities such as Secondary Index Builder (SIB) or Database Organizer (DBO) FUNCTION=UNLOAD, will end with errors and/or ABENDs when reading the database. IMPACT: HPR database recovery creates a bad database which cannot be read because of bad pointers. CIRCUMVENTION: IMS database recovery (DFSURDB0) can be used to recover the database dataset(s). PRODUCT(S) AFFECTED: CA High Performance Recovery Release 16.0 Star Problem(s): HPR 235 Copyright (C) 2014 CA. All rights reserved. R00190-I160-SP1 DESC(HPR RECOVER CREATES A BAD DATABASE). ++VER (Z038) FMID (CIDOG00) PRE ( RO69207 ) SUP ( RO68413 TR68413 TR72686 TR72776 TR72788 ) ++IF FMID(CITKG00) REQ( RO72789). ++IF FMID(CHPRG00) REQ( RO72787).

17 CA IMS Tools CA RS PTF RO RO72789 RO72789 M.C.S. ENTRIES = ++PTF (RO72789) HPR RECOVER CREATES A BAD DATABASE Title: HPR RECOVER CREATES A BAD DATABASE CA High Performance Recovery for IMS for z/os PROBLEM DESCRIPTION: FUNCTION=RECOVER of CA High Performance Recovery for IMS for z/os (HPR) may create a broken database partition. This problem may occur under the following conditions: 1) DBRC=NO is specified for a HALDB database/partition and the recovery assets are a Concurrent Image Copy (CIC) and Change Accum (CA) file, where both files are supplied as JCL overrides 2) DBRC=YES is specified with the only recovery assets being CIC and CA file, as there were no ALLOC records known to DBRC with a start time later than the purge time on the CA file. SYMPTOMS: The HPR database recovery will end successfully. However Database Analyzer (DBA) or a pointer checker product will find errors. IMS processes will ABEND with a U0852 ABEND code when trying to read the database. Database utilities such as Secondary Index Builder (SIB) or Database Organizer (DBO) FUNCTION=UNLOAD, will end with errors and/or ABENDs when reading the database. IMPACT: HPR database recovery creates a bad database which cannot be read because of bad pointers. CIRCUMVENTION: IMS database recovery (DFSURDB0) can be used to recover the database dataset(s). PRODUCT(S) AFFECTED: CA High Performance Recovery Release 16.0 Star Problem(s): HPR 235 Copyright (C) 2014 CA. All rights reserved. R00190-I160-SP1 DESC(HPR RECOVER CREATES A BAD DATABASE). ++VER (Z038) FMID (CITKG00) PRE ( RO62723 RO63820 ) SUP ( RO62221 RO66678 RO67041 RO68294 TR62221 TR66678 TR67041 TR68294 TR72777 TR72789 ) ++IF FMID(CIDOG00) REQ( RO72788). ++IF FMID(CHPRG00) REQ( RO72787).

18 CA IMS Tools CA RS PTF RO RO72844 RO72844 M.C.S. ENTRIES = ++PTF (RO72844) TASK COUNT INCORRECT PROBLEM DESCRIPTION: If the maximum number of tasks is limited and mutiple data movers need to be used within a single copy operation, if DFSMSdss is one of those data movers, it is possible that the number of tasks reserved for DFSMSdss will be set to zero. This correction ensures there is one task reserved for DFSMSdss. SYMPTOMS: The number of tasks displayed may not match the actual number of tasks being used. IMPACT: The number of tasks in use may not be the quatity expected. CIRCUMVENTION: None PRODUCT(S) AFFECTED: PQC DB2 Tools Quick Copy Release B PQC DB2 Tools Quick Copy Release 17.0 PQC DB2 Tools Quick Copy Release 16.0 DBCOPY IMS Tools Copy Release B DBCOPY IMS Tools Copy Release 17.0 DBCOPY IMS Tools Copy Release 16.0 Star Problem(s): TGR 248 (C)2014 CA. All Rights Reserved.R02650-D16-SP1 DESC(TASK COUNT INCORRECT). ++VER (Z038) FMID (CTGRG00) PRE ( RO42109 RO52372 RO55596 RO63645 ) SUP ( ZTGJ027 )

19 CA IMS Tools CA RS PTF RO RO72920 RO72920 M.C.S. ENTRIES = ++PTF (RO72920) HPR BUILDS BAD DB WITH CIC AND CHANGE ACCUM PROBLEM DESCRIPTION: FUNCTION=RECOVER of CA High Performance Recovery for IMS for z/os (HPR) may create a broken database partition. This problem may occur under the following condition: DBRC=YES is specified with the recovery assets being CIC, CA file and subsequent log datasets. SYMPTOMS: The HPR database recovery will end successfully. However Database Analyzer (DBA) or a pointer checker product will find errors. IMS processes will ABEND with a U0852 ABEND code when trying to read the database. Database utilities such as Secondary Index Builder (SIB) or Database Organizer (DBO) FUNCTION=UNLOAD, will end with errors and/or ABENDs when reading the database. IMPACT: HPR database recovery creates a bad database which cannot be read because of bad pointers. CIRCUMVENTION: IMS database recovery (DFSURDB0) can be used to recover the database dataset(s). PRODUCT(S) AFFECTED: CA High Performance Recovery Release 16.0 CA High Performance Recovery Version 18.0 Star Problem(s): HPR 237 Copyright (C) 2014 CA. All rights reserved. R00191-I160-SP1 DESC(HPR BUILDS BAD DB WITH CIC AND CHANGE ACCUM). ++VER (Z038) FMID (CIDOG00) PRE ( RO69207 ) SUP ( TR72920 ) ++IF FMID(CITKG00) REQ( RO72921).

20 CA IMS Tools CA RS PTF RO RO72921 RO72921 M.C.S. ENTRIES = ++PTF (RO72921) HPR BUILDS BAD DB WITH CIC AND CHANGE ACCUM PROBLEM DESCRIPTION: FUNCTION=RECOVER of CA High Performance Recovery for IMS for z/os (HPR) may create a broken database partition. This problem may occur under the following condition: DBRC=YES is specified with the recovery assets being CIC, CA file and subsequent log datasets. SYMPTOMS: The HPR database recovery will end successfully. However Database Analyzer (DBA) or a pointer checker product will find errors. IMS processes will ABEND with a U0852 ABEND code when trying to read the database. Database utilities such as Secondary Index Builder (SIB) or Database Organizer (DBO) FUNCTION=UNLOAD, will end with errors and/or ABENDs when reading the database. IMPACT: HPR database recovery creates a bad database which cannot be read because of bad pointers. CIRCUMVENTION: IMS database recovery (DFSURDB0) can be used to recover the database dataset(s). PRODUCT(S) AFFECTED: CA High Performance Recovery Release 16.0 CA High Performance Recovery Version 18.0 Star Problem(s): HPR 237 Copyright (C) 2014 CA. All rights reserved. R00191-I160-SP1 DESC(HPR BUILDS BAD DB WITH CIC AND CHANGE ACCUM). ++VER (Z038) FMID (CITKG00) PRE ( RO72789 ) SUP ( AR72789 TR72921 ) ++IF FMID(CIDOG00) REQ( RO72920).

21 CA IMS Tools CA RS PTF RO RO72951 RO72951 M.C.S. ENTRIES = ++PTF (RO72951) SIB CREATES TOO MANY INDEX RECORDS. CA Secondary Index Builder for IMS for z/os PROBLEM DESCRIPTION: The INDEXCREATE function of CA Secondary Index Builder for IMS for z/os can create PSINDEXes with too many index records when BUILDILDS=YES is specified. This will occur when there are logically related segments that have been logically deleted but not physically deleted. SYMPTOMS: A database integrity checker product will find the records and flag them as errors. The CA Database Analyzer for IMS for z/os will report the extra records with the error message: DBA5803E THE "index_name/segm_name" INDEX SEGMENT AT RBA X'xxxxxxxx' HAS A "EPS/INDX" POINTER AT OFFSET X'xxxx' THAT POINTS AT SEGMENT "segm_name" IN PARTITION xxxxxxx AT RBA X'xxxxxxxx' BUT NO SEGMENT WAS FOUND THERE. THE TARGET RBA WAS X'xxxxxxxx' BEFORE BEING CHANGED BY THE ILE AT RBA X'xxxxxxxx'. IMPACT: The PSINDEX is in error and should not be used. CIRCUMVENTION: To rebuild the PSINDEXes, remove the BUILDILDS=YES statement and rerun. To rebuild the ILDSes, run a SIB INDEXCREATE and specify BUILDILDS=ONLY. PRODUCT(S) AFFECTED: CA Secondary Index Builder Release 16.0 Star Problem(s): SIB 125 Copyright (C) 2014 CA. All rights reserved. R00192-I160-SP1 DESC(SIB CREATES TOO MANY INDEX RECORDS.). ++VER (Z038) FMID (CIDOG00) PRE ( RO60485 RO63661 RO65812 RO69331 ) SUP ( RO65277 TR65277 TR72152 TR72208 TR72676 TR72951 )

22 CA IMS Tools CA RS PTF RO RO73101 RO73101 M.C.S. ENTRIES = ++PTF (RO73101) IMPROVE DBO3902E MSG DIAGNOSTICS. CA Database Copier for IMS for z/os PROBLEM DESCRIPTION: CA Database Copier for IMS for z/os FUNCTION=COPY can end with error message DBO3902E. But the message by itself does not give any information about why the error occurred. There needs to be more diagnostic trace information when the error occurs. SYMPTOMS: The DBCOPY function ends with RC=16 and messages: DBO3902E THE RBA RETURNED BY MEDIA MANAGER WAS NOT THE EXPECTED RBA. IDI7601I FUNCTION RETURN CODE = 0016 (MODULE DBOUDBE, SUFFIX(0), OFFSET 0AB2). IMPACT: The image copy step ends without completing the function. CIRCUMVENTION: Rerunning the step may work. PRODUCT(S) AFFECTED: CA Database Organizer Release 16.0 CA Database Organizer Version 18.0 Star Problem(s): DBO 1019 Copyright (C) 2014 CA. All rights reserved. R00193-I160-SP1 DESC(IMPROVE DBO3902E MSG DIAGNOSTICS.). ++VER (Z038) FMID (CIDOG00) SUP ( TR73101 )

23 CA IMS Tools CA RS PTF RO RO73102 RO73102 M.C.S. ENTRIES = ++PTF (RO73102) ITK PAUSE COLD/WARM START DISCREPANCIES PROBLEM DESCRIPTION: During the execution of the CA Database Organizer for IMS for z/os, (DBO) the ITK STC component of the Full Function Online Reorg (FFOR) function may experience some of the problems indicated below: 1. Under certain conditions FFOR will perform a COLD start despite the fact that a WARM start had been selected on the EXEC statement of the STC JCL, (PGM=HPOINIT,PARM='TYPE=W,PAUSE=W'). 2. While processing, the PAUSE component of FFOR rejects a processing request with message ""ITK6517E IMSX UNAVAILABLE TO PROCESS" because it views the connected IMS system in a state of terminated or in shutdown. 3. After a COLD start the PAUSE component of FFOR terminates on a System 0E0 reason code 029 abend in module ITKBMP00 during the scheduling of the first FFOR job. SYMPTOMS: 1. The ITK STC indicates the STC is to be warm-started, but PAUSE selects a COLD start instead: PGM=HPOINIT,PARM='TYPE=W,PAUSE=W', ITK6526I PAUS COLD START IN PROGRES ITK6500I PAUS INITIALIZATION COMPLETE 2. While processing a new pause request, the FFOR step terminates with RC:08 while the ITK STC displays the following messages for each new PAUSE request from the STC: ITK7400I SHUTDOWN DETECTED ON IMSx NO REGIONS IN PAUS MODE ITK6517E IMS UNAVAILABLE FOR PAUSE ON PSB/database/job name 3. After a COLD START the first FFOR request cause the ITK STC to ABEND with SYSTEM COMPLETION CODE=0E0 REASON CODE= in module ITKBMP00. PSW AT TIME OF ERROR 070C E38 ILC 4 INTC 29 ACTIVE LOAD MODULE ADDRESS= OFFSET=007E738 NAME ITKBMP00 DATA AT PSW 00027E F0 454C58F0 IMPACT: 1. No impact on the system. When there are no FFOR jobs connected to an IMS system PAUSE sheds all its internal data structures to free CSA during the shutdown of the ITK STC. This cause PAUSE to rebuild (COLD START) data structures on the next start up of the ITK STC even when a WARM start was specified. 2. Online reorg did not run, FFOR terminates with RC: The ITK STC terminates and is unuseable for online reorganization. CIRCUMVENTION: None. KEYWORD(s): ABEND SHUTDOWN START PRODUCT UNAVAILABLE WARM COLD STC S0E0 REORG OPENED PROBLEM FFOR ITK ITKBMP00 TYPE=W ITK6517E ITK7400I PRODUCT(S) AFFECTED: CA Database Organizer Release 16.0 CA Database Organizer Version 18.0 Star Problem(s): DBO 1020 Copyright (C) 2014 CA. All rights reserved. R00194-I160-SP1 DESC(ITK PAUSE COLD/WARM START DISCREPANCIES). ++VER (Z038) FMID (CITSG00) PRE ( RO69471 RO72449 ) SUP ( TR72407 TR73102 ) ++HOLD (RO73102) SYSTEM FMID(CITSG00) REASON (ACTION ) DATE (14238) COMMENT (

24 CA IMS Tools CA RS PTF RO73102 IMS Toolkit Started Task Component Release 16.0 SEQUENCE Before using the ITK STC and FFOR functions PURPOSE A new method of managing the start and shutdown sequences for the ITK STC is introduced with this PTF. It removes the prior obstacles of failed FFOR cycles due to timing discrepancies between IMS and the ITK STC cycles during shutdown or startup. After the PTF you will be *able to start or stop any of the processing components, (IMS or the ITK STC), independently of each other as follows:. Start or recycle IMS without the presence of the STC. Start or recycle the STC without the presence of IMS. Shutdown the STC while IMS is active, no FFOR active. Reconnect the STC (warm start), to IMS at any time. Recycle IMS without any considerations to the STC USERS AFFECTED ALL KNOWLEDGE REQUIRED Current level of operation ACCESS REQUIRED As per customer specification ************************** * STEPS TO PERFORM * ************************** 1. Apply the PTF 2. Recycle the ITK STC with a warm start, alternatively you may also recycle IMS and the STC there after. 3. Note: Shutdown of the STC while a FFOR task is busy is not allowed. ). ++HOLD (RO73102) SYSTEM FMID(CITSG00) REASON (DOC ) DATE (14238) COMMENT ( IMS Toolkit Started Task Component Release *************************** * PUBLICATION * *************************** NEW MESSAGES: ITK6543I CONNECTION ESTABLISHED WITH IMSCTLR SCD: 009A8998 Reason: The ITKSTC establish a connection with an IMS Control Region. The name of the IMS Control Region and the address of the IMS SCD forms part of the message. This message is displayed the first time a FFOR reorg is submitted to a specific IMS system after the STC has been started. Action: None informational message Module: ITKBMP00 ITK6544I CONNECTION *TERMINATED WITH IMSUCTLR SCD: 009A8998 Reason: A request to shut down the ITKSTC has been received and the STC is disconectting from the IMS Control Region displayed in this message. The address of the address of the SCD forms part of the message. This message is repeated for each IMS system connected to the ITK STC.

25 CA IMS Tools CA RS PTF RO73102 Action: None informational message only. Module: ITKBMP00 ITK6545I SHUTDOWN COMPLETED - NEXT START WILL BE COLD. Reason: During shutdown the ITKSTC deletes all internal data structures to free storage in CSA. This situation presents itself when there were no con nection to an IMS Control Region and no PAUSE requests had been received during the current STC session. Message ITK6546I will be displayed during the start up of the next session if a WARM start had been requested. Action: None - Informational message Module: ITKBMP00 ITK6546I INTERNAL COLD START SELECTED Reason: The ITKSTC is performing a COLD start to reconstruct PAUSE data structures after a WARM start request had been receieved. The situation presents itself when a prior shutdown of the ITKSTC indicated (message ITK6545I), that there was no connection with any IMS Control region during the duration of the prior STC session. Message ITK6545I will be displayed during the termination of the prior ITKSTC session to indicate that the next WARM start request will b executed as a COLD start. Action: None informational message Module: ITKBMP00 ).

26 CA IMS Tools CA RS PTF RO RO73103 RO73103 M.C.S. ENTRIES = ++PTF (RO73103) DBA NOT PROVIDING POINTER ERROR DETAIL FOR PHIDAM ROOTS Database Analyzer for IMS for z/os PROBLEM DESCRIPTION: When Database Analyzer for IMS for z/os (DBA) is invoked to analyze multiple partitions of a HALDB PHIDAM database, root twin pointer error details are not given for the second and subsequent partitions. Note that statistical checking is performed on all partitions. SYMPTOMS: Error messages DBA6609E and DBA6621E are issued when the PHIDAM DSGROUP A is analyzed, but no DBA1504E message(s) are issued when the primary index is analyzed if multiple partitions are processed as part of the command. Multiple partitions can be processed with the ANALYZEALL function or the ANALYZE function with a NUMBEROFPARTS specification of 2 or greater. Here is the full message text: DBA6609E FOR SEGMENT rootsegm, THE PTF AND PTB POINTERS DO NOT AGREE. DBA6621E THE "PTF -PTB " BACKWARD POINTERS IN SEGMENT "rootsegm" ARE IN ERROR. And when pointer-error detail messages are provided: DBA1504E THE "rootsegm" SEGMENT AT RBA X'root rba' HAS A "PTBorPTF" POINTER AT OFFSET X'000x' THAT POINTS AT SEGMENT "rootsegm" AT RBA X'otro' BUT THE PREVIOUS SEGMENT IN THE CHAIN IS AT RBA X'yaya'. IMPACT: A separate DBA analysis must be run in order to obtain the RBAs of the segments with the pointer errors. Specify the following control cards to analyze just the single partition with statistical errors: FUNCTION=ANALYZE,DBDNAME=master,PARTITION=partname CIRCUMVENTION: None. Note that statistical checking is performed on all partitions. Only pointer error detail messages are missing. PRODUCT(S) AFFECTED: CA Database Analyzer Release 15.0 CA Database Analyzer Release 16.0 CA Database Analyzer Version 18.0 Star Problem(s): DBA 467 Copyright (C) 2014 CA. All rights reserved. R00195-I160-SP1 DESC(DBA NOT PROVIDING POINTER ERROR DETAIL FOR PHIDAM ROOTS). ++VER (Z038) FMID (CIDAG00) PRE ( RO62618 RO63610 RO67392 RO69723 ) SUP ( TR73103 )