|
View previous topic :: View next topic
|
| Author |
Message |
mots
New User
.jpg)
Joined: 16 May 2007
Posts: 6
Location: Pune
|
|
|
|
Hello,
I'm executing an Online program whose function is to write the records into an ESDS VSAM file after completion of program execution I’m expecting the records should get written into the VSAM file but when I open the VSAM file using TSO File aid option I’m unable to see the records entry into an VSAM file. I closed the online VSAM file and then only I was able to see the records entry in a file.
Could you please suggest why this is happing? What I need to do to see the records entry without closing the VSAM file.
I have defined the VSAM File with below shown options.
DEFINE CLUSTER -
(NAME (NAVUAT.VBCCF.CFD02D6)
VOLUMES (M2VA02) -
RECORDSIZE (750 750) -
CYLINDERS (10 10) -
SHAREOPTIONS (2 3) -
SPEED -
-
NONINDEXED -
) -
DATA -
(NAME (NAVUAT.VBCCF.CFD02D6.DATA) -
CONTROLINTERVALSIZE(1024) -
)
Thank You,
Mots |
|
| Back to top |
|
 |
Rajesh Midde99
New User
.jpg)
Joined: 04 Dec 2008
Posts: 11
Location: Bangalore,India
|
|
|
|
Hi
The answer is in your question
| Quote: |
when I open the VSAM file using TSO File aid option I’m unable to see the records entry into an VSAM file. I closed the online VSAM file and then only I was able to see the records entry in a file.
|
When you are opening the VSAM file in TSO with out giving CLOSE disable in CICS, It gives you the previous status of records held on that ESDS file.
Which means, it doesn't gets updated. When you close it, by Exclusive CLOSE command, the file gets closed and will able to give you the updations made. I can't give you more info regarding the storages and what happens internally.
Correct me, If I am wrong and Please let me know how the internal process works in this case?
Regards
Rajesh |
|
| Back to top |
|
|
mots
New User
Joined: 16 May 2007
Posts: 6
Location: Pune
|
|
|
|
| I suppose looking at this process the Records data is get stored in Buffer and after closing the file it get released to file and then only the records are get populated. but i have other file KSDS it shows me the records just after complition of the program execution. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| Is the VSAM file in a CICS LSR pool? This can affect when the buffers are flushed to disk. The problem symptoms you're describing are classic buffer issues -- sometimes CICS requires the file to be closed before it will write the buffers to disk, and until the buffers are written to disk no batch program is going to see the latest CICS additions. |
|
| Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
IFIRC, CICS loads the VSAM catalog info on file open and it is not updated until the VSAM file is closed in CICS. Thus, TSO sees the file as it was when CICS opened it.
Garry. |
|
| Back to top |
|
|
Earl Haigh
Active User
Joined: 25 Jul 2006
Posts: 475
|
|
|
|
| Quote: |
| Could you please suggest why this is happing? What I need to do to see the records entry without closing the VSAM file. |
ESDS Vsam files need to be closed before trying to view from another
region. You can not view ALL the records without first closing the
ESDS file. thats the way it works  |
|
| Back to top |
|
|
mots
New User
Joined: 16 May 2007
Posts: 6
Location: Pune
|
|
|
|
Hi Earl Haigh,
Can you clarify me is it a case only with VSAM ESDS file or all type of VSAM files (i.e.KSDS, RRDS). Since I have a another KSDS file and there I'm able to see the records after completion of PGM execution and without closing the KSDS file. |
|
| Back to top |
|
|
Earl Haigh
Active User
Joined: 25 Jul 2006
Posts: 475
|
|
|
|
| ESDS only .. |
|
| Back to top |
|
|
sdsinfo
New User
Joined: 14 Jan 2008
Posts: 10
Location: bangalore
|
|
|
|
Hi,
this is the case with all the vsam files.
u can not open a file which is already opened. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| Quote: |
this is the case with all the vsam files.
u can not open a file which is already opened.
|
Sorry -- WRONG! Check out what SHAREOPTIONS are used for and specifically what (2,3) means. As long as a VSAM file is being used for reading only, and has the SHAREOPTIONS set correctly, any number of processes can open that file simultaneously. |
|
| Back to top |
|
|
|
|
