Re: Strange FTP problem -- MIDRANGE-L

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.