It is defined shareoption 4 4 and was open to 5 CICSs. I have
closed it in each.
Any clues as to how I might find where it thinks it is open?
--
Mit freundlichen Gruessen,
Steve Weifenbach -- steve dot weifenbach at hanesfinishing dot com
"If it's true that we are here to help others, then what exactly
are the others here for?" -- unknown origin
Kevin P Corkery
Independent Consultant
Voorhees, New Jersey
Wandschneider, Scott wrote:
>Are any alternate indexes still open?
>
>
>Thanks,
>Scott
>
>
>
>
--
Kevin P Corkery
Independent Consultant
Voorhees, New Jersey
-----Original Message-----
From: owner...@Lehigh.EDU [mailto:owner...@Lehigh.EDU] On Behalf Of
Ron Ashley
Sent: Friday, October 29, 2004 2:44 PM
To: VSE Discussion List
Subject: RE: VSAM file IDC3028I Data Set in use
I see nothing here.
We also use BSI TCP-ip and do not have any files defined for FTP.
Thanks,
Scott
email: scott.wan...@i-structure.com
-----Original Message-----
From: owner...@Lehigh.EDU [mailto:owner...@Lehigh.EDU] On Behalf
Of Steve
Sent: Friday, October 29, 2004 1:42 PM
To: VSE Discussion List
Subject: Re: VSAM file IDC3028I Data Set in use
No. It is a straight RRDS file without any indexes.
Wandschneider, Scott wrote:
>Are any alternate indexes still open?
>
>
>Thanks,
>Scott
>
>
>
>
--
Wandschneider, Scott wrote:
>Do you have more than one VSE with MasterCat? MCAT in VSE1 can have a
>file open and a del/def in VSE2 will fail.
>
>
>
>
But this error message occurred before I went into mastercat
to see and I only looked at the CAT-INFO. It was not
access for records by mastercat.
Could that still be the issue?
Rbo...@aol.com wrote:
>Why do I get the feeling that CA-Mastercat has it open.
>
>
>
>
Of course I don't know for sure, but one way to find out is to shutdown Mastercat, although that may or may not fix it.
The explain for IDC3028I says there is a secondary message that provides
further information. Are you getting that in MCAT?
Also, could having the dataset defined in either standard or partition
user labels be causing this? I know for a fact that it will for a
catalog, because that bit me a couple of weekends ago while migrating a
catalog. I had to delete the label from standard labels before I could
purge the catalog and redefine it.
Steve wrote:
--
Michael Rosinger
Systems Programmer/DBA
Computer Credit, Inc.
640 W. 4th Street
Winston-Salem, NC 27101
voice : 336-761-1524
fax : 336-761-8852
email : mrosinger at cciws dot com
Rbo...@aol.com wrote:
><<Could that still be the issue?>>
>
>Of course I don't know for sure, but one way to find out is to shutdown Mastercat, although that may or may not fix it.
>
>
>
>
I tried to do this this morning after we IPL yesterday with the same
result. I should have tried
it immediately after IPL to assure that no intermediate was
interfering. Now I can't be sure.
This is the output I get from IDCAMS:
IDC3028I DATA SET IN USE
IDC3009I ** VSAM CATALOG RETURN CODE IS 184 - REASON CODE IS IGG0CLCX-4
IDC0551I **ENTRY CSS75.LISTING.FILE NOT DELETED
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8
I tried to do this this morning after we IPL yesterday with the same
result. I should have tried it immediately after IPL to assure that
no intermediate was interfering. Now I can't be sure.
When I have had this occur, I found out something interesting:
While I could not delete the file, I was able to use the IDCAMS ALTER command to change the name of the Data and Index (if Keyed) component(s), and, if I remember correctly, the Cluster as well. Then, I was able to redefine the Production file, and I deleted the 'renamed' one at a later time, once it was no longer in use.
I have had this occur three times over the years, and was never able to pin down 'who' was using the file.
If you have any Performance Monitoring tools, such as Explore/VSE, and have it monitoring VSAM Files and Catalogs, that product may have the catalog open, too. So, it may not be MCAT.
Good luck,
Dave
Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura
805-662-6731
David....@mail.co.ventura.ca.us
>>> steve.we...@hanesfinishing.com 11/1/2004 8:43:01 AM >>>
Glenn Powers
Systems Software Specialist
Harte-Hanks
Steve
<steve.weifenbach@hanesfin To: "VSE Discussion List" <vs...@Lehigh.EDU>
ishing.com> cc:
Sent by: Subject: Re: VSAM file IDC3028I Data Set in use
owner...@Lehigh.EDU
11/01/2004 10:48 AM
Please respond to vse-l
I'll try this again, hopefully with better formatting.
This is the output I get from IDCAMS:
-----Original Message-----
From: owner...@Lehigh.EDU [mailto:owner...@Lehigh.EDU]On Behalf Of
David Stuart
Sent: Monday, November 01, 2004 10:52 AM
To: VSE Discussion List
Subject: Re: VSAM file IDC3028I Data Set in use
Steve,
When I have had this occur, I found out something interesting:
While I could not delete the file, I was able to use the IDCAMS ALTER command to change the name of the Data and Index (if Keyed) component(s), and, if I remember correctly, the Cluster as well. Then, I was able to redefine the Production file, and I deleted the 'renamed' one at a later time, once it was no longer in use.
I have had this occur three times over the years, and was never able to pin down 'who' was using the file.
If you have any Performance Monitoring tools, such as Explore/VSE, and have it monitoring VSAM Files and Catalogs, that product may have the catalog open, too. So, it may not be MCAT.
Good luck,
Dave
Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura
805-662-6731
David....@mail.co.ventura.ca.us
>>> steve.we...@hanesfinishing.com 11/1/2004 8:43:01 AM >>>
I was wondering about this "OPEN" bit. Would you mind pointing the way?
Robert Payne wrote:
>This can also occur if an AIX is open somewhere. A few times over
>the years, I've encountered this after some unknown ugly event
>that nobody noticed and the "OPEN" bit in the catalog record was
>left on. We use a homegrown utility program to reset the bit.
>just FYI,
>Bubba
>
>
--
55 CEMT S DA(SLSF001) CLO
C2 0055
C2 0055 Dat(SLSF001 ) Vsa Clo Une Rea Bro
C2 0055 RESPONSE: NORMAL TIME: 11.32.53 DATE: 11.01.04
C2 0055 APPLID=CICSHDF1
C2-0055
56 CEMT S DA(SLSF001) CLO
C3 0056
C3 0056 Dat(SLSF001 ) Vsa Clo Une Rea Bro
C3 0056 RESPONSE: NORMAL TIME: 11.33.02 DATE: 11.01.04
C3 0056 APPLID=CICSHID1
C3-0056
57 CEMT S DA(SLSF001) CLO
C4 0057
C4 0057 Dat(SLSF001 ) Vsa Clo Une Rea Bro
C4 0057 RESPONSE: NORMAL TIME: 11.33.07 DATE: 11.01.04
C4 0057 APPLID=CICSDEVP
C4-0057
58 CEMT S DA(SLSF001) CLO
C5 0058
C5 0058 Dat(SLSF001 ) Vsa Clo Une Rea Bro
C5 0058 RESPONSE: NORMAL TIME: 16.33.13 DATE: 11.01.04
C5 0058 APPLID=CICSHID2
C5-0058
59 CEMT S DA(SLSF001) CLO
C6 0059
C6 0059 Dat(SLSF001 ) Vsa Clo Une Rea Bro
C6 0059 RESPONSE: NORMAL TIME: 11.33.18 DATE: 11.01.04
C6 0059 APPLID=CICSHID3
C6-0059
Glenn_...@harte-hanks.com wrote:
>Steve
> In CICS's does it show Closed Enabled or Closed Disabled?
>
>Glenn Powers
>Systems Software Specialist
>Harte-Hanks
>
>
David Stuart wrote:
>Steve,
>
>When I have had this occur, I found out something interesting:
>
>While I could not delete the file, I was able to use the IDCAMS ALTER command to change the name of the Data and Index (if Keyed) component(s), and, if I remember correctly, the Cluster as well. Then, I was able to redefine the Production file, and I deleted the 'renamed' one at a later time, once it was no longer in use.
>
>I have had this occur three times over the years, and was never able to pin down 'who' was using the file.
>
>If you have any Performance Monitoring tools, such as Explore/VSE, and have it monitoring VSAM Files and Catalogs, that product may have the catalog open, too. So, it may not be MCAT.
>
>
>
If you have a task in CICS that has the file still open, you can do a
forceclose the task will abend.
Glenn Powers
Systems Software Specialist
Harte-Hanks
Steve
<steve.weifenbach@hanesfin To: "VSE Discussion List" <vs...@Lehigh.EDU>
ishing.com> cc:
Sent by: Subject: Re: VSAM file IDC3028I Data Set in use
owner...@Lehigh.EDU
11/01/2004 11:07 AM
Please respond to vse-l
Glenn_...@harte-hanks.com wrote:
Glenn_...@harte-hanks.com wrote:
>Make the files CLO DIS the disable will close the ACB in CICS so you can
>delete, and redefine the file.
>
>If you have a task in CICS that has the file still open, you can do a
>forceclose the task will abend.
>
>
>
-----Original Message-----
From: owner...@Lehigh.EDU [mailto:owner...@Lehigh.EDU] On Behalf
Of Steve
Sent: Monday, November 01, 2004 12:58 PM
To: VSE Discussion List
Subject: Re: VSAM file IDC3028I Data Set in use
Glenn_...@harte-hanks.com wrote:
--
Mit freundlichen Gruessen,
Confidentiality Warning: This e-mail contains information intended only for the use of the individual or entity named above. If the reader of this e-mail is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, any dissemination, publication or copying of this e-mail is strictly prohibited. The sender does not accept any responsibility for any loss, disruption or damage to your data or computer system that may occur while using data contained in, or transmitted with, this e-mail. If you have received this e-mail in error, please immediately notify us by return e-mail. Thank you.
-----Original Message-----
From: owner...@Lehigh.EDU [mailto:owner...@Lehigh.EDU]On Behalf Of
Steve
Sent: Monday, November 01, 2004 11:09 AM
To: VSE Discussion List
Subject: Re: VSAM file IDC3028I Data Set in use
Hey, Bubba
I was wondering about this "OPEN" bit. Would you mind pointing the way?
Robert Payne wrote:
>This can also occur if an AIX is open somewhere. A few times over
>the years, I've encountered this after some unknown ugly event
>that nobody noticed and the "OPEN" bit in the catalog record was
>left on. We use a homegrown utility program to reset the bit.
>just FYI,
>Bubba
>
>
--
Thanks for all the help.
Thanks, anyway.
5.5.4 Data and Index Catalog Record
Data and Index records describe data sets and their indexes. Figure 5-15
shows the format of the data and index records.
??????????????????????????????????????????????????????????????????????????
Offset Bytes and
Dec Hex Bit Pattern Field Name Description
????????????????????????????????????????????????????????????????????????
0 0 44 Key and ID area
0 0 1 Binary zeros
1 1 3 ENTIDNO Control interval number of entry
4 4 1 RELIND Release indicator;
X'00' This record was created
with a DOS/VS Release prior to
Release 31.
X'01' this record was created
with DOS/VS Release 31 or later.
5 5 6 CRAVOL CRA volume serial number
11 B 3 CRAIDNO CRA control interval number
14 E 4 CRADEVT CRA device type
18 12 26 Binary zeros
44 2C 1 ENTYPE Record type- 'D' for a data re-
cord or 'I' for an index record.
45 2D 2 Record length
47 2F 1 Number of variable-length
fields that precede the pointer
to an Extension record.
Always zero.
48 30 1 Length of the fixed-length
fields in this record, exclud-
ing any fixed-length fields
following displacement 142 (8E).
This value is always equal
to the displacement from the
beginning of the record to the
pointer to an Extension record.
49 31 44 ENTNAME For a Data or Index record, the
data-set name
93 5D 8 OWNERID Owner of the data set,
specified when the data set
was defined.
101 65 3 DSETCRDT Data-set creation data, in
packed-decimal form YDD,
specified when the data set
was defined.
104 68 3 DSETEXDT Data-set expiration date, in
packed-decimal form YDD,
specified when the data set
was defined.
Offset Bytes and
Dec Hex Bit Pattern Field Name Description
????????????????????????????????????????????????????????????????????????
107 6B 1 ATTR1 Data-set attributes, which are
defined in Access Method
Services commands, as follows:
1... .... Speed-recovery features will
be minimized or omitted in
order to optimize operating
speed during initial loading
.1.. .... Unique component. Entire space
occupied by a unique component
..1. .... Reusable data set
...1 .... Erase the component upon
deletion.
.... 1... Recoverable catalog
.... .1.. Inhibit update
.... ..1. This component has been
temporarily exported
.... ...x Reserved for OS/VS MVM
108 6C 1 ATTR2 Data-set sharing attributes
as follows:
Cross-partition sharing:
00.. .... The data set can be shared by
READ users or it can be used
by one UPDATE/OUTPUT user.
01.. .... The data set can be shared by
READ users and one UPDATE/OUT-
PUT user.
10.. .... The data set can be fully
shared
11.. .... The data set can be fully
shared; with assistance
supplied by VSAM.
Cross-system sharing (set by
DOS but used only by OS):
..00 .... The data set can be shared by
READ users or it can be used
by one UPDATE/OUTPUT user.
..01 .... The data set can be shared by
READ user and one UPDATE/OUT-
PUT user.
..10 .... The data set can be fully
shared
..11 .... The data set can be fully
shared; with assistance
supplied by VSAM.
.... 1... NOALLOCATION cluster
.... ...1 DS not usable
.... .xx. Reserved
109 6D 1 OPENIND Open indicator flag; if this <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
byte contains X'80', the data <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
set is open for output. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
110 6E 4 BUFSIZE Minimum buffer size
Offset Bytes and
Dec Hex Bit Pattern Field Name Description
????????????????????????????????????????????????????????????????????????
114 72 3 PRIMSPAC Primary space allocated for
the data set or index, speci-
fied when the data set or
index was defined.
117 75 3 SCONSPAC Secondary space allocation for
the data set or index, speci-
fied when the data set or
index was defined.
120 78 1 SPACOPTN Space options flags.
10.. .... Track request, which indicates
that space was allocated in
terms of tracks.
11.. .... Cylinder request, which indi-
cates that space was allocated
in terms of cylinders.
...0 .... Secondary allocation class same
as primary allocation class.
Cluster, AIX)
...1 .... Use class-0 for secondary
allocation
.... .000 Data set in class-0 space.
.... .001 Data set in class-1 space.
.... .010 Data set in class-2 space.
.... .011 Data set in class-3 space.
.... .100 Data set in class-4 space.
.... .101 Data set in class-5 space.
.... .110 Data set in class-6 space.
.... .111 Data set in class-7 space.
..x. x... Reserved
121 79 4 HURBADS High used RBA of the data set
or index.
125 7D 4 HARBADS High allocated RBA of the data
set or index.
129 81 4 LRECL For a Data record, the logical
record size of the data set
described by this Data record.
For an Index record,
always X'FF's.
133 85 2 USERINFO User information for the ISAM
interface program (IIP).
135 87 8 EXCPEXIT Exception exit
The following six-byte entry contains control information for the group
occurrence pointers that follow it.(1)
143 8F 5 Pointer to Extension record.
If this record is not continued
in an Extension record, this
field contains zeros.
148 94 1 The number of group occurrence
pointers that follow.(1)
(1) For further information see section Group occurrences in catalog records.
Offset Bytes and
Dec Hex Bit Pattern Field Name Description
????????????????????????????????????????????????????????????????????????
Group occurrence pointer (repetitive)
Bits 0 and 1 of Byte 3 identify the group occurrence further:
00xx xxxx Pointer to a group occurrence
within the record
Byte Meaning
0 Reserved
1-2 Displacement of the
group occurrence from
the beginning of all
group occurrences in
this record.
3 Bits 0 and 1 are set
to zero. Bits 2 through
7 contain a code
that describes the
group occurrence
pointed to.
4 Sequence number of the
group occurrence
pointed to.
10xx xxxx Pointer to a group occurrence
contained in an Extension
record.
Byte Meaning
0-2 Control-interval number
of the Extension record
that contains this
group occurrence.
3 Bits 0 and 1 are set to
1 and 0, respectively.
Bits 2 through 7
contain a code that
describes the group
occurrence pointed to.
4 Sequence number of the
group occurrence pointed
to by code.
x1xx xxxx Pointer to a group occurrence
which has been deleted.
The code in bits 2
through 7 of byte 3 and
the sequence number in
byte 4 have been re-
tained however.
??????????????????????????????????????????????????????????????????????????
Figure 5-15. Data and Index Catalog Record Format
Robert Payne wrote:
>Steve, just sent the EZT+ source code snip to you direct. If you don't
>have EZT+ then maybe the logic will help you do it with another language.
>Lotsa Luck :)
>Bubba
>
>
>
>
--
-----Original Message-----
From: owner...@Lehigh.EDU [mailto:owner...@Lehigh.EDU]On Behalf Of
Steve
Sent: Monday, November 01, 2004 12:48 PM
To: VSE Discussion List
Subject: Re: VSAM file IDC3028I Data Set in use
Robert Payne wrote:
>Steve, something I forget to mention is that you have to reset the
>bit on both INDEX and DATA type records (assuming it's KSDS). Look
>at the program that I sent, it refers to a specific file with the
>names hard coded for each component. It has been about 3 years since
>I've had to run that utility, so it hasn't happened very often and
>the last time was in a shared user catalog with a SHR(4) KSDS.
>:)
>Bubba
>
>
As suggested, I made a new file, changed CICS
jcl and cycled the CICS as scheduled. Poof!
The original file is no longer "in use" and
I have successfully redefined it (as a test).
Thanks for all your pointers. I am stumped
on the why, but the problem has gone away.