[2555] in Enterprise Print Delivery Team

home help back first fref pref prev next nref lref last post

Re: Problem with spooling the output of the G/L Statement run

daemon@ATHENA.MIT.EDU (David M Rosenberg)
Thu May 8 11:48:22 2003

Message-ID: <1052408899.3eba7c43a9d95@webmail.mit.edu>
Date: Thu,  8 May 2003 11:48:19 -0400
From: David M Rosenberg <dmr@MIT.EDU>
Reply-to: David M Rosenberg <rosenberg@MIT.EDU>
To: Gillian Emmons <gemmons@mit.edu>
Cc: Theresa M Regan <tregan@mit.edu>, Jay Nickerson <jnicker@mit.edu>,
        r3-admin@mit.edu,
        Enterprise Printing Delivery Project Team <printdel@mit.edu>,
        Infrastructure Services Service Team <isst@mit.edu>, debbie@mit.edu,
        mprudden@mit.edu, klyons@mit.edu
In-Reply-To: <5.1.0.14.2.20030508090824.01c62330@hesiod>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Quoting Gillian Emmons <gemmons@MIT.EDU>:
> Hi, will we need to re-submit lost SAP jobs, or are they still in the queue 
> somewhere?

Gill,

It should not have been necessary to rerun any jobs that had finished or to 
re-generate any G/L Statement files which were generated. (As always, a G/L 
statement file that was being generated when the system went down can't be added 
to - it must be re-generated from the beginning of that file. That is why the 
job produces a bunch of separate files, each of which takes an average of a half 
hour to generate.)

Some problem (which I believe Sebastien is looking into) prevented ZGLSMNT's job 
log from being visible in its entirety, which in turn, prevented the automatic 
continuation job from continuing automatically.

When Jay manually created a continuation job yesterday, he appeared to have some 
problems and ended up re-doing the full G/L statement job. Jay told me that he 
arranged with people at DOST so that only one copy of the duplicated G/L 
statement files would be printed. Because Jay re-ran the full job, it was again 
interrupted when the system went down last night. This morning Jay again 
manually created a continuation job. This time he was successful in continuing 
from the point where the job was interrupted.

In general a full G/L statement run produces about 38 files. In this case, 31 
files were produced from the run on Tuesday, another 21 files were produced from 
the run on Wednesday, and the last 17 files should be produced today. Of those 
69 files, only 38 of them should be printed.

Please contact me if I can be of any help. Today (Thursday) I'm at Lincoln at 
181-2344.

-- 
/David M Rosenberg

home help back first fref pref prev next nref lref last post