LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (February 2006)Back to main CICS-L pageJoin or leave CICS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Wed, 1 Feb 2006 17:28:36 -0500
Reply-To:     CICS List <CICS-L@LISTSERV.UGA.EDU>
Sender:       CICS List <CICS-L@LISTSERV.UGA.EDU>
From:         "Farley, Peter x23353" <Peter_Farley@ADP.COM>
Subject:      Re: Asynchronous CICS READ API (or SPI)?
Content-Type: text/plain; charset="Windows-1252"

OK, a little more outside thinking then -- Don't know how large your file is, but I have, in the past, used BLSR in long-running batch jobs to pre-stage entire VSAM files, by specifying enough buffer storage to hold the entire file in memory at once. Obviously, if your file(s) are bigger than 2G this isn't an option (plus we are talking CICS and not batch, but the principle applies nonetheless). How about bumping the LSR pool *WAY* up there, with a unique pool number for your files so no one else interferes with your buffers? Then even without "prestaging", when buffers are read/written they are more likely to still be there the next time around.

Obviously also depends on how critical your appl. is WRT others in the region and the LPAR.

Good luck.

Peter

-----Original Message----- From: CICS List [mailto:Tom.Schmidt@OASSOFTWARE.COM] Sent: Wednesday, February 01, 2006 5:19 PM To: CICS-L@LISTSERV.UGA.EDU Subject: Re: Asynchronous CICS READ API (or SPI)?

Peter, That would probably be overkill for what I'd like to accomplish (but thank you for thinking outside of the box).

I have code in the XFCFROUT GLUE routine that is looking at keys (not data - too sensitive and not necessary); I've noticed that, for several given transactions, the keys used for various files tend to be remarkably similar. In fact, they are predictably similar... which led me to the idea (if I was sufficiently clever - and had an API/SPI to do it with) that I might be able to prestage the downstream file CIs once I've seen the hint at the beginning of the transaction.

Dumb as that sounds (hey, I know) it may still have merit. John's idea of a lightweight program passed the FCT & key as a small STARTed transaction might be useful for the cases where the transaction is monitored in "region A" but the file is owned by "region B"; I might ship a transaction from A to B with the intent of letting B's QR TCB get busy early.

What I would really like would be to have an API to drive the prestaging I/O via the CO TCB (to get some parallelism going). And CICS doesn't seem to have that.

-- Tom Schmidt Madison, WI

On Wed, 1 Feb 2006 15:11:35 -0500, Farley, Peter x23353 wrote: > >Just an off-the-wall idea -- Would STARTBROWSE/ENDBROWSE fill the bill? >I don't know BROWSE internals, is there an actual internal read issued >at STARTBROWSE, before the first READNEXT? > >Peter

_ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.


Back to: Top of message | Previous page | Main CICS-L page