× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



When I said that I opened and closed the file explicitly within the
program, it did not occur to me until after I posted the "activation
group" problem. There is no activation group problem. I did not have
the open and close in the right position in the program. Once I put the
statements where they belonged, everything went like a dream. No errors
and the FTP was successful. Thanks to all for being a sounding board
and your comments.

Dick

-----Original Message-----
From: Dick Superneau
Sent: Tuesday, September 18, 2007 11:08 AM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: RE: MIDRANGE-L Digest, Vol 6, Issue 1893

Previous posts:

date: Tue, 18 Sep 2007 11:21:00 -0500
from: CRPence <crp@xxxxxxxxxxxxxxxxxxxx>
subject: Re: FTP problem CPD0095

The error is an innocuous defect in the FTP client processing; the
client is issuing its own OVRDBF request that fails. The error is seen

for files with small record lengths; i.e. IIRC, less than 6-bytes. I
could share more details if requested; no time presently -- just firing

this off to prevent a long thread of mis-directed attempts to resolve.
I was not aware of a side effect for the PUT reporting zero bytes
sent. If the FTP is run interactive with no user overrides, I believe
the same errors occur.? If so, the zero bytes reported as well?
4myRef kwd: batch ftp 66L4AF

Regards, Chuck
--
All comments provided "as is" with no warranties of any kind
whatsoever and may not represent positions, strategies, nor views of my

employer

Dick Superneau wrote:
I have a CL that is a copy of another program that I use to FTP data
from our system to one of our customers. The program is to put two
files from our system into the directory at the customer's FTP site.
The second put is successful. The first put ends up with zero bytes
transferred even though the file on the 520 is not empty. When I
step
through the program, the override to input and override to output
does
not produce any errors. After the FTP step, the job log shows the
following two statements:

cpd0095 Numeric value for parameter SEQONLY is not valid.
cpf0001 Error found on OVRDBF command.

When I look at the first error, the detail message is: CPD0095
Numeric value for parameter SEQONLY is not valid.

It appears that the message is generated inside the FTP call itself.
Google on CPD0095 didn't help me. Can anyone give me a clue as to
what
is happening? If I leave the overrides to input and output in place,
run the program but do not call the FTP process, there is no error.
I
cannot tell from the messages what override is being talked about.

Thanks for any input, Dick

Thanks Chuck,

As per the other post, I realized that the file appeared empty when it
got to the FTP command. Now it appears that I have an activation group
problem. The RPG program is an ILE program (two modules). The program
opens and closes the data file explicitly. The CL in which it resides
has been compiled with the activation group QILE. This CL calls another
CL that has been compiled with the activation group *CALLER. If I run
debug and display the data file, I can see the data file before I make a
program call. Once the program is called and I am stepping through it,
I can not see the data file with DSPPFM from the debug program or from
an alternate screen. If I leave debug and then display the file, I can
see the data. Where am I going wrong?

Thanks, Dick




As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.