[1823] in Enterprise Print Delivery Team
Re: PI1P and PI1T queues; GLTW
daemon@ATHENA.MIT.EDU (Theresa M Regan)
Wed Oct 24 12:31:29 2001
Message-Id: <200110241630.MAA17993@melbourne-city-street.mit.edu>
Date: Wed, 24 Oct 2001 12:30:55 -0400
To: "Lynne E. Durland" <durland@MIT.EDU>, kelley@MIT.EDU
From: Theresa M Regan <tregan@MIT.EDU>
Cc: debbie@MIT.EDU, mprudden@MIT.EDU, r3-print@MIT.EDU, printdel@MIT.EDU,
rosenberg@MIT.EDU
In-Reply-To: <5.0.2.1.2.20011017154531.03d45358@hesiod>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Hi Lynne,
I am just getting around to "clean-up" related activities. Based on your
e-mail confirmation, I have deleted the following output definitions from
SF2 (they were not propagated to any other SAP R/3 environment):
AnyPrinter L POST2 IS: InfoPrint Manager Test (via IPM)
E19-IP60-ld L POST2 IS: InfoPrint Manager Test (via IPM)
W91-3160-ld L POST2 IS: InfoPrint Manager Test (via IPM)
hpjdpcl-ld L HPLJ4 IS: InfoPrint Manager Test (via IPM)
hpjdps-ld L POST2 IS: InfoPrint Manager Test (via IPM)
hppsf-ld L POST2 IS: InfoPrint Manager Test (via IPM)
np12-ld L POST2 IS: InfoPrint Manager Test (via IPM)
webprt-jeff L POST2 IS: InfoPrint Manager Test (via IPM)
When Peter has a chance, it would be most helpful to have the following
references removed from the "windsurf.mit.edu" web, as well:
E19-IP60-ld L POST2 IS: InfoPrint Manager Test (via IPM)
W91-3160-ld L POST2 IS: InfoPrint Manager Test (via IPM)
hpjdpcl-ld L HPLJ4 IS: InfoPrint Manager Test (via IPM)
hpjdps-ld L POST2 IS: InfoPrint Manager Test (via IPM)
hppsf-ld L POST2 IS: InfoPrint Manager Test (via IPM)
np12-ld L POST2 IS: InfoPrint Manager Test (via IPM)
webprt-jeff L POST2 IS: InfoPrint Manager Test (via IPM)
Thanks,
Theresa
At 03:52 PM 10/17/2001 -0400, Lynne E. Durland wrote:
>Theresa,
>
>Down below where they are near to what I am answering are my responses.
>
>At 05:16 AM 10/17/2001, Theresa M Regan wrote:
>>Hi Lynne and David,
>>
>>The "disconnect" we are feeling about agreeing to "pi1p" and "pi1t" removal
>>is we will be left with 4 queues in SAP R/3 (and its respective
>>environments) which are not only defined for specific reasons, they are
>>also restricted queues (who may print to the these queues). Example: with
>>today's authorizations in place, only a small number of people could
>>attempt to follow a print request from start to finish on gltw, glmp and
>>glte in any SAP R/3 environment.
>>
>>As IPM continues to move toward production status, it involves several
>>concepts that extend beyond R3-prints immediate concerns; however, for
>>general enterprise/administrative printing are of concern/interest to
>>PrintDel and (several of) us.
>>
>> -- production / test IPM servers -- our experiences to-date,
>>the "test print server" was not a dimension we pondered and only
>>infrequently ever tested (the APS "test" print server is not explicitly
>>referenced within the SAP R/3 output device definitions)
>>
>> -- additional practices/protocols behind selecting a print queue
>>-- example: output printed to "xxxxx" means next day delivery and/or
>>additional "to-dos" to the operators
>>
>>In an effort to bring this dialogue to a close, it is fine to delete "pi1p"
>>and "pi1t". In its place, we request a general purpose printing definition
>>be defined and propagated throughout the entire process.
>>
>>Example: a spool device & print queue named 'EP60' for the general purpose
>>IPM printing from SAP to the IBM page printers: (IBM IP60). As well as,
>>'EP62' for requesting duplex explicitly. The intended
>>use/purpose/requirements would be no different than existing printers such
>>as RET, SST1, SST2, MRP2, etc. If PrintDel wishes to have complementary
>>print queues defined for the IPM test server, that is fine, too.
>
>I can follow up and do the deletions and cleanup tomorrow. I will at the
>same time add EP60 and EP62. I am currently trying to fully understand the
>work on the IPM server side to do the EP62 and EP12 queues. I will follow
>up with Garry this week and get this in place.
>
>
>>My timing for completing and sending this response is ill-timed for
>>accessing SAP R/3 (SF2) and verifying the following list. At last glance
>>in SF2, there were several other lingering IPM output definitions...
>>
>> AnyPrinter L POST2 IS: InfoPrint Manager Test (via IPM)
>> E19-IP60-ld L POST2 IS: InfoPrint Manager Test (via IPM)
>These first two:
>Old, from original testing/evaluation server remove
>
>> RETIPM L POST2 FSS: Campus W92-253I (HP Laser Jet 5 SI/MX
>>via IPM)
>> RETIPM2 L POST2 FSS: Campus W92-253I DUPLEX (HP Laser Jet 5
>>SI/MX via IPM)
>> W91-3160-ld L POST2 IS: InfoPrint Manager Test (via IPM)
>> hpjdpcl-ld L HPLJ4 IS: InfoPrint Manager Test (via IPM)
>> hpjdps-ld L POST2 IS: InfoPrint Manager Test (via IPM)
>> hppsf-ld L POST2 IS: InfoPrint Manager Test (via IPM)
>> np12-ld L POST2 IS: InfoPrint Manager Test (via IPM)
>> webprt-jeff L POST2 IS: InfoPrint Manager Test (via IPM)
>
>These last six:
>Old, from original testing/evaluation server remove
>
>If any other information is needed please let me know.
>
>Lynne
>
>
>
>
>>Could we identify which ones should remain and insure that they are in
>>"moira" and reflected on windsurf? If they are no longer needed, we will
>>delete them from SF2. (I do not believe they were propagated to other SAP
>>R/3 environments.)
>>
>>David, lastly, there is antiquated decision that a "printer" only be
>>associated with one print server. Is the timing such that RET can be
>>served from IPM or APS, but, not both?
>>
>>Thanks,
>>Theresa
>>
>>
