Question about LSR
Zarzoza Espino, William
Hi Listers!
I have a doubt about how many records contain Cics in buffers, we have RLS files and I want to know what is the maximum quantity of records in buffers.
For example Vsam (LRECL=500, CISIZE=512) and LSR:
CEDA View Lsrpool( LSRPOOL1 )
Lsrpool : LSRPOOL1
Group : FCTSAF
DEscription :
Lsrpoolid : 1 1-8
Maxkeylength : 103 0-255
SHarelimit : 050 1-100
STrings : 050 1-255
DATA BUFFERS
DATA512 : 00040 3-32767
Does Buffer contain only WRITEd and REWRITEd records ?
Best regards,
William Zarzoza
Systems programmer
Interbank - Peru
Edward Addison
With a 500 byte record, one will fit in the 512 byte Control Interval with 2 bytes left over (500 bytes for the record, 4 bytes for the CIDF and six bytes for the 2 RDFs). If a READ is issued, the buffer will contain the READ record. The READ buffer will be stolen if it was a direct read ( no UPDATE) and all 40 of your buffers are already in use.
Edward Addison
CICS Level II Senior Software Engineer
(919) 254-6515 T/L 444-6515
You cannot solve the problem with the same kind of thinking that created the problem.
- Einstein
| "Zarzoza Espino, William"
<WZar...@INTERCORP.COM.PE>
Sent by: CICS List <CIC...@LISTSERV.UGA.EDU> 08/22/2005 04:08 PM
|
|
Eugene S. Hudders
Edward Addison
I thought there may have been a typo ... title is 'Question about LSR' and inside it says RLS. RLS buffers are kept and managed in the Coupling Facility by SMSVSAM. The LSR buffers are ignored until the dataset is quiesced and opened in NON-RLS mode.
Edward Addison
CICS Level II Senior Software Engineer
(919) 254-6515 T/L 444-6515
You cannot solve the problem with the same kind of thinking that created the problem.
- Einstein
| "Laughton, Mark"
<Mark.L...@UK.EXPERIAN.COM>
|
| Sent by: CICS List <CIC...@LISTSERV.UGA.EDU> |
08/23/2005 03:03 AM |
|
|
Guys
Maybe I'm being thick (or havent had enough coffee yet!) but surely if the files are RLS (as WiIliam says they are) the LSRPOOL buffers aren't used? Surely the buffers are in the associated Coupling Facility structure...?
Beginning to doubt myself, I checked in the Resource Definition Guide which says:
"By default, if the file definition specifies RLSACCESS(YES), the LSRPOOLID is ignored when CICS opens the file. "
Confused.
-----Original Message-----
From: Zarzoza Espino, William [mailto:WZar...@INTERCORP.COM.PE]
Sent: 22 August 2005 21:09
To: CIC...@LISTSERV.UGA.EDU
Subject: Question about LSR
Hi Listers!
I have a doubt about how many records contain Cics in buffers, we have RLS files and I want to know what is the maximum quantity of records in buffers.
For example Vsam (LRECL=500, CISIZE=512)
and LSR:
CEDA View Lsrpool( LSRPOOL1 )
Lsrpool : LSRPOOL1
Group : FCTSAF
DEscription :
Lsrpoolid : 1
1-8
Maxkeylength : 103
0-255
SHarelimit : 050
1-100
STrings : 050
1-255
DATA BUFFERS
DATA512 : 00040
3-32767
Does Buffer contain only WRITEd and REWRITEd records ?
Best regards,
William Zarzoza
Systems programmer
Interbank - Peru
Find out about The Experian Conference 2005 at www.experian.co.uk/conference2005
==========================================================================
Information in this e-mail and any attachments are confidential, and may not be copied or used by anyone other than the addressee, nor disclosed to any third party without our permission. There is no intention to create any legally binding contract or other binding commitment through the use of this electronic communication unless it is issued in accordance with the Experian Limited standard terms and conditions of purchase or other express written agreement between Experian Limited and the recipient Experian Limited (registration number 653331) Registered office: Talbot House, Talbot Street, Nottingham NG80 1TH
Although Experian has taken reasonable steps to ensure that this communication and any attachments are free from computer virus, you are advised to take your own steps to ensure that they are actually virus free.
Zarzoza Espino, William
William Zarzoza
Systems
programmer
Interbank - Peru
De: CICS List [mailto:CIC...@LISTSERV.UGA.EDU] En nombre de Laughton, Mark
Enviado el: Martes, 23 de Agosto de 2005 02:04 a.m.
Para: CIC...@LISTSERV.UGA.EDU
Asunto: Re: Question about LSR
Bob Juch
Bob Juch
CICS Central
http://www.CICSCentral.com
Bob Juch
William,
No, because as already discussed here, RLS files don't use LSR.
It's true for both.
Bob Juch
CICS
Central
http://www.CICSCentral.com
From: Zarzoza Espino, William [mailto:WZar...@intercorp.com.pe]
Sent: Wednesday, August 24, 2005 7:03 PM
To: b...@CICSCENTRAL.COM
Subject: RE: Question about LSR
William Zarzoza
Systems
programmer
Interbank - Peru
De: CICS List [mailto:CIC...@LISTSERV.UGA.EDU] En nombre de Bob Juch
Enviado el: Miércoles, 24 de Agosto de 2005 04:12 p.m.
GOODWIN, DIANE M.
I always thought that the VSAM control interval caused an issue in this scenario.
From a batch job, you won’t see the last interval written until CICS closes the file.
Am I thinking of something out??
Diane
**********************************************************
This email and any files transmitted with it are confidential and
intended
solely for the use of the individual or entity to whom they are
addressed.
If you have received this email in error please notify
postm...@amica.com
and the sender of the message. Thank you.
**********************************************************
Russ Evans
NOTE: the use of 4,4 raises SERIOUS performance and data integrity issues and
SHOULD NOT be implemented without serious research. But it does work.
Russ
Quoting Bob Horne <rho...@US.IBM.COM>:
> Diane,
> Bob is right that CICS does not do deferred writes. As a result, updates
> to VSAM CI's are written to DASD immediately. The problem is that until
> CICS closes the file, the VSAM catalog information is not updated. As a
> result, when the batch job opens the file, the batch job accesses the old
> catalog information. This may or may not cause problems for the batch job
> depending on a variety of other factors (i.e., the results are not
> predictable). The safest course of action would be to close the VSAM file.
>
>
> Bob Horne
> IBM Software Group/Tivoli
> Atlanta, GA
>
>
>
> "GOODWIN, DIANE M." <DGOO...@AMICA.COM>
> Sent by: CICS List <CIC...@LISTSERV.UGA.EDU>
> 08/25/2005 01:44 PM
> Please respond to
> CICS List
>
>
> To
> CIC...@LISTSERV.UGA.EDU
> cc
>
> Subject
> Re: Question about LSR
>
>
>
>
>
>
> I always thought that the VSAM control interval caused an issue in this
> scenario.
> From a batch job, you won?t see the last interval written until CICS
> closes the file.
> Am I thinking of something out??
>
>
>
> Diane
>
>
Bob Horne
Russ,
Yes, there would be perform issues with VSAM share option (4,4) because VSAM would always read the data from DASD. In addition there is still the issue of the catalog information not being updated. VSAM share option (4 , 4) would still have problems if the VSAM file needed to go into additional extents.
Bob Horne
IBM Software Group/Tivoli
| Russ Evans <russ...@CTEL.NET>
|
| Sent by: CICS List <CIC...@LISTSERV.UGA.EDU> |
08/25/2005 03:30 PM |
Zarzoza Espino, William
William Zarzoza
Systems
programmer
Interbank - Peru
De: CICS List [mailto:CIC...@LISTSERV.UGA.EDU] En nombre de Bob Horne
Enviado el: Jueves, 25 de Agosto de 2005 12:59 p.m.
Diane,
Bob is right that CICS does not do deferred writes. As a result, updates to VSAM CI's are written to DASD immediately. The problem is that until CICS closes the file, the VSAM catalog information is not updated. As a result, when the batch job opens the file, the batch job accesses the old catalog information. This may or may not cause problems for the batch job depending on a variety of other factors (i.e., the results are not predictable). The safest course of action would be to close the VSAM file.
Bob Horne
IBM Software Group/Tivoli
Atlanta, GA
| "GOODWIN, DIANE M."
<DGOO...@AMICA.COM> Sent by: CICS List <CIC...@LISTSERV.UGA.EDU> 08/25/2005 01:44 PM
|
|
I always thought that the VSAM control interval caused an issue in this scenario.
Diane
Best regards,
==========================================================================
Chase, John
> From: CICS List On Behalf Of Bob Horne
>
> Russ,
> Yes, there would be perform issues with VSAM share option
> (4,4) because VSAM would always read the data from DASD. In
> addition there is still the issue of the catalog information
> not being updated. VSAM share option (4 , 4) would still have
> problems if the VSAM file needed to go into additional extents.
VSAM Shr(4,4) also precludes taking a CA split (maybe CI split; maybe
both?). BTDTGTS.
-jc-
Jangula, Duane A.
Region and also in an Adabas RPC server region with share options of 3,3.
The Rpc server would not read all the records that were updated from the
cics region. To solve that we defined the vsam files with shareoptions 4,4
and we no longer had any problems.
One of the posts that I saw suggested that there would still be problems
with NOT being able to read all records from the file and especially those
with very recent updates. I don't know about the catalog update process,
but I do know that having the shareoptions 4,4 will allow any batch job or
any other task to have access to all records on the vsam file; and even
those with very recents additions.
Duane Jangula
-----Original Message-----
From: CICS List [mailto:CIC...@VM.MARIST.EDU] On Behalf Of Bob Horne
Sent: Thursday, August 25, 2005 6:34 PM
To: CIC...@VM.MARIST.EDU
Subject: Re: Question about LSR
William,
Yes, depending on a variety of factors the batch job could potentially not
read some records. It depends on factors such as how the batch job is
reading the file, how CICS updated the file, whether the file may have
gone into additional extents, etc.
As for the problem with the two CICS regions, if you define the file as
remote in CICS2, then your file requests will be function-shipped to CICS1
and the file read is actually performed in CICS1. So, there would not be
any problem with the data being read from a buffer in the LSR pool in
CICS1.
Bob Horne
IBM Software Group/Tivoli
Atlanta, GA 30327
"Zarzoza Espino, William" <WZar...@INTERCORP.COM.PE>
Sent by: CICS List <CIC...@LISTSERV.UGA.EDU>
08/25/2005 05:10 PM
Please respond to
CICS List
Subject
Re: Question about LSR
Bob:
Then my batch job does not read some records because VSAM catalog
information is not updated while Cics has open the file?
Similar case I have between 2 Cics, Cics1 has defined a file with all the
attibutes and Cics2 have it defined with read and browse attributes.
Sometimes Cics2 does not read last updates executed by Cics1. For this
case, my solution is define the file in Cics2 like remote. But, the
problem is that last updates are in Cics1's buffers?
Best regards,
William Zarzoza
Systems programmer
Interbank - Peru
From a batch job, you won?t see the last interval written until CICS
closes the file.
Am I thinking of something out??
Diane
From: CICS List [mailto:CIC...@LISTSERV.UGA.EDU] On Behalf Of Bob Juch
Sent: Wednesday, August 24, 2005 5:12 PM
To: CIC...@LISTSERV.UGA.EDU
Subject: Re: Question about LSR
William,
A batch job WILL read everything in a file that was written to by CICS.
Writes are done immediately. No written records are in LSR.
Bob Juch
CICS Central
http://www.CICSCentral.com
-----Original Message-----
From: CICS List [mailto:CIC...@LISTSERV.UGA.EDU] On Behalf Of Zarzoza
Espino, William
Sent: Wednesday, August 24, 2005 5:03 PM
To: CIC...@LISTSERV.UGA.EDU
Subject: Re: [CICS-L] Question about LSR
Thanks for the responses.
My problem is when a job batch reads a non-RLS CICS file, everything does
not read it, because some records are in buffers. The solution is close
the file and read it.
But between the Close command and Cics responds, there are miliseconds in
which some transactions could execute and find the file BEING DISABLED
status.
An idea about this is WRITE "n" records via EXCI, and later read and
process the data.
My questions is, how many records should write in order to assure that
they do not remain records in buffers (with the attached data previously).
Do you know another alternative?
Thanks in advance.
Best regards,
William Zarzoza
Systems programmer
Interbank - Peru
Confused.
**********************************************************