Re: Grabbing wrong spool file

[rob@xxxxxxxxx]

Excellent point on "why didn't the CPYSPLF abort with the message also?".

I tried duplicating this to see if maybe CPYSPLF has some sort of 
autoexpand on it.  It doesn't - the file filled.  Maybe there was some 
sort of message reply entry temporarily active?

I double checked DSPLOG and only the file MESSAGE appears as needing to 
expand.

WRKOBJ *ALL/MAXSTORAGE only shows 1 PF.  While a huge stretch it does 
remain theoretically possible that someone may have copied this strange 
spool file into a file called MAXSTORAGE higher in the library list. 
However,
1)  The To: line on my email was correct.  And that comes from MAXSTORAGE.
2)  The contents of the desired spool file were never copied into the 
email.  If MAXSTORAGE contained the data from the wrong spool file, then 
SPOOL would have had the data from the right spool file and I would have 
had data from both spool files.

I did change the job to log like a lumberjack.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




Brendan Bispham <b.bispham@xxxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/04/2003 10:07 AM
Please respond to Midrange Systems Technical Discussion
 
        To:     Midrange Systems Technical Discussion 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        Re: Grabbing wrong spool file


I know you must have already checked for *ALL/MAXSTORAGE, but if:

> I would suspect, (don't have the joblog, and the logging level was
> minimized anyway), that this did it:
>              CPYF       FROMFILE(QTEMP/SPOOL) TOFILE(QTEMP/MESSAGE) +
>                           MBROPT(*ADD) FMTOPT(*NOCHK)

...if that were the case then you would have got the 'File full' message 
when 
qtemp/spool was populated.

In other words, if it were (just) a spooled file internals issue then you 
wouldn't get a 'File full' error with MESSAGES. So there's no reason to 
believe it's an OS400 bug. 

The likely place is the other CPYF, ie MAXSTORAGE. So if WRKF 
*ALL/MAXSTORAGE 
doesn't reveal anything, then you may have to conclude that it did exist 
but 
doesn't any longer. Either way, I'd change the program so that it uses a 
different (ie more specific) name such as EMAILHEADS with mbr MAXSTORAGE 
and 
see if it happens again. Oh, and add LOGCLPGM :)

HTH


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