ca idms 18.5 ca rs 1309 service list€¦ · · 2013-10-03ca idms 18.5 1 ca rs 1309 service list...

CA IDMS 18.5 1

CA RS 1309 Service ListCA IDMS 18.5 1

CA RS 1309 Service List

Release Service Description Hiper

18.5 RO59339 DC027002 SMPC IN LOCK MANAGER

RO59386 GARBLED DB STATS IN ABRT JOURNAL RECORDS

RO59460 MINOR CODE 26 RETURNED DURING INDEX PROCESSING

RO59568 SUCCESSIVE VARY SEGMENT, FILE AND AREAS CAUSES CV TO HANG

RO59841 SUPPORT FOR ENTERPRISE COBOL VERSION 5.1

RO59870 3964 FOLLOWING S0F8 WHEN USING ZIIP AND EOV FILE PROCESSING

RO60833 PEA- PTF RO59841 FOR COBOL 5.1 IS MISSING HOLDDATA

The CA RS 1309 service count for this release is 7

CA IDMS 18.0 2

CA RS 1309 Service ListCA IDMS 18.0 2

CA RS 1309 Service List

Release Service Description Hiper

18.0 RO51217 IDMS/4294 INCORRECT INITIALIZATION OF RHDCSNAP WORKAREA

RO55669 CV HUNG AFTER MANY TASKS WAIT FOR QUEUE AREA LOCKS

RO56336 OLQ MAP PROBLEMS

RO56454 DB005080 ON SQL AGAINST NETWORK DB USING DBKEY INDEX

RO56519 INOUTL LINE INPUT STATEMENTS FAIL SECURITY CHECK

RO56745 PREFETCH NOT ENABLED PROPERLY AFTER STARTUP

RO56777 IDSOURCE RESP-OVERRIDE CLAUSE DOES NOT WORK AS SPECIFIED

RO57264 NOPROTECT FORCES FETCH PROTECT ON

RO57416 UCFCICZ ESD AMODE 24 CONFLICT


RO57462 0060 ERROR STATUS OR LOOPS RUNNING TUNE INDEX

RO57468 ASMA034E ON COMPILE OF UCFCICS FRONT END TABLE

RO57562 ADS/ALIVE ABEND PROCESSING INVOKED IN ERROR

RO57721 #INTB CHANGES FOR CORRECT ADDRESSING MODES

RO57729 DB005533 WHEN CHANGING THE ATTRIBUTE OF AN ACCESS MODULE

RO57995 C TRACE FUNCTION FAILS IF DEEP NESTING

RO58010 DC027002 SMPC IN LOCK MANAGER

RO58071 DCMT VDP DELETE => DC273904 IF NULL PDE & DICTNAME=''

RO58386 S113-44 ABEND DURING DATASET OPEN ON EAV VOLUME

RO58477 REORG NOT FULLY UTILIZING EAV DEVICES


RO58754 LOOK DMCL DEFAULT CALC PAGE RANGE

RO59370 S0C4 IN DEMOSQL STEP WHEN CONFIGURING WITH CSM


RO59860 PTF RO48645 IS MISSING HOLDDATA INFORMATION

RO62131 DCMT D ACTIVE TASK OVERLAY WITH MULTITASKING **HIPER**

The CA RS 1309 service count for this release is 26

CA IDMS 3

CA RS 1309 Service List for CAGJI00CA IDMS 3

CA RS 1309 Service List for CAGJI00

FMID Service Description Hiper

CAGJI00 RO51217 IDMS/4294 INCORRECT INITIALIZATION OF RHDCSNAP WORKAREA

RO55669 CV HUNG AFTER MANY TASKS WAIT FOR QUEUE AREA LOCKS

RO56336 OLQ MAP PROBLEMS

RO56454 DB005080 ON SQL AGAINST NETWORK DB USING DBKEY INDEX

RO56519 INOUTL LINE INPUT STATEMENTS FAIL SECURITY CHECK

RO56745 PREFETCH NOT ENABLED PROPERLY AFTER STARTUP

RO56777 IDSOURCE RESP-OVERRIDE CLAUSE DOES NOT WORK AS SPECIFIED

RO57264 NOPROTECT FORCES FETCH PROTECT ON


RO57462 0060 ERROR STATUS OR LOOPS RUNNING TUNE INDEX

RO57562 ADS/ALIVE ABEND PROCESSING INVOKED IN ERROR

RO57721 #INTB CHANGES FOR CORRECT ADDRESSING MODES

RO57729 DB005533 WHEN CHANGING THE ATTRIBUTE OF AN ACCESS MODULE

RO57995 C TRACE FUNCTION FAILS IF DEEP NESTING

RO58010 DC027002 SMPC IN LOCK MANAGER

RO58071 DCMT VDP DELETE => DC273904 IF NULL PDE & DICTNAME=''

RO58386 S113-44 ABEND DURING DATASET OPEN ON EAV VOLUME

RO58477 REORG NOT FULLY UTILIZING EAV DEVICES


RO58754 LOOK DMCL DEFAULT CALC PAGE RANGE

RO59370 S0C4 IN DEMOSQL STEP WHEN CONFIGURING WITH CSM


RO59860 PTF RO48645 IS MISSING HOLDDATA INFORMATION

RO62131 DCMT D ACTIVE TASK OVERLAY WITH MULTITASKING **HIPER**

The CA RS 1309 service count for this FMID is 24

CA IDMS 4




CAGJI01 RO57416 UCFCICZ ESD AMODE 24 CONFLICT

RO57468 ASMA034E ON COMPILE OF UCFCICS FRONT END TABLE


CA IDMS 5




CAGJI50 RO59339 DC027002 SMPC IN LOCK MANAGER


RO59460 MINOR CODE 26 RETURNED DURING INDEX PROCESSING


RO59841 SUPPORT FOR ENTERPRISE COBOL VERSION 5.1


RO60833 PEA- PTF RO59841 FOR COBOL 5.1 IS MISSING HOLDDATA


CA IDMS 18.5 6

CA RS 1309 - PTF RO59339 DetailsCA IDMS 18.5 6

CA RS 1309 - PTF RO59339 Details

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

DC027002 SMPC IN LOCK MANAGER

PROBLEM DESCRIPTION:

A System Module Program Check may occur in Lock Manager

IDMSLKXE program in a Data Sharing system when processing

a SYSPLEX Broadcast message. An S0C4 abend occurs when an

LKR locking resource block that had earlier been freed up

is used, resulting in an invalid address pointer.

SYMPTOMS:

The following messages are displayed on the CV joblog :

DC027002 Vxxxx Tyyyy SYSTEM MODULE PROGRAM CHECKED NEAR IDMSLMGR

+ PSW WAS 078D1E00 80043EB6

+ TASK: PROG:*SYSTEM*

+ DUMP OF SYSTEM FOLLOWS

IMPACT:

SMPC in Lock Manager. The CV may subsequently abend with a

3937 abend code.

CIRCUMVENTION:

None. Has only occurred in Data Sharing systems.

PRODUCT(S) AFFECTED: CA IDMS Release 17.0

CA IDMS Release 18.0


Star Problem(s):

IDMS 4641

Copyright (C) 2013 CA. All rights reserved. R00066-AGJ185-SP1

DESC(DC027002 SMPC IN LOCK MANAGER) .

++VER (Z038)

FMID (CAGJI50)

SUP ( TR58178 TR59339 )

CA IDMS 18.5 7




GARBLED DB STATS IN ABRT JOURNAL RECORDS


During a warmstart of a CV any outstanding run-units are recovered

and ABRT checkpoints written to the journals. CA IDMS attempts to

report some level of database statistics for these run-units by

copying the last checkpoint, BGIN or COMT, into the ABRT checkpoint.

Unfortunately the BGIN checkpoint does not contain any of the

desired statistics fields. If the last checkpoint written for

a run-unit is a BGIN the resulting statistics fields in the ABRT

checkpoint will contain garbled values when displayed on any

journal reports. Since no other source for these statistics

remains within the new CV environment they should be reported as

all zeros.

SYMPTOMS:

Database statistics generated from the journal files for aborted

run-units active at the time of a CV outage may contain garbled

values when reported through some form of journal report.

IMPACT:

Users will have incorrect numbers for database tuning or other

purposes for which they may use database statistics.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED: CA IDMS Release 17.0



Star Problem(s):

IDMS 4645


DESC(GARBLED DB STATS IN ABRT JOURNAL RECORDS) .

++VER (Z038)

FMID (CAGJI50)

SUP ( TR59386 )

CA IDMS 18.5 8




MINOR CODE 26 RETURNED DURING INDEX PROCESSING


A 0026 IDMS status may be returned by the TUNE INDEX utility

during orphan adoption. The 0026 may also be possible from a

standard program accessing an index but is most likely to occur

within TUNE INDEX due to the large amount of orphan adoption

occurring within intermediate levels of an index.

SYMPTOMS:

The TUNE INDEX utility will fail with a return code of 8.

Examination of the output from the utility reveals that an IDMS

status of 0026 was returned from the DBMS.

IMPACT:

TUNE INDEX will not be able to successfully complete against the

specified index. Subsequent processing of the index may not be

as efficient as desired.

CIRCUMVENTION:

It is possible that following additional processing against the

index that the TUNE INDEX utility may be successful however

MAINTAIN INDEX can always be used to rebuild the index.




Star Problem(s):

IDMS 4638


DESC(MINOR CODE 26 RETURNED DURING INDEX PROCESSING) .

++VER (Z038)

FMID (CAGJI50)

SUP ( RO55219 RO58646 TR55219 TR58646 TR59460 )

CA IDMS 18.5 9




SUCCESSIVE VARY SEGMENT, FILE AND AREAS CAUSES CV TO HANG


Issuing successive DCMT Vary SEGment/File commands causes the

system to hang. These commands are performed by means of

UCF Batch CV jobs.

SYMPTOMS:

After successful execution of the batch job, the system freezes

and further commands are not performed.

The system output will not display any additional messages.

An example of the Vary commands is:

- DCMT V SEGMENT USERDB OFF

- DCMT V FILE USERDB.USERDB4 CLOSE

- DCMT V FILE USERDB.USERDB4 DEALLOCATE



...

- DCMT V FILE USERDB.USERDB4 DSNAME MEN.C1300.TECHDnnn.USERDB4

- DCMT V FILE USERDB.USERDB4 ALLOCATE



...

- DCMT V SEGMENT USERDB ON

- BYE

IMPACT:

The CA IDMS CV must be cancelled and restarted.

CIRCUMVENTION:

- Add the command 'DCMT Vary DMCL New Copy' as last command in the

batch job after the vary commands.

- Perform the vary commands online.




Star Problem(s):

IDMS 4617


DESC(SUCCESSIVE VARY SEGMENT, FILE AND AREAS CAUSES CV TO HANG) .

++VER (Z038)

FMID (CAGJI50)

SUP ( RO57520 TR57520 TR59568 )

CA IDMS 18.5 10




SUPPORT FOR ENTERPRISE COBOL VERSION 5.1

DESCRIPTION:

The Enterprise COBOL for z/OS Version 5.1 compiler and run-time system

from IBM introduced changes that are not compatible with previous

CULPRIT or online IDMS-DC/UCF processing. Therefore, CULPRIT

User Modules and online IDMS-DC/UCF programs cannot be compiled

with Enterprise COBOL for z/OS Version 5.1 or above if they are

to be used with IDMS or CULPRIT Release 17.0 or earlier.

The PTFs associated with this PROBLEM must be applied to achieve

compatibility with CULPRIT and IDMS Release 18.0 and Release 18.5

Also see documentation PROBLEM IDMS 4656 for further considerations

regarding use of Enterprise COBOL Version 5.1 with CULPRIT.


SYMPTOMS:

CULPRIT user modules compiled with Enterprise COBOL Version 5.1 or

above are likely to abend with any of a variety of abend codes.

Online IDMS-DC/UCF programs compiled with Enterprise COBOL

Version 5.1 or above are also likely to abend.

COBOL programs that access IDMS from batch or CICS are not

affected.

IMPACT:

The associated application will not be usable.

CIRCUMVENTION:

Compile the COBOL program with an earlier version of the

IBM COBOL compiler.


Release 18.0

Release 18.5

Star Problem(s):

IDMS 4615


DESC(SUPPORT FOR ENTERPRISE COBOL VERSION 5.1) .

++VER (Z038)

FMID (CAGJI50)

SUP ( TR59841 )

CA IDMS 18.5 11




3964 FOLLOWING S0F8 WHEN USING ZIIP AND EOV FILE PROCESSING

PROBLEM DESCRIPTION: When starting a zIIP enabled CV, a S0F8 ABEND

followed by a 3964 if EOV processing is necessary for datasets

considered by CA IDMS to be in BSAM file format. An example of this

could be if a HFS file is used for your TCP/IP services file or if

your dataset spans multiple volumes.

SYMPTOMS: In your JES LOG you will see an initial S0F8 ABEND which

causes a U3964 ABEND. This 3964 brings down the CV upon startup.

IMPACT: Your CV will not be able to be started.

CIRCUMVENTION: You may disable zIIP by setting zIIP=N in your startup

parameters, or you can use a normal PDS instead of an HFS dataset.

PRODUCT(S) AFFECTED: CA IDMS Base Option Release 18.0

CA IDMS Base Option Release 18.5

Star Problem(s):

IDMS 4664


DESC(3964 FOLLOWING S0F8 WHEN USING ZIIP AND EOV FILE PROCESSING) .

++VER (Z038)

FMID (CAGJI50)

SUP ( TR58435 TR59870 )

CA IDMS 18.5 12




PEA- PTF RO59841 FOR COBOL 5.1 IS MISSING HOLDDATA


PEA - 18.5 PTF RO59841 (Support for Enterprise COBOL Version 5.1)

was published without SMPE HOLDDATA which can result in SMPE APPLY

processing failure.

SYMPTOMS:

During SMPE APPLY processing of PTF RO59841 the following messages

may be seen:

GIM69012I RETRANSFORMATION OF PROGRAM CULLCBSL ON LIBRARY SYSUT1

WAS SUCCESSFUL FOR SYSMOD RO59841.

GIM69102E ** ALLOCATION FAILED FOR SMPTLOAD BECAUSE THERE IS NO

DDDEF ENTRY FOR SMPTLOAD IN TARGET ZONE CAIT18.

GIM28308E ** ALLOCATION FAILED FOR SMPTLOAD WHICH IS REQUIRED IN

ORDER TO PROCESS PROGRAM ELEMENT CULLCBSL IN SYSMOD

RO59841.

GIM30216I APPLY PROCESSING FAILED FOR SYSMOD RO59841. SYSTEM

UTILITY PROCESSING FAILED FOR AN ELEMENT IN RO59841.

IMPACT:

PTF RO59841 is not applied and there will be no CA IDMS support

for Enterprise COBOL 5.1.

CIRCUMVENTION:

There is no circumvention.


Star Problem(s):

IDMS 4684


DESC(PEA- PTF RO59841 FOR COBOL 5.1 IS MISSING HOLDDATA) .

++VER (Z038)

FMID (CAGJI50)

PRE ( RO59841 )

SUP ( AR59841 RI60794 TR60833 )

++HOLD (RO60833) SYSTEM FMID(CAGJI50)

REASON (ACTION ) DATE (13197)

COMMENT (

Product: CA IDMS Release: 18.5

Sequence:

Before installing this PTF, a DDDEF for SMPTLOAD

should be defined in the target and distribution

zones of your CSI.

Purpose:

A DDDEF for SMPTLOAD will be defined

the target and distribution

zones of your CSI.

Relevance:

There must be a DDDEF for SMPTLOAD in the target

in the target and distribution zones of your CSI.

Knowledge required:

SMPE apply experience.

Access required:

SMPE library access.

Steps to Perform:

Before installing this PTF, a DDDEF for SMPTLOAD

should be defined in the target and distribution

zones of your CSI.

You can check whether this DDDEF exists with the

following LIST command:

SET BOUNDARY(CAIT18).

LIST DDDEF(SMPTLOAD).

SET BOUNDARY(CAID18).


If the DDDEF is not found, you can add it with

the following commands:

Target zone:

CA IDMS 18.5 13


Release Service DetailsSET BOUNDARY(CAIT18).


UCLIN.

ADD DDDEF(SMPTLOAD)

UNIT(SYSDA)

SPACE(5,10)

DIR(16)

CYL

ENDUCL.


Distribution zone:

SET BOUNDARY(CAID18).


UCLIN.

ADD DDDEF(SMPTLOAD)

UNIT(SYSDA)

SPACE(5,10)

DIR(16)

CYL

ENDUCL.


).

CA IDMS 18.0 14




IDMS/4294 INCORRECT INITIALIZATION OF RHDCSNAP WORKAREA


A minor coding error in IDMS/4294 incorrectly initializes an

internal work control block in RHDCSNAP using the wrong length.

This error could cause residual data to be used for subsequent

snap requests resulting in incorrect output for task and system

snaps and SVCDUMP processsing.

SYMPTOMS:

Possible symptoms include no SNAP output, SNAP processing abends,

or the wrong type of SNAP request occurs after an abend.

IMPACT:

IDMS/4294 was published on CA IDMS R17.0 as PTF RO39167 for

z/VSE clients and as PTF RO39168 for z/OS clients. IDMS/4294

was also published on CA IDMS R18.0 as PTF RO40450 for z/OS clients.

Clients who have applied these PTFs may experience various snap

processing errors or incorrect snap dumps occurring.

CIRCUMVENTION:

Disable SNAP processing using the DCMT VARY SNAP command or by

specifying OFF for the SNAP TASK and SNAP SYSTEM parameters

in the CA IDMS sysgen SYSTEM statement.


Release 18.0

Release 18.5

Star Problem(s):

IDMS 4510


DESC(IDMS/4294 INCORRECT INITIALIZATION OF RHDCSNAP WORKAREA) .

++VER (Z038)

FMID (CAGJI00)

PRE ( RO40450 )

SUP ( RO53499 TR51217 TR53499 )

CA IDMS 18.0 15




CV HUNG AFTER MANY TASKS WAIT FOR QUEUE AREA LOCKS


System hangs after several attempts to sign on to the system.

During the sign on process, the tasks stall waiting for access

to the queue area (DDLDCRUN). As more tasks wait for queue

access, the system eventually hangs. The system must be canceled

and then restarted.

SYMPTOMS:

Several stall abends and run-unit related IDMS messages are

displayed, some messages with missing parameters. For example,

Ýones with missing information marked with (*)¨:

- DC001007 V11 T8771 TASK:S PROG:RHDCSNON WAITING FOR

LTXNLOCK 00002008 0000AE03

- DC052001 V525 T122 #SENDMSG - QUEUE I/O ERROR

- DC027007 V525 T122 TASK:S PROG:RHDCSNON ABENDED WITH CODE D002

- DC001009 V11 T8771 TSKID:8879 TASK:SENDIN01 PROG:SDDADD01

HOLDS LTXNLOCK 00002008 0000AE03

- DC001010 V11 T8771 TXNID:13043968 PROG:RHDCRUAL

SUBSCHEMA:IDMSNWK7 MODE:X

- DC001009 V11 T8771 TSKID:8213 TASK:FACTOTUM PROG:*SYSTEM*

HOLDS LTXNLOCK 00002008 0000AE03

- DC001003 V11 T8771 LTXNLOCK 00002008 0000AE03 (*)

- DC027007 V11 T8771 D002 (*)

- DC075005 GETRU FAILED -- Unable to connect to this task (*)

IMPACT:

The system hangs and a Cancel has to be performed. Access to the

database is denied until the system has successfully restarted.

CIRCUMVENTION:



Release 18.0

Release 17.0

Star Problem(s):

IDMS 4580


DESC(CV HUNG AFTER MANY TASKS WAIT FOR QUEUE AREA LOCKS) .

++VER (Z038)

FMID (CAGJI00)

SUP ( TR55669 )

CA IDMS 18.0 16




OLQ MAP PROBLEMS

Problems were found in 3 OLQ maps: the mixed-case version of OLQMFLD3

is all in uppercase; the heading for OLQMFLD5 has the word 'Report'

misspelled as 'Reprot'; the mixed-case version of OLQMPRTP has the

literal 'OR CLASS:' in uppercase.


SYMPTOMS:

The map issues are strictly cosmetic and do not affect any OLQ

processing.

IMPACT:

These corrections will not affect OLQ functionality. The only

difference is they will display correctly with the proper case

displayed and without typographical errors.

CIRCUMVENTION:

There are no workarounds required.


PRODUCT(S) AFFECTED: CA OLQ Release 18.0

Star Problem(s):

IDMS 4612


DESC(OLQ MAP PROBLEMS) .

++VER (Z038)

FMID (CAGJI00)

SUP ( TR56336 )

CA IDMS 18.0 17




DB005080 ON SQL AGAINST NETWORK DB USING DBKEY INDEX


When running an SQL query against a network database and the

most optimal access path selected by the optimizer is an index

set on the member record's DBKEY, error message:

*+ DB005080 T148 C-4M324: Internal system error in jmeal : 2 0

may be returned.

SYMPTOMS:

The SQL query will fail with error message:

*+ DB005080 T148 C-4M324: Internal system error in jmeal : 2 0

IMPACT:

Each SQL query using such DBKEY index set as optimal access

path, will fail with above error message.

CIRCUMVENTION:

No circumvention available.




Star Problem(s):

IDMS 4579


DESC(DB005080 ON SQL AGAINST NETWORK DB USING DBKEY INDEX) .

++VER (Z038)

FMID (CAGJI00)

SUP ( TR56454 )

CA IDMS 18.0 18




INOUTL LINE INPUT STATEMENTS FAIL SECURITY CHECK


If security is enabled for a CV and an INOUTL line is defined,

a security error occurs for the input task commands included

in the input file for the line. The security errors occur

even if the task codes for the input statements and the userid

of the user which submitted the CV startup JCL are defined

to IDMS security.

SYMPTOMS:

For example, if userid CVUSER and task code DCMT are defined

to security and CVUSER submits the CV startup JCL for CV89

and the INOUTL line input statements contain DCMT commands,

then the following security error occurs during CV startup for

the INOUTL line:

IDMS DC021102 V89 SECURITY VIOLATION BY USER ***.

ACCESS TO RESOURCE DCMT DENIED.

The same error occurs if the INOUTL line is varied online.

IMPACT:

With security enabled for the IDMS CV, none of the input

statements for the INOUTL line will be executed without

receiving a security error.

CIRCUMVENTION:



Release 18.0

Release 18.5

Star Problem(s):

IDMS 4613


DESC(INOUTL LINE INPUT STATEMENTS FAIL SECURITY CHECK) .

++VER (Z038)

FMID (CAGJI00)

SUP ( TR56519 )

CA IDMS 18.0 19




PREFETCH NOT ENABLED PROPERLY AFTER STARTUP


Any files assigned to the same buffer pool as the system dictionary

will not be allowed to use PREFETCH processing following the CV's

startup even if the CV has had PREFETCH enabled and the buffer

pool contains sufficient pages to allow PREFETCH to be used.

Varying the buffer to any number of pages large enough to enable

PREFETCH will result in these files using PREFETCH.

SYMPTOMS:

PREFETCH I/O will not be performed against files that should have

the feature enabled. A DCMT DIS FILE for these files will indicate

that PREFETCH is not allowed with a reason of (Buffer Cnt).

IMPACT:

Applications that were intended to use PREFETCH may run slower

than anticipated.

CIRCUMVENTION:

Issue a DCMT VARY BUFFER and change the number of pages used by the

buffer to a number larger than 500.




Star Problem(s):

IDMS 4587


DESC(PREFETCH NOT ENABLED PROPERLY AFTER STARTUP) .

++VER (Z038)

FMID (CAGJI00)

PRE ( RO26303 RO30578 RO31998 RO33429 )

SUP ( RO36113 RO41453 RO49042 RO51184 RO52829 RO54795

TR36113 TR41453 TR49042 TR51184 TR52829 TR54795

TR56745 )

CA IDMS 18.0 20




IDSOURCE RESP-OVERRIDE CLAUSE DOES NOT WORK AS SPECIFIED


When the RESP-OVERRIDE clause is specified in the IDSOURCE

parameter of Dictionary Migrator this should release

Dictionary security by generating a REGISTRATION OVERRIDE in the

IDD SET OPTIONS statement. This is not working as specified.

SYMPTOMS:

DC601081 USER NOT REGISTERED FOR FUNCTION AGAINST THIS ENTITY

Message may result from the attempted PUNCH of Source

Dictionary entites, without the appropriate user authority. The

use of a REGISTRATION OVERRIDE clause in the SET OPTIONS

overcomes this problem.

IMPACT:

The extraction of Dictionary entities fails.

CIRCUMVENTION:

None.




Star Problem(s):

IDMS 4614


DESC(IDSOURCE RESP-OVERRIDE CLAUSE DOES NOT WORK AS SPECIFIED) .

++VER (Z038)

FMID (CAGJI00)

SUP ( RO51720 TR51720 TR56777 )

CA IDMS 18.0 21




NOPROTECT FORCES FETCH PROTECT ON


When a system is defined as NOPROTECT in sysgen, fetch protect

is not turned off during startup.

SYMPTOMS:

The system is fetch protected when storage protect is off.

IMPACT:

The system cannot be read from another system running in a

different key. This poses a problem especially with Perfmon

external monitoring, as a fetch-protected system cannot be

monitored externally.

CIRCUMVENTION:

Run the system with storage protect turned on.

PRODUCT(S) AFFECTED:




Star Problem(s):

IDMS 4620


DESC(NOPROTECT FORCES FETCH PROTECT ON) .

++VER (Z038)

FMID (CAGJI00)

PRE ( RO27242 RO35437 RO49538 )

SUP ( RO42589 TR42589 TR57264 )

CA IDMS 18.0 22




UCFCICZ ESD AMODE 24 CONFLICT


Generating a UCFCICZ module produces a linkage editor warning.

SYMPTOMS:

"IEW2651W ESD AMODE 24 CONFLICTS WITH USER-SPECIFIED AMODE 31 FOR

ENTRY POINT CICZEP." message appears in the linkage editor step.

IMPACT:

Product functionality is not affected.

CIRCUMVENTION:

Ignore the IEW2651W warning message.


Star Problem(s):

IDMS 4625


DESC(UCFCICZ ESD AMODE 24 CONFLICT) .

++VER (Z038)

FMID (CAGJI01)

SUP ( TR57416 )

CA IDMS 18.0 23




SUCCESSIVE VARY SEGMENT, FILE AND AREAS CAUSES CV TO HANG


Issuing successive DCMT Vary SEGment/File commands causes the

system to hang. These commands are performed by means of

UCF Batch CV jobs.

SYMPTOMS:

After successful execution of the batch job, the system freezes

and further commands are not performed.

The system output will not display any additional messages.

An example of the Vary commands is:

- DCMT V SEGMENT USERDB OFF





...





...

- DCMT V SEGMENT USERDB ON

- BYE

IMPACT:

The CA IDMS CV must be cancelled and restarted.

CIRCUMVENTION:

- Add the command 'DCMT Vary DMCL New Copy' as last command in the

batch job after the vary commands.

- Perform the vary commands online.




Star Problem(s):

IDMS 4617


DESC(SUCCESSIVE VARY SEGMENT, FILE AND AREAS CAUSES CV TO HANG) .

++VER (Z038)

FMID (CAGJI00)

PRE ( RO31998 RO34034 RO35804 RO48379 )

SUP ( AC57521 RO26893 RO27707 RO27886 RO34918 RO36963

RO38054 RO41036 RO51132 RO51972 RO52570 RO57519

TR26893 TR27707 TR27886 TR34918 TR36963 TR38054

TR41036 TR47810 TR51132 TR51972 TR52570 TR57434

TR57519 )

CA IDMS 18.0 24




0060 ERROR STATUS OR LOOPS RUNNING TUNE INDEX


An error status of 0060 may be encountered when running the TUNE

INDEX utility in a CV mode. This error may also result in apparent

loops or hangs of the TUNE INDEX utility or its CV. This is

most likely to occur when multiple indexes are processed in a

single execution of the utility and the RESEQUENCE option has been

selected.

SYMPTOMS:

TUNE INDEX may terminate with a 0060 error status or the CV against

which it is run may appear to be looping or in a hang condition.

IMPACT:

The TUNE INDEX utility may not be able to be completed and in the

worst cases it may be necessary to cycle the CV against which the

utility is being run.

CIRCUMVENTION:

Process a single index per execution of the TUNE INDEX utility.



Star Problem(s):

IDMS 4622


DESC(0060 ERROR STATUS OR LOOPS RUNNING TUNE INDEX) .

++VER (Z038)

FMID (CAGJI00)

PRE ( RO29749 )

SUP ( RO30023 RO31264 RO37559 RO51921 RO53588 RO53879

TR30023 TR31264 TR37559 TR51921 TR53588 TR53879

TR57462 )

CA IDMS 18.0 25




ASMA034E ON COMPILE OF UCFCICS FRONT END TABLE


ASMA034E ON COMPILE OF UCFCICS FRONT END TABLE

If the #UCFCICS Front End Table contains more than 26 #UCFUTD

terminal entries, the assembly will fail with condition code 8

and the following message will be issued.

ASMA034E Operand =V(UCFCXEP1) beyond active USING range by nnn bytes

SYMPTOMS:

You will get the ASM034E message and the UCFCICS Front End Table

will not compile.

IMPACT:

You will not have a UCFCICS Front End Table to communicate with

the CA IDMS CV.

CIRCUMVENTION:

After the #UCFCICS statement in the assembly, enter a line that

has LTORG coded. Here is an example.

UCFCICS #UCFCICS UCTRAN=TCT,RESETKB=TASKEND,LASTOUT=TASKEND,DISC=YES

LTORG

This will allow the assembly to run correctly.



Star Problem(s):

IDMS 4627


DESC(ASMA034E ON COMPILE OF UCFCICS FRONT END TABLE) .

++VER (Z038)

FMID (CAGJI01)

SUP ( TR57468 )

CA IDMS 18.0 26




ADS/ALIVE ABEND PROCESSING INVOKED IN ERROR


When an ADS dialog abends, ADS/Alive post abend processing

may be invoked in error in a CV where ADS/Alive is not

activated.

SYMPTOMS:

After a dialog abend the following message is displayed :-

IDMS DC021002 V11 T1xxxx yyyyyyyy TASK:MENU; LOAD OF

USGTPARM FAILED--EITHER NOT DEFINED TO SYSTEM, DISABLED,

OR NOT IN LOAD LIBRARY

IMPACT:

Normal ADS Abend processing is bypassed and the above

message is displayed in error.

CIRCUMVENTION:

ADS/Alive post abend processing can be avoided by setting

optional bit OPT00089 on in the RHDCOPTF settings.



Star Problem(s):

IDMS 4630


DESC(ADS/ALIVE ABEND PROCESSING INVOKED IN ERROR) .

++VER (Z038)

FMID (CAGJI00)

SUP ( TR57562 )

CA IDMS 18.0 27




#INTB CHANGES FOR CORRECT ADDRESSING MODES


Changes to copybook #INTB to ensure the correct addressing

mode of AMODE 31 is used when IDMSUXIT gets called.

Otherwise S0C4 abends are possible in batch programs.

See also IDMS/4553.

SYMPTOMS:

Batch programs may abend with messages :

SYSTEM COMPLETION CODE=0C4 REASON CODE=00000011

PSW AT TIME OF ERROR 078D0000 00011AA2 ILC 4 INTC 11

ACTIVE LOAD MODULE ADDRESS=00010B58 OFFSET=000F4A

NAME=IDMSINTB

IMPACT:

Possible Batch program abends.

CIRCUMVENTION:

None.



Star Problem(s):

IDMS 4634


DESC(#INTB CHANGES FOR CORRECT ADDRESSING MODES) .

++VER (Z038)

FMID (CAGJI00)

PRE ( RO50854 )

SUP ( RO33342 RO52949 TR33342 TR50846 TR52949 TR57721 )

CA IDMS 18.0 28




DB005533 WHEN CHANGING THE ATTRIBUTE OF AN ACCESS MODULE


Trying to change the attribute of an access module, for example

AUTO RECREATE ON/OFF by means of an ALTER ACCESS MODULE

statement without replacing 1 or more RCMs, will result in error

message "DB005533 Requested RCMs not found." being issued.

SYMPTOMS:

Following ALTER ACCESS MODULE statement will produce the DB005533

error message:

ALTER ACCESS MODULE <schema-name>.<am-name> AUTO RECREATE OFF;

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

*+ DB005533 T125 C-4M324: Requested RCMs not found.

IMPACT:

It is not possible to change the attribute of an access module

without having to recreate it, that is ADD, DROP or REPLACE at

least 1 RCM.

CIRCUMVENTION:

DROP and afterwards reCREATE the access module with the correct

attributes or specify the 'REPLACE ALL' option.

In the example above, that would be the following statement:

ALTER ACCESS MODULE <schema-name>.<am-name> REPLACE ALL

AUTO RECREATE OFF;




Star Problem(s):

IDMS 4596

SMPC IN IDMSDBMS AFTER DYNAMIC RECOMPILE OF ACCESS MODULE.


After an access module is dynamically recompiled because of an

RCM stamp mismatch, the related application program may abend

with a program check near IDMSDBMS.

This is most likely to happen when records/tables are accessed

by a record/table that is not referenced by any of the SQL

statements of this particular RCM.

SYMPTOMS:

The following messages may be observed in the CV log:

IDMS DB005540 V75 C0M324: Dynamic recompile of SLKONV because

of RCM stamp mismatch.

IDMS DB027002 V75 T416339 SYSTEM MODULE PROGRAM CHECKED NEAR

IDMSDBMS AT OFFSET C0D6

PSW WAS 078D1E00 A420E6D6

TASK:ADS2 PROG:F258OBP

DUMP OF SYSTEM FOLLOWS

IMPACT:

Each execution of this application program will abend with the

same program check and error messages, until the related access

module is manually recompiled.

CIRCUMVENTION:

Manually recompile the access module by means of the ALTER

ACCESS MODULE statement and using the REPLACE option.




Star Problem(s):

IDMS 4632


DESC(DB005533 WHEN CHANGING THE ATTRIBUTE OF AN ACCESS MODULE) .

++VER (Z038)

FMID (CAGJI00)

PRE ( RO36699 )

SUP ( RO29760 TR29760 TR57729 )

CA IDMS 18.0 29




C TRACE FUNCTION FAILS IF DEEP NESTING


When the C trace function call has more than 80 entries,

because of deep nesting, the tracing stops until completion of

the SQL compile.

SYMPTOMS:

The SQL compile can end with a protection exception or internal

system error. The chance of abend increases with an increasing

call depth.

IMPACT:

The SQL compile will not complete.

CIRCUMVENTION:




Star Problem(s):

IDMS 4637


DESC(C TRACE FUNCTION FAILS IF DEEP NESTING) .

++VER (Z038)

FMID (CAGJI00)

SUP ( TR57995 )

CA IDMS 18.0 30




DC027002 SMPC IN LOCK MANAGER


A System Module Program Check may occur in Lock Manager

IDMSLKXE program in a Data Sharing system when processing

a SYSPLEX Broadcast message. An S0C4 abend occurs when an

LKR locking resource block that had earlier been freed up

is used, resulting in an invalid address pointer.

SYMPTOMS:

The following messages are displayed on the CV joblog :

DC027002 Vxxxx Tyyyy SYSTEM MODULE PROGRAM CHECKED NEAR IDMSLMGR

+ PSW WAS 078D1E00 80043EB6

+ TASK: PROG:*SYSTEM*

+ DUMP OF SYSTEM FOLLOWS

IMPACT:

SMPC in Lock Manager. The CV may subsequently abend with a

3937 abend code.

CIRCUMVENTION:

None. Has only occurred in Data Sharing systems.




Star Problem(s):

IDMS 4641


DESC(DC027002 SMPC IN LOCK MANAGER) .

++VER (Z038)

FMID (CAGJI00)

PRE ( RO46965 )

SUP ( TR58010 )

CA IDMS 18.0 31




DCMT VDP DELETE => DC273904 IF NULL PDE & DICTNAME=''


Program definitions that are created automatically such as by

using an IDMS or an IDMS Development Tool (ADSC, ADSOBCOM),

will not be found when issuing the command:

- DCMT Vary Dynamic Program <program_name> DELete .

This will occur when the dictionary is the default, DICTNAME=''.

The command fails because the default dictionary is not used in the

search for the Program Definition Element (PDE) to be deleted.

For more details, see: CA IDMS System Operations

-> Appendix D: DC/UCF Test Environment

-> Programs and the Test Environment

SYMPTOMS:

An attempt to delete a program definition (automatically created)

by means of the Task Code:

- 'DCMT VDP <program_name> DELete .'

will display the following message:

- IDMS DC273904 V125 Program <program_name> DOES NOT EXIST

IMPACT:

The program definition cannot be deleted by means of

DCMT VDP <program> DELETE .

CIRCUMVENTION:

There is no circumvention to delete the dynamically allocated Program

Definition Element.

To prevent the program from being executed, the client can issue

- DCMT Vary PRogram <program_name> DIsable




Star Problem(s):

IDMS 4609


DESC(DCMT VDP DELETE => DC273904 IF NULL PDE & DICTNAME='') .

++VER (Z038)

FMID (CAGJI00)

SUP ( TR56811 TR58071 )

CA IDMS 18.0 32




S113-44 ABEND DURING DATASET OPEN ON EAV VOLUME


A S113-44 abend will occur during the open of an CA IDMS database

file which is located on an Extended Address Volume beyond the

65,520 cylinder address range.

SYMPTOMS:

A S113-44 abend occurs attempting to open a CA IDMS database file

which is allocated beyond the 65,520 cylinder address range on an

EAV volume. The following error message is displayed in the job

output and the job abends:

IEC142I 113-44,IFG0194D,jobname,stepname,ddname,device#,volser,

dataset name

IMPACT:

The S113-44 abend will only occur for z/OS systems using EAV

volume support on z/OS 1.12 or later. Prior to z/OS 1.12, EAV

capacity did not exceed 65,520 cylinders. For z/OS 1.12 or

later systems using EAV support, the job attempting to open

the CA IDMS database file is abended and the CA IDMS database

file is unusable as long as it resides on the EAV volume beyond

the 65,520 cylinder address range.

CIRCUMVENTION:

If using EAV volume support on z/OS 1.12 or later, then allocate

all CA IDMS database files below the 65,520 cylinder address

range to prevent the S113-44 open abend.



Star Problem(s):

IDMS 4646


DESC(S113-44 ABEND DURING DATASET OPEN ON EAV VOLUME) .

++VER (Z038)

FMID (CAGJI00)

PRE ( RO27242 )

SUP ( TR58386 )

CA IDMS 18.0 33




REORG NOT FULLY UTILIZING EAV DEVICES


Dynamically allocated work files requested by a CA IDMS utility

are not allocated above the 65,520 cylinder range on an EAV

volume.

SYMPTOMS:

For example, the CA IDMS REORG utility requests several work

files to be allocated on a EAV volume past the 65,520 cylinder

range and the volume has ample space to satisfy the request.

However, the allocation request is denied due to insufficient

space and the following messages are displayed for each work file:

IGD17272I VOLUME SELECTION HAS FAILED FOR INSUFFICIENT SPACE FOR

<work file dataset name> ...(volume information is displayed)

IKJ56893I DATA SET <work file dataset name> NOT ALLOCATED+ ...

IGD17279I 1 VOLUMES WERE REJECTED BECAUSE THEY DID NOT HAVE

SUFFICIENT SPACE ...

+IDMS DB002261 C1M161: Dynamic file allocation failed - RC=004

ERR=970C INFO=0000 DSN=<work file dataset name>,

the IDMSBCF job executing the REORG utility abends with RC=08.

IMPACT:

The EAV volume is not fully utilized and the CA IDMS REORG utility

is unable to allocate the required work files on the EAV volume

beyond the 65,520 cylinder range.

CIRCUMVENTION:

Do not use dynamic allocation of the work files. Instead, manually

allocate the work files specifying EATTR=OPT on the DD statements for

the work files in the JCL for the IDMSBCF job.



Star Problem(s):

IDMS 4648


DESC(REORG NOT FULLY UTILIZING EAV DEVICES) .

++VER (Z038)

FMID (CAGJI00)

SUP ( RO38671 RO42075 TR38671 TR42075 TR58477 )

CA IDMS 18.0 34




GARBLED DB STATS IN ABRT JOURNAL RECORDS


During a warmstart of a CV any outstanding run-units are recovered

and ABRT checkpoints written to the journals. CA IDMS attempts to

report some level of database statistics for these run-units by

copying the last checkpoint, BGIN or COMT, into the ABRT checkpoint.

Unfortunately the BGIN checkpoint does not contain any of the

desired statistics fields. If the last checkpoint written for

a run-unit is a BGIN the resulting statistics fields in the ABRT

checkpoint will contain garbled values when displayed on any

journal reports. Since no other source for these statistics

remains within the new CV environment they should be reported as

all zeros.

SYMPTOMS:

Database statistics generated from the journal files for aborted

run-units active at the time of a CV outage may contain garbled

values when reported through some form of journal report.

IMPACT:

Users will have incorrect numbers for database tuning or other

purposes for which they may use database statistics.

CIRCUMVENTION:

None.




Star Problem(s):

IDMS 4645


DESC(GARBLED DB STATS IN ABRT JOURNAL RECORDS) .

++VER (Z038)

FMID (CAGJI00)

SUP ( TR58294 TR58552 )

CA IDMS 18.0 35




LOOK DMCL DEFAULT CALC PAGE RANGE


Adding an additional line to the LOOK DMCL ALL command stating

the Default CALC Page Range.

SYMPTOMS:

Output does not show the Default CALC Page Range.

IMPACT:

Client cannot see the Default CALC Page Range next to the

Area Page Range.

CIRCUMVENTION:

NONE




Star Problem(s):

IDMS 4626


DESC(LOOK DMCL DEFAULT CALC PAGE RANGE) .

++VER (Z038)

FMID (CAGJI00)

SUP ( TR58754 )

CA IDMS 18.0 36




S0C4 IN DEMOSQL STEP WHEN CONFIGURING WITH CSM


When doing an IDMS 18.5 configuration with CSM, a S0C4 may

occur in the DEMOSQL step. The problem is not related to CSM

or the IDMS metadata, but will most probably happen after

applying the appropriate solution for problem IDMS/4632,

that is RO58675 & RO58673 for R17.0 z/OS and z/VSE, RO57729

for R18.0 z/OS and RO57897 for R18.5 z/OS.

Those solutions for problem IDMS/4632 don't seem to cause

any harm in normal batch or CV processing, but when IDMSAMC

is called in a CSM or XDC environment, it causes a S0C4.

SYMPTOMS:

The DEMOSQL step of the configuration job will terminate

with a S0C4 abend code.

IMPACT:

The configuration job will terminate with a S0C4 abend code

in the DEMOSQL step.

CIRCUMVENTION:

There is no circumvention available.




Star Problem(s):

IDMS 4649


DESC(S0C4 IN DEMOSQL STEP WHEN CONFIGURING WITH CSM) .

++VER (Z038)

FMID (CAGJI00)

PRE ( RO57729 )

SUP ( TR59370 )

CA IDMS 18.0 37




3964 FOLLOWING S0F8 WHEN USING ZIIP AND EOV FILE PROCESSING

PROBLEM DESCRIPTION: When starting a zIIP enabled CV, a S0F8 ABEND

followed by a 3964 if EOV processing is necessary for datasets

considered by CA IDMS to be in BSAM file format. An example of this

could be if a HFS file is used for your TCP/IP services file or if

your dataset spans multiple volumes.

SYMPTOMS: In your JES LOG you will see an initial S0F8 ABEND which

causes a U3964 ABEND. This 3964 brings down the CV upon startup.

IMPACT: Your CV will not be able to be started.

CIRCUMVENTION: You may disable zIIP by setting zIIP=N in your startup

parameters, or you can use a normal PDS instead of an HFS dataset.


CA IDMS Base Option Release 18.5

Star Problem(s):

IDMS 4664


DESC(3964 FOLLOWING S0F8 WHEN USING ZIIP AND EOV FILE PROCESSING) .

++VER (Z038)

FMID (CAGJI00)

PRE ( RO27242 )

SUP ( RO58386 TR58386 TR59833 )

CA IDMS 18.0 38




PTF RO48645 IS MISSING HOLDDATA INFORMATION


PTF RO48645 does not include HOLDDATA information describing the

need to include a #DEFOPTF entry in RHDCOPTF.

SYMPTOMS:

Any processing enabled by this PTF does not occur.

IMPACT:

The need to include a #DEFOPTF entry may go unnoticed.

CIRCUMVENTION:

None.


Star Problem(s):

IDMS 4665


DESC(PTF RO48645 IS MISSING HOLDDATA INFORMATION) .

++VER (Z038)

FMID (CAGJI00)

PRE ( RO48645 )

SUP ( TR43828 TR59860 )

++HOLD (RO59860) SYSTEM FMID(CAGJI00)

REASON (ACTION ) DATE (13162)

COMMENT (

Product: CA IDMS Release: 18.0

Sequence: Before APPLY.

Purpose: Enable the use of optional functionality.

Relevance: All IDMS users making use of Optional apars.

Knowledge required:

SMP/E, Assemble #DEFOPTF macro, and/or ability to change SYSIDMS

parameters and perform SYSGEN modification.

Access required:

CA IDMS CSI and libraries, CA IDMS Startup JCL, SYSGEN compiler.

Steps to Perform:

To implement the functionality introduced by this PTF you will need

to Code the following #DEFOPTF in your RHDCOPTF source and then

re-assemble and link the RHDCOPTF module.

Code the following #DEFOPTF in your RHDCOPTF

module to activate this optional code:

#DEFOPTF OPT00327

).

CA IDMS 18.0 39




DCMT D ACTIVE TASK OVERLAY WITH MULTITASKING


DCMT DISPLAY ACTIVE TASK command can overlay storage in a

busy MULTITASKING CV. The RHDCMTTA program cannot lock the

dispatch chain (DCE Chain) because it would affect CV processing.

It is possible to walk off the DCE or ECB chain which

results in storage overlays in storage that does not belong to

the DCMT task. The storage overlay can result in numerous abends

including the abend of the CA IDMS CV.

Some of the abends that can occur when the storage is violated

are S0C4's,DC016003 Storage Violations, 3985 or 3990 abend of

the CA IDMS CV, D003 and D002 abends. The abends/aborts are

unpredictable due to the possibilty of a massive overlay.

SYMPTOMS:

Due to the storage overlay, tasks can abort and storage violations

will occur. The CA IDMS CV may abend due to the overlaid storage.

IMPACT:

The CA IDMS CV abends or tasks abort affecting production.

CIRCUMVENTION:

The ONLY getaround would be to disable the RHDCMTTA program.




Star Problem(s):

IDMS 4705


DESC(DCMT D ACTIVE TASK OVERLAY WITH MULTITASKING) .

++VER (Z038)

FMID (CAGJI00)

PRE ( RO41190 )

SUP ( BC57521 RO31569 TR31550 TR31569 TR62131 )

ca idms 18.5 ca rs 1309 service list€¦ · · 2013-10-03ca idms 18.5 1 ca rs 1309 service list...

Documents