CA IDMS CA RS 1406 Service List

Transcription

1 CA IDMS CA RS 1406 Service List Description Type 18.5 RO66749 ADSC COMPILE CAN CHANGE RESULTS OF GOODDATEX(J) PTF RO67058 EXIT 14 - OPTIONAL BIT OPT00334 PTF RO68756 COPY/INCLUDE IDMS MAP BINDS MAY BIND WRONG RECORD PTF RO68793 CSM CV ALREADY CONFIGURED SYSLIST DATASET ALREADY EXISTS PTF RO68821 WARMSTART ABENDS WITH A 3009 ABEND. PTF RO69000 CMS OPTION COMPATIBILITY WITH IBM APAR OA41945 PTF RO69042 I002 ERROR IN IDMSDBX3 RUNNING REORG PTF RO69145 OLP DOES NOT CORRECTLY FLUSH THE CA IDMS LOG BUFFERS PTF RO69290 MAPC: USER REGISTRATIONS NOT ALWAYS ENFORCED PTF RO69659 S0C4 RUNNING DB/AUDIT WHEN APF AUTHORIZED PTF RO69661 PRINT LOG GETS A S0C4. PTF RO69691 UNKNOWN KEYWORD 'RECURSIVE' DOING 'DISPLAY ALL' WITH BCF/OCF PTF RO69698 DISPLAY MESSAGE IF RESOURCE HOLDER TASK TERMINATED PTF RO69750 DC VTAM OPEN ERROR,RHDCPINT SPECIFIES NO IDMSDC PTF RO69775 SYSTEM MODULE PROGRAM CHECKED NEAR RHDCSCRM AT OFFSET 2A62. PTF RO69778 MOVE OF OVERLAPPING FIELDS MAY MOVE 'ALL SPACES' PTF RO69791 INDEX CORRUPTION AFTER RECOVERY. PTF RO69798 UPGRADE TO IDMS R18.0 YIELDS ADS CURRENCY ISSUES PTF RO69801 ACTIVITY LOGGING FOR COBOL COPY TO WRONG MODULE PTF RO69861 CV NUMBER 0 SHOWS AS A BLANK IN TASK ANALYZER RPTS PTF RO69889 EXTRACT JOURNAL GOES INTO LOOP. PTF The CA RS 1406 service count for this release is 21

2 CA IDMS CA RS 1406 Service List Description Type 18.0 RO59262 MAPC: USER REGISTRATIONS NOT ALWAYS ENFORCED PTF RO59865 OLP DOES NOT CORRECTLY FLUSH THE CA IDMS LOG BUFFERS PTF RO62948 SYSTEM MODULE PROGRAM CHECKED NEAR RHDCSCRM AT OFFSET 2A62. PTF RO66500 IDMS GIVES NO MESSAGE AFTER DCMT VARY DMCL NEW COPY. PTF RO66695 ADSC COMPILE CAN CHANGE RESULTS OF GOODDATEX(J) PTF RO66892 COPY/INCLUDE IDMS MAP BINDS MAY BIND WRONG RECORD PTF RO66978 EXIT 14 - OPTIONAL BIT OPT00334 PTF RO68830 INDEX CORRUPTION AFTER RECOVERY. PTF RO68986 CMS OPTION COMPATIBILITY WITH IBM APAR OA41945 PTF RO69472 UPGRADE TO IDMS R18.0 YIELDS ADS CURRENCY ISSUES PTF RO69646 S0C4 RUNNING DB/AUDIT WHEN APF AUTHORIZED PTF RO69657 PRINT LOG GETS A S0C4. PTF RO69694 FLOAT OF OPTIONAL APAR RO15092 TO 18 AND 18.5 PTF RO69697 DISPLAY MESSAGE IF RESOURCE HOLDER TASK TERMINATED PTF RO69776 MOVE OF OVERLAPPING FIELDS MAY MOVE 'ALL SPACES' PTF RO70014 EXTRACT JOURNAL GOES INTO LOOP. PTF The CA RS 1406 service count for this release is 16

3 CA IDMS 3 CA RS 1406 Service List for CAGJI00 FMID Service Description Type CAGJI00 RO59262 MAPC: USER REGISTRATIONS NOT ALWAYS ENFORCED PTF RO59865 OLP DOES NOT CORRECTLY FLUSH THE CA IDMS LOG BUFFERS PTF RO62948 SYSTEM MODULE PROGRAM CHECKED NEAR RHDCSCRM AT OFFSET 2A62. PTF RO66500 IDMS GIVES NO MESSAGE AFTER DCMT VARY DMCL NEW COPY. PTF RO66695 ADSC COMPILE CAN CHANGE RESULTS OF GOODDATEX(J) PTF RO66892 COPY/INCLUDE IDMS MAP BINDS MAY BIND WRONG RECORD PTF RO66978 EXIT 14 - OPTIONAL BIT OPT00334 PTF RO68830 INDEX CORRUPTION AFTER RECOVERY. PTF RO68986 CMS OPTION COMPATIBILITY WITH IBM APAR OA41945 PTF RO69472 UPGRADE TO IDMS R18.0 YIELDS ADS CURRENCY ISSUES PTF RO69646 S0C4 RUNNING DB/AUDIT WHEN APF AUTHORIZED PTF RO69657 PRINT LOG GETS A S0C4. PTF RO69694 FLOAT OF OPTIONAL APAR RO15092 TO 18 AND 18.5 PTF RO69697 DISPLAY MESSAGE IF RESOURCE HOLDER TASK TERMINATED PTF RO69776 MOVE OF OVERLAPPING FIELDS MAY MOVE 'ALL SPACES' PTF RO70014 EXTRACT JOURNAL GOES INTO LOOP. PTF The CA RS 1406 service count for this FMID is 16

4 CA IDMS 4 CA RS 1406 Service List for CAGJI50 FMID Service Description Type CAGJI50 RO66749 ADSC COMPILE CAN CHANGE RESULTS OF GOODDATEX(J) PTF RO67058 EXIT 14 - OPTIONAL BIT OPT00334 PTF RO68756 COPY/INCLUDE IDMS MAP BINDS MAY BIND WRONG RECORD PTF RO68793 CSM CV ALREADY CONFIGURED SYSLIST DATASET ALREADY EXISTS PTF RO68821 WARMSTART ABENDS WITH A 3009 ABEND. PTF RO69000 CMS OPTION COMPATIBILITY WITH IBM APAR OA41945 PTF RO69042 I002 ERROR IN IDMSDBX3 RUNNING REORG PTF RO69145 OLP DOES NOT CORRECTLY FLUSH THE CA IDMS LOG BUFFERS PTF RO69290 MAPC: USER REGISTRATIONS NOT ALWAYS ENFORCED PTF RO69659 S0C4 RUNNING DB/AUDIT WHEN APF AUTHORIZED PTF RO69661 PRINT LOG GETS A S0C4. PTF RO69691 UNKNOWN KEYWORD 'RECURSIVE' DOING 'DISPLAY ALL' WITH BCF/OCF PTF RO69698 DISPLAY MESSAGE IF RESOURCE HOLDER TASK TERMINATED PTF RO69750 DC VTAM OPEN ERROR,RHDCPINT SPECIFIES NO IDMSDC PTF RO69775 SYSTEM MODULE PROGRAM CHECKED NEAR RHDCSCRM AT OFFSET 2A62. PTF RO69778 MOVE OF OVERLAPPING FIELDS MAY MOVE 'ALL SPACES' PTF RO69791 INDEX CORRUPTION AFTER RECOVERY. PTF RO69798 UPGRADE TO IDMS R18.0 YIELDS ADS CURRENCY ISSUES PTF RO69801 ACTIVITY LOGGING FOR COBOL COPY TO WRONG MODULE PTF RO69861 CV NUMBER 0 SHOWS AS A BLANK IN TASK ANALYZER RPTS PTF RO69889 EXTRACT JOURNAL GOES INTO LOOP. PTF The CA RS 1406 service count for this FMID is 21

5 CA IDMS CA RS PTF RO RO66749 RO66749 M.C.S. ENTRIES = ++PTF (RO66749) ADSC COMPILE CAN CHANGE RESULTS OF GOODDATEX(J) Built-in function GOODDATEX examines 8-byte numeric strings and returns TRUE or FALSE depending on whether the string is a date in a standard format, for example string (02/21/1948) is a valid 'C'alendar date and GOODDATEX returns a TRUE result. On release 15.0, GOODDATEX incorrectly accepted 7-byte strings when checking Julian dates, for example incorrectly returned TRUE. The correct date format is The problem was that non-numeric 7-byte Julian dates, such as 'XX020130', incorrectly also returned result TRUE. This was corrected on release 16.0 with an apar that correctly distinguished between valid and invalid Julian dates. However, it assumed that the date field was 8 bytes long, which is what the ADS Reference Guide required and what the vast majority of ADS dialogs use. However, once the apar was applied, recompiling any dialog that had incorrectly coded GOODDATEX to use a 7-byte Julian date field returned FALSE on every JULIAN date test. Since no site should be required to search all dialogs for built-in function GOODDATEX that uses a 7-byte Julian date field, and no way exists to predict when dialogs will need to be compiled, rather than cause ADSC to produce an error message on an incorrectly coded GOODDATEX command, this apar will add support for 7-byte Julian dates. In rare cases, compile of a dialog on release 16.0 or later will change the result from built-in function GOODDATEX. When using a 7-byte Julian date that previously tested as VALID, after compile GOODDATEX might return result 'INVALID DATE'. A dialog can compile successfully yet occasionally run with an incorrect flow of control through the dialog resulting in invalid results from the dialog. Change the format of the Julian date field to 8 bytes with the first byte equal to '0' as described in section 7.15 GOODDATEX in the ADS Reference Guide. PRODUCT(S) AFFECTED: CA IDMS Release 18.5 CA IDMS Release 18.0 CA IDMS Release 17.0 IDMS 4766 Copyright (C) 2014 CA. All rights reserved. R00183-AGJ185-SP1 DESC(ADSC COMPILE CAN CHANGE RESULTS OF GOODDATEX(J)). FMID (CAGJI50) PRE ( RO59824 RO66250 ) SUP ( TR66749 )

6 CA IDMS CA RS PTF RO RO67058 RO67058 M.C.S. ENTRIES = ++PTF (RO67058) EXIT 14 - OPTIONAL BIT OPT00334 This is an enhancement to add an optional bit which will allow users to skip all USER EXIT 14 processing unless issuing a READY request in UPDATE mode. This can result in fewer swaps to and from the ziip engine and the CP which can increase performance. To implement this function you must code the following optional bit in module RHDCOPTF: #DEFOPTF OPT00334 EXIT 14 will continue to be processed regardless of the mode of the request. EXIT 14 will continue to be processed regardless of the mode of the request. There is no circumvention for this problem. PRODUCT(S) AFFECTED: CA IDMS Release 18.0 CA IDMS Release 18.5 IDMS 4797 Copyright (C) 2014 CA. All rights reserved. R00190-AGJ185-SP1 DESC(EXIT 14 - OPTIONAL BIT OPT00334). FMID (CAGJI50) PRE ( RO57307 RO61262 RO63133 RO63736 ) SUP ( AR59738 AR63133 FC62134 RI65898 RO55219 RO56324 RO58646 RO58951 RO59460 RO59738 RO60139 RO60928 RO62469 RO63312 RO65391 RO65899 RO66439 RO66820 RO66868 RO67946 RO68913 TR48954 TR49070 TR55219 TR56324 TR58646 TR58669 TR58951 TR59460 TR59738 TR60139 TR60928 TR62469 TR63312 TR65391 TR65899 TR66166 TR66439 TR66697 TR66820 TR66868 TR67058 TR67946 TR68045 TR68913 ) ++HOLD (RO67058) SYSTEM FMID(CAGJI50) REASON (ACTION ) DATE (14104) COMMENT ( CA IDMS Base Option Release 18.5 SEQUENCE Before Apply PURPOSE Enable the use of optional functionality USERS AFFECTED All IDMS users making use of Optional apars KNOWLEDGE SMP/E, Assemble #DEFOPTF macro, and/or ability to change REQUIRED SYSIDMS parameters and perform SYSGEN modification ACCESS CA IDMS CSI and libraries, CA IDMS Startup JCL, SYSGEN REQUIRED compiler ************************** * STEPS TO PERFORM * ************************** To implement the functionality introduced by this PTF you will need to Code the following #DEFOPTF in your RHDCOPTF module and then re-assemble and link the RHDCOPTF module. Code the following #DEFOPTF in your RHDCOPTF module to activate this optional code: #DEFOPTF OPT00334 ).

7 CA IDMS CA RS PTF RO RO68756 RO68756 M.C.S. ENTRIES = ++PTF (RO68756) COPY/INCLUDE IDMS MAP BINDS MAY BIND WRONG RECORD BIND MAP RECORD may bind to the wrong record when a map record is copied into a program multiple times under different synonym names. Also, COPY IDMS MAP-BINDS may not copy the map record into the program. The generated BIND MAP RECORD statement specifies the last synonym copied instead of the map record name. Compile errors may occur in the program or map data may not be returned to the record the program expects. Manually code the BIND MAP and BIND MAP record statements. PRODUCT(S) AFFECTED: CA IDMS Base Option Release 18.5 CA IDMS Base Option Release 18.0 CA IDMS Release 17.0 IDMS 4443 Copyright (C) 2014 CA. All rights reserved. R00216-AGJ185-SP1 DESC(COPY/INCLUDE IDMS MAP BINDS MAY BIND WRONG RECORD). FMID (CAGJI50) SUP ( TR68756 )

8 CA IDMS CA RS PTF RO RO68793 RO68793 M.C.S. ENTRIES = ++PTF (RO68793) CSM CV ALREADY CONFIGURED SYSLIST DATASET ALREADY EXISTS A CSM CV_ALREADY_CONFIGURED configuration will fail on implementation if a CV_ALREADY_CONFIGURED job has already been run against the same full configuration. The second configuration will fail because it attempts to allocate a SYSLST file with the same DSN that was created in the first CV_ALREADY_CONFIGURED. A second CV_ALREADY_CONFIGURED implemenation will fail with the following error: MSMC0236E Service validation error: Dataset should not exist Low. A second CV_ALREADY_CONFIGURED implementation will fail. Rename the SYSLST DSN that was created in the first CV_ALREADY_CONFIGURED configuration. PRODUCT(S) AFFECTED: CA IDMS Release 18.0 CA IDMS Release 18.5 IDMS 4826 Copyright (C) 2014 CA. All rights reserved. R00217-AGJ185-SP1 DESC(CSM CV ALREADY CONFIGURED SYSLIST DATASET ALREADY EXISTS). FMID (CAGJI50) PRE ( RO68724 ) SUP ( RO57418 RO65749 TR57418 TR65749 TR68793 )

9 CA IDMS CA RS PTF RO RO68821 RO68821 M.C.S. ENTRIES = ++PTF (RO68821) WARMSTART ABENDS WITH A 3009 ABEND. The user brings up a system using the DATE_SIMULATOR. After some time, the system is shutdown, and restarted. This system runs, and then is CANCELLED. The subsequent warmstart fails with the following; +IDMS DC V65 Starting WARMSTART +IDMS DC V65 Will begin Recovery with Journal SYSJRNL1 +IDMS DC V65 The Starting Segment Number is 7 +IDMS DC V65 Rebuilding run unit table starting at RBN 164 +IDMS DC V65 IDMSWARM ERRSWX= 022 MODNO= 049 +IDMS DC V65 RECOVERY did NOT START - See ERROR MESSAGE +IDMS DC V65 ** IOP Address 96DDA548 ** Work area address USER COMPLETION CODE=3009 A system is started using the DATE SIMULATOR. It is shutdown, and restarted. After some time, the system was cancelled, and restarted. The restart failed in warmstart, with the following messages; +IDMS DC V65 Starting WARMSTART +IDMS DC V65 Will begin Recovery with Journal SYSJRNL1 +IDMS DC V65 The Starting Segment Number is 7 +IDMS DC V65 Rebuilding run unit table starting at RBN 164 +IDMS DC V65 IDMSWARM ERRSWX= 022 MODNO= 049 +IDMS DC V65 RECOVERY did NOT START - See ERROR MESSAGE +IDMS DC V65 ** IOP Address 96DDA548 ** Work area address USER COMPLETION CODE=3009 The database must then be restored, and the journals formated, before the system can be restarted. The system and it's database is unavailable until the database is restored, and the journals are formated. If using the DATE SIMULATOR, format the journals before starting the system. PRODUCTS AFFECTED: PRODUCT(S) AFFECTED: CA IDMS Release 17.0 PRODUCT(S) AFFECTED: CA IDMS Release 18.0 PRODUCT(S) AFFECTED: CA IDMS Release 18.5 IDMS 4836 Copyright (C) 2014 CA. All rights reserved. R00218-AGJ185-SP1 DESC(WARMSTART ABENDS WITH A 3009 ABEND.). FMID (CAGJI50) SUP ( RO59386 TR59386 TR68821 )

10 CA IDMS CA RS PTF RO RO69000 RO69000 M.C.S. ENTRIES = ++PTF (RO69000) CMS OPTION COMPATIBILITY WITH IBM APAR OA41945 CA IDMS clients with the CA IDMS CMS Option installed on a z/os 1.12 or higher guest LPAR must install this CA IDMS PTF before installing IBM Apar OA CMS Batch or UCFCMS access to the z/os guest LPAR will not execute if IBM Apar OA41945 is applied prior to applying this CA IDMS PTF and a z/os restart is needed which will clear the bits in Control Register 0. VMCF communication to the z/os guest LPAR will be disabled and no CMS batch access or UCFCMS sessions can be established. There is no circumvention. PRODUCTS AFFECTED: CA IDMS Release 17.0 CA IDMS Release 18.0 CA IDMS Release 18.5 PRODUCT(S) AFFECTED: CA IDMS Base Option Release 18.0 CA IDMS Base Option Release 18.5 IDMS 4690 Copyright (C) 2014 CA. All rights reserved. R00223-AGJ185-SP1 DESC(CMS OPTION COMPATIBILITY WITH IBM APAR OA41945). FMID (CAGJI50) SUP ( TR69000 ) ++HOLD (RO69000) SYSTEM FMID(CAGJI50) REASON (ACTION ) DATE (14093) COMMENT ( CA IDMS Base Option Release 18.5 SEQUENCE After Apply PURPOSE Regenerate and reload the IDMS SVC USERS AFFECTED All IDMS users KNOWLEDGE Assemble the IDMS SVC REQUIRED Run the "CAIRIM" utility to reload the IDMS SVC ACCESS Assemble the IDMS SVC REQUIRED Run the "CAIRIM" utililty ************************** * STEPS TO PERFORM * ************************** The CA IDMS SVC must be regenerated as described in the IDMS SYSTEM operations guide. Any CA IDMS CV in use on a z/os system must be refreshed using the "CAIRIM" utility as described in the CA IDMS Installation guide. ).

11 CA IDMS CA RS PTF RO RO69042 RO69042 M.C.S. ENTRIES = ++PTF (RO69042) I002 ERROR IN IDMSDBX3 RUNNING REORG The REORG utility may experience an I002 abend in module IDMSDBX3 during a REBUILD3 task of the reload phase. This abend is dependent on the sequence of data within the task and will only occur when MPGI support is implemented and the segments involved use a varying number of records per page. Any of the REORG jobs processing a reload phase may experience an I002 abend in module IDMSDBX3 which will generate the following messages. +IDMS UT Internal Error Encountered. Program IDMSDBX3 code 2 +IDMS DC IDMS job abending with abend code I002 The site may not be able to complete the planned reorganization of their database. Modifying the number of areas specified on the utility's AREA parameter may allow the job to execute successfully. PRODUCTS AFFECTED: CA IDMS Release 18.5 IDMS 4845 Copyright (C) 2014 CA. All rights reserved. R00225-AGJ185-SP1 DESC(I002 ERROR IN IDMSDBX3 RUNNING REORG). FMID (CAGJI50) PRE ( RO67685 ) SUP ( TR69042 )

12 CA IDMS CA RS PTF RO RO69145 RO69145 M.C.S. ENTRIES = ++PTF (RO69145) OLP DOES NOT CORRECTLY FLUSH THE CA IDMS LOG BUFFERS When OLP is invoked, the latest data written to the IDMS LOG is not available. CA IDMS log data is not always immediately visible when the OLP task is invoked. The latest data written to the log is not available. Users have to wait for the log buffer to flush. After downloading the apar, the system must be recycled for the apar to take effect. If you enter; 'VARY NUC MOD RHDCLGSD NEW COPY'. The following message will be issued; IDMS DC USER:*** RELOAD FOR NUCLEUS MODULE RHDCLGSD NOT PERMITTED Issue a DCMT WRITE STATS or a SHOWMAP RHDCOPER. This will cause a large amount of data to be written to the log, which will force a flush of the log buffers. PRODUCT(S) AFFECTED: CA IDMS Release 17.0 PRODUCT(S) AFFECTED: CA IDMS Release 18.0 PRODUCT(S) AFFECTED: CA IDMS Release 18.5 IDMS 4209 Copyright (C) 2014 CA. All rights reserved. R00228-AGJ185-SP1 DESC(OLP DOES NOT CORRECTLY FLUSH THE CA IDMS LOG BUFFERS). FMID (CAGJI50) SUP ( TR69145 )

13 CA IDMS CA RS PTF RO RO69290 RO69290 M.C.S. ENTRIES = ++PTF (RO69290) MAPC: USER REGISTRATIONS NOT ALWAYS ENFORCED PROBLEM DESCRIPTION MAPC enforcement of entity-occurrence security (USER and entity PUBLIC ACCESS) does not occur unless entity-type group security (USER AUTHORITY and SET OPTIONS SECURITY FOR... IS) is enabled. MAPs with PUBLIC ACCESS IS DISPLAY can be updated by MAPC users not authorized by use of user registrations unless SECURITY FOR IDMS-DC IS ON. If RO15200 or RO15199 are applied, SECURITY FOR IDD IS ON will cause user registrations to be enforced, as well. No impact if either entity-type security as indicated above, is ON. Otherwise, any user registrations are not properly enforced. Set either IDMS-DC or IDD entity-type dictionary security to ON. PRODUCT(S) AFFECTED: CA IDMS Release 18.0 Release 17.0 IDMS 4290 Copyright (C) 2014 CA. All rights reserved. R00231-AGJ185-SP1 DESC(MAPC: USER REGISTRATIONS NOT ALWAYS ENFORCED). FMID (CAGJI50) SUP ( TR69290 )

14 CA IDMS CA RS PTF RO RO69659 RO69659 M.C.S. ENTRIES = ++PTF (RO69659) S0C4 RUNNING DB/AUDIT WHEN APF AUTHORIZED A S0C4 abend may occur while running the DB/AUDIT product if STEPLIB is APF authorized. A S0C4 abend may occur within module GSSNKWP. Users will not be able to successfully use the DB/AUDIT product to audit or repair their CA IDMS databases. Insert a non-authorized library into the jobstep's STEPLIB concatentation. PRODUCTS AFFECTED: CA DB/AUDIT Release 18.0 CA DB/AUDIT Release 18.5 IDMS 4854 Copyright (C) 2014 CA. All rights reserved. R00233-AGJ185-SP1 DESC(S0C4 RUNNING DB/AUDIT WHEN APF AUTHORIZED). FMID (CAGJI50) SUP ( TR69659 )

15 CA IDMS CA RS PTF RO RO69661 RO69661 M.C.S. ENTRIES = ++PTF (RO69661) PRINT LOG GETS A S0C4. The PRINT LOG or ARCHIVE LOG utility gets a S0C4 when trying to offload the DDLDCLOG. The DDLDCLOG fills, and a PRINT or ARCHIVE LOG is run to offload the LOG. The PRINT LOG fails with a S0C4. IDMS waits for the log to be archived. The DDLDCLOG fills, and a PRINT LOG is run to offload the LOG. The PRINT LOG abends with a S0C4. Any reruns of the PRINT LOG also fail. The system had to be cancelled, and the LOG formatted. The system was restarted. Warmstart was successful, and the access to the system was resumed. While the system was down, access to the database was denied. There is no circumvention. PRODUCTS AFFECTED: PRODUCT(S) AFFECTED: CA IDMS Release 17.0 PRODUCT(S) AFFECTED: CA IDMS Release 18.0 PRODUCT(S) AFFECTED: CA IDMS Release 18.5 IDMS 4761 Copyright (C) 2014 CA. All rights reserved. R00234-AGJ185-SP1 DESC(PRINT LOG GETS A S0C4.). FMID (CAGJI50) PRE ( RO67394 ) SUP ( RO65370 TR65370 TR69661 )

16 CA IDMS CA RS PTF RO RO69691 RO69691 M.C.S. ENTRIES = ++PTF (RO69691) UNKNOWN KEYWORD 'RECURSIVE' DOING 'DISPLAY ALL' WITH BCF/OCF With 18.5, the keyword 'RECURSIVE' introduces new functionality to IDD/IDMSDDDL and BCF/OCF. When used in a 'DISPLAY ALL... AS SYNTAX or AS COMMENT' statement, it will append the 'AS SYNTAX' or 'AS COMMENT' string to the end of each generated line of output. However, this is not true for all entities. When used to display SQL entities like TABLE, SCHEMA,... or Security entities like USER, GROUP,... with BCF/OCF, it will result in syntax error message 'UNKNOWN KEYWORD' being produced. The following statement will be correctly processed by BCF/OCF: DISPLAY ALL SEGMENT AS SYNTAX RECURSIVE VERB PUNCH; and will produce the following: PUNCH SEGMENT APPLCCDB AS SYNTAX ; PUNCH SEGMENT APPLDICT AS SYNTAX ; PUNCH SEGMENT ASFDICT AS SYNTAX ; However, executing the statement: DISPLAY ALL TABLE AS SYNTAX RECURSIVE VERB PUNCH; will result in the following being displayed: *+ Status = -4 SQLSTATE = Messages follow: *+ DB Tnn C-4M6018: ERRORS detected in processing request *+ E DC UNKNOWN KEYWORD You will not be able to submit punched output directly to BCF/OCF. No circumvention available. PRODUCT(S) AFFECTED: CA IDMS Release 18.5 IDMS 4852 Copyright (C) 2014 CA. All rights reserved. R00235-AGJ185-SP1 DESC(UNKNOWN KEYWORD 'RECURSIVE' DOING 'DISPLAY ALL' WITH BCF/OCF). FMID (CAGJI50) SUP ( TR69691 )

17 CA IDMS CA RS PTF RO RO69698 RO69698 M.C.S. ENTRIES = ++PTF (RO69698) DISPLAY MESSAGE IF RESOURCE HOLDER TASK TERMINATED When a task stalls waiting on a db-key resource and the resource holder is a terminated task, no information is provided to this effect. There are no DC001009/DC messages displayed to support the stalled task messages DC and DC If the task holding the resource is terminated, no DC or DC messages are possible. A message to this effect should be provided. It is not possible to determine that the resource being waited on was held by a terminated task. None. PRODUCT(S) AFFECTED: CA IDMS Release 17.0 CA IDMS Release 18.0 CA IDMS release 18.5 IDMS 4636 Copyright (C) 2014 CA. All rights reserved. R00236-AGJ185-SP1 DESC(DISPLAY MESSAGE IF RESOURCE HOLDER TASK TERMINATED). FMID (CAGJI50) PRE ( RO57307 RO60740 ) SUP ( TR58462 TR59462 TR69698 )

18 CA IDMS CA RS PTF RO RO69750 RO69750 M.C.S. ENTRIES = ++PTF (RO69750) DC VTAM OPEN ERROR,RHDCPINT SPECIFIES NO IDMSDC If a VTAM network is not in use and IDMSDC is not listed as an installed product in the RHDCPINT module, then CA IDMS VTAM open error messages DC and DC are still issued for the default VTAM01 line defined during the configuration process of the CA IDMS/DC system. During CA IDMS CV startup, CA IDMS VTAM open error messages DC VTAM FUNCTION OPEN ACB ERROR CODE = 005A0000 APPLID = DC LINE CANNOT BE RESTART are displayed on the system log. There is no impact on CA IDMS CV startup. Delete the lterm, pterm and line definitions for line VTAM01 by executing a CA IDMS sysgen to avoid the DC and DC error messages. PRODUCT(S) AFFECTED: CA IDMS Release 18.5 CA IDMS Release 18.0 IDMS 4856 Copyright (C) 2014 CA. All rights reserved. R00237-AGJ185-SP1 DESC(DC VTAM OPEN ERROR,RHDCPINT SPECIFIES NO IDMSDC). FMID (CAGJI50) SUP ( TR69750 )

19 CA IDMS CA RS PTF RO RO69775 RO69775 M.C.S. ENTRIES = ++PTF (RO69775) SYSTEM MODULE PROGRAM CHECKED NEAR RHDCSCRM AT OFFSET 2A62. The IDMS system crashes with a SYSTEM MODULE PROGRAM CHECK NEAR RHDCSCRM, or takes an unexpected SVC dump, and hangs. IDMS gets the following error; DC V51 T3193 SYSTEM MODULE PROGRAM CHECKED NEAR RHDCSCRM AT OFFSET 2A62 This is followed by a 3970 system crash. The system may also take a SVC dump, and then hang. The system must then be canceled, and restarted. In either case, the system crashed, and had to be restarted. This resulted in a loss of production time, and access to the database. There is no circumvention. PRODUCTS AFFECTED: PRODUCT(S) AFFECTED: CA IDMS Release 17.0 PRODUCT(S) AFFECTED: CA IDMS Release 18.0 PRODUCT(S) AFFECTED: CA IDMS Release 18.5 IDMS 4687 Copyright (C) 2014 CA. All rights reserved. R00238-AGJ185-SP1 DESC(SYSTEM MODULE PROGRAM CHECKED NEAR RHDCSCRM AT OFFSET 2A62.). FMID (CAGJI50) SUP ( TR69775 )

20 CA IDMS CA RS PTF RO RO69778 RO69778 M.C.S. ENTRIES = ++PTF (RO69778) MOVE OF OVERLAPPING FIELDS MAY MOVE 'ALL SPACES' The result from a MOVE of a subordinate element to its GROUP element can possibly set the entire GROUP element to SPACES whenever a dialog is compiled without the ADSC 'Symbol table is enabled' option set. NOTE: This PTF is the float of 17.x PTF RO69319 (z/os) and corresponding VSE PTF RO Whenever the first subordinate element in a GROUP element is moved to its GROUP element, the result of the MOVE will be that the entire GROUP element will contain SPACES if the dialog was compiled without the ADSC 'Symbol table is enabled' option set. For example, 02 EMP-NAME USAGE IS DISPLAY. 03 EMP-FIRST-NAME PICTURE IS X(10) USAGE IS DISPLAY. 03 EMP-LAST-NAME PICTURE IS X(15) USAGE IS DISPLAY. MOVE EMP-FIRST-NAME-0415 TO EMP-NAME * No matter what value is in EMP-FIRST-NAME-0415, after the MOVE, EMP-FIRST-NAME-0415 and EMP-LAST-NAME-0415 will both contain SPACES. The impact is unpredictable. In sites that test using the ADSC 'Symbol table is enabled' then turn off this option when the dialog is migrated to production, the error will appear on only the production system. It could appear as bad data, incorrect application flow of control or as an abend. Turn on the ADSC 'Symbol table is enabled' option and recompile the dialog. PRODUCT(S) AFFECTED: CA IDMS Release 18.0 CA IDMS Release 18.5 IDMS 4858 Copyright (C) 2014 CA. All rights reserved. R00239-AGJ185-SP1 DESC(MOVE OF OVERLAPPING FIELDS MAY MOVE 'ALL SPACES'). FMID (CAGJI50) SUP ( TR69778 )

21 CA IDMS CA RS PTF RO RO69791 RO69791 M.C.S. ENTRIES = ++PTF (RO69791) INDEX CORRUPTION AFTER RECOVERY. The IDMS system starts to get 1143 abends. Further investigation reveals that the index is corrupted. Transactions start to abend with 1143 abends. All of these abends appear to be related to the same index. The index had to be manually fixed, before the 1143 stopped. There is no circumvention. PRODUCTS AFFECTED: PRODUCT(S) AFFECTED: CA IDMS Release 17.0 PRODUCT(S) AFFECTED: CA IDMS Release 18.0 PRODUCT(S) AFFECTED: CA IDMS Release 18.5 IDMS 4837 Copyright (C) 2014 CA. All rights reserved. R00240-AGJ185-SP1 DESC(INDEX CORRUPTION AFTER RECOVERY.). FMID (CAGJI50) SUP ( RO54971 RO56735 TR54971 TR56735 TR69791 )

22 CA IDMS CA RS PTF RO RO69798 RO69798 M.C.S. ENTRIES = ++PTF (RO69798) UPGRADE TO IDMS R18.0 YIELDS ADS CURRENCY ISSUES Upgrading to (or through) IDMS Release 18.0 may result in application-level errors for applications using ADS Online. Problems occur for applications that extend Run Units to lower-level dialogs, which then in-turn issue 'DISPLAY' commands (thus terminating the Run Unit). When the low-level dialog resumes, a new Run Unit is created & passed back upwards. Under certain situations this new Run Unit may terminate prematurely, resulting in currency issues in the calling dialog. Various IDMS Database access failures may occur owing to the improper termination of extended run units. ADS/Online application-level failures. Back-off your upgrade to release PRODUCT(S) AFFECTED: CA IDMS Base Option Release 18.0 CA IDMS Base Option Release 18.5 IDMS 4846 ADS RUNTIME YIELDS DC WITH EXTENDED RU'S Various problems may occur when an Extended Run Unit is passed between multiple dialogs that have inconsistent SYMBOL TABLE settings, and which terminate the RU in a low-level dialog. The most common problem will be: DC CA ADS ABEND. COMMAND WITH INVALID CLASS TYPE After the DISPLAY has been issued, ADS/Online may abend with the following error message: DC CA ADS ABEND. COMMAND WITH INVALID CLASS TYPE Alternatively, a program check may occur within module ADSOMAIN. Medium, dialogs that execute as described in the Problem Description will abend. Compile all dialogs with either SYMBOL TABLE = YES or SYMBOL TABLE = NO PRODUCT(S) AFFECTED: CA IDMS Release 17.0 CA IDMS Release 18.0 CA IDMS Release 18.5 IDMS 4855 Copyright (C) 2014 CA. All rights reserved. R00241-AGJ185-SP1 DESC(UPGRADE TO IDMS R18.0 YIELDS ADS CURRENCY ISSUES). FMID (CAGJI50) PRE ( RO59398 RO69066 ) SUP ( TR69798 )

23 CA IDMS CA RS PTF RO RO69801 RO69801 M.C.S. ENTRIES = ++PTF (RO69801) ACTIVITY LOGGING FOR COBOL COPY TO WRONG MODULE If program activity logging is enabled, IDMSDMLC will add an activity for a COBOL COPY module statement. If a module of the same name exists in the dictionary, IDMSDMLC is incorrectly linking it to the program. The COBOL COPY statement will copy the module from a library. IDMSDMLC should add a dummy module to the dictionary for cross-referencing purposes but not link the program to an existing module added through IDD. This PTF also introduces a new parameter to avoid cross-referencing the information from the COBOL COPY statement when program activity logging is enabled. The parameter XREFCOPY=YES/NO can be specified on the EXEC parm, in the default precompiler options module or on a PARM= SYSIDMS parameter. The default is YES. Specifing NO will instruct the precompiler not to store a dummy module to cross reference the COBOL module with the program. No errors occur but if you issue a display for the program in IDD, an incorrect module version may be in the MODULE USED statement. The cross-referencing module information for a program will be incorrect. You can suppress activity logging by using the *NO-ACTIVITY-LOG option in your COBOL source or *RETRIEVAL. PRODUCT(S) AFFECTED: CA IDMS Base Option Release 18.5 CA IDMS Release 18.0 CA IDMS Release 17.0 IDMS 4779 Copyright (C) 2014 CA. All rights reserved. R00242-AGJ185-SP1 DESC(ACTIVITY LOGGING FOR COBOL COPY TO WRONG MODULE). FMID (CAGJI50) PRE ( RO68756 ) SUP ( TR69801 )

24 CA IDMS CA RS PTF RO RO69861 RO69861 M.C.S. ENTRIES = ++PTF (RO69861) CV NUMBER 0 SHOWS AS A BLANK IN TASK ANALYZER RPTS On the Task Analyzer reports, there is only a blank where the number of the CV should be when a CV number is 0. There is a blank on the CV number space in the Task Analyzer reports. User cannot see CV number. NONE. PRODUCT(S) AFFECTED: CA IDMS Base Option Release 18.0 PRODUCT(S) AFFECTED: CA IDMS Base Option Release 18.5 IDMS 4777 Copyright (C) 2014 CA. All rights reserved. R00243-AGJ185-SP1 DESC(CV NUMBER 0 SHOWS AS A BLANK IN TASK ANALYZER RPTS). FMID (CAGJI50) PRE ( RO61933 ) SUP ( TR66967 TR69861 ) ++HOLD (RO69861) SYSTEM FMID(CAGJI50) REASON (ACTION ) DATE (14122) COMMENT ( CA IDMS Base Option Release 18.5 SEQUENCE After Apply PURPOSE Update Reports USERS AFFECTED All IDMS users KNOWLEDGE REQUIRED Update definitions in the Dictionary ACCESS REQUIRED Ability to run IDMSDDDL in batch or use IDD online ************************** * STEPS TO PERFORM * ************************** After installing this PTF, please use the IDMSDDDL utility to update the dictionary which contains reports, normally the TOOLDICT dictionary, with the input in source member USFDDDL1, USFDDDL2, USFDDDL3 and USFDDDL4. The source will be in the SMP/E CAGJSRC library. ).

25 CA IDMS CA RS PTF RO RO69889 RO69889 M.C.S. ENTRIES = ++PTF (RO69889) EXTRACT JOURNAL GOES INTO LOOP. The IDMSBCF EXTRACT JOURNAL loops, or ends with a return code of U0016. In the case of the U0016, following messages are found : UT JOURNAL SEQUENCE ERROR--PREV -6,123,769,593,312,575,488 CURR -6,123,769,593,312,575,488 When running the EXTRACT JOURNAL, with RO66435 applied, the job either loops, or ends with a return code of U0016. The EXTRACT JOURNAL either loops, or ends with a return code of U0016. Back out RO66435, and rerun the Extract Journal. PRODUCT(S) AFFECTED: CA IDMS Base Option Release 18.0 CA IDMS Base Option Release 18.5 IDMS 4859 Copyright (C) 2014 CA. All rights reserved. R00245-AGJ185-SP1 DESC(EXTRACT JOURNAL GOES INTO LOOP.). FMID (CAGJI50) PRE ( RO66435 ) SUP ( TR69889 )

26 CA IDMS CA RS PTF RO RO59262 RO59262 M.C.S. ENTRIES = ++PTF (RO59262) MAPC: USER REGISTRATIONS NOT ALWAYS ENFORCED PROBLEM DESCRIPTION MAPC enforcement of entity-occurrence security (USER and entity PUBLIC ACCESS) does not occur unless entity-type group security (USER AUTHORITY and SET OPTIONS SECURITY FOR... IS) is enabled. MAPs with PUBLIC ACCESS IS DISPLAY can be updated by MAPC users not authorized by use of user registrations unless SECURITY FOR IDMS-DC IS ON. If RO15200 or RO15199 are applied, SECURITY FOR IDD IS ON will cause user registrations to be enforced, as well. No impact if either entity-type security as indicated above, is ON. Otherwise, any user registrations are not properly enforced. Set either IDMS-DC or IDD entity-type dictionary security to ON. PRODUCT(S) AFFECTED: CA IDMS Release 18.0 Release 17.0 IDMS 4290 Copyright (C) 2014 CA. All rights reserved. R00535-AGJ180-SP1 DESC(MAPC: USER REGISTRATIONS NOT ALWAYS ENFORCED). FMID (CAGJI00) SUP ( RO47789 TR41488 TR47789 TR47793 TR59262 )

27 CA IDMS CA RS PTF RO RO59865 RO59865 M.C.S. ENTRIES = ++PTF (RO59865) OLP DOES NOT CORRECTLY FLUSH THE CA IDMS LOG BUFFERS When OLP is invoked, the latest data written to the IDMS LOG is not available. CA IDMS log data is not always immediately visible when the OLP task is invoked. The latest data written to the log is not available. Users have to wait for the log buffer to flush. After downloading the apar, the system must be recycled for the apar to take effect. If you enter; 'VARY NUC MOD RHDCLGSD NEW COPY'. The following message will be issued; IDMS DC USER:*** RELOAD FOR NUCLEUS MODULE RHDCLGSD NOT PERMITTED Issue a DCMT WRITE STATS or a SHOWMAP RHDCOPER. This will cause a large amount of data to be written to the log, which will force a flush of the log buffers. PRODUCT(S) AFFECTED: CA IDMS Release 17.0 PRODUCT(S) AFFECTED: CA IDMS Release 18.0 PRODUCT(S) AFFECTED: CA IDMS Release 18.5 IDMS 4209 Copyright (C) 2014 CA. All rights reserved. R00543-AGJ180-SP1 DESC(OLP DOES NOT CORRECTLY FLUSH THE CA IDMS LOG BUFFERS). FMID (CAGJI00) PRE ( RO39073 RO41610 RO46188 ) SUP ( RO41142 TR41142 TR59865 )

28 CA IDMS CA RS PTF RO RO62948 RO62948 M.C.S. ENTRIES = ++PTF (RO62948) SYSTEM MODULE PROGRAM CHECKED NEAR RHDCSCRM AT OFFSET 2A62. The IDMS system crashes with a SYSTEM MODULE PROGRAM CHECK NEAR RHDCSCRM, or takes an unexpected SVC dump, and hangs. IDMS gets the following error; DC V51 T3193 SYSTEM MODULE PROGRAM CHECKED NEAR RHDCSCRM AT OFFSET 2A62 This is followed by a 3970 system crash. The system may also take a SVC dump, and then hang. The system must then be canceled, and restarted. In either case, the system crashed, and had to be restarted. This resulted in a loss of production time, and access to the database. There is no circumvention. PRODUCTS AFFECTED: PRODUCT(S) AFFECTED: CA IDMS Release 17.0 PRODUCT(S) AFFECTED: CA IDMS Release 18.0 PRODUCT(S) AFFECTED: CA IDMS Release 18.5 IDMS 4687 Copyright (C) 2014 CA. All rights reserved. R00577-AGJ180-SP1 DESC(SYSTEM MODULE PROGRAM CHECKED NEAR RHDCSCRM AT OFFSET 2A62.). FMID (CAGJI00) SUP ( TR62948 )

29 CA IDMS CA RS PTF RO RO66500 RO66500 M.C.S. ENTRIES = ++PTF (RO66500) IDMS GIVES NO MESSAGE AFTER DCMT VARY DMCL NEW COPY. A user makes changes to the DMCL. To incorporate the changes, the user issues a DCMT VARY DMCL NEW COPY. The user gets no display of the DMCL changes, nor response from IDMS. The user tries the DCMT VARY DMCL NEW COPY again, but finds that the changes have already been applied. A user issues a DCMT VARY DMCL NEW COPY. They do not get any response from IDMS, but the changes are incorporated into the DMCL. Since IDMS does not relate any information about the DMCL changes, the user has no idea what changes were made, or if they were incorporated into the DMCL. There is no circumvention. PRODUCTS AFFECTED: PRODUCT(S) AFFECTED: CA IDMS Release 18.0 PRODUCT(S) AFFECTED: CA IDMS Release 18.5 IDMS 4788 Copyright (C) 2014 CA. All rights reserved. R00616-AGJ180-SP1 DESC(IDMS GIVES NO MESSAGE AFTER DCMT VARY DMCL NEW COPY.). FMID (CAGJI00) PRE ( RO35804 RO48379 RO57434 ) SUP ( AC57521 RO26893 RO27707 RO27886 RO34918 RO36963 RO38054 RO41036 RO51132 RO51972 RO52570 RO57519 TR26893 TR27707 TR27886 TR34918 TR36963 TR38054 TR41036 TR47810 TR51132 TR51972 TR52570 TR57519 TR66500 )

30 CA IDMS CA RS PTF RO RO66695 RO66695 M.C.S. ENTRIES = ++PTF (RO66695) ADSC COMPILE CAN CHANGE RESULTS OF GOODDATEX(J) Built-in function GOODDATEX examines 8-byte numeric strings and returns TRUE or FALSE depending on whether the string is a date in a standard format, for example string (02/21/1948) is a valid 'C'alendar date and GOODDATEX returns a TRUE result. On release 15.0, GOODDATEX incorrectly accepted 7-byte strings when checking Julian dates, for example incorrectly returned TRUE. The correct date format is The problem was that non-numeric 7-byte Julian dates, such as 'XX020130', incorrectly also returned result TRUE. This was corrected on release 16.0 with an apar that correctly distinguished between valid and invalid Julian dates. However, it assumed that the date field was 8 bytes long, which is what the ADS Reference Guide required and what the vast majority of ADS dialogs use. However, once the apar was applied, recompiling any dialog that had incorrectly coded GOODDATEX to use a 7-byte Julian date field returned FALSE on every JULIAN date test. Since no site should be required to search all dialogs for built-in function GOODDATEX that uses a 7-byte Julian date field, and no way exists to predict when dialogs will need to be compiled, rather than cause ADSC to produce an error message on an incorrectly coded GOODDATEX command, this apar will add support for 7-byte Julian dates. In rare cases, compile of a dialog on release 16.0 or later will change the result from built-in function GOODDATEX. When using a 7-byte Julian date that previously tested as VALID, after compile GOODDATEX might return result 'INVALID DATE'. A dialog can compile successfully yet occasionally run with an incorrect flow of control through the dialog resulting in invalid results from the dialog. Change the format of the Julian date field to 8 bytes with the first byte equal to '0' as described in section 7.15 GOODDATEX in the ADS Reference Guide. PRODUCT(S) AFFECTED: CA IDMS Release 18.5 CA IDMS Release 18.0 CA IDMS Release 17.0 IDMS 4766 Copyright (C) 2014 CA. All rights reserved. R00620-AGJ180-SP1 DESC(ADSC COMPILE CAN CHANGE RESULTS OF GOODDATEX(J)). FMID (CAGJI00) PRE ( RO61682 RO66380 ) SUP ( TR49824 TR66695 )

31 CA IDMS CA RS PTF RO RO66892 RO66892 M.C.S. ENTRIES = ++PTF (RO66892) COPY/INCLUDE IDMS MAP BINDS MAY BIND WRONG RECORD BIND MAP RECORD may bind to the wrong record when a map record is copied into a program multiple times under different synonym names. Also, COPY IDMS MAP-BINDS may not copy the map record into the program. The generated BIND MAP RECORD statement specifies the last synonym copied instead of the map record name. Compile errors may occur in the program or map data may not be returned to the record the program expects. Manually code the BIND MAP and BIND MAP record statements. PRODUCT(S) AFFECTED: CA IDMS Base Option Release 18.5 CA IDMS Base Option Release 18.0 CA IDMS Release 17.0 IDMS 4443 Copyright (C) 2014 CA. All rights reserved. R00626-AGJ180-SP1 DESC(COPY/INCLUDE IDMS MAP BINDS MAY BIND WRONG RECORD). FMID (CAGJI00) SUP ( TR66892 )

32 CA IDMS CA RS PTF RO RO66978 RO66978 M.C.S. ENTRIES = ++PTF (RO66978) EXIT 14 - OPTIONAL BIT OPT00334 This is an enhancement to add an optional bit which will allow users to skip all USER EXIT 14 processing unless issuing a READY request in UPDATE mode. This can result in fewer swaps to and from the ziip engine and the CP which can increase performance. To implement this function you must code the following optional bit in module RHDCOPTF: #DEFOPTF OPT00334 EXIT 14 will continue to be processed regardless of the mode of the request. EXIT 14 will continue to be processed regardless of the mode of the request. There is no circumvention for this problem. PRODUCT(S) AFFECTED: CA IDMS Release 18.0 CA IDMS Release 18.5 IDMS 4797 Copyright (C) 2014 CA. All rights reserved. R00627-AGJ180-SP1 DESC(EXIT 14 - OPTIONAL BIT OPT00334). FMID (CAGJI00) PRE ( RO26303 RO27242 RO28146 RO28678 RO29749 RO33429 RO34886 RO39073 RO41047 RO42136 RO43297 RO48240 RO48379 RO50065 RO52809 RO53099 RO59876 RO61236 RO62975 RO63129 ) SUP ( AR52809 AR60163 AR62975 EC57521 RI36848 RI55088 RI65900 RI66414 RO26757 RO27549 RO27942 RO28687 RO29022 RO29682 RO30678 RO31398 RO31708 RO33477 RO33580 RO33594 RO34076 RO34130 RO35210 RO35647 RO36551 RO36554 RO36907 RO38268 RO40245 RO42047 RO43773 RO45068 RO45272 RO48910 RO48934 RO50932 RO51853 RO55209 RO55222 RO58260 RO60163 RO60927 RO62323 RO63294 RO64422 RO65984 RO66415 RO66816 RO66819 RO66998 RO68044 TR26757 TR27549 TR27942 TR28687 TR29022 TR29682 TR30678 TR31398 TR31708 TR33477 TR33580 TR33594 TR34076 TR34130 TR34973 TR35210 TR35647 TR36551 TR36554 TR36722 TR36907 TR37471 TR38268 TR40245 TR42047 TR42524 TR43773 TR44140 TR45068 TR45272 TR46748 TR47314 TR48910 TR48934 TR50932 TR51407 TR51853 TR52584 TR55200 TR55209 TR55222 TR58260 TR59720 TR60163 TR60927 TR62323 TR63294 TR64396 TR64422 TR65984 TR66162 TR66415 TR66816 TR66819 TR66978 TR66998 TR68044 ) ++HOLD (RO66978) SYSTEM FMID(CAGJI00) REASON (ACTION ) DATE (14104) COMMENT ( CA IDMS Base Option Release 18.0 SEQUENCE Before Apply PURPOSE Enable the use of optional functionality USERS AFFECTED All IDMS users making use of Optional apars KNOWLEDGE SMP/E, Assemble #DEFOPTF macro, and/or ability to change REQUIRED SYSIDMS parameters and perform SYSGEN modification ACCESS CA IDMS CSI and libraries, CA IDMS Startup JCL, SYSGEN REQUIRED compiler

33 CA IDMS CA RS PTF RO66978 ************************** * STEPS TO PERFORM * ************************** To implement the functionality introduced by this PTF you will need to Code the following #DEFOPTF in your RHDCOPTF module and then re-assemble and link the RHDCOPTF module. Code the following #DEFOPTF in your RHDCOPTF module to activate this optional code: #DEFOPTF OPT00334 ).

34 CA IDMS CA RS PTF RO RO68830 RO68830 M.C.S. ENTRIES = ++PTF (RO68830) INDEX CORRUPTION AFTER RECOVERY. The IDMS system starts to get 1143 abends. Further investigation reveals that the index is corrupted. Transactions start to abend with 1143 abends. All of these abends appear to be related to the same index. The index had to be manually fixed, before the 1143 stopped. There is no circumvention. PRODUCTS AFFECTED: PRODUCT(S) AFFECTED: CA IDMS Release 17.0 PRODUCT(S) AFFECTED: CA IDMS Release 18.0 PRODUCT(S) AFFECTED: CA IDMS Release 18.5 IDMS 4837 Copyright (C) 2014 CA. All rights reserved. R00643-AGJ180-SP1 DESC(INDEX CORRUPTION AFTER RECOVERY.). FMID (CAGJI00) PRE ( RO26303 RO30578 RO31998 RO33429 ) SUP ( RO36113 RO41453 RO49042 RO51184 RO52829 RO54795 RO56745 TR36113 TR41453 TR49042 TR51184 TR52829 TR54795 TR56745 TR68830 )

35 CA IDMS CA RS PTF RO RO68986 RO68986 M.C.S. ENTRIES = ++PTF (RO68986) CMS OPTION COMPATIBILITY WITH IBM APAR OA41945 CA IDMS clients with the CA IDMS CMS Option installed on a z/os 1.12 or higher guest LPAR must install this CA IDMS PTF before installing IBM Apar OA CMS Batch or UCFCMS access to the z/os guest LPAR will not execute if IBM Apar OA41945 is applied prior to applying this CA IDMS PTF and a z/os restart is needed which will clear the bits in Control Register 0. VMCF communication to the z/os guest LPAR will be disabled and no CMS batch access or UCFCMS sessions can be established. There is no circumvention. PRODUCTS AFFECTED: CA IDMS Release 17.0 CA IDMS Release 18.0 CA IDMS Release 18.5 PRODUCT(S) AFFECTED: CA IDMS Base Option Release 18.0 CA IDMS Base Option Release 18.5 IDMS 4690 Copyright (C) 2014 CA. All rights reserved. R00646-AGJ180-SP1 DESC(CMS OPTION COMPATIBILITY WITH IBM APAR OA41945). FMID (CAGJI00) PRE ( RO28527 RO36582 RO45670 RO49224 ) SUP ( TR68986 ) ++HOLD (RO68986) SYSTEM FMID(CAGJI00) REASON (ACTION ) DATE (14093) COMMENT ( CA IDMS Base Option Release 18.0 SEQUENCE After Apply PURPOSE Regenerate and reload the IDMS SVC USERS AFFECTED All IDMS users KNOWLEDGE Assemble the IDMS SVC REQUIRED Run the "CAIRIM" utility to reload the IDMS SVC ACCESS Assemble the IDMS SVC REQUIRED Run the "CAIRIM" utililty ************************** * STEPS TO PERFORM * ************************** The CA IDMS SVC must be regenerated as described in the IDMS SYSTEM operations guide. Any CA IDMS CV in use on a z/os system must be refreshed using the "CAIRIM" utility as described in the CA IDMS Installation guide. ).

36 CA IDMS CA RS PTF RO RO69472 RO69472 M.C.S. ENTRIES = ++PTF (RO69472) UPGRADE TO IDMS R18.0 YIELDS ADS CURRENCY ISSUES Upgrading to (or through) IDMS Release 18.0 may result in application-level errors for applications using ADS Online. Problems occur for applications that extend Run Units to lower-level dialogs, which then in-turn issue 'DISPLAY' commands (thus terminating the Run Unit). When the low-level dialog resumes, a new Run Unit is created & passed back upwards. Under certain situations this new Run Unit may terminate prematurely, resulting in currency issues in the calling dialog. Various IDMS Database access failures may occur owing to the improper termination of extended run units. ADS/Online application-level failures. Back-off your upgrade to release PRODUCT(S) AFFECTED: CA IDMS Base Option Release 18.0 CA IDMS Base Option Release 18.5 IDMS 4846 Copyright (C) 2014 CA. All rights reserved. R00653-AGJ180-SP1 DESC(UPGRADE TO IDMS R18.0 YIELDS ADS CURRENCY ISSUES). FMID (CAGJI00) PRE ( RO45924 RO65412 ) SUP ( TR69104 TR69472 )

37 CA IDMS CA RS PTF RO RO69646 RO69646 M.C.S. ENTRIES = ++PTF (RO69646) S0C4 RUNNING DB/AUDIT WHEN APF AUTHORIZED A S0C4 abend may occur while running the DB/AUDIT product if STEPLIB is APF authorized. A S0C4 abend may occur within module GSSNKWP. Users will not be able to successfully use the DB/AUDIT product to audit or repair their CA IDMS databases. Insert a non-authorized library into the jobstep's STEPLIB concatentation. PRODUCTS AFFECTED: CA DB/AUDIT Release 18.0 CA DB/AUDIT Release 18.5 IDMS 4854 Copyright (C) 2014 CA. All rights reserved. R00655-AGJ180-SP1 DESC(S0C4 RUNNING DB/AUDIT WHEN APF AUTHORIZED). FMID (CAGJI00) SUP ( TR69612 TR69646 )

38 CA IDMS CA RS PTF RO RO69657 RO69657 M.C.S. ENTRIES = ++PTF (RO69657) PRINT LOG GETS A S0C4. The PRINT LOG or ARCHIVE LOG utility gets a S0C4 when trying to offload the DDLDCLOG. The DDLDCLOG fills, and a PRINT or ARCHIVE LOG is run to offload the LOG. The PRINT LOG fails with a S0C4. IDMS waits for the log to be archived. The DDLDCLOG fills, and a PRINT LOG is run to offload the LOG. The PRINT LOG abends with a S0C4. Any reruns of the PRINT LOG also fail. The system had to be cancelled, and the LOG formatted. The system was restarted. Warmstart was successful, and the access to the system was resumed. While the system was down, access to the database was denied. There is no circumvention. PRODUCTS AFFECTED: PRODUCT(S) AFFECTED: CA IDMS Release 17.0 PRODUCT(S) AFFECTED: CA IDMS Release 18.0 PRODUCT(S) AFFECTED: CA IDMS Release 18.5 IDMS 4761 Copyright (C) 2014 CA. All rights reserved. R00657-AGJ180-SP1 DESC(PRINT LOG GETS A S0C4.). FMID (CAGJI00) PRE ( RO69694 ) SUP ( RO37037 TR37037 TR69657 )

39 CA IDMS CA RS PTF RO RO69694 RO69694 M.C.S. ENTRIES = ++PTF (RO69694) FLOAT OF OPTIONAL APAR RO15092 TO 18 AND 18.5 Optional apar to generate RU statistics at shutdown If option bit 313 is set in RHDCOPTF, run unit statistics will be written to the log at system shutdown. The statement to generate the bit in the assembly of RHDCOPTF is: #DEFOPTF OPT00313 RU statistics are not normally generated at shutdown Presence or absence of RU stats on log None PRODUCT(S) AFFECTED: CA IDMS Base Option Release 18.0 CA IDMS Base Option Release 18.5 IDMS 4807 Copyright (C) 2014 CA. All rights reserved. R00658-AGJ180-SP1 DESC(FLOAT OF OPTIONAL APAR RO15092 TO 18 AND 18.5). FMID (CAGJI00) SUP ( RO35393 RO37037 TR34489 TR35393 TR37037 TR69694 )

40 CA IDMS CA RS PTF RO RO69697 RO69697 M.C.S. ENTRIES = ++PTF (RO69697) DISPLAY MESSAGE IF RESOURCE HOLDER TASK TERMINATED When a task stalls waiting on a db-key resource and the resource holder is a terminated task, no information is provided to this effect. There are no DC001009/DC messages displayed to support the stalled task messages DC and DC If the task holding the resource is terminated, no DC or DC messages are possible. A message to this effect should be provided. It is not possible to determine that the resource being waited on was held by a terminated task. None. PRODUCT(S) AFFECTED: CA IDMS Release 17.0 CA IDMS Release 18.0 CA IDMS release 18.5 IDMS 4636 Copyright (C) 2014 CA. All rights reserved. R00659-AGJ180-SP1 DESC(DISPLAY MESSAGE IF RESOURCE HOLDER TASK TERMINATED). FMID (CAGJI00) PRE ( RO50065 ) SUP ( TR57862 TR69697 )

41 CA IDMS CA RS PTF RO RO69776 RO69776 M.C.S. ENTRIES = ++PTF (RO69776) MOVE OF OVERLAPPING FIELDS MAY MOVE 'ALL SPACES' The result from a MOVE of a subordinate element to its GROUP element can possibly set the entire GROUP element to SPACES whenever a dialog is compiled without the ADSC 'Symbol table is enabled' option set. NOTE: This PTF is the float of 17.x PTF RO69319 (z/os) and corresponding VSE PTF RO Whenever the first subordinate element in a GROUP element is moved to its GROUP element, the result of the MOVE will be that the entire GROUP element will contain SPACES if the dialog was compiled without the ADSC 'Symbol table is enabled' option set. For example, 02 EMP-NAME USAGE IS DISPLAY. 03 EMP-FIRST-NAME PICTURE IS X(10) USAGE IS DISPLAY. 03 EMP-LAST-NAME PICTURE IS X(15) USAGE IS DISPLAY. MOVE EMP-FIRST-NAME-0415 TO EMP-NAME * No matter what value is in EMP-FIRST-NAME-0415, after the MOVE, EMP-FIRST-NAME-0415 and EMP-LAST-NAME-0415 will both contain SPACES. The impact is unpredictable. In sites that test using the ADSC 'Symbol table is enabled' then turn off this option when the dialog is migrated to production, the error will appear on only the production system. It could appear as bad data, incorrect application flow of control or as an abend. Turn on the ADSC 'Symbol table is enabled' option and recompile the dialog. PRODUCT(S) AFFECTED: CA IDMS Release 18.0 CA IDMS Release 18.5 IDMS 4858 Copyright (C) 2014 CA. All rights reserved. R00663-AGJ180-SP1 DESC(MOVE OF OVERLAPPING FIELDS MAY MOVE 'ALL SPACES'). FMID (CAGJI00) SUP ( TR69776 )