Is there any command in Cobol (Batch Program) to DELAY

sravindra_s · New User Joined: 29 Nov 2005 Posts: 8

Hi All,

I am writing a cobol Batch TCP/IP program . where in " need to be able to set a delay on the call so we can throttle the call e.g. 30 milliseconds between calls. "

Meaning If my input file is having 3 records.

The Cobol program will read the first record once Connection to Port is established. After that the same first record needs to be talking to the port after a delay of 30 milliseconds . This will happen 10 times for the first record.

Then it reads the second record , process is repeated again till end of file.

we are doing Load Testing .

Bill Woodger · Posted: Wed Jun 25, 2014 11:39 am

Language Environment Callable Service CEEDLYM.

Ed Goodman · Active Member Joined: 08 Jun 2011 Posts: 556 Location: USA

Out of curiosity, why do you need the delay for a read operation? Are your reads timing out?

Rohit Umarjikar · Posted: Thu Jun 26, 2014 10:03 am

You can perform n times in between the read or calls and delay the execution

Bill Woodger · Posted: Thu Jun 26, 2014 12:16 pm

Unless the secret part of the requirement was "su** of up the entire CPU", no you don't. How would you even know how many TIMES is 30ms?

Robert Sample · Posted: Thu Jun 26, 2014 6:08 pm

If you think you need a delay in a batch program, the design is wrong -- period. Batch jobs are not supposed to need delays, and you could negatively impact your entire LPAR if you do so incorrectly. Redesign the process.

sravindra_s · New User Joined: 29 Nov 2005 Posts: 8

Thanks for the reply for my earlier query.

Mean time I was trying to connect to a port . But I am getting Below error.

60 ETIMEDOUT Connect The connection timed out before it
was completed. Ensure the server application is available.

How to solve this!!!!. Tried with different Port Number as well.

enrico-sorichetti · Posted: Mon Jun 30, 2014 5:43 pm

Ed Goodman · Active Member Joined: 08 Jun 2011 Posts: 556 Location: USA

I know it can be confusing dealing with ports and connections at first.

The error message tells you something very important. It's telling you that your program tried to reach out and connect with some server that waits for connections. It tried for 60 seconds, then gave up.

So, you need to make sure that the connection you are trying to make is valid from the perspective of the running program. Remember, the program is running on the mainframe, and has to reach that server from THERE. Just because you can ping it or whatever from your desktop, does NOT mean that the mainframe can see it.

You can be dealing with an invalid address, a firewall, different IP stacks, etc. So you have to start trying to isolate each factor and make sure it's correct.

So, start with the TSO command line and try to ping that server. I would bet doughnut money that you'll find your issue right away. Not two dozen doughnuts, but you know, like a 3/$2 kind of deal.

If you CAN ping it from the mainframe. Then it probably means the port is unreachable. So if the port can be reached from say, your desktop, then it must be a firewall.

The process here is just like any other problem. You need to think about what is actually happening, then break that down into testable chunks. Then test each of those chunks in isolation.

sravindra_s · New User Joined: 29 Nov 2005 Posts: 8

Thanks for your replies.

I had not passed the IP address to Half word Binary working storage variables to call IBM provided Connect socket program.

After which I connection successful message.

Ed Goodman · Active Member Joined: 08 Jun 2011 Posts: 556 Location: USA

Great, now I have to send 2 donuts to India!

Rohit Umarjikar · Posted: Wed Jul 02, 2014 11:33 pm