× 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.


  1.  Home
  2. MIDRANGE-L
  3. April 2009

RE: Strange FTP problem


I found the problem. Installing the MQ client adds a few Environment Variables. One of them is:


Display Environment Var (*SYS)

Name . . . . . . . . . : QIBM_USE_DESCRIPTOR_STDIO


Value . . . . . . . . . : 'I'




If I change the Value from 'I' to 'N' in my *JOB then the old CLP worked fine.


Thanks for you help.
Jim


--- On Wed, 4/8/09, Jerry Adams <Jerry@xxxxxxxxxxxxxxx> wrote:

From: Jerry Adams <Jerry@xxxxxxxxxxxxxxx>
Subject: RE: Strange FTP problem
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date: Wednesday, April 8, 2009, 7:57 PM
I wasn't able to follow up yesterday before I left work
for a dental appointment (I'm feeling much better today,
thanks).

This morning I looked at and tested variations of overrides
in the process (CL program) that we use daily for FTP
between systems. I was, indeed, as you and Chuck pointed
out, in error. Oh, there is an override to QSYSPRT, but it
is for another part of the process, not the FTP log. When
the FTP process is run interactively without any overrides
wants to terminal session (screen), but when I run it in
batch, it printed to QPRINT. Using an override to QPRINT,
using either an OVRPRTF or OVRDBF command, seemed to have no
effect; i.e., the FTP log still went to the terminal
session. But, as you and Chuck both said, when the OVRDBF
was for STDOUT, the FTP log did go to the file that I
created. The steps in the CL that I used are:

DLTF FILE(QTEMP/FTPLOG)
MONMSG MSGID(CPF2105)
CRTPF FILE(QTEMP/FTPLOG) RCDLEN(80)
OVRDBF FILE(STDOUT) TOFILE(QTEMP/FTPLOG)

Sorry for the erroneous reply yesterday.

Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wayne
McAlpine
Sent: Tuesday, April 07, 2009 6:56 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Strange FTP problem

I would suspect then that there is a conflicting override
to QPRINT.
Why don't you simply override STDOUT to a database file
instead of a
print file?

jim t wrote:
I checked of of my other systems & it does use
QPRINT.

On the machine that I am having a problem with I
changed to

CRTPRTF FILE(QTEMP/FTPTEST) HOLD(*YES)
SAVE(*YES)
OVRPRTF FILE(QSYSPRT) TOFILE(FTPTEST)

Still no luck. Jerry, do you have a working sample
that uses QSYSPRT that I could see?


Thanks
Jim


--- On Wed, 4/8/09, Jerry Adams
<Jerry@xxxxxxxxxxxxxxx> wrote:

From: Jerry Adams <Jerry@xxxxxxxxxxxxxxx>
Subject: RE: Strange FTP problem
To: "Midrange Systems Technical
Discussion" <midrange-l@xxxxxxxxxxxx>
Date: Wednesday, April 8, 2009, 12:50 AM
I don't think it does either, Michael. I
always use
QSYSPRT.

Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of
Michael Ryan
Sent: Tuesday, April 07, 2009 11:50 AM
To: Midrange Systems Technical Discussion
Subject: Re: Strange FTP problem

I didn't know that FTP generated QPRINT
output.

On Tue, Apr 7, 2009 at 12:29 PM, jim t
<jim_t_59@xxxxxxxxx> wrote:

This is what was working in the program:

CRTPRTF FILE(QTEMP/FTPTEST)
HOLD(*YES)
SAVE(*YES)
OVRPRTF FILE(QPRINT)
TOFILE(FTPTEST)

I would see the log in the spool file.

I have just added:

CRTPF FILE(QTEMP/FTPTST)
RCDLEN(198)
OVRDBF FILE(OUTPUT)
TOFILE(QTEMP/FTPTST) MBR(FTPTST)
CPYF FROMFILE(QTEMP/FTPTST)
TOFILE(*PRINT) +
FROMMBR(FTPTST)
OUTFMT(*CHAR)
I can now see the info in a spool file, so I
know that
the log information
does exist, but it doesn't explain why the
CRTPRTF
FILE(QTEMP/FTPTEST)
HOLD(*YES) SAVE(*YES) no longer works.

When not using FTP the following still works:

CRTPRTF FILE(QTEMP/FTPTEST)
HOLD(*YES)
SAVE(*YES)
OVRPRTF FILE(QPRINT)
TOFILE(FTPTEST)

Jim



--- On Tue, 4/7/09, Michael Ryan
<michaelrtr@xxxxxxxxx> wrote:
From: Michael Ryan
<michaelrtr@xxxxxxxxx>
Subject: Re: Strange FTP problem
To: "Midrange Systems Technical
Discussion" <midrange-l@xxxxxxxxxxxx>
Date: Tuesday, April 7, 2009, 10:31 PM
That FTPA option being changed
wouldn't
change logging,
but it does indicate
that something changed stuff.

Where is this log being generated?
What's the
file
name?

On Tue, Apr 7, 2009 at 11:55 AM, jim t
<jim_t_59@xxxxxxxxx> wrote:


Nothing else was done. I can't
understand why MQ
would do it either, it
just happened at the same time MQ was
installed. I did
notice that FTPA
option ALWSSL was set to *YES after
the MQ
install
completed. I changed it
back to *NO and still no logs.

Jim

--- On Tue, 4/7/09, Norm Dennis
<nhdennis@xxxxxxxxxxx> wrote:
From: Norm Dennis
<nhdennis@xxxxxxxxxxx>
Subject: RE: Strange FTP problem
To: "'Midrange Systems
Technical
Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: Tuesday, April 7, 2009, 8:28
PM
Was there anything else
implemented at
the same
time of the
MQ install?
Application changes, PTF's,
etc.?

Did the MQ install add an entry to
a
library list
or the
user profile?
Certainly sounds odd, I
wouldn't
expect MQ to
be the
issue but the install
process may have affected
something.


Norm Dennis

-----Original Message-----
From:
midrange-l-bounces@xxxxxxxxxxxx

[mailto:midrange-l-bounces@xxxxxxxxxxxx] On
Behalf Of jim t
Sent: Tuesday, 7 April 2009 9:46
PM
To: Midrange Systems Technical
Discussion
Subject: RE: Strange FTP problem


Same thing happens for both batch
&
interactive.
Jim


--- On Tue, 4/7/09, Norm Dennis
<nhdennis@xxxxxxxxxxx>
wrote:

From: Norm Dennis
<nhdennis@xxxxxxxxxxx>
Subject: RE: Strange FTP
problem
To: "'Midrange
Systems
Technical
Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: Tuesday, April 7, 2009,
8:05
PM
Sounds like you have changed a
path/library
list
somewhere,
somehow.
Is the FTP a batch or
interactive
process?

Norm Dennis

-----Original Message-----
From:
midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On
Behalf Of
jim t
Sent: Tuesday, 7 April 2009
9:21
PM
To: Midrange Systems Technical
Discussion
Subject: Strange FTP problem


I have a strange problem that
occured after
installing
MQ
Client on one of
our AS/400's that is
running
V5R4.
Prior to installing MQ I would
see
the
output log
I.E.

OS/400 is the remote operating
system. The
TCP/IP
version
is "V5R4M0".
250 Now using naming format
"0".
Enter an FTP subcommand.
QUIT
221 QUIT subcommand received.
Press ENTER to end terminal
session.
Input read from specified
override
file.
......
......
......


After I installed & tested
MQ
I no
longer see the
above
information. I
wouldn't think MQ would
effect
FTP but I
don't
know
where else to look. Any
ideas?


Thanks
Jim



--
This is the Midrange Systems
Technical
Discussion
(MIDRANGE-L) mailing list
To post a message email:
MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or
change list
options,
visit:


http://lists.midrange.com/mailman/listinfo/midrange-l
or email:
MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a
moment to
review the
archives
at
http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems
Technical
Discussion
(MIDRANGE-L) mailing list
To post a message email:
MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or
change list
options,
visit:


http://lists.midrange.com/mailman/listinfo/midrange-l
or email:
MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a
moment to
review the
archives
at
http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems
Technical
Discussion
(MIDRANGE-L) mailing list
To post a message email:
MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or
change
list
options,
visit:


http://lists.midrange.com/mailman/listinfo/midrange-l
or email:
MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a
moment to
review
the archives
at
http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems
Technical
Discussion
(MIDRANGE-L) mailing list
To post a message email:
MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or
change
list
options,
visit:


http://lists.midrange.com/mailman/listinfo/midrange-l
or email:
MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a
moment to
review
the archives
at
http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical
Discussion
(MIDRANGE-L) mailing list
To post a message email:
MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change
list
options,
visit:

http://lists.midrange.com/mailman/listinfo/midrange-l
or email:
MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment
to
review the
archives
at
http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical
Discussion
(MIDRANGE-L) mailing list
To post a message email:
MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list
options,
visit:


http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to
review
the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical
Discussion
(MIDRANGE-L) mailing list
To post a message email:
MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list
options,
visit:

http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review
the
archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:

http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the
archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:

http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the
archives
at http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
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.