|
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalfand use
Of Richard Schoen
Sent: Friday, July 7, 2017 10:42 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Exit point like functionality for spool files.
Stuff the attributes into the user defined data or other attributes
that info to drive file names.different
That would be the most flexible and you don't need a bunch of
queues unless you truly want to keep client docs separated.client
Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
------------------------------
message: 5
date: Fri, 7 Jul 2017 08:41:35 -0500
from: "Kevin Bucknum" <Kevin@xxxxxxxxxxxxxxxxxxx>
subject: Exit point like functionality for spool files.
Our setup has a common program library, a common data library, and a
specific library. As we switch from client to client, our menuprograms set the
current library to the client specific library. The powers that be arerolling out
a new document management system that they want to bolt on to anthat
existing workflow that uses a home grown spool file routing system
converts files to PDF's and can then route them various ways.in the
The problem I need to solve is that in order to automate the workflow
document management system, I need the client code in the PDF filename.
The options I have considered are: Go into each program and update thecode in
OVRPRTF that is already in the 99% of the programs to stuff the client
the SPLFA's. Create separate outq's in the routing system and havethose
adjust the naming based on the outq used. One is more work than Iwould
like to do, and doesn't address thinks like ad hoc queries, and theother relies
on the users knowing which outq to use, and then actually sending thespool
file there. The 99% of programs that have OVRPRTF's already use QPRINTand
QSYSPRT as the base PRTF. Unless I can come up with a better way,right now
my plan is to put a modified copy of QPRINT, QSYSPRT, QPQUPRFIL andmodified
possibly a few other print files into each client library with
USRDFNDTA to indicate the client, and then have the master routingprogram
look at that to create the file name.me to
Is there some sort of exit point that I'm not seeing that would allow
modify the SPFLA at creation time? I see some security exit points,and some
for network print server, but too many of our users bypass thesecurity
requirements of the exit point, and my understanding is that thenetwork
print server isn't involved in regular 5250 spool file creation andprinting.
list
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,http://archive.midrange.com/midrange-
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
l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.