RE: Exit point like functionality for spool files. -- MIDRANGE-L

That is what the routing system is built on. I'm trying to avoid having
to have specialized outqs for each practice and report destination.
Right now we have one outq per destination. If I can get the practice
code in the SPFA's then the NEP can name the output file in such a way
that the import mechanism of the document management system can sort the
files into the proper locations.

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

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

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

Have you looked into the data queue handling for an outq? When a

spool file

goes into a RDY state, a message gets placed on a queue.

I have a couple of applications that use this to monitor a queue for a

couple

of transformations we need to do. You just need to have a NEP

listening on

the data queue.

Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power

From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> on behalf of
Kevin Bucknum <Kevin@xxxxxxxxxxxxxxxxxxx>
Sent: Friday, July 7, 2017 8:50 AM
To: Midrange Systems Technical Discussion
Subject: RE: Exit point like functionality for spool files.

That's what I'm trying to do. The question was is there an easy way to

do that

without modifying hundreds of programs or creating 50 or 60 duplicates

QPRINT and QSYSPRT print files.

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

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

From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On

Behalf 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

and use

that info to drive file names.

That would be the most flexible and you don't need a bunch of

different

queues unless you truly want to keep client docs separated.

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

client

specific library. As we switch from client to client, our menu

programs set the

current library to the client specific library. The powers that be

are

rolling out

a new document management system that they want to bolt on to an
existing workflow that uses a home grown spool file routing system

that

converts files to PDF's and can then route them various ways.

The problem I need to solve is that in order to automate the

workflow

in the

document management system, I need the client code in the PDF file

name.

The options I have considered are: Go into each program and update

the

OVRPRTF that is already in the 99% of the programs to stuff the

client

code in

the SPLFA's. Create separate outq's in the routing system and have

those

adjust the naming based on the outq used. One is more work than I

would

like to do, and doesn't address thinks like ad hoc queries, and the

other relies

on the users knowing which outq to use, and then actually sending

the

spool

file there. The 99% of programs that have OVRPRTF's already use

QPRINT

and

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 and
possibly a few other print files into each client library with

modified

USRDFNDTA to indicate the client, and then have the master routing

program

look at that to create the file name.

Is there some sort of exit point that I'm not seeing that would

allow

me to

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 the

security

requirements of the exit point, and my understanding is that the

network

print server isn't involved in regular 5250 spool file creation and

printing.

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

Help support midrange.com by shopping at amazon.com with our

affiliate

link: http://amzn.to/2dEadiD

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

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

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

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD