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
On 12/16/2008 at 1:17 PM, in message <OFE09A2618.BD3B5378-ON85257521.006F3483-85257521.006F6D7D@xxxxxxxxx>, <rob@xxxxxxxxx> wrote:
ls *.txt (disk
227 Entering Passive Mode (10,10,1,213,158,129).
125 List started.
250 List completed.
ls *.txt (disk
227 Entering Passive Mode (10,10,1,213,206,200).
125 List started.
250 List completed.
ls *.txt (disk
227 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
midrange.com
