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



I think it could be the member name where the actual spoolfile data is
stored. Years ago I had to debug a printing problem and SupportLine had me
dig out the data which was in a file in the QSPL library. If I recall
correctly, the member name always started with a Q. But this wouldn't fit
with getting the user data sometimes.

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 11/03/2015 05:08:15
PM:
----- Message from Jon Paris <jon.paris@xxxxxxxxxxxxxx> on Tue, 3
Nov 2015 15:32:47 -0500 -----

To:

Rpg400 Rpg400-L <rpg400-l@xxxxxxxxxxxx>

Subject:

INFDS for Printer file

According to the IBM docs the following fields are defined in the INFDS.

...
D FILE_NAME 83 92
* File name
D LIBRARY 93 102
* Library name
D SPOOL_FILE 103 112
* Spool file name
D SPOOL_LIB 113 122
* Spool file lib
D SPOOL_NUM 123 124I 0
* Spool file num
...
I needed the spool file name and so used the one at position 103.
But that just (most often *) contains some weird combination of
letters and numbers starting with Q and has no apparent connection
with any of the other information recorded for the spool file.

This is not critical as I discovered that for my purposes the file
name in position 83 works just fine, but I just wondered if anyone
has any idea what the entry is about.

** I did notice that sometimes it appears to contain the User Data -
and not the Q… stuff but I could never figure out under what
circumstances it did that as one otherwise identical runs it
produced different results.


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.