Skip to main content

[archive] Accept System-information From System-info

  • May 15, 2009
  • 6 replies
  • 0 views
D

[Migrated content. Thread originally posted on 15 May 2009]

ACCEPT SYSTEM-INFORMATION FROM SYSTEM-INFO

I just wonder how acuCOBOL accomplish this function, how "ACCEPT" to acquire the system information?

My customer covers their data(vision files) with old date data, but
ACCEPT SYSTEM-INFORMATION FROM SYSTEM-INFO fails to excute.

I suggest the customer rebooting their server(windows2003).

Since this server also run other important applications, is there any way without rebooting the server to solve this reading system information failure issue?

    6 replies

    D

    [Migrated content. Thread originally posted on 15 May 2009]

    ACCEPT SYSTEM-INFORMATION FROM SYSTEM-INFO

    I just wonder how acuCOBOL accomplish this function, how "ACCEPT" to acquire the system information?

    My customer covers their data(vision files) with old date data, but
    ACCEPT SYSTEM-INFORMATION FROM SYSTEM-INFO fails to excute.

    I suggest the customer rebooting their server(windows2003).

    Since this server also run other important applications, is there any way without rebooting the server to solve this reading system information failure issue?
    I have never seen this type of behavior before. The runtime calls the Windows API to get the system information and no one has ever reported it failing to work.

    I would suggest checking to see what changed on the customers machine before this behavior started (OS update, 3rd party installation, relink of the runtime, etc).
    D

    [Migrated content. Thread originally posted on 15 May 2009]

    ACCEPT SYSTEM-INFORMATION FROM SYSTEM-INFO

    I just wonder how acuCOBOL accomplish this function, how "ACCEPT" to acquire the system information?

    My customer covers their data(vision files) with old date data, but
    ACCEPT SYSTEM-INFORMATION FROM SYSTEM-INFO fails to excute.

    I suggest the customer rebooting their server(windows2003).

    Since this server also run other important applications, is there any way without rebooting the server to solve this reading system information failure issue?
    I have never seen this type of behavior before. The runtime calls the Windows API to get the system information and no one has ever reported it failing to work.

    I would suggest checking to see what changed on the customers machine before this behavior started (OS update, 3rd party installation, relink of the runtime, etc).
    D

    [Migrated content. Thread originally posted on 15 May 2009]

    ACCEPT SYSTEM-INFORMATION FROM SYSTEM-INFO

    I just wonder how acuCOBOL accomplish this function, how "ACCEPT" to acquire the system information?

    My customer covers their data(vision files) with old date data, but
    ACCEPT SYSTEM-INFORMATION FROM SYSTEM-INFO fails to excute.

    I suggest the customer rebooting their server(windows2003).

    Since this server also run other important applications, is there any way without rebooting the server to solve this reading system information failure issue?
    I have never seen this type of behavior before. The runtime calls the Windows API to get the system information and no one has ever reported it failing to work.

    I would suggest checking to see what changed on the customers machine before this behavior started (OS update, 3rd party installation, relink of the runtime, etc).
    D

    [Migrated content. Thread originally posted on 15 May 2009]

    ACCEPT SYSTEM-INFORMATION FROM SYSTEM-INFO

    I just wonder how acuCOBOL accomplish this function, how "ACCEPT" to acquire the system information?

    My customer covers their data(vision files) with old date data, but
    ACCEPT SYSTEM-INFORMATION FROM SYSTEM-INFO fails to excute.

    I suggest the customer rebooting their server(windows2003).

    Since this server also run other important applications, is there any way without rebooting the server to solve this reading system information failure issue?
    I have never seen this type of behavior before. The runtime calls the Windows API to get the system information and no one has ever reported it failing to work.

    I would suggest checking to see what changed on the customers machine before this behavior started (OS update, 3rd party installation, relink of the runtime, etc).



    The fact is clear now, it is not "ACCEPT" issue.

    The customer reported a wrong scenario, and lead me to the wrong suspection.

    Anyway, thanks JonOn.
    D

    [Migrated content. Thread originally posted on 15 May 2009]

    ACCEPT SYSTEM-INFORMATION FROM SYSTEM-INFO

    I just wonder how acuCOBOL accomplish this function, how "ACCEPT" to acquire the system information?

    My customer covers their data(vision files) with old date data, but
    ACCEPT SYSTEM-INFORMATION FROM SYSTEM-INFO fails to excute.

    I suggest the customer rebooting their server(windows2003).

    Since this server also run other important applications, is there any way without rebooting the server to solve this reading system information failure issue?
    I have never seen this type of behavior before. The runtime calls the Windows API to get the system information and no one has ever reported it failing to work.

    I would suggest checking to see what changed on the customers machine before this behavior started (OS update, 3rd party installation, relink of the runtime, etc).



    The fact is clear now, it is not "ACCEPT" issue.

    The customer reported a wrong scenario, and lead me to the wrong suspection.

    Anyway, thanks JonOn.
    D

    [Migrated content. Thread originally posted on 15 May 2009]

    ACCEPT SYSTEM-INFORMATION FROM SYSTEM-INFO

    I just wonder how acuCOBOL accomplish this function, how "ACCEPT" to acquire the system information?

    My customer covers their data(vision files) with old date data, but
    ACCEPT SYSTEM-INFORMATION FROM SYSTEM-INFO fails to excute.

    I suggest the customer rebooting their server(windows2003).

    Since this server also run other important applications, is there any way without rebooting the server to solve this reading system information failure issue?
    I have never seen this type of behavior before. The runtime calls the Windows API to get the system information and no one has ever reported it failing to work.

    I would suggest checking to see what changed on the customers machine before this behavior started (OS update, 3rd party installation, relink of the runtime, etc).



    The fact is clear now, it is not "ACCEPT" issue.

    The customer reported a wrong scenario, and lead me to the wrong suspection.

    Anyway, thanks JonOn.

    Recent badge winners

    Explore all badges
    Terms & ConditionsAccessibility statement