Skip to main content

C$SYSTEM sync

  • Dec 11, 2015 12:57 PM UTC
  • 3 replies
  • 18 views

Andreas Weinand
Forum|alt.badge.img+2

We experienced the following unter AcuConnect 9.2:

Our Call C$SYSTEM with CSYS-ASYNC = 0 doesn't wait anymore for the Call to finish and the program runs independently.

How can we re-establish this functionality ?

3 replies

Stephen Hjerpe
  • Participating Frequently
  • Dec 11, 2015 3:03 PM UTC

We experienced the following unter AcuConnect 9.2:

Our Call C$SYSTEM with CSYS-ASYNC = 0 doesn't wait anymore for the Call to finish and the program runs independently.

How can we re-establish this functionality ?

Are you running on Windows 8, and calling C$SYSTEM with a non-GUI program, and without using cmd.exe, the runtime would return immediately to the COBOL program, without letting the command finish. This meant that the COBOL program could not get the exit code of the command. This should be fixed in the 9.2 runtime based on ECN-4210


Andreas Weinand
Forum|alt.badge.img+2
  • Author
  • Participating Frequently
  • Nov 14, 2017 11:01 AM UTC

We experienced the following unter AcuConnect 9.2:

Our Call C$SYSTEM with CSYS-ASYNC = 0 doesn't wait anymore for the Call to finish and the program runs independently.

How can we re-establish this functionality ?

Sorry, but I have to come back to this issue:

I just found out that the problem still (or again) exists with AcuConnect version 10.0.1 for Linux under a Windows10 client !

Stephen Hjerpe
  • Participating Frequently
  • Nov 14, 2017 3:07 PM UTC

We experienced the following unter AcuConnect 9.2:

Our Call C$SYSTEM with CSYS-ASYNC = 0 doesn't wait anymore for the Call to finish and the program runs independently.

How can we re-establish this functionality ?

Please contact Customer Care with your example.