EGL Development User Group

EGL Development User Group

EGL Development User Group

The EGL Development User Group is dedicated to sharing news, knowledge, and insights regarding the EGL language and Business Developer product. Consisting of IBMers, HCL, and users, this community collaborates to advance the EGL ecosystem.

 View Only
Expand all | Collapse all

VSAM Access from Cobol Runtime COBOL/CICS

  • 1.  VSAM Access from Cobol Runtime COBOL/CICS

    Posted Thu February 25, 2016 09:50 AM

    Hi Folks,

     

    Is there some way to the COBOL Runtime do not send CICS OPEN File command implicit ?  This is happen when the COBOL Runtime detect VSAM FILE in CICS is CLOSE


    what is the reason to this need ?

    The customer has a security policy in CICS and not to allow the user program to send CICS OPEN File command.

    The CICS OPEN File command is explicit send by CICS Manager when a user program send a CICS READ/Write File command.

    Regards,

    Hsieh

    .

     

     

    Hsieh


  • 2.  Re: VSAM Access from Cobol Runtime COBOL/CICS

    Posted Fri February 26, 2016 11:45 AM

    Hsieh,

     

    There is no way to bypass the open if the file is not already open.  The way I understand it works:

     

    - Does an inquire to get the file characteristics so this can be checked against the record definition.

    - If not open, sets the file open (if also enabled) and then does the inquire again since some options not valid on previous inquire if file has never been opened.

     

    What confuses me some... I thought you were working on a migration from vAGen to EGL (or CSP to EGL).  This is the way CSP and VAGen worked as well.   So, should not be a new EGL issue.

     

    Can they just make sure the file is open prior to the transactions running? 

     

     

     

    markevans


  • 3.  Re: VSAM Access from Cobol Runtime COBOL/CICS

    Posted Fri February 26, 2016 12:57 PM

    Mark,

    Yes, yes... The current behavior is same to CSP and VAGen.

    The security policy is new and the customer would like a option to turn off OPEN sent by runtime.

     

    Yes, to the new programs the solution would be to check in advance if the file is closed.

    But programs migrated from vagen has as imprementar this check, there are many programs.

     
    The migration has ended with success.

    I take and greatly appreciate your and Jeff.

    Hsieh


  • 4.  Re: VSAM Access from Cobol Runtime COBOL/CICS

    Posted Fri February 26, 2016 02:59 PM

    Hsieh,

     

    Glad to hear the migration was a success and glad we could help.

     

    The option to bypass the OPEN would have to be submitted as a request for enhancement.  We would then have to decide whether this is something we would want to do.  To my knowledge, in all the years I have been with CSP, VAGen, and now EGL, it is the first time I have heard this request.

     

    As an alternative, while this might not be practical, could something be done in a called COBOL program to deal with this security policy (read the file just to get the system to open it).  As I understand it, we do not issue the OPEN unless the INQUIRE says it is closed.   Or look at using the new Execute #CICS support in EGL (I think it works in CICS for VSE) to do a "dummy" read to get the file open.

     

    Mark

     

    markevans