• Subject: Changing Spool File Attributes
  • From: bvining@xxxxxxxxxxxx
  • Date: Mon, 15 Dec 97 11:44:58 CST


Though no where as easy as CHGSPLFA (which makes some sense as you are
definitely looking for a non-trivial degree of flexibility), you should be
able to accomplish this by way of system APIs.  You could use the List Spooled
Files (QUSLSPL) API with format SPLF0200 to list the APIs in the given *OUTQ
using keys such as 202 (Job name), 203 (User name), 204 (Job number), 219
(Internal spooled file identifier), 218 (Internal job identifier), and possibly
205 (Spool file number) to determine the last report generated for the current
job within this *OUTQ; and then use the Move Spooled File (QSPMOVSP) API with
the Source internal job identifier and Source internal spooled file identifier
returned by QUSLSPL (alternatively you could use CHGSPLFA rather than QSPMOVSP,
but the API will be faster as you already have the internal identifiers).

There may be an easier way, but this is the one that comes to mind first (for
me anyway).

Bruce Vining

>I wrote a CLP that calls some canned software that amongst other things
>generates a spool file on a particular outq.  This CLP simply codes a
>CHGSPLFA command to force the spool file to a different outq and to save it
>once printed.
>Now we are due an upgrade to the canned software and the vendor informs me
>that the spool file name may change with future releases.  Now I don't want
>to revisit this CLP every time the spool file name changes.
>So how can I code a CHGSPLFA or other such command to change the attributes
>of the last spool file(s) generated when I don't know the spool file
>name(s) ?  Bearing in mind that I DO NOT want to changes attributes of
>spool files that may already exist under the same profile name, or have
>been generated by a different profile but to the canned software's outq.
>Stephen Hunt
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@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 thread ...

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

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