If your interest is sharing, CICS can store a complete vsam file in dataspace using a standard IO routines (GET, PUT, POINT etc.). It is few CICS parameters away and involves no code change. I am not sure that EXCI will save you CPU or elapse. BTW, there are few products that store data in storage and/or dataspaces (Matrix from Expanse comes to mind). Another alternative is to store the dataset in a common area (nay be above the bar), and store the start and end addresses in single name-token pair. you just need a loaded program and a search one. this fits for a none updated file.
HTH ITschak On Thu, Mar 23, 2017 at 5:52 PM, Victor Gil <victor....@broadridge.com> wrote: > A co-worker suggested to save CPU by having one job to cache a VSAM file > [which is frequently looked up by multiple jobs] and introduce a new "look > up" API to "connect" to that job and locate a particular record with a > given key. > > I am a bit outdated in current systems services, so my first suggestion > was to use EXCI into a CICS region or call a DB2 stored procedure which > would act as a "server", but the question is - is there an easier way to > accomplish this in pure batch? I am familiar with the cross-memory access > but this would require heavy assembler coding, APF authorization, etc. all > of which we are trying to avoid. > > TIA! > -Victor- > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- ITschak Mugzach *|** IronSphere Platform* *|** An IT GRC for Legacy systems* *| Automated Security Readiness Reviews (SRR) **|* ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
