|
Jim,
Thanks. I'll forward that information.
And, now this morning we find that's not the half of it.
Bad things did happen.
Right at the moment - hopefully it happened overnight - the IP addresses for the old and new production machines both point to the old production machine.
Talk about frantic accountants!! Where's yesterday's work????
The company we outsourced with is going to fix their fix to their fix............
Thanks again,
Fran Denoncourt
Sr. Programmer/Analyst
Pinal County Treasurer's Office
Florence, AZ 85232
(520) 866-6404
Frances.Denoncourt@xxxxxxxxxxxxxxxxx
Receipt of this message does not grant you permission to send me
Unsolicited Commercial Email
<Quote> So, digging around a little more, I found that on the test systemOn 12/16/2008 at 7:59 PM, in message <A8AA1FFF8682462F81331099E9F24230@D3L5F1C1>, "Jim Franz" <franz400@xxxxxxxxxxxx> wrote:
the member name is the same as the physical where on the production system
it was not [LSOUTP001]. So, I guess FTP was trying to add the new member
because the old one was not named as expected.
</quote>
This happens when you restore a file and the file creation date on media is
different than creation date on disk and ALOWOBJDIF was not *NONE. (the
manual is not specific, but I would assume "date" includes "date & time".
The *none value would not restore file and an error issued to job log. There
are diff options for this parm - see the Backup and Recovery manual (page
229 for V5R4). It is common for some to just always change this parm to
ALOWOBJDIF(*ALL) but if you are restoring to a lib that is not empty, and
not checking the job log for these issues then bad things can happen.
Jim Franz
----- Original Message ----- From: "Frances Denoncourt" <Frances.Denoncourt@xxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, December 16, 2008 3:47 PM
Subject: Re: FTP V5R4 Upgrade - LSOUTPUT error
Rob,
That's good that it is overwritten because we have maxmbrs set to 1.
So, digging around a little more, I found that on the test system the
member name is the same as the physical where on the production system it
was not [LSOUTP001]. So, I guess FTP was trying to add the new member
because the old one was not named as expected.
Don't know how that member got there on production, but I ran the job on
the test machine with the correct member name and it was fine.
I changed the pfm name to LSOUTPUT on production. Hopefully the 4:30 run
will be Ok. I'll check the member name after the 4:30 run.
Thanks for helping me out.
Fran Denoncourt
Sr. Programmer/Analyst
Pinal County Treasurer's Office
Florence, AZ 85232
(520) 866-6404
Frances.Denoncourt@xxxxxxxxxxxxxxxxx
Receipt of this message does not grant you permission to send me
Unsolicited Commercial Email
227 Entering Passive Mode (10,10,1,213,158,129).ls *.txt (diskOn 12/16/2008 at 1:17 PM, in message
<OFE09A2618.BD3B5378-ON85257521.006F3483-85257521.006F6D7D@xxxxxxxxx>,
<rob@xxxxxxxxx> wrote:
125 List started.
250 List completed.
ls *.txt (disk227 Entering Passive Mode (10,10,1,213,206,200).
125 List started.
250 List completed.
ls *.txt (disk227 Entering Passive Mode (10,10,1,213,215,92).
125 List started.
250 List completed.
DSPFD LSOUTPUT
Maximum members . . . . . . . . . . . . . . : MAXMBRS *NOMAX
Number of members . . . . . . . . . . . . . : 1
DSPPFM LSOUTPUT
Looks like the one member just got overridden
Any chance the one member was removed and the file changed to MAXMBRS(0)?
Verify there's not a template higher up in the library list. With *ALLOBJ
authority do a
WRKOBJ *ALL/LSOUTPUT
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From:
"Frances Denoncourt" <Frances.Denoncourt@xxxxxxxxxxxxxxxxx>
To:
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date:
12/16/2008 02:42 PM
Subject:
Re: FTP V5R4 Upgrade - LSOUTPUT error
Sent by:
midrange-l-bounces@xxxxxxxxxxxx
Rob,
I sent another msg with the joblog msg about too many members.
We did not upgrade the existing machine to V5R4. We bought a new machine
which was presumably at V5R4. Not really sure about that point.
The people we outsourced to initially did a complete b/u restore on the
new machine for test purposed and then we were told to tell them which
libraries to restore when we went live.
I'd like to change the CL to remove the member, but I have this note from
a prior release on the server:
/* 01/31/2007 FDD New release Serv-U 6.3.1 returns error code 550 now
/* when no files exist
/* Be sure LSOUTPUT has at least one mbr - gets removed by FTP client
error 550 */
Sounds like a catch-22 to me.
Fran Denoncourt
Sr. Programmer/Analyst
Pinal County Treasurer's Office
Florence, AZ 85232
(520) 866-6404
Frances.Denoncourt@xxxxxxxxxxxxxxxxx
Receipt of this message does not grant you permission to send me
Unsolicited Commercial Email
<OFE5032487.02C28C4E-ON85257521.0068AA0D-85257521.0069255C@xxxxxxxxx>,On 12/16/2008 at 12:08 PM, in message
<rob@xxxxxxxxx> wrote:
If that script is ran on the i, does the job have an accompanying job log
also?
Did you do your upgrade by the:
"1 - Let's get new hardware with V5R4 loaded and restore a few libraries
and whatnot" method, or
"2 - Let's upgrade our existing hardware to V5R4 and either upgrade our
existing hardware to newer or do a complete unload/reload on to a scratch
new system"
Option 1 may say that LSOUTPUT is secured differently or any number of
options. Actually I would think that you should be able to delete it and
let it recreate. I ran a like ftp script and it got created
automatically.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From:
"Frances Denoncourt" <Frances.Denoncourt@xxxxxxxxxxxxxxxxx>
To:
<midrange-l@xxxxxxxxxxxx>
Date:
12/16/2008 01:54 PM
Subject:
FTP V5R4 Upgrade - LSOUTPUT error
Sent by:
midrange-l-bounces@xxxxxxxxxxxx
We upgraded both hardware and the O/S [V5R2 to V5R4]over the weekend. I
ran a couple of programs yesterday that put files onto a network server
with no errors.
Our clerks run programs that get files from the server. They just noticed
that data was not being retrieved - we don't get data every day from each
entity. I checked the server, we have two files sitting out there.
I think our dept is the only one that retrieves data in this manner, but I
sent this out to the other programmers with no response, so far.
I didn't see anything about this in the memo to users for both V5R3 and
V5R4.
Does anyone use scripts to retrieve data from a server?
For example:
CD /WARRANTS
LCD TRSFTP
SENDPASV
LS *.TXT (DISK
MGET *.TXT (REPLACE
MDELETE *.TXT
QUIT
I have three with at least two failing...here is one log:
LS *.TXT (DISK200 PORT Command successful.
150 Opening ASCII mode data connection for /bin/ls.
Unable to open or create target file LSOUTPUT in library TRSFTP.
226 Transfer complete.
No response received from FTP server.
Enter an FTP subcommand.
MGET *.TXT (REPLACEUnable to send data to server.
No response from remote host; all connections closed.
Enter an FTP subcommand.
MDELETE *.TXTYou must first open a connection.
Enter an FTP subcommand.
QUIT
The file is clearly in library TRSFTP:
Display Object Description - Basic
Library 2
of 2
Library . . . . . . . : TRSFTP Library ASP device . : *SYSBAS
Library ASP group . . : *SYSBAS
Type options, press Enter.
5=Display full attributes 8=Display service attributes
Opt Object Type Attribute Size Text
LSOUTPUT *FILE PF 36864 Output of LS
command
Programs that 'put' files to the server work fine, so far.
Fran Denoncourt
Sr. Programmer/Analyst
Pinal County Treasurer's Office
Florence, AZ 85232
(520) 866-6404
Frances.Denoncourt@xxxxxxxxxxxxxxxxx
Receipt of this message does not grant you permission to send me
Unsolicited Commercial Email
--
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 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.
midrange.com
