RE: Exit point like functionality for spool files.

Kevin,

You have had multiple responses, and its hard to remember every response and
your comments, but here is my suggestion (I've built something like this,
plus worked with some $$ forms tools that generate an enhanced spool based
on rules). Not knowing how much you have automated the setup of clients and
especially their users and printers (plus how users are assigned default
printers and what override capabilities they have)...

Assume a data area or file found in the customer specific lib has the
customer id (I prefer files over data areas). The copying of printer files
is an issue if you have program specific print files (not QSYSPRT but like
CSH001P - you don't want them in every customer lib).

You must be assigning a default printer for every customer or perhaps every
user if customers have multiple printers or some naming routine for the
printers.
1. Every printer has a queue, usually the printer name. Lets say a customer
XYZ Corp has 3 printers XYZLABEL XYZ001 XYZ002
Set up an extra outq for each one (XYZLABELQ XYZ001Q XYZ002Q) configured
with a data queue (1 program for all queues ( or use a table to determine
printer queue names).

2. spool goes to outq with the data queue
a. program reads the entry - because you get the spool attributes
the logic should not be bad.
b. generate the pdf
c. chgsplfa to move the spooled file to the outq of the printer

you don't have to change any existing programs
the program to monitor the queues - you have to manage how you start the
writers.
If you have clp or other overrides embedded in many programs than make the
data queue monitoring outq the existing name and make the writer outq a new
name.


While I was writing this I see Don just offered a similar idea - mines just
a little wordier..
Ask any questions about the data queue or how to ensure the queue is always
monitored.
I've used this for processes that handled thousands of spools per day or
even thousands in a single batch.

Jim Franz





-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Kevin
Bucknum
Sent: Friday, July 07, 2017 1:29 PM
To: Midrange Systems Technical Discussion
Subject: RE: Exit point like functionality for spool files.

And multiple entry points. Including power users with command line access
that can just issue a CHGCURLIB. Most one off queries would be run by me,
but I'm lazy and don't want to have to think about it anymore than I want
the users to have to think about it. I think it's RFE time.

Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550

-----Original Message-----

From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Rob Berendt
Sent: Friday, July 7, 2017 11:54 AM
To: Midrange Systems Technical Discussion
Subject: RE: Exit point like functionality for spool files.

Keep in mind that apparently he wants this to work with one-off

queries, etc.

These queries would be created on the fly and not "run this query with

menu

option" kind of stuff. Therefore it wouldn't already be wrapped with

CL to do

such overrides.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600

Mail

to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Christopher Bipes <chris.bipes@xxxxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 07/07/2017 12:34 PM
Subject: RE: Exit point like functionality for spool files.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I would look a putting into the base software a way to read from a

file or

data area the override print file parameters and the data would be in

the

customer library. Write once and use for all customers. Just need to

add

the necessary parameter data somewhere in the customer library.

You may have many programs that perform the override print file, but

it

would make sense to fix it there.


Chris Bipes
Director of Information Services
CrossCheck, Inc.

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.