CA Repository for z/OS 7.2 CA RS 1309 Service List · CA Repository for z/OS 2 ... CA RS 1309...

CA Repository for z/OS 7.2 1

CA RS 1309 Service ListCA Repository for z/OS 7.2 1

CA RS 1309 Service List

Release Service Description Hiper

7.2 RO56794 COLUMN "ROUND" NOT FOUND

RO56812 REPORT PANELS EDIT JCL => N LOOPS

RO57150 TERADATA MUST SORT ON DATABASE

RO57504 VIEW COLUMNS OUT OF SYNC

RO57514 DBXTRDV PERFORMANCE SLOWED

RO57536 COLUMN 'NEXTVAL' NOT FOUND

RO58023 ENCODING(EBCDIC 500) BINDS

RO58240 VIEW COLUMN RENAME WITHOUT AN "AS" KEYWORD

RO58507 COLUMN "POSITION" NOT FOUND

RO59098 DBXCATA - DB2 V10 VIEW CATSYNC ERROR 0C4

RO59228 PROGDEF - VERSIONS IN PART AND SPACE TBL

RO59880 ERWINXML - ERWIN EXCHANGE FOR ERWIN R9

RO59922 MAPS W/SPECIAL CHARACTERS CAUSE XSD FAILURE

RO60101 COLUMN 'NEXT' NOT FOUND

The CA RS 1309 service count for this release is 14

CA Repository for z/OS 2

CA RS 1309 Service List for CNW7200CA Repository for z/OS 2

CA RS 1309 Service List for CNW7200

FMID Service Description Hiper

CNW7200 RO56794 COLUMN "ROUND" NOT FOUND

RO57536 COLUMN 'NEXTVAL' NOT FOUND

RO58240 VIEW COLUMN RENAME WITHOUT AN "AS" KEYWORD

RO58507 COLUMN "POSITION" NOT FOUND

RO60101 COLUMN 'NEXT' NOT FOUND

The CA RS 1309 service count for this FMID is 5


CA RS 1309 Service List for COL7200CA Repository for z/OS 3

CA RS 1309 Service List for COL7200


COL7200 RO57504 VIEW COLUMNS OUT OF SYNC

RO57514 DBXTRDV PERFORMANCE SLOWED



CA RS 1309 Service List for CP$7200CA Repository for z/OS 4

CA RS 1309 Service List for CP$7200


CP$7200 RO56812 REPORT PANELS EDIT JCL => N LOOPS

RO57150 TERADATA MUST SORT ON DATABASE

RO58023 ENCODING(EBCDIC 500) BINDS

RO59228 PROGDEF - VERSIONS IN PART AND SPACE TBL

RO59880 ERWINXML - ERWIN EXCHANGE FOR ERWIN R9

RO59922 MAPS W/SPECIAL CHARACTERS CAUSE XSD FAILURE



CA RS 1309 Service List for CQH7200CA Repository for z/OS 5

CA RS 1309 Service List for CQH7200


CQH7200 RO59098 DBXCATA - DB2 V10 VIEW CATSYNC ERROR 0C4



CA RS 1309 - PTF RO56794 DetailsCA Repository for z/OS 7.2 6

CA RS 1309 - PTF RO56794 Details

Release Service Details7.2 RO56794 RO56794 M.C.S. ENTRIES = ++PTF (RO56794)

DESC (COLUMN "ROUND" NOT FOUND)

/*-------------------------------------------------------------------

PRODUCT: CA Repository Exchange for COBOL

RELEASE: 7.2

DATE: 27 MAR 2013

HYPER: NO

STARTRAK PROBLEM PRODUCT NAME: XSC PROBLEM NUMBER: 88

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

COLUMN "ROUND" NOT FOUND

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

The COBOL scanner, MSCANDB2, does not recognize the reserved

words "ROUND".

This results in a "COLUMN" not found error message and a RC=04 for

the step when processing any COBOL program that contains this

particular reserved word.

SYMPTOMS:

A COBOL program containing (for example):

EXEC SQL

DECLARE CURSOR_MRT CURSOR FOR

SELECT VERSION,

ROUND(KEY_NAME) !! ' ' !!

ROUND(STATUS), <<

DESCRIPTION

FROM DBX_DB2_KEY

WHERE ENT_ID = 2154

END-EXEC.

will get the message:

THE COLUMN "ROUND" OF TABLE ".DBX_DB2_KEY" WAS NOT FOUND.

IMPACT:

A COBOL program containing the reserved word (FUNCTION)

"ROUND" cannot be scanned into the Repository because

the Repository is treating the reserved word as a DB2

column name and generating a warning message

"THE COLUMN "ROUND " OF TABLE "XXXXXXX.DBX_DB2_KEY"

WAS NOT FOUND."

CIRCUMVENTION:

None.

PRODUCT(S) AFFECTED:

CA Repository Exchange for COBOL r7.2

-------------------------------------------------------------------*/.

++VER (Z038) FMID(CNW7200)

SUP (T5QV970,T5QV922,RO44941,T5QV590,T5QV576,T5QV182,

RO30379,T5QV106,RO26865,T5QV101,RO26994,RO44218,

RO50702,T5QV822,AR48152,RO48152,T5QV647,RO55369).





DESC (REPORT PANELS EDIT JCL => N LOOPS)

/*-------------------------------------------------------------------

PRODUCT: CA Repository for z/OS

RELEASE: 7.2

DATE: 27 MAR 2013

HYPER: NO

STARTRAK PROBLEM PRODUCT NAME: XTR PROBLEM NUMBER: 730

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

REPORT PANELS EDIT JCL => N LOOPS

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

When a user selects OPTIONS/REPORTS/NAMETOKN from the main

dialog screen, and the AR/ZOS PRINT panel comes up, there

is an OPTION "SUBMIT JCL? =====> (Y/N).

Answering NO is supposed to submit the generated JCL automatically,

without displaying the file for EDIT. However, the system

simply loops, unable to accept the dataset name

SYMPTOMS:

Entering OPTIONS/REPORTS/NAMETOKN with the "SUBMIT JCL = N"

parm, returns the message:

IKJ56709I INVALID DATA SET NAME, '<usrid>.RZOS.ISPF.FILE

and will not accept any known input.

IMPACT:

The user cannot submit the report JCL automatically

and must ATTN out of Repository all together.

CIRCUMVENTION:

NONE

PROBLEM DESCRIPTION: UNABLE TO GENERATE NAMETOKN TWICE IN SUCCESSION

XTR 729

When a user selects OPTIONS/REPORTS/NAMETOKN from the main

dialog screen, produces the report, and then backs out to

the main dialog screen, they cannot produce a report again.

If they enter OPTIONS/REPORTS/NAMETOKN again,

the screen merely returns to the main dialog screen

without displaying the AR/ZOS PRINT screen.

SYMPTOMS:

Entering OPTIONS/REPORTS/NAMETOKN for a second time will

simply return to the main dialog screen without displaying

the AR/ZOS PRINT screen.

IMPACT:

The user has to sign out of Repository completely and start

over to generate another report.

CIRCUMVENTION:

NONE

PRODUCTS AFFECTED:

CA Repository for z/OS r7.2.

-------------------------------------------------------------------*/.

++VER (Z038) FMID(CP$7200)

SUP (T5QV951,T5QV940).

++HOLD(RO56812) SYSTEM REASON(DB2BIND) FMID(CP$7200) COMMENT(

Product: CA Repository for z/OS Release: 7.2

Sequence: After Apply.

Purpose: DB2 Bind

Relevance: If you are applying the re-compiled module, you must bind the

DBRM into the DB2 subsystem.

Knowledge required:

Bind procedures on relevant DB2 subsys.

Access required:

Bind authority on relevant DB2 subsys

Steps to be performed:

Once the SMP/e portion of the fix application

is complete, the following instructions should

be turned over to the DB2 DBA in charge of the

repository for customization to your site's

specific procedures.



Release Service DetailsBind package DBXPRNT

with the following parameters:

DSN SYSTEM(subsys)

BIND PACKAGE(collection name)-

ENCODING(EBCDIC) -

ENABLE(*) -

PATH(repository qual) -

QUALIFIER(repository qual) -

MEMBER(DBXPRNT) -

VALIDATE(BIND) -

DYNAMICRULES(BIND) -

ISOLATION(CS) -

EXPLAIN(NO) -

FLAG(I) -

RELEASE(COMMIT) -

ACTION(REPLACE) -

END

Make the following substitutions for the values of the

parameters so they conform to your site's environment.

Change:

- subsys to the db2 system

- collection name to the repository package collection

- repository qual to the repository owner.

Make sure the DBRMLIB DD statement points to the

DBRM library that contains the DBRMs associated

with the PTFs that are applied.

).





DESC (TERADATA MUST SORT ON DATABASE)

/*-------------------------------------------------------------------

PRODUCT: CA Repository Exchange for Terada

RELEASE: 7.2

DATE: 4 APR 2013

HYPER: NO

STARTRAK PROBLEM PRODUCT NAME: XTD PROBLEM NUMBER: 44

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

TERADATA MUST SORT ON DATABASE

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

The CA Repository Exchange for TERADATA caysync job needs to

sort the input file starting in column 09, which includes the

DATABASE field. Files may contain data from more than one

database and data may not be unique without the database name.

SYMPTOMS:

While symptoms will vary depending on the particulars of the

input file used, the most common result will be

ABEND=S000 U4038 REASON=00000001

in the first step after the sort, which runs program DBXTRDV.

IMPACT:

The catsync fails and the data file cannot be inserted into

the CA Repository.

CIRCUMVENTION:

None.


CA Repository Exchange for Teradata r7.2

-------------------------------------------------------------------*/.

++VER (Z038) FMID(CP$7200)

SUP (T5QV697).





DESC (VIEW COLUMNS OUT OF SYNC)

/*-------------------------------------------------------------------


RELEASE: 7.2

DATE: 12 APR 2013

HYPER: NO


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

VIEW COLUMNS OUT OF SYNC

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

When processing VIEW COL records for a view, the CA Repository

Exchange for Teradata catsync program captures the VIEW database

and uses it as the table creator for the table on which the

view is defined.

SYMPTOMS:

While symptoms will vary depending on the particulars of the

input file used, if a table exists by the same name

as the VIEW table in the View database, the program will use

this table rather than the correct one, resulting in

the misalignment of columns. This can lead to various problems

in the subsequent load program, in particular an XIO00011,

(ENTITY NOT FOUND).

IMPACT:

The catsync stops at the XIO00011 and the entire run is rolled

back.

CIRCUMVENTION:

None.



-------------------------------------------------------------------*/.

++VER (Z038) FMID(COL7200)

PRE (RO50966)

SUP (T5QV823).





DESC (DBXTRDV PERFORMANCE SLOWED)

/*-------------------------------------------------------------------


RELEASE: 7.2

DATE: 12 APR 2013

HYPER: NO


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

DBXTRDV PERFORMANCE SLOWED

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

When processing extremely large input files, the CA Repository

Exchange for Teradata catsync program, DBXTRDV, will 'slow down'

appreciably. This is due to a loop which searches every column

in the input file.

SYMPTOMS:

Prior to the fix associated with XTD 41, the loop was limited

to 32,768 by a FB(15) counter. XTD 41 had to increase this

to FB(31) and with a large file (100K and up) the time

differential is substantial. A 200K file which used to take

2 hours became 8 hours with the XTD 41 fix.

IMPACT:

Ultimately the job runs with expected results (the output file,

return code and warning messages are the same), but the time

differential is unacceptable.

CIRCUMVENTION:

None.



-------------------------------------------------------------------*/.

++VER (Z038) FMID(COL7200)

PRE (RO50966)

SUP (T5QV915,RO57504,T5QV823).





DESC (COLUMN 'NEXTVAL' NOT FOUND)

/*-------------------------------------------------------------------


RELEASE: 7.2

DATE: 12 APR 2013

HYPER: NO


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

COLUMN 'NEXTVAL' NOT FOUND

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


word "NEXTVAL".




SYMPTOMS:


EXEC SQL

INSERT INTO UCPMC01T

( CUST_ID_NBR

,CUST_PRT_NBR

,UCPM_CASE_SEQ_NBR

)

VALUES

(:DCLUCPMC01T.CUST-ID-NBR

,:DCLUCPMC01T.CUST-PRT-NBR

,(SELECT NEXTVAL FOR UCPM_CASE_SEQ_NBR

FROM SYSIBM.SYSDUMMY1)

)

END-EXEC.

will get the message(s):

THE COLUMN "NEXTVAL" OF TABLE

"SYSIBM.SYSDUMMY1" WAS NOT FOUND.

THE COLUMN "UCPM_CASE_SEQ_NBR" OF TABLE

"SYSIBM.SYSDUMMY1" WAS NOT FOUND.

IMPACT:


"NEXTVAL" cannot be scanned into the Repository

if a RC=00 is a customer requirement.

CIRCUMVENTION:

None.



-------------------------------------------------------------------*/.


SUP (T5QV998,T5QV970,T5QV922,RO44941,T5QV590,T5QV576,

T5QV182,RO30379,T5QV106,RO26865,T5QV101,RO26994,

RO44218,RO50702,T5QV822,AR48152,RO48152,T5QV647,

RO55369,RO56794).





DESC (ENCODING(EBCDIC 500) BINDS)

/*-------------------------------------------------------------------


RELEASE: 7.2

DATE: 24 APR 2013

HYPER: NO


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

ENCODING(EBCDIC 500) BINDS

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

When using DB2 Version 8,9 or 10, the bind syntax generated out

of the Repository installation panel contains ENCODING(EBCDIC 500)

for every package.

SYMPTOMS:

When executed against DB2, the following warning is issued:

IKJ56716I EXTRANEOUS INFORMATION WAS IGNORED: 500

IMPACT:

The bind runs successfully using whatever the default for the site

happens to be.

CIRCUMVENTION

None.

PRODUCTS AFFECTED:

CA Repository for z/OS r7.2

-------------------------------------------------------------------*/.

++VER (Z038) FMID(CP$7200)

PRE (RO31041)

SUP (T54R023).





DESC (VIEW COLUMN RENAME WITHOUT AN "AS" KEYWORD)

/*-------------------------------------------------------------------


RELEASE: 7.2

DATE: 30 APR 2013

HYPER: NO


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

VIEW COLUMN RENAME WITHOUT AN "AS" KEYWORD

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

The COBOL scanner, MSCANDB2, does not recognize the rename of

a view or cursor column unless there is an AS keyword preceding

the new column name. Omitting the " AS " keyword results in a

"COLUMN NOT FOUND" warning message and a RC=04.

SYMPTOMS:


EXEC SQL

DECLARE CURSOR1 CURSOR FOR

SELECT A.CLM_TERMIN_RSN_CDE,

A.INSD_NM,

A.CUST_ID_NBR,

DESCRIPTION

SUM(B.CLM_BILL_DISB_AMT) SUM_DISB_AMT <<<<<<

FROM CLAIM01T A,

CDISB01T B

END-EXEC.


THE COLUMN "SUM_DISB_AMT " OF TABLE "PROD.CLAIM01T" WAS NOT FOUND.

Whereas the same DECLARE CURSOR1 using

SUM(B.CLM_BILL_DISB_AMT) AS SUM_DISB_AMT

will correctly define the cursor with a column called SUM_DISB_AMT.

IMPACT:

A COBOL program containing SQL which defines a new column name

without an "AS" keyword cannot be scanned into the Repository.

None.

CIRCUMVENTION:

None.



-------------------------------------------------------------------*/.


SUP (T54R016,T5QV182,RO30379,T5QV106,RO26865,T5QV101,

RO26994,T5QV576,RO44218,AR48152,T5QV590,RO44941,

RO48152,T5QV647,RO50702,T5QV822,T5QV922,RO55369,

T5QV970,RO56794,T5QV998,RO57536).




Release Service Details7.2 RO58507 RO58507 M.C.S. ENTRIES = ++APAR (RO58507)

DESC (COLUMN "POSITION" NOT FOUND)

/*-------------------------------------------------------------------


RELEASE: 7.2

DATE: 7 MAY 2013

HYPER: NO


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

COLUMN "POSITION" NOT FOUND

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


word "POSITION".

This results in a "COLUMN" not found error message and a RC=04

for the step when processing any COBOL program that contains

this particular reserved word.

SYMPTOMS:


EXEC SQL

DECLARE CURCLAIM CURSOR

FOR SELECT CLM_RPT_NBR,

CLM_NBR_ID_CODE,

CNTRCT_NBR,

CLM_TERMIN_RSN_CDE,

CUST_ID_NBR

FROM CLAIM01T

WHERE CUST_ID_NBR = :WS-CUST-ID-NBR

ORDER BY POSITION <<<<<<<<<<<<<<<

(CLM_NBR_ID_CODE,'MS LTCPW DI HC ',OCTETS),

CLM_RPT_NBR DESC,

CNTRCT_NBR ASC,

CLM_TERMIN_RSN_CDE ASC


THE COLUMN "POSITION" OF TABLE "<creator>.CLAIM01T" WAS NOT FOUND.

IMPACT:


"POSITION" cannot be scanned into the Repository because

the Repository is treating the reserved word as a DB2

column name and generating a warning message

"THE COLUMN "POSITION" OF TABLE "XXXXXXX.CLAIM01T"

WAS NOT FOUND."

CIRCUMVENTION:

None.



-------------------------------------------------------------------*/.


SUP (T54R029,T54R016,RO58240,T5QV106,RO26865,T5QV101,

RO26994,T5QV576,RO44218,AR48152,T5QV590,RO44941,


T5QV970,RO56794,T5QV998,RO57536,T5QV182,RO30379).





DESC (DBXCATA - DB2 V10 VIEW CATSYNC ERROR 0C4)

/*-------------------------------------------------------------------

PRODUCT: CA Repository Exchange for DB2

RELEASE: 7.2

DATE: 21 MAY 2013

HYPER: NO

STARTRAK PROBLEM PRODUCT NAME: XD2 PROBLEM NUMBER: 182

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

DBXCATA - DB2 V10 VIEW CATSYNC ERROR 0C4

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

Executing the CA Repository DB2 CATSYNC job may unsuccessfully end

during processing of VIEW(s).

SYMPTOMS:

The CATALOG step of the DB2 CATSYNC job abends with a 0C4 or U4038

condition code.

IMPACT:

The CA Repository DB2 CATSYNC job abends.

CIRCUMVENTION:

None


CA Repository Exchange for DB2 r7.2

-------------------------------------------------------------------*/.

++VER (Z038) FMID(CQH7200)

PRE (RO31042)

SUP (T54R014,RO56068,T5QV964).

++HOLD(RO59098) SYSTEM REASON(DB2BIND) FMID(CQH7200) COMMENT(


Sequence:

After Apply.

Purpose:

DB2 Bind

Relevance:

If you are applying the re-compiled module, you must bind the DBRM

into the DB2 subsystem.

Knowledge required:

Bind procedures on relevant DB2 subsys.

Access required:

Bind authority on relevant DB2 subsys



is complete, the following instructions should

be turned over to the DB2 DBA in charge of the

repository for customization to your site's

specific procedures.

Bind package DBXCATA with the following parameters:

DSN SYSTEM(subsys)

BIND PACKAGE(collection name) -

ENCODING(EBCDIC) -

ENABLE(*) -

PATH(repository qual)

QUALIFIER(SYSIBM) -

MEMBER(DBXCATA) -

LIBRARY(dbrmlib) -

VALIDATE(BIND) -

DYNAMICRULES(BIND) -

ISOLATION(CS) -

EXPLAIN(NO) -

FLAG(I) -

RELEASE(COMMIT) -

ACTION(REPLACE)

END

Make the following substitutions for the values of the

parameters so they conform to your site's environment.

- subsys to the db2 subsystem

- collection name to the repository package collection



Release Service Details- repository qual to the repository owner.

- dbrmlib to DBRM library that contains the DBRMs associated

with the PTFs that are applied.

).





DESC (PROGDEF - VERSIONS IN PART AND SPACE TBL)

/*-------------------------------------------------------------------


RELEASE: 7.2

DATE: 23 MAY 2013

HYPER: NO


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

PROGDEF - VERSIONS IN PART AND SPACE TBL

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

Executing the CA Repository DB2 CATSYNC job for existing PART KEY

may load PART KEY with multiple versions in the PART table and SPACE

table.

SYMPTOMS:

Existing instances of PART KEY relationships will be versioned

instead of being reused.

IMPACT:

Multiple versions creates inaccurate information and will adversely

effect impact analysis in the repository. In addition, this creates

unwanted meta-data.

CIRCUMVENTION:

Manually bind module PRMPT.


CA Repository Exchange for DB2 r7.2.

-------------------------------------------------------------------*/.

++VER (Z038) FMID(CP$7200)

PRE (RO31041)

SUP (T54R035,RO31179,T5QV118).





DESC (ERWINXML - ERWIN EXCHANGE FOR ERWIN R9)

/*-------------------------------------------------------------------


RELEASE: 7.2

DATE: 11 JUN 2013

HYPER: NO


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

ERWINXML - ERWIN EXCHANGE FOR ERWIN R9

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

ERwin r9 is now available and the ERwin Exchange must be modified

to support it, while keeping all previous functionality.

SYMPTOMS:

Customers who run the ERwin Scanner with previous control files

and an XML file from ERwin r9 will receive the following error:

'Versions of ERwin File and control file do not match'.

IMPACT:

No ERwin r9 XML files can be scanned.

CIRCUMVENTION:

None


CA Repository Exchange for CA ERwin Data Modeler r7.2

-------------------------------------------------------------------*/.

++VER (Z038) FMID(CP$7200)

PRE (RO43861)

SUP (T5QV949,RO45696,T5QV649).

++HOLD(RO59880) SYSTEM REASON(ACTION) FMID(CP$7200) COMMENT(


Sequence:

After Apply.

Purpose:

Upload updating Erwin control data into the Repository table.

Relevance:

If you are applying updating Erwin control data, you must upload it into

Repository DB2 control table.

Knowledge required:

Installation, customization and upgrading the RzOS 7.2.

Access required:

Repository administration authority is required.

Once the SMP/e portion of the fix application is complete, the following

instructions

need to be turned over to the DB2 DBA in charge of the repository for

customization to your site's specific procedures.

Follow the directions in the CA Repository for z/OS Installation Guide under

Load Component Data Tables in Chapter 6 " Configuring Your Product".

Set options as follows:

----------------------------- Load Component Data -----------------

COMMAND ===> Load Data For...

ERwin? ===> Y

Webstation Option? ===> N

Edit or Submit? ===> E (E-edit,S-submit)

Save Output? ===> N (Y-yes,N-no)

Output Data Set ===>

Warning!

If you are using the CA Repository Exchange for Erwin you will also need to

Install windows fix RO59877.

).





DESC (MAPS W/SPECIAL CHARACTERS CAUSE XSD FAILURE)

/*-------------------------------------------------------------------


RELEASE: 7.2

DATE: 12 JUN 2013

HYPER: NO


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

MAPS W/SPECIAL CHARACTERS CAUSE XSD FAILURE

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

MAP 103 (COLUMNS) has an alignment problem causing the

COLUMN NAME field to display on the previous

COLUMNS SET INFORMATION line.

In addition several MAPS are found to contain special

characters which prevent proper generation of the XSD file.

These character appear only in literals and can simply

be eliminated. The MAPS are: 00024, 26522, 26523, 27333.

SYMPTOMS:

The Map 103 alignment is merely an nuisance, the data show

on the wrong line but it is obvious where they belong.

Maps containing the special characters will get different

errors depending on the map. For example, Map 0024 will get:

"s4s-att-invalid-value: Invalid attribute value for 'name'

for 'name' in element'. Recorded reason:

cvc-datatype-valid.1.2.1:

'-------------------STORAGE_TABLE_INFORMATION----------'

IMPACT:

Customers cannot generate XSD for dialogs IEFALL, ERWIN2, EXTEND

which means they cannot use those dialogs in WSO.

CIRCUMVENTION:

NONE

PRODUCTS AFFECTED:

CA Repository for z/OS r7.2.

-------------------------------------------------------------------*/.

++VER (Z038) FMID(CP$7200)

PRE (RO26749)

SUP (T54R033,RO48184,T5QV644,RO25123,T5QV081).

++HOLD(T54R033) SYSTEM REASON(ACTION) FMID(CP$7200) COMMENT(


Sequence:

After Apply.

Purpose:

Load new IO MAP tables

Relevance:

The new map data are provided as members of the DATA dataset.

The relevant data must be loaded into the Repository IO MAP

control tables.

Knowledge required:

Install procedures for the repository.

Access required:

Load authority on relevant DB2 subsys



is complete, follow the directions in the

CA Repository for z/OS Installation Guide r7.2

under the 'Load the New Data' section, in

'Chapter 7: Migration Information'.

At the Installation Upgrade Customization Menu,

(Main Menu # 13)

Select option 5 LOAD and set options as follows:

Load control tables...

DIALOGs? ===> N CODE TABLEs? ===> N

ENTITYs? ===> N IO MAPs? ===> Y

MESSAGEs? ===> N COMMANDs? ===> N



Release Service DetailsSet SQLID to? ===>

Current Contents? ===> A (A-add,R-replace,P-new products)

Check the generated JCL according to your site's standard.

Leave only members provided by the solution.

When following those instructions the

custom data will be retained.

).





DESC (COLUMN 'NEXT' NOT FOUND)

/*-------------------------------------------------------------------


RELEASE: 7.2

DATE: 18 JUN 2013

HYPER: NO


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

COLUMN 'NEXT' NOT FOUND

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


word "NEXT VALUE".




SYMPTOMS:


EXEC SQL

EXEC SQL

SELECT NEXT VALUE FOR AGMT_ID_NBR

INTO :WS-AGMT-ID-NBR

FROM SYSIBM.SYSDUMMY1

END-EXEC.

will get the message(s):

THE COLUMN "NEXT " OF TABLE "SYSIBM.SYSDUMMY1" WAS NOT FOUND.

THE COLUMN "AGMT_ID_NBR " OF TABLE "SYSIBM.SYSDUMMY1" WAS NOT FOUND.

IMPACT:


"NEXT VALUE" cannot be scanned into the Repository.

CIRCUMVENTION:

None.



-------------------------------------------------------------------*/.


SUP (T54R058,T54R016,RO58240,T5QV106,RO26865,T5QV101,

RO26994,T5QV576,RO44218,AR48152,T5QV590,RO44941,


T5QV970,RO56794,T5QV998,RO57536,T5QV182,RO30379,

RO58507,T54R029).

Date post:	06-Dec-2018
Category:	Documents
Upload:	hoangthuan
View:	223 times
Download:	0 times

CA Repository for z/OS 7.2 CA RS 1309 Service List · CA Repository for z/OS 2 ... CA RS 1309...

Documents