Re: Pulling spool files off AS/400

The following spooled file APIs could be explore for your project:

QUSLSpl (List Spooled Files)
QUSRSplA (Retrieve Spooled File Attributes)
QSpOpnSp (Open Spooled File)
QSpCrtSp (Create Spooled File)
QSpGetSp (Get Spooled File Data)
QSpPutSp (Put Spooled File Data)
QSpCloSp (Close Spooled File)

----- Original Message -----
From: "Nel Dennis" <DNel3@OLDMUTUAL.com>
To: <midrange-l@midrange.com>
Sent: Wednesday, January 09, 2002 8:11 AM
Subject: RE: Pulling spool files off AS/400 - VB?


> This message is in MIME format. Since your mail reader does not understand
> this format, some or all of this message may not be legible.
> --
> [ Picked text/plain from multipart/alternative ]
> You could also just create an Client Access Printer session and just
assign
> the printer to print to file.
>
> Then all you would do is move the required spooled file to that
outq/writer
> and it would then "print" (save to file) to the file and directory
specified
> by the user.
>
> Thanks
> Dennis Nel
>
> -----Original Message-----
> From: Adam Lang [mailto:aalang@rutgersinsurance.com]
> Sent: 08 January 2002 06:18
> To: midrange-l@midrange.com
> Subject: Re: Pulling spool files off AS/400 - VB?
>
>
> Ok, it looks like I need to go deeper into the problem at hand and the
> solution I am looking to do.
>
> Our insurance application is all green screen.  We have just started doing
> commercial insurance for New York.  There is a program with our CPP
package
> that will generate a quote.
>
> Currently brokers will call us up, ask for a quote, we will do it, print
it
> out and fax it back to them.
>
> The COO wants to make this a paperless transmission.
>
> So, out of a brainstorm session, I decided the best solution was to have
the
> quote program spit out the quote print to a unique outqueue.  I would have
a
> VB program that theperson can open to view that specific outqueue, select
> the job he wants, save it to his desktop and then he can email it off to
the
> broker.
>
> Emailing from the AS/400 is not an option.  I would prefer to write my own
> client side application as opposed to using Ops Nav, due to the fact that
it
> is not a toy everyone should be playing with.
>
> Adam Lang
> Systems Engineer
> Rutgers Casualty Insurance Company
> http://www.rutgersinsurance.com
> ----- Original Message -----
> From: "John Ross" <jross-ml@netshare400.com>
> To: <midrange-l@midrange.com>
> Sent: Tuesday, January 08, 2002 10:23 AM
> Subject: Re: Pulling spool files off AS/400 - VB?
>
>
> > What you really want to know it how OPS Nav does it. And then you assume
> > you can do it the same way. I would look at
> > http://www-1.ibm.com/servers/eserver/iseries/clientaccess/toolkit/vb.htm
(
> > at the bottom is a link
> > to
> >
>
http://www-1.ibm.com/servers/eserver/iseries/clientaccess/toolkit/vbopnav.ht
> m
> > )  but you cannot assume just because OPS Nav does it you can do it
> without
> > any code on the AS/400. That is only true if IBM gives you access to
what
> > they use to do it.
> >
> > If you can not get access or find out how Ops Nav does it. I would look
at
> > using data queues and LPR (line printer remote) (Remote outq). You can
> hook
> > a data queue to an outq and it looks like IBM shows how to read data
> queues
> > using VB to see what is in the out queue, somehow release or move the
> spool
> > file, and LPR to get the actual report. I have never seen raw data in
LPR
> > so this maybe harder then I think. I think there are some LPR VB
controls
> > you can get.
> >
> > John Ross
> >
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > To post a message email: MIDRANGE-L@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > or email: MIDRANGE-L-request@midrange.com
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> >
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>