CA IDMS 18.5 CA RS 1411 Service List unable to cancel a looping task. ptf ro74210 db002504 job9 base install with sql and backups ptf ro74237 faulty dcmt display snap values ptf ro74569

CA IDMS 18.5 1

CA RS 1411 Service ListCA IDMS 18.5 1

CA RS 1411 Service List

Release Service Description Type

18.5 RO72392 S0C4 WITH USING EXTERNAL PERFMON PTF

RO72592 WRONG TRANSACTION-ID SUBSTITUTED IN THE DC202007 MESSAGE. PTF

RO73076 CATCH HELP TEXT EXCEEDING THE MAX AT COMPILE TIME PTF

RO73630 CV HANGS AFTER AN ABEND IN RHDCDEAD. PTF

RO73810 SQL QUERY MAY RESULT IN STORAGE VIOLATION ABENDS. PTF

RO73831 CA ENDEVOR/DB LINK EDIT CONCERN PTF

RO73946 'PRINT INDEX ... SUMMARY' MAY GET DB002424. PTF

RO73961 INCORRECT VALUES ON DCMT DISPLAY PTF

RO73975 S0C4 IDMSINFO & PMRM ACTIVE SYTEM SUMM PGM NAME NOT RHDCOMVS PTF

RO74051 ERR STATUS 1226 INSERTING A ROW INTO A TABLE WITH DEF. INDEX PTF

RO74131 UNABLE TO CANCEL A LOOPING TASK. PTF

RO74210 DB002504 JOB9 BASE INSTALL WITH SQL AND BACKUPS PTF

RO74237 FAULTY DCMT DISPLAY SNAP VALUES PTF

RO74569 S0C4 IN Z/OS BATCH JOBS WHEN RUNNING AUTHORIZED PTF

RO74586 S0C4 IN OLQSSCAN WHEN ACCESSING A SYSTEM-OWNED INDEX PTF

RO74684 DCMT D ALL STO TIMES SOS OVERFLOW PTF

RO74827 IDMSBCF S0C1 USING COMMANDS WITH LARGE NUMBERS OF CHARACTERS PTF

RO74854 USFAOPT MISSING FIELDS PTF

RO74943 CPU TIME IN PERFMON REPORTS DOESN'T HONOR MONEYED=E PTF

RO75092 SYSTRACE STILL IN SNAP DUMPS AFTER TURNED OFF PTF

The CA RS 1411 service count for this release is 20

CA IDMS 18.0 2

CA RS 1411 Service ListCA IDMS 18.0 2

CA RS 1411 Service List

Release Service Description Type

18.0 RO69874 SQL QUERY MAY RESULT IN STORAGE VIOLATION ABENDS. PTF






RO73716 NODENAME NOT SUBSTITUTED IN THE DC410004 MESSAGE. PTF











The CA RS 1411 service count for this release is 17

CA IDMS 3

CA RS 1411 Service List for CAGJI00CA IDMS 3

CA RS 1411 Service List for CAGJI00

FMID Service Description Type

CAGJI00 RO69874 SQL QUERY MAY RESULT IN STORAGE VIOLATION ABENDS. PTF






RO73716 NODENAME NOT SUBSTITUTED IN THE DC410004 MESSAGE. PTF











The CA RS 1411 service count for this FMID is 17

CA IDMS 4

CA RS 1411 Service List for CAGJI50CA IDMS 4

CA RS 1411 Service List for CAGJI50

FMID Service Description Type

CAGJI50 RO72392 S0C4 WITH USING EXTERNAL PERFMON PTF




RO73810 SQL QUERY MAY RESULT IN STORAGE VIOLATION ABENDS. PTF


RO73946 'PRINT INDEX ... SUMMARY' MAY GET DB002424. PTF


RO73975 S0C4 IDMSINFO & PMRM ACTIVE SYTEM SUMM PGM NAME NOT RHDCOMVS PTF



RO74210 DB002504 JOB9 BASE INSTALL WITH SQL AND BACKUPS PTF









The CA RS 1411 service count for this FMID is 20

CA IDMS 18.5 5

CA RS 1411 - PTF RO72392 DetailsCA IDMS 18.5 5

CA RS 1411 - PTF RO72392 Details

Release Service Details18.5 RO72392 RO72392 M.C.S. ENTRIES = ++PTF (RO72392)

S0C4 WITH USING EXTERNAL PERFMON

PROBLEM DESCRIPTION:

When monitoring an external CV, the Transaction Details screen will abend

if the remote CV being monitored has any suspended transactions or lterms in

pseudo-converse. The abend is in PMRTBATD

SYMPTOMS:

The perfmon session will display the following error:

02 Error in External Monitoring

TASK...... Transaction Detail

JOBNAME... P17I060

RETCD..... 00000010

RSNCD..... 00000034

DC130308 - PMRTBATD - PC abend recovery invoked

This error occurs everytime the Transaction Details screen is refreshed.

IMPACT: Low. The Transaction Details screen of the external Perfmon session

will abend.

CIRCUMVENTION: None

PRODUCT(S) AFFECTED: CA IDMS Release 18.5

Star Problem(s):

IDMS 4904

Copyright (C) 2014 CA. All rights reserved. R00280-AGJ185-SP1

DESC(S0C4 WITH USING EXTERNAL PERFMON).

++VER (Z038)

FMID (CAGJI50)

PRE ( RO55534 RO71145 )

SUP ( RO57262 TR57262 TR72392 )

CA IDMS 18.5 6




WRONG TRANSACTION-ID SUBSTITUTED IN THE DC202007 MESSAGE.


Warmstart may issue message DC202007 as part of its recovery

process. This message indicates the Transaction-ID for which

an ABRT checkpoint has been written. However, if the

Transaction-ID is greater than X'7FFFFFFF', an invalid value

will be substituted in the DC202007 message.

SYMPTOMS:

The following messages related to recovery may be returned

during warmstart:

IDMS DC202019 Vnnn Will roll out Transaction-ID 2612793765

IDMS DC203005 Vnnn Program-ID MFDBC404 Transaction-ID 2612793765

has been Rolled Out!

IDMS DC202007 Vnnn Transaction-ID 1682173531 ABRT checkpoint

written

In this case, the invalid Transaction-ID substituted in the

DC202007 message is the 2's-complement of the correct

Transaction-ID found in the DC202019 and DC203005 messages.

IMPACT:

Although the journals are correct, invalid information is

returned after warmstart and this may lead to the wrong conclusions.

CIRCUMVENTION:

There is no circumvention available.


CA IDMS Release 18.0


Star Problem(s):

IDMS 4906


DESC(WRONG TRANSACTION-ID SUBSTITUTED IN THE DC202007 MESSAGE.).

++VER (Z038)

FMID (CAGJI50)

PRE ( RO71145 )

SUP ( RO59386 RO68821 TR59386 TR68821 TR72592 )

CA IDMS 18.5 7




CATCH HELP TEXT EXCEEDING THE MAX AT COMPILE TIME


Mapping HELP supports HELP modules up to 65,535 characters. No

message is produced at compile time indicating a module exceeds

that amount.

SYMPTOMS:

IDD HELP modules much larger than 65,535 characters are allowed.

IMPACT:

MAP field HELP may not display for all fields with HELP defined.

CIRCUMVENTION:

Limit HELP modules to 65,535 characters (910 text lines) or less.


Release 18.0

Star Problem(s):

IDMS 4916


DESC(CATCH HELP TEXT EXCEEDING THE MAX AT COMPILE TIME).

++VER (Z038)

FMID (CAGJI50)

SUP ( TR73076 )

CA IDMS 18.5 8




CV HANGS AFTER AN ABEND IN RHDCDEAD.


CV appears to hang. RHDCDEAD, the Deadlock manager, gets a

S0C4. The system must be cancelled and restarted before access

to the system can be resumed.

SYMPTOMS:

An IDMS system is started. Shortly thereafter, it appears to hang.

The system is cancelled with a dump. Analysis of the dump reveals

that the Deadlock manager, RHDCDEAD, had abended.

IMPACT:

Until the system can be cancelled, and restarted, access to the

system and it's database is denied.

CIRCUMVENTION:

There is no circumvention.

PRODUCTS AFFECTED:



Star Problem(s):

IDMS 4921


DESC(CV HANGS AFTER AN ABEND IN RHDCDEAD.).

++VER (Z038)

FMID (CAGJI50)

PRE ( RO71145 )

SUP ( RO66986 TR66986 TR73630 )

CA IDMS 18.5 9




SQL QUERY MAY RESULT IN STORAGE VIOLATION ABENDS.


Executing an SQL query with OCF or BCF may result in storage

violation abends. This is most likely to happen when the SQL

query is executed against a network database where the referenced

record, that is table, contains more columns than the maximum

number allowed, that is 1024. For example, the referenced record

may contain a group element defined with the OCCURS nnn TIMES

clause. After applying the solution for this problem, the SQL

query will now return message: "DB005270: Maximum number of

columns exceeded".

SYMPTOMS:

When the SQL query is executed thru OCF, the following message

will indicate the storage violation:

PREVIOUS TASK ABENDED WITH ABEND CODE D002 AND MESSAGE CODE 016003

The following will be issued to the DC LOG file:

DC016003 Vnnn Tnnn TASK:OCF PROG:IDMSOCF FREED STORAGE AT ADDRESS

xxxxxxxx WAS FOUND TO HAVE BEEN VIOLATED

In other situations, you may also get:

DC016006 Vnnn Tnnn TASK:OCF PROG:IDMSOCF STORAGE-FRAME TO FREE AT

ADDRESS xxxxxxxx WAS FOUND TO HAVE BEEN VIOLATED

IMPACT:

The SQL query will each time abend with code D002 and depending on

the configuration followed by the DC016003 or DC016006 message.

CIRCUMVENTION:





Star Problem(s):

IDMS 4750


DESC(SQL QUERY MAY RESULT IN STORAGE VIOLATION ABENDS.).

++VER (Z038)

FMID (CAGJI50)

PRE ( RO71145 )

SUP ( TR69887 TR73810 )

CA IDMS 18.5 10




CA ENDEVOR/DB LINK EDIT CONCERN


Three CA Endevor/DB modules are linked AMODE24/RMODE24.

SYMPTOMS:

NDVRARCO, NDVRDCMP, and NDVRDLVR may abend with an 0C4.

IMPACT:

Archive/Compress, data comparison, and delivery are not

functioning properly.

CIRCUMVENTION:

Re-link these 3 modules using the following statements:

INCLUDE CAGJLOAD(NDVRDLVR)

ENTRY IDMSENTR

SETOPT PARM(AMODE=31,REUS(NONE),RMODE=ANY)

NAME NDVRDLVR(R)

INCLUDE CAGJLOAD(NDVRARCO)

ENTRY IDMSENTR


NAME NDVRARCO(R)

INCLUDE CAGJLOAD(NDVRDCMP)

ENTRY IDMSENTR


NAME NDVRDCMP(R)


Release 18.0

Star Problem(s):

IDMS 4928


DESC(CA ENDEVOR/DB LINK EDIT CONCERN).

++VER (Z038)

FMID (CAGJI50)

SUP ( TR73831 )

CA IDMS 18.5 11




'PRINT INDEX ... SUMMARY' MAY GET DB002424.


PRINT INDEX ... SUMMARY may return error message DB002424.

This will happen when the index being processed is a user-

owned index and if an owner record has been relocated, that is

split into an SR2/SR3 pair.

SYMPTOMS:

The following PRINT INDEX statement:

PRINT INDEX <index> SEGMENT <segment> USING <subs> SUMMARY;

may produce the following error message and truncated output:

*+ Status = -4 SQLSTATE = 28000 Messages follow:

*+ DB002424 Tnnn C-4M369: DBKey = 0251EF01 is not an SR8

Further output will be truncated after the index summary

header and before the index overview.

IMPACT:

There is no broken SR8 chain as may be indicated by the

DB002424 message, but a summary report of the target index

cannot be created.

CIRCUMVENTION:

Do not use the 'SUMMARY' report option, but for example use the

'FULL' option.




Star Problem(s):

IDMS 4848


DESC('PRINT INDEX ... SUMMARY' MAY GET DB002424.).

++VER (Z038)

FMID (CAGJI50)

PRE ( RO71145 )

SUP ( RO62729 RO67602 TR62729 TR67602 TR69147 TR73946 )

CA IDMS 18.5 12




INCORRECT VALUES ON DCMT DISPLAY


Problem 1: DCMT D ACT STO 0 displays incorrect values for Times SOS when

Times SOS is greater than a regular full word.

Problem 2: DCMT D ACT STO 0 displays incorrect percentage values for GETSTG

requests when scan #1 and scan #2 contain values greater than a full word

value of '7FFFFFFF'.

SYMPTOMS:

DCMT D ACT STO 0 will display incorrectly for Times SOS and % of GETSTG

requests if values are greater than a full word.

IMPACT:

The values displayed will sometimes be incorrect.

CIRCUMVENTION:

None.

PRODUCT(S) AFFECTED:




Star Problem(s):

IDMS 4930


DESC(INCORRECT VALUES ON DCMT DISPLAY).

++VER (Z038)

FMID (CAGJI50)

PRE ( RO71145 )

SUP ( RO66161 RO68988 TR66161 TR68988 TR73961 )

CA IDMS 18.5 13




S0C4 IDMSINFO & PMRM ACTIVE SYTEM SUMM PGM NAME NOT RHDCOMVS


There are two different problems with CA IDMS External Performance

Monitoring contained in IDMS/4861:

Problem 1: A recursive S0C4 abend can occur in the IDMSINFO

address space in load module IDMSMCVS+3A8.

Problem 2: When displaying the Active System Summary using the

external Performance Monitor Task, the Program Name

field may not display the correct startup module name.

SYMPTOMS:

Problem 1: During CV shutdown of an externally monitored CV,

the IDMSINFO address space may recursively abend

with a S0C4. The abend PSW is located in

load module IDMSMCVS+3A8. The recursive abends

continue until the shutdown CVs are restarted.

Problem 2: If the IDMS CV is attached as part of CV startup or the

WTOREXIT loads a program during CV startup, then the

Program Name field of the Active System Summary will

either contains blanks or the name of WTOREXIT's

loaded program not the name of the startup load module.

IMPACT:

Problem 1: The recursive S0C4 abends in the IDMSINFO address space

can cause the MVS spool to fill and the IDMSINFO

address space becomes unusable until the shutdown CVs

are restarted.

Problem 2: Minor impact. The external Performance Monitor task

executes normally but the Program Name field in the

Active System Summary can be misleading.

CIRCUMVENTION:

Problem 1: There is no circumvention.

Problem 2: There is no circumvention.

PRODUCT(S) AFFECTED: CA IDMS RELEASE 18.5

Star Problem(s):

IDMS 4861


DESC(S0C4 IDMSINFO & PMRM ACTIVE SYTEM SUMM PGM NAME NOT RHDCOMVS).

++VER (Z038)

FMID (CAGJI50)

PRE ( RO65335 RO71145 )

SUP ( TR73975 )

CA IDMS 18.5 14




ERR STATUS 1226 INSERTING A ROW INTO A TABLE WITH DEF. INDEX


If an SQL table has been defined with a default index and an

ALTER TABLE statement received error message "DB002116 Total

sort column length too long", inserting a row into that table

in the same session may return error status 1226. This will only

happen when there is no COMMIT statement in the session input

and when the schema is dropped and recreated between the ALTER

TABLE and INSERT statements.

SYMPTOMS:

The following example illustrates the session input statements

and the messages that are returned:

----------------------------------

CREATE SCHEMA XTEMPSCH DEFAULT AREA SQLDEMO.EMPLAREA ;

Status = 0 SQLSTATE = 00000

CREATE TABLE XTEMPSCH.DEPARTMENT

(ID INT,

NAME VARCHAR(20)) ;


CREATE INDEX INDXDEPT ON XTEMPSCH.DEPARTMENT (NAME) ;


INSERT INTO XTEMPSCH.DEPARTMENT VALUES (50, 'HR') ;


1 row processed

ALTER TABLE XTEMPSCH.DEPARTMENT

ALTER NAME SET DATA TYPE CHAR(2000) ;

Status = -4 SQLSTATE = 50002 Messages follow:

DB002116 T64 C-4M351: Total sort column length too long

DROP SCHEMA XTEMPSCH CASCADE ;





(ID INT,

NAME VARCHAR(1996)) ;






DB001061 T0 C-4M387: Error on a DTS SEND/RECEIVE: -23

Communications with server has been disrupted


Command Facility ended with a critical error

The DC LOG will contain the following:

-------------------------------------

IDMS DB001031 V400 T64 C-7M321: DB error 1226; Tbl:DEPARTMENT,

Area:EMPLAREA, ErrSet:ROWID01065, ErrTbl:DEPARTMENT,

ErrArea:EMPLAREA

IDMS DC027007 V400 T64 TASK:RHDCNP3S PROG:IDMSDDAM ABENDED WITH CODE D002

IMPACT:

With the above session input statements, it will not be possible

to insert a row into the newly created table. BCF or OCF will each

time abend with a critical error.

CIRCUMVENTION:

There are 3 ways to circumvent the problem:

1. Define the table without a DEFAULT INDEX, that is:

CREATE TABLE ... NO DEFAULT INDEX ;

2. Correct the ALTER TABLE statement avoiding the DB002116

error message.

3. Put a COMMIT statement between the DROP and CREATE SCHEMA

statements.



CA IDMS 18.5 15


Release Service DetailsStar Problem(s):

IDMS 4827


DESC(ERR STATUS 1226 INSERTING A ROW INTO A TABLE WITH DEF. INDEX).

++VER (Z038)

FMID (CAGJI50)

SUP ( TR74051 )

CA IDMS 18.5 16




UNABLE TO CANCEL A LOOPING TASK.


When a user task is in a very tight loop between 2 system

service calls, for example #GETSTG and #FREESTG of the same

storage and CALL limits have not been specified or limit

checking has not been enabled, it might not be possible to

terminate that looping task. Trying to kill the looping task

will set the appropriate abend code and 'external abend request'

flag, but that flag is not checked.

SYMPTOMS:

The looping task cannot be terminated and is using a lot of

CPU.

IMPACT:

The looping task is consuming a lot of CPU and the only way to

resume normal service, is to cancel and restart the CV.

CIRCUMVENTION:

The only way to get out of this situation is to cancel and

restart the CV.



Star Problem(s):

IDMS 4911


DESC(UNABLE TO CANCEL A LOOPING TASK.).

++VER (Z038)

FMID (CAGJI50)

PRE ( RO57307 RO58656 RO67793 RO71145 )

SUP ( RO57360 TR57268 TR57328 TR57360 TR74131 )

CA IDMS 18.5 17




DB002504 JOB9 BASE INSTALL WITH SQL AND BACKUPS


Performing a non-CSM base install with SQL selected and backups for System 99

causes error DB002504 in Job 9 during the backup. The SYSSQL segment is

being backed up before it has been formatted.

SYMPTOMS:

The job will end with a return code 8 and the below messages:

UT015011 Unexpected EOF at page=20,001. High page=24,000.

DB002504 C-4M354: Backup/Restore incomplete

IMPACT:

The backup process during installation will fail.

CIRCUMVENTION:

After Job 9 ends with Return Code 8, submit Job 10. This will format the

SYSSQL segment. Then submit the jcl from Job 9 to perform the backups.


Star Problem(s):

IDMS 4939


DESC(DB002504 JOB9 BASE INSTALL WITH SQL AND BACKUPS).

++VER (Z038)

FMID (CAGJI50)

PRE ( RO58319 RO68724 )

SUP ( TR74210 )

CA IDMS 18.5 18




FAULTY DCMT DISPLAY SNAP VALUES


Using a DCMT VARY SNAP TASK TRACE TASK command will display TASK SNAP TRACE

TASK IS ON (ENABLED) in DCMT D SNAP. It should say TASK SNAP TRACE STATUS IS

TASK (ENABLED).

SYMPTOMS:

DCMT D SNAP displays incorrect message.

IMPACT:

Wrong message displayed.

CIRCUMVENTION:

None.




Star Problem(s):

IDMS 4938


DESC(FAULTY DCMT DISPLAY SNAP VALUES).

++VER (Z038)

FMID (CAGJI50)

SUP ( TR74237 )

CA IDMS 18.5 19




S0C4 IN Z/OS BATCH JOBS WHEN RUNNING AUTHORIZED


S0C4 abends may occur when running batch jobs in a z/OS environment

when all libraries in the jobstep's loadlib concatenation are

APF authorized or when running on a z/OS release of 1.9 or higher

and the lpar is ipl'ed using the REFRPROT option. These abends are

typically identified as being in module RHDCOMVS but may occur in

other modules.

SYMPTOMS:

A S0C4 abend during the jobstep's execution.

IMPACT:

The jobstep cannot be successfully completed.

CIRCUMVENTION:

If all libraries in the jobstep's loadlib concatenation are

APF authorized insert a non-APF authorized library into the

concatenation. If the lpar is ipl'ed with the REFRPROT option

re-ipl the lpar without this option.

PRODUCTS AFFECTED: CA IDMS Release 18.0


Star Problem(s):

IDMS 4946


DESC(S0C4 IN Z/OS BATCH JOBS WHEN RUNNING AUTHORIZED).

++VER (Z038)

FMID (CAGJI50)

PRE ( RO59398 RO68886 RO69066 RO71145 )

SUP ( TR70512 TR74569 )

CA IDMS 18.5 20




S0C4 IN OLQSSCAN WHEN ACCESSING A SYSTEM-OWNED INDEX


OLQ may receive an S0C4 abend in OLQSSCAN when comparing a field

that is a key field of a system-owned index to a particular value.

SYMPTOMS:

DC027001 Program Check in OLQSSCAN or S0C4 in OLQSSCAN will occur.

IMPACT:

An abend occurs and no report is generated.

CIRCUMVENTION:

Eliminate the comparison of the field to a particular value.


CA IDMS Base Option Release 18.0



Star Problem(s):

IDMS 4881


DESC(S0C4 IN OLQSSCAN WHEN ACCESSING A SYSTEM-OWNED INDEX).

++VER (Z038)

FMID (CAGJI50)

PRE ( RO69186 RO71145 )

SUP ( TR72211 TR72864 TR74586 )

CA IDMS 18.5 21




DCMT D ALL STO TIMES SOS OVERFLOW


In DCMT D ALL STO, TIMES SOS is overflowing into the PFIX and

CONTAINS TYPES columns, causing it to display improperly.

SYMPTOMS:

DCMT D ALL STO will display improperly for TIMES SOS.

IMPACT:

The values displayed will be incorrect.

CIRCUMVENTION:

None.





Star Problem(s):

IDMS 4942


DESC(DCMT D ALL STO TIMES SOS OVERFLOW).

++VER (Z038)

FMID (CAGJI50)

PRE ( RO71145 )

SUP ( RO66161 RO68988 RO73961 TR66161 TR68988 TR73961

TR74355 TR74684 )

CA IDMS 18.5 22




IDMSBCF S0C1 USING COMMANDS WITH LARGE NUMBERS OF CHARACTERS


When attempting to run an IDMSBCF job with commands that have lengths of

3000-4000 characters or higher, the job will ABEND with a S0C1 after

processing the first line.

SYMPTOMS:

The IDMSBCF job will ABEND with a S0C1 or a S0C4 depending on your system

configuration.

IMPACT:

The IDMSBCF will not be completed.

CIRCUMVENTION:

There is no circumvention to this problem.

PRODUCTS AFFECTED:




Star Problem(s):

IDMS 4650


DESC(IDMSBCF S0C1 USING COMMANDS WITH LARGE NUMBERS OF CHARACTERS).

++VER (Z038)

FMID (CAGJI50)

PRE ( RO71145 )

SUP ( TR74827 )

CA IDMS 18.5 23




USFAOPT MISSING FIELDS


In USFAOPT, the AUTHORIZATION MODE and AUTHORIZATION

SVC under SMF are displayed with invalid or no values. These

fields were removed as of Release 18.0 because the IDMS

SVC is now used and these fields are removed from the display.

SYMPTOMS:

USFAOPT incorrectly displays AUTH MODE and AUTH SVC fields.

IMPACT:

Invalid fields are displayed.

CIRCUMVENTION:

None.




Star Problem(s):

IDMS 4953


DESC(USFAOPT MISSING FIELDS).

++VER (Z038)

FMID (CAGJI50)

PRE ( RO71145 )

SUP ( RO65675 RO65857 TR65675 TR65857 TR74854 )

CA IDMS 18.5 24




CPU TIME IN PERFMON REPORTS DOESN'T HONOR MONEYED=E


Various PERFMON batch Application Monitor reports do not honor

the MONEYED=E profile parameter when displaying CPU task times.

These reports always display the field using a '.' instead of

an ',' for the time decimal point.

Also when using the MONEYED=E profile parameter the file statistics

produced by report PMARPT00 will be displayed with Z's embedded

in the numeric values.

SYMPTOMS:

CPU task time fields will always be displayed with a '.' as the

decimal point instead of a ',' per European conventions. A CPU

time of 1.3 seconds should be displayed as 1,3 when MONEYED=E

is specified on the Culprit PROFILE statement.

The file statistics generated by report PMARPT00 will also have

Z's embedded in the numeric value. For example, a value of

1,122 records read will produce the following line.

112,ZZZ,ZZ2 STATISTICS RECORDS READ

IMPACT:

The format of the CPU time fields on various reports do not

conform to local conventions and users will have to interpret

the corrupted file statistics by ignoring the Z's.

CIRCUMVENTION:

None.



Star Problem(s):

IDMS 4929


DESC(CPU TIME IN PERFMON REPORTS DOESN'T HONOR MONEYED=E).

++VER (Z038)

FMID (CAGJI50)

SUP ( TR73899 TR74943 )

++HOLD (RO74943) SYSTEM FMID(CAGJI50)

REASON (ACTION ) DATE (14301)

COMMENT (

+----------------------------------------------------------------------+

| CA IDMS Base Option Release 18.5 |

+----------+-----------------------------------------------------------+

|SEQUENCE | After Apply |

+----------+-----------------------------------------------------------+

|PURPOSE | Update reports |

+----------+-----------------------------------------------------------+

|USERS | All IDMS users |

|AFFECTED | |

+----------+-----------------------------------------------------------+

|KNOWLEDGE | Update definitions in the dictionary |

|REQUIRED | |

+----------+-----------------------------------------------------------+

|ACCESS | Ability to run IDMSDDDL in batch or use IDD online |

|REQUIRED | |

+----------+-----------------------------------------------------------+

**************************

* STEPS TO PERFORM *

**************************

After installing this PTF, please use the IDMSDDDL utility

to update the dictionary which contains reports, normally

the SYSDIRL dictionary, with the input in source members:

PMARPT00

PMARPT01

PMARPT02

CA IDMS 18.5 25


Release Service DetailsPMARPT03

PMARPT04

PMARPT05

PMARPT08

PMARPT12

PMARPT14

PMARPT16

PMARPT31

The source will be in the SMP/E distribution source

library if an ACCEPT has been executed for the PTF

and in the SMPMTS library if an APPLY has been

executed but no ACCEPT has been executed.

).

CA IDMS 18.5 26




SYSTRACE STILL IN SNAP DUMPS AFTER TURNED OFF


If a CV's system trace is dynamically disabled by executing a

DCMT VARY SYSTRACE OFF command and a snap dump is generated

the dump will still contain the system trace. In addition the

system trace information in the snap dump will not be current.

SYMPTOMS:

The system trace table is displayed within a snap dump despite

the fact that the collection of trace entries has been turned

off.

IMPACT:

Users may use obsolete information within the included system

trace table when attempting to diagnose the cause of the abend

generating the snap dump.

CIRCUMVENTION:

Ignore the system trace entries within the dump if the SYSTRACE

facility has been turned off.



Star Problem(s):

IDMS 4960


DESC(SYSTRACE STILL IN SNAP DUMPS AFTER TURNED OFF).

++VER (Z038)

FMID (CAGJI50)

PRE ( RO71145 RO71202 )

SUP ( RO56701 RO68187 TR56701 TR68187 TR75092 )

CA IDMS 18.0 27




SQL QUERY MAY RESULT IN STORAGE VIOLATION ABENDS.


Executing an SQL query with OCF or BCF may result in storage

violation abends. This is most likely to happen when the SQL

query is executed against a network database where the referenced

record, that is table, contains more columns than the maximum

number allowed, that is 1024. For example, the referenced record

may contain a group element defined with the OCCURS nnn TIMES

clause. After applying the solution for this problem, the SQL

query will now return message: "DB005270: Maximum number of

columns exceeded".

SYMPTOMS:

When the SQL query is executed thru OCF, the following message

will indicate the storage violation:

PREVIOUS TASK ABENDED WITH ABEND CODE D002 AND MESSAGE CODE 016003

The following will be issued to the DC LOG file:

DC016003 Vnnn Tnnn TASK:OCF PROG:IDMSOCF FREED STORAGE AT ADDRESS

xxxxxxxx WAS FOUND TO HAVE BEEN VIOLATED

In other situations, you may also get:

DC016006 Vnnn Tnnn TASK:OCF PROG:IDMSOCF STORAGE-FRAME TO FREE AT

ADDRESS xxxxxxxx WAS FOUND TO HAVE BEEN VIOLATED

IMPACT:

The SQL query will each time abend with code D002 and depending on

the configuration followed by the DC016003 or DC016006 message.

CIRCUMVENTION:





Star Problem(s):

IDMS 4750


DESC(SQL QUERY MAY RESULT IN STORAGE VIOLATION ABENDS.).

++VER (Z038)

FMID (CAGJI00)

SUP ( TR69874 )

CA IDMS 18.0 28




WRONG TRANSACTION-ID SUBSTITUTED IN THE DC202007 MESSAGE.


Warmstart may issue message DC202007 as part of its recovery

process. This message indicates the Transaction-ID for which

an ABRT checkpoint has been written. However, if the

Transaction-ID is greater than X'7FFFFFFF', an invalid value

will be substituted in the DC202007 message.

SYMPTOMS:

The following messages related to recovery may be returned

during warmstart:

IDMS DC202019 Vnnn Will roll out Transaction-ID 2612793765

IDMS DC203005 Vnnn Program-ID MFDBC404 Transaction-ID 2612793765

has been Rolled Out!

IDMS DC202007 Vnnn Transaction-ID 1682173531 ABRT checkpoint

written

In this case, the invalid Transaction-ID substituted in the

DC202007 message is the 2's-complement of the correct

Transaction-ID found in the DC202019 and DC203005 messages.

IMPACT:

Although the journals are correct, invalid information is

returned after warmstart and this may lead to the wrong conclusions.

CIRCUMVENTION:





Star Problem(s):

IDMS 4906


DESC(WRONG TRANSACTION-ID SUBSTITUTED IN THE DC202007 MESSAGE.).

++VER (Z038)

FMID (CAGJI00)

SUP ( RO58552 TR58294 TR58552 TR72591 )

CA IDMS 18.0 29




S0C4 IN OLQSSCAN WHEN ACCESSING A SYSTEM-OWNED INDEX


OLQ may receive an S0C4 abend in OLQSSCAN when comparing a field

that is a key field of a system-owned index to a particular value.

SYMPTOMS:

DC027001 Program Check in OLQSSCAN or S0C4 in OLQSSCAN will occur.

IMPACT:

An abend occurs and no report is generated.

CIRCUMVENTION:

Eliminate the comparison of the field to a particular value.





Star Problem(s):

IDMS 4881


DESC(S0C4 IN OLQSSCAN WHEN ACCESSING A SYSTEM-OWNED INDEX).

++VER (Z038)

FMID (CAGJI00)

PRE ( RO69177 )

SUP ( TR71106 TR72863 )

CA IDMS 18.0 30




CATCH HELP TEXT EXCEEDING THE MAX AT COMPILE TIME


Mapping HELP supports HELP modules up to 65,535 characters. No

message is produced at compile time indicating a module exceeds

that amount.

SYMPTOMS:

IDD HELP modules much larger than 65,535 characters are allowed.

IMPACT:

MAP field HELP may not display for all fields with HELP defined.

CIRCUMVENTION:

Limit HELP modules to 65,535 characters (910 text lines) or less.


Release 18.0

Star Problem(s):

IDMS 4916


DESC(CATCH HELP TEXT EXCEEDING THE MAX AT COMPILE TIME).

++VER (Z038)

FMID (CAGJI00)

SUP ( TR72917 )

CA IDMS 18.0 31




UNABLE TO CANCEL A LOOPING TASK.


When a user task is in a very tight loop between 2 system

service calls, for example #GETSTG and #FREESTG of the same

storage and CALL limits have not been specified or limit

checking has not been enabled, it might not be possible to

terminate that looping task. Trying to kill the looping task

will set the appropriate abend code and 'external abend request'

flag, but that flag is not checked.

SYMPTOMS:

The looping task cannot be terminated and is using a lot of

CPU.

IMPACT:

The looping task is consuming a lot of CPU and the only way to

resume normal service, is to cancel and restart the CV.

CIRCUMVENTION:

The only way to get out of this situation is to cancel and

restart the CV.



Star Problem(s):

IDMS 4911


DESC(UNABLE TO CANCEL A LOOPING TASK.).

++VER (Z038)

FMID (CAGJI00)

PRE ( RO27242 RO35437 RO49538 RO63743 )

SUP ( RO42589 RO57264 TR42589 TR57264 TR73068 )

CA IDMS 18.0 32




CV HANGS AFTER AN ABEND IN RHDCDEAD.


CV appears to hang. RHDCDEAD, the Deadlock manager, gets a

S0C4. The system must be cancelled and restarted before access

to the system can be resumed.

SYMPTOMS:

An IDMS system is started. Shortly thereafter, it appears to hang.

The system is cancelled with a dump. Analysis of the dump reveals

that the Deadlock manager, RHDCDEAD, had abended.

IMPACT:

Until the system can be cancelled, and restarted, access to the

system and it's database is denied.

CIRCUMVENTION:

There is no circumvention.

PRODUCTS AFFECTED:



Star Problem(s):

IDMS 4921


DESC(CV HANGS AFTER AN ABEND IN RHDCDEAD.).

++VER (Z038)

FMID (CAGJI00)

SUP ( RO67051 TR67051 TR73604 )

CA IDMS 18.0 33




NODENAME NOT SUBSTITUTED IN THE DC410004 MESSAGE.


When the SVC communication access method is used within a DC/UCF

communications network and the Data Transfer Services commmunication

(DTS) layer is trying to connect to the target CV, message

DC410004 may be issued indicating that the BIND request has

failed. The message contains the error-status returned by the BIND

request, but does not contain the NODE name of the target CV.

SYMPTOMS:

When the BIND request fails, the following messages will be issued:

DC410004 Vnn Tnn DNS BIND REQUEST UNIT FAILURE, STATUS IS: error-status

Vnn Tnn DTS Error: TD0C - F/e physical connect error rc = -41

Vnn Tnn LTE=LD000001 USER=userid

Vnn Tnn DTS Error: TD0D - Reason code = -41

Vnn Tnn LTE=LD000001 USER=userid

IMPACT:

In a high-level DC/UCF communications network where many nodes are

connecting to each other, it is difficult to determine the failing

DC system without having the NODE name in the failure message.

CIRCUMVENTION:




Star Problem(s):

IDMS 4896


DESC(NODENAME NOT SUBSTITUTED IN THE DC410004 MESSAGE.).

++VER (Z038)

FMID (CAGJI00)

PRE ( RO49753 )

SUP ( AR40431 RI44071 RO40431 RO44057 RO56100 TR40431

TR44057 TR56100 TR73716 )



COMMENT (

+----------------------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+

|PURPOSE | Update Messages |

+----------+-----------------------------------------------------------+

|USERS | |

|AFFECTED | All IDMS users |

+----------+-----------------------------------------------------------+

|KNOWLEDGE | |

|REQUIRED | Update definitions in the Dictionary |

+----------+-----------------------------------------------------------+

|ACCESS | |

|REQUIRED | Ability to run IDMSDDDL in batch or use IDD online |

+----------+-----------------------------------------------------------+

**************************


**************************


to update your SYSTEM dictionary's message area

with the input in source member DC400. Please note using this

member will result in the update of all messages contained within

DC400. You may optionally decide to only update the specific

message associated with this correction. To do this simply

include message DC410004 as input to the IDMSDDDL utility.

CA IDMS 18.0 34


Release Service DetailsThe source will be in the SMP/E CAGJSRC library.

).

CA IDMS 18.0 35




INCORRECT VALUES ON DCMT DISPLAY


Problem 1: DCMT D ACT STO 0 displays incorrect values for Times SOS when

Times SOS is greater than a regular full word.

Problem 2: DCMT D ACT STO 0 displays incorrect percentage values for GETSTG

requests when scan #1 and scan #2 contain values greater than a full word

value of '7FFFFFFF'.

SYMPTOMS:

DCMT D ACT STO 0 will display incorrectly for Times SOS and % of GETSTG

requests if values are greater than a full word.

IMPACT:

The values displayed will sometimes be incorrect.

CIRCUMVENTION:

None.





Star Problem(s):

IDMS 4930


DESC(INCORRECT VALUES ON DCMT DISPLAY).

++VER (Z038)

FMID (CAGJI00)

SUP ( RO47483 RO53469 RO66158 RO68987 TR47483 TR53469

TR53560 TR66158 TR68987 TR73963 )

CA IDMS 18.0 36




CA ENDEVOR/DB LINK EDIT CONCERN


Three CA Endevor/DB modules are linked AMODE24/RMODE24.

SYMPTOMS:

NDVRARCO, NDVRDCMP, and NDVRDLVR may abend with an 0C4.

IMPACT:

Archive/Compress, data comparison, and delivery are not

functioning properly.

CIRCUMVENTION:

Re-link these 3 modules using the following statements:

INCLUDE CAGJLOAD(NDVRDLVR)

ENTRY IDMSENTR


NAME NDVRDLVR(R)

INCLUDE CAGJLOAD(NDVRARCO)

ENTRY IDMSENTR


NAME NDVRARCO(R)

INCLUDE CAGJLOAD(NDVRDCMP)

ENTRY IDMSENTR


NAME NDVRDCMP(R)


Release 18.0

Star Problem(s):

IDMS 4928


DESC(CA ENDEVOR/DB LINK EDIT CONCERN).

++VER (Z038)

FMID (CAGJI00)

SUP ( TR74011 )

CA IDMS 18.0 37




ERR STATUS 1226 INSERTING A ROW INTO A TABLE WITH DEF. INDEX


If an SQL table has been defined with a default index and an

ALTER TABLE statement received error message "DB002116 Total

sort column length too long", inserting a row into that table

in the same session may return error status 1226. This will only

happen when there is no COMMIT statement in the session input

and when the schema is dropped and recreated between the ALTER

TABLE and INSERT statements.

SYMPTOMS:

The following example illustrates the session input statements

and the messages that are returned:

----------------------------------




(ID INT,

NAME VARCHAR(20)) ;






1 row processed

ALTER TABLE XTEMPSCH.DEPARTMENT

ALTER NAME SET DATA TYPE CHAR(2000) ;


DB002116 T64 C-4M351: Total sort column length too long

DROP SCHEMA XTEMPSCH CASCADE ;





(ID INT,

NAME VARCHAR(1996)) ;






DB001061 T0 C-4M387: Error on a DTS SEND/RECEIVE: -23

Communications with server has been disrupted


Command Facility ended with a critical error

The DC LOG will contain the following:

-------------------------------------

IDMS DB001031 V400 T64 C-7M321: DB error 1226; Tbl:DEPARTMENT,

Area:EMPLAREA, ErrSet:ROWID01065, ErrTbl:DEPARTMENT,

ErrArea:EMPLAREA

IDMS DC027007 V400 T64 TASK:RHDCNP3S PROG:IDMSDDAM ABENDED WITH CODE D002

IMPACT:

With the above session input statements, it will not be possible

to insert a row into the newly created table. BCF or OCF will each

time abend with a critical error.

CIRCUMVENTION:

There are 3 ways to circumvent the problem:

1. Define the table without a DEFAULT INDEX, that is:

CREATE TABLE ... NO DEFAULT INDEX ;

2. Correct the ALTER TABLE statement avoiding the DB002116

error message.

3. Put a COMMIT statement between the DROP and CREATE SCHEMA

statements.



CA IDMS 18.0 38


Release Service DetailsStar Problem(s):

IDMS 4827


DESC(ERR STATUS 1226 INSERTING A ROW INTO A TABLE WITH DEF. INDEX).

++VER (Z038)

FMID (CAGJI00)

SUP ( RO42864 TR42864 TR74043 )

CA IDMS 18.0 39




FAULTY DCMT DISPLAY SNAP VALUES


Using a DCMT VARY SNAP TASK TRACE TASK command will display TASK SNAP TRACE

TASK IS ON (ENABLED) in DCMT D SNAP. It should say TASK SNAP TRACE STATUS IS

TASK (ENABLED).

SYMPTOMS:

DCMT D SNAP displays incorrect message.

IMPACT:

Wrong message displayed.

CIRCUMVENTION:

None.




Star Problem(s):

IDMS 4938


DESC(FAULTY DCMT DISPLAY SNAP VALUES).

++VER (Z038)

FMID (CAGJI00)

SUP ( TR74236 )

CA IDMS 18.0 40




S0C4 IN Z/OS BATCH JOBS WHEN RUNNING AUTHORIZED


S0C4 abends may occur when running batch jobs in a z/OS environment

when all libraries in the jobstep's loadlib concatenation are

APF authorized or when running on a z/OS release of 1.9 or higher

and the lpar is ipl'ed using the REFRPROT option. These abends are

typically identified as being in module RHDCOMVS but may occur in

other modules.

SYMPTOMS:

A S0C4 abend during the jobstep's execution.

IMPACT:

The jobstep cannot be successfully completed.

CIRCUMVENTION:

If all libraries in the jobstep's loadlib concatenation are

APF authorized insert a non-APF authorized library into the

concatenation. If the lpar is ipl'ed with the REFRPROT option

re-ipl the lpar without this option.



Star Problem(s):

IDMS 4946


DESC(S0C4 IN Z/OS BATCH JOBS WHEN RUNNING AUTHORIZED).

++VER (Z038)

FMID (CAGJI00)

PRE ( RO38376 RO45924 RO65412 RO68872 )

SUP ( RO29606 TR29465 TR29606 TR70523 TR74571 )

CA IDMS 18.0 41




DCMT D ALL STO TIMES SOS OVERFLOW


In DCMT D ALL STO, TIMES SOS is overflowing into the PFIX and

CONTAINS TYPES columns, causing it to display improperly.

SYMPTOMS:

DCMT D ALL STO will display improperly for TIMES SOS.

IMPACT:

The values displayed will be incorrect.

CIRCUMVENTION:

None.





Star Problem(s):

IDMS 4942


DESC(DCMT D ALL STO TIMES SOS OVERFLOW).

++VER (Z038)

FMID (CAGJI00)

SUP ( RO47483 RO53469 RO66158 RO68987 RO73963 TR47483

TR53469 TR53560 TR66158 TR68987 TR73963 TR74356

TR74683 )

CA IDMS 18.0 42




IDMSBCF S0C1 USING COMMANDS WITH LARGE NUMBERS OF CHARACTERS


When attempting to run an IDMSBCF job with commands that have lengths of

3000-4000 characters or higher, the job will ABEND with a S0C1 after

processing the first line.

SYMPTOMS:

The IDMSBCF job will ABEND with a S0C1 or a S0C4 depending on your system

configuration.

IMPACT:

The IDMSBCF will not be completed.

CIRCUMVENTION:

There is no circumvention to this problem.

PRODUCTS AFFECTED:




Star Problem(s):

IDMS 4650


DESC(IDMSBCF S0C1 USING COMMANDS WITH LARGE NUMBERS OF CHARACTERS).

++VER (Z038)

FMID (CAGJI00)

PRE ( RO26303 )

SUP ( RO26764 RO30791 RO37174 RO48631 TR26764 TR30791

TR37174 TR44105 TR48631 TR74797 )

CA IDMS 18.0 43




USFAOPT MISSING FIELDS


In USFAOPT, the AUTHORIZATION MODE and AUTHORIZATION

SVC under SMF are displayed with invalid or no values. These

fields were removed as of Release 18.0 because the IDMS

SVC is now used and these fields are removed from the display.

SYMPTOMS:

USFAOPT incorrectly displays AUTH MODE and AUTH SVC fields.

IMPACT:

Invalid fields are displayed.

CIRCUMVENTION:

None.




Star Problem(s):

IDMS 4953


DESC(USFAOPT MISSING FIELDS).

++VER (Z038)

FMID (CAGJI00)

SUP ( RO65678 RO65856 TR65678 TR65856 TR74851 TR74941 )

CA IDMS 18.0 44




CPU TIME IN PERFMON REPORTS DOESN'T HONOR MONEYED=E


Various PERFMON batch Application Monitor reports do not honor

the MONEYED=E profile parameter when displaying CPU task times.

These reports always display the field using a '.' instead of

an ',' for the time decimal point.

Also when using the MONEYED=E profile parameter the file statistics

produced by report PMARPT00 will be displayed with Z's embedded

in the numeric values.

SYMPTOMS:

CPU task time fields will always be displayed with a '.' as the

decimal point instead of a ',' per European conventions. A CPU

time of 1.3 seconds should be displayed as 1,3 when MONEYED=E

is specified on the Culprit PROFILE statement.

The file statistics generated by report PMARPT00 will also have

Z's embedded in the numeric value. For example, a value of

1,122 records read will produce the following line.

112,ZZZ,ZZ2 STATISTICS RECORDS READ

IMPACT:

The format of the CPU time fields on various reports do not

conform to local conventions and users will have to interpret

the corrupted file statistics by ignoring the Z's.

CIRCUMVENTION:

None.



Star Problem(s):

IDMS 4929


DESC(CPU TIME IN PERFMON REPORTS DOESN'T HONOR MONEYED=E).

++VER (Z038)

FMID (CAGJI00)

SUP ( TR74024 TR74944 )



COMMENT (

+----------------------------------------------------------------------+


+----------+-----------------------------------------------------------+


+----------+-----------------------------------------------------------+

|PURPOSE | Update Reports |

+----------+-----------------------------------------------------------+

|USERS | All IDMS users |

|AFFECTED | |

+----------+-----------------------------------------------------------+

|KNOWLEDGE | Update definitions in the Dictionary |

|REQUIRED | |

+----------+-----------------------------------------------------------+

|ACCESS | Ability to run IDMSDDDL in batch or use IDD online |

|REQUIRED | |

+----------+-----------------------------------------------------------+

**************************


**************************


to update the dictionary which contains reports, normally

the SYSDIRL dictionary, with the input in source members:

PMARPT00

PMARPT01

PMARPT02

CA IDMS 18.0 45


Release Service DetailsPMARPT03

PMARPT04

PMARPT05

PMARPT08

PMARPT12

PMARPT14

PMARPT16

PMARPT31

The source will be in the SMP/E distribution source

library if an ACCEPT has been executed for the PTF

and in the SMPMTS library if an APPLY has been

executed but no ACCEPT has been executed.

).

CA IDMS 18.0 46




SYSTRACE STILL IN SNAP DUMPS AFTER TURNED OFF


If a CV's system trace is dynamically disabled by executing a

DCMT VARY SYSTRACE OFF command and a snap dump is generated

the dump will still contain the system trace. In addition the

system trace information in the snap dump will not be current.

SYMPTOMS:

The system trace table is displayed within a snap dump despite

the fact that the collection of trace entries has been turned

off.

IMPACT:

Users may use obsolete information within the included system

trace table when attempting to diagnose the cause of the abend

generating the snap dump.

CIRCUMVENTION:

Ignore the system trace entries within the dump if the SYSTRACE

facility has been turned off.



Star Problem(s):

IDMS 4960


DESC(SYSTRACE STILL IN SNAP DUMPS AFTER TURNED OFF).

++VER (Z038)

FMID (CAGJI00)

PRE ( RO40450 RO73468 )

SUP ( RO51217 RO53499 RO67749 TR51217 TR53499 TR67749

TR75094 )

Documents

CA IDMS 18.5 CA RS 1411 Service List unable to cancel a looping task. ptf ro74210 db002504 job9 base install with sql and backups ptf ro74237 faulty dcmt display snap values ptf ro74569