× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: A quick question on spool files
  • From: "Salter, James" <JSalter@xxxxxxxxxx>
  • Date: Thu, 3 Aug 2000 11:00:42 -0500

Is there anyway to catch it midstream and change from an AFPDS spoolfile
into an SCS?

I am trying to override every last little printfile that I can think of, yet
I haven't been successful


-----Original Message-----
From: oliver.wenzel@cibavision.Novartis.com
[mailto:oliver.wenzel@cibavision.Novartis.com]
Sent: Thursday, August 03, 2000 4:43 AM
To: MIDRANGE-L@midrange.com
Subject: AW: A quick question on spool files


Hello,

this should be what you are searching for - I just got it on a newsletter.

Hth,

Oliver


============================================================================
=================

QSPGETF AND QSPPUTF APIs AND COMMANDS
IBM Knowledgebase item 8011926 describes two APIs that are 
undocumented in the AS/400 manuals. The two APIs, Get Spooled File 
(QSPGETF) and Put Spooled File (QSPPUTF), copy spool files to and 
restore them from physical files, respectively. The advantage of 
QSPGETF and QSPPUTF over the well-documented Copy Spooled File command 
(CPYSPLF) is that the APIs are able to copy Advanced Function Printing 
Data Stream (AFPDS) and Intelligent Printer Data Stream (IPDS) spool 
files, whereas CPYSPLF cannot.

You can call the QSPGETF and QSPPUTF APIs directly, or you can call 
them using command wrappers over the APIs.

a. Calling the APIs Directly
The QSPGETF API call below saves spool file QPRINT to database file 
SPOOLDB in USER1LIB library, member MBR1, where the spool file number 
is 1 and the spool file job is 010160/user1/dsp03:

CALL PGM(QSYS/QSPGETF) PARM('QPRINT ' 'SPOOLDB USER1LIB ' +
'DSP03 USER1 010160' X'0001' 'MBR1 ')

The QSPPUTF API call below creates a spool file in USER1 output queue 
in QGPL library from the MBR1 member in the SPOOLDB database file:

CALL PGM(QSYS/QSPPUTF) PARM('SPOOLDB USER1LIB ' 'USER1 QGPL ' 'MBR1 ')

b. Calling the APIs from command wrappers
The two calls below correspond to the examples above, but these 
examples use the command calls instead of calls directly to the APIs:

GETSPLF FILE(QPRINT) TOFILE(USER1LIB/SPOOLDB) +
JOB(010160/USER1/DSP03) SPLNBR(1) TOMBR(MBR1)

PUTSPLF FROMFILE(USER1LIB/SPOOLDB) OUTQ(QGPL/USER1) +
FROMMBR(MBR1)

Although the QSPGETF and QSPPUTF APIs are included in every OS/400 
release since V3R2, the commands are not included. Fortunately, you 
can obtain the compiled commands and the command source code from the 
Knowledgebase item, which can be found at

http://as400service.ibm.com/8625680A007CA5C6/0/10AFE2F98C7F5FB9862565C2007D4
6A8?Open&Highlight=2,8011926 .
 
This item was adapted from IBM Knowledgebase item 8011926

============================================================================
=================

> -----Ursprüngliche Nachricht-----
> Von:  ORiordan_Paudie@emc.com [SMTP:ORiordan_Paudie@emc.com]
> Gesendet am:  Donnerstag, 3. August 2000 10:16
> An:   MIDRANGE-L@midrange.com
> Betreff:      A quick question on spool files
> 
> Hi 
> Just a quick question to see if anybody has done this and how to do it
> 
> Is it possible to change spool files into Database members/files for query
> purposes
> and how do you do it?
> 
> Thanks in advance for your help
> 
> Regards
> Paudie O'Riordan
> Tel:  353 21 281978
> Mob: 353 86 2253508
> Fax: 353 21 281888
> Email; oriordan_paudie@emc.com
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.