1. Forum
  2. Newsgroups
  3. comp.lang.cobol

  • Mighty COBOL is very impatient...

    From Kellie Fitton@KELLIEFITTON@yahoo.com to comp.lang.cobol on Mon Jun 11 08:53:17 2018
    From Newsgroup: comp.lang.cobol


    Hi Folks,

    In a Windows Client/Server environment: To improve the data
    performance of large ISAM files and reduce the disk latency,
    the application creates single large index file format type,
    rebuild the indexed files periodically when needed, and sets
    large file buffers size. However, the COBOL application still
    experience the network latency even though the file server has
    large amounts of system memory. So, since the data and network
    latency are co-related with each other, the main question is:

    1). How to reduce the network latency from within the COBOL
    application?

    Thank you for your feedback.








    COBOL - the elephant that can stand on its trunk...

    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Doc Trins O'Grace@doctrinsograce@gmail.com to comp.lang.cobol on Mon Jun 11 09:40:32 2018
    From Newsgroup: comp.lang.cobol

    Dealing with this myself.

    The network seems to chatter a lot!

    One thing I did to reduce bandwidth was to place as much work on the host side as possible. An example, that might not be pertinent to you, was to use stored procedures.

    I don't know if that will help you, ma'am, but perhaps it will be the seed that will sprout other solutions.
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From docdwarf@docdwarf@panix.com () to comp.lang.cobol on Mon Jun 11 17:07:22 2018
    From Newsgroup: comp.lang.cobol

    In article <086b9173-2df2-4ffd-b253-c2a9ec42fbb0@googlegroups.com>,
    Kellie Fitton <KELLIEFITTON@yahoo.com> wrote:

    Hi Folks,

    In a Windows Client/Server environment: To improve the data
    performance of large ISAM files and reduce the disk latency,
    the application creates single large index file format type,
    rebuild the indexed files periodically when needed, and sets
    large file buffers size. However, the COBOL application still
    experience the network latency even though the file server has
    large amounts of system memory. So, since the data and network
    latency are co-related with each other, the main question is:

    1). How to reduce the network latency from within the COBOL
    application?

    Use the COBOL standard networking latency adressing protocols.

    DD
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Kellie Fitton@KELLIEFITTON@yahoo.com to comp.lang.cobol on Mon Jun 11 11:03:57 2018
    From Newsgroup: comp.lang.cobol

    On Monday, June 11, 2018 at 9:40:33 AM UTC-7, Doc Trins O'Grace wrote:
    Dealing with this myself.

    The network seems to chatter a lot!

    One thing I did to reduce bandwidth was to place as much work on the host side as possible. An example, that might not be pertinent to you, was to use stored procedures.

    I don't know if that will help you, ma'am, but perhaps it will be the seed that will sprout other solutions.


    There are some efficiencies that can be a side benefit when
    placing most of the work load on the host side, such as more
    efficient caching of the file's data, thereby removing some
    of the physical file reads and their associated disk latency.

    Thank you...
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Clark F Morris@cfmpublic@ns.sympatico.ca to comp.lang.cobol on Mon Jun 11 19:54:19 2018
    From Newsgroup: comp.lang.cobol

    On Mon, 11 Jun 2018 17:07:22 +0000 (UTC), docdwarf@panix.com () wrote:

    In article <086b9173-2df2-4ffd-b253-c2a9ec42fbb0@googlegroups.com>,
    Kellie Fitton <KELLIEFITTON@yahoo.com> wrote:

    Hi Folks,

    In a Windows Client/Server environment: To improve the data
    performance of large ISAM files and reduce the disk latency,
    the application creates single large index file format type,
    rebuild the indexed files periodically when needed, and sets
    large file buffers size. However, the COBOL application still
    experience the network latency even though the file server has
    large amounts of system memory. So, since the data and network
    latency are co-related with each other, the main question is:

    1). How to reduce the network latency from within the COBOL
    application?

    Use the COBOL standard networking latency adressing protocols.

    What COBOL standard networking latency addressing protocols on what
    platforms? This is the first I've heard of them and I started COBOL programming in 1963. There have been various things over the years
    but none of the ones I heard of have been COBOL specific. Granted I
    haven't been actively programming since 2002.

    Clark Morris

    DD
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Richard@riplin@azonic.co.nz to comp.lang.cobol on Mon Jun 11 16:40:21 2018
    From Newsgroup: comp.lang.cobol

    On Tuesday, June 12, 2018 at 3:53:18 AM UTC+12, Kellie Fitton wrote:
    Hi Folks,

    In a Windows Client/Server environment: To improve the data
    performance of large ISAM files and reduce the disk latency,
    the application creates single large index file format type,
    rebuild the indexed files periodically when needed, and sets
    large file buffers size. However, the COBOL application still
    experience the network latency even though the file server has
    large amounts of system memory. So, since the data and network
    latency are co-related with each other, the main question is:

    In a client server application where the ISAM files are on a server and the index lookup is done on the client then the system cannot cache the data and index blocks in the client to minimize latency because the files may be shared and updated by other clients.
    1). How to reduce the network latency from within the COBOL
    application?
    You run the application on the server (like I do, but that is on Linux) or you run a 'record server' on the server so that all index lookups are done there and only the required records, or groups of them, move over the network, such as MicroFocus FileShare.
    Or switch to a database server.
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From gwallace@gwallace@aceway.net to comp.lang.cobol on Tue Jun 12 00:18:08 2018
    From Newsgroup: comp.lang.cobol

    On Tuesday, 12 June 2018 01:53:18 UTC+10, Kellie Fitton wrote:
    Hi Folks,

    In a Windows Client/Server environment: To improve the data
    performance of large ISAM files and reduce the disk latency,
    the application creates single large index file format type,
    rebuild the indexed files periodically when needed, and sets
    large file buffers size. However, the COBOL application still
    experience the network latency even though the file server has
    large amounts of system memory. So, since the data and network
    latency are co-related with each other, the main question is:

    1). How to reduce the network latency from within the COBOL
    application?

    Thank you for your feedback.








    COBOL - the elephant that can stand on its trunk...
    Hi Kellie
    If the program is running on one server or workstation (client) and the data is on a network server, there is a significant time delay caused by the Network layer. It is also dependant on the Network speed.
    AcuCobol has a product called AcuServer and MF COBOL may have something similar. It basically means that most disk IO is resolved on the remote server and works pretty fast. AcuServer uses a unique port to communicate.
    I could say a lot more about this but see if this points you to where to look. To discover how fast the application could be, put both the programs and the data on the same client and do a timing test without using networked mapped or Windows share drives. To eliminate the Network layer and still use a local mapped drive here is a Command file sample.
    REM THE SUBST COMMAND ACTS LIKE A MAPPED DRIVE
    SUBST S: /D
    SUBST S: C:\DEV
    The 2nd line deletes/removes previous mapping. S: is the mapped drive.
    Greg
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From docdwarf@docdwarf@panix.com () to comp.lang.cobol on Tue Jun 12 12:18:34 2018
    From Newsgroup: comp.lang.cobol

    In article <13vthd5o1pnm5i0ss45ceb8cu118gra9ot@4ax.com>,
    Clark F Morris <cfmpublic@ns.sympatico.ca> wrote:
    On Mon, 11 Jun 2018 17:07:22 +0000 (UTC), docdwarf@panix.com () wrote:

    In article <086b9173-2df2-4ffd-b253-c2a9ec42fbb0@googlegroups.com>,
    Kellie Fitton <KELLIEFITTON@yahoo.com> wrote:

    Hi Folks,

    In a Windows Client/Server environment: To improve the data
    performance of large ISAM files and reduce the disk latency,
    the application creates single large index file format type,
    rebuild the indexed files periodically when needed, and sets
    large file buffers size. However, the COBOL application still
    experience the network latency even though the file server has
    large amounts of system memory. So, since the data and network
    latency are co-related with each other, the main question is:

    1). How to reduce the network latency from within the COBOL
    application?

    Use the COBOL standard networking latency adressing protocols.

    What COBOL standard networking latency addressing protocols on what >platforms? This is the first I've heard of them and I started COBOL >programming in 1963.

    That's exactly the point, Mr Morris. Remember 'how many programmers does
    it take to change a lightbulb?'?

    The answer to Ms Fitton's latest interview-question is 'talk to the
    networking team'.

    DD
    --- Synchronet 3.20a-Linux NewsLink 1.114