IBM Mainframe Forum

that's my jcl to create AIX ,and I'm sure that was successfully executed ...
'P390.BOOK.KSDS' has been defined as file(book) in cics ,when I want to open the file again ,I failed ,why?????

Hello,

'P390.BOOK.KSDS' has been defined as file(book) in cics ,when I want to open the file again ,I failed ,why?????

What is a "file(book)" to you?. Again? Does this mean you successfully opened this file one time? How did you open this file?

that's my jcl to create AIX ,and I'm sure that was successfully executed ...

You need to post the outputs from all of the runs that were successful and the error that is happening when you try to open this file.

dick scherrer wrote:Hello,

What is a "file(book)" to you?. Again? Does this mean you successfully opened this file one time? How did you open this file? ...

ceda define file(book) dsname('p390.book.ksds') group(XXXX)
and I have used file(book) serval times in a transation to read and write records

You need to post the outputs from all of the runs that were successful and the error that is happening when you try to open this file

before I read file in transation ,I must set the file opened

and
before I create AIX on p390.book.ksds ,I must set it closed

but after I create an AIX ,I cannot set file(book) opened

Hello,

but after I create an AIX ,I cannot set file(book) opened

Why not - what error prevents the open?

What happens if you combine the CREATEs into one run and then repro some data into the file?

It may help if you post the complete output from the IDCAMS.

Did you define the path in CICS?

OBJECT CHARACTERISTICS CICS RELEASE = 0640
CEDA View File( V100TB1 )
File : V100TB1
Group : FCTT2
DEScription :
VSAM PARAMETERS
DSNAme : TBASLO.DBT2.V100TB1.PERM.PATH
Password : PASSWORD NOT SPECIFIED
RLsaccess : No Yes ! No
LSrpoolid : 1 1-8 ! None
READInteg : Uncommitted Uncommitted ! Consistent ! Repeatable
DSNSharing : Allreqs Allreqs ! Modifyreqs
STRings : 002 1-255
Nsrgroup :
REMOTE ATTRIBUTES
REMOTESystem :
REMOTEName :
REMOTE AND CFDATATABLE PARAMETERS
+ RECORDSize : 1-32767

Your subject "cannot open KSDS" is totally wrong and misleading. You cannot open the alternate index -- which is defined as a separate VSAM file and RELATEd to the base cluster. If you have not defined an entry in CEDA for the alternate index, you cannot use it in a CICS region -- just like for any other VSAM file.

Robert, not necessarily. When you try to open a KSDS that has an alternate index with upgrade then you have to have the definitions for the path available too, otherwise when you update the KSDS the AIX can not be updated correspondingly. I asume that is the case here.

From the second post the o/p made:

ceda define file(book) dsname('p390.book.ksds') group(XXXX)
and I have used file(book) serval times in a transation to read and write records

The KSDS worked fine -- it is the alternate index that couldn't be accessed.