CA IMS Tools CA RS 1601 Service List

Transcription

1 CA IMS Tools CA RS 1601 Service List Release Service Description Type 16.0 RO86907 ADD SEGMENT CONCATENATED KEY MEGGAGE. PTF RO87216 MAKE DBO PASS COMPRESSED SEGM TO USER EXIT PTF RO87269 ABEND 0C1 IN ITK STARTED TASK W/ MULTIPLE FFOR JOBS RUNNING PTF RO87270 ABEND 0C1 IN ITK STARTED TASK W/ MULTIPLE FFOR JOBS RUNNING PTF RO87271 ABEND 0C1 IN ITK STARTED TASK W/ MULTIPLE FFOR JOBS RUNNING PTF RO87272 CIC RUNTIME AND STOPTIME TIMEZONE FORMAT DISCREPANCY PTF RO87273 CIC RUNTIME AND STOPTIME TIMEZONE FORMAT DISCREPANCY PTF The CA RS 1601 service count for this release is 7

2 CA IMS Tools 2 CA RS 1601 Service List for CIDOG00 FMID Service Description Type CIDOG00 RO86907 ADD SEGMENT CONCATENATED KEY MEGGAGE. PTF RO87216 MAKE DBO PASS COMPRESSED SEGM TO USER EXIT PTF RO87269 ABEND 0C1 IN ITK STARTED TASK W/ MULTIPLE FFOR JOBS RUNNING PTF RO87272 CIC RUNTIME AND STOPTIME TIMEZONE FORMAT DISCREPANCY PTF The CA RS 1601 service count for this FMID is 4

3 CA IMS Tools 3 CA RS 1601 Service List for CITKG00 FMID Service Description Type CITKG00 RO87270 ABEND 0C1 IN ITK STARTED TASK W/ MULTIPLE FFOR JOBS RUNNING PTF RO87273 CIC RUNTIME AND STOPTIME TIMEZONE FORMAT DISCREPANCY PTF The CA RS 1601 service count for this FMID is 2

4 CA IMS Tools 4 CA RS 1601 Service List for CITSG00 FMID Service Description Type CITSG00 RO87271 ABEND 0C1 IN ITK STARTED TASK W/ MULTIPLE FFOR JOBS RUNNING PTF The CA RS 1601 service count for this FMID is 1

5 CA IMS Tools CA RS PTF RO86907 Release Service 16.0 RO86907 RO86907 M.C.S. ENTRIES = ++PTF (RO86907) ADD SEGMENT CONCATENATED KEY MEGGAGE. CA Database Organizer for IMS for z/os Title 'Add message information when reloading duplicate segments ends in error'. CA Database Organizer for IMS for z/os (DBO) when using FUNCTION=RELOAD, a segment sequence error can occur when two child segments have the same keys. However, RELOAD does not provide enough information that can be used identify the segments with the duplicate keys. The RELOAD job step fails with RC=8 and, in DBOMSGS, you will see: DBO3605E SEQUENCE CORRECTION WAS REQUESTED BUT CANNOT BE PERFORMED FOR SEGMENT "xxxxxxxx". DBO3606I A DUPLICATE KEY VALUE WITH A UNIQUE KEY FIELD IS UNCORRECTABLE. DBO3607I KEY:yyyyyyyyyyyyyyyyy The RELOAD fails and the segments with duplicate keys must be identified and resolved before the database can be reloaded. None. DBO 1059 Copyright (C) 2015 CA. All rights reserved. R00265-I160-SP1 DESC(ADD SEGMENT CONCATENATED KEY MEGGAGE.). ++VER (Z038) FMID (CIDOG00) SUP ( RO62047 TR62047 TR86907 )

6 CA IMS Tools CA RS PTF RO87216 Release Service 16.0 RO87216 RO87216 M.C.S. ENTRIES = ++PTF (RO87216) MAKE DBO PASS COMPRESSED SEGM TO USER EXIT Title: DBO TO PASS COMPRESSED SEGMENT TO USER EXIT PROGRAM. CA Database Organizer for IMS for z/os Currently CA Database Organizer for IMS for z/os (DBO) only passes expanded segments to USER EXIT programs. If the USER EXIT is expecting a compressed segment, it may abend with a S0C4. A new keyword will be added to enable a compressed segment to be passed to the USER EXIT: USEREXITEXPAND=NO. An example of a DBO UNLOAD step where the user exit abends is: In DBOMSGS, you will see: IDI1300E A S0C4 ABEND OCCURRED (MODULE DBOUCTL, SUFFIX(0), HEX OFFSET 141E, DBOUCTL0... IDI1309I RECOVERY WILL NOT BE ATTEMPTED - NO RECOVERY ROUTINE AVAILABLE. The UNLOAD fails and will abend with the USER EXIT program. None. DBO 1060 Copyright (C) 2015 CA. All rights reserved. R00266-I160-SP1 DESC(MAKE DBO PASS COMPRESSED SEGM TO USER EXIT). ++VER (Z038) FMID (CIDOG00) PRE ( RO62184 RO64086 RO69207 RO81711 ) SUP ( RO63643 RO71297 RO71905 RO74264 TR63643 TR71297 TR71817 TR71905 TR74260 TR74264 TR87216 )

7 CA IMS Tools CA RS PTF RO87269 Release Service 16.0 RO87269 RO87269 M.C.S. ENTRIES = ++PTF (RO87269) The following items are included in this solution: 1. ABEND 0C1 IN ITK STARTED TASK W/ MULTIPLE FFOR JOBS RUNNING 2. ABEND D23 OR 0C4 AFTER STC DISABLE OR SHUTDOWN COMMAND 3. DBO3902E FOR CONCURRENT IMAGE COPY WHEN MMGRIO=Y 4. COPYIC FAILS ON FAST PATH DB WITH MULTIPLE AREAS 5. MULTIPLE IC FUNCTIONS CAN GET IDI1802E OR DBO5900E 6. RECURSIVE OC4 ABEND AFTER ITKSTC S IMS CHANGE ACCUMULATION FAILS DFS3335A REASON 2 AFTER FFOR 8. MASTER HALDB FFOR UPDATES NOT CAPTURED AFTER PARTITION FFOR 9. NO INDEX CHANGE.DBDS ICOFF IN HPOCMDS WHEN RENAME=NO 10. BATCHREORG OF EMPTY DB ENDS RC= NEW SHARING SUBSYSTEM NOT DETECTED SOON ENOUGH BY FFOR 12. FFOR UPDATES REORG NUMBERS FOR EACH DSG WHEN REORGV ON 13. EMPTY SECONDARY INDEXES NOT CREATED WITH BUILDILDS=Y ABEND 0C1 IN ITK STARTED TASK W/ MULTIPLE FFOR JOBS RUNNING CA Common Components for IMS for z/os The ITK started task (STC) can abend S0C1 when multiple Full Function Online Reorganization (FFOR) jobs are running concurrently. In the started task JES message log, there will be multiple messages HPO2405I indicating that reorganizations have started. The symptoms of the S0C1 abend are that all but two of the lower halves of the 16 registers are zero. Only registers 0 and 13 are non-zero. The system register display is followed by this message from the STC: HPO6004I HPO REQUEST SUBTASK TERMINATED The format of the HPO2405I message is: HPO2405I REORG jobname jobnumber HAS STARTED ON sysname Any of the FFOR jobs running at the time of the STC abend will fail. Usually they will fail with a U0016 abend or return code 12. It is also possible for them to fail with a S202 abend. The online database is not affected and the reorganization is aborted. However, the started task can remain "stuck". It may not note that those reorganization jobs have ended. If so, instead of the STC ending, it will issue the following message every four minutes: HPO2049I WAITING FOR JOBS TO DISCONNECT If that occurs, issue the following command to flush the remaining reorganizations: F stcname,kill ALL The STC will then either end or abend SD23. This problem has never been seen when the number of concurrent online reorganizations is two or one. IMS Toolkit Common Component Version 16.0 IMS Toolkit Common Component Version 18.0 IMS Toolkit Common Component Version 19.0 COM 480 ABEND D23 OR 0C4 AFTER STC DISABLE OR SHUTDOWN COMMAND CA Common Components for IMS for z/os The ITK started task (STC) can abend SD23 or S0C4 after certain commands are issued while Full Function Online Reorganization (FFOR) jobs are running. If a "DISABLE" command is issued to the started task while FFOR jobs are running, the following message is issued just before a S0C4 abend: HPO2107I HPO SUBSYSTEM HAS BEEN DRAINED If a SHUTDOWN command (z/os STOP command) is issued while FFOR jobs

8 Release Service CA IMS Tools CA RS PTF RO87269 are running, the following messages are issued just before a SD23 abend: HPO2103I THE FOLLOWING SESSIONS ARE ACTIVE: HPO2104I jobname -imsid -dbdname (There may be several HPO2104I lines.) The started task abends, or is stuck until a FORCE with ARM is used. If a "DISPLAY ACTIVE" command to the STC shows that the STC is under the mistaken impression that FFOR jobs are running when they are not really running, the best approach to avoid the abends described above is to either use individual "KILL imsid dbdname" commands to purge the STC of those FFOR executions, or "KILL ALL" to purge them all at once if they are all not really running. IMS Toolkit Common Component Version 16.0 IMS Toolkit Common Component Version 18.0 IMS Toolkit Common Component Version 19.0 COM 481 DBO3902E FOR CONCURRENT IMAGE COPY WHEN MMGRIO=Y CA Database Copier for IMS for z/os (DBCOPY) can fail when performing a concurrent image copy on a VSAM database with the MMGRIO=YES control statement. This can occur when the database is extended to contain new control intervals (CIs) with an updated High Used RBA while the concurrent image copy is still processing. The job will receive the following error message and end with return code 16: DBO3902E THE RBA RETURNED BY MEDIA MANAGER WAS NOT THE EXPECTED RBA. The image copy fails but, the problem can be circumvented - at the cost of performance. Run the concurrent image copy with MMGRIO=NO. CA Database Copier Version 16.0 CA Database Copier Version 18.0 CA Database Copier Version 19.0 DBCOPY 238 COPYIC FAILS ON FAST PATH DB WITH MULTIPLE AREAS CA Database Copier for IMS for z/os (DBCOPY) will fail when processing a copy image copy function on a fast path database that is composed of multiple areas. DBOI023E DDNAME CONTROL STATEMENT IS REQUIRED FOR A COPY IC OF A MULTI-DSG DATABASE. No copy can be made using the COPYIC function, even if AREA= is specified. None. CA Database Copier Version 16.0 CA Database Copier Version 18.0 CA Database Copier Version 19.0 DBCOPY 239 MULTIPLE IC FUNCTIONS CAN GET IDI1802E OR DBO5900E CA Database Copier for IMS for z/os CA Database Copier for IMS for z/os (DBCOPY) may fail when attempting

9 Release Service CA IMS Tools CA RS PTF RO87269 to perform multiple image copy functions within the same jobstep. This can occur when the subsequent image copy is of a different database type than the previous image copy. Depending on the database type, 2 different errors can occur: IDI1802E FILE "XXXXXXXX" IS NOT ALLOCATED. DBON303E COPY CONTROLLER FAILED RC = C. IDI7601I FUNCTION RETURN CODE = 0012 (MODULE DBOUOPE, SUFFIX(K), OFFSET 0C9C DBO5900E THE DDNAME/AREA SPECIFIED WAS NOT FOUND IN THE DBD. DBON303E COPY CONTROLLER FAILED RC = C. IDI7601I FUNCTION RETURN CODE = 0012 (MODULE DBODBDD, SUFFIX(K), OFFSET 0B22 Attempting to perform multiple image copies from within the same jobstep may fail if the image copies are of different database types. Specify only 1 image copy per jobstep. CA Database Copier Version 16.0 CA Database Copier Version 18.0 CA Database Copier Version 19.0 DBCOPY 240 RECURSIVE OC4 ABEND AFTER ITKSTC S The CA Database Copier for IMS for z/os (DBC) function terminates abnormally with message DBO1313E DBRC DATA BASE AUTHORIZATION FAILED. 2. The CA Database Organizer for IMS for z/os fails with a recursive SC04 ABENDs in module ITKBMP00 after a S301 failure in the ITKSTC. 3. The CA Database Organizer for IMS for z/os fails with a recursive SC04 ABENDs in module ITKBRIQ after message HPO5209I DATABASE IS BEING USED BY THE FOLLOWING SUBSYSTEMS had been issued. 4. Several ITK messages issued by the BMPPAUSE facility and HPO control region lack sufficient information to detect external reasons (IMS), for a PAUSE time out. It also makes it difficult to relate FFOR tasks to the ITK STC activities and time stamps. 1. The CA Database Copier for IMS for z/os (DBC) function terminates abnormally with message DBO1313E DBRC DATA BASE AUTHORIZATION FAILED because the ITK STC failed to issue an auto resume after a PAUSE timeout. BMPs associated with the database remained in a quiesced mode and allocated to the IMS control region, thus failing DBRC authorization for batch image copy cycles. 2. The CA Database Organizer for IMS for z/os fails with a recursive SC04 ABENDs in module ITKBMP00 after a S301 failure in the ITK STC ITK6540I SVC DUMP REQUESTED FOR ASID 0000,037C,8382 IDI0123S Processing of abend S301 terminated due to unsupported IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=301 TIME= SEQ=27280 CPU=4001 ASID=010D PSW AT TIME OF ERROR 070C FF6F36 ILC 2 INTC 0D NO ACTIVE MODULE FOUND DATA AT PSW 00FF6F A0DB The CA Database Organizer for IMS for z/os fails with a recursive SC04 ABENDs in module ITKBRIQ after message "HPO5209I DATABASE IS BEING USED BY THE FOLLOWING SUBSYSTEMS" had been issued. IDI1300E A S0C4 RC= ABEND OCCURRED (MODULE ITKBRIQ, SUFFIX(K),OFFSET 014C IDI1303I A RECURSIVE ABEND HAS OCCURRED - RECOVERY WILL NOT BE ATTEMPTED. IDI1311I Control Flags: TCB:00AD68F0 ABCB:23F7B068 IDI1305I ABEND CODE: 840C4000 PROGRAM:.4/ EPA: The CA Database Copier terminates abnormally due to DBRC authorization issues. The resulting image copy is not useable.

10 Release Service CA IMS Tools CA RS PTF RO The ITK STC is unable to support the CA Database Organizer for IMS FFOR environment. The ITK STC and IMS Control region must be cold started to support FFOR functionality. 3. CA Database Organizer for IMS for z/os function fails. The database has not been reorganized. 4. Problem determination as to why an application is unable to reach a sync point within a specified time-out period is impossible. Debugging chronological events of FFOR activity is cumbersome. 5. The ITK STC is unable to service the CA Database Organizer for IMS for z/os environment. None in all cases DBO 1042 IMS CHANGE ACCUMULATION FAILS DFS3335A REASON 2 AFTER FFOR Database Organizer for IMS for z/os After the Full Function Online Reorg (FFOR) facility of Database Organizer for IMS for z/os (DBO) is used, the IMS Change Accumulation function can fail with message DFS3335A, reason code 2. The IMS change accumulation will fail with the following message: DFS3335A LOG INPUT IS NOT IN SEQUENCE FOR FUNCTION CA; REASON CODE = 2 The database is not recoverable using the IMS utilities. An attempt to use IMS recovery leads right back to change accumulation with the following message issued: DSP0281I LOG MERGE REQUIRED FOR RECOVERY REQUEST Use the CA High Performance Recovery for IMS for z/os Change Accumulation and/or Recovery facilities. If the IMS utilities are used, the risk can be mitigated, but not eliminated, by taking a concurrent image copy after the FFOR function completes. Doing so obviates the need for the log created during FFOR by the call replay process. CA Database Organizer Release 16.0 DBO 1048 MASTER HALDB FFOR UPDATES NOT CAPTURED AFTER PARTITION FFOR The Full Function Online Reorg (FFOR) facility of CA Database Organizer may incorrectly bypass replaying updates during transaction replay for a HAL database. This can occur when the same HAL database is used in both ALLPARTS=YES and NUMBEROFPARTS= online reorganizations, where repositories exist in the ITK started task for both master and partition DBD names. If SAFETYNET=Y is used, one can expect to see the following message, and the online reorganization will fail: HPO8008E DATABASE COMPARISON UNSUCCESSFUL In all cases, HPORPTS will show zero transactions replayed even if replays were expected: *** Beginning playback for DBD dbname using SOUPDAT1 Number of records read : 0 Number of records replayed: 0 ISRT call count=0 REPL call count=0

11 CA IMS Tools CA RS PTF RO87269 Release Service DLET call count=0 After both master DBD and partition named repositories exist in the started task, subsequent online reorganizations of a particular type (ALLPARTS, or NUMBEROFPARTS) will not replay transactions that occurred during the reorg. This can lead to database corruption and data loss. Do not use the same HAL database in both ALLPARTS=Y and NUMBEROFPARTS= reorganizations. If you already have, performing a warm start of the ITK started task will clear the repositories and prevent the problem. Product(s) Affected: CA Database Organizer Release 16.0 CA Database Organizer Release 18.0 CA Database Organizer Release 19.0 DBO 1050 NO INDEX CHANGE.DBDS ICOFF IN HPOCMDS WHEN RENAME=NO CA Database Organizer for IMS for z/os The CA Database Organizer for IMS for z/os (DBO) BATCHREORG function and Full Function Online Reorg (FFOR) component will bypass writing the CHANGE.DB(DS) command(s) to the HPOCMDS DD when RENAME=NO is specified in the control statements. The CHANGE.DB(DS) command(s) will be absent from the HPOCMDS DD which lists the DBRC commands that would have or should have been issued if RENAME=YES or other keyword combinations had been specified. The ability to have these commands that were not issued and easily use them to be manually issued to DBRC is not available. None. DBO 1051 BATCHREORG OF EMPTY DB ENDS RC=12 CA Database Organizer for IMS for z/os The CA Database Organizer for IMS for z/os (DBO) BATCHREORG function will finish with a return code of 12 when attempting to REORG an empty HAL database with ALLPARTS=YES specified even though the RELOAD portion of the REORG finished with a return code of 4. HPO5102E ERROR DURING DBO EXECUTION, CHECK DBOMSGSR DATASET HPO1D01I ORIGINAL DATABASE SUCCESSFULLY REINSTATED IDI7601I FUNCTION RETURN CODE = 0012 (MODULE HPORELD,... (in the RELOAD function) DBOI123W NO SEGMENTS WERE RELOADED.... IDI7601I FUNCTION RETURN CODE = 0004 (MODULE DBODCTL, IDI7602I CUMULATIVE RETURN CODE = The BATCHREORG function will fail with a return code of 12. None.

12 CA IMS Tools CA RS PTF RO87269 Release Service DBO 1055 NEW SHARING SUBSYSTEM NOT DETECTED SOON ENOUGH BY FFOR Database Organizer for IMS for z/os The Full Function Online Reorganization (FFOR) facility of Database Organizer for IMS for z/os (DBO) does not recognize soon enough that a new sharing subsystem has accessed a database. The reorganized database can be brought online to IMS before the problem is recognized. If the online reorganization takes less than ten minutes, and a new sharing subsystem opens the database after the reorganization has started, then the problem is not recognized until the databases have been renamed and brought online. One scenario is when the database is online to IMS, but not open. In that case, the following message is found in HPOMSGS: HPO5207I DATABASE IS NOT SHARED In another scenario, the database may be online to, say, only one system at the start of the reorganization, but a second system opens the database while the reorganization is occureing. In that case, only one system is named in the following messages in HPOMSGS: HPO5209I DATABASE IS BEING USED BY THE FOLLOWING SUBSYSTEMS HPO5210I sys1 With both scenarios, the problem comes if the new sharing subsystem is on a different LPAR than the reorganization is running. In that case, the database updates are not captured. This is a scenario that FFOR can detect, but the problem in this case is that the problem is recognized too late. The HPOMSGS dataset contains the following: HPO0B01I RENAMING oldname TO oldname.o HPO0B01I RENAMING newname.n TO oldname... HPO7101I NOTIFY.REORG SUCCESSFULLY DONE HPO7401I NOTIFY.IC SUCCESSFULLY DONE HPO1551I NOTIFY.PRILOG SUCCESSFULLY DONE... HPO0507E REORG ABANDONED DUE TO THE DETECTION OF AN UNRECOVERABLE ERROR HPO0A03E REORG ABANDONED DUE TO THE DETECTION OF AN UNRECOVERABLE ERROR IDI7601I FUNCTION RETURN CODE = 0012 (MODULE HPODBR0, SUFFIX(0), OFFSET 0D8A). And the job log will show the following WTOs: HPO8110I DBRC SUCCESSFULLY NOTIFIED OF REORG AND IMAGE COPY HPO8113I DBRC SUCCESSFULLY NOTIFIED OF PRILOG AND DBDS ALLOC HPO0053E IMS SYSTEM sys2 IS NOW SHARING dbdname HPO0054E REORG ABANDONED DUE TO PRECEDING ERROR The database brought online to IMS is missing updates from the other system and the cleanup (/DBR of the database, undo the renames) is left to the user. Ensure that the database is open on all sharing subsystems before the online reorganization occurs. DBO 1057 FFOR UPDATES REORG NUMBERS FOR EACH DSG WHEN REORGV ON Database Organizer for IMS for z/os The Full Function Online Reorg (FFOR) facility for CA Database Organizer for IMS for z/os (DBO) will incorrectly update the reorganization numbers for

13 Release Service CA IMS Tools CA RS PTF RO87269 a HAL database when Reorg Verification is active in the Recon datasets. The reorganization numbers end up incrementing for every dataset group (DSG) member in the partition, rather than once per partition. You will see the reorganization number increment multiple times for the same partition in the HPOMSGS dataset: DSP0132I IMAGE COPY NEEDED FOR DSP0132I DBDNAME=partn DDNAME=partnA DSP1108I REORG# CHANGED FROM TO FOR DATABASE partn HPO7101I NOTIFY.REORG SUCCESSFULLY DONE FOR partn, partna DSP0132I IMAGE COPY NEEDED FOR DSP0132I DBDNAME=partn DDNAME=partnB DSP1108I REORG# CHANGED FROM TO FOR DATABASE partn HPO7101I NOTIFY.REORG SUCCESSFULLY DONE FOR partn, partnb DSP0132I IMAGE COPY NEEDED FOR DSP0132I DBDNAME=partn DDNAME=partnC DSP1108I REORG# CHANGED FROM TO FOR DATABASE partn HPO7101I NOTIFY.REORG SUCCESSFULLY DONE FOR partn, partnc Subsequent Database Analyzer (DBA) pointer checking can show the following: DBD NAME: dbdname PHDAM/VSAM DD NAME : partna DS NAME : database.dsn - volume DBA3905I ERROR MESSAGES FOR DATA BASE "dbdname ", DD NAME "partna". DBA0001E ERROR IN BIT CI # = 2 (HEX ), RBA OF CI = DBA0020I THE ERROR WAS DETECTED AT CI OFFSET 2 (HEX 0002). DBA0061I REORG NUMBER DOES NOT MATCH THE DBRC VALUE. DBD NAME: PSINDX PSINDEX/VSAM DD NAME : PSINDX1A DS NAME : index.dataset.name - volume DBA0001E ERROR IN DATA REC # = 54 (HEX ), RBA OF REC = DBA0020I THE ERROR WAS DETECTED AT REC OFFSET 0 (HEX 0000). DBA5806E THE "PSINDX /PSIDXSRT" INDEX SEGMENT AT RBA X'xxxxxxxx' HAS NO CORRESPONDING ILE IN PARTITION PART2 FOR ILK X'segment ilk' High. There will be a mismatch between the physical partition reorg number and the number in the recon dataset, and some secondary index and ILDS entries will reveal pointer errors. Run the online reorg with RENAME=NO and manually perform the NOTIFY.REORG commands provided in HPOCMDS. DBO 1058 EMPTY SECONDARY INDEXES NOT CREATED WITH BUILDILDS=Y CA Secondary Index Builder for IMS for z/os (SIB) will not create all the necessary empty secondary indexes when running with the BUILDILDS=YES control statement during functions INDEXCREATE or INDEXBUILD. This can cause subsequent failures when attempting to open those secondary indexes with other utilities such as image copy. The error will not be apparent in SIB, however if trying to image copy the indexes later with CA Database Copier for IMS for z/os (DBCOPY), the following error will occur for the empty indexes: IDI1208I A VSAM EXCEPTION OCCURRED DURING EXECUTION OF A OPEN ACB REQUEST IDI1200I VSAM STATUS - FOR FILE PSINDX2A, THE ACB OPERANDS WERE INCONSISTENT IDI1207I VSAM INFORMATION: REQUEST=OPEN ACB, RETURN CODE=0008, FEEDBACK=0 DBO6901E UNABLE TO OPEN DATA BASE DATA SET WITH DD NAME "PSINDX2A". Low. Although subsequent image copies of the indexes will not be taken, it is not of great consequence since they are empty and a simple

14 CA IMS Tools CA RS PTF RO87269 Release Service circumvention exists. Run the INDEXCREATE or INDEXBUILD function again without the BUILDILDS=YES keyword. CA Secondary Index Builder Version 16.0 CA Secondary Index Builder Version 18.0 CA Secondary Index Builder Version 19.0 SIB 132 Copyright (C) 2015 CA. All rights reserved. R00267-I160-SP1 DESC(ABEND 0C1 IN ITK STARTED TASK W/ MULTIPLE FFOR JOBS RUNNING). ++VER (Z038) FMID (CIDOG00) PRE ( RO60070 RO60485 RO61104 RO63661 RO63777 RO64086 RO64637 RO65812 RO65883 RO66266 RO66524 RO68929 RO69207 RO69331 RO72788 RO72951 RO73726 RO76968 RO77204 RO77375 RO78527 RO79682 RO80489 RO81057 RO81711 ) SUP ( RO60467 RO60788 RO61397 RO64220 RO65227 RO65277 RO68413 RO69649 RO71131 RO74772 RO76127 TR60467 TR60788 TR61397 TR63671 TR63673 TR63723 TR64220 TR65181 TR65227 TR65277 TR66241 TR68413 TR69558 TR69649 TR71131 TR72686 TR72776 TR74670 TR74772 TR76127 TR87269 ) ++IF FMID(CITKG00) REQ(RO87270 ). ++IF FMID(CITSG00) REQ(RO87271 ). ++HOLD (RO87269) SYSTEM FMID(CIDOG00) REASON (ACTION ) DATE (15352) COMMENT ( SEQUENCE Before using Full Function Online Reorganization of DBO PURPOSE This describes how to activate this PTF in your environment USERS AFFECTED All users of the Full Function Online Reorganization (FFOR) Database Organizer for IMS for z/os (DBO) KNOWLEDGE REQUIRED IMS Database Administration ACCESS REQUIRED Ability to bounce CA Database Management for IMS started task and also the IMS systems which use FFOR ************************** * STEPS TO PERFORM * ************************** 1. Wait for any pending DBO FFOR (Full Function Online Reorganization) jobs to complete. 2. Stop the ITK started task (STCITK is distributed name) 3. Restart the ITK started task with option TYPE=W,PAUSE=W. ).

15 CA IMS Tools CA RS PTF RO87270 Release Service 16.0 RO87270 RO87270 M.C.S. ENTRIES = ++PTF (RO87270) The following items are included in this solution: 1. ABEND 0C1 IN ITK STARTED TASK W/ MULTIPLE FFOR JOBS RUNNING 2. ABEND D23 OR 0C4 AFTER STC DISABLE OR SHUTDOWN COMMAND 3. DBO3902E FOR CONCURRENT IMAGE COPY WHEN MMGRIO=Y 4. COPYIC FAILS ON FAST PATH DB WITH MULTIPLE AREAS 5. MULTIPLE IC FUNCTIONS CAN GET IDI1802E OR DBO5900E 6. RECURSIVE OC4 ABEND AFTER ITKSTC S IMS CHANGE ACCUMULATION FAILS DFS3335A REASON 2 AFTER FFOR 8. MASTER HALDB FFOR UPDATES NOT CAPTURED AFTER PARTITION FFOR 9. NO INDEX CHANGE.DBDS ICOFF IN HPOCMDS WHEN RENAME=NO 10. BATCHREORG OF EMPTY DB ENDS RC= NEW SHARING SUBSYSTEM NOT DETECTED SOON ENOUGH BY FFOR 12. FFOR UPDATES REORG NUMBERS FOR EACH DSG WHEN REORGV ON 13. EMPTY SECONDARY INDEXES NOT CREATED WITH BUILDILDS=Y ABEND 0C1 IN ITK STARTED TASK W/ MULTIPLE FFOR JOBS RUNNING CA Common Components for IMS for z/os The ITK started task (STC) can abend S0C1 when multiple Full Function Online Reorganization (FFOR) jobs are running concurrently. In the started task JES message log, there will be multiple messages HPO2405I indicating that reorganizations have started. The symptoms of the S0C1 abend are that all but two of the lower halves of the 16 registers are zero. Only registers 0 and 13 are non-zero. The system register display is followed by this message from the STC: HPO6004I HPO REQUEST SUBTASK TERMINATED The format of the HPO2405I message is: HPO2405I REORG jobname jobnumber HAS STARTED ON sysname Any of the FFOR jobs running at the time of the STC abend will fail. Usually they will fail with a U0016 abend or return code 12. It is also possible for them to fail with a S202 abend. The online database is not affected and the reorganization is aborted. However, the started task can remain "stuck". It may not note that those reorganization jobs have ended. If so, instead of the STC ending, it will issue the following message every four minutes: HPO2049I WAITING FOR JOBS TO DISCONNECT If that occurs, issue the following command to flush the remaining reorganizations: F stcname,kill ALL The STC will then either end or abend SD23. This problem has never been seen when the number of concurrent online reorganizations is two or one. IMS Toolkit Common Component Version 16.0 IMS Toolkit Common Component Version 18.0 IMS Toolkit Common Component Version 19.0 COM 480 ABEND D23 OR 0C4 AFTER STC DISABLE OR SHUTDOWN COMMAND CA Common Components for IMS for z/os The ITK started task (STC) can abend SD23 or S0C4 after certain commands are issued while Full Function Online Reorganization (FFOR) jobs are running. If a "DISABLE" command is issued to the started task while FFOR jobs are running, the following message is issued just before a S0C4 abend: HPO2107I HPO SUBSYSTEM HAS BEEN DRAINED If a SHUTDOWN command (z/os STOP command) is issued while FFOR jobs

16 Release Service CA IMS Tools CA RS PTF RO87270 are running, the following messages are issued just before a SD23 abend: HPO2103I THE FOLLOWING SESSIONS ARE ACTIVE: HPO2104I jobname -imsid -dbdname (There may be several HPO2104I lines.) The started task abends, or is stuck until a FORCE with ARM is used. If a "DISPLAY ACTIVE" command to the STC shows that the STC is under the mistaken impression that FFOR jobs are running when they are not really running, the best approach to avoid the abends described above is to either use individual "KILL imsid dbdname" commands to purge the STC of those FFOR executions, or "KILL ALL" to purge them all at once if they are all not really running. IMS Toolkit Common Component Version 16.0 IMS Toolkit Common Component Version 18.0 IMS Toolkit Common Component Version 19.0 COM 481 DBO3902E FOR CONCURRENT IMAGE COPY WHEN MMGRIO=Y CA Database Copier for IMS for z/os (DBCOPY) can fail when performing a concurrent image copy on a VSAM database with the MMGRIO=YES control statement. This can occur when the database is extended to contain new control intervals (CIs) with an updated High Used RBA while the concurrent image copy is still processing. The job will receive the following error message and end with return code 16: DBO3902E THE RBA RETURNED BY MEDIA MANAGER WAS NOT THE EXPECTED RBA. The image copy fails but, the problem can be circumvented - at the cost of performance. Run the concurrent image copy with MMGRIO=NO. CA Database Copier Version 16.0 CA Database Copier Version 18.0 CA Database Copier Version 19.0 DBCOPY 238 COPYIC FAILS ON FAST PATH DB WITH MULTIPLE AREAS CA Database Copier for IMS for z/os (DBCOPY) will fail when processing a copy image copy function on a fast path database that is composed of multiple areas. DBOI023E DDNAME CONTROL STATEMENT IS REQUIRED FOR A COPY IC OF A MULTI-DSG DATABASE. No copy can be made using the COPYIC function, even if AREA= is specified. None. CA Database Copier Version 16.0 CA Database Copier Version 18.0 CA Database Copier Version 19.0 DBCOPY 239 MULTIPLE IC FUNCTIONS CAN GET IDI1802E OR DBO5900E CA Database Copier for IMS for z/os CA Database Copier for IMS for z/os (DBCOPY) may fail when attempting

17 Release Service CA IMS Tools CA RS PTF RO87270 to perform multiple image copy functions within the same jobstep. This can occur when the subsequent image copy is of a different database type than the previous image copy. Depending on the database type, 2 different errors can occur: IDI1802E FILE "XXXXXXXX" IS NOT ALLOCATED. DBON303E COPY CONTROLLER FAILED RC = C. IDI7601I FUNCTION RETURN CODE = 0012 (MODULE DBOUOPE, SUFFIX(K), OFFSET 0C9C DBO5900E THE DDNAME/AREA SPECIFIED WAS NOT FOUND IN THE DBD. DBON303E COPY CONTROLLER FAILED RC = C. IDI7601I FUNCTION RETURN CODE = 0012 (MODULE DBODBDD, SUFFIX(K), OFFSET 0B22 Attempting to perform multiple image copies from within the same jobstep may fail if the image copies are of different database types. Specify only 1 image copy per jobstep. CA Database Copier Version 16.0 CA Database Copier Version 18.0 CA Database Copier Version 19.0 DBCOPY 240 RECURSIVE OC4 ABEND AFTER ITKSTC S The CA Database Copier for IMS for z/os (DBC) function terminates abnormally with message DBO1313E DBRC DATA BASE AUTHORIZATION FAILED. 2. The CA Database Organizer for IMS for z/os fails with a recursive SC04 ABENDs in module ITKBMP00 after a S301 failure in the ITKSTC. 3. The CA Database Organizer for IMS for z/os fails with a recursive SC04 ABENDs in module ITKBRIQ after message HPO5209I DATABASE IS BEING USED BY THE FOLLOWING SUBSYSTEMS had been issued. 4. Several ITK messages issued by the BMPPAUSE facility and HPO control region lack sufficient information to detect external reasons (IMS), for a PAUSE time out. It also makes it difficult to relate FFOR tasks to the ITK STC activities and time stamps. 1. The CA Database Copier for IMS for z/os (DBC) function terminates abnormally with message DBO1313E DBRC DATA BASE AUTHORIZATION FAILED because the ITK STC failed to issue an auto resume after a PAUSE timeout. BMPs associated with the database remained in a quiesced mode and allocated to the IMS control region, thus failing DBRC authorization for batch image copy cycles. 2. The CA Database Organizer for IMS for z/os fails with a recursive SC04 ABENDs in module ITKBMP00 after a S301 failure in the ITK STC ITK6540I SVC DUMP REQUESTED FOR ASID 0000,037C,8382 IDI0123S Processing of abend S301 terminated due to unsupported IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=301 TIME= SEQ=27280 CPU=4001 ASID=010D PSW AT TIME OF ERROR 070C FF6F36 ILC 2 INTC 0D NO ACTIVE MODULE FOUND DATA AT PSW 00FF6F A0DB The CA Database Organizer for IMS for z/os fails with a recursive SC04 ABENDs in module ITKBRIQ after message "HPO5209I DATABASE IS BEING USED BY THE FOLLOWING SUBSYSTEMS" had been issued. IDI1300E A S0C4 RC= ABEND OCCURRED (MODULE ITKBRIQ, SUFFIX(K),OFFSET 014C IDI1303I A RECURSIVE ABEND HAS OCCURRED - RECOVERY WILL NOT BE ATTEMPTED. IDI1311I Control Flags: TCB:00AD68F0 ABCB:23F7B068 IDI1305I ABEND CODE: 840C4000 PROGRAM:.4/ EPA: The CA Database Copier terminates abnormally due to DBRC authorization issues. The resulting image copy is not useable.

18 Release Service CA IMS Tools CA RS PTF RO The ITK STC is unable to support the CA Database Organizer for IMS FFOR environment. The ITK STC and IMS Control region must be cold started to support FFOR functionality. 3. CA Database Organizer for IMS for z/os function fails. The database has not been reorganized. 4. Problem determination as to why an application is unable to reach a sync point within a specified time-out period is impossible. Debugging chronological events of FFOR activity is cumbersome. 5. The ITK STC is unable to service the CA Database Organizer for IMS for z/os environment. None in all cases DBO 1042 IMS CHANGE ACCUMULATION FAILS DFS3335A REASON 2 AFTER FFOR Database Organizer for IMS for z/os After the Full Function Online Reorg (FFOR) facility of Database Organizer for IMS for z/os (DBO) is used, the IMS Change Accumulation function can fail with message DFS3335A, reason code 2. The IMS change accumulation will fail with the following message: DFS3335A LOG INPUT IS NOT IN SEQUENCE FOR FUNCTION CA; REASON CODE = 2 The database is not recoverable using the IMS utilities. An attempt to use IMS recovery leads right back to change accumulation with the following message issued: DSP0281I LOG MERGE REQUIRED FOR RECOVERY REQUEST Use the CA High Performance Recovery for IMS for z/os Change Accumulation and/or Recovery facilities. If the IMS utilities are used, the risk can be mitigated, but not eliminated, by taking a concurrent image copy after the FFOR function completes. Doing so obviates the need for the log created during FFOR by the call replay process. CA Database Organizer Release 16.0 DBO 1048 MASTER HALDB FFOR UPDATES NOT CAPTURED AFTER PARTITION FFOR The Full Function Online Reorg (FFOR) facility of CA Database Organizer may incorrectly bypass replaying updates during transaction replay for a HAL database. This can occur when the same HAL database is used in both ALLPARTS=YES and NUMBEROFPARTS= online reorganizations, where repositories exist in the ITK started task for both master and partition DBD names. If SAFETYNET=Y is used, one can expect to see the following message, and the online reorganization will fail: HPO8008E DATABASE COMPARISON UNSUCCESSFUL In all cases, HPORPTS will show zero transactions replayed even if replays were expected: *** Beginning playback for DBD dbname using SOUPDAT1 Number of records read : 0 Number of records replayed: 0 ISRT call count=0 REPL call count=0

19 CA IMS Tools CA RS PTF RO87270 Release Service DLET call count=0 After both master DBD and partition named repositories exist in the started task, subsequent online reorganizations of a particular type (ALLPARTS, or NUMBEROFPARTS) will not replay transactions that occurred during the reorg. This can lead to database corruption and data loss. Do not use the same HAL database in both ALLPARTS=Y and NUMBEROFPARTS= reorganizations. If you already have, performing a warm start of the ITK started task will clear the repositories and prevent the problem. Product(s) Affected: CA Database Organizer Release 16.0 CA Database Organizer Release 18.0 CA Database Organizer Release 19.0 DBO 1050 NO INDEX CHANGE.DBDS ICOFF IN HPOCMDS WHEN RENAME=NO CA Database Organizer for IMS for z/os The CA Database Organizer for IMS for z/os (DBO) BATCHREORG function and Full Function Online Reorg (FFOR) component will bypass writing the CHANGE.DB(DS) command(s) to the HPOCMDS DD when RENAME=NO is specified in the control statements. The CHANGE.DB(DS) command(s) will be absent from the HPOCMDS DD which lists the DBRC commands that would have or should have been issued if RENAME=YES or other keyword combinations had been specified. The ability to have these commands that were not issued and easily use them to be manually issued to DBRC is not available. None. DBO 1051 BATCHREORG OF EMPTY DB ENDS RC=12 CA Database Organizer for IMS for z/os The CA Database Organizer for IMS for z/os (DBO) BATCHREORG function will finish with a return code of 12 when attempting to REORG an empty HAL database with ALLPARTS=YES specified even though the RELOAD portion of the REORG finished with a return code of 4. HPO5102E ERROR DURING DBO EXECUTION, CHECK DBOMSGSR DATASET HPO1D01I ORIGINAL DATABASE SUCCESSFULLY REINSTATED IDI7601I FUNCTION RETURN CODE = 0012 (MODULE HPORELD,... (in the RELOAD function) DBOI123W NO SEGMENTS WERE RELOADED.... IDI7601I FUNCTION RETURN CODE = 0004 (MODULE DBODCTL, IDI7602I CUMULATIVE RETURN CODE = The BATCHREORG function will fail with a return code of 12. None.

20 CA IMS Tools CA RS PTF RO87270 Release Service DBO 1055 NEW SHARING SUBSYSTEM NOT DETECTED SOON ENOUGH BY FFOR Database Organizer for IMS for z/os The Full Function Online Reorganization (FFOR) facility of Database Organizer for IMS for z/os (DBO) does not recognize soon enough that a new sharing subsystem has accessed a database. The reorganized database can be brought online to IMS before the problem is recognized. If the online reorganization takes less than ten minutes, and a new sharing subsystem opens the database after the reorganization has started, then the problem is not recognized until the databases have been renamed and brought online. One scenario is when the database is online to IMS, but not open. In that case, the following message is found in HPOMSGS: HPO5207I DATABASE IS NOT SHARED In another scenario, the database may be online to, say, only one system at the start of the reorganization, but a second system opens the database while the reorganization is occureing. In that case, only one system is named in the following messages in HPOMSGS: HPO5209I DATABASE IS BEING USED BY THE FOLLOWING SUBSYSTEMS HPO5210I sys1 With both scenarios, the problem comes if the new sharing subsystem is on a different LPAR than the reorganization is running. In that case, the database updates are not captured. This is a scenario that FFOR can detect, but the problem in this case is that the problem is recognized too late. The HPOMSGS dataset contains the following: HPO0B01I RENAMING oldname TO oldname.o HPO0B01I RENAMING newname.n TO oldname... HPO7101I NOTIFY.REORG SUCCESSFULLY DONE HPO7401I NOTIFY.IC SUCCESSFULLY DONE HPO1551I NOTIFY.PRILOG SUCCESSFULLY DONE... HPO0507E REORG ABANDONED DUE TO THE DETECTION OF AN UNRECOVERABLE ERROR HPO0A03E REORG ABANDONED DUE TO THE DETECTION OF AN UNRECOVERABLE ERROR IDI7601I FUNCTION RETURN CODE = 0012 (MODULE HPODBR0, SUFFIX(0), OFFSET 0D8A). And the job log will show the following WTOs: HPO8110I DBRC SUCCESSFULLY NOTIFIED OF REORG AND IMAGE COPY HPO8113I DBRC SUCCESSFULLY NOTIFIED OF PRILOG AND DBDS ALLOC HPO0053E IMS SYSTEM sys2 IS NOW SHARING dbdname HPO0054E REORG ABANDONED DUE TO PRECEDING ERROR The database brought online to IMS is missing updates from the other system and the cleanup (/DBR of the database, undo the renames) is left to the user. Ensure that the database is open on all sharing subsystems before the online reorganization occurs. DBO 1057 FFOR UPDATES REORG NUMBERS FOR EACH DSG WHEN REORGV ON Database Organizer for IMS for z/os The Full Function Online Reorg (FFOR) facility for CA Database Organizer for IMS for z/os (DBO) will incorrectly update the reorganization numbers for

21 Release Service CA IMS Tools CA RS PTF RO87270 a HAL database when Reorg Verification is active in the Recon datasets. The reorganization numbers end up incrementing for every dataset group (DSG) member in the partition, rather than once per partition. You will see the reorganization number increment multiple times for the same partition in the HPOMSGS dataset: DSP0132I IMAGE COPY NEEDED FOR DSP0132I DBDNAME=partn DDNAME=partnA DSP1108I REORG# CHANGED FROM TO FOR DATABASE partn HPO7101I NOTIFY.REORG SUCCESSFULLY DONE FOR partn, partna DSP0132I IMAGE COPY NEEDED FOR DSP0132I DBDNAME=partn DDNAME=partnB DSP1108I REORG# CHANGED FROM TO FOR DATABASE partn HPO7101I NOTIFY.REORG SUCCESSFULLY DONE FOR partn, partnb DSP0132I IMAGE COPY NEEDED FOR DSP0132I DBDNAME=partn DDNAME=partnC DSP1108I REORG# CHANGED FROM TO FOR DATABASE partn HPO7101I NOTIFY.REORG SUCCESSFULLY DONE FOR partn, partnc Subsequent Database Analyzer (DBA) pointer checking can show the following: DBD NAME: dbdname PHDAM/VSAM DD NAME : partna DS NAME : database.dsn - volume DBA3905I ERROR MESSAGES FOR DATA BASE "dbdname ", DD NAME "partna". DBA0001E ERROR IN BIT CI # = 2 (HEX ), RBA OF CI = DBA0020I THE ERROR WAS DETECTED AT CI OFFSET 2 (HEX 0002). DBA0061I REORG NUMBER DOES NOT MATCH THE DBRC VALUE. DBD NAME: PSINDX PSINDEX/VSAM DD NAME : PSINDX1A DS NAME : index.dataset.name - volume DBA0001E ERROR IN DATA REC # = 54 (HEX ), RBA OF REC = DBA0020I THE ERROR WAS DETECTED AT REC OFFSET 0 (HEX 0000). DBA5806E THE "PSINDX /PSIDXSRT" INDEX SEGMENT AT RBA X'xxxxxxxx' HAS NO CORRESPONDING ILE IN PARTITION PART2 FOR ILK X'segment ilk' High. There will be a mismatch between the physical partition reorg number and the number in the recon dataset, and some secondary index and ILDS entries will reveal pointer errors. Run the online reorg with RENAME=NO and manually perform the NOTIFY.REORG commands provided in HPOCMDS. DBO 1058 EMPTY SECONDARY INDEXES NOT CREATED WITH BUILDILDS=Y CA Secondary Index Builder for IMS for z/os (SIB) will not create all the necessary empty secondary indexes when running with the BUILDILDS=YES control statement during functions INDEXCREATE or INDEXBUILD. This can cause subsequent failures when attempting to open those secondary indexes with other utilities such as image copy. The error will not be apparent in SIB, however if trying to image copy the indexes later with CA Database Copier for IMS for z/os (DBCOPY), the following error will occur for the empty indexes: IDI1208I A VSAM EXCEPTION OCCURRED DURING EXECUTION OF A OPEN ACB REQUEST IDI1200I VSAM STATUS - FOR FILE PSINDX2A, THE ACB OPERANDS WERE INCONSISTENT IDI1207I VSAM INFORMATION: REQUEST=OPEN ACB, RETURN CODE=0008, FEEDBACK=0 DBO6901E UNABLE TO OPEN DATA BASE DATA SET WITH DD NAME "PSINDX2A". Low. Although subsequent image copies of the indexes will not be taken, it is not of great consequence since they are empty and a simple

22 CA IMS Tools CA RS PTF RO87270 Release Service circumvention exists. Run the INDEXCREATE or INDEXBUILD function again without the BUILDILDS=YES keyword. CA Secondary Index Builder Version 16.0 CA Secondary Index Builder Version 18.0 CA Secondary Index Builder Version 19.0 SIB 132 Copyright (C) 2015 CA. All rights reserved. R00267-I160-SP1 DESC(ABEND 0C1 IN ITK STARTED TASK W/ MULTIPLE FFOR JOBS RUNNING). ++VER (Z038) FMID (CITKG00) PRE ( RO81712 ) SUP ( TR87270 ) ++IF FMID(CITSG00) REQ(RO87271 ). ++IF FMID(CIDOG00) REQ(RO87269 ).

23 CA IMS Tools CA RS PTF RO87271 Release Service 16.0 RO87271 RO87271 M.C.S. ENTRIES = ++PTF (RO87271) The following items are included in this solution: 1. ABEND 0C1 IN ITK STARTED TASK W/ MULTIPLE FFOR JOBS RUNNING 2. ABEND D23 OR 0C4 AFTER STC DISABLE OR SHUTDOWN COMMAND 3. DBO3902E FOR CONCURRENT IMAGE COPY WHEN MMGRIO=Y 4. COPYIC FAILS ON FAST PATH DB WITH MULTIPLE AREAS 5. MULTIPLE IC FUNCTIONS CAN GET IDI1802E OR DBO5900E 6. RECURSIVE OC4 ABEND AFTER ITKSTC S IMS CHANGE ACCUMULATION FAILS DFS3335A REASON 2 AFTER FFOR 8. MASTER HALDB FFOR UPDATES NOT CAPTURED AFTER PARTITION FFOR 9. NO INDEX CHANGE.DBDS ICOFF IN HPOCMDS WHEN RENAME=NO 10. BATCHREORG OF EMPTY DB ENDS RC= NEW SHARING SUBSYSTEM NOT DETECTED SOON ENOUGH BY FFOR 12. FFOR UPDATES REORG NUMBERS FOR EACH DSG WHEN REORGV ON 13. EMPTY SECONDARY INDEXES NOT CREATED WITH BUILDILDS=Y ABEND 0C1 IN ITK STARTED TASK W/ MULTIPLE FFOR JOBS RUNNING CA Common Components for IMS for z/os The ITK started task (STC) can abend S0C1 when multiple Full Function Online Reorganization (FFOR) jobs are running concurrently. In the started task JES message log, there will be multiple messages HPO2405I indicating that reorganizations have started. The symptoms of the S0C1 abend are that all but two of the lower halves of the 16 registers are zero. Only registers 0 and 13 are non-zero. The system register display is followed by this message from the STC: HPO6004I HPO REQUEST SUBTASK TERMINATED The format of the HPO2405I message is: HPO2405I REORG jobname jobnumber HAS STARTED ON sysname Any of the FFOR jobs running at the time of the STC abend will fail. Usually they will fail with a U0016 abend or return code 12. It is also possible for them to fail with a S202 abend. The online database is not affected and the reorganization is aborted. However, the started task can remain "stuck". It may not note that those reorganization jobs have ended. If so, instead of the STC ending, it will issue the following message every four minutes: HPO2049I WAITING FOR JOBS TO DISCONNECT If that occurs, issue the following command to flush the remaining reorganizations: F stcname,kill ALL The STC will then either end or abend SD23. This problem has never been seen when the number of concurrent online reorganizations is two or one. IMS Toolkit Common Component Version 16.0 IMS Toolkit Common Component Version 18.0 IMS Toolkit Common Component Version 19.0 COM 480 ABEND D23 OR 0C4 AFTER STC DISABLE OR SHUTDOWN COMMAND CA Common Components for IMS for z/os The ITK started task (STC) can abend SD23 or S0C4 after certain commands are issued while Full Function Online Reorganization (FFOR) jobs are running. If a "DISABLE" command is issued to the started task while FFOR jobs are running, the following message is issued just before a S0C4 abend: HPO2107I HPO SUBSYSTEM HAS BEEN DRAINED If a SHUTDOWN command (z/os STOP command) is issued while FFOR jobs

24 Release Service CA IMS Tools CA RS PTF RO87271 are running, the following messages are issued just before a SD23 abend: HPO2103I THE FOLLOWING SESSIONS ARE ACTIVE: HPO2104I jobname -imsid -dbdname (There may be several HPO2104I lines.) The started task abends, or is stuck until a FORCE with ARM is used. If a "DISPLAY ACTIVE" command to the STC shows that the STC is under the mistaken impression that FFOR jobs are running when they are not really running, the best approach to avoid the abends described above is to either use individual "KILL imsid dbdname" commands to purge the STC of those FFOR executions, or "KILL ALL" to purge them all at once if they are all not really running. IMS Toolkit Common Component Version 16.0 IMS Toolkit Common Component Version 18.0 IMS Toolkit Common Component Version 19.0 COM 481 DBO3902E FOR CONCURRENT IMAGE COPY WHEN MMGRIO=Y CA Database Copier for IMS for z/os (DBCOPY) can fail when performing a concurrent image copy on a VSAM database with the MMGRIO=YES control statement. This can occur when the database is extended to contain new control intervals (CIs) with an updated High Used RBA while the concurrent image copy is still processing. The job will receive the following error message and end with return code 16: DBO3902E THE RBA RETURNED BY MEDIA MANAGER WAS NOT THE EXPECTED RBA. The image copy fails but, the problem can be circumvented - at the cost of performance. Run the concurrent image copy with MMGRIO=NO. CA Database Copier Version 16.0 CA Database Copier Version 18.0 CA Database Copier Version 19.0 DBCOPY 238 COPYIC FAILS ON FAST PATH DB WITH MULTIPLE AREAS CA Database Copier for IMS for z/os (DBCOPY) will fail when processing a copy image copy function on a fast path database that is composed of multiple areas. DBOI023E DDNAME CONTROL STATEMENT IS REQUIRED FOR A COPY IC OF A MULTI-DSG DATABASE. No copy can be made using the COPYIC function, even if AREA= is specified. None. CA Database Copier Version 16.0 CA Database Copier Version 18.0 CA Database Copier Version 19.0 DBCOPY 239 MULTIPLE IC FUNCTIONS CAN GET IDI1802E OR DBO5900E CA Database Copier for IMS for z/os CA Database Copier for IMS for z/os (DBCOPY) may fail when attempting

25 Release Service CA IMS Tools CA RS PTF RO87271 to perform multiple image copy functions within the same jobstep. This can occur when the subsequent image copy is of a different database type than the previous image copy. Depending on the database type, 2 different errors can occur: IDI1802E FILE "XXXXXXXX" IS NOT ALLOCATED. DBON303E COPY CONTROLLER FAILED RC = C. IDI7601I FUNCTION RETURN CODE = 0012 (MODULE DBOUOPE, SUFFIX(K), OFFSET 0C9C DBO5900E THE DDNAME/AREA SPECIFIED WAS NOT FOUND IN THE DBD. DBON303E COPY CONTROLLER FAILED RC = C. IDI7601I FUNCTION RETURN CODE = 0012 (MODULE DBODBDD, SUFFIX(K), OFFSET 0B22 Attempting to perform multiple image copies from within the same jobstep may fail if the image copies are of different database types. Specify only 1 image copy per jobstep. CA Database Copier Version 16.0 CA Database Copier Version 18.0 CA Database Copier Version 19.0 DBCOPY 240 RECURSIVE OC4 ABEND AFTER ITKSTC S The CA Database Copier for IMS for z/os (DBC) function terminates abnormally with message DBO1313E DBRC DATA BASE AUTHORIZATION FAILED. 2. The CA Database Organizer for IMS for z/os fails with a recursive SC04 ABENDs in module ITKBMP00 after a S301 failure in the ITKSTC. 3. The CA Database Organizer for IMS for z/os fails with a recursive SC04 ABENDs in module ITKBRIQ after message HPO5209I DATABASE IS BEING USED BY THE FOLLOWING SUBSYSTEMS had been issued. 4. Several ITK messages issued by the BMPPAUSE facility and HPO control region lack sufficient information to detect external reasons (IMS), for a PAUSE time out. It also makes it difficult to relate FFOR tasks to the ITK STC activities and time stamps. 1. The CA Database Copier for IMS for z/os (DBC) function terminates abnormally with message DBO1313E DBRC DATA BASE AUTHORIZATION FAILED because the ITK STC failed to issue an auto resume after a PAUSE timeout. BMPs associated with the database remained in a quiesced mode and allocated to the IMS control region, thus failing DBRC authorization for batch image copy cycles. 2. The CA Database Organizer for IMS for z/os fails with a recursive SC04 ABENDs in module ITKBMP00 after a S301 failure in the ITK STC ITK6540I SVC DUMP REQUESTED FOR ASID 0000,037C,8382 IDI0123S Processing of abend S301 terminated due to unsupported IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=301 TIME= SEQ=27280 CPU=4001 ASID=010D PSW AT TIME OF ERROR 070C FF6F36 ILC 2 INTC 0D NO ACTIVE MODULE FOUND DATA AT PSW 00FF6F A0DB The CA Database Organizer for IMS for z/os fails with a recursive SC04 ABENDs in module ITKBRIQ after message "HPO5209I DATABASE IS BEING USED BY THE FOLLOWING SUBSYSTEMS" had been issued. IDI1300E A S0C4 RC= ABEND OCCURRED (MODULE ITKBRIQ, SUFFIX(K),OFFSET 014C IDI1303I A RECURSIVE ABEND HAS OCCURRED - RECOVERY WILL NOT BE ATTEMPTED. IDI1311I Control Flags: TCB:00AD68F0 ABCB:23F7B068 IDI1305I ABEND CODE: 840C4000 PROGRAM:.4/ EPA: The CA Database Copier terminates abnormally due to DBRC authorization issues. The resulting image copy is not useable.