If you put *INLR on then open files will be closed when leaving the program.
The next time you call the program all files not specified with usropn will be opened
and the variables are initialized.
If you leave the program without setting *INLR on then the files are left open and
the variables are left with the values they currently have.
When the program is called again then the variables still have the values they had when
the program was left. It is then up to you to take care of initialization of them.
The files are also left open. Thus you don’t have the overhead to reopen them.
Many years ago I found a program that opened the files, did what it had to do, then closed
the files again. It was called many times. I found out that opening/closing the files took about
50% of the execution time.
You just have to take care that records are not left locked when leaving the program.
Regards
Peder
Fra: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx <ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx>
På vegne af she lumbera
Sendt: 28. september 2020 03:42
Til: Brad Stone <bvstone@xxxxxxxxx>; ftpapi@xxxxxxxxxxxxxxxxxxxxxx
Emne: Re: [Ftpapi] SetError() #2: Host name look up failed
CAUTION: This email originated
from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
I read this somewhere in the archive.
Created EXAMPLE1 using www.yahoo.com. Figured it was better to DOS yahoo than Scott's server ;)
Created a second program that called that one 1000 times in a loop.
Ran fine. No errors.
Changed the program into a module, took off LR and replaced with return. CALLP for 1000 times in a loop.
Ran fine. No errors.
And this from the internet
As a rule, never seton LR when a program will be called multiple times. This rule most definitely applied to a trigger program that could be called hundreds
or possibly thousands of times.
My program will be called a lot of times, does it mean I cannot make use of
This is how my program ends
It seems the issue is intermittent. After processing a lot of records already, the first few will be successful and then the others will fall into this error.
Do you know if I need to initialize headers or anything?
On Saturday, 26 September 2020, 12:21:03 am GMT+8, Brad Stone <bvstone@xxxxxxxxx> wrote:
Ask your network admin what DNS servers you should be using, then double check they are specified in CFGTCP option 12 in the DNS servers section.
You won't always get a response on the PING, but it should show it resolves to an IP address in the job log.
Someone may have also set up a host table entry for one of the host names. Big no no.
Even if I connect to 2 different URLs, it should be using the same DNS right?
Not sure, if it is our network configuration but I cannot ping both in the command line although I can see based on the logs and the output that we are able
to connect to URL1.
On Friday, 25 September 2020, 10:56:01 pm GMT+8, Brad Stone <bvstone@xxxxxxxxx> wrote:
Ping the hose name from the command line. And double check it's right. Then double check the DNS servers listed in CFGTCP option
12.
I hope anyone can help me.
We have been accessing 2 URLs using HTTPAPI. We are getting successful message from the first URL but are getting Error #2 on the 2nd. I have been reading similar
issues in the archive and one of which is pointing to the DNS resolver. In my case, it couldn't be the cause as we are using the same machine. Can anyone give me an idea what to look for or to check to solve the issue?
2020-09-25-15.11.00.233000: http_persist_open(): entered
2020-09-25-15.11.00.244000: http_long_ParseURL(): entered
2020-09-25-15.11.00.253000: DNS resolver retrans: 2
2020-09-25-15.11.00.253000: DNS resolver retry : 2
2020-09-25-15.11.00.253000: DNS resolver options: x'00000136'
2020-09-25-15.11.00.257000: DNS default domain: XXXX.XX
2020-09-25-15.11.00.258000: DNS server found: XXX.XX.XXX.X
2020-09-25-15.11.00.258000: DNS server found: XXX.XX.XXX.X
2020-09-25-15.11.00.320000: Nagle's algorithm (TCP_NODELAY) disabled.
2020-09-25-15.11.00.781000: SetError() £13: HTTP/1.1 201 Created
2020-09-25-15.11.00.781000: http_close(): entered
2020-09-25-15.25.49.562000: http_persist_open(): entered
2020-09-25-15.25.49.569000: http_long_ParseURL(): entered
2020-09-25-15.25.49.569000: DNS resolver retrans: 2
2020-09-25-15.25.49.569000: DNS resolver retry : 2
2020-09-25-15.25.49.569000: DNS resolver options: x'00000136'
2020-09-25-15.25.49.569000: DNS default domain:
XXXX.XX
2020-09-25-15.25.49.569000: DNS server found:
XXX.XX.XXX.X
2020-09-25-15.25.49.569000: DNS server found:
XXX.XX.XXX.X
2020-09-25-15.25.49.569000: SetError() #2: Host name look up failed.
2020-09-25-15.25.49.569000: http_close(): entered
--
_______________________________________________
Ftpapi mailing list
Ftpapi@xxxxxxxxxxxxxxxxxxxxxx
http://scottklement.com/mailman/listinfo/ftpapi
This email and any files transmitted with it may be confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify the sender.
|