As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
We have a Mainframe application that data is in files that are compressed. Several years ago there was an attempt to use the adapters from IBI to access these files but the attempt failed. The problem seemed to be that the data is in a proprietary compression.
Is there anybody that has had success in accessing files like these?
Thanks DanThis message has been edited. Last edited by: moyer1dl,
Thats a good question. I had the understanding that cobol had no problem accessing these files.
Although, the Mainframe programmers say that there are tools from the company that made the application to access these compressed files. I am not sure if they are used for COBOL to access them.
I am sure that you can find (or ask for) the routines that access the files. Then you should be able to have an idea of how the files are structured: simple sequential, hierarchy sequential, direct access in some form, etc.
With this data it should be possible (maybe not easy) to create your own interface to run these routines, what is called a "private interface". We have done this often in the past.
Daniel In Focus since 1982 wf 8.202M/Win10/IIS/SSA - WrapApp Front End for WF
Posts: 1980 | Location: Tel Aviv, Israel | Registered: March 23, 2006
Bonjour, Special VSAM aspects seem to be on the trend ... (And they are a Focus Problem, Kerry, not just Cobol). 1) Suffix = PRIVATE lead to GETPRV module. A motivated Programmer can make the link between special Files and Focus. (Could someone send me an example of reading Vsam RRDS file by Module(s) based on DDNAME (- through ACCESS PDS) 2) Suffix = YourChoice lead to a more complicated interface. Your Module must comply to the way Focus Handles different segments in a Focus DataBase. Both ways are not brand new ( except that the 1) approach does not need anymore to link GetPrv into Focsam => It's much cleaner now) I very much liked this opening onto the out world by clean Focus Exits. Very different of the nopain Clicking or DoubleClicking of our modern informatics From the past, with love Focusely
Focus Mainframe 7.6.11 Dev Studio 7.6.11 and !!! PC Focus, Focus for OS/2, FFW Six, MSO
If this provides any insight as far as solutions to connect to compressed files. The Mainframe Application is called BCMS (Billing Customer Management System)formally owned by PMS (Policy Management Systems) now owned by CSC.
I'm afraid it doesn't. Do I understand that it is only the BCMS application that accesses the files? Does PMS or CSC provide an API? In the past we have done this: In one occasion the files were VSAM but had a proprietary structure. In another there were a set of subroutines to call in order to open the files read a record travel through a hiererachy, etc. So, I think that you should contact CSC and ask for instructions. If there are none then you are probably up the proverbial creek. However, if you do get something, we can look at it here and maybe provide some help. Good luck!
Daniel In Focus since 1982 wf 8.202M/Win10/IIS/SSA - WrapApp Front End for WF
Posts: 1980 | Location: Tel Aviv, Israel | Registered: March 23, 2006
Once you find out how they are read from a 3 Generation Language (FORTRAN, COBOL , C . . ) could should be able to do the SUFFIX=PRIVATE but my preference always was to use the SUFFIX= because it is a standalone load module and not linked into a FOCUS module.